First communication device and first communication device method

Abstract

One aspect of this disclosure includes a method of a first communication device. The method includes receiving a Registration Request message from a user device (UE). The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The method includes transmitting the Requested NSSAI to a second communication device. The method includes receiving an Allowed NSSAI from the second communication device. The Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes transmitting a Registration Accept message to the UE. The Registration Accept message includes a Partially Allowed NSSAI. The Partially Allowed NSSAI includes the S-NSSAI.

Description

Technical Field

[0001] The present disclosure relates to a method of a first communication device, a method of a user equipment (UE), the first communication device, and the UE, etc.

Background Art

[0002] According to 3GPP (registered trademark) SA2 contribution S2-2303160 (Non-Patent Document 2), the 3GPP SA2 group concludes that the AMF selects, for the UE, the Partially Allowed NSSAI and the Rejected S-NSSAI(s) partially in the RA based on the local policy of the AMF.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

[0004] According to the 5GC network slice management mechanism defined in 3GPP TS23.501 (Non-Patent Document 3), the 5GC has a Network Slice Selection Function (NSSF), which is a dedicated functional entity for assigning S-NSSAIs to UEs based on network slices in the NSSAI (Requested NSSAI) requested by the UE, UE subscriber data, UE location, other configuration data in the 5GC, and associated Operation and Maintenance (O&M) systems. Based on this mechanism, the mobile operator configures a network slice-related database in the NSSF.

[0005] On the other hand, Non-Patent Document 2 defines newly introduced network slice-related data, as well as the selection of Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, based on AMF's sole decision based on AMF local policy.

[0006] However, there are several issues with AMF decisions based on AMF local policies. This disclosure includes a mechanism to at least partially address the above issues. [Means for solving the problem]

[0007] The method of the first communication device relating to the first aspect of this disclosure is: A Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) is received from User Equipment (UE). The Requested NSSAI is transmitted to the second communication device. The second communication device receives Allowed NSSAI, which includes Single Network Slice Selection Assistance Information (S-NSSAI), A Registration Accept message including "Partially Allowed NSSAI" is sent to the UE. The Partially Allowed NSSAI includes the S-NSSAI.

[0008] The user equipment (UE) method relating to the second aspect of this disclosure is: A Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) is sent to the first communication device. I received a Registration Accept message that included "Partially Allowed NSSAI". The aforementioned Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), The S-NSSAI in the Partially Allowed NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI includes the S-NSSAI.

[0009] The first communication device relating to the third aspect of this disclosure is A means for receiving a Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) from User Equipment (UE), Means for transmitting the Requested NSSAI to a second communication device, A means for receiving Allowed NSSAI, including Single Network Slice Selection Assistance Information (S-NSSAI), from the second communication device, The system includes means for sending a Registration Accept message, including a Partially Allowed NSSAI, to the UE. The Partially Allowed NSSAI includes the S-NSSAI.

[0010] The user equipment (UE) relating to the fourth aspect of this disclosure is: Means for sending a Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) to a first communication device, It includes means for receiving Registration Accept messages, including Partially Allowed NSSAI, The aforementioned Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), The S-NSSAI in the Partially Allowed NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI includes the S-NSSAI. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a signaling diagram of a first example of the first embodiment. [Figure 2] Figure 2 is a signaling diagram of a second example of the first embodiment. [Figure 3] Figure 3 is a signaling diagram of a third example of the first embodiment. [Figure 4] Figure 4 is a diagram showing the system overview. [Figure 5] Figure 5 is a block diagram showing the UE. [Figure 6] Figure 6 is a block diagram showing the (R)AN node. [Figure 7] Figure 7 is a diagram showing the system overview of the (R)AN node based on the O-RAN architecture. [Figure 8] Figure 8 is a block diagram showing the RU. [Figure 9] Figure 9 is a block diagram showing the DU. [Figure 10] Figure 10 is a block diagram showing the CU. [Figure 11] Figure 11 is a block diagram showing the AMF. [Figure 12] Figure 12 is a block diagram showing the PCF. [Figure 13] Figure 13 is a block diagram showing the NWDAF. [Figure 14] Figure 14 is a block diagram showing the UDM. [Figure 15] Figure 15 is a block diagram showing the NSSF. [Figure 16] Figure 16 is a signaling diagram of the registration of the AMF reallocation procedure.

Embodiments for Carrying Out the Invention

[0012] For the purposes of this document, 3GPP TR21.905 (Non-Patent Document 1), and the abbreviations given below are applicable. If there are the same abbreviations in Non-Patent Document 1, the abbreviations defined in this document shall take precedence over them. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function ARFCN Absolute radio-frequency channel number AS Access Stratum ASN Abstract Syntax Notation ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AuC Authentication Centre AUSF Authentication Server Function AUTN Authentication token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre G-PDU GTP encapsulated user Plane Data Unit GPS Global Positioning System GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed(ローミング) HSS Home Subscriber Server IAB Integrated access and backhaul IPsec Internet Protocol Security IMEI / TAC IMEI Type Allocation Code IMSI International Mobile Subscriber Identity IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out(ローミング) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume ME Mobile Equipment MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MINT Minimization of service interruption MITM Man In the Middle MME Mobility Management Entity MNC Mobile Network Code MOCN Multiple Operator Core Network MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol MT Mobile Termination N3IWF Non-3GPP InterWorking Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access-Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NMEA National Marine Electronics Association NPN Non-Public Network NR New Radio NSAG Network Slice Access Stratum Group NRF Network Repository Function NSAC Network Slice Admission Control NSACF Network Slice Admission Control Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PCO Protocol Configuration Options PCRF Policy and Charging Rules Function PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio)Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control RSN Redundancy Sequence Number RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RVAS Roaming Value Added Service SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SENSE Signal Level Enhanced Network Selection SEPP Security Edge Protection Proxy SGW Serving Gateway SIB System Information Block SINR Signal to Interference plus Noise Ratio SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SOR Steering Of Roaming SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TAU Tracking Area Update TEID Tunnel Endpoint Identifier TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function UPSI UE Policy Section Identifier URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy USIM User Services Identity Module VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited Public Land Mobile Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0013] definition For the purposes of this document, the terms and definitions given in Non-Patent Document 1 and below shall apply. If the same term is defined in 3GPP TR21.905 (Non-Patent Document 1), the terms defined in this document shall take precedence.

[0014] Outline Those skilled in the art will understand that elements in the drawings are shown for simplification and may not necessarily be drawn to scale. Furthermore, with respect to the structure of a device, one or more components of the device may be represented in the drawings by conventional symbols, and the drawings may show only certain details relevant to understanding aspects of this disclosure so as not to obscure the drawings with details that would be readily apparent to those skilled in the art who benefit from the description herein.

[0015] For the purpose of facilitating understanding of the principles of this disclosure, the embodiments shown in the figures will be referenced and specific language will be used to describe them. Nevertheless, it will be understood that this is not intended to limit the scope of this disclosure. Such modifications and further alterations to the exemplary systems, as well as such further applications of the principles of this disclosure, as would ordinarily conceivable to those skilled in the art, should be construed as being within the scope of this disclosure.

[0016] The terms “comprises,” “comprising,” or any other variation thereof are intended to encompass non-exclusive inclusions such that a process or method containing a list of steps may include steps not explicitly enumerated, or other steps specific to such process or method, rather than only those steps. Similarly, one or more devices, entities, subsystems, elements, components, or constituents following “comprises ~ a” do not, without further constraint, exclude the existence of other devices, subsystems, elements, components, constituents, additional devices, additional subsystems, additional elements, additional components, or additional constituents. Throughout this specification, occurrences of the phrases “in one aspect,” “in another aspect,” and similar wording may, but not necessarily, all refer to the same aspect.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art to which this disclosure pertains. The systems, methods, and examples provided herein are illustrative and not intended to limit the scope of this disclosure.

[0018] In the following specification and claims, certain terms may be defined as having the following meanings: The singular forms “a,” “an,” and “the” include plural references unless the context clearly indicates otherwise.

[0019] Where used herein, data is meaningful information and represents values ​​resulting from parameters; therefore, information is related to data and knowledge. Further knowledge means an understanding of abstract or concrete concepts. This exemplary system is simplified for the sake of facilitating the explanation of the subject matter of this disclosure and is not intended to limit the scope of this disclosure. The embodiments disclosed herein can be implemented using other devices, systems, and configurations in addition to, or instead of, the system, and all such embodiments are considered to be within the scope of this disclosure.

[0020] Each embodiment (i.e., the first embodiment, the second embodiment, the third embodiment, the first example of the first embodiment, the second example of the first embodiment, the third example of the first embodiment, the first example of the second embodiment, the second example of the second embodiment, the third example of the second embodiment, and variations of each embodiment), and the elements contained in each of the embodiments described below, can be implemented independently or in combination with any other. These embodiments contain novel features that differ from one another. Thus, these embodiments contribute to achieving different objectives or solving different problems and to obtaining different advantages.

[0021] Any list described in the following aspects includes at least one or more parameters.

[0022] Partially Allowed NSSAI can be expressed as Partially allowed NSSAI, Partially allowed NSSAI, Partially Allowed S-NSSAI, Partially Allowed network slice, Partially Allowed S-NSSAI, etc.

[0023] A partially rejected S-NSSAI within a RA can be expressed as follows: S-NSSAI rejected partially in the RA, S-NSSAIs rejected partially, S-NSSAI rejected partially, Partially rejected NSSAI, partially rejected NSSAI, partially rejected NSSAI, Partially rejected S-NSSAI, Rejected S-NSSAIs partially, Rejected S-NSSAI partially, Partially rejected NSSAI, Partially rejected network slice, etc.

[0024] In this disclosure, network slice may mean S-NSSAI. In this disclosure, S-NSSAI may mean network slice. In this disclosure, S-NSSAI may mean a network slice identified by S-NSSAI. In this disclosure, network slices can be identified by the corresponding S-NSSAI.

[0025] An exemplary object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problems.

[0026] A method of a first communication device according to an exemplary aspect of the present disclosure includes receiving at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes transmitting at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI to a user device (UE).

[0027] A method of a first communication device according to an exemplary embodiment of the present disclosure includes receiving information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). The method includes determining at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI. The method includes transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to a user device (UE).

[0028] A user equipment (UE) method relating to an exemplary aspect of this disclosure includes transmitting information to a communication device indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). The method includes, when transmitting the information, receiving at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI from the communication device.

[0029] A method of a first communication device according to an exemplary embodiment of the present disclosure includes receiving information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). The method includes determining at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI. The method includes transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to the second communication device.

[0030] A first communication device according to an exemplary embodiment of the present disclosure includes at least one memory and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The at least one hardware processor is configured to transmit at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI to a user device (UE).

[0031] A first communication device according to an exemplary embodiment of the present disclosure includes at least one memory and at least one hardware processor coupled to at least one memory. The at least one hardware processor is configured to receive information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to determine at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI. The at least one hardware processor is configured to transmit at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI to a user device (UE).

[0032] A user device (UE) in an exemplary aspect of the present disclosure includes at least one memory and at least one hardware processor coupled to at least one memory. The at least one hardware processor is configured to transmit information to a communication device indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). When transmitting information, the at least one hardware processor is configured to receive at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI from the communication device.

[0033] A first communication device according to an exemplary embodiment of the present disclosure includes at least one memory and at least one hardware processor coupled to at least one memory. The at least one hardware processor is configured to receive information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to determine at least one of the NSSAI and the Partially Rejected S-NSSAI. The at least one hardware processor is configured to transmit at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to the second communication device.

[0034] Exemplary embodiments of the present disclosure include a method for core network communication devices. The method includes communicating between core network devices to control the availability of a partial network slice in a registration area when a network slice is available at one or more TAs of a RA in a PLMN or SNPN. The method includes transmitting first information from a first core network device to a second core network device indicating a Requested NSSAI received from a user device (UE), the second core network device selecting second information indicating a Partially Allowed NSSAI and third information indicating a Partially Rejected S-NSSAI in a RA during the registration procedure.

[0035] For example, this disclosure relates to a core network device. The core network device may select a Partially Allowed NSSAI and a Partially Rejected S-NSSAI within the RA based on a systematic mechanism using a system-wide database in PLMN or SNPN.

[0036] At least one definition of Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA in Non-Patent Literature 2 can be applied to at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA in this Disclosure.

[0037] First aspect This embodiment includes a mechanism for selecting newly introduced network slice-related data, such as Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, based on a systematic mechanism using a system-wide database in PLMN or SNPN.

[0038] First example of the first aspect According to the network slice management mechanism in 5GC as defined in Non-Patent Document 3, 5GC has a Network Slice Selection Function (NSSF), which is a dedicated functional entity for assigning S-NSSAI to UEs based on the network slice in the Requested NSSAI from the UE, the UE's subscriber data, the UE's location, and other configuration data in 5GC and associated Operation and Maintenance (O&M) systems. Based on this mechanism, the mobile operator configures the network slice-related database in the NSSF.

[0039] On the other hand, Non-Patent Document 2 defines newly introduced network slice-related data, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within RA as being selected based on AMF's sole decision based on AMF local policy.

[0040] This means that mobile operators managing network slice-related databases in NSSF must maintain a separate database for Partially Allowed NSSAI in AMF and partially reject S-NSSAI in RA.

[0041] Therefore, mobile operators need to manage network slice-related data using both NSSF and AMF.

[0042] This makes it difficult for mobile operators to manage network slice-related data within the network, resulting in additional management costs.

[0043] For example, a first example of the first embodiment includes a flexible mechanism for managing newly introduced network slice-related data, such as Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, in a mobile operator's network.

[0044] Figure 1 shows an example of selecting newly introduced network slice-related data using NSSF76.

[0045] The detailed processing of the first example of the first embodiment will be described below with reference to Figure 1.

[0046] Step 1. UE3 sends a Registration Request message to AMF70 that includes at least one of the following: User ID, Requested NSSAI, and Partial Network Slice Availability support indication.

[0047] The following bullet points explain the details of each parameter. The user ID may be 5G-GUTI, SUCI, or SUPI. For example, the user ID may be UE3's 5G-GUTI, SUCI, or SUPI. The user ID may also be expressed as User Identity. • A Requested NSSAI is a list of S-NSSAIs that UE3 requests to be used. The definition of a Requested NSSAI in the current 3GPP standard may apply to the Requested NSSAI in this disclosure. The Partial Network Slice Availability support indicator indicates that UE3 supports processing at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI within the RA. For example, the Partial Network Slice Availability support indicator indicates that UE3 can recognize or understand at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI. For example, the Partial Network Slice Availability support indicator indicates that UE3 can perform processes related to at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI. The Partial Network Slice Availability support indicator may indicate that UE3 supports at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI.

[0048] Step 2. Upon receiving the Registration Request message in Step 1, AMF70 calls the Nudm_UECM_Registration service on UDM75 to register AMF70 as a roaming node for UE3. UDM75 may be included in HPLMN.

[0049] Step 3. After the Nudm_UECM_Registration service is completed in Step 2, AMF70 sends a Nudm_SDM_Get Request message to UDM75 that includes a user ID and at least one of the Partial Network Slice Availability support indicators. Refer to Step 1 for definitions of the Partial Network Slice Availability support indicators and user IDs. For example, the Partial Network Slice Availability support indicators and user IDs in Step 3 may be the same as those in Step 1.

[0050] Step 4. Upon receiving a Nudm_SDM_Get Request message, UDM75 retrieves subscriber data from UE3 and sends a Nudm_SDM_Get Response message containing the subscriber data from UE3. The subscriber data may include the following: • S-NSSAI service area. This may be the geographical area of ​​Visited PLMN or NSPN. This information can be represented by at least one of the following: Universal Geographical Area Description (GAD) as defined in 3GPP TS23.032 (Non-Patent Document 4). NMEA format used in GPS systems. A revised Civic location format for location objects in presence information data format as defined in RFC5139 (Non-Patent Document 5). > A list of TAIs within the current VPLMN. • The limited service area of ​​S-NSSAI. This may be a geographical area within the Visited PLMN or NSPN. This information may be expressed as shown in the S-NSSAI service area.

[0051] In one example, UDM75 may include the data shown in the bullet points above only if UDM75 receives a Partial Network Slice Availability support indication from AMF70 in step 3.

[0052] Step 5. After AMF70 obtains subscriber data from UDM75 in Step 4, including the Subscribed NSSAI used by AMF70 to determine the Allowed NSSAI and / or Rejected NSSAI for UE3, AMF70 sends an Nnssf_NSSelection_Get message to NSSF76 that includes at least one of the Requested NSSAI, Partial Network Slice Availability support indicator, and other existing information. See Step 1 for definitions of the Partial Network Slice Availability indicator and Requested NSSAI. For example, the Partial Network Slice Availability support indicator and Requested NSSAI in Step 4 may be the same as those in Step 1. The Nnssf_NSSelection_Get message may include the TAI.

[0053] Step 6. Upon receiving the Nnssf_NSSelection_Get message, NSSF76 generates at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI in the RA based on the input parameters, for example, at least one of the Requested NSSAI and TAI in the Nnssf_NSSelection_Get message. For example, NSSF76 may determine at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI based on the input parameters.

[0054] The input parameters may be expressed as information for determining at least one of the following: Partially Allowed NSSAI and Partially Rejected S-NSSAI.

[0055] NSSF76 may generate a Partially Allowed NSSAI and at least one Partially Rejected S-NSSAI in the RA only if the Nnssf_NSSelection_Get message contains an indication of Partial Network Slice Availability support. The indication of Partial Network Slice Availability support may indicate to NSSF76 that UE3 supports a Partially Allowed NSSAI or a Partially Rejected S-NSSAI. NSSF76 may generate at least one Allowed NSSAI and Rejected NSSAI based on input parameters in the Nnssf_NSSelection_Get message, such as Requested NSSAI and TAI.

[0056] NSSF76 sends an Nnssf_NSSelection_Get Response message to AMF70 that includes at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI in RA. For example, if NSSF76 generates at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI in RA, NSSF76 may send an Nnssf_NSSelection_Get Response message to AMF70.

[0057] NSSF76 may include Partially Allowed NSSAI and Partially Rejected S-NSSAI in RA only if the Nnssf_NSSelection_Get message includes an indication of Partial Network Slice Availability support.

[0058] A Partially Allowed NSSAI may include a list of Allowed S-NSSAIs, each S-NSSAI in the list having a list of associated TAIs. S-NSSAIs within a Partially Allowed NSSAI may only be permitted for use with the TAI associated with that S-NSSAI.

[0059] For example, an S-NSSAI within a Partially Allowed NSSAI may be associated with a TAI or TA.

[0060] For example, a Partially Allowed NSSAI S-NSSAI may indicate an S-NSSAI that is permitted or available in the relevant or specific TAI or TA. For example, a Partially Allowed NSSAI includes S-NSSAI1 that is permitted or available in TAI1 (or TA1). For example, a Partially Allowed NSSAI includes an S-NSSAI that is permitted or available in the relevant or specific TAI or TA.

[0061] For example, a Partially Allowed NSSAI can be associated with a TAI or TA. For instance, if a Partially Allowed NSSAI is associated with TAI1 (or TA1) and the Partially Allowed NSSAI includes S-NSSAI1, then S-NSSAI1 may be permitted or usable by TAI1 (or TA1).

[0062] For example, a Partially Allowed NSSAI may indicate an S-NSSAI that is permitted or available on a related or specific TA or TAI. For example, a Partially Allowed NSSAI may include an S-NSSAI associated with a TA or TAI. For example, if a Partially Allowed NSSAI includes an S-NSSAI1 associated with TAI1 or TA1 identified by TAI1, it may mean that S-NSSAI1 is permitted or available on TAI1 or TA1 identified by TAI1. For example, if UE3 receives a Partially Allowed NSSAI that includes an S-NSSAI1 associated with TAI1 or TA1 identified by TAI1, and UE3 wants to use S-NSSAI1, UE3 may think that S-NSSAI1 is permitted or available on TA1. If UE3 wants to use S-NSSAI1 (for example, UE3 wants to establish a PDU session on S-NSSAI1), and determines that UE3 is in TA1, then UE3 may use S-NSSAI1 (for example, UE3 may establish a PDU session using S-NSSAI1, or UE3 may establish a PDU session on or associated with S-NSSAI1). If UE3 is not in TA1, UE3 may move to TA1 and use S-NSSAI1 in TA1. For example, Partially Allowed NSSAI or Partially Allowed NSSAI S-NSSAI may indicate an S-NSSAI that is allowed or usable in a particular TAI or a TA identified by a particular TAI. Partially Allowed NSSAI or Partially Allowed NSSAI S-NSSAI may be associated with a particular TAI or a TA identified by a particular TAI.

[0063] A partially rejected S-NSSAI in a RA may contain a list of S-NSSAIs, each S-NSSAI in the list associated with a list of TAIs. An S-NSSAI in a partially rejected S-NSSAI in a RA may only be permitted for use in the TAI associated with that S-NSSAI. In order to use an S-NSSAI in a TAI, or a TA identified by a TAI, the UE must perform a Registration procedure using the S-NSSAI set as the Requested NSSAI in the associated TAI.

[0064] For example, an S-NSSAI in a partially rejected S-NSSAI within a RA may be associated with a TAI or TA. For example, a partially rejected S-NSSAI within a RA may include an S-NSSAI associated with a TA or TAI. For example, if a partially rejected S-NSSAI within a RA includes an S-NSSAI1 associated with TAI1 or TA1 identified by TAI1, it may mean that S-NSSAI1 is only permitted or usable in TAI1 or TA1 identified by TAI1. For example, if UE3 receives a partially rejected S-NSSAI within a RA that includes an S-NSSAI1 associated with TAI1 or TA1 identified by TAI1, and UE3 wants to use S-NSSAI1, UE3 may move to TA1 and perform the Registration procedure for S-NSSAI1 in TA1. If UE3 is already in TA1, UE3 may perform the Registration procedure for S-NSSAI1 in TA1.

[0065] For example, a partially rejected S-NSSAI in a RA or an S-NSSAI of a partially rejected S-NSSAI in a RA may indicate an S-NSSAI that is permitted or made available for use by UE3 performing a new registration procedure for the S-NSSAI in a specific TAI or a TA identified by a specific TAI, or by performing the registration procedure for the S-NSSAI again in a specific TAI or a TA identified by a specific TAI.

[0066] For example, a partially rejected S-NSSAI in a RA or an S-NSSAI of a partially rejected S-NSSAI in a RA may indicate an S-NSSAI that is permitted or available in a specific TAI or a TA identified by a specific TAI when UE3 performs a new Registration procedure for an S-NSSAI in a specific TAI or a TA identified by a specific TAI, or performs a Registration procedure for an S-NSSAI again in a specific TAI or a TA identified by a specific TAI. A partially rejected S-NSSAI in a RA or an S-NSSAI of a partially rejected S-NSSAI in a RA may be associated with a specific TAI or a TA identified by a specific TAI.

[0067] For example, the S-NSSAI in a partially rejected S-NSSAI within a RA may indicate an S-NSSAI that is permitted or available only in the associated or specific TAI or TA. For example, a partially rejected S-NSSAI within a RA may include S-NSSAI1 that is permitted or available only in TAI1 (or TA1).

[0068] For example, a partially rejected S-NSSAI within a RA includes an S-NSSAI that is permitted or usable only in the associated or specific TAI or TA.

[0069] For example, a partially rejected S-NSSAI in a RA may be associated with a TAI or TA. For example, if a partially rejected S-NSSAI in a RA is associated with TAI1 (or TA1) and the partially rejected S-NSSAI in the RA includes S-NSSAI1, then S-NSSAI1 may only be permitted or usable in TAI1 (or TA1). For example, if a partially rejected S-NSSAI in a RA is associated with TAI1 (or TA1) and the partially rejected S-NSSAI in the RA includes S-NSSAI1, then S-NSSAI1 may be rejected in TAIs (or TAs) other than TAI1 (or TA1).

[0070] For example, a partially rejected S-NSSAI within a RA may indicate an S-NSSAI that is permitted or usable only in the relevant or specific TA or TAI.

[0071] NSSF76 may include at least one of the following in its Nnssf_NSSelection_Get Response message: a first target AMF set, a first list of candidate AMFs, a second target AMF set, a second list of candidate AMFs, a third AMF set, and a third list of candidate AMFs. The AMFs in the first target AMF set or the first list may only support Allowed NSSAI. The AMFs in the second target AMF set or the second list may support both Allowed NSSAI and Partially Allowed NSSAI. The AMFs in the third target AMF set or the third list may only support Partially Allowed NSSAI.

[0072] For example, if NSSF76 receives a Requested NSSAI containing S-NSSAI1, NSSF76 may generate a Partially Allowed NSSAI containing S-NSSAI1 by setting S-NSSAI1 to Partially Allowed NSSAI, based on the operator's policy or NSSF76's local settings.

[0073] For example, if NSSF76 receives a Requested NSSAI containing S-NSSAI1, NSSF76 may generate a Partially Rejected S-NSSAI in the RA containing S-NSSAI1 by setting S-NSSAI1 as a Partially Rejected S-NSSAI in the RA, based on the operator's policy or NSSF76's local settings.

[0074] For example, if NSSF76 receives a Requested NSSAI containing S-NSSAI1 and TAI1, NSSF76 may generate a Partially Allowed NSSAI containing S-NSSAI1 for TAI1 by setting S-NSSAI1 as a Partially Allowed NSSAI, based on the operator's policy or NSSF76's local settings.

[0075] For example, if NSSF76 receives a Requested NSSAI and TAI1 that include S-NSSAI1, NSSF76 may, based on the operator's policy or NSSF76's local settings, set S-NSSAI1 as a Partially Allowed NSSAI and associate TAI1 with S-NSSAI1, thereby generating a Partially Allowed NSSAI that includes S-NSSAI1 associated with TAI1. S-NSSAI1 associated with TAI1 may indicate that S-NSSAI1 is permitted or usable only in TAI1 (for example, in TA1 indicated by TAI1).

[0076] For example, if NSSF76 receives a Requested NSSAI and TAI1 that include S-NSSAI1, NSSF76 may generate a Partially Rejected S-NSSAI in the RA for the TAI1 that includes S-NSSAI1 by setting S-NSSAI1 as a Partially Rejected S-NSSAI in the RA, based on the operator's policy or NSSF76's local settings.

[0077] For example, if NSSF76 receives a Requested NSSAI and TAI1 containing S-NSSAI1, NSSF76 may, based on the operator's policy or NSSF76's local settings, generate a Partially Rejected S-NSSAI in the RA containing S-NSSAI1 associated with TAI1 by setting S-NSSAI1 as a Partially Rejected S-NSSAI in the RA and associating TAI1 with S-NSSAI1. S-NSSAI1 associated with TAI1 may indicate that S-NSSAI1 is permitted or available in TAI1 (for example, in TA1 indicated by TAI1).

[0078] For example, in this disclosure, NSSF76 may set an S-NSSAI that NSSF76 allows UE3 to use in a particular TA to be a Partially Allowed NSSAI, based on at least one of the input parameters, the operator policy, and NSSF76's local settings. For example, in this disclosure, NSSF76 may set an S-NSSAI that is allowed or available for use when UE3 performs a new Registration procedure for an S-NSSAI in a particular TA, or performs the Registration procedure for an S-NSSAI again for a Partially Rejected S-NSSAI in the RA in a particular TA, based on at least one of the input parameters, the operator policy, and NSSF76's local settings.

[0079] For example, NSSF76 may determine at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI based on information indicating which network slices or S-NSSAIs are permitted or available to UE3. At least one of the input parameters, operator policies, and NSSF76 local settings may include information indicating which network slices or S-NSSAIs are permitted or available to UE3, or other information for determining at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAIs.

[0080] Step 7. Upon receiving the Nnssf_NSSelection_Get Response message in Step 6, AMF70 determines at least one of the following based on the input from NSSF76 in Step 6: RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within the RA. For example, AMF70 may determine at least one of the following based on the input from NSSF76 in Step 6: RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within the RA.

[0081] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message, AMF70 may determine the relationship between the RA (e.g., TAI list) and at least one of the following: Partially Allowed NSSAI, Partially Rejected S-NSSAI, Allowed NSSAI, and Rejected NSSAI.

[0082] For example, consider a case where Allowed NSSAI includes S-NSSAI1, Partially Allowed NSSAI includes S-NSSAI2, and Partially Rejected S-NSSAI includes S-NSSAI3 (for example, AMF70 receives an Nnssf_NSSelection_Get response message containing Allowed NSSAI including S-NSSAI1, Partially Allowed NSSAI including S-NSSAI2, and Partially Rejected S-NSSAI including S-NSSAI3), and RA includes TA1 to TA4. In this case, AMF70 may allow the use of S-NSSAI1 in RA (i.e., in TA1 to TA4), allow the use of S-NSSAI2 in TA1 and TA2, and allow the use of S-NSSAI3 in TA4. In other words, AMF70 can determine that Allowed NSSAI is for RA (i.e., TA1 to TA4), Partially Allowed NSSAI is for TA1 and TA2, and Partially Rejected S-NSSAI is for TA4.

[0083] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message, AMF70 may decide to send at least one of the received Partially Allowed NSSAI, Partially Rejected S-NSSAI, Allowed NSSAI, and Rejected NSSAI to UE3 as is.

[0084] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message that includes a Partially Allowed NSSAI containing S-NSSAI1, AMF70 may decide to send at least the Partially Allowed NSSAI containing S-NSSAI1 to UE3.

[0085] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message containing a partially rejected S-NSSAI in the RA that includes S-NSSAI1, AMF70 may decide to send at least the received partially rejected S-NSSAI in the RA that includes S-NSSAI1 to UE3.

[0086] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message containing a Partially Allowed NSSAI for TAI1 including S-NSSAI1, AMF70 may decide to send at least the received Partially Allowed NSSAI for TAI1 including S-NSSAI1 to UE3.

[0087] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message containing a partially rejected S-NSSAI in the RA concerning TAI1, including S-NSSAI1, AMF70 may decide to send at least the partially rejected S-NSSAI in the RA concerning TAI1, including S-NSSAI1, that it received to UE3.

[0088] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message that includes a Partially Allowed NSSAI, which includes an S-NSSAI1 associated with TAI1, AMF70 may decide to send at least the received Partially Allowed NSSAI, which includes an S-NSSAI1 associated with TAI1, to UE3.

[0089] For example, if AMF70 receives an Nnssf_NSSelection_Get Response message containing a partially rejected S-NSSAI in the RA, which includes an S-NSSAI1 associated with TAI1, AMF70 may decide to send at least the received partially rejected S-NSSAI in the RA, which includes an S-NSSAI1 associated with TAI1, to UE3.

[0090] If AMF70 decides to transmit a Partially Allowed NSSAI along with an Allowed NSSAI, AMF70 may select an AMF that supports both Allowed NSSAI and Partially Allowed NSSAI from a second set of target AMFs or a second list of candidate AMFs.

[0091] For example, in this disclosure, the AMF70 may set an S-NSSAI that the AMF70 allows the UE3 to use in a particular TA to a Partially Allowed NSSAI, based on at least one of the input from the NSSF76 in step 6, the operator's policy, and the AMF70's local settings.

[0092] For example, in this disclosure, AMF70 may, based on at least one of the input from NSSF76 in step 6, the operator's policy, and AMF70's local settings, set any S-NSSAI that is permitted or available for use when UE3 performs a new S-NSSAI Registration procedure at a particular TA, or performs an S-NSSAI Registration procedure again at a particular TA, as a Partially Rejected S-NSSAI in the RA.

[0093] Step 8. AMF70 sends a Registration Accept message to UE3 that includes at least one of the following: RA (i.e., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, Partially Rejected S-NSSAI within the RA, and other existing information.

[0094] For example, AMF70 may send a Registration Accept message containing the information determined in step 7 (e.g., at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI).

[0095] For example, AMF70 may send a UE Configuration Update message or other message containing the information determined in step 7 (e.g., at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI).

[0096] Step 9. Upon receiving a Registration Accept message from AMF70, UE3 stores the TAI list, Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, Partially Rejected S-NSSAI in RA, and at least one of the other information received in Step 8. For example, UE3 may store the TAI list, Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, Partially Rejected S-NSSAI in RA, and other received information in non-volatile memory within UE3.

[0097] Step 10. UE3 sends a Registration Complete message to AMF70.

[0098] Modification 1 of the first example of the first aspect: If UE3 receives an Allowed NSSAI containing an S-NSSAI (e.g., S-NSSAI1) and a Partially Allowed NSSAI containing the same S-NSSAI (e.g., S-NSSAI1) from AMF70 in the Registration Accept message in step 8, UE3 may accept the received S-NSSAI (e.g., S-NSSAI1) as an Allowed NSSAI (for example, UE3 may accept the Allowed NSSAI containing S-NSSAI1 and use the Allowed NSSAI for subsequent processing), or if UE3 has stored or holds a Partially Allowed NSSAI containing an S-NSSAI (e.g., S-NSSAI1), UE3 may remove the S-NSSAI (e.g., S-NSSAI1) from the Partially Allowed NSSAI.

[0099] Alternatively, if UE3 receives an Allowed NSSAI containing an S-NSSAI (e.g., S-NSSAI1) and a Partially Allowed NSSAI containing the same S-NSSAI (e.g., S-NSSAI1) from AMF70 in the Registration Accept message in step 8, UE3 may accept the received S-NSSAI (e.g., S-NSSAI1) as a Partially Allowed NSSAI (for example, UE3 may accept the Partially Allowed NSSAI containing S-NSSAI1 and use the Partially Allowed NSSAI for subsequent processing), or if UE3 already has an Allowed NSSAI containing an S-NSSAI (e.g., S-NSSAI1), UE3 may remove the S-NSSAI (e.g., S-NSSAI1) from the Allowed NSSAI.

[0100] Modification 2 of the first example of the first embodiment: If UE3 receives a Rejected NSSAI containing an S-NSSAI (e.g., S-NSSAI1) and a partially rejected S-NSSAI in the RA containing the same S-NSSAI (e.g., S-NSSAI1) from AMF70 in the Registration Accept message in step 8, UE3 may accept the received S-NSSAI (e.g., S-NSSAI1) as a Rejected NSSAI, or if UE3 has already stored or holds a partially rejected S-NSSAI in the RA containing an S-NSSAI (e.g., S-NSSAI1), UE3 may remove the S-NSSAI (e.g., S-NSSAI1) from the partially rejected S-NSSAI in the RA.

[0101] Alternatively, if UE3 receives a Rejected NSSAI containing an S-NSSAI (e.g., S-NSSAI1) and a partially Rejected S-NSSAI in the RA containing the same S-NSSAI (e.g., S-NSSAI1) from AMF70 in the Registration Accept message in step 8, UE3 may accept the received S-NSSAI (e.g., S-NSSAI1) as a partially Rejected S-NSSAI in the RA, and if UE3 already stores or holds a Rejected NSSAI containing an S-NSSAI (e.g., S-NSSAI1), UE3 may remove the S-NSSAI (e.g., S-NSSAI1) from the Rejected NSSAI.

[0102] Modification 3 of the first example of the first aspect: In one example, the Partially Allowed NSSAI in steps 6, 7, 8, and 9 may include a list of Allowed S-NSSAI, each S-NSSAI in the list associated with a list of cells.

[0103] For example, S-NSSAI in Partially Allowed NSSAI can be associated with a list of cells. For example, S-NSSAI in Partially Allowed NSSAI can be associated with a cell. For example, a Partially Allowed NSSAI S-NSSAI may be associated with a specific cell or may be available in a specific cell.

[0104] For example, S-NSSAI1 associated with cell 1 is included in Partially Allowed NSSAI. S-NSSAI1 associated with cell 1 may be allowed or available in cell 1.

[0105] For example, S-NSSAI1 associated with TA1 and cell 1 is included in Partially Allowed NSSAI. S-NSSAI1 associated with TA1 and cell 1 may be allowed or available in cell 1 of TA1.

[0106] Modification 4 of the first example of the first aspect: For example, in step 6, NSSF76 does not have to provide a Partially Allowed NSSAI or a Partially Rejected S-NSSAI in the RA, but may provide a list of S-NSSAIs that are not uniformly supported in the RA, including TAs that are present in the Allowed NSSAI and Requested NSSAI and supported by AMF70, and TAs that support the S-NSSAIs in the list (e.g., TAIs of the TAs). NSSF76 may also send a target AMF set containing AMFs that support the Allowed NSSAI, or a list of candidate AMFs that support the Allowed NSSAI. In step 7, upon receiving the Nnssf_NSSelection_Get Response message, AMF70 may construct a Partially Allowed NSSAI. AMF70 may send Allowed NSSAI and Partially Allowed NSSAI to NSSF76 in an existing or new message to obtain a target AMF set containing AMFs that support both Allowed NSSAI and Partially Allowed NSSAI, or a list of candidate AMFs that support both Allowed NSSAI and Partially Allowed NSSAI. Upon receiving a message from AMF70, NSSF76 may provide AMF70 with a target AMF set or a list of candidate AMFs in an existing or new message. Upon receiving a message from NSSF76, AMF70 may select an AMF from the list of target AMF sets or candidate AMFs. Steps 8 and 9 may be performed later.

[0107] Modification 5 of the first example of the first aspect: For example, AMF70 may subscribe to NSSF76 to receive notifications about network slice support within the PLMN on a periodic or event-based basis. For instance, AMF70 may subscribe to NSSF76 or send a subscription request to NSSF76 and receive notifications from NSSF76 about network slice support within the PLMN. The notifications may be periodic or regular. Notifications may be sent to AMF70 on a periodic or regular basis. Notifications may be sent to AMF70 when a specific event occurs.

[0108] During the request to join NSSF76, AMF70 may provide a list of network slices supported by AMF70 (e.g., a list of S-NSSAIs). AMF70 may also provide the type of notification required by NSSF76. For example, the type may indicate that periodic or regular notifications are required. For example, the type may indicate that notifications are required when a specific event occurs. For example, the event may include a change in one or more network slices (e.g., one or more S-NSSAIs) supported by AMF70. The change may relate to whether the network slice (e.g., S-NSSAI) is fully supported or partially supported within the PLMN. If a network slice changes from being fully supported in the PLMN to being partially supported in the PLMN (e.g., if the TAs supporting the network slice change from an RA including TA1 and TA2 to TA1 only), NSSF76 may provide AMF70 with a notification containing an updated list of TAs that support each network slice (e.g., NSSF76 may provide AMF70 with TA1 that supports the network slice). If a network slice is temporarily supported, NSSF76 may provide a time window during which the temporary slice is supported. AMF70 may store network slice support information received from NSSF76 for each network slice supported by AMF70. For example, the network slice support information may include an updated list and at least one of the time windows. If UE3 sends a Partial Network Slice Availability support indication while registering with AMF70, AMF70 may use the network slice support information stored within AMF70 to verify whether the network slice in the Requested NSSAI provided by UE3 in step 1 of Figure 1 (e.g., S-NSSAI) is fully or partially supported by PLMN.If one or more network slices within a Requested NSSAI are partially supported by PLMN, AMF70 may consider the TAs that support these network slices when determining which RA to assign to UE3, so as to minimize the number of partially supported network slices in UE3's RA. AMF70 may use the Registration Accept message in step 8 of Figure 1 to provide UE3 with allowed network slices (e.g., Allowed NSSAI), partially allowed network slices (e.g., Partially Allowed NSSAI), and partially rejected network slices (e.g., Partially Rejected S-NSSAI in the RA). Alternatively, AMF70 may use the UE Configuration Update message to provide UE3 with partially allowed and partially rejected network slices.

[0109] Modification 6 of the first example of the first aspect: AMF70 does not need to include a Partial Network Slice Availability support indicator in the Nudm_SDM_Get Request message. UDM75 may send a Nudm_SDM_Get Response message even if the Nudm_SDM_Get Request message does not include a Partial Network Slice Availability support indicator.

[0110] The Partial Network Slice Availability support indicator does not necessarily have to be included in the message shown in Figure 1. Each node in Figure 1 may perform the process shown in Figure 1 without the Partial Network Slice Availability support indicator.

[0111] These variations can be applied to other examples of the first embodiment.

[0112] The above problem can be solved according to the first example of the first embodiment and at least one of the modifications of the first example.

[0113] For example, at least one of the first examples of the first embodiment and one of the modifications thereof can solve the problem of some issues with AMF decisions based on AMF local policies.

[0114] For example, the first example of the first embodiment and at least one of its modifications solve the problem that mobile operators have to manage network slice-related data in one NSSF and the other AMF, which makes it difficult for mobile operators to manage network slice-related data within their networks and incurs additional management costs.

[0115] For example, according to the first example of the first embodiment and at least one of the modifications of the first example, NSSF76 can constitute at least one of a Partially Allowed NSSAI and a Partially Rejected S-NSSAI within the RA. For example, it does not require separate management of network slice-related data. For example, network slice-related data is stored in NSSF76. Thus, the above problem can be solved.

[0116] A second example of the first embodiment: According to the network slice management mechanism in 5GC as defined in Non-Patent Document 3, 5GC has a dedicated functional entity called Network Slice Selection Function (NSSF) for assigning S-NSSAI to UEs based on the network slice in the Requested NSSAI from the UE, the UE's subscriber data, the UE's location, and other configuration data in 5GC and related Operation and Maintenance (O&M) systems. Based on this mechanism, the mobile operator configures a network slice-related database in the NSSF.

[0117] On the other hand, Non-Patent Document 2 defines newly introduced network slice-related data, Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, which are selected based on AMF's sole decision based on AMF local policy.

[0118] The presence of nodes other than AMF in a 5G system, and therefore the fact that only AMF can implement the above decisions based on AMF local policies, could be an unnecessary limitation for the 5G system.

[0119] For example, a second example of the first embodiment includes a flexible mechanism for managing newly introduced network slice-related data, such as Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, in a mobile operator's network.

[0120] Figure 2 includes an example where, based on one or more operator policies or settings in PCF73, PCF73 allows AMF70 to provide Partially Allowed NSSAI and Partially Rejected S-NSSAI within the RA. This example allows network slices to be classified as partially allowed or partially denied not only because these network slices are not supported by certain TAs in the UE's RA, but also based on operator policies in PCF73 that may take into account slice congestion (e.g., network slices are not allowed in congested TAs) or other issues related to network slices. For example, one or more network slices may be supported across the UE3's RA, but some TAs in the RA may be very congested, so based on operator policies or settings in PCF73, network slices in these TAs with high congestion (e.g., congestion exceeding a threshold level set in one or more operator policies) may be considered not supported in the highly congested TAs. In this case, these network slices are supported by all TAs in the RA, but are treated as partially allowed network slices and provided to UE3. In other words, TAs with congestion higher than the threshold set in the operator policy or configuration in PCF73 are not permitted. While NSSF76 has a system-wide granularity, PCF73 allows the granularity of this function to be per UE, per location, or for a specific time period only.

[0121] Referring to Figure 2, the detailed processing of the second example of the first embodiment will be described.

[0122] Step 1. Steps 1 through 4 in Figure 1 are performed.

[0123] Step 2. After AMF70 retrieves subscriber data for UE3 from UDM75, AMF70 sends an Npcf_AMPolicyControl_Create message to PCF73 that includes at least one of the Requested NSSAI, Partial Network Slice Availability support indicator, and other existing information. See Step 1 in Figure 1 for definitions of Requested NSSAI and Partial Network Slice Availability support indicator. For example, the Partial Network Slice Availability support indicator and Requested NSSAI in Step 2 may be the same as those in Step 1.

[0124] Step 3. When PCF73 receives the Npcf_AMPolicyControl_Create message, it may decide to configure the RA to partially allow or partially deny one or more requested S-NSSAIs (e.g., S-NSSAIs of the Requested NSSAI) based on the Requested NSSAI, the operator settings, and at least one of PCF73's operator policies. For example, PCF73 may decide to partially allow an NSSAI and at least one partially rejected S-NSSAI in the RA based on the received Requested NSSAI, the operator settings, and at least one of PCF73's operator policies. For example, PCF73 may decide to partially allow an NSSAI and at least one partially rejected S-NSSAI in the RA even if PCF73 does not receive a Partial Network Slice Availability support indication.

[0125] The received Requested NSSAI, operator settings, and at least one of the operator policies may be expressed as information for determining at least one of the Partially Allowed NSSAI and Partial S-NSSAI.

[0126] For example, one or more network slices may be supported across the entire RA of UE3, but some TAs in the RA may experience very high congestion, or for other reasons, based on the operator policy or PCF73 settings, network slices within those TAs may be considered unsupported in those TAs due to high congestion (e.g., congestion exceeding the threshold level set in the operator policy) or other reasons. In this case, these network slices are supported in all TAs of the RA, but are treated as partially allowed network slices (e.g., Partially Allowed NSSAI), i.e., not allowed in TAs where congestion is higher than the threshold set in the operator policy or PCF73 settings, and are provided to UE3. PCF73 can determine whether a network slice is a partially allowed network slice (e.g., Partially Allowed NSSAI) or a partially denied network slice (e.g., Partially Denied S-NSSAI) at a granularity of all UE bases, groups of UE bases, or a single UE base, depending on the instructions in the operator policy or PCF73 settings.

[0127] PCF73 generates a Partially Allowed NSSAI and a Partially Rejected S-NSSAI in the RA based on input parameters in the Npcf_AMPolicyControl_Create message, such as Requested NSSAI. PCF73 may generate at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI in the RA only if the Npcf_AMPolicyControl_Create message includes an indication of Partial Network Slice Availability support.

[0128] For example, PCF73 may configure S-NSSAIs within Requested NSSAIs as Partially Allowed NSSAIs or Partially Rejected S-NSSAIs within RAs, based on the operator policies or local settings within PCF73.

[0129] For example, PCF73 may set an S-NSSAI in a Requested NSSAI to a Partially Allowed NSSAI or a Partially Rejected S-NSSAI in a RA, based on the operator's policy or local settings within PCF73.

[0130] For example, suppose S-NSSAI1 is supported in an RA including TA1 and TA2, and PCF73 recognizes that TA1 is in a highly congested state (e.g., the congestion level of TA1 is higher than the threshold congestion level set by the operator configuration or policy) based on the operator's policy or local settings in PCF73. In this case, PCF73 may set S-NSSAI1 to Partially Allowed NSSAI for TA2 (e.g., UE3 can trigger a PDU session request when on TA2, but even if S-NSSAI1 is supported on TA1, UE3 cannot trigger a PDU session request when on TA1 because of the high congestion level on TA1), or PCF73 may set S-NSSAI1 related to TA2 to Partially Allowed NSSAI.

[0131] For example, suppose S-NSSAI1 is supported within an RA including TA1 and TA2, and PCF73 recognizes that TA1 is in a highly congested state based on the operator's policy or local settings within PCF73. In this case, PCF73 may set S-NSSAI1 to partially rejected S-NSSAI with respect to TA1, or PCF73 may set S-NSSAI1 related to TA1 to partially rejected S-NSSAI.

[0132] Please note that whether a Requested NSSAI's S-NSSAI is set to a Partially Allowed NSSAI or a Partially Rejected S-NSSAI within the RA may be determined based on other factors. For example, PCF73 may determine whether a Requested NSSAI's S-NSSAI is set to Partially Allowed NSSAI or Partially Rejected S-NSSAI within the RA based on subscriber data in UE3 (for example, an S-NSSAI that is normally fully supported in the PLMN and UE's RA may, at a specific time of day, week, or year, transition from an Allowed S-NSSAI (e.g., Allowed NSSAI) to a Partially Allowed S-NSSAI (e.g., Partially Allowed NSSAI) for UE3 at a particular time of day, week, or year due to subscription in the UDM. In this way, operators can balance quality of service between UEs with different subscription levels, enabling UEs with higher priority subscriptions to maintain quality of service even when the system is congested), or based on information indicating which network slices (e.g., S-NSSAI) are supported in the TA (or TAI).

[0133] Subscriber data may indicate which network slices (e.g., S-NSSAI) are permitted or available to the UE.

[0134] For example, suppose S-NSSAI1 is supported within an RA including TA1 and TA2, and PCF73 knows, based on the operator's policy or PCF73's local settings, that S-NSSAI1 is permitted or available for UE3 within TA1. In this case, PCF73 may set S-NSSAI1 to Partially Allowed NSSAI for TA1, or PCF73 may set S-NSSAI1 associated with TA1 to Partially Allowed NSSAI.

[0135] For example, suppose S-NSSAI1 is supported within an RA including TA1 and TA2, and PCF73 knows, based on the operator's policy or PCF73's local settings, that S-NSSAI1 is permitted or available to UE3 when UE3 performs the Registration procedure in TA1. In this case, PCF73 may set S-NSSAI1 to partially rejected S-NSSAI with respect to TA1, or PCF73 may set S-NSSAI1 related to TA1 to partially rejected S-NSSAI.

[0136] For example, in this disclosure, PCF73 may set an S-NSSAI that PCF73 allows UE3 to use in a particular TA as a Partially Allowed NSSAI, based on the received Requested NSSAI, operator settings, and at least one of PCF73's operator policies.

[0137] For example, in this disclosure, PCF73 may set S-NSSAIs that are permitted or available for use when UE3 performs a new Registration procedure for S-NSSAI at a particular TA, or performs a Registration procedure for S-NSSAI again at a particular TA, based on the received Requested NSSAI, operator settings, and PCF73's operator policy, as Partially Rejected S-NSSAIs in the RA.

[0138] For example, PCF73 may determine at least one of a Partially Allowed NSSAI and a Partially Rejected S-NSSAI, similar to NSSF76 in step 6 of Figure 1 or AMF70 in step 7 of Figure 1.

[0139] For example, AMF70 or NSSF76 in Figure 1, similar to PCF73 in Figure 2, may partially determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI.

[0140] Step 4. PCF73 sends an Npcf_AMPolicyControl_Create Response message to AMF70 that includes at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI in the RA.

[0141] For example, PCF73 may send an Npcf_AMPolicyControl_Create Response message containing the information determined in step 3 (e.g., at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI).

[0142] PCF73 may include Partially Allowed NSSAI and Partially Rejected S-NSSAI in RA only if the Npcf_AMPolicyControl_Create message includes an indication of Partial Network Slice Availability support. For details on Partially Allowed NSSAI and Partially Rejected S-NSSAI in RA, see step 6 in Figure 1.

[0143] Step 5. Upon receiving the Npcf_AMPolicyControl_Create Response message in Step 4, AMF70 determines the RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within the RA based on the input from PCF73 in Step 4. AMF70 may perform the same processing as in Step 7 in Figure 1.

[0144] Step 6. Steps 8 through 10 in Figure 1 are performed.

[0145] Modification 1 of the second example of the first embodiment: In one example, operator policies or settings related to network slice availability (e.g., the operator policies or settings described in step 3) may be provided by PCF73 to AMF70 in step 4 of Figure 2, either in the Npcf_AMPolicyControl_Create Response message or in other existing or new messages between PCF73 and AMF70. In this case, AMF70 may determine, based on the operator policies and settings related to network slice availability provided by PCF73 to AMF70 in step 4 of Figure 2, which network slices (e.g., S-NSSAI) of the Requested NSSAI provided by UE3 in step 1 of Figure 2 should be treated as partially allowed network slices (e.g., Partially Allowed NSSAI) or partially denied network slices (e.g., Partially Denied S-NSSAI). For example, one or more network slices may be supported across the entire RA of UE3, but because some TAs in the RA may experience very high congestion, or for other reasons, based on the operator policy and settings related to network slice availability provided from PCF73 to AMF70, the network slices of those TAs may be deemed unsupported in those TAs due to high congestion (e.g., congestion exceeding the threshold level set in the operator policy) or for other reasons. In this case, even if these network slices are supported in all TAs of the RA of UE3, they are treated as Partially Allowed network slices, meaning they are provided to UE3 as not being permitted in TAs where congestion is higher than the threshold set in the operator policy and settings related to network slice availability provided from PCF73 to AMF70.The AMF70 can determine whether a network slice is a partially allowed or partially rejected network slice at a granularity of all UE bases, per group of UE bases, or per single UE base, depending on the operator policy or configuration instructions received from the PCF73. For example, the AMF70 may configure the S-NSSAI of a Requested NSSAI as a Partially Allowed NSSAI or a Partially Rejected S-NSSAI in the RA, based on the operator policy or configuration received from the PCF73, similar to the PCF73 in step 3 of Figure 2.

[0146] The above problems can be solved according to a second example of the first embodiment and at least one of variations of the second example.

[0147] For example, at least one of the second example of the first embodiment and a modification thereof can solve the problem of some issues with regard to decisions made by the AMF based on the AMF local policy.

[0148] For example, at least one of the second example of the first embodiment and a variation thereof can solve the problem that the above decision based on the AMF local policy can be made only by the AMF, which could potentially impose unnecessary restrictions on the 5G system.

[0149] For example, according to at least one of the second example of the first embodiment and a modification of the second example, the PCF73 can constitute at least one of a Partially Allowed NSSAI and a Partially Rejected S-NSSAI in the RA. Thus, the above problem can be solved.

[0150] Third example of the first aspect According to the network slice management mechanism in 5GC as defined in Non-Patent Document 3, 5GC has a Network Slice Selection Function (NSSF), which is a dedicated functional entity for assigning S-NSSAI to UEs based on the network slice in the Requested NSSAI from the UE, the UE's subscriber data, the UE's location, and other configuration data in 5GC and associated Operation and Maintenance (O&M) systems. Based on this mechanism, the mobile operator configures a network slice-related database in the NSSF.

[0151] On the other hand, Non-Patent Document 2 defines newly introduced network slice-related data, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within RA as being selected based on AMF's sole decision based on AMF local policy.

[0152] The presence of nodes other than AMF in a 5G system, and therefore the fact that only AMF can implement the above decisions based on AMF local policies, could be an unnecessary limitation for the 5G system.

[0153] For example, a third example of the first embodiment includes a flexible mechanism for managing newly introduced network slice-related data, such as Partially Allowed NSSAI and Partially Rejected S-NSSAI within RA, in a mobile operator's network.

[0154] Figure 3 illustrates an example that relies on network slice information provided by NWDAF74. This allows network slices to be classified as partially permitted or partially denied based on the latest network slice status information provided by NWDAF74, which may relate to slice congestion (e.g., slices are not allowed in highly congested TAs) or network slice issues, not just because the slice is not supported by some TAs in the RA. For example, one or more network slices may be supported across the UE3's RA, but some TAs in the RA experience very high congestion. Based on the network slice status information provided by NWDAF74, network slices in these highly congested TAs (e.g., congestion exceeding the threshold level set by the operator policy) may be considered unsupported in those highly congested TAs. In this case, these network slices are supported by all TAs in the RA, but are treated as partially permitted or partially denied network slices and provided to UE3. That is, they are not permitted in TAs where congestion is higher than the threshold set in the network slice status information provided by NWDAF74.

[0155] Referring to Figure 3, the detailed processing of the third example of the first embodiment will be described.

[0156] Step 1. The AMF70 subscribes to the network slice information notification service provided by the NWDAF74.

[0157] The network slice information notification service provides service customers with up-to-date network slice information, including at least one of the following: congestion level, restricted area, permitted area, and available time information.

[0158] For example, NWDAF74 may provide network slice information to AMF70.

[0159] If AMF70 subscribes to the network slice information notification service provided by NWDAF74, AMF70 may provide NWDAF74 with a list of network slices (e.g., S-NSSAI) that AMF70 supports. NWDAF74 may then provide AMF70 with network slice information regarding the network slices (e.g., S-NSSAI) indicated in the list.

[0160] For example, the congestion level can indicate whether or not the network slice (S-NSSAI) is congested in the TA. For example, the congestion level may indicate the level of congestion in a network slice at a Terminal Address (TA). For example, the congestion level may indicate whether S-NSSAI1 or the network slice identified by S-NSSAI1 is congested in the TA. For example, the congestion level may indicate the level of congestion in S-NSSAI1 or the network slice identified by S-NSSAI1 in the TA. For example, the congestion level may be higher than the congestion threshold level defined by the operator's settings or policy for a network slice identified by S-NSSAI1 or S-NSSAI1 in the TA.

[0161] For example, a restricted area may indicate a limited region. For example, a restricted area may refer to a region that is restricted by congestion in a network slice. For example, a restricted area may indicate a restricted TA (Time Attack). For example, a restricted area may represent a TA that is limited by congestion in a network slice. For example, a restricted area may indicate an area or TA where S-NSSAI or the network slice identified by S-NSSAI is restricted or unavailable. For example, a restricted area may indicate that S-NSSAI or a network slice identified by S-NSSAI is restricted or unavailable at the TA. For example, a restricted area may indicate an area or TA where S-NSSAI1 or the network slice identified by S-NSSAI1 is restricted or unavailable. For example, a restricted area may indicate that S-NSSAI1 or the network slice identified by S-NSSAI1 is restricted or unavailable at the TA. For example, a restricted area may indicate that S-NSSAI1 or the network slice identified by S-NSSAI1 is restricted or unavailable at specific times of the day, week, or year as defined by the operator's policy or configuration.

[0162] For example, a permitted area may indicate an area that is permitted. For example, an permitted area might indicate an area that is allowed due to network slice congestion. For example, an authorized area might indicate an authorized TA (Transportation Access Point). For example, an authorized area might indicate a permitted TA (Terminal Adapter) that takes network slice congestion into consideration. For example, an authorized area may indicate an area or TA where S-NSSAI or a network slice identified by S-NSSAI is permitted or available. For example, an authorized area may indicate an area or TA where S-NSSAI1 or a network slice identified by S-NSSAI1 is authorized or available. For example, an authorized area may indicate that S-NSSAI1 or the network slice identified by S-NSSAI1 is authorized or available at the TA. For example, an authorized area may indicate that S-NSSAI1 or the network slice identified by S-NSSAI1 is permitted or available at specific times of the day, week, or year as defined by the operator's policy or configuration.

[0163] The available time information may indicate the expiration or duration of at least one of the following: congestion level, restricted area, or permitted area. The available time information may indicate the expiration date or period of the network slice (or S-NSSAI).

[0164] Step 2. When the conditions for notification are met, NWDAF74 sends an Nnwdaf_SliceInformation Notification message to AMF70 containing network slice information about the network slices supported by AMF70. For example, NWDAF74 may periodically send Nnwdaf_SliceInformation Notification messages to AMF70. For example, NWDAF74 may send an Nnwdaf_SliceInformation Notification message to AMF70 containing network slice information for the network slices shown in the list in step 1.

[0165] Network slice information can be represented as information for determining at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI.

[0166] Step 3. Based on the information in the Nnwdaf_SliceInformation Notification message received from NWDAF74, AMF70 determines whether an update to the UE configuration is necessary. For example, based on network slice support information received from NWDAF74, such as network slice congestion and other network slice issues, AMF70 may decide to treat one or more network slices from UE3's Allowed NSSAI as partially allowed network slices because these network slices are showing a high level of congestion at a specific TA in UE3's RA, or because these network slices have other issues at some TAs in UE3's RA. In such a case, AMF70 may update UE3's Allowed NSSAI by removing the problematic network slices from UE3's Allowed NSSAI and adding these network slices to Partially Allowed NSSAI or Partially Rejected S-NSSAI in UE3's RA.

[0167] For example, suppose the RA includes TA1 to TA4, and the AMF70 sends an Allowed NSSAI including S-NSSAI1, 2, and 3 to the UE3, and the AMF70 stores the Allowed NSSAI. Also suppose the received congestion level indicates that the network slice identified by S-NSSAI2 is congested at TA3 and TA4, and the network slice identified by S-NSSAI3 is congested at TA1 to TA3. In this case, the AMF70 may remove S-NSSAI2 and 3 from the Allowed NSSAI. The AMF70 may also set S-NSSAI2 associated with at least one of TA1 and TA2 as a Partially Allowed NSSAI. The AMF70 may also set S-NSSAI3 associated with at least TA4 as a Partially Rejected S-NSSAI in the RA. For example, if TAI1 identifies TA1 and TAI2 identifies TA2, S-NSSAI2 may be associated with at least one of TAI1 and TAI2. For example, if TAI4 identifies TA4, S-NSSAI3 may be associated with at least one of TAI4.

[0168] For example, in this disclosure, the AMF70 may set an S-NSSAI that the AMF70 is allowed to continue using for a UE3 within a particular TA to a Partially Allowed NSSAI, based on at least one of the received network slice information, the operator's policy, and the AMF70's local settings.

[0169] For example, in this disclosure, AMF70 may set an S-NSSAI that is permitted or available for use as a partial S-NSSAI in RA when UE3 performs a new Registration procedure for an S-NSSAI in a particular TA or performs a Registration procedure for an S-NSSAI again in a particular TA, based on at least one of the received network slice information, the operator's policy, and AMF70's local settings.

[0170] For example, suppose the RA includes TA1 through TA4, and the AMF70 sends an Allowed NSSAI including S-NSSAI1, 2, and 3 to the UE3, and the AMF70 stores the Allowed NSSAI. Also suppose the received restricted area is such that the network slice identified by S-NSSAI2 is restricted or unavailable by TA3 and TA4, and the network slice identified by S-NSSAI3 is restricted or unavailable by TA1 through TA3. In this case, the AMF70 may remove S-NSSAI2 and 3 from the Allowed NSSAI. The AMF70 may also set S-NSSAI2 associated with at least one of TA1 and TA2 as a Partially Allowed NSSAI. The AMF70 may also set S-NSSAI3 associated with at least TA4 as a Partially Rejected S-NSSAI in the RA. For example, if TAI1 identifies TA1 and TAI2 identifies TA2, S-NSSAI2 may be associated with at least one of TAI1 and TAI2. For example, if TAI4 identifies TA4, S-NSSAI3 may be associated with at least TAI4.

[0171] A received restricted area indicating that network slices identified by S-NSSAI are restricted or unavailable at a particular TA may indicate that network slices identified by S-NSSAI are permitted or available, except at the specific TA.

[0172] Furthermore, a received restricted area indicating that the network slice identified by S-NSSAI2 is restricted or unavailable in TA1 and TA2 may indicate that the network slice identified by S-NSSAI2 is permitted or available in TA3 and TA4.

[0173] For example, suppose the RA includes TA1 to TA4, and the AMF70 sends an Allowed NSSAI including S-NSSAI1, 2, and 3 to the UE3, and the AMF70 stores the Allowed NSSAI. Also suppose the received allow area indicates that the network slice identified by S-NSSAI1 is allowed or available in TA1 to TA4, the network slice identified by S-NSSAI2 is allowed or available in TA1 and TA2, and the network slice identified by S-NSSAI3 is allowed or available in TA4. In this case, the AMF70 may remove S-NSSAI2 and 3 from the Allowed NSSAI. The AMF70 may also set S-NSSAI2 associated with at least one of TA1 and TA2 as a Partially Allowed NSSAI. The AMF70 may also set S-NSSAI3 associated with at least TA4 as a Partially Rejected S-NSSAI in the RA. For example, if TAI1 identifies TA1 and TAI2 identifies TA2, S-NSSAI2 may be associated with at least one of TAI1 and TAI2. For example, if TAI4 identifies TA4, S-NSSAI3 may be associated with at least one of TAI4.

[0174] A received authorized area indicating that a network slice identified by S-NSSAI is permitted or available at a specific TA may indicate that the network slice identified by S-NSSAI is not permitted, restricted, or unavailable at any other TA.

[0175] Received authorized areas indicating that network slices identified by S-NSSAI2 are permitted or available in TA1 and TA2 may indicate in TA3 and TA4 that network slices identified by S-NSSAI2 are not permitted, restricted, or unavailable.

[0176] For example, if the received available time is from 9:00 AM to 5:00 PM, and the current time is from 9:00 AM to 5:00 PM, AMF70 may consider at least one of the received congestion levels, restricted areas, and permitted areas. For example, if the current time is from 9:00 AM to 5:00 PM, AMF70 may perform the above processing to decide on updating the Allowed NSSAI and set the S-NSSAI to at least one of the Partially Allowed NSSAI and Partially Rejected S-NSSAI.

[0177] For example, suppose the RA includes TA1 through TA4, and the AMF70 sends an Allowed NSSAI including S-NSSAI1, 2, and 3 to the UE3, and the AMF70 stores the Allowed NSSAI. Also suppose the received availability information indicates that the network slice identified by S-NSSAI1 is allowed or available in TA1 through TA4 from 9am to 5pm, the network slice identified by S-NSSAI2 is allowed or available in TA1 and TA2 from 9am to 5pm, and the network slice identified by S-NSSAI3 is allowed or available in TA4 from 9am to 5pm. In this case, the AMF70 may remove S-NSSAI2 and 3 from the Allowed NSSAI as long as the current time is between 9am and 5pm. The AMF70 may also set S-NSSAI2 associated with at least one of TA1 and TA2 as a Partially Allowed NSSAI. Furthermore, the AMF70 may set S-NSSAI3, which is associated with at least TA4, as a partially rejected S-NSSAI in the RA. For example, if TAI1 identifies TA1 and TAI2 identifies TA2, S-NSSAI2 may be associated with at least one of TAI1 and TAI2. For example, if TAI4 identifies TA4, S-NSSAI3 may be associated with at least TAI4.

[0178] For example, if the Allowed NSSAI sent to the UE3 by the AMF70 includes S-NSSAI1 through S-NSSAI4, and the above network slice information indicates that S-NSSAI4 is unavailable in the RA (i.e., S-NSSAI4 is unavailable in all TAs of the RA), the AMF70 may remove S-NSSAI4 from the Allowed NSSAI and set S-NSSAI4 as a Rejected NSSAI.

[0179] For example, AMF70 may determine at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI based on the information received from NWDAF74.

[0180] Step 4. If AMF70 determines in Step 3 that a UE configuration update is required, AMF70 sends a UE Configuration Update Command message to UE3 that includes an updated Allowed NSSAI, an updated Rejected NSSAI, an updated Partially Allowed NSSAI, an updated Partially Rejected S-NSSAI in the RA, and at least one of the other existing pieces of information.

[0181] For example, if AMF70 decides in step 3 to update Allowed NSSAI and Rejected NSSAI and decides to set S-NSSAI to at least one of Partially Allowed NSSAI and Partially Rejected S-NSSAI, AMF70 may send a UE Configuration Update Command message to UE3 that includes the updated Allowed NSSAI, the updated Rejected NSSAI, Partially Allowed NSSAI, and at least one of Partially Rejected S-NSSAI.

[0182] For example, AMF70 may send a UE Configuration Update Command message to UE3 that includes at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI, which were updated, generated, set, or configured in step 3.

[0183] For example, if AMF70 receives Partial Network Slice Availability support from UE3, AMF70 may send a UE Configuration Update Command message to UE3. See Step 1 in Figure 1 for a definition of Partial Network Slice Availability support indication.

[0184] Step 5. When UE3 receives a UE Configuration Update Command message from AMF70, it stores Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, Partially Rejected S-NSSAI in RA, and at least one of the other received information from Step 4. UE3 may store the received information in non-volatile memory within UE3.

[0185] Step 6. UE3 sends a UE Configuration Update Complete message to AMF70.

[0186] Modification 1 of the third example of the first embodiment: In step 3, AMF70 may decide to update the UE configuration of UE3 when the next registration procedure (e.g., the mobility registration procedure) is performed. In this case, the Partially Allowed NSSAI, Partially Rejected in RA, and other information that needs to be updated in UE3, as determined by AMF70 based on input from NWDAF74, will be reflected in step 7 of Figure 1.

[0187] For example, in step 7 of FIG. 1, the AMF 70 may determine the RA, Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within the RA based on the network slice information from the NWDAF 74 mentioned in step 2 of FIG. 3.

[0188] For example, in step 7 of FIG. 1, the AMF 70 may determine the RA, Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI within the RA based on at least one of the information from the NSSF 76 mentioned in step 6 of FIG. 1, the information from the PCF 73 mentioned in step 4 of FIG. 2, and the network slice information from the NWDAF 74 mentioned in step 2 of FIG. 3.

[0189] For example, the AMF 70 may consider the information received from the NWDAF 74 during the Registration procedure. For example, when the AMF 70 receives a Registration Request message from the UE 3 and the network slice information from the NWDAF 74 is available, the AMF 70 may perform the same procedure in step 3 of FIG. 3. Then, the AMF 70 may send a Registration Accept message including at least one of the Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Partially Rejected S-NSSAI updated, generated, set, or configured in step 3 of FIG. 3.

[0190] According to at least one of the third example of the first aspect and the modification of the third example, the above problem can be solved.

[0191] For example, at least one of the third example of the first aspect and the modification of the third example can solve the problem that there are some problems regarding the determination by the AMF based on the AMF local policy.

[0192] For example, at least one of the third example of the first aspect and the modification example of the third example can solve the problem that the above determination based on the AMF local policy can only be made by the AMF alone, which may impose unnecessary restrictions on the 5G system.

[0193] For example, according to at least one of the third example of the first aspect and the modification example of the third example, the NWDAF 74 can transmit information for determining at least one of the Partially Allowed NSSAI and the partially Rejected S-NSSAI within the RA. Therefore, the above problem can be solved.

[0194] For example, the Disclosure includes a process for determining at least one of the Partially Allowed NSSAIs and Partially Rejected S-NSSAIs within the RA. For example, if one node of the Disclosure determines at least one of the Partially Allowed NSSAIs and Partially Rejected S-NSSAIs within the RA, that node may use a process performed by other nodes to determine at least one of the Partially Allowed NSSAIs and Partially Rejected S-NSSAIs within the RA. For example, one node may store information used by other nodes to determine at least one of the Partially Allowed NSSAIs and Partially Rejected S-NSSAIs within the RA. For example, NSSF76 in Figure 1 may store information used by PCF73 in Figure 2 to determine at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI in the RA, and based on that information, may determine at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI in the RA, similar to PCF73 in Figure 2. For example, the information may be provided to NSSF76 in advance (for example, NSSF76 may store the information beforehand). For example, NSSF76 may receive the information beforehand from other communication devices (including, for example, PCF73).

[0195] System Overview Figure 4 schematically shows a telecommunications system 1 for mobile (cellular or wireless) to which the above embodiments can be applied.

[0196] Telecommunication system 1 represents a system overview that enables end-to-end communication. For example, UE3 (or user equipment, "mobile device" 3) communicates with other UE3 or service servers in the data network 20 via their respective (R)AN nodes 5 and core network 7.

[0197] (R)AN Node 5 supports any radio access, including non-3GPP RATs, such as 5G radio access technology (RAT), E-UTRA radio access technology, beyond 5G RAT, 6G RAT, and wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0198] (R)AN node 5 can be divided into Radio Unit (RU), Distributed Unit (DU), and Centralized Unit (CU). In some embodiments, each unit can be connected to one another, and (R)AN node 5 can be constructed by adopting an architecture defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.

[0199] (R)AN node 5 can be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions can be allocated to handle communications. In some embodiments, user traffic can be distributed across multiple user plane functions, and the user traffic on each user plane function is aggregated at both UE3 and (R)AN node 5. This divided architecture can be called "dual connectivity" or "multi-connectivity".

[0200] (R)AN node 5 can also support communications using satellite access. In some embodiments, (R)AN node 5 can support both satellite and ground access.

[0201] Furthermore, (R)AN node 5 can also be called an access node for non-wireless access. Non-wireless access includes fixed-line access as defined by the Broadband Forum (BBF), as well as optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0202] The core network 7 may include logical nodes (or "functions") to support communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes control plane functions and user plane functions, among other functions. Each function within a logical node can be considered a network function. Network functions can be provided to other nodes by adapting a Service Based Architecture (SBA).

[0203] Network functions can be deployed as distributed, redundant, stateless, and scalable services delivered from several locations and several execution instances at each location, by adapting network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV). Core Network 7 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0204] As is well known, UE3 can enter and exit the area (i.e., radio cell) served by (R)AN node 5 when UE3 is moving within the geographic area covered by telecommunications system 1. To track UE3 and facilitate movement between different (R)AN node 5, the core network 7 includes at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME), a mobility management node for Beyond 5G, or a mobility management node for 6G may be used instead of the AMF 70.

[0205] The core network 7 also includes, among other things, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Data Analytics Function (NWDAF) 74, a Unified Data Management (UDM) 75, and a Network Slice Selection Function (NSSF) 76. When UE3 is roaming to the visited Public Land Mobile Network (VPLMN), UE3's home Public Land Mobile Network (HPLMN) provides the roaming UE3 with the UDM 75, as well as at least some of the functions of SMF 71, UPF 72, and PCF 73.

[0206] UE3 and each Serving(R)AN node 5 are connected via appropriate air interfaces (e.g., so-called "Uu" interfaces). Adjacent (R)AN nodes 5 are connected to each other via appropriate (R)AN nodes 5 to (R)AN node interfaces (e.g., so-called "Xn" interfaces). Each (R)AN node 5 is also connected to nodes in the core network 7 (so-called core network nodes, etc.) via appropriate interfaces (e.g., so-called "N2" / "N3" interfaces). The core network 7 also provides connectivity to the data network 20. The data network 20 can be the internet, a public network, an external network, a private network, or an internal network of the PLMN. If the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the data network 20 can provide IP Multimedia Subsystem (IMS) services. UE3 can connect to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types. The data network may contain Application Function (AF) 201.

[0207] The "Uu" interface may include the Control plane of the Uu interface and the User plane of the Uu interface.

[0208] The User plane of the Uu interface is responsible for transmitting user traffic between UE3 and Serving(R)AN node 5. The User plane of the Uu interface can have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers via physical connections.

[0209] The Control Plane of the Uu interface is responsible for establishing, changing, and releasing the connection between UE3 and the serving (R)AN node 5. The Control Plane of the Uu interface can have a hierarchical structure with the RRC, PDCP, RLC, and MAC sublayers via a physical connection.

[0210] For example, to support AS signaling, the following messages are communicated via the RRC layer. · RRC Setup Request message: This message is sent from UE3 to the (R)AN node 5. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters can be included together in the RRC Setup Request message. > establishmentCause, and ue-Identity. ue-Identity can have a value of ng-5G-S-TMSI-Part1, or randomValue. · RRC Setup message: This message is sent from the (R)AN node 5 to UE3. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters can be included together in the RRC Setup message. > masterCellGroup, and radioBearerConfig. · RRC Setup Complete message: This message is sent from UE3 to the (R)AN node 5. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters can be included together in the RRC Setup Complete message. > guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0211] The UE3 and AMF70 are connected via an appropriate interface (e.g., the so-called N1 interface). The N1 interface is responsible for providing communication between the UE3 and AMF70 in order to support NAS signaling. The N1 interface can be established via 3GPP access and non-3GPP access. For example, the following messages are communicated via the N1 interface. • Registration request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the registration request message: >5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters. • Registration Acceptance Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this form, the following parameters may be included in the registration acceptance message. >5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI. • Registration Complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Registration Complete message. SOR transparent container. • Authentication Request message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Request message. >ngKSI, ABBA, Authentication parameter RAND(5G authentication challenge), Authentication parameter AUTN(5G authentication challenge), and EAP message. • Authentication Response message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Response message. >Authentication response message identity, Authentication response parameter and EAP message. • Authentication Result message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Result message. >ngKSI, EAP messages, and ABBA. • Authentication Failure message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Failure message. Authentication failure message identifier, 5GMM cause, and Authentication failure parameters. • Authentication Reject message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Reject message. >EAP message. • Service Request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Request message. >ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. • Service Accept message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Accept message: >PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value. • Service Reject message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Reject message. >5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list. • Configuration Update Command message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Configuration Update Command message. >Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI. • Configuration Update Complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Configuration Update Complete message. >Configuration update complete message identity.

[0212] User Equipment (UE) Figure 5 is a block diagram showing the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31 that can operate to send and receive signals with nodes connected via one or more antennas 32. UE3 may also include a user interface 34 for inputting and outputting information to and from the outside. Although not necessarily shown in Figure 5, UE3 can have all the usual functions of a conventional mobile device, which can be provided by any one or any combination of hardware, software, and firmware, as needed. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of UE3 according to the software stored in memory 36. The software includes, among other things, an operating system 361, as well as a communication control module 362 having at least one transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for signaling between the UE3 and other nodes, such as (R)AN node 5 and AMF70, and for processing (generating / transmitting / receiving) uplink / downlink data packets. Such signaling may include, for example, appropriately formatted signaling messages relating to access and mobility management procedures (for the UE3) (e.g., registration request messages and associated response messages). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. If multiple USIMs 35 are installed, the controller 33 may enable only one USIM 35 or multiple USIMs 35 simultaneously.

[0213] UE3 can support, for example, Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0214] UE3 can be, for example, items of equipment for production or manufacturing, and / or items of energy-related machinery (e.g., boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power generators, batteries, nuclear systems and / or related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or their application systems, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machines, printing and / or related machinery, paperwork machinery, chemical machinery, mining and / or construction machinery and / or related equipment, machinery and / or equipment for agriculture, forestry and / or fisheries, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the aforementioned equipment or machinery).

[0215] UE3 can be, for example, a transport equipment item (e.g., transport equipment such as railway cars, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other vessels, aircraft, rockets, satellites, drones, balloons, etc.). UE3 can be, for example, an item of information and communication equipment (e.g., electronic computers and related equipment, communication and related equipment, electronic components and other information and communication equipment).

[0216] UE3 can be, for example, refrigerators, refrigerator applications, merchandise and / or service industry equipment items, vending machines, automated service machines, office equipment, consumer electronics and electronic devices (e.g., audio equipment, video equipment, speakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners and other consumer electronic devices).

[0217] UE3 can be, for example, an electrical application system or device (such as an X-ray system, particle accelerator, radioisotope device, sound wave device, electromagnetic application device, power application device, etc.).

[0218] UE3 can include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or surveying or sensing equipment (e.g., smoke detectors, motion sensors, wireless tags, etc.), wristwatches or clocks, inspection equipment, optical devices, medical equipment and / or systems, weapons, cutlery products, hand tools, etc.

[0219] UE3 can be, for example, a wireless-equipped personal digital assistant, or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device, such as a personal computer or electrical measuring instrument). UE3 can be part of a device or system that provides applications, services, and solutions related to the Internet of Things (IoT), as described below, using various wired and / or wireless communication technologies.

[0220] Internet of Things devices (or "things") can be equipped with appropriate electronics, software, sensors, network connectivity, etc., which enable them to collect and exchange data with each other and with other communication devices. IoT devices can comprise automated equipment that follows software instructions stored in internal memory. IoT devices can operate without requiring human monitoring or interaction with humans. IoT devices can also remain stationary and / or inactive for extended periods. IoT devices can be implemented as part of (generally) stationary equipment. IoT devices can also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people to be monitored / tracked. IoT technology can be understood as being implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0221] IoT devices are sometimes referred to as Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band-IoT UEs (NB-IoT UEs). UE3 is understood to support one or more IoT or MTC applications.

[0222] UE3 can be a smartphone or a wearable device (e.g., smart glasses, smartwatch, smart ring, or hearable device).

[0223] UE3 can be an automobile, connected car, autonomous vehicle, vehicle device, motorcycle, or Vehicle to Everything (V2X) communication module (e.g., vehicle-to-vehicle communication module, vehicle-to-infrastructure communication module, vehicle-to-pedestrian communication module, and vehicle-to-network communication module).

[0224] (R)AN node Figure 6 is a block diagram showing the main components of an exemplary (R)AN node 5, for example, a base station (an "eNB" in LTE, a "gNB" in 5G, a 5G Beyond base station, or a 6G base station). As shown in the figure, the (R)AN node 5 includes a transceiver circuit 51 that can operate to send and receive signals with a connected UE3 via one or more antennas 52, and to send and receive signals with other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 according to software stored in memory 55. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551, and a communication control module 552 having at least a transceiver control module 5521.

[0225] The communication control module 552 (using its transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between (R)AN node 5 and other nodes, e.g., UE3, another (R)AN node 5, AMF70, UPF72, (for example, directly or indirectly). The signaling may include, for example, appropriately formatted signaling messages related to radio connectivity and connectivity with the core network 7 (for a particular UE3), particularly connectivity establishment and maintenance (e.g., RRC connectivity establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages from the N2 reference point), and Xn application protocol (XnAP) messages (i.e., messages from the Xn reference point). Such signaling may also include, for example, broadcast information in the transmission case (e.g., master information and system information). The controller 54, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0226] (R) AN node 5 can support Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). (R)AN node 5 can be represented as RAN node, RAN, (R)AN, etc.

[0227] System Overview of (R)AN Node 5 Based on O-RAN Architecture Figure 7 schematically shows an (R)AN node 5 based on an O-RAN architecture to which the configuration of (R)AN node 5 can be applied.

[0228] The (R)AN node 5, based on the O-RAN architecture, represents a system overview in which the (R)AN node is divided into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Centralized Unit (CU) 62. In some embodiments, each unit can be combined. For example, RU 60 can be combined with DU 61 as an integration / combination unit, and DU 61 can be combined with CU 62 as another integration / combination unit. Any function described in the unit description (e.g., one of RU 60, DU 61, and CU 62) can be implemented in the above integration / combination units. Furthermore, CU 62 can be separated into two functional units, such as a CU Control plane (CP) and a CU User plane (UP). The CU CP has control plane functionality in the (R)AN node 5. The CU UP has user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface).

[0229] Each UE3 and each serving RU60 is connected via an appropriate air interface (e.g., the so-called "Uu" interface). Each RU60 is connected to a DU61 via an appropriate interface (e.g., the so-called "Front haul", "Open Front haul", or "F1" interface). Each DU61 is connected to a CU62 via an appropriate interface (e.g., the so-called "Mid haul", "Open Mid haul", or "E2" interface). Each CU62 is also connected to a node in the core network 7 (e.g., the so-called core network node) via an appropriate interface (e.g., the so-called "Back haul", "Open Back haul", or "N2" / "N3" interfaces). Furthermore, the user plane portion of the DU61 can also be connected to the core network node 7 via the appropriate interface "N3".

[0230] Depending on the functions divided among RU60, DU61, and CU62, each unit provides a portion of the functions provided by (R)AN node 5. For example, RU60 can provide the function for communicating with UE3 via the air interface, DU61 can provide the function for the MAC and RLC layers, and CU62 can provide the function for the PDCP, SDAP, and RRC layers.

[0231] Radio Unit (RU) Figure 8 is a block diagram showing the main components of the RU portion of an exemplary RU60, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the RU60 includes a transceiver circuit 601 that can operate to send and receive signals with a connected UE3 via one or more antennas 602, and to send and receive signals with other network nodes or network units (directly or indirectly) via a network interface 603. The controller 604 controls the operation of the RU60 according to software stored in memory 605. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051, and a communication control module 6052 having at least a transceiver control module 60521.

[0232] The communication control module 6052 (using its transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between RU60 and other nodes or units, such as UE3, another RU60, and DU61, (for example, directly or indirectly). This signaling may include appropriately formatted signaling messages, for example, regarding the radio connection (for a particular UE3) and the connection with RU60, particularly the MAC and RLC layers.

[0233] The controller 604, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0234] The RU60 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0235] As described above, RU60 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the RU60 description can be implemented in the above integration / coupling unit.

[0236] Distributed Unit (DU) Figure 9 is a block diagram showing the main components of the DU portion of an exemplary DU61, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the device includes a transceiver circuit 611 that can operate to send and receive signals with other nodes or units (including RU60) via a network interface 612. A controller 613 controls the operation of the DU61 according to software stored in memory 614. The software can be pre-installed in memory 614 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141, and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for processing (generating / transmitting / receiving) signaling between the DU61 and other nodes or units, such as RU60, other nodes and units.

[0237] The DU61 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0238] As described above, RU60 can be integrated / coupled with DU61 or CU62 as an integration / coupling unit. Any function described in the DU61 description can be implemented in one of the above integration / coupling units.

[0239] Centralized Unit (CU) Figure 10 is a block diagram showing the main components of the CU portion of an exemplary CU62, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the device includes a transceiver circuit 621 that can operate to send and receive signals with other nodes or units (including DU61) via a network interface 622. A controller 623 controls the operation of the CU62 according to software stored in memory 624. The software can be pre-installed in memory 624 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241, and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for processing (generating / transmitting / receiving) signaling between the CU62 and other nodes or units, such as DU61, other nodes and units.

[0240] CU62 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0241] As described above, CU62 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the CU62 description can be implemented in the above integration / coupling unit.

[0242] AMF Figure 11 is a block diagram illustrating the main components of the AMF70. As shown, the device includes a transceiver circuit 701 that can operate to send and receive signals with other nodes (including UE3 and NSSF76) via a network interface 702. A controller 703 controls the operation of the AMF70 according to software stored in memory 704. The software can be pre-installed in memory 704 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041, and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 (using its transceiver control module 70421) is responsible for processing (generating / transmitting / receiving) signaling between the AMF70 and other nodes, for example, UE3 (via (R)AN node 5) and other core network nodes (including the core network node in UE3's HPLMN when UE3 is roaming in). Such signaling could include, for example, well-formatted signaling messages relating to access and mobility management procedures (for UE3) (e.g., registration request messages and associated response messages).

[0243] The AMF70 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0244] PCF Figure 12 is a block diagram showing the main components of the PCF73. As shown, the device includes a transceiver circuit 731 that can operate to send and receive signals with other nodes (including the AMF70) via a network interface 732. The controller 733 controls the operation of the PCF73 according to software stored in memory 734. The software can be pre-installed in memory 734 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., removable memory device (RMD)). The software includes, among other things, an operating system 7341, and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for processing (generating / transmitting / receiving) signaling between the PCF73 and other nodes, such as the AMF70, and other core network nodes (including the core network within the HPLMN of the UE3 when the UE3 is roaming). Such signaling could include, for example, well-formatted signaling messages regarding policy management procedures (for UE3), such as HTTP restful methods based on service-based interfaces.

[0245] PCF73 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0246] NWDAF Figure 13 is a block diagram showing the main components of the NWDAF74. As shown, the device includes a transceiver circuit 741 that can operate to send and receive signals with other nodes (including AMF70 and UDM75) via a network interface 742. A controller 743 controls the operation of the NWDAF74 according to software stored in memory 744. The software can be pre-installed in memory 744 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., removable memory device (RMD)). The software includes, among other things, an operating system 7441, and a communication control module 7442 having at least a transceiver control module 74421. The communication control module 7442 (using its transceiver control module 74421) is responsible for processing (generating / transmitting / receiving) signaling between the NWDAF74 and other nodes, such as AMF70, and other core network nodes (including the core network nodes in the HPLMN of UE3 when UE3 is roaming). Such signaling could include, for example, well-formatted signaling messages regarding policy management procedures (for UE3), such as HTTP restful methods based on service-based interfaces.

[0247] The NWDAF74 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0248] UDM Figure 14 is a block diagram showing the main components of the UDM75. As shown, the device includes a transceiver circuit 751 that can operate to send and receive signals with other nodes (including the AMF70) via a network interface 752. A controller 753 controls the operation of the UDM75 according to software stored in memory 754. The software can be pre-installed in memory 754 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541, and a communication control module 7542 having at least a transceiver control module 75421. The communication control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / transmitting / receiving) signaling between the UDM75 and other nodes, such as the AMF70 and other core network nodes (including the core network nodes in the VPLMN of the UE3 when the UE3 is roaming). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to mobility management procedures (for UE3).

[0249] The UDM75 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0250] NSSF Figure 15 is a block diagram showing the main components of NSSF76. As shown, the device includes a transceiver circuit 761 that can operate to send and receive signals with other nodes (AMF70) via a network interface 762. A controller 763 controls the operation of NSSF76 according to software stored in memory 764. The software can be pre-installed in memory 764 and / or downloaded, for example, via a telecommunications network or from a removable storage device (RMD). The software includes, among other things, an operating system 7641, and a communication control module 7642 having at least a transceiver control module 76421. The communication control module 7642 (using its transceiver control module 76421) is responsible for processing (generating / transmitting / receiving) signaling between NSSF76 and other nodes, such as AMF70, and other core network nodes (including the core network node in the VPLMN of UE3 when UE3 is roaming out). Such signaling could include, for example, well-formatted signaling messages regarding mobility management procedures (for UE3), such as HTTP restful methods based on service-based interfaces.

[0251] NSSF76 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0252] Figure 16 shows registration by the AMF reassignment procedure. The exemplary embodiments disclosed above, in whole or in part, may be described as follows, but are not limited thereto.

[0253] 4.2.2.2.3 Registration via AMF reassignment When an AMF receives a registration request, for example, if the initial AMF is not suitable for servicing the UE, the AMF may need to reroute the registration request to another AMF. The registration procedure using the AMF reassignment procedure described in Figure 4.2.2.2.3-1 is used to reroute the UE's NAS messages to the target AMF during the registration procedure.

[0254] The initial AMF and target AMF register their functions in the NRF.

[0255] 1. If the UE is in the CM-IDLE state, steps 1 and 2 of figure 4.2.2.2.2-1 occur, and (R)AN sends the registration request message in the initial UE message to the initial AMF. If the UE is in the CM-CONNECTED state and triggers the registration procedure, NG-RAN sends the registration request message in the uplink NAS transport message to the serving AMF, which is the initial AMF. The AMF may skip steps 2-3.

[0256] 2. If AMF requires subscription information from the SUPI or UE to determine whether to reroute the registration request, or if the registration request was not sent with integrity protection, or if integrity protection is indicated as a failure, AMF performs steps 4 through 9a or 9b of figure 4.2.2.2.2-1.

[0257] 3a. [Conditional] If the initial AMF requires the UE's subscription information to determine whether to reroute the registration request, and the UE's slice selection subscription information was not provided by the old AMF, the AMF selects the UDM as described in Section 6.3.8.3 TS23.501[2].

[0258] 3b. Get UDM:Nudm_SDM_Get (SUPI, Slice Selection Subscription data) from the initial AMF.

[0259] The initial AMF requests the UE's slice selection subscription data from the UDM by calling the Nudm_SDM_Get service operation (see Section 5.2.3.3.1). The UDM can retrieve this information from the UDM using Nudr_DM_Query(SUPI, Slice Selection Subscription data).

[0260] In the case of disaster roaming registration, AMF can provide UDM with information regarding the disaster roaming service.

[0261] 3c.UDM's response to the initial AMF:Nudm_SDM_Get. AMF retrieves slice selection subscription data, including Subscribed S-NSSAI.

[0262] The UDM responds to the initial AMF with slice selection subscription data.

[0263] For disaster roaming registration, based on the local policy and / or local settings specified in Section 5.50.4 of 3TS 23,501[2], the UDM responds to the initial AMF with slice selection subscription data for disaster roaming services.

[0264] 4a. [Conditional] From the initial AMF, NSSF:Nnssf_NSSelection_Get(Requested NSSAI,[Mapping Of Requested NSSAI],Subscribed S-NSSAI with the default S-NSSAI indication,[NSSRG Information],TAI, Allowed NSSAI for the other access type (if any),[Mapping of Allowed NSSAI], SUPI's PLMN ID, Partial Network Slice Availability support indication).

[0265] If slice selection is necessary (see section 5.15.5.2.1 of 3TS 23.501[2]), for example, if the initial AMF cannot process all S-NSSAI from the Requested NSSAI permitted by the subscription information, the initial AMF calls the Nnssf_NSSelection_Get service operation from the NSSF by including the Requested NSSAI, optionally the Mapping of Requested NSSAI, the Subscribed S-NSSAI with the default S-NSSAI instruction, [NSSRG Information], Allowed NSSAI of other access types (if any), the Mapping of Allowed NSSAI, the PLMN ID of the SUPI, and the TAI of the UE. The Partial Network Slice Availability support indication tells the NSSF that the UE supports processing partially allowed or partially denied NSSAI. The AMF includes, if available, NSSRG information for HPLMN S-NSSAI as defined in Section 5.15.12 of 3TS 23.501, including information on whether the UE has instructed support for subscription-based limits on concurrent enrollment of network slices and whether the UDM has instructed that all subscribed S-NSSAI be provided to UEs that do not support it.

[0266] 4b. [Conditional] Response from NSSF to initial AMF: Nnssf_NSSelection_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], partially allowed NSSAI of the first access type and associated TAs of each S-NSSAI present in the partially allowed NSSAI or partially rejected NSSAI and for each S-NSSAI in the partially rejected NSSAI the list of TA supporting the S-NSSAI).

[0267] The NSSF performs the steps specified in point (B) of section 5.15.5.2.1 of 3TS 23.501[2]. The NSSF returns to the initial AMF a list of candidate AMFs based on the Allowed NSSAI for the first access type, optional Mapping of Allowed NSSAI, Allowed NSSAI for the second access type (if any), optional Mapping of Allowed NSSAI, and the target AMF set, or configuration. The NSSF may return the NSI ID associated with the network slice instance corresponding to a particular S-NSSAI. The NSSF may return the NRF used to select NF / services within the selected network slice instance. It may also return information about the reasons for denial of S-NSSAIs that are not included in the allowed NSSAIs. The NSSF may return the configured NSSAIs of the Serving PLMN and, if applicable, the associated mappings of the configured NSSAIs. If NSSRG information is included in the request, NSSF provides a configured NSSAI as described in section 5.15.12 of 3TS 23.501[2].

[0268] If AMF receives a Partial Network Slice Availability support indication and none of the S-NSSAIs of the Requested NSSAI are supported in the registered area, AMF will send the S-NSSAI of the partially permitted NSSAI and the associated TA of the S-NSSAI to AMF.

[0269] NOTE: For each S-NSSAI of a Partially Allowed NSSAI, the NSSF obtains a list of supported TAIs from the UDM in an existing or new message, or from the AMF in an existing or new message.

[0270] NOTE1: The NRF returned by the NSSF (if any) belongs to any level of NRF (see Section 6.2.6 of 3TS 23.501[2]) according to the operator's deployment decision.

[0271] 5. [Conditional] Older AMF from initial AMF: Namf_Communication_RegistrationStatusUpdate (cause of failure).

[0272] If the UE is in CM-IDLE and another AMF is selected, the initial AMF sends a rejection notice to the old AMF indicating that the UE registration procedure was not fully completed in the initial AMF. The old AMF then proceeds as if Namf_Communication_UEContextTransfer had not been received.

[0273] 6a. From the initial AMF, NRF: Nnrf_NFDiscovery_Request (NF type, AMF Set).

[0274] If the initial AMF does not have the target AMF address stored locally, and the initial AMF needs to use direct rerouting to the target AMF, or include the AMF address in rerouting via (NG-R)AN messages, the initial AMF calls the Nnrf_NFDiscovery_Request service operation from the NRF to find a suitable target AMF with the necessary NF capabilities to serve the UE. The NF type is set to AMF. The AMF set is included in Nnrf_NFDiscovery_Request.

[0275] 6b. Response from a "conditional" NRF to AMF:Nnrf_NFDiscovery_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)).

[0276] The NRF responds with a list of potential target AMFs. The NRF can also provide details of the services offered by the candidate AMFs, along with notification endpoints for each type of notification service registered with the NRF by the selected AMF, if available. Alternatively, it provides a list of potential target AMFs and their functionalities, along with additional selection rules as needed. Based on the registered NFs and requested functionalities, the target AMFs are selected by the initial AMF.

[0277] If a security association has been established between the UE and the initial AMF, the initial AMF performs step 7(A) to forward the NAS message to the target AMF in order to avoid registration failure.

[0278] NOTE2: When the initial AMF forwards NAS messages to the target AMF via (R)AN, the security context of the initial AMF is not forwarded to the target AMF. In this case, the UE rejects NAS messages sent from the target AMF because the security contexts of the UE and the target AMF are not synchronized.

[0279] NOTE3: If AMF reassignment is performed in step 7(A), network slice isolation will not be fully maintained.

[0280] If the initial AMF is not part of the target AMF set and a list of candidate AMFs cannot be obtained by querying the NRF using the target AMF set (for example, if a locally pre-configured NRF on the AMF does not provide the requested information, if a query to a suitable NRF provided by the NSSF is unsuccessful, or if the initial AMF is aware that it is not authorized as an AMF to provide services), the initial AMF will perform step 7(B) to forward the NAS message to the target AMF via (R)AN, unless a security association has been established between the UE and the initial AMF. Allowed NSSAI and AMF sets are included to allow (R)AN to select a target AMF, as described in section 6.3.5 of 3TS 23.501[2].

[0281] 7(A). If the initial AMF decides to forward the NAS message directly to the target AMF based on local policy and subscription information, the initial AMF calls Namf_Communication_N1MessageNotify to the target AMF to transmit the rerouted NAS message. The Namf_Communication_N1MessageNotify service operation includes AN access information (e.g., information that enables the (R)AN to identify the N2 termination point, the CAG identifier of the CAG cell), the complete Registration Request message in cleartext as specified in TS33.501

[15] , and the UE's SUPI and MM context, if available. If the initial AMF has obtained information from the NSSF as described in step 4b, it includes that information, except for the AMF set or a list of AMF addresses. The target AMF updates the (R)AN with the UE's new updated N2 termination point in the first message from the target AMF to the RAN in step 8.

[0282] 7(B).[Conditional]If the UE is in CM-IDLE, and the initial AMF decides, based on local policy and subscription information, to forward the NAS message to the target AMF via (R)AN unless the target AMF is returned from NSSF and identified by the list of candidate AMFs, the initial AMF sends an NGAP Reroute NAS Request message to (R)AN (step 7a). The NGAP Reroute Request NAS message contains information about the target AMF and the complete Registration Request message. If the initial AMF has obtained information as described in step 4b, that information is included. (R)AN sends an initial UE message to the target AMF indicating rerouting by slicing, containing the information from step 4b provided by NSSF (step 7b).

[0283] NOTE4: If the UE is CM-CONNECTED, i.e., if the NGAP Uplink NAS Transport was received in step 1, step 7B is not supported.

[0284] 8. After receiving the Registration Request message sent in step 7(A)a or step 7(B)b, the target AMF continues the registration procedure from steps 4 to 22 of figure 4.2.2.2.2-1, including the UE context obtained from the old AMF (the target AMF corresponds to the new AMF). If a 5G security context is received from the initial AMF, the target AMF continues to use that context instead of any 5G security context that the target AMF could obtain from the old AMF. If the initial AMF decides to forward the NAS message to the target AMF (step 7(A)), the first message from the target AMF to (R)AN (Initial Context Setup Request or Downlink NAS Transport) includes the name of the initial AMF and the target AMF UE NGAP ID.

[0285] 5.2.16.2.1 Nnssf_NSSelection_Get service operation Service operation name: Nnssf_NSSelection_Get Description: This service operation enables network slice selection in both the Serving PLMN and HPLMN. It also allows the NSSF to provide the AMF with the Allowed NSSAI and Configured NSSAI for the Serving PLMN. It can also provide applicable NSAG information (section 5.15.14 of 3TS 23.501[2]).

[0286] This may be called during the registration procedure, the inter-PLMN mobility procedure, the PDU session establishment procedure, or the UE configuration update procedure. When called during the registration procedure, it may trigger an AMF reassignment. When called during the PDU session establishment procedure, it may be called in the VPLMN or HPLMN. When called in the VPLMN, it returns the hNRF selected by the hNSSF and, if applicable, the HPLMN NSI ID value. When called during the UE configuration update procedure or the inter-PLMN mobility procedure, it may be called in the serving PLMN.

[0287] NOTE1: The list of events that trigger the Nnssf_NSSelection_Get service operation call is not complete. NOTE2: NSSF can identify the serving network and access type from the TAI, as described in TS29.571

[70] .

[0288] Required input: None.

[0289] Input, conditionally required: If this service operation is invoked during the registration procedure for network slice selection or the UE configuration update procedure, the following input will be required: -Subscribed S-NSSAI if marked as the default S-NSSAI, PLMN ID of SUPI, TAI, NF type of NF service consumer, requester ID. If this service operation is called to derive the S-NSSAI of the serving PLMN (as described in Section 4.11.1.3.3), the following input is required: - S-NSSAI of HPLMN associated with the established PDN connection, PLMN ID of SUPI, NF type of NF service consumer, requester ID. If this service operation is invoked by the target AMF during a PLMN-to-PLMN mobility procedure, the following input is required: -HPLMN's S-NSSAI, SUPI's PLMN ID, TAI. If this service operation is called during the PDN Connection Establishment of the EPS serving PLMN by SMF+PGW-C, the following input is required: -UE's Subscribed S-NSSAI, SUPI's PLMN ID, NF service consumer's NF type, requester ID. If this service operation is called during the PDU Session Establishment procedure of a serving PLMN, the following input is required: -S-NSSAI, Non-Roaming / LBO Roaming / HR Roaming indication, SUPI PLMN ID, TAI, NF Service Consumer NF Type, Requester ID.

[0290] Input, options: If this service operation is invoked during a registration procedure for network slice selection or UE configuration update procedures, the following inputs are provided, if available: -UE support for subscription-based limits on simultaneous registration of Requested NSSAI, Requested NSSAI mapping, Default Configured NSSAI Indication, NSSRG information, display of network slice functionality, UDM display that provides all subscribed S-NSSAI for UEs that do not show support for subscription-based limits on simultaneous registration of network slices, Allowed NSSAI for the current access type, Allowed NSSAI for other access types, and corresponding mappings of Allowed NSSAI for the current access type and other access types, RA's Rejected S-NSSAI, NSAG information. If this service operation is invoked during the PDU session establishment procedure, the following input is optional. - HPLMN S-NSSAI that maps from Allowed NSSAI to S-NSSAI for Serving PLMN. When AMF obtains Partial Network Slice Availability support from the UE, AMF sends this information to NSSF.

[0291] Output, conditionally required: If this service operation is invoked during a registration procedure for network slice selection or UE configuration update procedures, one or more of the following outputs are requested: - Allowed NSSAI, Configured NSSAI, Target AMF set, or (based on configuration) a list of candidate AMFs. If this service operation is invoked during a PLMN-to-PLMN mobility procedure, one or more of the following outputs are requested: - Allowed NSSAI. If this service operation is called to derive the S-NSSAI of the serving PLMN (as described in Section 4.11.1.3.3), the following output is required: - Mapping of S-NSSAI for HPLMN associated with established PDN connections and S-NSSAI associated with PDN connections established in Serving PLMN. If this service operation is invoked by SMF+PGW-C while a PDN connection is being established in the EPS serving PLMN, the following output is required: - UE's Subscribed S-NSSAI, mapping of S-NSSAI associated with UE's subscribed S-NSSAI in the service PLMN. If this service operation is called during the PDU session establishment procedure, the following output is requested. - The NRF used to select NF / services within the selected network slice instance.

[0292] Output, conditional options: If this service operation is invoked during a UE registration procedure or a UE configuration update procedure, one or more of the following outputs are optional. -Mapping of Allowed NSSAIs, mapping of configured NSSAIs, NSI ID associated with the network slice instance of an Allowed NSSAI, NRF used to select NF / services within the selected network slice instance, and NRF used to identify a list of candidate AMFs from the AMF set, rejected S-NSSAIs and the reason for rejection, target NSSAI, NSAG information (as defined in section 5.15.14 of 3TS 23.501[2]).

[0293] If this service operation is invoked during a PLMN-to-PLMN mobility procedure, the following output is optional. -Mapping of Allowed NSSAI. If this service operation is called during the PDU session establishment procedure, the following output is optional. - The NSI ID associated with the S-NSSAI provided in the input. If the service operation is called during initial registration, mobility registration, PLMN-to-PLMN mobility, or EPS-to-5GS mobility, the following output is optional. - Partially Allowed NSSAI or partially rejected NSSAI; - A TAI associated with each S-NSSAI present in a partially permitted or partially denied NSSAI.

[0294] Variations and alternative examples Detailed embodiments have been described above. As those skilled in the art will understand, several modifications and substitutions can be made to the embodiments described above while still benefiting from the disclosure as embodied therein. Some of these substitutions and modifications are described here only as examples.

[0295] For the sake of clarity, the above description assumes that the UE3 and network device have several separate modules (such as a communications control module). These modules may be provided in this way in certain applications, for example, where an existing system is modified to implement the present disclosure. However, in other applications, such as systems designed from the outset with the features of the present invention in mind, these modules may be incorporated into the overall operating system or code, and therefore may not be identified as separate entities. These modules may also be implemented as software, hardware, firmware, or a combination thereof.

[0296] Each controller may include, but is not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (program and / or data), processing registers, communication buses (such as control buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, and any other suitable form of processing circuitry. In the above embodiments, several software modules have been described. As those skilled in the art will understand, software modules can be provided in compiled or uncompiled form and supplied to the UE3 and network devices as signals over a computer network or on a recording medium. Furthermore, some or all of the functions performed by this software can be performed using one or more dedicated hardware circuits. However, it is preferable to use software modules because it facilitates updating the UE3 and network devices to update those functions.

[0297] In the above embodiments, 3GPP wireless communication (wireless access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed-line communication technologies (e.g., BBF access, cable access, optical access, etc.) can also be used in accordance with the above embodiments.

[0298] The category of user devices may include, for example, mobile phones, smartphones, user devices, personal digital assistants, laptop / tablet computers, web browsers, e-readers, and other communication devices. Such mobile (or even more broadly, fixed) devices are typically operated by a user, but it is also possible to connect so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices to a network. For brevity, this application refers to mobile devices (or UEs) in the description, but it will be understood that the described technology can be implemented in any communication device (mobile and / or generally fixed) that can connect to a communication network to send and receive data, whether such communication devices are controlled by human input or by software instructions stored in memory. Various other modifications are obvious to those skilled in the art and will not be described in further detail here.

[0299] As those skilled in the art will understand, this disclosure can be embodied as a method and a system. Accordingly, this disclosure can take the form of entirely hardware embodiments, software embodiments, or embodiments combining software and hardware embodiments.

[0300] Each block in the block diagram can be understood as being implemented by computer program instructions. These computer program instructions can be provided to a processor in a general-purpose computer, a dedicated computer, or other programmable data processing device to manufacture a machine, thereby generating means for implementing the functions / operations specified in the flowchart and / or block diagram, through which the instructions executed via the computer or other programmable data processing device processor. The general-purpose processor may be a microprocessor, but instead, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, multiple microprocessors, one or more microprocessors, or any other such configuration.

[0301] The methods or algorithms described in relation to the embodiments disclosed herein can be directly embodied in hardware, in software modules executed by a processor, or in a combination of the two. The software module may be RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. The storage medium can be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor. The processor and storage medium may be located within an ASIC.

[0302] The preceding description of the disclosed embodiments is provided to enable those skilled in the art to implement or use the disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but rather to be given the broadest scope consistent with the principles and novel features disclosed herein.

[0303] This disclosure is illustrated and described in detail with reference to its exemplary embodiments, but is not limited to these embodiments. Those skilled in the art will understand that various modifications can be made to the form and details without departing from the spirit and scope of this disclosure as defined herein. For example, the embodiments described above are not limited to 5GS, and these embodiments can also be applied to communication systems other than 5GS (e.g., 6G systems, 5G Beyond systems). Note

[0304] The exemplary embodiments disclosed above, in whole or in part, may be described as follows, but are not limited to these:

[0305] (Note 1) A method for a first communication device, The second communication device receives at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI), A method for sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to user equipment (UE).

[0306] (Note 2) The method according to Appendix 1, wherein sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes sending a Registration Accept message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0307] (Note 3) moreover, The UE receives information indicating that it can understand at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, The method described in Appendix 1 or 2, which involves transmitting the aforementioned information to a second communication device.

[0308] (Note 4) The method according to Appendix 3, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI when transmitting the information to the second communication device.

[0309] (Note 5) Receiving the aforementioned information includes receiving a Registration Request message containing the aforementioned information, The method described in Appendix 3 or 4, wherein transmitting the aforementioned information includes transmitting an Nnssf_NSSelection_Get message containing the aforementioned information.

[0310] (Note 6) The method according to any one of the items in Appendix 1 to 5, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving an Nnssf_NSSelection_Get Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0311] (Note 7) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Network Slice Selection Function (NSSF) as described in any one of the items 1 to 6 of the appendix.

[0312] (Note 8) Receiving the aforementioned information includes receiving a Registration Request message containing the aforementioned information, The method described in Appendix 3 or 4, which includes transmitting the aforementioned information, and also includes transmitting an Npcf_AMPolicyControl_Create message containing the aforementioned information.

[0313] (Note 9) The method according to Appendices 1 to 4 and 8, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving an Npcf_AMPolicyControl_Create Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0314] (Note 10) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Policy Control Function (PCF) as described in Appendices 1 to 4, 8 and 9.

[0315] (Note 11) A method for a first communication device, Information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance (S-NSSAI) is received from a second communication device. Determine at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, A method for sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to user equipment (UE).

[0316] (Note 12) Receiving the aforementioned information includes receiving an Nnwdaf_SliceInformation notification message containing the aforementioned information. Sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI is the method described in Appendix 11, which includes sending a UE Configuration Update Command message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0317] (Note 13) The first communication device is an Access and Mobility Management Function (AMF), The method described in Appendix 11 or 12, wherein the second communication device is a Network Data Analytics Function (NWDAF).

[0318] (Note 14) A method for user equipment (UE), Information indicating that the UE can understand at least one of the Partially Allowed Network Slice Selection Assistance Information (NSSAI) and the Partially Rejected Single Network Slice Selection Assistance (S-NSSAI) is transmitted to the communication device. A method for transmitting the aforementioned information and receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI from the communication device.

[0319] (Note 15) Transmitting the aforementioned information includes sending a Registration Request message containing the aforementioned information. The method according to Appendix 14, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving a Registration Accept message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0320] (Note 16) The aforementioned communication device is an Access and Mobility Management Function (AMF) as described in Appendix 14 or 15.

[0321] (Note 17) A method for a first communication device, Information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance (S-NSSAI) is received from a second communication device. Determine at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, A method for transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to the second communication device.

[0322] (Note 18) Receiving the aforementioned information includes receiving an Nnssf_NSSelection_Get message containing the aforementioned information. The method as described in Appendix 17, wherein sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes sending an Nnssf_NSSelection_Get Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0323] (Note 19) The first communication device is a Network Slice Selection Function (NSSF), The second communication device is an Access and Mobility Management Function (AMF) as described in Appendix 17 or 18.

[0324] (Note 20) Receiving the aforementioned information includes receiving an Npcf_AMPolicyControl_Create message containing the aforementioned information. The method as described in Appendix 17, wherein sending at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes sending an Npcf_AMPolicyControl_Create response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0325] (Note 21) The aforementioned first communication device is a Policy Control Function (PCF), The second communication device is an Access and Mobility Management Function (AMF) as described in Appendix 17 or 20.

[0326] (Note 22) A first communication device, Means for receiving at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, A first communication device comprising means for transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to user equipment (UE).

[0327] (Note 23) The first communication device as described in Appendix 22, wherein transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes transmitting a Registration Accept message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0328] (Note 24) Means for receiving information indicating that the UE can understand at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, The first communication device as described in Appendix 22 or 23, further comprising means for transmitting the aforementioned information to a second communication device.

[0329] (Note 25) The first communication device as described in Appendix 24, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI when transmitting the information to the second communication device.

[0330] (Note 26) Receiving the aforementioned information includes receiving a Registration Request message containing the aforementioned information, The first communication device as described in Appendix 24 or 25, wherein transmitting the aforementioned information includes transmitting an Nnssf_NSSelection_Get message containing the aforementioned information.

[0331] (Note 27) The first communication device as described in any one of Appendix 22 to 26, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving an Nnssf_NSSelection_Get Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0332] (Note 28) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Network Slice Selection Function (NSSF), as described in any one of the items 22 to 27 of the appendix.

[0333] (Note 29) Receiving the aforementioned information includes receiving a Registration Request message containing the aforementioned information, The first communication device as described in Appendix 24 or 25, which transmits the aforementioned information, including transmitting an Npcf_AMPolicyControl_Create message containing the aforementioned information.

[0334] (Note 30) The first communication device according to appendices 22 to 25 and 29, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving an Npcf_AMPolicyControl_Create Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0335] (Note 31) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is the first communication device described in appendices 22 to 25, 29 and 30, which is a Policy Control Function (PCF).

[0336] (Note 32) A first communication device, Means for receiving information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance (S-NSSAI), Means for determining at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, A first communication device comprising means for transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to user equipment (UE).

[0337] (Note 33) Receiving the aforementioned information includes receiving an Nnwdaf_SliceInformation notification message containing the aforementioned information. The first communication device as described in Appendix 32, wherein transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes transmitting a UE Configuration Update Command message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0338] (Note 34) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is the first communication device described in Appendix 32 or 33, which is a Network Data Analytics Function (NWDAF).

[0339] (Note 35) User equipment (UE), Means for transmitting information to a communication device indicating that the UE can understand at least one of the Partially Allowed Network Slice Selection Assistance Information (NSSAI) and the Partially Rejected Single Network Slice Selection Assistance (S-NSSAI), A UE comprising means for receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI from a communication device when transmitting the aforementioned information.

[0340] (Note 36) Transmitting the aforementioned information includes sending a Registration Request message containing the aforementioned information. The UE device according to Appendix 35, wherein receiving at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes receiving a Registration Accept message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0341] (Note 37) The aforementioned communication device is an Access and Mobility Management Function (AMF), as defined in Appendix 35 or 36.

[0342] (Note 38) A first communication device, Means for receiving information from a second communication device for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Partially Rejected Single Network Slice Selection Assistance (S-NSSAI), Means for determining at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI, A first communication device comprising means for transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI to the second communication device.

[0343] (Note 39) Receiving the aforementioned information includes receiving an Nnssf_NSSelection_Get message containing the aforementioned information. The first communication device as described in Appendix 38, wherein transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes transmitting an Nnssf_NSSelection_Get Response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0344] (Note 40) The first communication device is a Network Slice Selection Function (NSSF), The second communication device is the first communication device as described in Appendix 38 or 39, which is an Access and Mobility Management Function (AMF).

[0345] (Note 41) Receiving the aforementioned information includes receiving an Npcf_AMPolicyControl_Create message containing the aforementioned information. The first communication device as described in Appendix 38, wherein transmitting at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI includes transmitting an Npcf_AMPolicyControl_Create response message containing at least one of the Partially Allowed NSSAI and the Partially Rejected S-NSSAI.

[0346] (Note 42) The aforementioned first communication device is a Policy Control Function (PCF), The second communication device is the first communication device as described in Appendix 38 or 41, which is an Access and Mobility Management Function (AMF).

[0347] (Note 43) A method for a first communication device, A Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) is received from User Equipment (UE). The Requested NSSAI is transmitted to the second communication device. The second communication device receives Allowed NSSAI, which includes Single Network Slice Selection Assistance Information (S-NSSAI), A Registration Accept message including "Partially Allowed NSSAI" is sent to the UE. The Partially Allowed NSSAI is a method that includes the S-NSSAI.

[0348] (Note 44) The method described in Appendix 43, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI.

[0349] (Note 45) The method described in Appendix 43, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI and the policy of the first communication device.

[0350] (Note 46) The Allowed NSSAI is determined based on the Requested NSSAI, according to any one of the methods described in Appendix 43 to 45.

[0351] (Note 47) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Network Slice Selection Function (NSSF) as described in any one of the appendices 43 to 46.

[0352] (Note 48) A method for User Equipment (UE), A Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) is sent to the first communication device. I received a Registration Accept message that included "Partially Allowed NSSAI". The aforementioned Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), The S-NSSAI in the Partially Allowed NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI is a method comprising the S-NSSAI.

[0353] (Note 49) The S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI, as described in Appendix 48.

[0354] (Note 50) The method described in Appendix 48, wherein the S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI and the policy of the first communication device.

[0355] (Note 51) The Allowed NSSAI is determined based on the Requested NSSAI, according to any one of the methods described in Appendix 48 to 50.

[0356] (Note 52) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Network Slice Selection Function (NSSF) as described in any one of the appendices 48 to 51.

[0357] (Note 53) A first communication device, A means for receiving a Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) from User Equipment (UE), Means for transmitting the Requested NSSAI to a second communication device, A means for receiving Allowed NSSAI, including Single Network Slice Selection Assistance Information (S-NSSAI), from the second communication device, The system includes means for sending a Registration Accept message, including a Partially Allowed NSSAI, to the UE. The Partially Allowed NSSAI is a first communication device including the S-NSSAI.

[0358] (Note 54) The S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI, as described in Appendix 53.

[0359] (Note 55) The S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI and the policy of the first communication device, as described in Appendix 53.

[0360] (Note 56) The Allowed NSSAI is the first communication device described in any one of the appendices 53 to 55, determined based on the Requested NSSAI.

[0361] (Note 57) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is the first communication device described in any one of the appendices 53 to 56, which is a Network Slice Selection Function (NSSF).

[0362] (Note 58) User Equipment (UE), Means for sending a Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) to a first communication device, It includes means for receiving Registration Accept messages, including Partially Allowed NSSAI, The aforementioned Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), The S-NSSAI in the Partially Allowed NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI includes the S-NSSAI, which is a UE.

[0363] (Note 59) The S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI, as described in Appendix 58.

[0364] (Note 60) The S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI and the policy of the first communication device, as described in Appendix 58.

[0365] (Note 61) The Allowed NSSAI is determined based on the Requested NSSAI, and is a UE specified in any one of the items in Appendix 58 to 60.

[0366] (Note 62) The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Network Slice Selection Function (NSSF), as described in any one of the items 58 to 61 of the appendix.

[0367] This application is based on Indian Patent Application No. 202311025745, filed on April 5, 2023, and claims priority thereunder. [Explanation of Symbols]

[0368] 1. Telecommunications 3 UE 5(R)AN Node 7 Core Network 20 Data Networks 60 RU 61 DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 NWDAF 75 UDM 76 NSSF 201 OF

Claims

1. A method for a first communication device, A Registration Request message containing Requested Network Slice Selection Assistance Information (NSSAI) is received from the User Equipment (UE). The Requested NSSAI is transmitted to the second communication device. The second communication device receives an Allow NSSAI including Single Network Slice Selection Assistance Information (S-NSSAI), A Registration Accept message including Partially Allowed NSSAI is sent to the UE. The Partially Allowed NSSAI is a method comprising the S-NSSAI.

2. The method according to claim 1, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI.

3. The method according to claim 1, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI and the policy of the first communication device.

4. The method according to any one of claims 1 to 3, wherein the Allowed NSSAI is determined based on the Requested NSSAI.

5. The first communication device is an Access and Mobility Management Function (AMF), The method according to any one of claims 1 to 4, wherein the second communication device is a Network Slice Selection Function (NSSF).

6. A method for User Equipment (UE), A Registration Request message including Requested Network Slice Selection Assistance Information (NSSAI) is sent to the first communication device. Upon receiving a Registration Accept message including Partially Allowed NSSAI, The Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), In the Partially Allowed NSSAI, the S-NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI is a method comprising the S-NSSAI.

7. The method according to claim 6, wherein the S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI.

8. The method according to claim 6, wherein the S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI and the policy of the first communication device.

9. The method according to any one of claims 6 to 8, wherein the Allowed NSSAI is determined based on the Requested NSSAI.

10. The first communication device is an Access and Mobility Management Function (AMF), The method according to any one of claims 6 to 9, wherein the second communication device is a Network Slice Selection Function (NSSF).

11. A first communication device, Means for receiving a Registration Request message from User Equipment (UE) including Requested Network Slice Selection Assistance Information (NSSAI), Means for transmitting the Requested NSSAI to a second communication device, Means for receiving Allow NSSAI, including Single Network Slice Selection Assistance Information (S-NSSAI), from the second communication device, The system includes means for sending a Registration Accept message including Partially Allowed NSSAI to the UE, The Partially Allowed NSSAI is a first communication device that includes the S-NSSAI.

12. The first communication device according to claim 11, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI.

13. The first communication device according to claim 11, wherein the S-NSSAI in the Partially Allowed NSSAI is determined by the first communication device based on the Allowed NSSAI and the policy of the first communication device.

14. The first communication device according to any one of claims 11 to 13, wherein the Allowed NSSAI is determined based on the Requested NSSAI.

15. The first communication device is an Access and Mobility Management Function (AMF), The first communication device according to any one of claims 11 to 14, wherein the second communication device is a Network Slice Selection Function (NSSF).

16. User Equipment (UE), Means for transmitting a Registration Request message including Requested Network Slice Selection Assistance Information (NSSAI) to a first communication device, The system includes means for receiving Registration Accept messages, including Partially Allowed NSSAI. The Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), In the Partially Allowed NSSAI, the S-NSSAI is based on the Allowed NSSAI transmitted from the second communication device to the first communication device. The Allowed NSSAI includes the S-NSSAI, and is a UE.

17. The UE according to claim 16, wherein the S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI.

18. The UE according to claim 16, wherein the S-NSSAI in the Partially Allowed NSSAI is determined based on the Allowed NSSAI and the policy of the first communication device.

19. The Allowed NSSAI is determined based on the Requested NSSAI, the UE according to any one of claims 16 to 18.

20. The first communication device is an Access and Mobility Management Function (AMF), The UE according to any one of claims 16 to 19, wherein the second communication device is a Network Slice Selection Function (NSSF).

Images