DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Examiner has considered Amendment after Non-Final mailed 4/30/2026.
Claims 1-20 are pending.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-5, 7-10, 15-20 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Chen Larsson et al. US 20250330373.
Regarding claim 1, A method of a user equipment (UE) (UE, Figure 3, element 310) in a mobile communication system, network node NW, Figure 3, element 320), UE capability information including information on one or more artificial intelligence (AI)/machine learning (ML) functionalities supported by the UE (the UE sends ML model support information to the NW as part of capability report, Figure 3, element 330, para. 0108, 0144, providing one or more indications of ML model support information to a network node that describes one or more ML models available at the UE, the one or more indications of ML model support information indicating at least one of; one or more model indicators; and one or more model version indicators, para. 0187); receiving, from the base station, AI/ML functionality-related information (NW determines a model ID based on the received information and sends that ML model ID to the UE, Figure 3, element 340, the ML model identifier comprises a short model identifier, the short model identifier configured to be at least one of: unique for the UE for an identified ML model for at least a current session; a number of bits determined by the maximum number of concurrent configured models for the UE; comprised of additional fields including at least one of a model type code and a version number. In some cases, the ML model identifier comprises a long model identifier, the long model identifier configured to be unique for the same model type or model version over multiple sessions and for multiple UEs and allows consistent model identifier allocation over time and across the network, para. 0188); determining at least one applicable AI/ML functionality based on the received AI/ML functionality-related information and an availability of a valid AI/ML model in the UE; and transmitting, to the base station, information indicating the determined at least one applicable AI/ML functionality (the UE and NW engage in model handling signaling using the model ID, para. 0350).
Regarding claim 2, the method of claim 1, wherein, the AI/ML functionality- related information includes at least one of network configuration information, operation scenario, operation zone information, or area information divided for collecting dataset (NW determines a model ID based on the received information and sends that ML model ID to the UE, Figure 3, element 340, the ML model identifier comprises a short model identifier or long model identifier).
Regarding claim 3, The method of claim 1, wherein the information related to the at least one AI/ML model corresponding to the at least one applicable AI/ML functionality includes AI/ML model information supported for each AI/ML functionality-related network configuration is identified (the UE and NW engage in model handling signaling using the model ID, para. 0350, the gNB may initially determine a provisional model ID with contacting the coordination node, signal it to the UE, model operation and handling procedures may be temporarily carried out using the provisional ID while the gNB communicates so that it may revise the model ID if such a model is already present in the database and the gNB may then update the model ID to the revised value for further communication with the UE, para. 0157).
Regarding claim 4, The method of claim 1, further comprising: receiving, from the base station, a UE capability enquiry wherein the UE capability information is transmitted as a response to the UE capability enquiry (the UE transmits the at least one ML version or other ML capability info of at least one ML model to the NW node as part of the UE capability transfer procedure, included in the UECapabilityInformation message, as one or more Information Element(s) (IEs) and/or fields, this is transmitted by the UE in response to the reception of a UECapabilityEnquire message, the UECapabilityEnquire message may include an indication for the report of a specific ML version or other ML support info, para. 0144).
Regarding claim 5, The method of claim 4, wherein, in the transmitting the UE capability information to the base station in response to the UE capability enquiry, the UE capability information including the AI/ML functionalities and network configuration information supported for each AI/ML functionality is forwarded to the base station (the UE transmits the at least one ML version or other ML capability info of at least one ML model to the NW node as part of the UE capability transfer procedure, included in the UECapabilityInformation message, as one or more Information Element(s) (IEs) and/or fields, this is transmitted by the UE in response to the reception of a UECapabilityEnquire message, the UECapabilityEnquire message may include an indication for the report of a specific ML version or other ML support info, para. 0144).
Regarding claim 7, The method of claim 4, wherein, in the transmitting the UE capability information to the base station in response to the UE capability enquiry, general UE capability information and AI/ML functionality-related UE capability information are reported individually (the UE transmits the at least one ML version or other ML capability info of at least one ML model to the NW node as part of the UE capability transfer procedure, included in the UECapabilityInformation message, as one or more Information Element(s) (IEs) and/or fields, this is transmitted by the UE in response to the reception of a UECapabilityEnquire message, the UECapabilityEnquire message may include an indication for the report of a specific ML version or other ML support info, para. 0144) or in an integrated process based on a result of decision on whether to report the general UE capability information and the AI/ML functionality-related UE capability information in respective processes or not.
Regarding claim 8, The method of claim 1, wherein the AI/ML functionality- related information includes radio source control (RRC) configuration or configuration information (NW determines a model ID based on the received information and sends that ML model ID to the UE, Figure 3, element 340, the model ID may be received by the UE using RRC signaling, para. 0060).
Regarding claim 9, The method of claim 1,wherein the UE capability information or the AI/ML functionality-related information includes a functionality identifier (functionality ID) (NW determines a model ID based on the received information and sends that ML model ID to the UE, Figure 3, element 340, obtaining the ML model ID comprises determining the model ID having multiple parts, comprising one or more of functionality and configuration, para. 0073).
Regarding claim 10, The method of claim 18, wherein, the information related to at least one AI/ML model corresponding to the at least one applicable AI/ML functionality includes at least one of model ID information or model information supported for each AI/ML functionality-related network configuration, along with functionality ID information supported for each AI/ML functionality- related network configuration (NW determines a model ID based on the received information and sends that ML model ID to the UE, Figure 3, element 340, obtaining the ML model ID comprises determining the model ID having multiple parts, comprising one or more of functionality and configuration, para. 0073).
Claims 15-20 are rejected under the same rationale.
Allowable Subject Matter
Claims 6, 11-14 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Response to Arguments
Applicant’s arguments have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MELANIE JAGANNATHAN whose telephone number is (571)272-3163. The examiner can normally be reached M-F 9-5.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Marcus Smith can be reached at 571-270-1096. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MELANIE JAGANNATHAN/Primary Examiner, Art Unit 2468
Prosecution Insights