Method of access and mobility management function (AMF) apparatus, method of user equipment (UE), method of policy control function (PCF) apparatus, method of radio access network (RAN) node, AMF apparatus, UE, pcf apparatus, and ran node

Abstract

To provide user equipment (UE), an AMF apparatus, and a method for performing cell selection and cell reselection based on network slice priority and network slice grouping information.SOLUTION: A telecommunication system has an access and mobility management function (AMF) for receiving a registration request message from UE, sending a subscription permanent identifier (SUPI) related to the UE to a unified data management (UDM) apparatus, receiving first information related to single network slice selection assistance information (S-NSSAI) from the UDM apparatus, and sending to the UE a registration accept message including priority related to the S-NSSAI determined on the basis of the first information.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to an Application Function (AF) device method, a Network Exposure Function (NEF) device method, a Unified Data Management (UDM) device method, an Access and Mobility Management Function (AMF) device method, a User Equipment (UE) method, a Policy Control Function (PCF) device method, a Radio Access Network (RAN) node method, an AF device, an NEF device, a UDM device, an AMF device, a UE, a PCF device, and a RAN node. [Background technology]

[0002] At the 3GPP RAN WG2#115-e meeting, Non-Patent Document 2 was agreed upon. This document discloses the following technical aspects.

[0003] The following information is used in the UE AS for evaluation of cell reselection: -Slice-specific absolute priority of each slice of the frequency that supports the slice ("Slice Info") The UE receives slice info using RRC signaling (system information and / or dedicated RRC signaling). - A list of slices with slice priorities for cell reselection.

[0004] With respect to the list of slices with slice priorities, it is assumed that the UE Access Stratum (AS) receives a list from the NAS containing slice priorities for each of the slices included in the list when / before transitioning to RRC_IDLE / RRC_INACTIVE and when the list and / or priorities change while the UE is in RRC_IDLE / RRC_INACTIVE.

[0005] This cell reselection evaluation is designed based on the following design principles. - The frequency priority mapping for each slice (slice -> frequency -> absolute priority of each frequency) is provided to the UE. The frequency priority mapping for each slice (slice -> frequency -> absolute priority of each frequency) is part of the "slice info" that is allowed to be provided to the UE using both broadcast and dedicated signaling.

[0006] Additionally, a slice group concept is also disclosed, where a slice group consists of one or more slices, one slice belongs to one and only one slice group, and each slice group is uniquely identified by a slice group identifier. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.0.0 (2020-07) [Non-patent document 2] 3GPP RAN WG2#115-e meeting R2-2108928: "LS on Slice list and priority information for cell reselection". (2021-08) [Non-patent document 3] IETF RFC 5580: "Carrying Location Objects in RADIUS and Diameter". (2009-08) [Non-patent document 4] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". V17.1.0 (2021-09) Summary of the Invention [Problem to be solved by the invention]

[0008] One of the prominent issues is how and in what form a 5GS network (or another network node) provides network slice priority information and network slice grouping information to a UE and other network nodes so that the UE can perform cell selection and cell reselection based on the network slice priority and network slice grouping information. This includes provisioning the network slice priority and possible network slice grouping to the 5GS itself if the network slice is owned by an external service provider. [Means for solving the problem]

[0009] In an aspect of the present disclosure, a method in an Application Function (AF) device includes modifying a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) and transmitting the priority to a Network Exposure Function (NEF) device.

[0010] In an aspect of the present disclosure, a method in a Network Exposure Function (NEF) device includes receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Application Function (AF) device and sending the priority to a Unified Data Management (UDM) device.

[0011] In an aspect of the present disclosure, a method in a Unified Data Management (UDM) device includes receiving a preference associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Network Exposure Function (NEF) device and storing the preference.

[0012] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) device includes receiving a registration request message from a User Equipment (UE), sending a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device, receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device, and sending a registration accept message to the UE including the priority.

[0013] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) device includes receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device, and sending a UE Configuration Update message including the priority to a User Equipment (UE).

[0014] In an aspect of the present disclosure, a method in a User Equipment (UE) includes transmitting a registration request message including information indicating that the UE supports priorities associated with Single Network Slice Selection Assistance Information (S-NSSAI), and receiving a registration accept message including the priorities.

[0015] In an aspect of the present disclosure, a method in a Policy Control Function (PCF) device includes receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device, updating a policy based on the priority, and transmitting the policy.

[0016] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) device includes receiving, from a Policy Control Function (PCF) device, a policy including a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI), and transmitting the policy to a User Equipment (UE).

[0017] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) device includes receiving a Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from a Unified Data Management (UDM) device, and sending an N2 message including the S-NSSAI and the priority to a Radio Access Network (RAN) node.

[0018] In an aspect of the present disclosure, a method in a Radio Access Network (RAN) node includes receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from an Access and Mobility Management Function (AMF) device, and using the priority for a handover-related process or a PDU session-related process.

[0019] In an aspect of the present disclosure, an Application Function (AF) device includes means for modifying a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) and means for transmitting the priority to a Network Exposure Function (NEF) device.

[0020] In an aspect of the present disclosure, a Network Exposure Function (NEF) device includes means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Application Function (AF) device, and means for sending the priority to a Unified Data Management (UDM) device.

[0021] In an aspect of the present disclosure, a Unified Data Management (UDM) device includes means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Network Exposure Function (NEF) device, and means for storing the priority.

[0022] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) device includes means for receiving a registration request message from a User Equipment (UE), means for sending a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device, means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device, and means for sending a registration accept message including the priority to the UE.

[0023] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) device includes means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device, and means for sending a UE Configuration Update message including the priority to a User Equipment (UE).

[0024] In an aspect of the present disclosure, a User Equipment (UE) includes means for transmitting a registration request message including information indicating that the UE supports priorities associated with Single Network Slice Selection Assistance Information (S-NSSAI), and means for receiving a registration accept message including the priorities.

[0025] In an aspect of the present disclosure, a Policy Control Function (PCF) device includes means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device, means for updating a policy based on the priority, and means for transmitting the policy.

[0026] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) device includes means for receiving a policy including a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Policy Control Function (PCF) device, and means for transmitting the policy to a User Equipment (UE).

[0027] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) device includes means for receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from a Unified Data Management (UDM) device, and means for sending an N2 message including the S-NSSAI and the priority to a Radio Access Network (RAN) node.

[0028] In an aspect of the present disclosure, a Radio Access Network (RAN) node includes means for receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from an Access and Mobility Management Function (AMF) device, and means for using the priority for a handover-related process or a PDU session-related process. [Brief explanation of the drawings]

[0029] [Figure 1] FIG. 1 shows the new information in the User Equipment (UE) for cell selection and cell reselection. [Figure 2] FIG. 2 shows slice information. [Figure 3] FIG. 3 is a signaling diagram of a first example of the first embodiment. [Figure 4] FIG. 4 is a signaling diagram of a first example of the second embodiment. [Figure 5] FIG. 5 is a signaling diagram of a second example of the second embodiment. [Figure 6] FIG. 6 is a signaling diagram of a third example of the second embodiment. [Figure 7] FIG. 7 is a signaling diagram of a fourth example of the second embodiment. [Figure 8] FIG. 8 is a signaling diagram of a first example of the third embodiment. [Figure 9] FIG. 9 is a diagram showing an outline of the system. [Figure 10] FIG. 10 is a block diagram illustrating a user equipment (UE). [Figure 11] FIG. 11 is a block diagram illustrating an (R)AN node. [Figure 12]FIG. 12 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 13] FIG. 13 is a block diagram showing a radio unit (RU). [Figure 14] FIG. 14 is a block diagram showing a distributed unit (DU). [Figure 15] FIG. 15 is a block diagram showing a centralized unit (CU). [Figure 16] FIG. 16 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 17] FIG. 17 is a block diagram illustrating a Policy Control Function (PCF). [Figure 18] FIG. 18 is a block diagram illustrating the Network Exposure Function (NEF). [Figure 19] FIG. 19 is a block diagram illustrating Unified Data Management (UDM). [Figure 20] FIG. 20 is a block diagram showing an Application Function (AF). DETAILED DESCRIPTION OF THE INVENTION

[0030] <abbreviation> For purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following apply: Abbreviations defined in this specification take precedence over the definition of the same abbreviation in Non-Patent Document 1 if the same abbreviation appears in that document.

[0031] 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function AS Access Stratum ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token 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 GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HR Home Routed (roaming) IAB Integrated access and backhaul IMEI / TAC IMEI Type Allocation Code IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out (roaming) 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 MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MITM Man In the Middle MNC Mobile Network Code MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol 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 NPN Non-Public Network NR New Radio NRF Network Repository 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 PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy 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 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 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 URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited PLMN 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

[0032] <Definition> For purposes of this specification, the terms and definitions given in Non-Patent Document 1 and the following apply: Terms defined in this specification take precedence over the definition of the same term in Non-Patent Document 1, if any.

[0033] <General remarks> Those skilled in the art will appreciate that elements in the figures may be shown in simplified form and not necessarily drawn to scale. Furthermore, with respect to the structure of a device, one or more components of the device may be represented by conventional symbols in the figures, and the figures may show only certain details relevant to understanding aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0034] To promote an understanding of the principles of the present disclosure, reference will now be made to embodiments illustrated in the drawings and specific language will be used to describe those principles. It will nevertheless be understood that no limitation on the scope of the present disclosure is intended thereby. Such alterations and further modifications in the illustrated systems, and such further applications of the principles of the present disclosure as would normally occur to one skilled in the art, are to be construed as being within the scope of the present disclosure.

[0035] The terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method comprising a list of steps not only includes those steps, but may also include other steps not expressly listed or inherent in such process or method. Similarly, the reference to one or more devices, entities, subsystems, elements, structures, or components preceded by "comprises" does not, absent further constraints, preclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the phrases "in an embodiment," "in another embodiment," and similar terms may all refer to the same embodiment, but do not necessarily do so.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and are not intended to be limiting.

[0037] In the following specification and claims, reference will be made to a number of terms that shall be defined to have the following meanings: The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0038] As used herein, information refers to data and knowledge when data is meaningful information and represents values ​​attributed to parameters. Furthermore, knowledge refers to an understanding of an abstract or concrete concept. It should be noted that this exemplary system is simplified to facilitate explanation of the subject matter of the present disclosure and is not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used in addition to or instead of the system to implement aspects disclosed herein, and all such aspects are contemplated as being within the scope of the present disclosure.

[0039] Each aspect and elements included in each aspect described below can be implemented independently or in combination with each other, and the aspects include different novel features, and therefore contribute to achieving different objectives or solving different problems and achieving different advantages.

[0040] FIG. 1 illustrates an example of new information available to a user equipment (UE) for cell selection and / or cell reselection based on network slice priority.

[0041] 2 illustrates an example of new slice information provided to a UE. Note that this example does not illustrate the structure of slice information. Slice information may be referred to as slice information in this disclosure.

[0042] The following aspects disclose a method for cell selection and reselection based on network slice priorities and network slice groupings. The aspects allow an external service provider to provide and update network slice priorities and network slice groupings to a 5GS. The aspects also allow the 5GS to provide the network slice priorities and groupings to a UE, a RAN node, and other network nodes to facilitate cell selection and reselection based on the network slice priorities and network slice groupings.

[0043] <First aspect> The present disclosure proposes a mechanism that enables at least one of network slice priority information and network slice grouping information to be provisioned in a 5G System (5GS) as UE subscription information. The present disclosure also proposes a mechanism that enables the UE subscription information to be updated by an external service provider. The 5GS may be expressed as, but is not limited to, a UDM.

[0044] <First Example of First Aspect> The present disclosure in Figure 3 discloses a mechanism for provisioning network slice priority information to a 5G network server and updating the network slice priority information by an external service provider for its customers served by the 5G network. A customer may be represented as a mobile terminal user. A UDM may be represented as a UDM 75. A NEF may be represented as a NEF 74. An AF may be represented as an AF 77.

[0045] 1. A service provider may decide to provision network slice priorities for its users or update already provisioned network slice priorities used by its users or customers for priority-based cell selection and reselection. The provisioning or updating of network slice priorities may be performed by an Application Function (AF). The AF may be represented as an AF node, an AF apparatus, an AF device, or any other entity. The network slice priorities may be a list including slice priorities for each of the slices included in the list of network slices. The network slice priorities may be included in slice information. For example, the network slice priorities may be represented as S-NSSAI1 having UE network slice priority 1 and S-NSSAI2 having UE network slice priority 3. The network slice priority may mean one network slice priority. "S-NSSAI1 having UE network slice priority 1" may mean that UE network slice priority 1 (or the first UE network slice priority) is assigned to S-NSSAI1. "S-NSSAI2 with UE network slice priority 3" may mean that UE network slice priority 3 (or a third UE network slice priority) is assigned to S-NSSAI2. The network slice priority may be referred to as network slice priorities, network slice priority, UE network slice priority, UE slice priority, UE slice priority, slice priority, network slice priority information, or any other. Priority-based cell selection and reselection may be expressed by a service provider as directing a UE to a network slice based on criteria such as service preference, availability, or any other consideration. The network slice priority may refer to at least one of the network slice priorities.

[0046] 2. The AF triggers an Nnef_ParameterProvision_Request to provide network slice priorities to the Unified Data Management (UDM). The AF sends an Nnef_ParameterProvision_Request message or any other message to the Network Exposure Function (NEF) to provision parameters to the 5G system, and the AF includes UE identity or UE group identity, and one or more network slices having network slice priorities in the parameters. For example, the UE identity or UE group identity may be represented as a UE_ID or a UE ID. For example, the one or more network slices having network slice priorities may be represented as an S-NSSAI1 having UE network slice priority 1 and an S-NSSAI3 having UE network slice priority 3. For example, the Nnef_ParameterProvision_Request message may include the UE_ID, the S-NSSAI1, the UE network slice priority 1, the S-NSSAI3, and the UE network slice priority 3. For example, the Nnef_ParameterProvision_Request message may include a UE_ID, an S-NSSAI1, a UE network slice priority of 1 assigned to the S-NSSAI1, an S-NSSAI3, and a UE network slice priority of 3 assigned to the S-NSSAI3.

[0047] 3. The NEF may trigger an AF authorization procedure to verify the authenticity of the AF. The NEF may be represented as an NEF node, an NEF apparatus, an NEF device, or any other entity. The AF may be represented as a service provider.

[0048] 4. After successful AF authorization, the NEF forwards the request from the AF to the UDM via a Nudm_ParameterProvision_Request message or any other message to provision parameters to the UDM. For example, the Nudm_ParameterProvision_Request message may include the UE_ID, S-NSSAI1, UE network slice priority 1, S-NSSAI3, and UE network slice priority 3. For example, the Nudm_ParameterProvision_Request message may include the UE_ID, S-NSSAI1, UE network slice priority 1 assigned to S-NSSAI1, S-NSSAI3, and UE network slice priority 3 assigned to S-NSSAI3. The UDM may be represented as a UDM node, UDM apparatus, UDM device, database, or any other entity. For example, the NEF may forward the request from the AF to the UDM via a Nudm_ParameterProvision_Request message without AF authorization.

[0049] 5. When the UDM receives the Nudm_ParameterProvision_Request message, the UDM stores the newly provisioned or updated UE network slice priority in the UE's subscription information, and the UDM may trigger a procedure to update the UE and other network nodes to which the network slice priority update is applicable. When the UDM stores the newly provisioned or updated UE network slice priority in the UE's subscription information, it may be expressed as the UDM updating the UE's slice priority in the UE's subscription information. The UE's subscription information may be expressed as UE subscription information, subscription information for the associated UE, or any other information. For example, when the UDM receives the Nudm_ParameterProvision_Request message, the UDM stores the newly provisioned or updated UE network slice priority in the subscription information for the UE identified by the received UE_ID, and the UDM may trigger a procedure to update the UE and other network nodes to which the network slice priority update is applicable. For example, if the UDM receives a Nudm_ParameterProvision_Request message including UE_ID1 identifying UE1, S-NSSAI1 associated with UE network slice priority 1, and S-NSSAI3 associated with UE network slice priority 3, the UDM associates S-NSSAI1 with UE network slice priority 1 and S-NSSAI3 with UE network slice priority 3, and stores the UE network slice priorities in the subscription information for UE1.For example, if the UDM receives a Nudm_ParameterProvision_Request message including UE_ID1 identifying UE1, S-NSSAI1 associated with UE network slice priority 1, and S-NSSAI3 associated with UE network slice priority 3, and the UDM already has subscription information for UE1, the UDM associates S-NSSAI1 with UE network slice priority 1 and S-NSSAI3 with UE network slice priority 3, and updates the UE network slice priorities in the subscription information for UE1 with the newly provisioned UE network slice priorities.

[0050] <Modification 1 of the first example of the first aspect> Regarding network slice priority, instead of a list of one or more S-NSSAIs (or a list of one or more network slices) with priorities in step 2, the AF may provide network slices in groups, where each group includes network slices that have similarities based on criteria such as similar priorities, similar services, similar technologies, similar functions, or any other criteria for creating groups of one or more network slices. For example, the AF may provide network slice group 1 including S-NSSAI1 and S-NSSAI3 with UE network slice group priority 1, and network slice group 2 including S-NSSAI2 and S-NSSAI4 with UE network slice group priority 2. These network slice groups have unique group identities and relative priorities between them. The AF provides these network slice groups associated with one UE or a group of UEs to the UDM via the NEF, and the UDM stores the network slice groups in the subscription information for the associated UEs.

[0051] <Modification 2 of the first example of the first aspect> In step 2, the AF may include a network slice priority validity or a network slice group priority validity in the Nnef_ParameterProvision_Request message to define the time during which the provided network slice priority or the provided network slice group priority is valid. The network slice priority validity or the network slice group priority validity may indicate that the network slice priority or the network slice group priority may be valid until the network slice priority and the network slice group priority are updated. The network slice priority validity or the network slice group priority validity may indicate a limited time that is valid, for example, for several days, weeks, or months, after which the network slice priority or the network slice group priority may become the default network slice priority or the default network slice group priority. The network slice priority validity and the network slice group priority validity are stored in the UDM in step 5 and remain valid until the network slice priority or the network slice group priority is updated or expires. The network slice priority validity and the network slice group priority validity may be transferred to the UE or UE group member. When the network slice priority validity or the network slice group priority validity expires, the UDM may update the network slice priority or the network slice group priority to indicate that the network slice priority or the network slice group priority is applied to the UE or other network node with a new network slice priority and a new network slice group priority, for example, a default network slice priority or a default network slice group priority. The default network slice priority may be represented as a default value of the network slice priority. The default network slice group priority may be represented as a default value of the network slice group priority.

[0052] <Modification 3 of the first example of the first aspect> In step 2, the AF may include a network slice priority validity or a network slice group priority validity in the Nnef_ParameterProvision_Request message to define a specific location where the provided network slice priority or the provided network slice group priority is valid. The network slice priority validity or the network slice group priority validity may indicate that the network slice priority or the network slice group priority may be valid in a specified location, for example, for a TAI, a cell, a PLMN ID, a RAT, or a geographical location as described in Non-Patent Document 3. When the UE leaves the specified location indicated by the network slice priority validity or the network slice group priority validity, the network slice priority or the network slice group priority may become the default network slice priority or the default network slice group priority. The network slice priority validity and the network slice group priority validity are stored in the UDM in step 5 and transferred to the UE or the UE group member.

[0053] <Modification 4 of the first example of the first aspect> In step 2, the AF may include a network slice priority validity or a network slice group priority validity in the Nnef_ParameterProvision_Request message to define a specific access type or access RAT type for which the provided network slice priority or the provided network slice group priority is valid. The network slice priority or the network slice group priority may be valid for a specified access type or access RAT type, for example, NR, EUTRA, NBIOT, LTE-M, NR_U, WLAN, VIRTUAL, TRUSTED_N3GA, TRUSTED_WLAN, WIRELINE, WIRELINE_CABLE, or WIRELINE_BBF for 3GPP access, non-3GPP access, or RAT types as defined in Non-Patent Document 4. The network slice priority validity and the network slice group priority validity are stored in the UDM in step 5 and forwarded to the UE or group member.

[0054] It should be noted that the network slice priority validity or network slice group priority validity in variant 2, variant 3, and variant 4 in the first example may be independent of each other or may be selectively combined.

[0055] <Second aspect> The present disclosure proposes a mechanism that enables at least one of network slice priority information and network slice grouping information from UE subscription information in a UDM to be provided to a UE. The present disclosure also proposes a mechanism that enables an update to at least one of network slice priority information and network slice grouping information in a UDM to trigger an update to the UE. In some embodiments, the UE may be represented as UE 3. The RAN node may be represented as (R)AN node 5. The AMF may be represented as AMF 70. The PCF may be represented as PCF 73. The UDM may be represented as UDM 75.

[0056] <First example of the second aspect> The present disclosure in Figure 4 discloses a mechanism for provisioning and even updating network slice priority information for a UE during the UE registration procedure.

[0057] 0. The UDM holds UE subscription information including UE subscribed network slices and their priorities. For example, S-NSSAI1 is associated with network slice priority 1, S-NSSAI2 is associated with network slice priority 2, and S-NSSAI3 is associated with network slice priority 3. For example, the UDM stores S-NSSAI1 associated with network slice priority 1, S-NSSAI2 associated with network slice priority 2, and S-NSSAI3 associated with network slice priority 3 as UE subscribed network slices and their priorities. For example, the UDM may receive the UE subscribed network slices and their priorities from the AF through the process in the first aspect.

[0058] 1. The UE triggers a registration procedure, and if the UE supports at least one of the network slice priority function and the network slice grouping function, the UE indicates in a registration request message or any other NAS message that the UE supports at least one of the network slice priority function and the network slice grouping function. For example, if the UE can recognize or understand a network slice together with its network slice priority, as described below, and its network slice group, as described below, the UE supports at least one of the network slice priority function and the network slice grouping function.

[0059] 2. If the AMF does not have UE subscription information for the UE, the AMF sends a Nudm_SDM_Get message to the UDM to fetch the UE subscription information. If the AMF does not have UE subscription information for the UE, this may be a case of initial registration. The AMF includes UE identification information, for example, a SUPI for the UE, in the Nudm_SDM_Get message. The AMF may include the requested NSSAI received from the UE in the registration request message in the Nudm_SDM_Get message. The requested NSSAI may indicate the network slice to which the UE is requesting registration.

[0060] 3. The UDM replies to the AMF with a Nudm_SDM_Get response message, and the UDM includes the UE subscription information in the Nudm_SDM_Get response message. The UE subscription information may include the network slice to which the UE is requesting registration and the network slice to which the UE is subscribed, as well as their network slice priorities. The UE subscription information may include all network slices stored by the UDM. For example, if the UE subscribes to S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3, and the UE is requesting registration for S-NSSAI1, S-NSSAI2, and S-NSSAI3, the UDM may send a Nudm_SDM_Get response message including the UE_ID for the UE, S-NSSAI1, the UE network slice priority 1 assigned to S-NSSAI1, S-NSSAI2, the UE network slice priority 2 assigned to S-NSSAI2, and S-NSSAI3, and the UE network slice priority 3 assigned to S-NSSAI3. The UE ID for a UE may be expressed as a SUPI or UE.

[0061] 4. If the UE indicates support for network slice priority in the registration request message or any other NAS message, the AMF includes the network slices requested by the UE and the network slices to which the UE subscribes, along with their network slice priorities, in the Configured NSSAI or the Allowed NSSAI. If the UE also indicates support for network slice grouping, the AMF groups the network slices in a network slice group, where each network slice group may be identified using a unique network slice group ID, and each network slice group may include one or more network slices. The AMF may include the network slice group IDs associated with the network slices requested by the UE and the network slices to which the UE subscribes, along with their network slice priorities, in the Configured NSSAI or the Allowed NSSAI. The network slice group ID may be expressed as a network slice group ID, or an NS group ID or group ID. The network slices in the group may be listed in priority order. "id" may mean identification information or identifier. The AMF may use various criteria when grouping network slices in a network slice group. The AMF may use standardized criteria or operator-defined criteria. Some examples of various criteria are listed below.

[0062] Criteria based on network slice priority—for example, network slices with the same or similar priority may be part of the same network slice group; or

[0063] Criteria based on the services provided by the network slices—for example, network slices that can provide the same or similar services may be part of the same network slice group, and network slices that can provide the same or similar services may be represented as network slices having the same Slice Service Type (SST).

[0064] Criteria based on network slice membership—for example, network slices belonging to the same operator or equivalent PLMNs may be grouped in the same network slice group, and network slices belonging to the same operator may be represented as network slices having the same slice differentiator (SD).

[0065] Any other criteria for network slice grouping.

[0066] 5. The AMF provides the UE with the network slice together with its network slice priority and network slice group in the configuration NSSAI or authorization NSSAI, or as a separate parameter, in the registration accept message or any other NAS message from the AMF to the UE, where each network slice group is identified by a unique network slice group ID. When the UE receives the network slice priority and network slice group, the UE sends a registration complete message to indicate that it has received the network slice priority or network slice group. The network slice group may be represented as an NS group. The network slice group ID may be represented as an NS group ID. For example, if the UE requests S-NSSAI1, S-NSSAI2, and S-NSSAI3 in the registration request and the UE subscribes to S-NSSAI1 and S-NSSAI3, the AMF provides S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3. A UE requesting S-NSSAI1, S-NSSAI2, and S-NSSAI3 in a registration request may be represented as the UE including S-NSSAI1, S-NSSAI2, and S-NSSAI3 in the requested NSSAIs. For example, if a UE requests S-NSSAI1, S-NSSAI2, and S-NSSAI3 in a registration request and the UE subscribes to S-NSSAI1 and S-NSSAI3, the AMF creates network slice group 1 including S-NSSAI1 and network slice group 3 including S-NSSAI3. The AMF assigns network slice group id1 to network slice group 1 and assigns network slice group id3 to network slice group 3. The AMF provides network slice group 1 including S-NSSAI1 with network slice priority 1 and network slice group 3 including S-NSSAI3 with network slice priority 3.For example, the AMF may provide the UE with information indicating that network slice priority 1 is assigned to S-NSSAI1 and information indicating that network slice priority 3 is assigned to S-NSSAI3. For example, the AMF may provide the UE with information indicating that S-NSSAI1 is included in network slice group 1 identified by network slice group id1 and that network slice priority 1 is assigned to S-NSSAI1, and information indicating that S-NSSAI3 is included in network slice group 3 identified by network slice group id3 and that network slice priority 3 is assigned to S-NSSAI3. The AMF may provide the network slice together with its network slice priority without the network slice group.

[0067] 6. When the UE receives the registration accept message, the UE may update its UE configuration. Updating the UE configuration may be represented as a UE configuration update, or as storing a network slice with its priority and associated NS group ID and applying the updated UE configuration, if available. The UE stores the network slice provided by the network with its network slice priority and network slice group. If the AMF provides a network slice with its network slice priority without a network slice group, the UE may store the network slice with its network slice priority. The network may be represented as an AMF. The UE may utilize at least one of the network slice priority and grouping information for service improvement and resource optimization. The grouping information may be represented as information indicating a network slice group. For example, the UE uses at least one of the network slice priority and grouping information for the process as shown below.

[0068] Cell selection and reselection based on network slice priority or network slice group—For example, when the UE is selecting a cell or reselecting a new cell, the UE may consider the network slices supported by candidate cells, and the UE may give priority to a cell supporting a network slice with the highest priority among the network slices assigned by the UE in the Configuration NSSAI or Authorization NSSAI. For example, the UE may select or reselect a cell supporting a network slice with the highest priority among the network slices assigned by the UE in the Configuration NSSAI or Authorization NSSAI.

[0069] Alternatively, even if the current serving cell has good signal strength, i.e., the current cell can continue to serve the UE, the UE may trigger cell selection or cell reselection based on a higher priority network slice or a higher priority network slice group supported by other cells available to the UE.

[0070] - Service optimization - For example, if a UE has multiple services requiring access to the network, the UE may prioritize services in higher priority network slices.

[0071] <Modification 1 of the first example of the second aspect> If the UDM holds at least one of a network slice priority validity, a network slice group ID, a network slice group priority, and a network slice group priority validity as a UE subscription in step 0, steps 3 and 5 may include at least one of a network slice priority validity and a network slice group priority validity to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. If the UDM holds the network slice priority validity in step 0 and the AMF assigns the network slice group priority and the network slice group priority validity in step 4, the AMF may include at least one of the network slice priority validity and the network slice group priority validity in step 5 to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. When the UE receives at least one of the network slice priority validity and the network slice group priority validity, the UE applies the network slice priority based on at least one of the received network slice priority validity and the received network slice group priority validity. The network slice priority validity and the network slice group priority validity may be the same as the network slice priority validity and the network slice group priority validity in variants 2, 3, and 4 of the first example of the first aspect.

[0072] For example, the network slice priority validity may indicate at least one period for which the network slice priority is valid, and a location for which the network slice priority is valid, as well as an access type or access RAT type for which the network slice priority is valid. The location may be expressed as a TAI, cell, PLMN ID, RAT, or geographical location as described by Non-Patent Document 3.

[0073] For example, the network slice group priority validity may indicate at least one period for which the network slice group priority is valid, and the location for which the network slice group priority is valid, as well as the access type or access RAT type for which the network slice group priority is valid. The location may be expressed as a TAI, cell, PLMN ID, RAT, or geographic location as described in Non-Patent Document 3.

[0074] For example, when a period indicated by the network slice priority validity expires, the UE may update the network slice priority to a default network slice priority. For example, when a period indicated by the network slice group priority validity expires, the UE may update the network slice group priority to a default network slice group priority.

[0075] For example, when the UE leaves the location indicated by the network slice priority validity, the UE may update the network slice priority to a default network slice priority. For example, when the UE leaves the location indicated by the network slice group priority validity, the UE may update the network slice group priority to a default network slice group priority.

[0076] For example, when the UE changes at least one of the access type and the access RAT type indicated by the network slice priority validity, the UE may update the network slice priority to a default network slice priority. For example, when the UE changes at least one of the access type and the access RAT type indicated by the network slice group priority validity, the UE may update the network slice group priority to a default network slice group priority.

[0077] The registration authorization may also include a list of one or more tracking areas in which the NS group ID is valid in the registration area, or an indication of whether the NS group ID is valid in the registration area. If the registration area includes Tracking Areas (TAs) belonging to different PLMNs, another indication may be sent to indicate whether the NS group ID is valid in the serving PLMN or all PLMNs in the registration area. The serving PLMN may be indicated by the MCC and MNC of the GUAMI of the assigned 5G-GUTI. There may be another indication regarding whether the NS group ID is applicable to all PLMNs in the equivalent PLMN list. These indications may be sent to the UE. For example, these indications may indicate whether the network slice in the group identified by the NS group ID is valid. For example, the UE may use these indications to determine whether at least one of the network slice priority and the network slice group priority is valid. For example, the UE may determine whether at least one of the network slice priority and the network slice group priority is valid in the location or PLMN indicated by these indications. The location may refer to a registration area or a tracking area. The PLMN may refer to a serving PLMN.

[0078] <Second Example of the Second Aspect> The present disclosure in Figure 5 discloses a mechanism for provisioning and even updating network slice priority information for a UE during a UE configuration update procedure.

[0079] 1. The UE subscribed network slice priority information in the UDM can be updated by an operator or service provider via the NEF. The UE subscribed network slice priority information in the UDM can be updated by the process in the first aspect. For example, the UE subscribed S-NSSAI1 becomes network slice priority 1, and the UE subscribed S-NSSAI3 becomes network slice priority 3. For example, network slice priority 1 is assigned to the UE subscribed S-NSSAI1, and network slice priority 3 is assigned to the S-NSSAI3.

[0080] 2. When the network slice priority (or network slice priorities) is changed in the UDM, the UDM triggers a Nudm_SDM_Notification message (or any other message to indicate a change in UE subscription information) to the AMF, including the UE ID, S-NSSAI1, network slice priority 1, S-NSSAI3, and network slice priority 3, to update the UE context in the AMF with the new network slice priorities, e.g., S-NSSAI1 has updated network slice priority 1 and S-NSSAI3 has updated network slice priority 3. For example, the UDM sends a Nudm_SDM_Notification message to the AMF, including S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3.

[0081] 3. If the UE whose network slice priority has been updated is in idle mode, the AMF may page the UE to put the UE into connected mode.

[0082] 4. The UE is in connected mode or if the UE was paged in step 3, the UE is put into connected mode.

[0083] 5. If the UE supports network slice priority (or network slice priority function), the AMF includes the network slice with the changed network slice priority together with the new network slice priority in a UE Configuration Update (UCU) message to the UE (or any other NAS message from the AMF to the UE). A UE supporting network slice priority (or network slice priority function) may mean that the UE indicates support for network slice priority (or network slice priority function) in a registration request message or any other NAS message when registering with the network. If the UE also indicates support for network slice grouping (or network slice grouping function), the AMF groups network slices in network slice groups, where each network slice group may be identified using a unique network slice group ID, and each network slice group may include one or more network slices. A UE supporting network slice grouping (or network slice grouping function) may mean that the UE indicates support for network slice grouping (or network slice grouping function) in a registration request message or any other NAS message when registering with the network. Network slices in a network slice group may be listed in priority order. The AMF may use various criteria when grouping network slices in a network slice group. The AMF may use standardized criteria or operator-defined criteria. Examples of various criteria are shown below.

[0084] Criteria based on network slice priority—for example, network slices with the same or similar priority may be part of the same network slice group; or

[0085] Criteria based on the services provided by the network slices—for example, network slices that can provide the same or similar services may be part of the same network slice group, and network slices that can provide the same or similar services may be represented as network slices having the same Slice Service Type (SST).

[0086] Criteria based on network slice membership—for example, network slices belonging to the same operator or equivalent PLMNs may be grouped in the same network slice group, and network slices belonging to the same operator may be represented as network slices having the same slice differentiator (SD).

[0087] Any other criteria for network slice grouping.

[0088] For example, if a UE can recognize or understand a network slice together with its network slice priority, as described below, and a network slice group, as described below, the UE supports at least one of network slice priority and network slice grouping.

[0089] 6. The AMF provides the UE with an updated network slice together with its updated network slice priority and network slice group in a UE Configuration Update message, where each network slice group is identified by a unique network slice group id. The AMF may provide the network slice together with its network slice priority without the network slice group.

[0090] For example, if the UE indicates support for network slice priority, the AMF sends a UE Configuration Update (UCU) message including S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3.

[0091] For example, if the UE indicates support for network slice priority and support for network slice grouping, the AMF creates network slice group 1 including S-NSSAI1 and network slice group 3 including S-NSSAI3. The AMF assigns network slice group id1 to network slice group 1 and assigns network slice group id3 to network slice group 3. Then, the AMF sends a UE Configuration Update (UCU) message, which includes network slice group 1 including S-NSSAI1 with network slice priority 1 and network slice group 3 including S-NSSAI3 with network slice priority 3. The AMF may include network slice group id1 and network slice group id3 in the UCU message.

[0092] For example, the AMF may provide, to the UE, information indicating that network slice priority 1 is assigned to S-NSSAI1 and information indicating that network slice priority 3 is assigned to S-NSSAI3. For example, the AMF may provide, to the UE, information indicating that S-NSSAI1 is included in network slice group 1 identified by network slice group id1 and that network slice priority 1 is assigned to S-NSSAI1, and information indicating that S-NSSAI3 is included in network slice group 3 identified by network slice group id3 and that network slice priority 3 is assigned to S-NSSAI3.

[0093] 7. When the UE receives a UE configuration update message, the UE may update the UE configuration. Updating the UE configuration may be represented as a UE configuration update, or as storing a network slice with its new priority and associated NS group ID, and applying the updated UE configuration, if available. The UE stores a network slice provided by the network with its network slice priority and network slice group. The network may be represented as an AMF. If the AMF provides a network slice with its network slice priority without a network slice group, the UE may store the network slice with its network slice priority. The UE may utilize at least one of the network slice priority and grouping information for service improvement and resource optimization. The grouping information may be represented as information indicating a network slice group. For example, the UE uses at least one of the network slice priority and grouping information for the process as shown below.

[0094] Cell selection and reselection based on network slice priority or network slice group—For example, when the UE is selecting a cell or reselecting a new cell, the UE may consider the network slices supported by candidate cells, and the UE may give priority to a cell supporting a network slice with the highest priority among the network slices assigned by the UE in the Configuration NSSAI or Authorization NSSAI. For example, the UE may select or reselect a cell supporting a network slice with the highest priority among the network slices assigned by the UE in the Configuration NSSAI or Authorization NSSAI.

[0095] Alternatively, even if the current serving cell has good signal strength, i.e., the current cell can continue to serve the UE, the UE may trigger cell selection or cell reselection based on a higher priority network slice or a higher priority network slice group supported by other cells available to the UE.

[0096] - Service optimization - For example, if a UE has multiple services requiring access to the network, the UE may prioritize services in higher priority network slices.

[0097] <Modification 1 of the second example of the second aspect> If the UDM holds at least one of a network slice priority validity, a network slice group ID, a network slice group priority, and a network slice group priority validity as a UE subscription, and if at least one of the network slice priority validity and the network slice group priority validity is changed in step 1, steps 2 and 6 include at least one of a network slice priority validity and a network slice group priority validity to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. If the UDM holds the network slice priority validity in step 0 and the AMF assigns the network slice group priority and the network slice group priority validity in step 5, the AMF may include at least one of the network slice priority validity and the network slice group priority validity in step 6 to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. When the UE receives at least one of the network slice priority validity and the network slice group priority validity, the UE applies the network slice priority based on at least one of the received network slice priority validity and the received network slice group priority validity. The network slice priority validity and the network slice group priority validity may be the same as the network slice priority validity and the network slice group priority validity in Variants 2, 3, and 4 of the first example of the first aspect. The UE may use at least one of the received network slice priority validity and the received network slice group priority validity, similar to Variant 1 of the first example of the second aspect.

[0098] The UE Configuration Update (UCU) message may also include a list of one or more tracking areas in which the NS group ID is valid in the registration area, or an indication of whether the NS group ID is valid in the registration area. The UE Configuration Update (UCU) message may also include a list of one or more tracking areas in which the NS group ID is valid in the registration area, or an indication of whether the NS group ID is valid in the registration area. If the registration area includes Tracking Areas (TAs) belonging to different PLMNs, another indication may be sent to indicate whether the NS group ID is valid in the serving PLMN (MCC and MNC of the assigned 5G-GUTI GUAMI) or all PLMNs in the registration area. There may be another indication regarding whether the NS group ID is applicable to all PLMNs in the equivalent PLMN list. These indications may be sent to the UE. For example, these indications may indicate whether a network slice in the group identified by the NS group ID is valid. For example, the UE may use these indications to determine whether at least one of a network slice priority and a network slice group priority is valid. For example, the UE may determine whether at least one of the network slice priority and the network slice group priority is valid in the location or PLMN indicated by these indications. The location may be represented as a registration area or a tracking area. The PLMN may be represented as a serving PLMN. The UE stores a validity parameter for each network slice priority and a validity parameter for each network slice group priority along with each network slice priority and network slice group priority, and the UE runs a timer for each network slice and network slice group with a value equal to the validity parameter for each network slice priority and network slice group priority.The UE uses the stored network slice priority and the stored network slice group priority for cell selection and reselection according to the description in step 7 of the second example of the second aspect until the priority validity timer for each of the network slice and the network slice group expires or the priority validity is next updated by the network for the network slice or the network slice group. When one or more network slice priority validity timers or network slice group priority validity timers expire or the network slice priority validity or the network slice group priority validity is updated by the network, for example, if updated by the network, the UE restarts the network slice priority or the network slice group priority validity timer, or if the validity timer expires and is not updated by the network, the UE sets the network slice priority and the network slice group priority to default priorities.

[0099] <Third Example of the Second Aspect> The present disclosure in FIG. 6 discloses a mechanism for updating access and mobility policy rules and restrictions in the AMF and UE.

[0100] 1. The UE subscribed network slice priority information in the UDM can be updated by an operator or service provider via the NEF. The UE subscribed network slice priority information in the UDM can be updated by the process in the first aspect. For example, the UE subscribed S-NSSAI1 becomes network slice priority 1, and the UE subscribed S-NSSAI3 becomes network slice priority 3. For example, network slice priority 1 is assigned to the UE subscribed S-NSSAI1, and network slice priority 3 is assigned to the S-NSSAI3.

[0101] 2. When the network slice priority (or network slice priorities) is changed in the UDM, the UDM triggers an Npcf UE Subscription Update message (or any other message to indicate a change in UE subscription information) to the PCF, including the UE ID, S-NSSAI1, network slice priority 1, S-NSSAI3, and network slice priority 3, to update the PCC rules or at least one of the URSP rules and NSSP rules for the UE in the PCF with the new network slice priority, e.g., the UE subscribed S-NSSAI1 has an updated network slice priority of 1, and S-NSSAI3 has an updated network slice priority of 3. The AM rules may be expressed as Access and Mobility (AM) policies, and at least one of the URSP rules and NSSP rules may be expressed as UE policies. For example, the UDM sends an Npcf UE Subscription Update message to the PCF, which includes a UE ID for the UE, an S-NSSAI1 with network slice priority 1, and an S-NSSAI3 with network slice priority 3.

[0102] 3. The PCF updates the Access and Mobility (AM) policy for the UE or group of UEs whose network slice priority has changed. The AM policy can be expressed as AM rules and restrictions, AM policy rules, access and mobility control and restriction policies, or AM restrictions. It is proposed to define the following new AM rules and restrictions that depend on the network slice priority:

[0103] Network slice priority rule—The network slice priority rule defines the relative network slice priority for the UE. The granularity of this rule can be per TA or per PLMN.

[0104] Per-DNN network slice priority rule—The per-DNN network slice priority rule defines the relative network slice priority for a UE for network slices supported by a particular DNN. The granularity of this rule can be per TA or per PLMN.

[0105] Network slice priority-based cell selection—The network slice priority-based cell selection rule specifies the relative network slice priority for cell selection by the UE. The granularity of this rule can be per TA or per PLMN.

[0106] Network slice registration rules—Network slice registration rules define the network slices to which a UE is proposed to register. The network may control UE registration, more specifically, the network slice to which a UE requests registration and when the UE registers to that network slice based on the AM policy. The network slice to which a UE requests registration may refer to the network slice that the UE includes in the request NSSAI. The network may assist the UE via an AM policy update with a list of network slices to which the UE is recommended to register, e.g., listed in network slice priority order, to help the UE determine which network slice to request registration to by updating the AM policy with information that helps the UE register to a network slice that is likely to be supported at the UE's location. The network may use current AM restrictions and UE mobility statistics, as well as predictions such as expected UE mobility and expected UE movement trajectory provided by the NWDAF or the service provider. For example, the network may use current AM restrictions and UE mobility statistics, as well as predictions such as expected UE mobility and expected UE movement trajectory provided by the NWDAF or service provider, to control UE registration or to help the UE determine which network slice to request registration to.

[0107] For example, the PCF creates or updates AM policy rules associated with S-NSSAI1 and S-NSSAI3 based on the updated network slice priority 1 and the updated network slice priority 3. The AM policy rules may be expressed as at least one of network slice priority rules, per-DNN network slice priority rules, and network slice priority-based cell selection. For example, to create or update the AM policy rules, the PCF includes S-NSSAI1 with the updated network slice priority 1 and S-NSSAI3 with the updated network slice priority 3 in the AM policy rules. For example, if the PCF has information associated with at least one of the TA, the PLMN, and the DNN, or obtains information from another network node, the PCF uses the information to create or update the AM policy. For example, the PCF updates the AM policy for a UE identified by a UE ID.

[0108] 4. The PCF sends an Npcf_AMPolicyControl message containing the updated new AM policy rules to the AMF. The updated new AM policy rules may include new AM policy rules created by the PCF. The AMF stores the updated new AM policy rules in the UE context.

[0109] 5. The AMF updates the UE with the updated new AM policy rules through a UE configuration update procedure. For example, the AMF sends the updated new AM policy rules to the UE during the UE configuration update procedure.

[0110] 6. When the UE receives the Npcf_AMPolicyControl message, the UE may update its UE configuration. Updating the UE configuration may be represented as a UE configuration update or as storing the updated new AM policy. The UE stores the updated new AM policy rule and starts applying the AM policy rule. For example, the UE starts applying the AM policy rule immediately upon receiving the AM policy rule. For example, the UE may use the updated new AM policy rule for at least one of cell selection, cell reselection, and service optimization, such as step 7 described in the second example of the second aspect.

[0111] <Modification 1 of the third example of the second aspect> If the UDM holds at least one of a network slice priority validity, a network slice group ID, a network slice group priority, and a network slice group priority validity as a UE subscription, and if at least one of the network slice priority validity and the network slice group priority validity is changed in step 1, steps 2, 4, and 5 include at least one of a network slice priority validity and a network slice group priority validity to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. If the UDM holds the network slice priority validity in step 1, and the PCF assigns a network slice group ID, a network slice group priority, and a network slice group priority validity in step 3, the PCF may include at least one of the network slice priority validity and the network slice group priority validity in step 3 to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. If the UDM retains the network slice priority validity in step 1, and the AMF assigns the network slice group ID, the network slice group priority, and the network slice group priority validity in step 5, the AMF may include at least one of the network slice priority validity and the network slice group priority validity in step 5 to convey at least one of the network slice priority validity and the network slice group priority validity to the UE. When the UE receives at least one of the network slice priority validity and the network slice group priority validity, the UE applies the network slice priority based on at least one of the received network slice priority validity and the received network slice group priority validity.The network slice priority validity and the network slice group priority validity may be the same as the network slice priority validity and the network slice group priority validity in Variants 2, 3, and 4 of the first example of the first aspect. The UE stores a validity parameter for each network slice priority and a validity parameter for each network slice priority, together with each network slice priority and network slice group priority, and the UE runs a timer for each network slice and network slice group with a value equal to the validity parameter for each network slice priority and network slice group priority. The UE uses the stored network slice priority and the stored network slice group priority for cell selection and reselection according to the description in step 7 of the second example of the second aspect until the priority validity timer for each network slice and network slice group expires or until the priority validity is next updated by the network for the network slice or network slice group. When one or more network slice priority validity timers or network slice group priority validity timers expire or the network slice priority validity or network slice group priority validity is updated by the network, for example, if updated by the network, the UE restarts the network slice priority or network slice group priority validity timer, or if the validity timer expires and is not updated by the network, the UE sets the network slice priority and network slice group priority to default priorities. The network slice priorities may be grouped in a network slice group, and the network slice group may be transmitted to an associated node. The associated node may be represented as at least one of a PCF, an AMF, and a UE. In this case, the network slice group may be identified by a unique network slice group ID, and each network slice group may include one or more network slices.The network slices in the network slice group may be listed in order of priority. The grouping may be performed by the UDM, the PCF, or the AMF. When grouping the network slices in the network slice group, at least one of the criteria as mentioned in Variant 1 of the first example of the first aspect or the first example of the second aspect may be used. The UE may use at least one of the received network slice priority validity and the received network slice group priority validity, as in Variant 1 of the first example of the second aspect.

[0112] <Fourth Example of the Second Aspect> The present disclosure in FIG. 7 discloses a mechanism for updating UE policies in the PCF and UE based on changes in network slice priority.

[0113] 1. The UE subscribed network slice priority information in the UDM can be updated by an operator or service provider via the NEF. The UE subscribed network slice priority information in the UDM can be updated by the process in the first aspect. For example, the UE subscribed S-NSSAI1 becomes network slice priority 1, and the S-NSSAI3 becomes network slice priority 3. For example, the network slice priority 1 is assigned to the UE subscribed S-NSSAI1, and the network slice priority 3 is assigned to the S-NSSAI3.

[0114] 2. When the network slice priority (or network slice priorities) is changed in the UDM, the UDM triggers an Npcf UE Subscription Update message (or any other message to indicate the change in UE subscription information) to the PCF, including the UE ID, S-NSSAI1, network slice priority 1, S-NSSAI3, and network slice priority 3, to update at least one of the URSP rules and NSSP rules for the UE in the PCF with the new network slice priority, e.g., the UE subscribed S-NSSAI1 has updated network slice priority 1 and S-NSSAI3 has updated network slice priority 3. For example, the UDM sends an Npcf UE Subscription Update message to the PCF, which includes the UE ID for the UE, S-NSSAI1 with network slice priority 1, and S-NSSAI3 with network slice priority 3.

[0115] 3. The PCF updates the network slice priority in at least one of the URSP rule and the NSSP rule for the UE based on the updated network slice priority (or based on the updated network slice priorities). For example, the PCF updates the slice priorities associated with S-NSSAI1 and S-NSSAI3 in at least one of the URSP rule and the NSSP rule by using the updated network slice priority 1 and the updated network slice priority 3. For example, the PCF may add the updated network slice priority 1 for S-NSSAI1 and the updated network slice priority 3 for S-NSSAI3 to at least one of the URSP rule and the NSSP rule.

[0116] 4. The PCF sends at least one of the updated URSP rules and the updated NSSP rules to the UE during a UE policy update procedure, which may refer to a procedure for updating a UE policy.

[0117] 5. When the UE receives at least one of updated URSP rules and updated NSSP rules during the UE policy update procedure, the UE may update the UE policy. Updating the UE policy may be represented as a UE policy update or as storing at least one of updated URSP rules and updated NSSP rules. The UE stores the updated UE policy rules and applies the updated rules and updated network slice priorities when mapping applications to network slices and routing PDU sessions, taking into account the latest network slice priorities. The UE policy may include at least one of updated URSP rules and updated NSSP rules. The updated UE policy rules may be represented as updated PCC rules, updated URSP and NSSP policies, etc. For example, the UE updates the UE policy rules based on the received at least one of updated URSP policies and NSSP policies. The received at least one of updated URSP policies and NSSP policies may be represented as at least one of updated URSP rules and updated NSSP rules. For example, when multiple network slices are listed in a network slice selection rule including multiple network slices, the network slices are listed in a priority order based on the network slice priorities in the UE subscription. For example, the UE may sort the multiple network slices in the network slice selection rule in a priority order based on the updated network slice priorities. For different UEs, the priority order may be different based on the UE-subscribed network slice priorities. For example, the UE may use the updated UE policy rule for at least one of cell selection and cell reselection and service optimization, such as step 6 described in the first example of the second aspect.Also, via updates of UE policies and URSP rules in the UE by the network, the UE may use the updates of UE policies and URSP rules in determining which network slice to register with, how long the UE should maintain registration with that network slice, and which network slice the UE should deregister from, based on, for example, active or running applications in the UE, based on network slice priority, or any other consideration by the network such as operator policy. Through updates of UE policies and URSP rules in the UE by the network, the UE may also use the updates of UE policies and URSP rules in determining which network slice to request service from, for example, whether to trigger a PDU session, release a PDU session, or move a PDU session between network slices, based on, for example, again active or running applications in the UE, based on network slice priority, or any other consideration by the network such as operator policy.

[0118] <Modification 1 of the fourth example of the second aspect> If the UDM holds at least one of a network slice priority validity, a network slice group ID, a network slice group priority, and a network slice group priority validity as a UE subscription, and if at least one of the network slice priority validity and the network slice group priority validity is changed in step 1, steps 2 and 4 include at least one of a network slice priority validity and a network slice group priority validity to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. If the UDM holds the network slice priority validity in step 1, and the PCF assigns a network slice group ID, a network slice group priority, and a network slice group priority validity in step 3, the PCF may include at least one of the network slice priority validity and the network slice group priority validity in step 3 to transmit at least one of the network slice priority validity and the network slice group priority validity to the UE. When the UE receives at least one of the network slice priority validity and the network slice group priority validity, the UE applies the network slice priority based on at least one of the received network slice priority validity and the received network slice group priority validity. The network slice priority validity and the network slice group priority validity may be the same as the network slice priority validity and the network slice group priority validity in variants 2, 3, and 4 of the first example of the first aspect. The UE stores validity parameters for each network slice priority and validity for each network slice group priority together with each network slice priority and network slice group priority, and the UE runs a timer for each network slice and network slice group with a value equal to the validity parameter of each network slice priority and network slice group priority.The UE uses the stored network slice priorities and network slice group priorities for cell selection and reselection according to the description in step 7 of the second example of the second aspect until the priority validity timers for each of the network slices and network slice groups expire or the priority validity is next updated by the network for the network slice or network slice group. When one or more network slice priority validity timers or network slice group priority validity timers expire or the network slice priority validity or network slice group priority validity is updated by the network, for example, if updated by the network, the UE restarts the network slice priority or network slice group priority validity timer, or if the validity timers expire and are not updated by the network, the UE sets the network slice priorities and network slice group priorities to default priorities. The network slice priorities may be grouped in network slice groups, and the network slice groups may be transmitted to an associated node. The associated node may be represented as at least one of a PCF, an AMF, and a UE. In this case, the network slice groups may be identified by a unique network slice group ID, and each network slice group may include one or more network slices. The network slices in the network slice group may be listed in order of priority. The grouping may be performed by the UDM, the PCF, or the AMF. When grouping the network slices in the network slice group, at least one of the criteria as mentioned in Variant 1 of the first example of the first aspect or the first example of the second aspect may be used. The UE may use at least one of the received network slice priority validity and the received network slice group priority validity, as in Variant 1 of the first example of the second aspect.

[0119] <Modification 2 of the fourth example of the second aspect>In steps 3 and 4, through a UE policy update in the UE by the network based on the network slice priority and the network slice group priority, the network can control UE registration, more specifically, the network slice to which the UE requests registration and when the UE registers to that network slice. The UE policy update may be expressed as at least one of the URSP rule updates. The network slice to which the UE requests registration may refer to the network slice that the UE includes in the request NSSAI. According to the current state of the art, the UE may request registration to a network slice that the UE may or may not use during the registration period, or may use at widely separated times. This may lead to network resource allocation not being used by the UE. To optimize the use of network resources, the network may assist the UE through a UE policy update with a list of network slices to which the UE is recommended to register and the time to remain registered. For example, the network may provide the UE with a new URSP rule, for example, called a "network slice for UE registration" rule, or any other indication of the URSP rule, to indicate to the UE information about the network slice to which the UE is proposed to register and the time to remain registered within the URSP rule. In this manner, the network may assist the UE in determining when and to which network slice to request registration by updating the UE policy in the UE with information that helps the UE register with the network slice that the UE is expected to use or on which network slice the UE has installed or activated compatible applications. The UE policy update may be expressed as a URSP and an NSSP rule, and the UE policy may be expressed as a URSP rule. For example, the list of network slices may list one or more network slices in a preferred order.Therefore, UE registration to a network slice can be optimized so that the UE registers with the network slice that the UE is likely to use and registers with the network slice when necessary. The UE may register with the network slice depending on when it needs to use it. This helps to use network resources more efficiently.

[0120] <Third aspect> The present disclosure discloses a mechanism that enables network slice priority information and network slice grouping information from UE subscription information in the UDM to be provided to other network nodes to which this information is applicable. Any further updates to the network slice priority or network slice grouping in the UDM trigger refresh updates to other network nodes that utilize the network slice priority and network slice grouping information.

[0121] <First example of the third aspect> The present disclosure in Figure 8 discloses a mechanism for provisioning and even updating network slice priority information and network slice group information to a RAN node for a connected UE. The UE may be represented as UE 3. The RAN node and the RAN may be represented as (R)AN node 5. The AMF may be represented as AMF 70. The UDM may be represented as UDM 75.

[0122] 1. The UE is registered with the network and is in connected mode.

[0123] 2. The UE subscribed network slice priority information in the UDM can be updated by an operator or service provider via the NEF. The UE subscribed network slice priority information in the UDM can be updated by the process in the first aspect. For example, the UE subscribed S-NSSAI1 becomes network slice priority 1, and the UE subscribed S-NSSAI3 becomes network slice priority 3. For example, network slice priority 1 is assigned to the UE subscribed S-NSSAI1, and network slice priority 3 is assigned to S-NSSAI3.

[0124] 3. When the network slice priority (or network slice priorities) is updated in the UDM, the UDM triggers a Nudm_SDM_Notification message (or any other message to indicate a change in UE subscription information) to the AMF, including the UE ID, S-NSSAI1, network slice priority 1, S-NSSAI3, and network slice priority 3, to update the UE context in the AMF with the new network slice priority, e.g., the UE subscribed S-NSSAI1 has the updated network slice priority 1, and S-NSSAI3 has the updated network slice priority 3. For example, the UDM sends a Nudm_SDM_Notification message to the AMF, including S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3.

[0125] 4. If the UE supports network slice priority (or network slice priority function), the AMF includes the network slice whose network slice priority has been changed along with the new network slice priority in the N2 message to the UE. A UE supporting network slice priority (or network slice priority function) may mean that the UE indicates support for network slice priority (or network slice priority function) in a registration request message or any other NAS message when registering with the network. If the UE also indicates support for network slice grouping (or network slice grouping function), the AMF groups network slices in network slice groups, where each network slice group may be identified using a unique network slice group ID and each network slice group may include one or more network slices. A UE supporting network slice grouping (or network slice grouping function) may mean that the UE indicates support for network slice grouping (or network slice grouping function) in a registration request message or any other NAS message when registering with the network. Network slices in a network slice group may be listed in priority order. The AMF may use various criteria when grouping network slices in groups. The AMF may use standardized criteria or operator-defined criteria. Examples of various criteria are given below.

[0126] Criteria based on network slice priority—for example, network slices with the same or similar priority may be part of the same network slice group; or

[0127] Criteria based on the services provided by the network slices—for example, network slices that can provide the same or similar services may be part of the same network slice group, and network slices that can provide the same or similar services may be represented as network slices having the same Slice Service Type (SST).

[0128] Criteria based on network slice membership—for example, network slices belonging to the same operator or equivalent PLMNs may be grouped in the same network slice group, and network slices belonging to the same operator may be represented as network slices having the same slice differentiator (SD).

[0129] Any other criteria for network slice grouping.

[0130] For example, if a UE can recognize or understand a network slice together with its network slice priority, as described below, and a network slice group, as described below, the UE supports at least one of network slice priority and network slice grouping.

[0131] 5. The AMF provides the RAN node with the updated network slice together with its updated network slice priority and network slice group in the N2 message, each of the network slice groups being identified by a unique network slice group id. The AMF may provide the network slice together with its network slice priority without the network slice group.

[0132] For example, if the UE indicates support for network slice priority, the AMF sends an N2 message to the RAN node, which includes S-NSSAI1 with network slice priority 1 and S-NSSAI3 with network slice priority 3. The RAN node may be represented as a gNB, a base station, or an NG-RAN node.

[0133] For example, if the UE indicates support for network slice priority and support for network slice grouping, the AMF creates network slice group 1 including S-NSSAI1 and network slice group 3 including S-NSSAI3. The AMF assigns network slice group id1 to network slice group 1 and assigns network slice group id3 to network slice group 3. The AMF then sends an N2 message to the RAN node, which includes network slice group 1 including S-NSSAI1 with network slice priority 1 and network slice group 3 including S-NSSAI3 with network slice priority 3. The AMF may include network slice group id1 and network slice group id3 in the N2 message.

[0134] For example, the AMF may provide the RAN node with information indicating that network slice priority 1 is assigned to S-NSSAI1 and information indicating that network slice priority 3 is assigned to S-NSSAI3. For example, the AMF may provide the RAN node with information indicating that S-NSSAI1 is included in network slice group 1 identified by network slice group id1 and that network slice priority 1 is assigned to S-NSSAI1, and information indicating that S-NSSAI3 is included in network slice group 3 identified by network slice group id3 and that network slice priority 3 is assigned to S-NSSAI3.

[0135] 6. When the RAN node receives the N2 message, the RAN node may update the network slice with its new priority and associated NS group ID. The RAN node stores the network slice provided by the network with its network slice priority and network slice group. The network may be represented as an AMF. The RAN node may use at least one of the network slice priority and grouping information for service improvement and resource optimization. The grouping information may be represented as information indicating the network slice group. For example, the RAN node uses at least one of the network slice priority and grouping information for at least one of the processes shown below. At least one of the processes may mean at least one of the processes for the UE.

[0136] -Handover to a cell supporting a higher priority network slice - For example, if the service requested in the PDU session establishment is available in network slices S-NSSAI1 and S-NSSAI3 and the RAN node selects a cell supporting S-NSSAI1, and a cell supporting higher priority S-NSSAI3 now becomes available, the RAN node may trigger a handover to a cell supporting higher priority network slice S-NSSAI3.

[0137] - PDU session resource modification - For example, if the service required in the PDU session establishment is available in network slices S-NSSAI1 and S-NSSAI3 and the PDU session is established in network slice S-NSSAI1 of higher priority, and S-NSSAI3 now has a higher priority than S-NSSAI1, the RAN node may trigger PDU session resource relocation to move the PDU session in network slice S-NSSAI3 with higher priority.

[0138] <Modification 1 of the first example of the third aspect> In step 5, the AMF may provide the network slices supported by the network and their priorities via an NG Setup Response message, or via a Handover Request message, or via an RRC Inactive Assistance Information message, or in the Core Network Assistance Information, or via any other message in the N2 interface between the AMF and the RAN node. For example, in step 5, the NG Setup Response message or the Handover Request message, the RRC Inactive Assistance Information message, or any other message in the N2 interface between the AMF and the RAN node may be applied instead of the N2 message. For example, the information transmitted to the RAN node in step 5 may be included in the Core Network Assistance Information.

[0139] <Modification 2 of the first example of the third aspect> If the UDM holds at least one of the network slice priority validity, the network slice group ID, the network slice group priority, and the network slice group priority validity information as a UE subscription in step 2, step 3 includes at least one of the network slice priority validity and the network slice group priority validity to transmit at least one of the network slice priority validity and the network slice group priority validity to the RAN node. In this case, the AMF finds a suitable network slice together with its updated network slice priority and updated network slice group priority based on the received at least one of the network slice priority validity and the network slice group priority validity in step 4, and includes at least one of the network slice priority validity and the network slice group priority validity in the N2 message in step 5. The network slice priority validity and the network slice group priority validity may be the same as the network slice priority validity and the network slice group priority validity in variants 2, 3, and 4 of the first example of the first aspect.

[0140] For example, if the network slice priority validity includes validity for several days, the AMF checks whether today matches the specified date and sets the network slice priority in the N2 message accordingly. For example, if the AMF determines that today matches the date indicated by the network slice priority validity, the AMF sets the network slice priority in the N2 message. If the AMF determines that today matches the date indicated by the network slice priority validity and the network slice group priority validity, the AMF sets the network slice priority and the network slice group in the N2 message.

[0141] For example, if the network slice priority validity includes a specific TAI, the AMF checks whether the TAI of the connected RAN matches the specified TAI and sets the network slice priority in the N2 message accordingly. For example, if the AMF determines that the TAI of the connected RAN matches the TAI indicated by the network slice priority validity, the AMF sets the network slice priority in the N2 message. If the AMF determines that the TAI of the connected RAN matches the TAI indicated by the network slice priority validity and the network slice group priority validity, the AMF sets the network slice priority and the network slice group in the N2 message.

[0142] For example, if the network slice priority validity includes a specific PLMN, the AMF checks whether the PLMN to which the AMF belongs matches the specified PLMN and sets the network slice priority in the N2 message accordingly. For example, if the AMF determines that the PLMN to which the AMF belongs matches the PLMN indicated by the network slice priority validity, the AMF sets the network slice priority in the N2 message. If the AMF determines that the PLMN to which the AMF belongs matches the PLMN indicated by the network slice priority validity and the network slice group priority validity, the AMF sets the network slice priority and the network slice group in the N2 message.

[0143] For example, if the network slice priority validity includes a specific RAT type, the AMF checks whether the RAT type of the connected RAN matches the specified RAT type and sets the network slice priority in the N2 message accordingly. For example, if the AMF determines that the RAT type of the connected RAN matches the RAT type indicated by the network slice priority validity, the AMF sets the network slice priority in the N2 message. If the AMF determines that the RAT type of the connected RAN matches the RAT type indicated by the network slice priority validity and the network slice group priority validity, the AMF sets the network slice priority and the network slice group in the N2 message.

[0144] <System Overview> FIG. 9 shows a schematic diagram of a mobile (cellular or wireless) telecommunications system 1 to which the above aspects are applicable.

[0145] The telecommunications system 1 represents an overview of a system capable of end-to-end communication, e.g., UEs 3 (or user equipment, "mobile devices" 3) communicating with other UEs 3 or service servers within a data network 20 via respective (R)AN nodes 5 and a core network 7.

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

[0147] The (R)AN node 5 may be separated into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU), which in some aspects may be connected to each other to form the (R)AN node 5 by employing an architecture such as that defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as the O-RU, O-DU, and O-CU, respectively.

[0148] The (R)AN node 5 may be separated into control plane functions and user plane functions. Furthermore, multiple user plane functions may be allocated to support communications. In some aspects, user traffic may be distributed across multiple user plane functions, with user traffic in each user plane function being aggregated at both the UE 3 and the (R)AN node 5. This separated architecture may be referred to as "dual connectivity" or "multi-connectivity."

[0149] The (R)AN node 5 may also support communications using satellite access. In some aspects, the (R)AN node 5 may support satellite access and terrestrial access.

[0150] In addition, the (R)AN node 5 may also be referred to as an access node for non-wireless access, including fixed access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

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

[0152] By applying network virtualization technologies such as those defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV), network functions can be deployed as distributed, redundant, stateless, and scalable, providing services from several locations and providing several execution instances at each location.

[0153] The core network 7 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0154] As is known, as a UE 3 moves around the geographic area covered by the telecommunications system 1, the UE 3 may move in and out of areas (i.e., radio cells) served by (R)AN nodes 5. To keep track of the UE 3 and facilitate movement between various (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN nodes 5 connected to the core network 7. In some core networks, a mobility management entity (MME) or mobility management node for Beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0155] 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 Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Data Analytics Function (NWDAF) 76. When a UE 3 roams into a visited Public Land Mobile Network (VPLMN), the home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionality of the SMF 71, UPF 72, and PCF 73 to the roaming-out UE 3.

[0156] The UE 3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via appropriate (R)AN node interfaces (e.g., a so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (e.g., so-called core network nodes) via appropriate interfaces (e.g., a so-called "N2" / "N3" interface and / or the like). From the core network 7, a connection is also provided to a data network 20. The data network 20 may be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. If the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services may be provided by the data network 20. The UE 3 may be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types.

[0157] The "Uu" interface may include a control plane of the Uu interface and a user plane of the Uu interface.

[0158] The user plane of the Uu interface is responsible for carrying user traffic between the UE 3 and the serving (R)AN node 5. The user plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC, and MAC sublayers over the physical connection.

[0159] The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between the UE 3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers depending on the physical connection.

[0160] For example, the following messages are communicated at the RRC layer to support AS signaling:

[0161] - RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Request message: --establishmentCause and ue-Identity. The ue-Identity may have the value of ng-5G-S-TMSI-Part1 or a random value.

[0162] RRC Setup Message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup message: --Master cell group (masterCellGroup) and radio bearer configuration (radioBearerConfig)

[0163] - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the RRC Setup Complete message: --guami type (guami-Type), iab node indication (iab-NodeIndication), idle measurement available (idleMeasAvailable), mobility state (mobilityState), ng-5G-S-TMSI-Part2 (ng-5G-S-TMSI-Part2), registered AMF (registeredAMF), selected PLMN identity (selectedPLMN-Identity)

[0164] The UE 3 and the AMF 70 are connected via an appropriate interface (e.g., a so-called N1 interface and / or the like). The N1 interface is responsible for providing communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface can be established in 3GPP access and non-3GPP access. For example, the following messages are communicated on the N1 interface:

[0165] Registration Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together 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 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 IDID), Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.

[0166] Registration Accept Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the registration accept 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 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 valuevalue, 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.

[0167] Registration Complete Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by the aspects of the present disclosure, the following parameters may be included together in the registration complete message: --SOR transparent container.

[0168] -Authentication Request Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be included together in the Authentication Request message: --ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge), and EAP message.

[0169] Authentication Response Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication response message: Authentication response message identity, authentication response parameters, and EAP message.

[0170] -Authentication Result Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Authentication Result Message: --ngKSI, EAP message, and ABBA.

[0171] Authentication Failure Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Authentication Failure Message: --Authentication failure message identity, 5GMM cause, and authentication failure parameter.

[0172] -Authentication Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the authentication rejection message: --EAP message.

[0173] - Service Request Message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Request Message: --ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.

[0174] - Service Authorization Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Authorization Message: --PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0175] - Service Rejection Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Service Rejection Message: --5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0176] Configuration Update Command Message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the Configuration Update Command message: --Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI.

[0177] Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters disclosed by aspects of the present disclosure, the following parameters may be present together in the configuration update complete message: --Configuration update complete message identity.

[0178] <User equipment (UE)> FIG. 10 is a block diagram illustrating the main components of a mobile device 3 (UE 3). As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from a connection node via one or more antennas 32. The UE 3 may also include a user interface 34 for inputting and outputting information from an external device. Although not necessarily illustrated, the UE 3 may have all the usual functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware, as needed. For example, the software may be pre-installed in memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of the UE 3 in accordance with software stored in the 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 communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. 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 the UE 3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. In the case of multiple USIMs 35, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0179] The UE 3 may, for example, support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0180] UE3 may be, for example, an item of production or manufacturing equipment and / or an item of energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or application systems thereof, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machinery, printing machinery and / or related machinery, paper converting machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, agricultural, forestry, and / or fishing machinery and / or implements, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, fittings, and / or application systems for any of the foregoing equipment or machines).

[0181] UE 3 may be, for example, an item of transportation equipment (e.g., vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).

[0182] The UE 3 may be, for example, an item of information and communications equipment (eg, information and communications equipment such as electronic computers and related equipment, communications and related equipment, electronic components, etc.).

[0183] The UE3 may be, for example, a refrigeration machine, a refrigeration machine application product, an item of commercial and / or service industry equipment, a vending machine, an automated service machine, an office machine or device, a consumer electronic device and appliance (e.g., consumer electronic appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners, etc.).

[0184] The UE 3 may be, for example, an electrical application system or device (eg, an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, a power application device, etc.).

[0185] The UE3 may be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a tester, or a surveying or detecting device (e.g., a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, or other surveying or detecting device), a watch or wall clock, laboratory equipment, optical equipment, medical equipment and / or systems, a weapon, an item of cutlery, a hand tool, or the like.

[0186] UE3 may be, for example, a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, electrical measuring machine)).

[0187] The UE 3 may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the "Internet of Things (IoT)."

[0188] Internet of Things devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, allowing them to collect and exchange data with each other and with other communicating devices. IoT devices may comprise autonomous machines that follow software instructions stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or idle for long periods of time. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0189] It will be understood that IoT technology may be implemented on any communication device that can connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0190] It will be appreciated that an IoT device is sometimes referred to as a Machine-Type Communication (MTC) device or a Machine-to-Machine (M2M) communication device, or a Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0191] The UE 3 may be a smartphone or a wearable device (e.g., smart glasses, a smart watch, a smart ring, or a hearable device).

[0192] The UE3 may be a car, a connected car, an autonomous vehicle, a vehicle device, a motorcycle, or a Vehicle to Everything (V2X) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-person communication module, and a vehicle-to-network communication module).

[0193] <(R)AN node> FIG. 11 is a block diagram illustrating the main components of an exemplary (R)AN node 5, e.g., a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the (R)AN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from connected UEs 3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls operation of the (R)AN node 5 according to software stored in memory 55. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0194] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72, either directly or indirectly. The signaling may include, for example, properly formatted signaling messages related to the radio connection and connection to the core network 7 for a particular UE 3, especially those related to connection establishment and maintenance, such as RRC connection establishment messages and other RRC messages, NG Application Protocol (NGAP) messages (i.e., messages at the N2 reference point), Xn Application Protocol (XnAP) messages (i.e., messages at the Xn reference point), etc. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

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

[0196] (R)AN node 5 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0197] <System overview of (R)AN node 5 based on the O-RAN architecture> FIG. 12 schematically shows the (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.

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

[0199] The UE 3 and each serving RU 60 are connected via an appropriate air interface (e.g., a so-called "Uu" interface and / or the like). Each RU 60 is connected to a DU 61 via an appropriate interface (such as a so-called "fronthaul", "open fronthaul", "F1" interface, and / or the like). Each DU 61 is connected to a CU 62 via an appropriate interface (such as a so-called "midhaul", "open midhaul", "E2" interface, and / or the like). Each CU 62 is also connected to a node in the core network 7 (such as a so-called core network node) via an appropriate interface (such as a so-called "backhaul", "open backhaul", "N2" / "N3" interface, and / or the like). In addition, the user plane part of the DU 61 may also be connected to the core network node 7 via an appropriate interface (such as a so-called "N3" interface and / or the like).

[0200] Depending on the functionality split between the RU 60, DU 61, and CU 62, each unit provides a portion of the functionality provided by the (R)AN node 5. For example, the RU 60 may provide functionality for communicating with the UE 3 over the air interface, the DU 61 may provide functionality supporting the MAC and RLC layers, and the CU 62 may provide functionality supporting the PDCP, SDAP, and RRC layers.

[0201] <Radio Unit (RU)> FIG. 13 is a block diagram illustrating the main components of an exemplary RU 60, e.g., the RU portion of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 operable to transmit signals to and receive signals from an attached UE 3 via one or more antennas 602, and to transmit and receive signals to and from other network nodes or network portions via a network interface 603 (directly or indirectly). A controller 604 controls the operation of the RU 60 according to software stored in memory 605. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0202] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling between (e.g., directly or indirectly) the RU 60 and other nodes or entities, such as the UE 3, other RUs 60, and the DU 61. The signaling may include, for example, appropriately formatted signaling messages relating to the radio connection and connectivity with the RU 60 (for a particular UE 3), in particular the MAC and RLC layers.

[0203] When implemented, the controller 604 is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or motion trajectory estimation.

[0204] The RU 60 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0205] As described above, the RU 60 may be integrated / combined with the DU 61 as an integration / combination unit. Any function described for the RU 60 may be implemented in the integration / combination unit.

[0206] <Distributed Unit (DU)> FIG. 14 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU portion of a base station (eNB in ​​LTE, gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the device includes a transceiver circuit 611 operable to transmit signals to and receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 according to software stored in memory 614. For example, the software may be pre-installed in memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signaling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0207] The DU 61 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0208] As mentioned above, the RU 60 may be integrated / combined with the DU 61 or the CU 62 as an integrated / combined unit. Any functionality described for the DU 61 may be implemented in one of the integrated / combined units.

[0209] <Centralized Unit (CU)> FIG. 15 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU portion of a base station (e.g., an eNB in ​​LTE, a gNB in ​​5G, a base station for Beyond 5G, or a base station for 6G). As shown, the device includes a transceiver circuit 621 operable to transmit signals to and receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 according to software stored in memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded 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 communication control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signaling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0210] CU 62 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0211] As described above, the CU 62 may be integrated / combined with the DU 61 as an integration / combination unit. Any functionality described for the CU 62 may be implemented in the integration / combination unit.

[0212] <amf> 16 is a block diagram illustrating the main components of the AMF 70. As shown, the device includes a transceiver circuit 701 operable to transmit signals to and receive signals from other nodes (including UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in memory 704. For example, the software may be pre-installed in the memory 704 and / or downloaded 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 / sending / receiving) signaling between the AMF 70 and other nodes, such as the UE 3 (e.g., via (R)AN node 5) and other nodes, such as other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0213] The AMF 70 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0214] <pcf> 17 is a block diagram illustrating the main components of the PCF 73. As shown, the device includes a transceiver circuit 731 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in memory 734. For example, the software may be pre-installed in the memory 734 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a 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 / sending / receiving) signaling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to policy management procedures (for the UE 3).

[0215] The PCF 73 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0216] <nef> 18 is a block diagram illustrating the major components of the NEF 74. As shown, the device includes a transceiver circuit 741 operable to transmit signals to and receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the NEF 74 according to software stored in memory 744. For example, the software may be pre-installed in memory 744 and / or downloaded over a telecommunications network or from a removable data storage device (e.g., a 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 / sending / receiving) signaling between the NEF 74 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the UE 3's HPLMN when the UE 3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) related to network exposure function procedures (for the UE 3).

[0217] The NEF 74 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0218] <udm> 19 is a block diagram illustrating the major components of the UDM 75. As shown, the device includes a transceiver circuit 751 operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in memory 754. For example, the software may be pre-installed in memory 754 and / or downloaded 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 / sending / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to mobility management procedures (for the UE 3).

[0219] The UDM 75 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0220] <af> 20 is a block diagram illustrating the major components of the AF 77. As shown, the device includes a transceiver circuit 771 operable to transmit signals to and receive signals from other nodes (including the NEF 74) via a network interface 772. A controller 773 controls the operation of the AF 77 in accordance with software stored in memory 774. For example, the software may be pre-installed in memory 774 and / or downloaded via a telecommunications network or from a removable data storage 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 / sending / receiving) signaling between the AF 77 and other nodes, such as the NEF 74 and other core network nodes (including core network nodes in the UE 3's VPLMN when the UE 3 is roaming out). Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on service-based interfaces) relating to mobility management procedures (for the UE 3).

[0221] The AF 77 may support a Non-Public Network (NPN), which may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0222] <Modifications and Replacements> Detailed embodiments have been described above. Still, those skilled in the art will appreciate that numerous modifications and alternatives may be made to the above embodiments while having the benefit of the disclosure embodied herein. By way of example only, many such alternatives and modifications are now described.

[0223] In the above description, the UE 3 and network devices are described for ease of understanding as having a number of separate modules (such as a communications control module). These modules may be provided in this manner for particular applications, for example, where an existing system is modified to implement the present disclosure; in other applications, for example, in a system designed with inventive features in mind from the beginning; however, these modules may not be recognizable as separate entities because they may be built into an overall operating system or code. These modules may also be implemented in software, hardware, firmware, or a mixture of these.

[0224] Each controller may comprise any suitable form of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, and / or the like.

[0225] In the above embodiments, a number of software modules have been described. Those skilled in the art will understand that the software modules may be provided in compiled or uncompiled form, and may be provided to the UE 3 and network devices as signals over a computer network or on a recording medium. Furthermore, the functions performed by some or all of the software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred for updating the functions of the UE 3 and network devices, as they facilitate updating the UE 3 and network devices.

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

[0227] Items of user equipment may include, for example, communication devices such as mobile phones, smartphones, user appliances, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (and even generally fixed) devices are typically operated by a user, although so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices may also be connected to the network. For simplicity, this application will refer to mobile devices (or UEs) in the description, but it will be understood that the described techniques may be implemented on any (mobile and / or generally fixed) communication device that can connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0228] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0229] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and a system, and thus may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.

[0230] It will be understood that each block of the block diagrams can be implemented by computer program instructions. The computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to create a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the function / acts specified in the block or blocks of the flowcharts and / or block diagrams. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., multiple microprocessors, one or more microprocessors, or any other such configuration.

[0231] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such 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.

[0232] The previous description of examples of the present disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the 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 present disclosure. Thus, the present disclosure is not intended to be limited to the examples set forth herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0233] Although the present disclosure has been shown and described in detail with reference to exemplary embodiments thereof, the present disclosure is not limited to such embodiments. It will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined herein. For example, the above embodiments are not limited to 5GS, and the embodiments may also be applied to communication systems other than 5GS (e.g., 6G systems, Beyond 5G systems).

[0234] <Additional Notes> All or part of the exemplary aspects of the above disclosure may be described as, but are not limited to, the following supplementary notes.

[0235] Appendix 1. Change the priority associated with Single Network Slice Selection Assistance Information (S-NSSAI), sending the priority to a Network Exposure Function (NEF) device; Application Function (AF) device method.

[0236] Appendix 2. Receive a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Application Function (AF) device; sending the priority to a Unified Data Management (UDM) device; A method for a Network Exposure Function (NEF) device.

[0237] Appendix 3. Receive a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Network Exposure Function (NEF) device; storing the priority; A method for a Unified Data Management (UDM) device.

[0238] Appendix 4. receiving a registration request message from a User Equipment (UE); sending a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device; Receive a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device; sending a registration acknowledgement message to the UE including the priority; A method for an Access and Mobility Management Function (AMF) device.

[0239] Appendix 5. sending the registration accept message if the registration request message includes information indicating that the UE supports the priority; The method described in Appendix 4.

[0240] Appendix 6. receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; sending a UE configuration update message to a User Equipment (UE) including the priority; A method for an Access and Mobility Management Function (AMF) device.

[0241] Appendix 7. If the UE supports the priority, sending the UE Configuration Update message. The method described in Appendix 6.

[0242] Appendix 8. Sending a registration request message including information indicating that the UE supports a preference associated with Single Network Slice Selection Assistance Information (S-NSSAI); receiving a registration acceptance message including the priority; A User Equipment (UE) method.

[0243] Appendix 9. receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; updating the policy based on the priority; Sending the policy; A method for a Policy Control Function (PCF) device.

[0244] Appendix 10. receiving a policy including a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Policy Control Function (PCF) device; transmitting the policy to a User Equipment (UE); A method for an Access and Mobility Management Function (AMF) device.

[0245] Appendix 11. receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from a Unified Data Management (UDM) device; sending an N2 message including the S-NSSAI and the priority to a Radio Access Network (RAN) node; A method for an Access and Mobility Management Function (AMF) device.

[0246] Appendix 12. Receive Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from an Access and Mobility Management Function (AMF) device; using the priority for a process related to a handover or a process related to a PDU session; A method for a Radio Access Network (RAN) node.

[0247] Appendix 13. a means for modifying a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI); means for transmitting said priority to a Network Exposure Function (NEF) device; An Application Function (AF) device comprising:

[0248] Appendix 14. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Application Function (AF) device; means for transmitting said priority to a Unified Data Management (UDM) device; A Network Exposure Function (NEF) device comprising:

[0249] Appendix 15. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Network Exposure Function (NEF) device; means for storing the priority; A Unified Data Management (UDM) device comprising:

[0250] Appendix 16. means for receiving a registration request message from a User Equipment (UE); means for transmitting a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device; means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device; means for transmitting a registration acknowledgement message to the UE, the registration acknowledgement message including the priority; An Access and Mobility Management Function (AMF) device comprising:

[0251] Appendix 17. means for transmitting the registration accept message when the registration request message includes information indicating that the UE supports the priority; 17. The AMF device of claim 16.

[0252] Appendix 18. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; means for sending a UE configuration update message including the priority to a User Equipment (UE); An Access and Mobility Management Function (AMF) device comprising:

[0253] Appendix 19. means for transmitting the UE configuration update message if the UE supports the priority; 19. The AMF device of claim 18.

[0254] Appendix 20. means for transmitting a registration request message including information indicating that the UE supports preferences related to Single Network Slice Selection Assistance Information (S-NSSAI); means for receiving a registration approval message including the priority; A user equipment (UE) comprising:

[0255] Appendix 21. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; means for updating a policy based on the priority; means for transmitting the policy; A Policy Control Function (PCF) device comprising:

[0256] Appendix 22. means for receiving a policy including a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Policy Control Function (PCF) device; means for transmitting the policy to a User Equipment (UE); An Access and Mobility Management Function (AMF) device comprising:

[0257] Appendix 23. means for receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from a Unified Data Management (UDM) device; means for transmitting an N2 message including the S-NSSAI and the priority to a Radio Access Network (RAN) node; An access and mobility management function (AMF) device comprising:

[0258] Appendix 24. means for receiving Single Network Slice Selection Assistance Information (S-NSSAI) and a priority associated with the S-NSSAI from an Access and Mobility Management Function (AMF) device; means for using said priority for a process related to handover or a process related to a PDU session; A Radio Access Network (RAN) node comprising:

[0259] Although the present invention has been described above with reference to the embodiments (and examples), the present invention is not limited to the above-described embodiments (and examples). Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0260] This application claims priority to Indian Provisional Patent Application No. 202111050762, filed on November 5, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0261] 1. Telecommunications Systems 3UE 5 (R)AN nodes 7 Core Network 20 Data Network 31 Transceiver Circuit 32 Antenna 33 Controller 34 User Interface 35 USIM 36 memory 51 Transceiver circuit 52 Antenna 53 Network Interface 54 Controller 55 memory 60RU 61 DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 NEF 75 UDM 76 NWDAF 77AF 361 Operating Systems 362 Communication Control Module 551 Operating Systems 552 Communication Control Module 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 memory 611 Transceiver Circuit 612 Network Interface 613 Controller 614 memory 621 Transceiver Circuit 622 network interface 623 Controller 624 memory 701 Transceiver Circuit 702 network interface 703 Controller 704 memory 731 Transceiver Circuit 732 network interface 733 Controller 734 memory 741 Transceiver Circuit 742 network interfaces 743 Controller 744 memory 751 Transceiver Circuit 752 network interfaces 753 Controller 754 memory 771 Transceiver Circuit 772 network interfaces 773 Controller 774 memory 3621 Transceiver Control Module 5521 Transceiver Control Module 6051 Operating System 6052 Communication Control Module 6141 Operating System 6142 Communication Control Module 6241 Operating System 6242 Communication Control Module 7041 Operating System 7042 Communication Control Module 7341 Operating System 7342 Communication Control Module 7441 Operating System 7442 Communication Control Module 7541 Operating Systems 7542 Communication Control Module 7741 Operating System 7742 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 73421 Transceiver Control Module 74421 Transceiver Control Module 75421 Transceiver Control Module 77421 Transceiver Control Module< / af> < / udm> < / nef> < / pcf> < / amf>

Claims

1. receiving a registration request message from a User Equipment (UE); Sending a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device; receiving first information related to Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device; sending a registration accept message to the UE, the registration accept message including a priority associated with the S-NSSAI determined based on the first information; A method for an Access and Mobility Management Function (AMF) device.

2. If the registration request message includes information indicating that the UE supports the priority, sending the registration accept message including the priority associated with the S-NSSAI. The method of claim 1 .

3. receiving first information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; sending a UE Configuration Update message to a User Equipment (UE) including a priority associated with the S-NSSAI determined based on the first information; A method for an Access and Mobility Management Function (AMF) device.

4. If the UE supports the priority, sending the UE Configuration Update message including the priority associated with the S-NSSAI. The method of claim 3 .

5. Sending a Registration Request message including information indicating that the User Equipment (UE) supports preferences associated with Single Network Slice Selection Assistance Information (S-NSSAI); receiving a registration accept message including the priority or a UE configuration update message including the priority; UE method.

6. receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; updating the policy based on the priority; Sending the policy; A method for a Policy Control Function (PCF) device.

7. receiving a policy including a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Policy Control Function (PCF) device; transmitting the policy to a User Equipment (UE); A method for an Access and Mobility Management Function (AMF) device.

8. receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; sending an N2 message including the priority to a Radio Access Network (RAN) node; A method for an Access and Mobility Management Function (AMF) device.

9. receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Access and Mobility Management Function (AMF) device; Using the priority for a process related to handover or a process related to a PDU session; A method for a Radio Access Network (RAN) node.

10. means for receiving a registration request message from a User Equipment (UE); means for transmitting a Subscription Permanent Identifier (SUPI) associated with the UE to a Unified Data Management (UDM) device; means for receiving first information related to Single Network Slice Selection Assistance Information (S-NSSAI) from the UDM device; means for transmitting to the UE a registration accept message including a priority associated with the S-NSSAI determined based on the first information; An Access and Mobility Management Function (AMF) device comprising:

11. means for transmitting the registration accept message including the priority associated with the S-NSSAI if the registration request message includes information indicating that the UE supports the priority; The AMF device of claim 10.

12. means for receiving first information related to Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; means for transmitting a UE Configuration Update message to a User Equipment (UE) including a priority associated with the S-NSSAI determined based on the first information; An Access and Mobility Management Function (AMF) device comprising:

13. means for transmitting the UE Configuration Update message including the priority associated with the S-NSSAI if the UE supports the priority; The AMF device of claim 12.

14. means for transmitting a registration request message including information indicating that a User Equipment (UE) supports preferences related to Single Network Slice Selection Assistance Information (S-NSSAI); means for receiving a registration accept message including the priority or a UE configuration update message including the priority; A UE comprising:

15. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; means for updating a policy based on the priority; means for transmitting the policy; A Policy Control Function (PCF) device comprising:

16. means for receiving a policy including a preference associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Policy Control Function (PCF) device; means for transmitting the policy to a User Equipment (UE); An Access and Mobility Management Function (AMF) device comprising:

17. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from a Unified Data Management (UDM) device; means for transmitting an N2 message including the priority to a Radio Access Network (RAN) node; An access and mobility management function (AMF) device comprising:

18. means for receiving a priority associated with Single Network Slice Selection Assistance Information (S-NSSAI) from an Access and Mobility Management Function (AMF) device; means for using the priority for a process related to handover or a process related to a PDU session; A Radio Access Network (RAN) node comprising:

19. using the priority for at least one of cell selection or cell reselection; The UE method of claim 5.

20. means for using the priority for at least one of cell selection or cell reselection; 15. The UE of claim 14.

Images