Effective Company Strategies for KI Planning and Merging Proposals
Discover how companies can collaborate to optimize Key Issue planning, minimize document submission quotas, and streamline proposals for seamless integration. Explore the benefits of merging multi-company KI proposals and enhancing collaboration to achieve shared objectives efficiently.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
SA2 FS_AIMLsys Work Plan SA2 FS_AIMLsys Work Plan OPPO, Samsung 3/21/2025
FS_AIMLsys Study Phase Work Plan TR 23.700-80 TR 23.700-80 Submission to Sep. 2022 TSG SA#97 for Information TR 23.700-80 Submission to Dec. 2022 TSG SA#98 for Approval (1) TR Skeleton, Scope & New KIs approval & architecture assumptions & possible reference architecture (2) Last meeting for New KIs approval, start of new solutions approval, continuing the architecture assumption & possible reference architecture discussions (3) Last meeting for new solutions approval, TR solution clean up, start of solution evaluation FS_AIMLsys Key Issue Template: - High-level Descriptions Identify target objective from the SID - Specific Technical Issue(s) (4) TR solution clean-up, solution evaluation, start of conclusions (5) Study phase conclusion 3/21/2025
FS_AIMLsys Companys Interests on KI Planning Motivation: Encouraging joint company proposal to minimize chances for exceeding tdoc quota due to TU allocation per meeting FS_AIMLsys WT interests Objective 2 WT#1.2 X Objective 3 WT#1.3 X Objective 1 Company WT#1.1.a WT#1.1.b WT#1.1.c WT#1.1.d X ZZZ During the Jan. 13th Pre-SA2#149e FS_AIMLsys CC discussions, if possible, please identify company s interests on KI submissions, more specifically, for which particular objective(s) from the approved FS_AIMLsys SID, SP-211648 Rapporteur will collect all the info and publish for the consolidated list to encourage contributing companies to work together the joint PCR to minimize changes for exceeding tdoc quota due to the TU allocation per meeting.
FS_AIMLsys PCR Merging Proposal for KIs Motivation: Merge multi-company proposals for KIs targeting the same objective in the SID before the SA2 meeting in order to minimize chances for exceeding tdoc quota due to TU allocation per meeting In order to reduce number of submissions that exceed the tdoc quota due to the TU allocation, companies are encouraged to merge their PCRs in advance to maximize the proposed KI to be discussed during the SA2 meeting Company-A KI-X => Objective-n If quota is still exceeded after deadline, agenda recommendation by rapporteurs may comprise the following: mergers across similar contributions with basis document selection tdoc selection considering per-WT TU allocation, fairness across companies, multi-company contribution prioritization, unhandled tdocs from previous meetings, etc. Company-A, B, C KI-I => Objective-n KI-J => Objective-n Company-B KI-Y => Objective-n Company-C KI-Z => Objective-n
FS_AIMLsys KI Description Template Motivation: Streamline KI descriptions in the TR 23.700-80 PCR for the KI submission Discussions Targeting for which objective(s) in the FS_AIMLsys Background info Justification Will not be captured in the TR Proposal Targeting for which objective(s) in the FS_AIMLsys High-level Descriptions Brief but concise technical details for the KI listed in bullets Will be captured in the TR tagged with the approve tdoc# in the revision mark
