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 .
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-14 of U.S. Patent No. 12,245,091. Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of continuation application no. 19/036,235 are directed to the same inventive concept as the patented claims 1-14 of U.S. Patent No. 12,245,091, except that the claims in the continuation belong to different statutory categories and therefore, the claims in the continuation are obvious variants of the patented claims.
Application No. 19/036,235
U.S. Patent No. 12,245,091
1.A non-transitory computer-readable storage medium, storing instructions, wherein the instructions, when executed by a processor of a terminal device, cause the terminal device to implement:
sending a currently available first radio capability identifier of the terminal device to a first network node, in a case that a network node change-related condition is satisfied, wherein the terminal device supports radio capability signaling optimization (RACS);
wherein the network node change-related condition comprises: a security mode command carries a UE radio capability identifier request information element, the security mode command is sent by the first network node in a case that the terminal device supports RACS and a second network node does not support RACS; a condition for determining that the second network node does not support RACS comprises: a radio capability identifier of the terminal device is not contained in a context,
wherein the context is a context of the terminal device acquired from the second network node;
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and
wherein the first network node comprises a mobility management entity (MME).
1.A method for transmitting a radio capability identifier, applicable to a terminal device, wherein the terminal device supports radio capability signaling optimization RACS, the method comprising:
sending a currently available first radio capability identifier of a terminal device to a first network node, in a case that a network node change-related condition is satisfied;
wherein the network node change-related condition comprises: a security mode command carries a UE radio capability identifier request information element, the security mode command being sent by the first network node in a case that the terminal device supports RACS and a second network node does not support RACS; a condition for determining that the second network node does not support RACS comprises: a radio capability identifier of the terminal device is not contained in a context,
wherein the context is a context of the terminal device acquired from the second network node;
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and
wherein the first network node comprises a Mobility Management Entity (MME).
2. The storage medium according to claim 1, wherein the sending a currently available first radio capability identifier of the terminal device to a first network node comprises: sending the currently available first radio capability identifier of the terminal device to the first network node in a first message, wherein the first message includes one of: a registration request message or a security mode complete message.
2. The method according to claim 1, wherein the sending a currently available first radio capability identifier of a terminal device to a first network node comprises: sending the currently available first radio capability identifier of the terminal device to the first network node in a first message, wherein the first message includes one of: a registration request message or a security mode complete message.
3. The storage medium according to claim 1, wherein the network node change-related condition comprises at least one of the following: the terminal device moves out of a current tracking area list; the terminal device performs an inter-system change; the terminal device selects a new public land mobile network (PLMN); a configuration update command message received by the terminal device from the network node carries a registration request bit with a value of 1; or the terminal device initiates a registration update process.
3. The method according to claim 1, wherein the network node change-related condition further comprises at least one of the following: the terminal device moves out of a current tracking area list; the terminal device performs an inter-system change; the terminal device selects a new public land mobile network PLMN; a configuration update command message received by the terminal device from the first network node carries a registration request bit with a value of 1; or the terminal device initiates a registration update process.
4. The storage medium according to claim k, wherein the instructions, when executed by the processor of the terminal device, cause the terminal device to further implement: after sending the currently available first radio capability identifier of the terminal device to the first network node, receiving a second radio capability identifier sent by the first network node, wherein the second radio capability identifier matches a current radio capability of the terminal device.
4. The method according to claim 1, wherein
after the sending a currently available first radio capability identifier of a terminal device to a first network node, the method further comprises: receiving a second radio capability identifier sent by the first network node, wherein the second radio capability identifier matches a current radio capability of the terminal device.
5. The storage medium according to claim 4, wherein the receiving a second radio capability identifier sent by the first network node comprises: receiving the second radio capability identifier sent by the first network node in a second message, wherein the second message comprises one of: a registration accept message or a tracking area update (TAU) accept message.
5. The method according to claim 4,
wherein the receiving a second radio capability identifier sent by the first network node comprises: receiving the second radio capability identifier sent by the first network node in a second message, wherein the second message comprises one of: a registration accept message or a tracking area update TAU accept message.
6. The storage medium according to claim 4, wherein the second radio capability identifier is a radio capability identifier acquired by querying a UE capability management function (UCMF) node.
6. The method according to claim 4, wherein the second radio capability identifier is a radio capability identifier acquired by querying a UE capability management function UCMF node.
7. The storage medium according to claim 4, wherein the receiving a second radio capability identifier sent by the first network node comprises: receiving the second radio capability identifier sent by the first network node, in a case that the first radio capability identifier does not match the current radio capability of the terminal device.
7. The method according to claim 4,
wherein the receiving a second radio capability identifier sent by the first network node comprises: receiving the second radio capability identifier sent by the first network node, in a case that the first radio capability identifier does not match the current radio capability of the terminal device.
8. A first network node, wherein the first network node supports RACS, the first network node comprises a processor and a memory storing instructions, the instructions, when executed by the processor, cause the first network node to implement:
sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS, wherein the third radio capability identifier matches a current radio capability of the terminal device; wherein the instructions, when executed by the processor, cause the first network node to further implement:
receiving a fourth radio capability identifier sent by the terminal device; and the sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS comprises:
sending the third radio capability identifier to the terminal device, if the fourth radio capability identifier does not match the current radio capability of the terminal device, in a case that the terminal device supports RAGS and the second network node does not support RACS.
8. A method for transmitting a radio capability identifier, applicable to a network node, wherein the network node is a first network node, and the first network node supports RACS, the method comprising:
sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS, wherein the third radio capability identifier matches a current radio capability of the terminal device; wherein the method further comprises:
receiving a fourth radio capability identifier sent by the terminal device; and the sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS includes:
sending the third radio capability identifier to the terminal device, if the fourth radio capability identifier does not match the current radio capability of the terminal device, in a case that the terminal device supports RACS and the second network node does not support RACS.
9. The first network node according to claim 8, wherein the sending a third radio capability identifier to a terminal device comprises: sending the third radio capability identifier to the terminal device in a third message, wherein the third message comprises one of: a registration accept message or a tracking area update (TAU) accept message.
9. The method according to claim 8, wherein the sending a third radio capability identifier to a terminal device comprises: sending the third radio capability identifier to the terminal device in a third message, wherein the third message comprises one of: a registration accept message or a tracking area update TAU accept message.
10. The first network node according to claim 8, wherein the third radio capability identifier is a radio capability identifier acquired by querying a UE capability management function (UCMF) node.
10. The method according to claim 8, wherein the third radio capability identifier is a radio capability identifier acquired by querying a UE capability management function UCMF node.
11.The first network node according to claim 8, wherein a condition for determining that the second network node does not support RACS comprises at least one of the following: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node; or the first network node determines, based on network configuration information, that the second network node does not support RACS.
11. The method according to claim 8,
wherein a condition for determining that the second network node does not support RACS comprises at least one of the following: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node; or the first network node determines, based on network configuration information, that the second network node does not support RACS.
12. The first network node according to claim 11,
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and the first network node comprises a mobility management entity (MME).
14. The method according to claim 8, wherein a condition for determining that the second network node does not support RACS comprises: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node;
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and wherein the network node comprises a Mobility Management Entity (MME).
13. The first network node according to claim 8, wherein the receiving a fourth radio capability identifier sent by the terminal device comprises: receiving the fourth radio capability identifier sent by the terminal device in a fourth information, wherein the fourth information comprises one of: a registration request message or a security mode complete message.
12. The method according to claim 8, wherein the receiving a fourth radio capability identifier sent by the terminal device comprises: receiving the fourth radio capability identifier sent by the terminal device in a fourth information, wherein the fourth information comprises one of: a registration request message or a security mode complete message.
14. The first network node according to claim 8, wherein the instructions, when executed by the processor, cause the first network node to further implement: before receiving the fourth radio capability identifier sent by the terminal device, sending a security mode command carrying a UE radio capability identifier request information element to the terminal device.
13. The method according to claim 8, wherein
before the receiving a fourth radio capability identifier sent by the terminal device, the method further comprises: sending a security mode command carrying a UE radio capability identifier request information element to the terminal device.
15. A non-transitory computer-readable storage medium, storing instructions, wherein the instructions, when executed by a processor of a first network node, cause the first network node to implement:
sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS,
wherein the third radio capability identifier matches a current radio capability of the terminal device; wherein the instructions, when executed by the processor, cause the first network node to further implement:
receiving a fourth radio capability identifier sent by the terminal device; and the sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS comprises:
sending the third radio capability identifier to the terminal device, if the fourth radio capability identifier does not match the current radio capability of the terminal device, in a case that the terminal device supports RACS and the second network node does not support RACS.
8. A method for transmitting a radio capability identifier, applicable to a network node, wherein the network node is a first network node, and the first network node supports RACS, the method comprising:
sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS,
wherein the third radio capability identifier matches a current radio capability of the terminal device; wherein the method further comprises:
receiving a fourth radio capability identifier sent by the terminal device; and
the sending a third radio capability identifier to a terminal device in a case that the terminal device supports RACS and a second network node does not support RACS includes:
sending the third radio capability identifier to the terminal device, if the fourth radio capability identifier does not match the current radio capability of the terminal device, in a case that the terminal device supports RACS and the second network node does not support RACS.
16. The storage medium according to claim 15, wherein the sending a third radio capability identifier to a terminal device comprises: sending the third radio capability identifier to the terminal device in a third message, wherein the third message comprises one of: a registration accept message or a tracking area update (TAU) accept message.
9. The method according to claim 8, wherein the sending a third radio capability identifier to a terminal device comprises: sending the third radio capability identifier to the terminal device in a third message, wherein the third message comprises one of: a registration accept message or a tracking area update TAU accept message.
17. The storage medium according to claim 15, wherein the third radio capability identifier is a radio capability identifier acquired by querying a UE capability management function (UCMF) node.
10.The method according to claim 8, wherein the third radio capability identifier is a radio capability identifier acquired by querying a UE capability management function UCMF node.
18. The storage medium according to claim 15, wherein a condition for determining that the second network node does not support RACS comprises at least one of the following: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node; or the first network node determines, based on network configuration information, that the second network node does not support RACS;
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and the first network node comprises a mobility management entity (MME).
11. The method according to claim 8, wherein a condition for determining that the second network node does not support RACS comprises at least one of the following: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node; or the first network node determines, based on network configuration information, that the second network node does not support RACS.
14. The method according to claim 8, wherein a condition for determining that the second network node does not support RACS comprises: a radio capability identifier of the terminal device is not contained in a context, wherein the context is a context of the terminal device acquired from the second network node;
wherein the first network node is a network node after the terminal moves and the second network node is a network node before the terminal moves; and wherein the network node comprises a Mobility Management Entity (MME).
19. The storage medium according to claim 15, wherein the receiving a fourth radio
capability identifier sent by the terminal device comprises:
receiving the fourth radio capability identifier sent by the terminal device in a fourth information,
wherein the fourth information comprises one of: a registration request message or a security mode complete message.
12. The method according to claim 8, wherein the receiving a fourth radio capability identifier sent by the terminal device comprises:
receiving the fourth radio capability identifier sent by the terminal device in a fourth information, wherein the fourth information comprises one of: a registration request message or a security mode complete message.
20. The storage medium according to claim 15, wherein the instructions, when executed by the processor, cause the first network node to further implement: before receiving the fourth radio capability identifier sent by the terminal device, sending a security mode command carrying a UE radio capability identifier request information element to the terminal device.
13. The method according to claim 8,
wherein
before the receiving a fourth radio capability identifier sent by the terminal device, the method further comprises: sending a security mode command carrying a UE radio capability identifier request information element to the terminal device.
Prior Art of Record
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
(a) KE (US 2025/0016583) – Network-side network element for obtaining first information, wherein the first information comprises indication of whether a terminal supports capability signaling optimization.
(b)HORN et al. (US 2019/0313239) – Optimization of user equipment radio capability signaling.
(c)TIWARI et al. (US 2022/0330120)- Method and apparatus for providing UE radio capabilities in handover procedure.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MARISOL FIGUEROA whose telephone number is (571)272-7840. The examiner can normally be reached Mon-Thurs 8:00am-4:30pm.
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, Jinsong Hu can be reached at 571-272-3965. 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.
/MARISOL FIGUEROA/
Primary Examiner
Art Unit 2643
Prosecution Insights