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 .
Information Disclosure Statement
The information disclosure statement submitted on March 1, 2024 has been considered by the Examiner and made of record in the application file.
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-30 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Baskaran et al (US Pat. Pub. No. 2024/0388894).
Regarding claim 1, Baskaran et al discloses an apparatus for wireless communications, comprising:
at least one memory (see at least paragraph 47 [memory]) comprising instructions; and
at least one processor (see at least paragraph 47 [processor]) coupled to the at least one memory and configured to:
receive a user equipment (UE) parameters update (UPU) container, the UPU container (see at least paragraph 73 discloses UPU data container) comprising a UE parameters update header information element (IE) and a UE parameters update list IE, wherein the UE parameters update header IE comprises UE parameters update header information, and wherein the UE parameters update list IE comprises the UE parameters update header information of the UE parameters update header IE (see at least paragraphs 101-102 discloses UE receives UE parameter update (UPU) data; further UE receiving parameter update header and data list; paragraph 58 discloses that UPU procedure using routing identifier and NSSAI for updating; NSSAI considered as UE parameters update list IE); and
generate, based on the UE parameters update list IE, a UPU message authentication code (MAC) for verifying integrity of the UPU container (see at least paragraphs 103-104 discloses successfully verified integrity).
Regarding claim 2, Baskaran et al discloses the UPU container is a UPU transparent container with a data type value of 0 (see at least paragraph 126 discloses that UPU transparent container).
Regarding claim 3, Baskaran et al discloses the UE parameters update header information is included as a data set type in the UE parameters update list IE (see at least paragraph 107 discloses UPU data set type).
Regarding claim 4, Baskaran et al discloses the UE parameters update list IE
further comprises at least one of routing indicator update data, default configured Network Slice Selection Assistance Information (NSSAI) update data, disaster roaming information update data, or Mobile Equipment (ME) routing indicator update data (see at least paragraph 60 discloses that UPU procedure using routing identifier and NSSAI for updating).
Regarding claim 5, Baskaran et al discloses the UPU MAC is a UPU-MAC-I.sub.AUSF MAC (see at least paragraph 99 discloses UPU MAC).
Regarding claim 6, Baskaran et al discloses the at least one processor is configured to generate the UPU MAC based on the UE parameters update list IE and based on a key (see at least paragraph 114 discloses UPU MAC).
Regarding claim 7, Baskaran et al discloses the key is a K.sub.AUSF key (see at least paragraph 99 discloses K.sub.AUSF).
Regarding claim 8, Baskaran et al discloses the apparatus is a UE (see at least paragraph 60 [UE, 402]).
Regarding claim 9, Baskaran et al discloses the at least one processor is configured to determine the UE parameters update header information of the UE parameters update header IE matches the UE parameters update header information of the UE parameters update list IE to verify integrity of the UE parameters update header information of the UE parameters update header IE (see at least paragraph 103 discloses verifies integrity based on successful match).
Regarding claim 10, Baskaran et al discloses the at least one processor is
configured to generate the UPU MAC using the UE parameters update header
information of the UE parameters update list IE (see at least paragraph 104).
Regarding claim 11, Baskaran et al discloses a method of wireless communications at a network device (see at least paragraph 60 [UE, 402]), the method comprising:
receiving a user equipment (UE) parameters update (UPU) container, the UPU container (see at least paragraph 73 discloses UPU data container) comprising a UE parameters update header information element (IE) and a UE parameters update list IE, wherein the UE parameters update header IE comprises UE parameters update header information, and wherein the UE parameters update list IE comprises the UE parameters update header information of the UE parameters update header IE (see at least paragraphs 101-102 discloses UE receives UE parameter update (UPU) data; further UE receiving parameter update header and data list; paragraph 58 discloses that UPU procedure using routing identifier and NSSAI for updating; NSSAI considered as UE parameters update list IE); and
generating, based on the UE parameters update list IE, a UPU message authentication code (MAC) for verifying integrity of the UPU container (see at least paragraphs 103-104 discloses successfully verified integrity).
Regarding claim 12-20, see above rejection of claims 2-10.
Regarding claim 21, Baskaran et al discloses an apparatus for wireless communications, comprising:
at least one memory (see at least paragraph 54 [memory]) comprising instructions; and
at least one processor (see at least paragraph 54 [processor]) coupled to the
at least one memory and configured to:
generate a user equipment (UE) parameters update (UPU) container, the UPU container (see at least paragraphs 73 discloses UPU data container) comprising a UE parameters update header information element (IE) and a UE parameters update list IE, wherein the UE parameters update header IE comprises UE parameters update header information, and wherein the UE parameters update list IE comprises the UE parameters update header information of the UE parameters update header IE (see at least paragraphs 96 and 101-102 discloses UDM invokes UE parameter update (UPU) data; further UE parameter update include UPU header and data list; paragraph 58 discloses that UPU procedure using routing identifier and NSSAI for updating; NSSAI considered as UE parameters update list IE); and
transmit the UPU container to a UE (see at least paragraphs 101-102 discloses transmits UE parameter update (UPU) data to UE).
Regarding claim 22, Baskaran et al discloses the UPU container is a UPU transparent container with a data type value of 0 (see at least paragraph 126 discloses that UPU transparent container).
Regarding claim 23, Baskaran et al discloses wherein, to generate the UPU container, the at least one processor is configured to add the UE parameters update header information as a data set type in the UE parameters update list IE (see at least paragraph 107 discloses UPU data set type).
Regarding claim 24, Baskaran et al discloses the UE parameters update list IE further comprises at least one of routing indicator update data, default configured Network Slice Selection Assistance Information (NSSAI) update data, disaster roaming information update data, or Mobile Equipment (ME) routing indicator update data (see at least paragraph 60 discloses that UPU procedure using routing identifier and NSSAI for updating).
Regarding claim 25, Baskaran et al discloses the apparatus is a Unified Data Management (UDM) entity (see at least paragraph 60 [UDM, 408]).
Regarding claim 26, Baskaran et al discloses a method of wireless communications at a network entity (see at least paragraph 60 [UDM, 408]), comprising:
generating a user equipment (UE) parameters update (UPU) container, the UPU container (see at least paragraphs 73 discloses UPU data container) comprising a UE parameters update header information element (IE) and a UE parameters update list IE, wherein the UE parameters update header IE comprises UE parameters update header information, and wherein the UE parameters update list IE comprises the UE parameters update header information of the UE parameters update header IE (see at least paragraphs 96 and 101-102 discloses UDM invokes UE parameter update (UPU) data; further UE parameter update include UPU header and data list; paragraph 58 discloses that UPU procedure using routing identifier and NSSAI for updating; NSSAI considered as UE parameters update list IE); and
transmitting the UPU container to a UE (see at least paragraphs 101-102 discloses transmits UE parameter update (UPU) data to UE).
Regarding claim 27-30, see above rejection of claims 22-25.
Conclusion
The prior art made of record and not relied upon is considered pertinent to Applicant's disclosure.
The following prior art are cited to show a method, which is considered pertinent to the claimed invention:
Atarius et al (US Pat. Pub. No. 2024/0381281) directed toward performing UPU procedure.
Koshta et al (US Pat. Pub. No. 2022/0053316) directed toward perform a UPU procedure based on information received.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LITON MIAH whose telephone number is (571)270-3124. The examiner can normally be reached Mon - Fri 7:30am -5:00pm.
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, Rafael Perez-Gutierrez can be reached on 571-272-7915. 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.
/LITON MIAH/ Primary Examiner, Art Unit 2642
Prosecution Insights