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 .
Response to Amendment
Applicant amendment filed on 10/23/2024. Canceled claims 1-3 and added claims 4-5 which are pending.
Priority
Applicant cannot rely upon the certified copy of the foreign priority application to overcome this rejection because a translation of said application has not been made of record in accordance with 37 CFR 1.55. When an English language translation of a non-English language foreign application is required, the translation must be that of the certified copy (of the foreign application as filed) submitted together with a statement that the translation of the certified copy is accurate. See MPEP §§ 215 and 216.
Drawings
The drawings are objected to under 37 CFR 1.83(a). The drawings must show every feature of the invention specified in the claims. Therefore, “the UE supports location-related information associated with Single Network Slice Selection Assistance Information (S-NSSAI), the configured NSSAI in association with the location-related information associated with the S-NSSAI and a Public land mobile network (PLMN), the S-NSSAI includes information of multiple cells of one or more Tracking Area (TA) where one or more S-NSSAI(s) is available, and transmit an S-NSSAI, based on the location-related information associated with the S-NSSAI” must be shown or the feature(s) canceled from the claim(s). No new matter should be entered.
Corrected drawing sheets in compliance with 37 CFR 1.121(d) are required in reply to the Office action to avoid abandonment of the application. Any amended replacement drawing sheet should include all of the figures appearing on the immediate prior version of the sheet, even if only one figure is being amended. The figure or figure number of an amended drawing should not be labeled as “amended.” If a drawing figure is to be canceled, the appropriate figure must be removed from the replacement sheet, and where necessary, the remaining figures must be renumbered and appropriate changes made to the brief description of the several views of the drawings for consistency. Additional replacement sheets may be necessary to show the renumbering of the remaining figures. Each drawing sheet submitted after the filing date of an application must be labeled in the top margin as either “Replacement Sheet” or “New Sheet” pursuant to 37 CFR 1.121(d). If the changes are not accepted by the examiner, the applicant will be notified and informed of any required corrective action in the next Office action. The objection to the drawings will not be held in abeyance.
Specification
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
The following title is suggested:
The method and apparatus for transmission and/or reception for information indicates a function of storing condition information associated with Single Network Slice Selection Assistance Information (S-NSSAI).
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)(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.
(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) 4-5 are is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Qiao (US 20220386401 A1, filing date 5/27/2022, us-provisional-application US 63194680 05/28/2021 and us-provisional-application US 63195481 06/01/2021).
With respect to claims 4-5, Qiao teaches / A communication control method performed by a User Equipment (UE) (See e.g. [0347]- The wireless device may comprise one or more processors; and memory storing instructions .. to perform the described method) / A User Equipment (UE) (See e.g. Wireless Device as depicted in Figs. 1-1B, 13A, 15-20- & 23-28) comprising: transmission and reception circuitry (See e.g. [0177]-transceivers , radio unit, [0178]-The wireless device may send/transmit uplink data to and/or receive downlink data from the base station) ; controlling circuitry (See e.g. Prosecting system Fig. 13A, [0177]-all processing in the wireless device may be performed by the processing system); and storage circuitry (See e.g. Memory of Fig. 13A, [0177]- The dedicated memory may comprise instructions that may be processed and/or executed to carry out one or more respective functionalities of the transmission processing system), wherein the transmission and reception circuitry is configured to: transmit, to a core network (See e.g. Wireless Device 101 and 151 are communicating with the Core Network as depicted in Figs. 1-1B, [0187]- FIG. 13A. Any of the deployments (e.g., each deployment) may comprise a processing system for performing one or more functions and/or activities, memory for storing data and/or instructions, and/or an interface system for communicating with other network elements (e.g., other core network deployments), a registration request message (See e.g. [0063]-The wireless device may register with the network and [0064]) including information indicating that the UE supports location-related information associated (See e.g. [0064]-receive, from the wireless device, NAS messages. relate to communications between the wireless device and the core network. NAS messages may facilitate wireless device registration and mobility management, for example, by authenticating, identifying, configuring, and/or managing a connection of the wireless device. NAS messages may support session management procedures for maintaining user plane connectivity and quality of service (QoS) of a session between the wireless device the core network) with Single Network Slice Selection Assistance Information (S-NSSAI); and receive, from the core network (See e.g. [0070] The AUSF may support mutual authentication of the wireless device by the core network and authentication of the core network by the wireless device 301. [0071] The NSSF may select/determine one or more network slices to be used by the wireless device 301. The NSSF may select a slice based on slice selection information. For example, the NSSF may receive single network slice selection assistance information (S-NSSAI) and map the S-NSSAI to a network slice instance identifier (NSI).), a registration accept message (See e.g. [0134] The wireless device may transition to the RM registered state, for example, if the registration is accepted (e.g., via a registration accept procedure )) including a configured Network Slice Selection Assistance Information (NSSAI) (See e.g. [0142]- the wireless device may send/transmit a registration request to an AN . the wireless device may have moved from a coverage area of a previous AMF into a coverage area of a new AMF. The registration request may be/comprise a NAS message. The registration request may comprise a wireless device identifier. The AN 1 may determine/select an AMF for registration of the wireless device. The NAS registration request may comprise a network slice identifier) and location-related information associated with an S-NSSAI (See e.g. [0203]-S-NSSAI, [0237]- tracking area identity (TAI) (if available), security parameters, requested NSSAI, mapping of requested NSSAI, a core network capability of a wireless device), the controlling circuitry is configured to store (See e.g. Prosecting system Fig. 13A, [0177]-all processing in the wireless device may be performed by the processing system; (See e.g. Memory of Fig. 13A, [0177]), in the storage circuitry (See e.g. [0347]-The wireless device may comprise one or more processors; and memory storing instructions that, when executed by one or more processors, cause the wireless device to perform the described method, additional operations and/or include the additional elements. A system may comprise the wireless device configured to perform the described method, …. a device associated with a visited network entity (e.g., a base station, etc.) configured to send the indication), the configured NSSAI in association with the location-related information associated with the S-NSSAI and a Public land mobile network (PLMN) ( See e.g. [0203]-a parameter indicating an NSSAI list (e.g., s-NSSAI-List (e.g. list of network slice identifiers)), a parameter indicating a dedicated NAS message (e.g., dedicatedNAS-Message), a parameter indicating a TMSI, and/or the like. The parameter indicating a registered CPF (e.g., registeredCPF) may comprise a PLMN identity and/or a CPF identifier.) , the location-related information associated with the S-NSSAI includes information of multiple cells of one or more Tracking Area (TA) where one or more S-NSSAI (s) is available (See e.g. [0245] The one or more messages may comprise WD location information indicate a (geographical) location of the wireless device. The WD location information may comprise at least one of: a Cell Global Identification (CGI), a Service Area Identity (SAD, a Routing Area Identification (RAI), a Tracking Area Identity (TAI), a EUTRAN CGI (ECGI), a eNodeB ID, a gNodeB ID, and/or the like.) the controlling circuitry is configured to determine to transmit an S-NSSAI (See e.g. [260]- The wireless device may send/transmit a message. The message may comprise at least one of: a WD identity, a device identifier of the wireless device 2410, WD location information, VPLMN 1 identifier, an S-NSSAI 1 associated with the VPLMN 1, and/or a multiple VPLMN multiple network slice indication.), based on the location-related information associated with the S-NSSAI (See e.g. [0242] An HPLMN may determine configuration information for a wireless device, for example, in at least some wireless communications. The configuration information may indicate the wireless device to simultaneously access a plurality of different network slices via a plurality of VPLMNs. One or more wireless devices (e.g., a visiting wireless device, a roaming wireless device, etc.) may be capable of simultaneous access to a plurality of VPLMNs. One or more network nodes (e.g., a visited base station, a visited AMF, the VPLMNs, etc.) may not be in a status to allow simultaneous access to the plurality of VPLMNs. The HPLMN may not know/detect the status of the one or more network nodes (e.g., e.g., a visited base station, a visited AMF, the VPLMNs, etc.) with respect to multiple access, which may cause a failure of the wireless device in accessing the VPLMNs simultaneously. One or more wireless devices may be capable of providing information about/for available VPLMNs and/or wireless device location information to one or more network nodes (e.g., a visited base station, a visited AMF, the VPLMNs, the HPLMN, etc.). The one or more network nodes (e.g., a visited base station, a visited AMF, the VPLMNs, the HPLMN, etc.) may determine, based on the available VPLMNs and/or the wireless device location information, allowed VPLMNs.)
Claim(s) 4-5 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Lee (US 20220078877 A1, CON of US application 16521033 filed on 07/24/2019).
With respect to claims 4-5, Lee teaches / A communication control method performed by a User Equipment (UE) (See e.g. [0011]-a method of an electronic device) / A User Equipment (UE) (See e.g. Wireless Device as depicted in Figs. 1-2) comprising: transmission and reception circuitry (See e.g. [0055], communication module 190 of Fig. 1; [0071]- communication module 192 of Fig. 2); controlling circuitry (See e.g. [0055]- the electronic device 101 may include a processor 120, memory 130) and storage circuitry (See e.g. [0058]- Memory 130 of Figs. 1-2, The memory 130 may store various data used by at least one component (e.g., the processor )), wherein the transmission and reception circuitry is configured to: transmit, to a core network (See e.g. [0087]- The user data may mean user data other than the control message transmitted and received between the electronic device 101 and a core network 330 (e.g., the EPC 342). & Figs. 5A-5B), a registration request message (See e.g. [[0202] Referring to FIG. 12, in step 1205 of a network environment 1200, the electronic device 101 transmits a registration request message to the first base station 511. The registration request message may include information (e.g., the requested NSSAI) about the network slice instance requested by the electronic device 101.) including information indicating that the UE supports location-related information associated (See e.g. [[0206] In step 1220, the 5G core network 522 determines the allowed NSSAI and at least one rejected S-NSSAI, based at least on the requested NSSAI included in the registration request message, the information (e.g., subscriber information) of the electronic device 101 stored in the 5G core network 522, or the location information (e.g., TA information) of the electronic device 101. The rejected S-NSSAI may indicate a network slice instance that is not allowed on the electronic device 101.) with Single Network Slice Selection Assistance Information (S-NSSAI); and receive, from the core network (See e.g. [0206] In step 1220, the 5G core network 522 determines the allowed NSSAI and at least one rejected S-NSSAI, based at least on the requested NSSAI included in the registration request message, the information (e.g., subscriber information) of the electronic device 101 stored in the 5G core network 522, or the location information (e.g., TA information) of the electronic device 101. The rejected S-NSSAI may indicate a network slice instance that is not allowed on the electronic device 101.), a registration accept message (See e.g. [0207] In step 1225, the 5G core network 522 may transmit a registration accept message including the allowed NSSAI and the at least one rejected S-NSSAI, toward the electronic device 101)) including a configured Network Slice Selection Assistance Information (NSSAI) (See e.g. [0366] ….configured to receive the network capability information through system information broadcast from the base station.) and location-related information associated with an S-NSSAI (See e.g. [0206] In step 1220, the 5G core network 522 determines the allowed NSSAI and at least one rejected S-NSSAI, based at least on the requested NSSAI included in the registration request message, the information (e.g., subscriber information) of the electronic device 101 stored in the 5G core network 522, or the location information (e.g., TA information) of the electronic device 101. The rejected S-NSSAI may indicate a network slice instance that is not allowed on the electronic device 101.), the controlling circuitry is configured to store (See e.g. Prosecting system Fig. 13A, [0177]-all processing in the wireless device may be performed by the processing system; (See e.g. Memory of Fig. 13A, [0177]), in the storage circuitry (See e.g. [0347]-The wireless device may comprise one or more processors; and memory storing instructions that, when executed by one or more processors, cause the wireless device to perform the described method, additional operations and/or include the additional elements. A system may comprise the wireless device configured to perform the described method, …. a device associated with a visited network entity (e.g., a base station, etc.) configured to send the indication), the configured NSSAI in association with the location-related information associated with the S-NSSAI (See e.g. [0198] Referring to FIG. 11, in step 1105 of a method 1100, the electronic device 101 receives network slice information from a first base station 511. The network slice information may be information used to select a network slice instance. The network slice information may mean NSSAI. The NSSAI may include pieces of single-NSSAI (S-NSSAI). For example, NSSAI or S-NSSAI may include a slice/service type (SST) and slice differentiator (SD). The SST may indicate a network service type, and the SD may indicate information associated with the performance of a network slice instance.) and a Public land mobile network (PLMN) ( See e.g. [0203]- The electronic device 101 may generate the requested NSSAI based on at least one of the configured NSSAI or the allowed NSSAI. The configured NSSAI may mean the NSSAI provisioned from an electronic device 101 applicable to one or more PLMNs. The configured NSSAI may be designated by an operator. The allowed NSSAI may mean the NSSAI provided by a serving PLMN. For example, in the case of a registration procedure, the allowed NSSAI may mean NSSAI capable of being used in the registered PLMN by the electronic device 101. ) , the location-related information associated with the S-NSSAI includes information of multiple cells of one or more Tracking Area (TA) where one or more S-NSSAI (s) is available (See e.g. [0250] The information about a neighboring cell may further include network slice information of the neighboring cell. For example, the network slice information of the information about a neighboring cell may indicate a service, which the neighboring cell is capable of providing, from among eMBB, URLLC, and mMTC services. The network slice information may indicate the service defined by an operator in addition to the network slice defined by the 3GPP standard. The network slice information of the neighboring cell may be composed of a bit map. The bit map may comply with the values defined in Table 2 below. & [0210] When the rejected S-NSSAI indicates a network slice instance providing the URLLC service, the electronic device 101 may display the fact that eMBB is available. ) the controlling circuitry is configured to determine to transmit an S-NSSAI (See e.g. [0203] The electronic device 101 may generate the requested NSSAI based on at least one of the configured NSSAI or the allowed NSSAI. The configured NSSAI may mean the NSSAI provisioned from an electronic device 101 applicable to one or more PLMNs. The configured NSSAI may be designated by an operator. The allowed NSSAI may mean the NSSAI provided by a serving PLMN. For example, in the case of a registration procedure, the allowed NSSAI may mean NSSAI capable of being used in the registered PLMN by the electronic device 101. [0204] In step 1210, the first base station 511 selects an access & mobility management function (AMF) included in the 5G core network 522, based at least on the requested NSSAI. For example, the AMF may manage information associated with the access authorization for the 5G core network 522 of the electronic device 101 and the mobility of the electronic device 101.), based on the location-related information associated with the S-NSSAI (See e.g. [0206] In step 1220, the 5G core network 522 determines the allowed NSSAI and at least one rejected S-NSSAI, based at least on the requested NSSAI included in the registration request message, the information (e.g., subscriber information) of the electronic device 101 stored in the 5G core network 522, or the location information (e.g., TA information) of the electronic device 101. The rejected S-NSSAI may indicate a network slice instance that is not allowed on the electronic device 101. & [0332] Referring to FIG. 29, in step 2905, the electronic device 101 detects a second event associated with the mobility of the electronic device 101. For example, the second event may be at least one of handover, cell reselection, or tracking area update (TAU). & Figs 8 -15)
Claim(s) 4-5 are is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Starsinic (WO 2023146811 A1, publication date 8/3/2023, which this application claims the benefit of U.S. Provisional Patent Application No. 63/303,574, filed 1/27/2023).
With respect to claims 4-5, Starsinic teaches / A communication control method performed by a User Equipment (UE) (See e.g. [0003]- a wireless transmit/receive unit (WTRU) be configured to perform (e.g., implement a method)) / A User Equipment (UE) (See e.g. Wireless Device as depicted in Figs. 1-3) comprising: transmission and reception circuitry (See e.g. [0047]a wireless transmit/receive unit (WTRU) configured to transmit signals to, or receive signals from and 120-122 of Fig. 1B)); controlling circuitry (See e.g. [0056]- FIG. IB depicts the processor 118 and the transceiver 120) and storage circuitry (See e.g. [0050]- the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.), wherein the transmission and reception circuitry is configured to: transmit, to a core network (See e.g. [0003]- a wireless transmit/receive unit (WTRU) be configured to perform (e.g., implement a method) acts which include sending (e.g., to a network entity / Core Network 106 and 115 of Figs. 1C and 1B respectively)), a registration request message (See e.g. [0003]-a first registration request message associated with a first tracking area (TA) of a registration area (RA) including information indicating that the UE supports location-related information associated (See e.g. [0105] In certain representative embodiments, a WTRU may receive information from a network, such as the network, and the WTRU may perform procedures to determine slice availability in a TA using such received information. When the WTRU registers with the network, the WTRU may provide an (explicit or implicit) indication to the network that the WTRU may understand Slice-Specific Service Area (SSSA) information (e.g., perform procedures using the SSSA information). An AMF 182 may use the information from the WTRU in determining how to construct a RA, such as whether or not to include TAs in the RA where a rejected slice is available. The network may send information to the WTRU 102 so that it can be determined whether or not a slice is available in a TA.) with Single Network Slice Selection Assistance Information (S-NSSAI); and receive, from the core network (See e.g. [0107] In certain representative embodiments, a change in slice availability may trigger a WTRU 102 and/or a network, such as network 104/113, to take an action. As an example, a WTRU 102 may send a (e.g., new) Registration Request to the network and add a rejected S-NSSAI to the requested NSSAI (e.g., because the associated slice is now available). As an example, a WTRU 102 may send a (e.g., new) Registration Request to the network and may remove an S-NSSAI from its Requested NSSAI (i.e. because the associated slice is now unavailable). For example, a WTRU 102 may receive a NAS Message from an AMF 182. The NAS Message may be a UE Configuration Update Command that, for example, includes information indicating to add a Rejected S-NSSAI to the Allowed NSSAI (e.g.. because it is now available). As another example, the NAS Message may be a NAS notification that includes information indicating a previously Rejected S-NSSAI is now accessible. As another example, the NAS Message may be a UE Configuration Update Command that removes an S-NSSAI from its Allowed NSSAI (e.g., because it is now unavailable).), a registration accept message including a configured Network Slice Selection Assistance Information (NSSAI) (See e.g. a Configured NSSAI may be or include information indicating a list, or collection, of slices that a WTRU 102 may access. Any WTRU 102 may receive a Configured NSSAI in a message, such as a Registration Accept and/or WTRU Configuration Update message.) and location-related information associated with an S-NSSAI (See e.g. 0110] In certain representative embodiments, a Registration Area (RA) may refer to a set of Tracking Areas (TAs). A RA may be defined by a Tracking Area Identifier (TAI) List (e.g., a list of TAs). When a WTRU 102 registers with the network (e.g., sends a registration request to an AMF 182), an AMF 182 may allocate a registration area (e.g., a set of tracking areas in a TAI List) to the WTRU 102. [0111] …, a Configured NSSAI may be or include information indicating a list, or collection, of slices that a WTRU 102 may access. Any WTRU 102 may receive a Configured NSSAI in a message, such as a Registration Accept and/or WTRU Configuration Update message) the controlling circuitry is configured to store in the storage circuitry (See e.g. [0050]- the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.), the configured NSSAI in association with the location-related information associated with the S-NSSAI (See e.g. a WTRU 102 may receive SSSA information in a Registration Accept Message. For example, the SSSA information may be stored in a NAS-MM information element and be encoded such that it includes one or more slice identifiers (e.g., S- NSSAIs) and a set of TAs that belong to the RA. The set of TAs may be TAs in the Registration Area where the slices (e.g., S-NSSAIs) are available to the WTRU 102. For example, on condition that the WTRU 102 receives no SSSA information for a slice that is in the WTRU’s configured NSSAI, the WTRU 102 may interpret the missing SSSA information as an indication that the slice is available to the WTRU 102 in all tracking areas of the RA. As another example, the set of TAs may be the tracking areas in the RA where the slices (e.g., S-NSSAIs) are not available to the WTRU 102 (e.g., the slice is available in all other tracking areas of the Registration Area).) and a Public land mobile network (PLMN) ( See e.g. [0137]- 5 Network (PLMN), [0032] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) a radio access network (RAN), a core network (CN), a public switched telephone network (PSTN), the Internet, and other networks) , the location-related information associated with the S-NSSAI includes information of multiple cells of one or more Tracking Area (TA) where one or more S-NSSAI (s) is available (See e.g. [0124] In certain representative embodiments, a NG-RAN cell may broadcast slice group information indicating what slices the cell supports. For example, slice group identifiers may indicate what slices the cell supports. For example, an NG-RAN cell may use RRC messaging to provide slice group information to a WTRU 102 as a way of indicating what slices the cell supports. As another example, the network may use NAS signaling to provide information to WTRU 102 so that the WTRU 102 can determine what slices (e.g., S-NSSAI’s) are associated with a Slice Group Identifier.
[0125] PMF Protocol [0126] In certain representative embodiments, the PMF protocol may be used by the WTRU 102 and a PMF to exchange messages that relate to Round Trip Time (RTT) measurements, Packet Loss Rate (PLR) measurements, Access availability/unavailability information, and/or WTRU- assistance data. Access availability/unavailability information may refer to a report that is sent from the WTRU 102 to the PMF to indicate whether or not cellular and/or non-3GPP access is available for the WTRU 102. [0127] As described in 3GPP TS 23.501 Ver. 17.3.0, the availability of a Network Slice is configured in the network per TA. Network functions, such as the AMF 182, are configured to know, on a per-TA basis, whether a slice (e.g., S-NSSAI) is accessible. The AMF 182 is informed by 5G-AN nodes of the S-NSSAIs supported per TA when the 5G-AN nodes establish or update the N2 connection with the AMF 182.) the controlling circuitry is configured to determine to transmit an S-NSSAI based on the location-related information associated with the S-NSSAI (See e.g. [0141] In certain representative embodiments, a WTRU 102 may be configured with a Configured NSSAI. The Configured NSSAI may include a set, or list, of slices (e.g., S-NSSAIs) that the WTRU 102 may attempt to register to. When the WTRU 102 sends a Registration Request to an AMF, the WTRU 102 may provide a Requested NSSAI information element which lists the slices (e.g., S-NSSAIs) that the WTRU 102 wants to register to. One or more of the slices (e.g., S-NSSAIs) in the Requested NSSAI may not be available to the WTRU 102 in the WTRU’s current TA.).
Claim(s) 4-5 are is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Ianev (US 20220264505 A1, PCT filing date 3/18/2021).
With respect to claims 4-5, Starsinic teaches / A communication control method performed by a User Equipment (UE) (See e.g. [0023 apparatuses, methods, and programs that contribute to allowing a UE to easily utilize a network slice that is supported only in sparsely) / A User Equipment (UE) (See e.g. [0155] FIG. 21 is a block diagram showing a configuration example of the UE 4.) comprising: transmission and reception circuitry (See e.g. [0155] The RF transceiver 2101 may include a plurality of transceivers)); controlling circuitry (See e.g. 0161] In some implementations, as represented by a dashed line (2105) in FIG. 21, the baseband processor 2103 and the application processor 2104 may be integrated on a single chip.) and storage circuitry (See e.g. [0162] The memory 2106), wherein the transmission and reception circuitry is configured to: transmit, to a core network (See e.g. [0186] send a registration request message to an Access and Mobility management Function (AMF) (Which is part of the Core Network-[0017]) via a first access network (AN) node), a registration request message including information indicating that the UE supports location-related information associated (See e.g. [0185] at least one processor coupled to the at least one memory and configured to: [0186] send a registration request message to an Access and Mobility management Function (AMF) via a first access network (AN) node; and [0187] receive a registration accept message from the AMF via the first AN node, the registration accept message indicating a registration area of the UE and a first list of at least one conditionally allowed network slice identifier, wherein [0188] the registration area is a list of at least one tracking area. Step 501 of Fig. 5) with Single Network Slice Selection Assistance Information (S-NSSAI) (See e.g. Registration request (requested NSSAI) or S-NSSAIs of Fig 5); and receive, from the core network, a registration accept message including a configured Network Slice Selection Assistance Information (NSSAI) (See e.g. Registration Accept 503 of Fig. 5) and location-related information associated with an S-NSSAI (See e.g. [0081] FIG. 5 shows another example of the registration procedure of the UE 4. Steps 501 and 502 are similar to steps 401 and 402 in FIG. 4. FIG. 5 relates to the case described with reference to FIG. 3A. Accordingly, in step 503, the AMF 3 includes both S-NSSAI-1 and S-NSSAI-2 into the Conditional NSSAI. S-NSSAI-1 within the Conditional NSSAI may be associated with a subset of TAIs contained in the registration area of the UE 4. Similarly, S-NSSAI-2 within the Conditional NSSAI may be associated with a subset of TAIs contained in the registration area of the UE 4. According to the example of FIG. 3A, the TAI subset associated with S-NSSAI-1 contains TAI-1, while the TAI subset associated with S-NSSAI-2 contains TAI-2.) the controlling circuitry is configured to store in the storage circuitry (See e.g. 2105 and 2106 of Fig. 21), the configured NSSAI in association with the location-related information associated with the S-NSSAI (See e.g. [0007] A Requested NSSAI is signaled by a UE to a network in, for example, a registration procedure, allowing the network to determine a serving AMF, at least one network slice and at least one NSIs, for this UE. [0008] An allowed NSSAI is provided to a UE by a Serving PLMN and indicates one or more S-NSSAIs that the UE can use in the current Registration Area of the Serving PLMN. The Allowed NSSAI is determined by an AMF of the Serving PLMN, for example, during a registration procedure. Accordingly, the Allowed NSSAI is signaled to the UE by the network (i.e., AMF) and stored in memories (e.g., non-volatile memories) of both the AMF and the UE. [0009] A Rejected NSSAI includes one or more S-NSSAIs rejected by the current PLMN. The Rejected NSSAI may be referred to as rejected S-NSSAIs. A S-NSSAI is rejected throughout the current PLMN or rejected in the current registration area. If an AMF rejects any of one or more S-NSSAIs included in the Requested NSSAI, for example, in a registration procedure of a UE, it includes them in the Rejected NSSAI. The Rejected NSSAI is signaled to the UE by the network (i.e., AMF) and stored in memories of both the AMF and the UE.) , the location-related information associated with the S-NSSAI includes information of multiple cells of one or more Tracking Area (TA) where one or more S-NSSAI (s) is available (See e.g. [0022] These issues are related to a restriction on the registration area of the UE. As mentioned above, according to the current 3GPP specifications, all the S-NSSAIs included in the Allowed NSSAI must be available in all the TAs that make up the registration area. Relaxing this restriction may allow the UE to easily utilize a network slice that are only supported in sparsely (or patchily) placed local cells) the controlling circuitry is configured to determine to transmit an S-NSSAI based on the location-related information associated with the S-NSSAI (See e.g. [0025] In an aspect, a UE includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to send a registration request message to an AMF via a first access network (AN) node. The at least one processor is further configured to receive from the AMF via the first AN node a registration accept message indicating a registration area of the UE and a first list of at least one conditionally allowed network slice identifier. The registration area is a list of at least one tracking area. Each conditionally allowed network slice identifier is not available in every part of the registration area, but is available in at least one particular cell or at least one particular tracking area included in the registration area.).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KAMRAN AFSHAR whose telephone number is 571-272-7796. The examiner can normally be reached Monday-Thursday: 9:00AM-4:00PM ET.
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.
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.
/KAMRAN AFSHAR/Supervisory Patent Examiner, Art Unit 2125
Prosecution Insights