Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), and methods thereof.

Abstract

One aspect of this disclosure includes a method of a first communication device, the method including communicating with a second communication device, and the method including transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

Description

Technical Field

[0001] The present disclosure relates to a method for a first communication device, a method for a User Equipment (UE), a first communication device, a UE, and the like.

Background Art

[0002] Since network slicing was standardized in 3GPP (registered trademark) Rel-15, the final decision of network slice selection is entrusted to the UE. When an application in the UE requires a service, the UE selects a network slice based on the URSP rules provided by the network. The URSP rules define which applications having which network slices are permitted to start a service. In 3GPP Rel-18, a network slice replacement feature was introduced that enables a PDU session to be moved to an alternative network slice defined by OAM, PCC rules, or NSSF. The network slice replacement procedure is triggered by the AMF upon notification from OAM, PCF, or NSSF.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

[0004] An application server (or service provider or Application Function (AF)) may have good information about the correct network slice for an application, based, for example, on ongoing connection monitoring, connection statistics analysis, application characteristics, and service requirements (such as high-speed requirements). Therefore, network slice selection and replacement by the network, based on notifications from the application server, is required. However, the 3GPP standard lacks a mechanism to support network-based network slice selection and replacement. [Means for solving the problem]

[0005] The method of the first communication device is: To communicate with the second communication device, This includes transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

[0006] The method of the first communication device is: Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions based on Alternative S-NSSAI, The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM).

[0007] The User Equipment (UE) method is: To communicate with the first communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is the Access and Mobility Management Function (AMF), and the second communication device is the Unified Data Management (UDM).

[0008] The method of the first communication device is: Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting an Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Access and Mobility Management Function (AMF).

[0009] The method of the first communication device is: Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting an Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Session Management Function (SMF).

[0010] The User Equipment (UE) method is: Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the first communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions based on S-NSSAI, The first communication device is a Session Management Function (SMF).

[0011] The method of the first communication device is: To communicate with the second communication device, including transmitting an S-NSSAI replaced by an Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

[0012] The method of a User Equipment (UE) is to transmit a registration request message, where the registration request message includes an Alternative Single Network Slice Selection Assistance Information (S-NSSAI), to transmit a Protocol Data Unit (PDU) session establishment request message, where the PDU session establishment request message includes an Alternative S-NSSAI.

[0013] The method of a first communication device is to receive an Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, and to execute procedures related to a Protocol Data Unit (PDU) session based on the S-NSSAI, where the first communication device is an Access and Mobility Management Function (AMF).

[0014] The first communication device comprises means for communicating with a second communication device, and means for transmitting an Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

[0015] The first communication device A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for performing procedures related to a Protocol Data Unit (PDU) session based on Alternative S-NSSAI, The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM).

[0016] User Equipment (UE) is A means for communicating with the first communication device, The system includes means for performing procedures related to a Protocol Data Unit (PDU) session, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM).

[0017] The first communication device is A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Access and Mobility Management Function (AMF).

[0018] The first communication device is A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Session Management Function (SMF).

[0019] User Equipment (UE) is A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a first communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on S-NSSAI, The first communication device is a Session Management Function (SMF).

[0020] The first communication device is A means for communicating with a second communication device, The system includes means for transmitting Single Network Slice Selection Assistance Information (S-NSSAI) that has been replaced with Alternative S-NSSAI.

[0021] User Equipment (UE) is A means for sending a registration request message, The registration request message includes Alternative Single Network Slice Selection Assistance Information (S-NSSAI), and A means for sending a Protocol Data Unit (PDU) session establishment request message, The PDU session establishment request message comprises means including Alternative S-NSSAI.

[0022] The first communication device is A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on S-NSSAI, The first communication device is the Access and Mobility Management Function (AMF). [Brief explanation of the drawing]

[0023] [Figure 1] This figure shows network slice selection and replacement via AF through a UDM for existing PDU sessions (multiple sessions possible). [Figure 2] This figure shows network slice selection and replacement via AF through UDM for a new PDU session(s). [Figure 3]This figure shows network slice selection and replacement by AF via PCF. [Figure 4] This figure shows network slice selection and replacement via AF through NSSF for existing and new PDU sessions (multiple sessions possible). [Figure 5] This figure shows network slice selection and replacement using AF with UE support. [Figure 6] This figure shows network slice selection and replacement using UE subscription information. [Figure 7] This diagram shows user consent for sharing confidential information with a third-party AF via a NAS. [Figure 8] This diagram shows user consent for sharing confidential information with third-party applications via the application. [Figure 9] This figure shows user consent for sharing confidential information with third-party AFs from NWDAF. [Figure 10] This diagram shows instructions for URSP support to 5GC. [Figure 11] This diagram shows the system overview. [Figure 12] This is the UE Block. [Figure 13] (R)AN node block. [Figure 14] This figure shows a system overview of an (R)AN node based on the O-RAN architecture. [Figure 15] RU is a block letter. [Figure 16] DU branch office. [Figure 17] This is the CU (Clinical Unit) branch office. [Figure 18] AMF is a type of cylinder. [Figure 19] SMF block. [Figure 20] UPF block. [Figure 21] PCF block. [Figure 22] This is a block of NWDAF. [Figure 23] UDM cylinder. [Figure 24] This is the NSSF block. [Figure 25] This is an NSACF block. [Figure 26] AUSF is a block diagram. [Figure 27] AF is a block of paper. [Figure 28] A branch of NEF. [Modes for carrying out the invention]

[0024] Abbreviation For the purposes of this document, the abbreviations given in 3GPP TR21.905[1] and below apply. The abbreviations defined in this document take precedence over any definitions of the same abbreviations in 3GPP TR21.905[1], if any. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5G LAN 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 APP_ID Application Identity 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 QoS Quality of Service 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

[0025] definition For the purposes of this document, the terms and definitions given in 3GPP TR21.905[1] and below shall apply. Terms defined in this document shall take precedence over the definitions of the same terms in 3GPP TR21.905[1].

[0026] List of citations [1]3GPP TR21.905: “Vocabulary for 3GPP Specifications”.V17.1.0(2021-12) [2]3GPP TS23.501: “System architecture for the 5G System(5GS)”.V18.1.0(2023-03) [3]3GPP TS23.502: “Procedures for the 5G System (5GS)”.V18.1.1(2023-04) [4]3GPP TS23.503: “Policy and charging control framework for the 5G System(5GS)Stage 2”.V18.1.0(2023-03) [5]3GPP SA#100 Workshop-SWS-230044 https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / Workshops / 2023-06-13_Rel-19_WorkShop / Docs / SWS-230044.zip

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

[0028] For the purpose of facilitating understanding of the principles of this disclosure, embodiments shown in the figures will be referred to and described here using specific language. Nevertheless, it will be understood that no limitation of the scope of this disclosure is intended therein. Such changes and further modifications to the illustrated systems, as well as such further applications of the principles of this disclosure that a person skilled in the art would ordinarily conceive of, should be construed as being within the scope of this disclosure.

[0029] The terms “comprises,” “comprising,” or any other variation thereof are intended to cover non-exclusive inclusion, such that a process or method comprising a list of steps may include other steps that are not explicitly enumerated or are specific to such process or method, rather than including only those steps. Similarly, one or more devices or entities or subsystems or elements or structures or components preceded by “comprises…a” does not, without further constraint, exclude the existence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, occurrences of the phrases “in one aspect,” “in another aspect,” and similar language may, but not necessarily, refer to the same aspect.

[0030] 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.

[0031] In the following specification and claims, several terms may be defined as having the following meanings: The singular forms “a,” “an,” and “the” include the plural form unless the context clearly indicates otherwise. Where used herein, data is meaningful information and represents values ​​assigned to parameters; therefore, information is associated with data and knowledge. Further knowledge means an understanding of abstract or concrete concepts. Note that this exemplary system is simplified for the sake of facilitating the explanation of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement the embodiments disclosed herein, and all such embodiments are considered to be within the scope of this disclosure.

[0032] Each of the embodiments and its components described below may be implemented independently or in combination as appropriate. These embodiments contain novel features that differ from each other. Therefore, these embodiments contribute to solving different purposes or problems and to producing different effects.

[0033] Any list described in the following aspects includes at least one or more parameters. In this disclosure, the expression "A and / or B" may mean "at least one of A and B". The definitions of parameters (multiple parameters are possible) in each embodiment can be referenced from one another. The purpose of this disclosure is to provide a method and apparatus that can solve the problems described above. Each aspect and element may relate to one of the following descriptions, a combination of the following descriptions, or all of the following descriptions, but is not limited to each aspect and element described below. Each aspect and element may provide a solution relating to one of the following descriptions, a combination of the following descriptions, or all of the following descriptions, but each aspect and element may also provide a solution other than those described below. An application server (or service provider or Application Function (AF)) may have good information about the correct network slice for an application, based, for example, on ongoing connection monitoring, connection statistics analysis, application characteristics, and service requirements (such as high-speed requirements). Therefore, network slice selection and replacement by the network, based on notifications from the application server, is required. However, the 3GPP standard lacks a mechanism to support network-based network slice selection and replacement.

[0034] In addition, without network slice selection and replacement based on notifications from the application server, for example, network slice resources deployed under a Service Level Agreement (SLA) between a mobile network operator and a third party may not be fully utilized, potentially violating the purpose of the SLA.

[0035] A method of a first communication device according to an exemplary aspect of the present disclosure includes communicating with a second communication device. The method includes transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

[0036] An exemplary method of a first communication device according to the present disclosure includes receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes performing procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is an Access and Mobility Management Function (AMF). The second communication device is a Unified Data Management (UDM).

[0037] An exemplary method of User Equipment (UE) in this disclosure includes communicating with a first communication device. The method includes performing a procedure related to a Protocol Data Unit (PDU) session. The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). The Alternative S-NSSAI is transmitted to the first communication device by a second communication device. The first communication device is an Access and Mobility Management Function (AMF). The second communication device is a Unified Data Management (UDM).

[0038] A method for a first communication device according to an exemplary aspect of the present disclosure includes receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes transmitting the Alternative S-NSSAI to a third communication device. The first communication device is a Policy Control Function (PCF). The second communication device is a Network Exposure Function (NEF). The third communication device is an Access and Mobility Management Function (AMF).

[0039] A method for a first communication device according to an exemplary aspect of the present disclosure includes receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes transmitting the Alternative S-NSSAI to a third communication device. The first communication device is a Network Slice Selection Function (NSSF). The second communication device is a Network Exposure Function (NEF). The third communication device is a Session Management Function (SMF).

[0040] An exemplary User Equipment (UE) method in this disclosure includes receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a first communication device. The method includes performing procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is a Session Management Function (SMF).

[0041] A method of a first communication device according to an exemplary aspect of the present disclosure includes communicating with a second communication device. The method includes transmitting Single Network Slice Selection Assistance Information (S-NSSAI) which is replaced by Alternative S-NSSAI.

[0042] An exemplary method of User Equipment (UE) as described in this disclosure includes sending a registration request message, which includes Alternative Single Network Slice Selection Assistance Information (S-NSSAI). The method also includes sending a Protocol Data Unit (PDU) session establishment request message, which includes Alternative S-NSSAI.

[0043] An exemplary method of a first communication device according to the present disclosure includes receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The method includes performing procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is an Access and Mobility Management Function (AMF).

[0044] A first communication device according to an exemplary embodiment of the present disclosure comprises at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to communicate with a second communication device. The at least one hardware processor is configured to transmit Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

[0045] An exemplary embodiment of the present disclosure of a first communication device comprises at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The at least one hardware processor is configured to perform procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is an Access and Mobility Management Function (AMF). The second communication device is a Unified Data Management (UDM).

[0046] User Equipment (UE) in exemplary aspects of this 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 communicate with a first communication device. The at least one hardware processor is configured to perform procedures related to a Protocol Data Unit (PDU) session. Procedures related to a PDU session are triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). The Alternative S-NSSAI is transmitted to the first communication device by a second communication device. The first communication device is an Access and Mobility Management Function (AMF). The second communication device is a Unified Data Management (UDM).

[0047] An exemplary embodiment of the present disclosure provides a first communication device comprising at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The at least one hardware processor is configured to transmit Alternative S-NSSAI to a third communication device. The first communication device is a Policy Control Function (PCF). The second communication device is a Network Exposure Function (NEF). The third communication device is an Access and Mobility Management Function (AMF).

[0048] An exemplary embodiment of the present disclosure provides a first communication device comprising at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The at least one hardware processor is configured to transmit Alternative S-NSSAI to a third communication device. The first communication device is a Network Slice Selection Function (NSSF). The second communication device is a Network Exposure Function (NEF). The third communication device is a Session Management Function (SMF).

[0049] User Equipment (UE) in exemplary aspects of this 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 Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a first communication device. The at least one hardware processor is configured to perform procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is a Session Management Function (SMF).

[0050] An exemplary communication device according to the present disclosure comprises at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to communicate with a second communication device. The at least one hardware processor is configured to transmit Single Network Slice Selection Assistance Information (S-NSSAI) replaced by Alternative S-NSSAI.

[0051] User Equipment (UE) in exemplary aspects of this 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 send registration request messages, which include Alternative Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to send Protocol Data Unit (PDU) session establishment request messages, which include Alternative S-NSSAI.

[0052] An exemplary embodiment of the present disclosure of a first communication device comprises at least one memory and at least one hardware processor connected to at least one memory. The at least one hardware processor is configured to receive Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device. The at least one hardware processor is configured to perform procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI. The first communication device is an Access and Mobility Management Function (AMF).

[0053] First aspect The first aspect includes a mechanism by which an application server 201 (e.g., AF201) via NEF79 and UDM75 selects a network slice for a new PDU session or replaces a network slice for an existing PDU session.

[0054] A first example of the first aspect: A detailed process of a first example of a first embodiment of a mechanism for replacing network slices for an existing PDU session(s) using AF201 via UDM75 is described below with reference to Figure 1. Figure 1: Network slice selection and replacement via AF through UDM for existing PDU session(s).

[0055] 1. The PDU session is established by UE3 on S-NSSAI-1.

[0056] 2. An application server (e.g., AF201) may trigger a network slice replacement and provide an Alternative S-NSSAI for each of the UE3 (or group of UEs) subscribed S-NSSAIs in UDM75 via NEF79 to move existing or new PDU sessions to the Alternative S-NSSAI. For example, AF201 may trigger the replacement of a network slice based on the information it possesses. For example, AF201 may trigger network slice replacement based on information related to at least one of the following: ongoing connection monitoring, connection statistics analysis, application characteristics, and service requirements (such as high-speed and high-quality-of-service requirements).

[0057] For example, AF201 may trigger network slice replacement if at least one of the results of ongoing connection monitoring and / or connection statistics analysis meets the operator policy or application policy requirements. For example, AF201 may trigger network slice replacement based on at least one of application characteristics and service requirements (such as high-speed and high-quality-of-service requirements). For example, the ongoing connection monitoring, connection statistics analysis, application characteristics, and service requirements described above may relate to an S-NSSAI(or network slice(s) indicated by an S-NSSAI(or)).

[0058] For example, the ongoing connection monitoring, connection statistics analysis, application characteristics, and service requirements described above may be related to S-NSSAI-1 (or the network slice indicated by S-NSSAI-1). For example, if the results of connection monitoring related to S-NSSAI-1 (such as the results of connection monitoring related to a PDU session(s) on S-NSSAI-1) indicate that the connection quality is poor, insufficient, or below a predetermined threshold, AF201 may trigger a network slice replacement (for example, AF201 may send an Alternative S-NSSAI to S-NSSAI-1 as described in step 3). For example, if AF201 detects that an S-NSSAI (e.g., S-NSSAI-1 or the network slice indicated by S-NSSAI-1) is unavailable or congested, AF201 may trigger a network slice replacement (for example, AF201 may send an Alternative S-NSSAI for S-NSSAI-1, as described in step 3).

[0059] 3. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, and AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. -S-NSSAI-1-AF201 is a network slice to be replaced, for which an Alternative S-NSSAI is provided. AF201 may provide an Alternative S-NSSAI for one or more S-NSSAIs to which UE3 is subscribed. S-NSSAI-1 may be the S-NSSAI of the network slice to be replaced, for which AF201 provides an Alternative S-NSSAI. S-NSSAI-1 may be the S-NSSAI of the network slice to be replaced. S-NSSAI-1 may be the S-NSSAI of the network slice to be replaced by an Alternative S-NSSAI. -Alternative S-NSSAI- This is an alternative network slice for S-NSSAI-1, i.e., the network slice to which S-NSSAI-1 is replaced. AF201 may provide multiple alternative network slices for each S-NSSAI-1. An Alternative S-NSSAI may also be a special slice under a bundle service containing the application requested by UE3. An Alternative S-NSSAI may be the S-NSSAI of the network slice to which S-NSSAI-1 is replaced. An Alternative S-NSSAI may be the S-NSSAI of the network slice that replaces S-NSSAI-1. Optionally, AF201 may provide at least one of the following: -Location parameter- Information expressed as a cell or list of cells, TA or list of TAs, or geographical location, meaning that the provided Alternative S-NSSAI is valid only in those locations. The location parameter may indicate the locations where the Alternative S-NSSAI (or the network slice indicated by the Alternative S-NSSAI) is valid. -Effectiveness parameter- Information that may be provided as time, in terms of hours, days, or any other expression of duration, meaning that the Alternative S-NSSAI is effective during these durations. The effectiveness parameter may indicate the time, duration, interval, or period during which the Alternative S-NSSAI (or the network slice indicated by the Alternative S-NSSAI) is effective. -APN- Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3. For example, the user IP address is the IP address assigned to UE3.

[0060] For example, AF201 may pre-store information indicating the correspondence between S-NSSAI(multiple) and Alternative S-NSSAI(multiple) for S-NSSAI(multiple), or it may receive such information from other network nodes(multiple). For example, AF201 may pre-store information indicating that S-NSSAI-2 is the alternative S-NSSAI to S-NSSAI-1, or it may receive this information from another network node(s). For example, using this information, AF201 may select S-NSSAI-1 and its alternative S-NSSAI (e.g., S-NSSAI-2). For example, when AF201 triggers a network slice replacement, AF201 may select one S-NSSAI(s) to replace (e.g., S-NSSAI-1) and then select an Alternative S-NSSAI(s)(e.g., S-NSSAI-2) for the selected S-NSSAI(s). Next, AF201 may send the selected S-NSSAI and the selected Alternative S-NSSAI(s)(s) to NEF79. For example, AF201 may trigger network slice replacement by sending an Nnef_Service_Parameter_Update request message.

[0061] 4. NEF79 may call the Nudm_SDM_Get service operation to perform at least one of the following mappings: - Mapping (or converting) the GPSI in the global UE_Id to SUPI according to the information received from UDM75. -Map (or convert) the external UE group identity to the internal group identifier according to the information received from UDM75.

[0062] 5. NEF79 may need to authorize service-specific parameter provisioning requests with UDM75 by performing the Nudm_ServiceSpecificAuthorisation_Create service operation as defined in section 4.15.6.7a of 3GPP TS23.502[3].

[0063] 6. An Alternative S-NSSAI is stored in the UE3 subscription information within UDM75 for the S-NSSAI it substitutes for, e.g., S-NSSAI-1, or (if already stored) updated. Each UE3 subscription S-NSSAI may be assigned an Alternative S-NSSAI in the UE subscription information within UDM75. If location parameters and / or validity parameters are provided for an Alternative S-NSSAI, they are also stored or updated in the UE subscription information for that Alternative S-NSSAI within UDM75. For example, UDM75 may receive at least one of the following from NEF79 during at least one of steps 4 and 5: S-NSSAI-1, Alternative S-NSSAI, location parameters, and validity parameters. For example, UDM75 may store Alternative S-NSSAI associated with S-NSSAI-1. For example, UDM75 may store an Alternative S-NSSAI associated with at least one of the S-NSSAI-1, location parameters, and validity parameters. For example, UDM75 can update the stored Alternative S-NSSAI based on the received Alternative S-NSSAI.

[0064] 7. NEF79 responds to AF201 by sending an Nnef_ServiceParameter_Update response message to confirm the parameter update.

[0065] 8. UDM75 triggers a Nudm_SDM_Notification to AMF70, in which the message includes at least one of the following: the network slice to be replaced (e.g., S-NSSAI-1), the Alternative S-NSSAI which is the network slice replacing S-NSSAI-1, location parameters, validity parameters, APN, DNN, and user IP address. For example, UDM75 may send a Nudm_SDM_Notification message to AMF70 that includes at least one of the following: S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address. This requests that any existing PDU sessions on the network slice (e.g., S-NSSAI-1) be moved to the Alternative S-NSSAI. If location parameters and / or validity parameters are provided, UDM75 may trigger a Nudm_SDM_Notification only at locations and times that conform to the restrictions imposed by the location and validity parameters. Alternatively, UDM75 may provide location parameters and / or effectiveness parameters to AMF70.

[0066] 9. If AMF70 receives S-NSSAI-1 and Alternative S-NSSAI in step 8, AMF70 triggers a PDU session correction procedure, as in step 1h of section 4.3.3.2 of 3GPP TS23.502[3], to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI. The AMF70 may refer to the user IP address in step 8 (for example, the user IP address received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI. The AMF70 may refer to at least one of the APN and DNN from step 8 (for example, at least one of the APN and DNN received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0067] UE3 may indicate to a node(s)(e.g., AMF70) during any procedure (e.g., registration procedure) that it supports the slice replacement function. For example, UE3 may indicate to a node(s)(e.g., AMF70) that UE3 supports network slice replacement as described in this disclosure (e.g., Figure 1). In this case, if UE3 indicates support for the slice replacement function and an S-NSSAI-1 requested by UE3 (e.g., an S-NSSAI-1 on which a PDU session has been established) requires replacement in accordance with the notification from UDM75 in step 8, AMF70 may trigger a PDU session modification procedure to move the PDU session from S-NSSAI-1 to an Alternative S-NSSAI. For example, the message in step 8 may indicate or notify that S-NSSAI-1 needs to be replaced with an Alternative S-NSSAI.

[0068] Furthermore, if UE3 indicates support for slice replacement functionality and the S-NSSAI-1 requested by UE3 requires replacement in accordance with the notification from UDM75 in step 8, AMF70 may trigger a PDU session modification procedure, as in step 1h of section 4.3.3.2 of 3GPP TS23.502[3], to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI. If AMF70 receives at least one of the location and validity parameters for Alternative S-NSSAI, AMF70 may trigger network slice replacement by Alternative S-NSSAI only at the locations and times permitted by the location and validity parameters.

[0069] Support for slice replacement functionality may be expressed as network slice replacement support. The definition of network slice replacement support in the first example of the seventh embodiment may be applied to each embodiment. For example, UE3 may indicate network slice replacement support in the same way as in the first example of the seventh embodiment. The way in which UE3 indicates network slice replacement support in the first example of the seventh embodiment may be applied to each embodiment. For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that a replacement of S-NSSAI-1 is required as requested by UE3.

[0070] For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that the S-NSSAI-1 requested by UE3 requires replacement, and may perform a PDU session modification procedure such as step 1h in section 4.3.3.2 of 3GPP TS23.502[3] to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI.

[0071] Continue the network trigger PDU session modification procedure from step 1h to Alternative S-NSSAI according to section 4.3.3.2 of 10.3GPP TS23.502[3].

[0072] For example, in this disclosure, S-NSSAI-1 and Alternative S-NSSAI may be included in Alternative NSSAI. For example, in this disclosure, instead of sending and receiving S-NSSAI-1 and Alternative S-NSSAI separately, Alternative NSSAI may be sent and received. The Alternative NSSAI can identify a list of mapping information between the S-NSSAI to be replaced (e.g., S-NSSAI-1) and the Alternative S-NSSAI. The Alternative NSSAI may contain a list of mapping information between the S-NSSAI to be replaced (e.g., S-NSSAI-1) and the Alternative S-NSSAI.

[0073] Modification 1 of the first example of the first aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh embodiment.

[0074] Modification 2 of the first example of the first embodiment In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing. For example, AF201 may know whether UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect.

[0075] Modification 3 of the first example of the first aspect In step 2, AF201 may trigger an AF trigger request for a slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing but does support network slice replacement support functionality. For example, AF201 may know the capability of UE3 based on the procedure disclosed by the first example of the seventh embodiment.

[0076] Modification 4 of the first example of the first aspect In step 9, the AMF70 may send a NAS message to the UE3 that includes at least one of the following: the network slice to be replaced (e.g., S-NSSAI-1), an Alternative S-NSSAI which is the network slice that replaces S-NSSAI-1, location parameters, validity parameters, APN, DNN, and user IP address. If UE3 receives S-NSSAI-1 and Alternative S-NSSAI, UE3 may initiate a PDU session modification procedure to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI.

[0077] For example, UE3 itself may initiate a PDU session modification procedure to switch to a different slice recommended by AF201 based on location and validity parameters. UE3 may refer to the user's IP address to find the PDU session that needs to be modified from S-NSSAI-1 to Alternative S-NSSAI. UE3 may refer to at least one of the APN and DNN to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0078] Modification 5 of the first example of the first aspect For example, AF201 may decide to perform slice substitution for a specific access type (e.g., 3GPP access or non-3GPP access) or a RAT type of 3GPP access. In this case, AF201 may send information indicating the access type (e.g., information indicating the access type (e.g., 3GPP access, non-3GPP access, or RAT type of 3GPP access (e.g., NR, EUTRA, etc.))) to NEF79 in step 3 in the Nnef_ServiceParameter_Update request message. In step 6, the access type may also be passed to UDM75 or UDR, which may store the access type. In step 8, UDM75 provides the access type to AMF70. If AMF70 receives the access type in step 8, AMF70 may initiate a PDU session modification procedure for PDU sessions activated on the access type indicated by the received access type.

[0079] A second example of the first embodiment: A detailed process of a second example of the first embodiment for a mechanism for network slice selection for a new PDU session(s) via UDM75 using AF201 is described below with reference to Figure 2. Figure 2: Network slice selection and replacement via AF through UDM for a new PDU session (multiple sessions possible).

[0080] 1. The application server (e.g., AF201) may trigger a network slice replacement and provide an Alternative S-NSSAI for each of the UE3 (or group of UEs) in UDM75 via NEF79. Step 1 may be the same as Step 2 in Figure 1.

[0081] 2. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, and AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. -S-NSSAI-1-AF201 is a network slice to be replaced, which provides an Alternative S-NSSAI. AF201 may provide an Alternative S-NSSAI to one or more S-NSSAIs that UE3 is subscribed to. -Alternative S-NSSAI- This is an alternative network slice for S-NSSAI-1, i.e., a network slice to which S-NSSAI-1 is replaced. AF201 may provide multiple alternative network slices for each S-NSSAI-1.

[0082] Optionally, AF201 may provide at least one of the following: Location parameters - Information represented as a cell or list of cells, TA or list of TAs, or geographical location, meaning that the provided Alternative S-NSSAI is only valid in those locations. -Validity parameter-Alternative S-NSSAI information that can be provided as time, day, or any other expression of duration, in the sense that it is valid during these durations. -APN- Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3. Step 2 may be the same as Step 3 in Figure 1. The definitions of global UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameter, validity parameter, APN, DNN, and user IP address in the first example of the first embodiment may be applied to other examples or embodiments.

[0083] 3. NEF79 may call the Nudm_SDM_Get service operation to perform the following mapping. - Mapping GPSI in the global UE_Id to SUPI according to the information received from UDM75. - Mapping external UE group identities to internal group identifiers according to the information received from UDM75. Step 3 may be the same as Step 4 in Figure 1.

[0084] 4. NEF79 may need to authorize service-specific parameter provisioning requests with UDM75 by performing the Nudm_ServiceSpecificAuthorisation_Create service operation as defined in section 4.15.6.7a of 3GPP TS23.502[3]. Step 4 may be the same as Step 5 in Figure 1.

[0085] 5. An Alternative S-NSSAI is stored in the UE subscription information within UDM75 for the S-NSSAI it substitutes for, e.g., S-NSSAI-1, or updated (if already stored). Each UE3 subscription S-NSSAI may be assigned an Alternative S-NSSAI in the UE3 subscription information within UDM75. If location parameters and / or validity parameters are provided for an Alternative S-NSSAI, they are also stored or updated in the UE subscription information for that Alternative S-NSSAI within UDM75. Step 5 may be the same as Step 6 in Figure 1.

[0086] 6. NEF79 responds to AF201 by sending an Nnef_ServiceParameter_Update response message to confirm the parameter update. Step 6 may be the same as Step 7 in Figure 1.

[0087] 7. UDM75 may trigger a Nudm_SDM_Notification to AMF70, in which UDM75 will include at least one of the following in the message: the network slice to be replaced (e.g., S-NSSAI-1), the Alternative S-NSSAI which is the network slice replacing S-NSSAI-1, location parameters, validity parameters, APN, DNN, and user IP address. If location parameters and / or validity parameters are provided, UDM75 may also include the location parameters and / or validity parameters in the Nudm_SDM_Notification. AMF70 stores the provided Alternative S-NSSAI, as well as the location and validity parameters, in the UE context of UE3. For example, UDM75 may send a Nudm_SDM_Notification message to AMF70 that includes at least one of the following: UE_Id (e.g., UE3 identity, UE3 SUPI, etc.), S-NSSAI-1, Alternative S-NSSAI, location parameters, and validity parameters. Step 7 may be the same as Step 8 in Figure 1. When AMF70 receives a Nudm_SDM_Notification message, it may send a Nudm_SDM_Notification response message to UDM75.

[0088] 8. At some point, UE3 triggers a request for PDU session establishment on S-NSSAI-1 by sending a PDU session establishment request message that includes at least one of UE_Id, PDU_Session_Id, S-NSSAI-1, and DNN. For example, UE3 may perform the PDU session establishment procedure for S-NSSAI-1 by sending a PDU session establishment request message.

[0089] 9. When AMF70 receives a PDU session establishment request message, AMF70 sends a Nudm_SDM_Get request message to UDM75 that includes at least one of the following: UE_Id, S-NSSAI-1, and an instruction that UE3 supports the network slice replacement function. UE3 may send the instruction to a node(s) (e.g., AMF70) during any procedure (e.g., registration procedure). For example, the instruction may indicate that UE3 supports network slice replacement as described in this disclosure (e.g., Figure 2). If AMF70 receives the instruction from UE3, AMF70 may include the instruction in a Nudm_SDM_Get request message.

[0090] Furthermore, if UE3 indicates support for the slice replacement feature during any procedure (e.g., the registration procedure), AMF70 sends a Nudm_SDM_Get request message to UDM75, in which AMF70 includes at least one of the following in the Nudm_SDM_Get request message: UE_Id, requested S-NSSAI-1 for the PDU session, and an instruction that UE3 supports the network slice replacement feature. This instruction may be expressed as "network slice replacement supported by the UE 3". For example, UE3 may demonstrate support for slice replacement functionality, similar to step 9 in Figure 1.

[0091] 10. If UE3 supports the network slice replacement function in accordance with the instructions in the Nudm_SDM_Get request message from AMF70, UDM75 provides an Alternative S-NSSAI. UDM75 may provide AMF70 with at least one of the location parameter and the validity parameter. For example, if UDM75 receives a Nudm_SDM_Get request message containing S-NSSAI-1, UDM75 may provide an Alternative S-NSSAI. For example, if UDM75 receives a Nudm_SDM_Get request message containing S-NSSAI-1, UDM75 may find an Alternative S-NSSAI for S-NSSAI-1 and provide the Alternative S-NSSAI.

[0092] 11. UDM75 sends a Nudm_SDM_Get response message to AMF70, where UDM75 includes at least one of the following: the S-NSSAI to be replaced, i.e., S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address. For example, UDM75 may send a Nudm_SDM_Get response message to AMF70 that includes at least one of S-NSSAI-1 and Alternative S-NSSAI. UDM75 may include location parameters, validity parameters, APN, DNN, and user IP address in the Nudm_SDM_Get response message.

[0093] 12. If UE3 indicates support for slice substitution functionality (for example, during the registration procedure) and the S-NSSAI-1 requested by UE3 requires substitution, AMF70 will continue establishing the PDU session on the Alternative S-NSSAI instead of the S-NSSAI-1 requested by UE3. AMF70 may refer to at least one of the APN and DNN in step 7a or step 11 (for example, at least one of the APN and DNN received in step 7a or step 11), regardless of whether a modification from S-NSSAI-1 to Alternative S-NSSAI is required. For example, if AMF70 receives a Nudm_SDM_Get response message, AMF70 may continue or trigger the establishment of a PDU session with Alternative S-NSSAI.

[0094] For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that a replacement of S-NSSAI-1 is required as requested by UE3. For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that a replacement for S-NSSAI-1 is required as requested by UE3, and may execute or trigger the PDU session establishment procedure for Alternative S-NSSAI.

[0095] Continue establishing the PDU session on the Alternative S-NSSAI from Step 3, in accordance with Section 4.3.2.2.1 of 13.3GPP TS23.502[3].

[0096] Modification 1 of the second example of the first embodiment For example, after step 7 (e.g., step 7a or 7b), AMF70 may page UE3 (if not connected), and once UE3 establishes a connection, AMF70 may provide the Alternative S-NSSAI to UE3 by a UE configuration update message in accordance with the agreed Rel-18 Alternative S-NSSAI functionality of 3GPP TS23.502[3]. For example, AMF70 may send a UE configuration update message to UE3 that includes the Alternative S-NSSAI. AMF70 may include at least one of the location and validity parameters associated with the Alternative S-NSSAI in the UE3 context within AMF70 if they are available in the UE3 context. Alternatively, AMF70 may provide the Alternative S-NSSAI along with at least one of the location and validity parameters in a Registration Accept message during the registration procedure. If at least one of the following is provided: Alternative S-NSSAI, location parameters, and validity parameters, UE3 will only use the Alternative S-NSSAI in locations and times permitted by the location and validity parameters. UE3 does not need to trigger a PDU session request for the Alternative S-NSSAI in locations and times restricted by the location and validity information for that Alternative S-NSSAI.

[0097] For example, if UE3 receives an Alternative S-NSSAI and wants to establish a PDU session on S-NSSAI-1, UE3 may establish the PDU session on the Alternative S-NSSAI instead of S-NSSAI-1. For example, if UE3 also receives location parameters, UE3 may establish a PDU session on Alternative S-NSSAI instead of S-NSSAI-1 at the location indicated by the location parameters. For example, if UE3 also receives validity parameters, UE3 may establish a PDU session on Alternative S-NSSAI instead of S-NSSAI-1 for the time, duration, interval, or period indicated by the validity parameters.

[0098] Modification 2 of the second example of the first embodiment In step 1, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh embodiment.

[0099] Modification 3 of the second example of the first embodiment In step 1, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 1, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing. For example, AF201 may know whether UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect.

[0100] Modification 4 of the second example of the first embodiment In step 1, AF201 may trigger an AF trigger request for a slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing but does support network slice replacement support functionality. For example, AF201 may know the capabilities of UE3 based on the procedure disclosed by the first example of the seventh aspect.

[0101] Modification 5 of the second example of the first embodiment For example, AF201 may decide to perform slice substitution for a specific access type (e.g., 3GPP access or non-3GPP access) or for a RAT type of 3GPP access. In this case, AF201 may, in step 2, send the Nnef_ServiceParameter_Update request message to NEF79 with the access type (e.g., information indicating the access type for each RAT type of 3GPP access (e.g., NR, EUTRA, etc.) (e.g., 3GPP access, non-3GPP access)). In step 5, the access type may also be passed to UDM75 or UDR, which may store the access type. In at least one of step 7a and step 11, UDM75 may provide the access type to AMF70. If AMF70 receives the access type in at least one of step 7a and step 11, AMF70 may initiate the PDU session establishment procedure on the access type indicated by the received access type.

[0102] Second aspect A second aspect includes a mechanism for replacing network slices of an existing PDU session(s) by an application server (e.g., AF201) via PCF73.

[0103] First example of the second aspect: A detailed process of the first example of a second embodiment for a mechanism for replacing network slices with an existing PDU session(s) via PCF73 using AF201 is described below with reference to Figure 3. Figure 3: Network slice selection and replacement by AF via PCF

[0104] 1. The PDU session is established by UE3 on S-NSSAI-1. Step 1 may be the same as Step 1 in Figure 1.

[0105] 2. The application server (e.g., AF201) may trigger a network slice replacement and provide an Alternative S-NSSAI for each of the joining S-NSSAIs of the UE3 (or group of UEs) in UDM75 via NEF79 to move existing or new PDU sessions to the Alternative S-NSSAI. Step 2 may be the same as Step 2 in Figure 1.

[0106] 3. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, and AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. -S-NSSAI-1-AF201 is a replacement network slice that provides an Alternative S-NSSAI. AF201 may provide an Alternative S-NSSAI for one or more S-NSSAIs that UE3 subscribes to. -Alternative S-NSSAI- This is an alternative network slice for S-NSSAI-1, i.e., a network slice to which S-NSSAI-1 is replaced. AF201 may provide multiple alternative network slices for each S-NSSAI-1.

[0107] Optionally, AF201 may provide at least one of the following: -Location Parameters- Information represented as a cell or list of cells, TA or list of TAs, or geographical location, meaning that the provided Alternative S-NSSAI is only valid in these locations. -Validity parameter-Alternative S-NSSAI information that can be provided as time, day, or any other expression of duration, in the sense that it is valid during these durations. -APN- Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3. Step 3 may be the same as Step 3 in Figure 1.

[0108] 4. NEF79 may call the Nudm_SDM_Get service operation to perform the following mapping. - Mapping GPSI in the global UE_Id to SUPI according to the information received from UDM75. - Mapping external UE group identities to internal group identifiers according to the information received from UDM75. Step 4 may be the same as Step 4 in Figure 1.

[0109] 5. NEF79 may need to authorize service-specific parameter provisioning requests with UDM75 by sending the Nudm_ServiceSpecificAuthorisation_Create service action as defined in section 4.15.6.7a of 3GPP TS23.502[3]. Step 5 may be the same as Step 5 in Figure 1.

[0110] 6. NEF79 responds to AF201 by sending an Nnef_ServiceParameter_Update response message to confirm the parameter update. Step 6 may be the same as Step 7 in Figure 1.

[0111] 7. NEF79 provides the network slice to be replaced (e.g., S-NSSAI-1) and the Alternative S-NSSAI to PCF73. NEF79 may also provide PCF73 with location parameters, validity parameters, APN, DNN, and user IP address. For example, NEF79 may send an Nnef_ServiceParameter_Update message that includes at least one of the following: UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address. For example, NEF79 may provide at least one of the following through other existing or new services between NEF79 and PCF73: UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address.

[0112] 8. PCF73 provides AMF70 with at least one of S-NSSAI-1 and Alternative S-NSSAI. PCF73 may also provide AMF70 with at least one of location parameters, validity parameters, APN, DNN, and user IP address. For example, PCF73 may send an Npcf_AMPolicyControl_UpdateNotify message that includes at least one of the following: UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address.

[0113] 9. If AMF70 receives S-NSSAI-1 and Alternative S-NSSAI in step 8, AMF70 triggers a PDU session correction procedure, as in step 1h of section 4.3.3.2 of 3GPP TS23.502[3], to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI. The AMF70 may refer to the user IP address in step 8 (for example, the user IP address received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI. The AMF70 may refer to at least one of the APN and DNN in step 8 (for example, at least one of the APN and DNN received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0114] UE3 may indicate to a node(s)(e.g., AMF70) during any procedure (e.g., registration procedure) that it supports the slice replacement function. For example, UE3 may indicate to a node(s)(e.g., AMF70) that it supports the network slice replacement described in this disclosure (e.g., Figure 3). In this case, if UE3 indicates support for the slice replacement function and the S-NSSAI-1 requested by UE3 requires replacement in accordance with the notification from UDM75 in step 8, AMF70 may trigger a PDU session modification procedure to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI.

[0115] Furthermore, if UE3 indicates support for the slice replacement function during registration, and the S-NSSAI-1 requested by UE3 requires replacement in accordance with the notification from PCF73 in step 8, AMF70 triggers a PDU session modification procedure to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI. If AMF70 receives at least one of the location and validity parameters for Alternative S-NSSAI, AMF70 may trigger network slice replacement by Alternative S-NSSAI only at the locations and times permitted by the location and validity parameters. For example, UE3 may demonstrate support for slice replacement functionality, similar to step 9 in Figure 1.

[0116] Furthermore, AMF70 may provide the Alternative S-NSSAI to UE3 in a UE configuration update message or a registration acceptance message in the next registration procedure with UE3, along with at least one of the relevant location parameters and validity parameters. If the Alternative S-NSSAI and at least one of the location parameters and validity parameters are provided, UE3 may use the Alternative S-NSSAI only in locations and times permitted by the location and validity parameters. UE3 does not need to trigger a PDU session request for the Alternative S-NSSAI in locations and times restricted by the location and validity information for that Alternative S-NSSAI. For example, AMF70 may send a UE configuration update message or registration acceptance message to UE3 that includes an Alternative S-NSSAI (for example, indicating that the Alternative S-NSSAI is for S-NSSAI-1). For example, if UE3 receives an Alternative S-NSSAI, UE3 may use the Alternative S-NSSAI instead of S-NSSAI-1 to establish the PDU session. Step 9 may be the same as Step 9 in Figure 1.

[0117] Continue the network trigger PDU session modification from step 1h to Alternative S-NSSAI according to section 4.3.3.2 of 10.3GPP TS23.502[3]. Step 10 may be the same as Step 10 in Figure 1.

[0118] Modification 1 of the first example of the second embodiment For example, the Alternative S-NSSAI and associated location and validity parameters provided to AMF70 in step 8 of Figure 3 may also be used for network slice substitution with the Alternative S-NSSAI for new PDU session establishment. If, after step 8 of Figure 3, UE3 initiates a PDU session establishment request on the network slice for the Alternative S-NSSAI provided to AMF70 in step 8, AMF70 may decide to continue the PDU session establishment procedure on the Alternative S-NSSAI in accordance with section 5.15.19 of 3GPP TS23.501[2], provided that location and validity restrictions allow it, i.e., the Alternative S-NSSAI is permitted at the UE location and the request is made within the time permitted by the validity parameters.

[0119] For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI in step 8, and UE3 initiates a PDU session establishment request on S-NSSAI-1 after step 8, AMF70 may decide to continue the PDU session establishment procedure on Alternative S-NSSAI instead of S-NSSAI-1, in accordance with section 5.15.19 of 3GPP TS23.501[2].

[0120] Modification 2 of the first example of the second embodiment In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh embodiment.

[0121] Modification 3 of the first example of the second aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing. For example, AF201 may know whether UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect.

[0122] Modification 4 of the first example of the second embodiment In step 2, AF201 may trigger an AF trigger request for a slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing but does support network slice replacement support functionality. For example, AF201 may know the capability of UE3 based on the procedure disclosed by the first example of the seventh embodiment.

[0123] Third aspect A third aspect includes a mechanism for an application server (e.g., AF201) via NSSF76 to select a network slice for a new PDU session or replace a network slice for an existing PDU session.

[0124] First example of the third aspect: A detailed process of a first example of a third embodiment of the mechanism for network slice selection for a new PDU session or network slice replacement for an existing PDU session via NSSF76 using AF201 is described below with reference to Figure 4. Figure 4: Network slice selection and replacement via AF through NSSF for existing and new PDU sessions (multiple sessions possible).

[0125] 1. The PDU session may be established by UE3 on S-NSSAI-1. Step 1 may be the same as Step 1 in Figure 1.

[0126] 2. An application server (e.g., AF201) may trigger a network slice replacement and provide an Alternative S-NSSAI to each of the joining S-NSSAIs of UE3 (or groups of UEs) in UDM75 via NEF79 in order to move existing or new PDU sessions to the Alternative S-NSSAI. Step 2 may be the same as Step 2 in Figure 1.

[0127] 3. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, and AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. -S-NSSAI-1-AF201 is a replacement network slice that provides an Alternative S-NSSAI. AF201 may provide an Alternative S-NSSAI for one or more S-NSSAIs that UE3 subscribes to. -Alternative S-NSSAI- This is an alternative network slice for S-NSSAI-1, i.e., a network slice to which S-NSSAI-1 is replaced. AF201 may provide multiple alternative network slices for each S-NSSAI-1.

[0128] Optionally, AF201 may provide at least one of the following: -Location Parameters- Information that can be represented as a cell or a list of cells, a TA or a list of TAs, or a geographical location, meaning that the provided Alternative S-NSSAI is only valid at these locations. -Validity parameter-Alternative S-NSSAI is valid during a time interval, and this information can be provided as time, days, or any other expression for that time interval. APN - Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3. Step 3 may be the same as Step 3 in Figure 1.

[0129] 4. NEF79 may call the Nudm_SDM_Get service operation to perform the following mapping. - Mapping GPSI in the global UE_Id to SUPI according to the information received from UDM75. - Mapping external UE group identities to internal group identifiers according to the information received from UDM75. Step 4 may be the same as Step 4 in Figure 1.

[0130] 5. NEF 79 may need to authorize the service-specific parameter provisioning request with UDM 75 by sending the Nudm_ServiceSpecificAuthorisation_Create service operation defined in Section 4.15.6.7a of 3GPP TS23.502 [3]. Step 5 may be the same as Step 5 in Figure 1.

[0131] 6. NEF 79 responds to AF 201 by sending the Nnef_ServiceParameter_Update response message to confirm the parameter update. Step 6 may be the same as Step 7 in Figure 1.

[0132] 7. NEF 79 provides the replaced network slice (e.g., S-NSSAI-1) and Alternative S-NSSAI to NSSF 76. NEF 79 may provide at least one of the location parameter, validity parameter, APN, DNN, and user IP address to NSSF 76. For example, NSSF 76 may send an Nnef_ServiceParameter_Update message including at least one of UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameter, validity parameter, APN, DNN, and user IP address. For example, NSSF 76 may provide at least one of UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameter, validity parameter, APN, DNN, and user IP address via any other existing or new service between NEF 79 and NSSF 76.

[0133] 8. NSSF76 provides AMF70 with at least one of S-NSSAI-1 and Alternative S-NSSAI. NSSF76 may also provide AMF70 with at least one of the following: location parameters, validity parameters, APN, DNN, and user IP address. For example, NSSF76 may send an Nnssf_NSSAIAvailability_Notify message that includes at least one of the following: UE_Id, S-NSSAI-1, Alternative S-NSSAI, location parameters, validity parameters, APN, DNN, and user IP address.

[0134] 9. If UE3 indicates support for slice substitution during registration, and S-NSSAI-1 requested by UE3 requires substitution in accordance with the notification from NSSF76, -In the case of an existing PDU session(s) on S-NSSAI-1, AMF70 triggers a PDU session modification procedure to Alternative S-NSSAI, as in step 1h of section 4.3.3.2 of 3GPP TS23.502[3], -In the case of a new PDU session request on S-NSSAI-1, AMF70 continues establishing the PDU session on Alternative S-NSSAI as in step 3 of section 4.3.2.2.1 of 3GPP TS23.502[3].

[0135] The AMF70 may refer to the user IP address in step 8 (for example, the user IP address received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0136] The AMF70 may refer to at least one of the APN and DNN from step 8 (for example, at least one of the APN and DNN received in step 8) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0137] For example, with respect to an existing PDU session(s) on S-NSSAI-1 (for example, if a PDU session(s) on S-NSSAI-1 is established in step 1), if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI in step 8, AMF70 may trigger a PDU session modification procedure to move the PDU session(s) from S-NSSAI-1 to Alternative S-NSSAI.

[0138] For example, in the case of a new PDU session request on S-NSSAI-1 (for example, if no PDU session(s) have been established on S-NSSAI-1 in step 1), UE3 may trigger a request to establish a PDU session on S-NSSAI-1 by sending a PDU session establishment request message containing at least one of UE_Id, PDU_Session_Id, S-NSSAI-1, and DNN. If AMF70 receives the PDU session establishment request message, AMF70 may continue the PDU session establishment procedure for an Alternative S-NSSAI instead of S-NSSAI-1.

[0139] UE3 may indicate to a node(s)(e.g., AMF70) that it supports the slice replacement functionality during any procedure (e.g., the registration procedure). For example, UE3 may indicate to a node(s)(e.g., AMF70) that UE3 supports the network slice replacement described herein (e.g., Figure 4).

[0140] If UE3 indicates support for slice replacement functionality and S-NSSAI-1 requested by UE3 requires replacement in accordance with the notification from NSSF76 in step 8 (for example, if a PDU session(s) on S-NSSAI-1 is established in step 1 and AMF70 receives an Nnssf_NSSAIAvailability_Notify message from NSSF76), AMF70 may trigger a PDU session modification procedure to move the PDU session(s) from S-NSSAI-1 to an Alternative S-NSSAI for any existing PDU session(s) on S-NSSAI-1.

[0141] If UE3 indicates support for slice replacement functionality, and the S-NSSAI-1 requested by UE3 requires replacement in accordance with the notification from NSSF76 in step 8 (for example, AMF70 receives a PDU session establishment request message from UE3 containing at least one of UE_Id, PDU_Session_Id, S-NSSAI-1, and DNN, and AMF70 receives an Nnssf_NSSAIAvailability_Notify message from NSSF76), then AMF70 may continue the PDU session establishment procedure for the Alternative S-NSSAI instead of S-NSSAI-1 for the new PDU session request on S-NSSAI-1.

[0142] For example, UE3 may demonstrate support for slice replacement functionality, similar to step 9 in Figure 1. For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that a replacement of S-NSSAI-1 is required as requested by UE3.

[0143] For example, if AMF70 receives S-NSSAI-1 and Alternative S-NSSAI, AMF70 may determine that it needs to replace S-NSSAI-1 as requested by UE3, and may perform a PDU session modification procedure for Alternative S-NSSAI or a PDU session establishment procedure for Alternative S-NSSAI.

[0144] Modification 1 of the first example of the third aspect In one example, in step 8 of Figure 4, AMF70 may provide UE3 with an Alternative S-NSSAI along with at least one of the relevant location and validity parameters in a UE configuration update message or in a registration acceptance message in the registration procedure with UE3. If an Alternative S-NSSAI and at least one of the location and validity parameters are provided, UE3 may use the Alternative S-NSSAI only in locations and times permitted by the location and validity parameters. UE3 does not need to trigger a PDU session request for the Alternative S-NSSAI in locations and times restricted by the location and validity information for that Alternative S-NSSAI.

[0145] For example, AMF70 may send a UE configuration update message or registration acceptance message, including an Alternative S-NSSAI, to UE3. For example, if UE3 receives an Alternative S-NSSAI, UE3 may use the Alternative S-NSSAI instead of S-NSSAI-1 for the PDU session establishment procedure or the PDU session modification procedure. For example, if UE3 receives a UE configuration update message or a registration acceptance message, UE3 may use an Alternative S-NSSAI instead of S-NSSAI-1 in the PDU session establishment procedure or the PDU session modification procedure.

[0146] Variation 2 of the first example of the third aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only when AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh aspect.

[0147] Variation 3 of the first example of the third aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only when AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only when AF201 knows that UE3 does not support URSP rule processing.

[0148] Variation 4 of the first example of the third aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only when AF201 knows that UE3 does not support URSP rule processing but supports the network slice replacement support function. For example, AF201 may know the capabilities of UE3 based on the procedure disclosed by the first example of the seventh aspect.

[0149] Fourth aspect The fourth aspect includes a mechanism for network slice selection and replacement by an application server (e.g., AF201) with UE assistance.

[0150] First example of the fourth aspect: The detailed process of the first example of the fourth aspect of the mechanism for network slice selection for new PDU sessions(or more) and network slice replacement for existing PDU sessions(or more) using AF201 with UE3 support is described below with reference to Figure 5. Figure 5: Network slice selection and replacement using AF with UE assistance

[0151] 1. The PDU session is established by UE3 on S-NSSAI-1. Step 1 may be the same as Step 1 in Figure 1.

[0152] 2. The application server (e.g., AF201) may trigger a network slice replacement and provide an Alternative S-NSSAI for each of the joining S-NSSAIs of the UE3 (or group of UEs) in UDM75 via NEF79 to move existing or new PDU sessions to the Alternative S-NSSAI. Step 2 may be the same as Step 2 in Figure 1.

[0153] 3. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, and AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. -S-NSSAI-1-AF201 is a network slice to be replaced, which provides an Alternative S-NSSAI. AF201 may provide an Alternative S-NSSAI for one or more S-NSSAIs that the UE joins. -Alternative S-NSSAI- This is an alternative network slice for S-NSSAI-1, i.e., a network slice to which S-NSSAI-1 is replaced. AF201 may provide multiple alternative network slices for each S-NSSAI-1.

[0154] Optionally, AF201 may provide at least one of the following: -APN- Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3.

[0155] 4. NEF79 may call the Nudm_SDM_Get service operation to perform the mapping in the same way as in step 4 of Figure 1. Step 4 may be the same as Step 4 in Figure 1. NEF79 may need to authorize service-specific parameter provisioning requests with UDM75 by sending the Nudm_ServiceSpecificAuthorisation_Create service action as defined in section 4.15.6.7a of TS23.502[3]. Step 4 may be the same as Step 5 in Figure 1.

[0156] 5. NEF79 responds to AF201 by sending an Nnef_ServiceParameter_Update response message to confirm the parameter update. Step 5 may be the same as Step 7 in Figure 1.

[0157] NEF79 may provide NSSF76 with the network slice to be replaced (e.g., S-NSSAI-1) and the Alternative S-NSSAI. NEF79 may also provide NSSF76 with at least one of the following: DNN, APN, and user IP address. For example, NEF79 may send an Nnef_ServiceParameter_Update message to NSSF76 that includes at least one of the following: UE_Id, S-NSSAI-1, Alternative S-NSSAI, DNN, APN, and user IP address. For example, NEF79 may provide at least one of the following via any other existing or new service between NEF79 and NSSF76: UE_Id, S-NSSAI-1, Alternative S-NSSAI, DNN, APN, and user IP address.

[0158] 6. NSSF76 provides SMF71 with at least one of S-NSSAI-1 and Alternative S-NSSAI. NSSF76 may also provide SMF71 with at least one of the following: DNN, APN, and user IP address. For example, NSSF76 may send an Nnssf_NSSAIAvailability_Notify message that includes at least one of the following: UE_Id, S-NSSAI-1, Alternative S-NSSAI, DNN, APN, and user IP address.

[0159] 7. SMF71 interacts with UE3 via existing or new NAS messages, and SMF71 includes in the message at least one of the following: a PDU session ID (e.g., the PDU session ID of any ongoing PDU session, e.g., S-NSSAI-1), or a network slice to be replaced by an Alternative S-NSSAI, e.g., S-NSSAI-1. SMF71 may refer to the user IP address in step 6 (for example, the user IP address received in step 6) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI.

[0160] SMF71 may refer to at least one of the APN and DNN from step 6 (for example, at least one of the APN and DNN received in step 6) to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI. For example, SMF71 may send an existing or new NAS message to UE3 that includes at least one of the following: PDU session ID (e.g., the PDU session ID of an ongoing PDU session, or the PDU session ID of an ongoing PDU session of S-NSSAI-1), S-NSSAI-1, or Alternative S-NSSAI. SMF71 may also include at least one of the following in the existing or new NAS message: DNN and APN.

[0161] 8. If UE3 determines that a PDU session exists for S-NSSAI-1 (for example, a PDU session for S-NSSAI-1 was established in step 1), UE3 moves the data from the PDU session associated with S-NSSAI-1 to the PDU session associated with Alternative S-NSSAI. For example, UE3 may trigger a PDU session correction procedure in accordance with the UE trigger PDU session correction procedure from step 1a of section 4.3.3.2 of 3GPP TS23.502[3] to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI. Otherwise (for example, if there is no PDU session on S-NSSAI-1 (or if a PDU session on S-NSSAI-1 is not established in step 1) and the establishment of a PDU session on S-NSSAI-1 is required), UE3 will start establishing a PDU session on Alternative S-NSSAI instead of S-NSSAI-1, following the PDU session establishment procedure in section 4.3.3.2.1 of 3GPP TS23.502[3].

[0162] Modification 1 of the first example of the fourth aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh embodiment.

[0163] Modification 2 of the first example of the fourth aspect In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 2, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing. For example, AF201 may know whether UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect.

[0164] Modification 3 of the first example of the fourth aspect In step 2, AF201 may trigger an AF trigger request for a slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing but does support network slice replacement support functionality. For example, AF201 may know the capability of UE3 based on the procedure disclosed by the first example of the seventh embodiment.

[0165] Fifth aspect A fifth aspect includes a mechanism for replacing network slices for an existing PDU session(s) using UE3 subscription information.

[0166] First example of the fifth aspect A detailed process of the first example of a fifth aspect of the mechanism for network slice replacement for existing PDU sessions(s) using UE3 subscription information is described below with reference to Figure 6. Figure 6: Network slice selection and replacement using UE subscription information

[0167] 1. UE3 initiates the registration procedure toward AMF70 to register with the network by sending a registration request message. UE3 includes an Alternative S-NSSAI in the registration request message for each S-NSSAI included in the requested NSSAI. For example, S-NSSAI-2 is shown as an Alternative S-NSSAI for S-NSSAI-1. For example, UE3 sends a registration request message that includes a request NSSAI containing S-NSSAI-1, and at least one S-NSSAI-2 which is an alternative S-NSSAI for S-NSSAI-1.

[0168] 2. The AMF70 continues the registration procedure and sends a Nudm_UECM_Registration request message to the UDM75, in which the AMF70 includes the requested network slices, along with any alternative network slices for them. For example, the AMF70 may include request S-NSSAI-1 and alternative S-NSSAI-2 in the Nudm_UECM_Registration request message. For example, AMF70 may send a Nudm_UECM_Registration request message to UDM75 that includes at least one of S-NSSAI-1 and S-NSSAI-2. For example, AMF70 may send a Nudm_UECM_Registration request message to UDM75 that includes at least one of S-NSSAI-1, which is included in the request NSSAI, and S-NSSAI-2, which is an Alternative S-NSSAI. For example, AMF70 may send a Nudm_UECM_Registration request message to UDM75 that includes at least one of a request NSSAI containing S-NSSAI-1 and an Alternative S-NSSAI, S-NSSAI-2.

[0169] 3. The UDM75 stores the Alternative S-NSSAI(s) received from the AMF70 in the UE3 subscription information within the UDM75 (or UDR) for the network slice they substitute. For example, Alternative S-NSSAI-2 is stored as an Alternative S-NSSAI for S-NSSAI-1. For example, the UDM75 may store S-NSSAI-2 as an Alternative S-NSSAI for S-NSSAI-1. The UDM75 confirms the registration of the UE3 by sending a Nudm_UECM_Registration response message. For example, UDM75 may store Alternative S-NSSAI associated with S-NSSAI-1.

[0170] For example, UDM75 can update the stored Alternative S-NSSAI based on the received Alternative S-NSSAI.

[0171] 4. The UE3 registration process is completed by sending a registration acceptance message to UE3 via AMF70. For example, UE3 may receive a registration acceptance message from AMF70. The registration acceptance message may include an Allowed NSSAI, which may include S-NSSAI-1.

[0172] 5. At some point, UE3 triggers a PDU session establishment request on S-NSSAI-1. UE3 may also indicate an alternative network slice to the requested S-NSSAI-1, e.g., Alternative S-NSSAI-2. For example, UE3 may send a PDU session establishment request message to SMF71 that includes at least one of S-NSSAI-1 and S-NSSAI-2 as an Alternative S-NSSAI for S-NSSAI-1. S-NSSAI-2 as an Alternative S-NSSAI may be represented as Alternative S-NSSAI-2.

[0173] 6. The PDU session establishment procedure continues in accordance with 3GPP TS23.502[3], and the PDU session on S-NSSAI-1 is established.

[0174] 7. An application server, such as AF201, may monitor the PDU session and decide to move the PDU session from S-NSSAI-1 to Alternative S-NSSAI-2 in order to improve the quality of the connection or to alleviate congestion on S-NSSAI-1 (or on the network slice indicated by S-NSSAI-1). Step 7 may be the same as Step 2 in Figure 1.

[0175] 8. AF201 uses the service parameter update service to send an Nnef_Service_Parameter_Update request message to NEF79, where AF201 includes at least one of the following in the Nnef_Service_Parameter_Update request message: -Global UE_Id- The global UE_Id defines the UE3 to which network slice replacement is required and may be represented in GPSI format. The external UE group identity may also be used to define multiple UEs to which the network slice replacement request applies. - Replace S-NSSAI-1-UDM75: If an Alternative S-NSSAI is available in the UE3 subscription, the network slice or S-NSSAI that will be replaced by the Alternative S-NSSAI. For example, Replace S-NSSAI-1 may be represented as Replace S-NSSAI. For example, Replace S-NSSAI may indicate S-NSSAI-1 or be set to S-NSSAI-1. For example, Replace S-NSSAI may indicate an S-NSSAI that will be replaced by an Alternative S-NSSAI. Replace S-NSSAI-1 may indicate that S-NSSAI-1 will be replaced by Alternative S-NSSAI-2.

[0176] Optionally, AF201 may provide either a DNN or an APN. -APN- Access Point Name. -DNN - Data Network Name (DNN) is equivalent to APN in EPS. -User IP address- The IP address assigned to UE3.

[0177] 9. NEF79 may invoke the Nudm_SDM_Get service operation to map GPSI in the global UE_Id to SUPI, and NEF79 may need to authorize service-specific parameter provisioning requests using UDM75. Step 9 may be the same as at least one of steps 4 and 5 in Figure 1.

[0178] 10. UDM75 selects Alternative S-NSSAI-2 for S-NSSAI-1 based on UE3 subscription information and updates the UE3 policy within PCF73. For example, UDM75 may receive substitution S-NSSAI-1 from NEF79 in step 9. For example, since UDM75 has stored S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1 in step 3, if UDM75 receives a substitute S-NSSAI-1 from NEF79, UDM75 may select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1. For example, UDM75 may contact PCF73 to update the policy of UE3 within PCF73. For example, UDM75 may send a request to PCF73 to update the policy of UE3 within PCF73. The request may include at least one of the following: UE_Id (e.g., SUPI), S-NSSAI-1, and S-NSSAI-2 as an Alternative S-NSSAI for S-NSSAI-1. The request may also include at least one of the following: DNN, APN, and user IP address.

[0179] For example, when PCF73 receives a request, PCF73 may update the UE3 policy. For example, PCF73 may update the information regarding network slice(s) in the UE3 policy. For example, PCF73 may update the UE3 policy so that S-NSSAI-2 is preferred by UE3 over S-NSSAI-1. For example, PCF73 may update the UE3 policy so that S-NSSAI-2 is preferred by UE3 over S-NSSAI-1 when UE3 performs a registration procedure or a PDU session establishment procedure. When PCF73 receives at least one of the DNN, APN, and user IP address, PCF73 may update the UE3 policy so that S-NSSAI-2 is preferred by UE3 over S-NSSAI-1 for the DNN or APN.

[0180] PCF73 may refer to the user IP address from UDM75 to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI. PCF73 may refer to at least one of the APN and DNN from UDM75 to find the PDU session to be modified from S-NSSAI-1 to Alternative S-NSSAI. PCF73 may submit the updated UE3 policy to UE3.

[0181] 11. PCF73 triggers a request for network slice substitution to AMF70, for example, a request to substitute S-NSSAI-1 with Alternative S-NSSAI-2 (or S-NSSAI-2). This means that PDU sessions on S-NSSAI-1 need to be transferred to Alternative S-NSSAI-2. For example, PCF73 may send a request to AMF70 that includes at least one of UE_Id, S-NSSAI-1, and S-NSSAI-2 as an Alternative S-NSSAI. For example, if PCF73 receives a request from UDM75, or if PCF73 updates the policy for UE3, PCF73 may send a request to AMF70 that includes at least one of UE_Id, S-NSSAI-1, and S-NSSAI-2 as an Alternative S-NSSAI. S-NSSAI-2 as an Alternative S-NSSAI may be represented as Alternative S-NSSAI-2.

[0182] Alternatively, a request to AMF70 to replace S-NSSAI-1 with Alternative S-NSSAI-2 may be triggered by NSSF76 via Nnssf_NSSAIAvailability_Notify in accordance with section 5.2.16.3.3 of TS23.502[4]. For example, NSSF76 may receive at least one of the following from other network nodes (e.g., UDM75, PCF73, etc.): UE_Id, S-NSSAI-1, S-NSSAI-2 as Alternative S-NSSAI for S-NSSAI-1, DNN, APN, and user IP address. In this case, NSSF76 may send at least one of the following to AMF70: UE_Id, S-NSSAI-1, S-NSSAI-2 as Alternative S-NSSAI for S-NSSAI-1, DNN, APN, and user IP address.

[0183] 12.AMF70 triggers a PDU session modification procedure for slice substitution from S-NSSAI-1 to Alternative S-NSSAI-2, in accordance with section 5.15.19 of 3GPP TS23.501[2].

[0184] Continue modifying the network triggered PDU session to Alternative S-NSSAI according to step 1h of section 4.3.3.2 of 13.3GPP TS23.502[3].

[0185] For example, if a PDU session establishment request message is sent after step 11 and AMF70 receives the PDU session establishment request message, AMF70 may perform the PDU session establishment procedure for the Alternative S-NSSAI instead of S-NSSAI-1.

[0186] Modification 1 of the first example of the fifth aspect In one example, after a PDU session is established on S-NSSAI-1, i.e., after step 6 in Figure 6, UE3 and AF201 may exchange information related to the quality of the connection via the application layer. This information can form the basis for AF201's decision in step 7 to trigger network slice replacement.

[0187] For example, if AF201 receives information indicating that the quality of the connection on S-NSSAI-1 has deteriorated, AF201 may perform the process(s) in step 7. For example, if AF201 receives information indicating that S-NSSAI-1 (or the network slice indicated by S-NSSAI-1) is congested, AF201 may perform the process(s) in step 7.

[0188] Modification 2 of the first example of the fifth aspect In step 7, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports the network slice replacement support function. For example, AF201 may know that UE3 supports the network slice replacement support function based on the procedure disclosed by the first example of the seventh aspect.

[0189] Modification 3 of the first example of the fifth aspect In step 7, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 supports URSP rule processing. For example, AF201 may know that UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect. In step 7, AF201 may trigger an AF trigger request for the slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing. For example, AF201 may know whether UE3 supports URSP rule processing based on the procedure disclosed by the first example of the seventh aspect.

[0190] Modification 4 of the first example of the fifth aspect In step 7, AF201 may trigger an AF trigger request for a slice replacement procedure only if AF201 knows that UE3 does not support URSP rule processing but does support network slice replacement support functionality. For example, AF201 may know the capability of UE3 based on the procedure disclosed by the first example of the seventh aspect.

[0191] Sixth aspect The sixth aspect includes a mechanism for obtaining user consent to share confidential information with AF201 (for example, AF201 in this disclosure may be a third-party AF201).

[0192] First example of the sixth aspect: A detailed process of the first example of the sixth aspect of a mechanism for obtaining user consent to share confidential information with a third-party AF201 via NAS is described below with reference to Figure 7. Figure 7: User consent for sharing confidential information with a third-party AF via NAS

[0193] 1. AF201 requests 5GC to share user information, such as user location. For example, AF201 triggers a request to NEF79, including at least one of the following in the request: global UE_Id (e.g., GPSI, the GPSI of UE3) and Application Identity (App_Id). The global UE_Id may be represented as UE ID. The App_Id may be the identity of the application within UE3. For example, AF201 may send a request to NEF79 that includes at least one of the global UE_Id and App_Id. The request may be referred to as a user information request.

[0194] 2. NEF79 calls UDM75 to request user information, including GPSI and App_Id. For example, NEF79 may send a request to UDM75 that includes at least one of GPSI and App_Id.

[0195] 3. UDM75 converts the global UE_Id (e.g., GPSI) to a 3GPP identity (e.g., SUPI, SUPI for UE3) and checks whether AF201 is authorized for the requested service. For example, UDM75 may check whether AF201 is authorized to perform the request. For example, UDM75 may pre-store or receive from other network nodes to check whether AF201 is authorized to perform the request. For example, if UDM75 determines that AF201 is authorized to carry out the request, UDM75 may proceed to the process(s) in step 4.

[0196] 4. UDM75 checks whether the UE_Id requires user consent for information sharing with AF201. For example, UDM75 may check whether user consent is required for information sharing with AF201 (for example, the user may be identified by a UE_Id (or 3GPP identity (e.g., SUPI))). For example, UDM75 may check whether user consent is required to share information (e.g., user location) with AF201 (e.g., the user may be identified by a UE_Id (or 3GPP identity (e.g., SUPI))). For example, UDM75 may pre-store information to confirm whether the UE_Id requires user consent, or it may receive this information from other network nodes, in order to share information with AF201. For example, UDM75 may pre-store information to determine whether user consent is required, or it may receive this information from other network nodes.

[0197] 5. If a user with a UE_Id requires user consent to share information with AF201 (or if UDM75 determines that user consent is required), UDM75 triggers a request for user consent from AMF70. For example, UDM75 may send a request to AMF70 that includes at least one of UE_Id and App_Id.

[0198] 6. The AMF70 forwards the user consent request to the UE3 via NAS signaling.

[0199] 7. The user agrees to share information with AF201. For example, if UE3 receives a request from AMF70, UE3 may display a confirmation screen on its screen to ask the user whether it can share information (e.g., user location) with AF201. If the user confirms that they can share information (such as user location) with AF201 (for example, if the user presses the "Yes" button displayed on the UE3 screen, it can be assumed that the user has confirmed that they can share information (such as user location) with AF201), UE3 may proceed to step 8(or more).

[0200] 8. In NAS signaling, UE3 sends a user consent response to AMF70, and UE3 includes the UE_Id and App_Id related to user consent in the user consent response. For example, UE3 may send a user consent response to AMF70 that includes at least one of UE_Id and App_Id. For example, UE3 may send a user consent response to AMF70 that includes at least one of the UE_Id and App_Id related to user consent.

[0201] 9. AMF70 transmits or forwards the user consent response to UDM75.

[0202] 10. UDM75 stores user consent about the App_Id (or the application indicated by the App_Id) in the UE3 subscription information within UDM75.

[0203] 11. UDM75 sends a user consent response to NEF79.

[0204] 12. NEF79 forwards the user consent response to AF201.

[0205] 13. After obtaining user consent, AF201 may make a decision to select or replace a network slice for the user based on the QoS of the user's ongoing PDU session(s) indicated by the UE_Id. For example, after obtaining user consent, AF201 may make an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6. For example, after obtaining user consent, AF201 may make an AF trigger request for slice replacement, as described in at least one of Figures 1, 2, 3, 4, 5, and 6, to the user indicated by UE_Id.

[0206] For example, AF201 may pre-store or receive from other network nodes information regarding the QoS of ongoing PDU sessions. For example, AF201 may pre-store or receive from other network nodes information regarding the QoS of ongoing PDU sessions for each user.

[0207] For example, if the information indicates that the QoS (or quality of connection) for a PDU session on S-NSSAI-1 (or on a network slice indicated by S-NSSAI-1) will be poor, AF201 may decide to make an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, or S-NSSAI-2 as an alternative S-NSSAI to S-NSSAI-1).

[0208] For example, if the information indicates that congestion has occurred for S-NSSAI-1 (or the network slice indicated by S-NSSAI-1), AF201 may decide to make an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, or it may select S-NSSAI-2 as the alternative S-NSSAI for S-NSSAI-1). For example, if user consent is positive (e.g., a UE3 user indicates consent to sharing information with AF201), AF201 may proceed with the process(s) in step 13.

[0209] A second example of the sixth aspect: A detailed process of the second example of the sixth aspect of a mechanism for obtaining user consent to share confidential information with a third-party AF201 via an application is described below with reference to Figure 8. Figure 8: User consent for sharing confidential information with third-party AFs via the application.

[0210] 1. AF201 triggers a request to UE3 for information sharing via the application layer. For example, AF201 may request an application within UE3 to share information such as user location, signal coverage level, and signal quality by sending application layer messages via the application layer. The information requested to be shared may include information on signal strength and signal quality, and at least one of QoS and QoE. For example, AF201 may request an application within UE3 to share information about an ongoing PDU session(s) for UE3. For example, AF201 may request applications within UE3 to share information about the PDU session(s) currently running on S-NSSAI-1. For example, AF201 may request the sharing of information about S-NSSAI-1 from an application within UE3.

[0211] 2. Applications within UE3 will warn UE3 users about the necessary consents required by AF201. For example, an application within UE3 may display an alert on the User Interface (UI) (for example, on the UE3 screen) indicating that user consent is required to share information with AF201.

[0212] 3. Users will be given the option to allow or deny information sharing with AF201. For example, an application within UE3, or UE3 itself, may display a confirmation screen on the UE3 screen to ask the user whether or not it is possible to share information with AF201.

[0213] 4. User choices, such as given consent to information sharing, are communicated to AF201 at the application level. For example, an application within UE3 may send information indicating whether the user has confirmed that it is shareable with AF201. If the user confirms that information sharing with AF201 is possible (for example, if the user presses the "Yes" button displayed on the UE screen, it can be considered that the user has confirmed that information sharing with AF201 is possible), the application within UE3 may send information indicating that the user has confirmed that information sharing with AF201 is possible to AF201 via the application layer in step 4.

[0214] 5. The user shares information with AF201 via the application layer (for example, location information, signal coverage level, signal quality, etc.). For example, if the user confirms that information can be shared with AF201, the application within UE3 may send information to AF201 via the application layer (such as location information, signal coverage level, signal quality, etc.). For example, the information sent may relate to one or more ongoing PDU sessions in UE3. For example, the information transmitted may relate to an ongoing PDU session(s) on S-NSSAI-1. For example, the information transmitted may be related to S-NSSAI-1.

[0215] 6. After obtaining user consent and information (e.g., information regarding at least one of the following: user location, signal coverage level, signal quality, signal strength and quality, QoS and QoE), AF201 may make a decision to select or replace a network slice for the user based on the information obtained about the user's ongoing PDU session(s) indicated by the UE_Id(e.g., global UE_Id(e.g., GPSI, GPSI of UE3)). For example, AF201 may, based on the acquired information, make an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6. For example, if information indicates that the QoS (or quality of connection) for a PDU session on S-NSSAI-1 (or on a network slice indicated by S-NSSAI-1) has deteriorated, AF201 may decide to execute an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1, and execute the associated process(s) for replacing the network slice).

[0216] For example, if the information indicates that at least one of the signal coverage level, signal quality, and signal strength and quality has deteriorated (for example, if the information indicates that at least one of the signal coverage level, signal quality, and signal strength and quality has deteriorated below a predetermined threshold), AF201 may decide to execute an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, or select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1).

[0217] Information relating to at least one of the following may be expressed as status information, communication status, etc.: user location, signal coverage level, signal quality, signal strength and quality, QoS and QoE. For example, if the communication status satisfies a predetermined condition or status, AF201 may decide to execute an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1, or execute the associated process(s) for replacing the network slice).

[0218] Third example of the sixth aspect: A detailed process for the third example of the sixth aspect of the mechanism for obtaining user consent to share confidential information from NWDAF74 with third-party AF201 is described below with reference to Figure 9. Figure 9: User consent for sharing confidential information with third-party AFs from NWDAF

[0219] 1. AF201 requires analysis information from NWDAF74. AF201 triggers a request for information sharing to NEF79, and AF201 includes at least one of the following in the request: global UE_Id (e.g., GPSI, GPSI for UE3) or Application Identity (App_Id). For example, AF201 may send a request to NEF79 that includes at least one of the global UE_Id and App_Id. The analysis information may include information for performing the process(s) in step 13 of Figure 7 or the process(s) in step 6 of Figure 8 (for example, at least one of the following: user location, signal coverage level, signal quality, signal strength and quality, QoS and QoE).

[0220] 2. NEF79 interacts with UDM75 to resolve the global UE_Id and obtain the UE3's 3GPP identity (e.g., UE3's SUPI), and then NEF79 forwards an information sharing request, including the SUPI and App_Id, to NWDAF74. For example, if NEF79 receives at least one of the global UE_Id and App_Id, NEF79 may send at least one of the global UE_Id and App_Id to UDM75. For example, if UDM75 receives at least one of the global UE_Id and App_Id, UDM75 may convert the global UE_Id (e.g., GPSI) to a 3GPP identity (e.g., SUPI, SUPI for UE3). If UDM75 converts a global UE_Id (e.g., GPSI) to a 3GPP identity (e.g., SUPI, SUPI for UE3), UDM75 may send the 3GPP identity to NEF79. If NEF79 receives a 3GPP identity, NEF79 may send an information sharing request to NWDAF74. The request may include at least one of the following: the 3GPP identity (e.g., SUPI) and the App_Id.

[0221] 3. NWDAF74 confirms with UDM75 whether the requested information sharing requires user consent.

[0222] 4. NWDAF74 sends a request for consent to share information to UDM75. For example, if NWDAF74 receives a request from NEF79, NWDAF74 may send a request for consent to information sharing to UDM75. For example, if NWDAF74 receives a request from NEF79, NWDAF74 may send a request to UDM75 to confirm whether the requested information sharing requires user consent. Requests sent to UDM75 may include at least one of the following: UE_Id (e.g., SUPI) and App_Id.

[0223] 5. If user consent is required for the information to be shared, UDM75 follows steps 5-10 in Figure 7. For example, if UDM75 receives a request from NWDAF74, UDM75 may perform step 5 in Figure 7, and then perform subsequent processes (multiple processes) (for example, steps 6 to 10 in Figure 7).

[0224] 6. UDM75 forwards the user consent received from UE3 to NWDAF74.

[0225] 7. If user consent from UE3 is positive (for example, if user consent indicates that the user in UE3 agrees to share analytics information with AF201), NWDAF74 sends the requested analytics information, at least one of the associated UE_Id and App_Id to NEF79. The requested analysis information may include information for performing the process(s) in step 13 of Figure 7 or the process(s) in step 6 of Figure 8. The requested analysis information may include at least one of the following: user location, signal coverage level, signal quality, signal strength and quality, QoS and QoE. The requested analysis information may also be expressed as communication status.

[0226] 8. NEF79 forwards the analysis information received from NWDAF74 to AF201.

[0227] 9. Based on the received analysis information, AF201 determines whether to replace the network slice. For example, AF201 may perform the process(s) shown in step 13 of Figure 7 or the process(s) shown in step 6 of Figure 8 based on the analysis information.

[0228] Seventh aspect A seventh aspect includes a mechanism for instructing UE URSP support to 5GC and AF201.

[0229] First example of the seventh aspect: A detailed process of the first example of the seventh aspect for the mechanism for instructing UE URSP support to 5GC and AF201 is described below with reference to Figure 10. Figure 10: Instructions for URSP support to 5GC and AF

[0230] 1. During UE3 registration (e.g., during the registration procedure), UE3 sends a registration request message to AMF70 that includes at least one of the following: User ID, Network Slice Replacement Support, and URSP Support. The User ID represents the UE3's identity, e.g., 5G-GUTI or SUCI. Network slice replacement support demonstrates UE3's ability to support the network slice replacement feature, as described in 3GPP TS23.501[2].

[0231] URSP support indicates the UE3's ability to support URSP rule processing in accordance with 3GPP TS23.503[4]. URSP support may also indicate that the UE3 can understand, use, or process URSP rules. URSP support may indicate that the UE3 supports URSP rules. URSP support may indicate that the UE3 can determine how to route outgoing traffic using URSP rules. URSP support can indicate the ability to report URSP rule enforcement to the network. URSP support may indicate that the UE3 supports reporting URSP rule enforcement to the network. Support for URSP rules may be coded as a negative expression, e.g., URSP not supporting indicator, or URSP not supported. URSP support may indicate that the UE3 does not support URSP rule processing. URSP support may indicate that the UE3 does not support reporting URSP rule enforcement to the network. URSP support may indicate that the UE3 cannot understand, use, or process URSP rules. URSP support may indicate that UE3 does not support URSP rules. URSP support may indicate that UE3 cannot determine how to route outgoing traffic using URSP rules. URSP rule processing may include reporting URSP rule enforcement to the network, understanding, using, or processing URSP rules, or determining how to route outgoing traffic using URSP rules.

[0232] For example, UE3 may transmit at least one of network slice replacement support and URSP support in any procedure other than the registration procedure. Network slice replacement support may be described as information indicating that UE3 supports the network slice replacement feature. For example, only UE3 instances that can understand, use, or process URSP rules may include URSP support in their registration request messages. For example, UE3 instances that cannot understand, use, or process URSP rules may not include URSP support in their registration request messages. The URSP rule may also be represented as URSP.

[0233] 2. Upon receiving a registration request message, the AMF70 stores the UE3's network slice replacement support (e.g., network slice replacement support) and URSP functionality (e.g., URSP support) in the UE3 context (e.g., UE context(s) for UE3) within the AMF70. AMF70 may provide URSP updates to UE3 via a UE configuration update message or registration acceptance message only if UE3 indicates support for the URSP function (e.g., URSP support) during the registration procedure. AMF70 sends a Nudm_UECMRegistration request message to UDM75 that includes at least one of the following: user ID, network slice replacement support, and URSP support.

[0234] 3. When UDM75 receives a Nudm_UECMRegistration request message, it sends a Nudm_UECMRegistration response message to AMF70.

[0235] 4. If NEF79 is subscribed to the Nudm SDM service as described in 3GPP TS23.502[3], UDM75 sends a Nudm_SDM_Notification message to NEF79 that includes at least one of the following: user ID, network slice replacement support, and URSP support.

[0236] 5. If AF201 is subscribed to the Nnef EventExposure service as described in 3GPP TS23.502[3], NEF79 sends an Nnef_EventExposure_Notify message to AF201 that includes at least one of the following: user ID, network slice replacement support, or URSP support. For example, based on URSP support, AF201 may make decisions for network slice selection or network slice replacement for a user indicated by a user ID.

[0237] For example, if URSP support indicates that UE3 does not support URSP rule processing (for example, if URSP support indicates that UE3 cannot understand, use, or process URSP rules, or if AF201 does not receive URSP support, or if AF201 does not receive URSP support because UE3 does not include URSP support in the registration request message), AF201 may decide on a network slice selection or network slice replacement for the user indicated by the user ID (for example, AF201 may execute an AF trigger request for slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1, or execute the associated process(s) for replacing the network slice)).

[0238] For example, if URSP support indicates that UE3 supports URSP rule processing (for example, if URSP support indicates that UE3 can understand, use, or process URSP rules), AF201 may determine a network slice selection or network slice replacement for the user indicated by the user ID (for example, AF201 may execute an AF trigger request for a slice replacement as described in at least one of Figures 1, 2, 3, 4, 5, and 6 (for example, AF201 may select S-NSSAI-1 to be replaced, select S-NSSAI-2 as an alternative S-NSSAI for S-NSSAI-1, or execute any associated process(s) for replacing the network slice)).

[0239] 6. The AMF70 sends a registration acceptance message, including 5G-GUTI, to the UE3. For example, if AMF70 receives a Nudm_UECMRegistration response message from UDM75, AMF70 may send a registration acceptance message.

[0240] Modification 1 of the third example of the seventh aspect Step 4 may be a different Nudm service message. The message in Step 4 may be, for example, a Nudm_EventExposure_Notify message, or another existing Nudm service message, or a new Ndum service message, or an existing Nnef service message, or a new Nnef service message.

[0241] Modification 2 of the third example of the seventh aspect Step 5 may be a different Nnef service message. The message in Step 5 may be, for example, an Nnef_PFDManagement_Notify message, an Nnef_Trigger_Delivery message, an Nnef_Trigger_DeliveryNotify message, an Nnef_APISupportCapability_Notify message, or another existing Nnef service message or a new Nnef service message.

[0242] According to at least one of the above embodiments or at least one of the above modifications, for example, the above-mentioned problems (multiple problems) can be solved. For example, at least one of the above embodiments or at least one of the above modifications can solve the problem that the 3GPP standard does not have a mechanism for supporting network slice selection and replacement by a network. For example, at least one of the above embodiments or at least one of the above modifications proposes a procedure(s) to support network-based network slice selection and replacement, thereby solving the problem that there is no mechanism in the 3GPP standard to support network-based network slice selection and replacement. According to at least one of the above embodiments or at least one of the above modifications, for example, it is possible to provide the UE with connectivity on a network slice that is best optimized, taking into account application and service characteristics.

[0243] System Overview Figure 11 schematically shows a telecommunications system 1 for mobile (cellular or wireless) to which the above embodiment can be applied. 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.

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

[0245] (R)AN node 5 can be divided into Radio Unit (RU), Distributed Unit (DU), and Centralized Unit (CU). In some embodiments, each of the units 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, with the above units corresponding to O-RU, O-DU, and O-CU, respectively.

[0246] (R)AN node 5 can be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions can be allocated to support 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 is sometimes referred to as "dual connectivity" or "multi-connectivity".

[0247] (R)AN node 5 can also support communications using satellite access. In some embodiments, (R)AN node 5 can support both satellite and terrestrial access. Furthermore, (R)AN node 5 may also be referred to as 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).

[0248] The core network 7 may include logical nodes (or "functions") for supporting communication in the telecommunications system 1. For example, the core network 7 can 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). Network functions can be deployed as a distributed, redundant, stateless, and scalable system that provides services from multiple locations and multiple execution instances at each location, by adapting network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSINFV). 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).

[0249] As is well known, when a UE3 is moving within the geographic area covered by the telecommunications system 1, the UE3 can enter and exit the area (i.e., radio cell) serviced by the (R)AN node 5. To track the 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.

[0250] 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, a Network Slice Selection Function (NSSF) 76, and a Network Slice Admission Control Function (NSACF) 77. 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, PCF 73, and NSACF 77.

[0251] 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 node 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) via appropriate interfaces (e.g., so-called "N2" / "N3" interfaces(or more). 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 the 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 an Application Function (AF) 201.

[0252] The "Uu" interface may include the control plane of the Uu interface and the user plane of the Uu interface. 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 may have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers via physical connections. The Uu interface control plane is responsible for establishing, fixing, and releasing connections between UE3 and Serving(R)AN node 5. The Uu interface control plane may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers via physical connections. For example, to support AS signaling, the following message is communicated via the RRC layer.

[0253] RRC setup request message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may 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 a random value. RRC Setup Message: This message is sent from (R)AN node 5 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be included together in the RRC setup message. >masterCellGroup and radioBearerConfig RRC setup complete message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this disclosure, the following parameters may be included together in the RRC setup complete message. #guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0254] The UE3 and AMF70 are connected via an appropriate interface (e.g., a so-called N1 interface). The N1 interface is responsible for providing communication between the UE3 and AMF70 to support NAS signaling. The N1 interface may be established via 3GPP access and non-3GPP access. For example, the following messages are communicated over 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 classmark 2, 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 disclosure, 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 aspect of 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 aspect of disclosure, the following parameters may be populated together in the authentication response message. >Authentication response message identity, authentication response parameters, 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 populated together with 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 populated together with the authentication failure message. Authentication failure message, identity, 5GMM cause, and authentication failure parameters. Authentication denial message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be populated together with the authentication denial 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 populated together with the service request message. >ngKSI, service type, 5G-S-TMSI, uplink data status, PDU session status, authorized PDU session status, NAS message container. Service Acceptance Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be populated together with the service acceptance message. >PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value. Denial of Service Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be populated together with the denial of service 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 aspect of disclosure, the following parameters may be populated together with 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, 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 populated together with the configuration update complete message. >Configuration update complete message identity. Figure 11: System Overview

[0255] User Equipment (UE) Figure 12 is a block diagram showing the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31 capable of transmitting and receiving signals to and from connected nodes(s) via one or more antennas 32. UE3 may also include a user interface 34 for inputting and outputting information externally. Although not necessarily shown, UE3 may have all the usual functions of a conventional mobile device, which may be provided by hardware, software, and firmware, or a combination thereof, as appropriate. The software may 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 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (which uses the transceiver control module 3621) is responsible for processing (generating / transmitting / receiving) signaling and uplink / downlink data packets between the UE3 and other nodes such as the (R)AN node 5 and AMF70. Such signaling may include appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for the UE3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. If multiple USIMs 35 are installed, the controller 33 may activate only one USIM 35 or multiple USIMs 35 simultaneously.

[0256] UE3 may 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). UE3 can be, for example, equipment for production or manufacturing and / or 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).

[0257] 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 may be information and communication equipment (for example, information and communication equipment such as electronic computers and related devices, communication and related devices, and electronic components).

[0258] UE3 can include, for example, refrigerators, refrigerator applications, goods and / or service industry equipment items, vending machines, automated service machines, office equipment, consumer electronics and electronic devices, (such as consumer electronic devices such as audio equipment, video equipment, speakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners, etc.). UE3 can be an electrical application system or device (for example, an electrical application system or device such as an X-ray system, particle accelerator, radioisotope equipment, sound wave equipment, electromagnetic application equipment, or electronic power application equipment).

[0259] UE3 can include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or measuring or sensing devices such as smoke detectors, motion sensors, wireless tags, etc., as well as watches or clocks, inspection equipment, optical devices, medical devices and / or systems, weapons, cutlery products, hand tools, etc.

[0260] UE3 can be, for example, a wirelessly 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, e.g., 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.

[0261] 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 stationary equipment (in most cases). 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 implementable 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.

[0262] It should be understood that IoT devices are sometimes called Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band-IoT UE (NB-IoT UE). It should be understood that UE3 can support one or more IoT or MTC applications. UE3 can be a smartphone or a wearable device (e.g., smart glasses, smartwatch, smart ring, or hearable device). UE3 can be an automobile, connected car, autonomous vehicle, vehicle device, motorcycle, or V2X (Vehicle to Everything) 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). Figure 12: User Equipment (UE)

[0263] (R)AN node Figure 13 is a block diagram showing the main components of an exemplary (R)AN node 5, for example, a base station ("eNB" in LTE, "gNB" in 5G, a base station for 5G and beyond, a base station for 6G). As shown in the figure, the (R)AN node 5 includes a transceiver circuit 51 that can operate to send and receive signals with connected UE3(or more) 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 may be 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.

[0264] The communication control module 552 (which uses the transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between (R)AN node 5 and other nodes such as UE3, another (R)AN node 5, AMF70, and UPF72 (e.g., 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).

[0265] The controller 54, if implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation. (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 may also be represented as RAN node, RAN, (R)AN, etc. Figure 13: (R) AN node

[0266] System Overview of (R)AN Node 5 Based on O-RAN Architecture Figure 14 schematically shows (R)AN node 5 based on an O-RAN architecture to which the (R)AN node 5 configuration can be applied. 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 integrated / coupled with DU 61 as an integration / coupled unit, and DU 61 can be integrated / coupled with CU 62 as another integration / coupled unit. Any function in the description of a unit (e.g., one of RU 60, DU 61, and CU 62) can be implemented in the above integration / coupled 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).

[0267] UE3 and each serving RU60 are connected via appropriate air interfaces (e.g., so-called "Uu" interfaces). Each RU60 is connected to a DU61 via an appropriate interface (e.g., so-called "fronthaul", "open fronthaul", "F1" interface). Each DU61 is connected to a CU62 via an appropriate interface (e.g., so-called "midhaul", "open midhaul", "E2" interface). Each CU62 is also connected to a node in the core network 7 (e.g., so-called core network nodes) via an appropriate interface (e.g., so-called "backhaul", "open backhaul", "N2" / "N3" interfaces(or more)). The user plane portion of the DU61 may also be connected to a core network node via an appropriate interface (e.g., so-called "N3" interfaces(or more)).

[0268] 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 may provide the function to communicate with UE3 via the air interface, DU61 may provide the function to support the MAC layer and RLC layer, and CU62 may provide the function to support the PDCP layer, SDAP layer, and RRC layer. Figure 14: System overview of (R)AN node 5 based on the O-RAN architecture

[0269] Radio Unit (RU) Figure 15 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, base stations for 5G and later, and base stations for 6G). As shown in the figure, the RU60 includes a transceiver circuit 601 that is capable of transmitting and receiving signals to and from connected UE(s)3 via one or more antennas 602, and transmitting and receiving signals (directly or indirectly) to and from other network nodes or network units via a network interface 603. A 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 may be 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.

[0270] The communications control module 6052 (which uses the 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 (e.g., directly or indirectly). The signaling may include appropriately formatted signaling messages, for example, related to the radio connection and the connection with RU60 (for a particular UE3), particularly related to the MAC and RLC layers.

[0271] 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. The RU60 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, RU60 can be integrated / coupled with DU61 as an integration / coupling unit. Any functionality described for RU60 can be implemented in the above integration / coupling unit. Figure 15: Radio Unit (RU)

[0272] Distributed Unit (DU) Figure 16 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, base station for 5G and beyond, base station for 6G). As illustrated, the device includes a transceiver circuit 611 that can operate to transmit signals to and receive signals from 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 may be 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 communications control module 6142 having at least a transceiver control module 61421. The communications 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 and other nodes and units.

[0273] The DU61 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, RU60 may be integrated / combined as a unit with DU61 or CU62. Any function described for DU61 may be implemented in one of the above integrated / combined units. Figure 16: Distributed Unit (DU)

[0274] Centralized Unit (CU) Figure 17 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 communications control module 6242 having at least a transceiver control module 62421. The communications 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 and other nodes and units.

[0275] CU62 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 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. Figure 17: Centralized Unit (CU)

[0276] AMF Figure 18 is a block diagram showing the main components of the AMF70. As shown, the device includes a transceiver circuit 701 that can operate to send and receive signals to and from 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 may be 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 communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / transmitting / receiving) signaling between the AMF70 and other nodes such as UE3 (e.g., via (R)AN node 5) and other core network nodes (including the core network node in HPLMN of UE3 when UE3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for UE3). The AMF70 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 18: AMF

[0277] SMF Figure 19 is a block diagram showing the main components of the SMF71. As shown, the device includes a transceiver circuit 711 that can operate to send and receive signals to and from other nodes (including the AMF70) via a network interface 712. A controller 713 controls the operation of the SMF71 according to software stored in memory 714. The software can be pre-installed in memory 714 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using the transceiver control module 71421) is responsible for handling (generating / transmitting / receiving) signaling between the SMF71 and other nodes such as the AMF70 and other core network nodes (including the core network node in the HPLMN of the UE3 when the UE3 is roaming in). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3).

[0278] The SMF71 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 19: SMF

[0279] UPF Figure 20 is a block diagram showing the main components of UPF72. As shown, the device includes a transceiver circuit 721 that can operate to send and receive signals to and from other nodes (including SMF71) via a network interface 722. A controller 723 controls the operation of UPF72 according to software stored in memory 724. The software can, for example, be pre-installed in memory 724 and / or downloaded 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 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / transmitting / receiving) signaling between UPF72 and other nodes such as SMF71 and other core network nodes (including core network nodes in the HPLMN of UE3 when UE3 is roaming in). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3). UPF72 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 20: UPF

[0280] PCF Figure 21 is a block diagram showing the main components of PCF73. As shown, the device includes a transceiver circuit 731 that can operate to send and receive signals to and from other nodes (including AMF70) via a network interface 732. A controller 733 controls the operation of 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 communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / transmitting / receiving) signaling between PCF73 and other nodes, such as AMF70 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 (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3). PCF73 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 21: PCF

[0281] NWDAF Figure 22 is a block diagram showing the main components of the NWDAF74. As shown, the device includes a transceiver circuit 741 capable of transmitting and receiving signals to and from 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 communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (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 in). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3). The NWDAF74 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 22: NWDAF

[0282] UDM Figure 23 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 to and from 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 may be 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 communications control module 7542 having at least a transceiver control module 75421. The communications 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 node in the VPLMN of the UE3 when the UE3 is roaming out). 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). 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). Figure 23: UDM

[0283] NSSF Figure 24 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 to and from other nodes (including 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 may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / transmitting / receiving) signaling between NSSF76 and other nodes such as AMF70 and other core network nodes (including core network nodes in the VPLMN of UE3 when UE3 is roaming out). 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). NSSF76 may support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). Figure 24: NSSF

[0284] NSACF Figure 25 is a block diagram showing the main components of NSACF77. As shown, the device includes a transceiver circuit 771 capable of transmitting and receiving signals to and from other nodes (including AMF70) via a network interface 772. A controller 773 controls the operation of NSACF77 according to software stored in memory 774. This software can be pre-installed in memory 774 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., removable memory device (RMD)). The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / transmitting / receiving) signaling between NSACF77 and other nodes such as AMF70 and other core network nodes (including core network nodes in the HPLMN of UE3 when UE3 is roaming in). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to network data analysis functionality procedures (for UE3). The NSACF77 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). Figure 25: NSACF

[0285] AUSF Figure 26 is a block diagram showing the main components of AUSF78. As shown, the device includes a transceiver circuit 781 capable of transmitting and receiving signals to and from other nodes (including AMF70) via a network interface 782. A controller 783 controls the operation of AUSF78 according to software stored in memory 784. This software can be pre-installed in memory 784 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (e.g., removable memory device (RMD)). The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating / transmitting / receiving) signaling between AUSF78 and other nodes such as AMF70 and other core network nodes (including core network nodes in the HPLMN of UE3 when UE3 is roaming in). Such signaling could include, for example, well-formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to network data analysis functionality procedures (for UE3). The AUSF78 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). Figure 26: AUSF

[0286] AF Figure 27 is a block diagram showing the main components of AF201. As shown, the device includes a transceiver circuit 2011 capable of sending and receiving signals to and from other nodes (including UE3) via a network interface 2012. A controller 2013 controls the operation of AF201 according to software stored in memory 2014. The software can be pre-installed in memory 2014 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 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / transmitting / receiving) signaling between AF201 and other nodes, such as UE3 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 (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3). The AF201 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). Figure 27: AF

[0287] NEF Figure 28 is a block diagram showing the main components of the NEF79. As shown, the device includes a transceiver circuit 791 that can operate to transmit and receive signals to and from other nodes (including AF201 and UDM75) via a network interface 792. A controller 793 controls the operation of the NEF79 according to software stored in memory 794. The software can be pre-installed in memory 794 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7941 and a communications control module 7942 having at least a transceiver control module 79421. The communications control module 7942 (using its transceiver control module 79421) is responsible for handling (generating / transmitting / receiving) signaling between the NEF79 and other nodes such as AF201, UDM75, 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 (e.g., HTTP restful methods based on service-based interfaces) relating to mobility management procedures (for UE3). The NEF79 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). Figure 28: NEF

[0288] Variations and alternative examples Detailed embodiments are described above. As those skilled in the art will understand, several modifications and substitutions can be made to the above embodiments while still benefiting from the disclosures embodied herein. Only a few of these substitutions and modifications are described here as examples.

[0289] In the above description, the UE3 and network device are described as having several separate modules (such as a communications control module) for ease of understanding. These modules may be provided in this way for a specific application, for example, when an existing system is modified to implement the disclosure. However, for other applications, for example, a system designed from the outset with the features of the disclosure in mind, these modules may be incorporated into the operating system or the entire code, and therefore these modules may not be recognized as separate entities. These modules may be implemented in software, hardware, firmware, or a combination thereof.

[0290] Each controller may include, but is not limited to, any suitable form of processing circuitry, including, for example, 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. In the above embodiments, several software modules have been described. As those skilled in the art will understand, these 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, the functions performed by some or all of this software can be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates their updates in order to update the functions of the UE3 and network devices.

[0291] In the above embodiment, 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 embodiment.

[0292] User equipment items may include, for example, communication devices such as mobile phones, smartphones, user devices, personal digital assistants, laptop / tablet computers, web browsers, e-readers, and / or equivalents. Such mobile (or more generally, 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 simplicity, this application refers to mobile devices (or UEs) in the description, but it will be understood that the technology described can be implemented on any communication device (mobile and / or generally fixed) that can connect to a communication network to transmit / receive data, regardless of whether such communication devices are controlled by human input or 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.

[0293] As will be understood by those skilled in the art, this disclosure can be embodied as methods and systems. Accordingly, this disclosure can take the form of entirely hardware embodiments, software embodiments, or embodiments combining software and hardware aspects.

[0294] It will be understood that each block in the block diagram can be implemented by computer program instructions. These computer program instructions may be instructions that are provided to a general-purpose computer, a dedicated computer, or a processor of another programmable data processing device to create a machine, in order to create a means for implementing the functions / operations specified in one or more blocks of the flowchart or block diagram or both. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0295] The methods or algorithms described in relation to the examples disclosed herein may be implemented directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC.

[0296] The preceding descriptions of the disclosed examples are provided to enable those skilled in the art to manufacture or use the disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Accordingly, the disclosure is not limited to the examples shown herein, but should be given the broadest scope that corresponds to the principles and novel features disclosed herein.

[0297] Although the present disclosure has been described above with reference to embodiments, the present disclosure is not limited to the embodiments described above. It is clear that a person with ordinary skill in the art to which the present disclosure belongs can conceive of various modifications or alterations within the scope of the technical idea described in the claims, and these are also understood to be within the technical scope of the present disclosure. For example, the above embodiments are not limited to 5GS but are also applicable to communication systems other than 5GS (e.g., 6G systems, 5G beyond systems).

[0298] Note Some or all of the exemplary embodiments disclosed above may also be described as follows, but are not limited to: (Note 1) A method for a first communication device, To communicate with the second communication device, A method including transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI). (Note 2) Alternative S-NSSAI is sent after receiving user consent for User Equipment (UE). The method described in Appendix 1. (Note 3) Alternative S-NSSAI is transmitted after the communication status meets a predetermined status. The method described in Appendix 1. (Note 4) This further includes receiving information indicating that User Equipment (UE) supports the network slice replacement function, Alternative S-NSSAI is transmitted after receiving information. The method described in Appendix 1. (Note 5) This further includes receiving information indicating that User Equipment (UE) supports processing UE Route Selection Policy (URSP) rules, Alternative S-NSSAI is transmitted after receiving information. The method described in Appendix 1. (Note 6) This further includes receiving first information indicating that the User Equipment (UE) supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules, Alternative S-NSSAI is transmitted after receiving the first and second pieces of information. The method described in Appendix 1. (Note 7) The first communication device is an Application Function (AF). The method described in any one of the appendices 1 to 6. (Note 8) The first communication device is Unified Data Management (UDM). The method described in Appendix 1. (Note 9) The first communication device is a Network Exposure Function (NEF). The method described in Appendix 1. (Note 10) A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions based on Alternative S-NSSAI, The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM), a method. (Note 11) Procedures related to PDU sessions include PDU session correction procedures. The method described in Appendix 10. (Note 12) The PDU session correction procedure is performed when the User Equipment (UE) receives information indicating that it supports the network slice replacement function. The method described in Appendix 11. (Note 13) The procedures related to PDU sessions include the PDU session establishment procedure, The method described in Appendix 10. (Note 14) The PDU session establishment procedure is performed when the User Equipment (UE) receives information indicating that it supports the network slice replacement function. The method described in Appendix 13. (Note 15) A method for User Equipment (UE), To communicate with the first communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM), a method. (Note 16) Procedures related to PDU sessions include PDU session correction procedures. The method described in Appendix 15. (Note 17) This further includes sending information indicating that the UE supports the network slice replacement function, The PDU session correction procedure is performed when the UE sends information indicating that it supports the network slice replacement function. The method described in Appendix 16. (Note 18) This further includes sending information indicating that the UE supports processing UE Route Selection Policy (URSP) rules, The PDU session remediation procedure is performed when the UE sends information indicating that it supports processing UE Route Selection Policy (URSP) rules. The method described in Appendix 16. (Note 19) This further includes sending a first piece of information indicating that the UE supports network slice replacement functionality, and a second piece of information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session correction procedure is performed when sending the first and second pieces of information. The method described in Appendix 16. (Note 20) The procedures related to PDU sessions include the PDU session establishment procedure, The method described in Appendix 15. (Note 21) This further includes sending information indicating that the UE supports the network slice replacement function, The PDU session establishment procedure is performed when the UE sends information indicating that it supports the network slice replacement function. The method described in Appendix 20. (Note 22) This further includes sending information indicating that the UE supports processing UE Route Selection Policy (URSP) rules, The PDU session establishment procedure is performed as described in Appendix 20 when the UE sends information indicating that it supports processing URSP rules. (Note 23) This further includes sending a first piece of information indicating that the UE supports network slice replacement functionality, and a second piece of information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. When transmitting the first and second pieces of information, the PDU session establishment procedure is performed. The method described in Appendix 20. (Note 24) A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting an Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF). The third communication device is an Access and Mobility Management Function (AMF), according to the method. (Note 25) A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting an Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF). The third communication device is a Session Management Function (SMF). (Note 26) A method for User Equipment (UE), Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the first communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions based on S-NSSAI, The first communication device is a Session Management Function (SMF), according to this method. (Note 27) Procedures related to PDU sessions include PDU session correction procedures. The method described in Appendix 26. (Note 28) The procedures related to PDU sessions include the PDU session establishment procedure, The method described in Appendix 26. (Note 29) A method for a first communication device, To communicate with the second communication device, A method including transmitting S-NSSAI that has been replaced with Alternative Single Network Slice Selection Assistance Information (S-NSSAI). (Note 30) The first communication device is an Application Function (AF). The method described in Appendix 29. (Note 31) A method for User Equipment (UE), This involves sending a registration request message, The registration request message includes Alternative Single Network Slice Selection Assistance Information (S-NSSAI), This involves sending a Protocol Data Unit (PDU) session establishment request message, The PDU session establishment request message includes an Alternative S-NSSAI and a method that includes the following. (Note 32) A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes performing procedures related to Protocol Data Unit (PDU) sessions based on S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF), according to the method. (Note 33) The second communication device is a Policy Control Function (PCF). Procedures related to PDU sessions include PDU session correction procedures. The method described in Appendix 32. (Note 34) The second communication device is User Equipment (UE), The procedures related to PDU sessions include the PDU session establishment procedure, The method described in Appendix 32. (Note 35) A means for communicating with a second communication device, A first communication device comprising means for transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI). (Note 36) Alternative S-NSSAI is sent after receiving user consent for User Equipment (UE). The first communication device described in Appendix 35. (Note 37) Alternative S-NSSAI is transmitted after the communication status meets a predetermined status. The first communication device described in Appendix 35. (Note 38) The User Equipment (UE) further provides means for receiving information indicating that it supports network slice replacement functionality. Alternative S-NSSAI is transmitted after receiving information. The first communication device described in Appendix 35. (Note 39) The User Equipment (UE) further provides a means for receiving information indicating that it supports the processing of UE Route Selection Policy (URSP) rules. Alternative S-NSSAI is transmitted after receiving information. The first communication device described in Appendix 35. (Note 40) The system further includes means for receiving first information indicating that User Equipment (UE) supports network slice replacement functionality, and second information indicating that UE does not support processing UE Route Selection Policy (URSP) rules. Alternative S-NSSAI is transmitted after receiving the first and second pieces of information. The first communication device described in Appendix 35. (Note 41) The first communication device is an Application Function (AF). The first communication device described in any one of the appendices 35 to 40. (Note 42) The first communication device is Unified Data Management (UDM). The first communication device described in Appendix 35. (Note 43) The first communication device is a Network Exposure Function (NEF). The first communication device described in Appendix 35. (Note 44) A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for performing procedures related to a Protocol Data Unit (PDU) session based on Alternative S-NSSAI, The first communication device is the Access and Mobility Management Function (AMF), The second communication device is Unified Data Management (UDM), which is the first communication device. (Note 45) Procedures related to PDU sessions include PDU session correction procedures. The first communication device described in Appendix 44. (Note 46) The PDU session correction procedure is performed when the first communication device receives information indicating that the User Equipment (UE) supports the network slice replacement function. The first communication device described in Appendix 45. (Note 47) The procedures related to PDU sessions include the PDU session establishment procedure, The first communication device described in Appendix 44. (Note 48) The PDU session establishment procedure is performed when the first communication device receives information indicating that the User Equipment (UE) supports the network slice replacement function. The first communication device described in Appendix 47. (Note 49) User Equipment (UE), A means for communicating with the first communication device, The system includes means for performing procedures related to a Protocol Data Unit (PDU) session, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI). Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is the Access and Mobility Management Function (AMF), The second communication device is the Unified Data Management (UDM), or UE. (Note 50) Procedures related to PDU sessions include PDU session correction procedures. UE as described in Appendix 49. (Note 51) The UE further provides a means for transmitting information indicating that it supports network slice replacement functionality, The PDU session correction procedure is performed when the UE sends information indicating that it supports the network slice replacement function. UE as described in Appendix 50. (Note 52) The UE further provides a means for sending information indicating that it supports processing UE Route Selection Policy (URSP) rules, The PDU session remediation procedure is performed when the UE sends information indicating that it supports processing UE Route Selection Policy (URSP) rules. UE as described in Appendix 50. (Note 53) The system further includes means for transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session correction procedure is performed when the UE sends the first and second pieces of information. UE as described in Appendix 50. (Note 54) The procedures related to PDU sessions include the PDU session establishment procedure, UE as described in Appendix 49. (Note 55) The UE further provides a means for transmitting information indicating that it supports network slice replacement functionality, The PDU session establishment procedure is performed when the UE sends information indicating that it supports the network slice replacement function. UE as described in Appendix 54. (Note 56) The UE further provides a means for sending information indicating that it supports processing UE Route Selection Policy (URSP) rules, If the UE sends information indicating that it supports processing URSP rules, the PDU session establishment procedure is executed. UE as described in Appendix 54. (Note 57) The system further includes means for transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session establishment procedure is performed when the UE sends the first and second pieces of information. UE as described in Appendix 54. (Note 58) A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Access and Mobility Management Function (AMF), which is the first communication device. (Note 59) A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF). The third communication device is the Session Management Function (SMF), which is the first communication device. (Note 60) User Equipment (UE), A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a first communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on S-NSSAI, The first communication device is a Session Management Function (SMF), which is the UE. (Note 61) Procedures related to PDU sessions include PDU session correction procedures. UE as described in Appendix 60. (Note 62) The procedures related to PDU sessions include the PDU session establishment procedure, UE as described in Appendix 60. (Note 63) A first communication device, A means for communicating with a second communication device, A first communication device comprising means for transmitting Single Network Slice Selection Assistance Information (S-NSSAI) that has been replaced with Alternative S-NSSAI. (Note 64) The first communication device is an Application Function (AF). The first communication device described in Appendix 63. (Note 65) User Equipment (UE), A means for sending a registration request message, The registration request message includes Alternative Single Network Slice Selection Assistance Information (S-NSSAI), and A means for sending a Protocol Data Unit (PDU) session establishment request message, A PDU session establishment request message includes means, including Alternative S-NSSAI, and is provided by the UE. (Note 66) A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF). (Note 67) The second communication device is a Policy Control Function (PCF). Procedures related to PDU sessions include PDU session correction procedures. The first communication device described in Appendix 66. (Note 68) The second communication device is User Equipment (UE), The procedures related to PDU sessions include the PDU session establishment procedure, The first communication device described in Appendix 66.

[0299] This application claims priority based on Indian Patent Application No. 202311048590, filed on 19 July 2023, and incorporates all of its disclosures herein. [Explanation of Symbols]

[0300] 3. User Equipment (UE) 5 (R)AN Node 7 Core Network 31 Transceiver Circuit 32 Antennas 33 Controllers 34 User Interface 35 USIM 36 memory 51 Transceiver Circuit 52 Antennas 53 Network Interfaces 54 Controllers 55 memory 60 Radio Unit (RU) 61 Distributed Unit (DU) 62 Centralized Unit (CU) 70 Access and Mobility Management Function (AMF) 71 Session Management Function (SMF) 72. User Plane Function (UPF) 75 Unified Data Management (UDM) 76 Network Slice Selection Function (NSSF) 77 Network Slice Admission Control Function (NSACF) 79 Network Exposure Function (NEF) 201 Application Function (AF) 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 memory 611 Transceiver Circuit 612 Network Interfaces 613 Controller 614 memory 621 Transceiver Circuit 622 Network Interfaces 623 Controller 624 memory 711 Transceiver Circuit 712 Network Interfaces 713 Controller 714 memory 721 Transceiver Circuit 722 Network Interfaces 723 Controller 724 memory 731 Transceiver Circuit 732 Network Interfaces 733 Controller 734 memory 741 Transceiver Circuit 742 Network Interfaces 743 Controller 744 memory 751 Transceiver Circuit 752 Network Interfaces 753 Controller 754 memory 761 Transceiver Circuit 762 Network Interfaces 763 Controller 764 memory 771 Transceiver Circuit 772 Network Interfaces 773 Controller 774 memory 781 Transceiver Circuit 782 Network Interfaces 783 Controller 784 memory 791 Transceiver Circuit 792 Network Interfaces 793 Controller 794 memory 2011 Transceiver Circuit 2012 Network Interface 2013 Controller 2014 Memory

Claims

1. A method for a first communication device, To communicate with the second communication device, A method including transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

2. The aforementioned Alternative S-NSSAI is transmitted after receiving user consent for User Equipment (UE). The method according to claim 1.

3. The Alternative S-NSSAI is transmitted after the communication status meets a predetermined status. The method according to claim 1.

4. This further includes receiving information indicating that User Equipment (UE) supports the network slice replacement function, The Alternative S-NSSAI is transmitted after receiving the information. The method according to claim 1.

5. This further includes receiving information indicating that User Equipment (UE) supports the processing of UE Route Selection Policy (URSP) rules, The Alternative S-NSSAI is transmitted after receiving the information. The method according to claim 1.

6. The process further includes receiving first information indicating that User Equipment (UE) supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The Alternative S-NSSAI is transmitted after receiving the first information and the second information. The method according to claim 1.

7. The first communication device is an Application Function (AF), The method according to any one of claims 1 to 6.

8. The first communication device is Unified Data Management (UDM). The method according to claim 1.

9. The first communication device is a Network Exposure Function (NEF). The method according to claim 1.

10. A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes performing procedures related to a Protocol Data Unit (PDU) session based on the aforementioned Alternative S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF), The method wherein the second communication device is Unified Data Management (UDM).

11. The procedure relating to the PDU session includes a PDU session modification procedure, The method according to claim 10.

12. The aforementioned PDU session correction procedure is performed when the User Equipment (UE) receives information indicating that it supports the network slice replacement function. The method according to claim 11.

13. The procedure relating to the PDU session includes a PDU session establishment procedure, The method according to claim 10.

14. The PDU session establishment procedure is performed when the User Equipment (UE) receives information indicating that it supports the network slice replacement function. The method according to claim 13.

15. A method for User Equipment (UE), To communicate with the first communication device, This includes performing procedures related to a Protocol Data Unit (PDU) session, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI), The Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is an Access and Mobility Management Function (AMF), The method wherein the second communication device is Unified Data Management (UDM).

16. The procedure relating to the PDU session includes a PDU session modification procedure, The method according to claim 15.

17. The UE further includes transmitting information indicating that it supports network slice replacement functionality, The PDU session correction procedure is performed when the UE transmits the information indicating that it supports the network slice replacement function. The method according to claim 16.

18. The UE further includes transmitting information indicating that it supports processing UE Route Selection Policy (URSP) rules, The PDU session correction procedure is performed when the UE transmits the information indicating that it supports processing the URSP rule. The method according to claim 16.

19. The method further includes transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session modification procedure is performed when transmitting the first information and the second information. The method according to claim 16.

20. The procedure relating to the PDU session includes a PDU session establishment procedure, The method according to claim 15.

21. The UE further includes transmitting information indicating that it supports network slice replacement functionality, The PDU session establishment procedure is performed when the UE transmits the information indicating that it supports the network slice replacement function. The method according to claim 20.

22. The UE further includes transmitting information indicating that it supports processing UE Route Selection Policy (URSP) rules, The PDU session establishment procedure is performed when the UE transmits the information indicating that it supports processing the URSP rule. The method according to claim 20.

23. The method further includes transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session establishment procedure is performed when transmitting the first information and the second information. The method according to claim 20.

24. A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting the Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF), The method wherein the third communication device is an Access and Mobility Management Function (AMF).

25. A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes transmitting the Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF), The method wherein the third communication device is a Session Management Function (SMF).

26. A method for User Equipment (UE), Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the first communication device, This includes performing procedures related to a Protocol Data Unit (PDU) session based on the aforementioned S-NSSAI, The method wherein the first communication device is a Session Management Function (SMF).

27. The procedure relating to the PDU session includes a PDU session modification procedure, The method according to claim 26.

28. The procedure relating to the PDU session includes a PDU session establishment procedure, The method according to claim 26.

29. A method for a first communication device, A method comprising communicating with a second communication device and transmitting S-NSSAI that has been replaced with Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

30. The first communication device is an Application Function (AF), The method according to claim 29.

31. A method for User Equipment (UE), This involves sending a registration request message, The aforementioned registration request message includes Alternative Single Network Slice Selection Assistance Information (S-NSSAI), Sending a Protocol Data Unit (PDU) session establishment request message, The PDU session establishment request message includes the Alternative S-NSSAI, and the method includes the latter.

32. A method for a first communication device, Receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from the second communication device, This includes performing procedures related to a Protocol Data Unit (PDU) session based on the aforementioned S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF), in this method.

33. The second communication device is a Policy Control Function (PCF), The procedure relating to the PDU session includes a PDU session modification procedure, The communication method according to claim 32.

34. The second communication device is User Equipment (UE), The procedure relating to the PDU session includes a PDU session establishment procedure, The communication method according to claim 32.

35. A first communication device, A means for communicating with a second communication device, A first communication device comprising means for transmitting Alternative Single Network Slice Selection Assistance Information (S-NSSAI).

36. The aforementioned Alternative S-NSSAI is transmitted after receiving user consent for User Equipment (UE). The first communication device according to claim 35.

37. The Alternative S-NSSAI is transmitted after the communication status meets a predetermined status. The first communication device according to claim 35.

38. The User Equipment (UE) further provides means for receiving information indicating that it supports network slice replacement functionality. The Alternative S-NSSAI is transmitted after receiving the information. The first communication device according to claim 35.

39. The User Equipment (UE) further provides means for receiving information indicating that it supports the processing of UE Route Selection Policy (URSP) rules, The Alternative S-NSSAI is transmitted after receiving the information. The first communication device according to claim 35.

40. The system further includes means for receiving first information indicating that User Equipment (UE) supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The Alternative S-NSSAI is transmitted after receiving the first information and the second information. The first communication device according to claim 35.

41. The first communication device is an Application Function (AF), The first communication device according to any one of claims 35 to 40.

42. The first communication device is Unified Data Management (UDM). The first communication device according to claim 35.

43. The first communication device is a Network Exposure Function (NEF). The first communication device according to claim 35.

44. A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on the Alternative S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Unified Data Management (UDM) system, which is the first communication device.

45. The procedures related to the PDU session include the PDU session modification procedure, The first communication device according to claim 44.

46. When the first communication device receives information indicating that User Equipment (UE) supports the network slice replacement function, it executes the PDU session modification procedure. The first communication device according to claim 45.

47. The procedure relating to the PDU session includes a PDU session establishment procedure, The first communication device according to claim 44.

48. The PDU session establishment procedure is performed when the first communication device receives information indicating that the User Equipment (UE) supports the network slice replacement function. The first communication device according to claim 47.

49. User Equipment (UE), A means for communicating with the first communication device, The system includes means for performing procedures related to a Protocol Data Unit (PDU) session, The procedure related to the PDU session is triggered by the first communication device based on Alternative Single Network Slice Selection Assistance Information (S-NSSAI), The Alternative S-NSSAI is transmitted to the first communication device by the second communication device. The first communication device is an Access and Mobility Management Function (AMF), The second communication device is a Unified Data Management (UDM), or UE.

50. The procedure relating to the PDU session includes a PDU session modification procedure, The UE described in claim 49.

51. The UE further comprises means for transmitting information indicating that it supports network slice replacement functionality, The PDU session correction procedure is performed when the UE transmits the information indicating that the UE supports the network slice replacement function. The UE according to claim 50.

52. The UE further comprises means for transmitting information indicating that it supports processing UE Route Selection Policy (URSP) rules, If the UE transmits the information indicating that the UE supports processing the URSP rule, the PDU session correction procedure is executed. The UE according to claim 50.

53. The means further comprises transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session modification procedure is performed when the UE transmits the first information and the second information. The UE according to claim 50.

54. The procedure relating to the PDU session includes a PDU session establishment procedure, The UE described in claim 49.

55. The UE further comprises means for transmitting information indicating that it supports network slice replacement functionality, The PDU session establishment procedure is executed when the UE transmits the information indicating that the UE supports the network slice replacement function. The UE described in claim 54.

56. The UE further comprises means for transmitting information indicating that it supports processing UE Route Selection Policy (URSP) rules, If the UE transmits the information indicating that the UE supports processing the URSP rule, the PDU session establishment procedure is executed. The UE described in claim 54.

57. The means further comprises transmitting first information indicating that the UE supports network slice replacement functionality, and second information indicating that the UE does not support processing UE Route Selection Policy (URSP) rules. The PDU session establishment procedure is performed when the UE transmits the first information and the second information. The UE described in claim 54.

58. A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting the Alternative S-NSSAI to a third communication device, The first communication device is a Policy Control Function (PCF), The second communication device is a Network Exposure Function (NEF), The third communication device is the first communication device, which is an Access and Mobility Management Function (AMF).

59. A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for transmitting the Alternative S-NSSAI to a third communication device, The first communication device is a Network Slice Selection Function (NSSF), The second communication device is a Network Exposure Function (NEF), The third communication device is the first communication device, which is a Session Management Function (SMF).

60. User Equipment (UE), A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a first communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on the aforementioned S-NSSAI, The first communication device is a Session Management Function (SMF), which is a UE.

61. The procedure relating to the PDU session includes a PDU session modification procedure, The UE according to claim 60.

62. The procedure relating to the PDU session includes a PDU session establishment procedure, The UE according to claim 60.

63. A first communication device, A means for communicating with a second communication device, A first communication device comprising means for transmitting Single Network Slice Selection Assistance Information (S-NSSAI) that has been replaced with Alternative S-NSSAI.

64. The first communication device is an Application Function (AF), The first communication device according to claim 63.

65. User Equipment (UE), A means for sending a registration request message, The registration request message includes means, which include Alternative Single Network Slice Selection Assistance Information (S-NSSAI), A means for sending a Protocol Data Unit (PDU) session establishment request message, The PDU session establishment request message comprises a means including the Alternative S-NSSAI, and a UE.

66. A first communication device, A means for receiving Alternative Single Network Slice Selection Assistance Information (S-NSSAI) from a second communication device, The system includes means for executing procedures related to a Protocol Data Unit (PDU) session based on the aforementioned S-NSSAI, The first communication device is an Access and Mobility Management Function (AMF).

67. The second communication device is a Policy Control Function (PCF), The procedure relating to the PDU session includes a PDU session modification procedure, The first communication device according to claim 66.

68. The second communication device is User Equipment (UE), The procedure relating to the PDU session includes a PDU session establishment procedure, The first communication device according to claim 66.

Images