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 .
Priority
Acknowledgment is made of applicant’s claim for foreign priority under 35 U.S.C. 119 (a)-(d). The certified copy has been filed in parent Application No. KR-10-2022-0054485, filed on 2nd May 2022.
---------- ---------- ----------
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 1st November 2024 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
========== ========== ==========
Claim Rejections - 35 USC § 102
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1 – 7, 8 – 14 and 15 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Lou et al (US 2019/0349774 A1).
Claim 15 (similarly Claim 1). Lou shows a device supporting network slicing of a user equipment (UE) (figs. 1, 5 and 7: terminal device), the UE comprising: a transceiver (fig. 7: sending/receiving unit); and a processor (the terminal device implicitly has a processor) configured to: transmit a first non-access stratum (NAS) message ([0242]: a terminal device sends a first RRC message to a RAN node; [0247]: the first RRC message may further carry a NAS message that is used to initiate a network slice selection or PDU session establishment process) to a network entity: receive, from the network entity, a second NAS message including slicing-related information related to a slice priority and an access stratum (AS) slice group ([0243]: the RAN node sends a second RRC message to the terminal device; [0251]: the second RRC message may further include redirection cell information which is used to indicate information about a cell that is selected by the RAN node for the terminal device and that is to be re-accessed by the terminal device; [0252]: the second RRC message may further include information such as an allowed-to-be-accessed or prohibited-from-being-accessed cell identity, a tracking area identifier or code, a paging area identifier, or a PLMN identifier of at least one network slice in the first network slice set); and select a radio access network (RAN) slice in an AS layer using the slicing-related information ([0255]: the second RRC message may further include redirection carrier information which is used to indicate a carrier frequency to which the terminal device needs to be redirected when the terminal device exits an RRC connection state and re-initiates cell selection, for example, a carrier frequency applicable to a 5G, eLTE, LTE, or a like communications system; [0257]: the terminal device may save at least one piece of the foregoing information included in the second RRC message, and the at least one piece of the foregoing information is used for mobility management of the terminal device in an RRC idle state, for example, cell selection or cell reselection).
Claim 2. Lou shows the method of claim 1, wherein the second NAS message includes any one of a registration accept message ([0112]: the RAN1 node may further send a first network slice management request reply message to the CN1 node, where the first network slice management request reply message may indicate that the RAN1 node accepts or rejects the first network slice management request message of the CN1 node), a configuration command ([0254]: the second RRC message may further include a random access configuration parameter corresponding to the at least one network slice in the first network slice set), or a service request message ([0101]: service information corresponding to the at least one network slice in the first network slice set which is information about bearer-related, session-related, and stream-related establishment, modification, or release).
Claim 3. Lou shows the method of claim 1, wherein the slicing-related information includes at least one of a tracking area code (TAC) ([0126] – [0127]: the network slice identifier corresponding to each network slice in the first network slice set… a network slice identifier, a cell identity, a tracking area identifier or code), a slice group identifier of a slice group mapped to the MAC ([0080]: slice group information which is used to indicate a network slice group that is formed based on a characteristic, for example, all network slices that can be accessed by the terminal device are used as a slice group, or a network slice group is classified according to another standard), or information about a slice group priority mapped to the slice group ([0218]: the CN1 node maps the DCN identifier corresponding to the at least one network slice in the NS Set1-RAN1 to the network slice identifier corresponding to the at least one network slice in the NS Set1-RAN1, selects the CN2 node that is corresponding to the RAN2, and sends the seventh message to the CN2 in wherein the seventh message includes the network slice identifier corresponding to at least one DCN identifier in the NS Set1-RAN1 and the CN2 node determines the second network slice set, namely, the NS Set2-CN2… the CN2 needs to map a network slice identifier to a DCN identifier. Specifically, the CN2 maps the network slice identifier corresponding to the at least one network slice in the second network slice set to a DCN identifier corresponding to the at least one network slice in the second network slice set).
Claim 4. Lou shows the method of claim 1, wherein the slicing-related information includes at least one of network slice selection assistance information (NSSAI) for identifying a network slice ([0075]: network slice identifier), a slice type ([0076]: network slice type information), or a slice differentiator (n/a).
Claim 5. Lou shows the method of claim 1, further comprising, when the received slicing-related information does not match pre-stored slicing-related information, storing an AS slice group and slice priority corresponding to the received slicing-related information as non-allowable slice information ([0034]: allowed-to-be-established service information and/or not-allowed-to-be-established service information that are/is corresponding to the at least one network slice in the second network slice set; [0270]: if the RAN node does not support some or all network slices in the second network slice set, the RAN node may send a third interface message to the CN node… the third interface message may include a network slice identifier corresponding to a network slice that cannot be supported by the RAN2 node).
Claim 6. Lou shows the method of claim 1, further comprising receiving, from the network entity, information indicating whether the network entity supports a function related to the AS slice group and/or slice priority ([0167]: a source-side RAN network element may preferably consider to support a neighboring RAN network element in which the high-priority tracking area is located as a target-side RAN network element; [0217]: a function of mapping a network slice identifier to a DCN identifier at the CN1 node or the CN2 node needs to be implemented).
Claim 7. Lou shows the method of claim 1, further comprising transmitting, to the network entity, information indicating whether the UE supports a function related to the AS slice group and/or slice priority ([0249]: the network slice reselection policy may indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device is allowed to select another network slice for the terminal device in a manner of handover or cell reselection… the identifier of the at least one network slice that can replace the network slice may be sorted based on a priority).
---------- ---------- ----------
Claim 8. Lou shows a method for communication by a network entity (figs. 1, 5 and 7: RAN node) using network slicing (abstract), the method comprising: receiving a first non-access stratum (NAS) message from a user equipment (UE) ([0242]: a terminal device sends a first RRC message to a RAN node; [0247]: the first RRC message may further carry a NAS message that is used to initiate a network slice selection or PDU session establishment process); and transmitting, to the UE, a second non-access stratum (NAS) message including slicing-related information related to a slice priority and an access stratum (AS) slice group ([0243]: the RAN node sends a second RRC message to the terminal device; [0251]: the second RRC message may further include redirection cell information which is used to indicate information about a cell that is selected by the RAN node for the terminal device and that is to be re-accessed by the terminal device; [0252]: the second RRC message may further include information such as an allowed-to-be-accessed or prohibited-from-being-accessed cell identity, a tracking area identifier or code, a paging area identifier, or a PLMN identifier of at least one network slice in the first network slice set), wherein the slicing-related information is used for the UE to select a radio access network (RAN) slice in an AS layer ([0255]: the second RRC message may further include redirection carrier information which is used to indicate a carrier frequency to which the terminal device needs to be redirected when the terminal device exits an RRC connection state and re-initiates cell selection, for example, a carrier frequency applicable to a 5G, eLTE, LTE, or a like communications system; [0257]: the terminal device may save at least one piece of the foregoing information included in the second RRC message, and the at least one piece of the foregoing information is used for mobility management of the terminal device in an RRC idle state, for example, cell selection or cell reselection).
Claim 9. Lou shows the method of claim 8, wherein the second NAS message includes any one of a registration accept message ([0112]: the RAN1 node may further send a first network slice management request reply message to the CN1 node, where the first network slice management request reply message may indicate that the RAN1 node accepts or rejects the first network slice management request message of the CN1 node), a configuration command ([0254]: the second RRC message may further include a random access configuration parameter corresponding to the at least one network slice in the first network slice set), or a service request message ([0101]: service information corresponding to the at least one network slice in the first network slice set which is information about bearer-related, session-related, and stream-related establishment, modification, or release).
Claim 10. Lou shows the method of claim 8, wherein the slicing-related information includes at least one of a tracking area code (TAC) ([0126] – [0127]: the network slice identifier corresponding to each network slice in the first network slice set… a network slice identifier, a cell identity, a tracking area identifier or code), a slice group identifier of a slice group mapped to the MAC ([0080]: slice group information which is used to indicate a network slice group that is formed based on a characteristic, for example, all network slices that can be accessed by the terminal device are used as a slice group, or a network slice group is classified according to another standard), or information about a slice group priority mapped to the slice group ([0218]: the CN1 node maps the DCN identifier corresponding to the at least one network slice in the NS Set1-RAN1 to the network slice identifier corresponding to the at least one network slice in the NS Set1-RAN1, selects the CN2 node that is corresponding to the RAN2, and sends the seventh message to the CN2 in wherein the seventh message includes the network slice identifier corresponding to at least one DCN identifier in the NS Set1-RAN1 and the CN2 node determines the second network slice set, namely, the NS Set2-CN2… the CN2 needs to map a network slice identifier to a DCN identifier. Specifically, the CN2 maps the network slice identifier corresponding to the at least one network slice in the second network slice set to a DCN identifier corresponding to the at least one network slice in the second network slice set).
Claim 11. Lou shows the method of claim 8, wherein the slicing-related information includes at least one of network slice selection assistance information (NSSAI) for identifying a network slice ([0075]: network slice identifier), a slice type ([0076]: network slice type information), or a slice differentiator (n/a).
Claim 12. Lou shows the method of claim 8, further comprising, when the received slicing-related information does not match pre-stored slicing-related information, storing an AS slice group and slice priority corresponding to the received slicing-related information as non-allowable slice information ([0034]: allowed-to-be-established service information and/or not-allowed-to-be-established service information that are/is corresponding to the at least one network slice in the second network slice set; [0270]: if the RAN node does not support some or all network slices in the second network slice set, the RAN node may send a third interface message to the CN node… the third interface message may include a network slice identifier corresponding to a network slice that cannot be supported by the RAN2 node).
Claim 13. Lou shows the method of claim 8, further comprising receiving, from the network entity, information indicating whether the network entity supports a function related to the AS slice group and/or slice priority ([0167]: a source-side RAN network element may preferably consider to support a neighboring RAN network element in which the high-priority tracking area is located as a target-side RAN network element; [0217]: a function of mapping a network slice identifier to a DCN identifier at the CN1 node or the CN2 node needs to be implemented).
Claim 14. Lou shows the method of claim 8, further comprising transmitting, to the network entity, information indicating whether the UE supports a function related to the AS slice group and/or slice priority ([0249]: the network slice reselection policy may indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device is allowed to select another network slice for the terminal device in a manner of handover or cell reselection… the identifier of the at least one network slice that can replace the network slice may be sorted based on a priority).
========== ========== ==========
Conclusion
The prior art made of record is considered pertinent to applicant’s disclosure.
1. Tiwari et al, US 2020/0396788 A1: a User Equipment for handling a closed access group (CAG) related procedure in a wireless communication system, comprising a radio communications circuitry; and a processing circuitry, coupled with the radio communications circuitry, configured to: transmit a radio resource control (RRC) resume request message to a network; receive a RRC resume message from the network in response to a determination that at least one CAG identifier (ID) broadcasted in a CAG cell is included in an allowed CAG list of the UE.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri.
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, Jeffrey Rutkowski can be reached on 571.270.1215. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/XAVIER S WONG/Primary Examiner, Art Unit 2415 27th September 2026
Prosecution Insights