AMF, NG-RAN node, AMF method and NG-RAN node method

Abstract

The system design disclosed by R2-2108928 works with a basic 5GS network structure. On the other hand, there are many variants of 5GS available according to the 3GPP specifications. Since the system design disclosed by R2-2108928 does not take into account the variants of 5GS available according to the 3GPP specifications, there are cases where the system design disclosed by R2-2108928 does not work with the variants. [Solution] The method of an Access and Mobility Management Function (AMF) apparatus includes sending a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI), receiving a second message including the PLMN ID and the S-NSSAI associated with the identifier, and sending the S-NSSAI associated with the identifier.

Description

[Technical Field]

[0001] The present disclosure relates to a method for an Access and Mobility Management Function (AMF) device, a method for a Next Generation-Radio Access Network (NG-RAN) node, a method for a User Equipment (UE), a method for a Master Node (MN), an AMF device, an NG-RAN node, a UE, and an MN. [Background technology]

[0002] At the 3GPP RAN WG2#115-e meeting, R2-2108928, LS on Slice list and priority information for cell reselection (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:

[0004] -Slice-specific absolute priority for each slice of the frequency that supports slicing ("Slice Info")

[0005] The UE receives slice info using RRC signaling (system information and / or dedicated RRC signaling).

[0006] - A list of slices with slice priorities for cell reselection.

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

[0008] This cell reselection evaluation is designed based on the following design principles.

[0009] - The frequency priority mapping for each slice (slice -> frequency -> absolute priority of each frequency) is provided to the UE.

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

[0011] 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]

[0012] [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] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". V16.7.0 (2021-10) [Non-patent document 4] 3GPP TS 23.251: "Network sharing; Architecture and functional description". V16.0.0 (2020-07) [Non-Patent Document 5] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". V16.6.0 (2021-06) [Non-patent document 6] 3GPP TS 37.340: “NR; Multi-connectivity; Overall description; Stage-2”. V16.7.0 (2021-09) Summary of the Invention [Problem to be solved by the invention]

[0013] The system design disclosed by Non-Patent Document 2 works with a basic 5GS network structure, whereas there are many variants of 5GS available according to the 3GPP specifications.

[0014] The system design disclosed by Non-Patent Document 2 does not take into account the 5GS variants available according to the 3GPP specifications, and therefore there are cases in which the system design disclosed by Non-Patent Document 2 does not work with the variants.

[0015] For example, Non-Patent Document 4 discloses RAN sharing by multiple PLMN operators, and there are cases where the system design disclosed in Non-Patent Document 2 does not function properly in a shared RAN.

[0016] For example, Non-Patent Document 6 discloses multi-radio dual connectivity, and there are cases where the system design disclosed in Non-Patent Document 2 does not function properly in a multi-radio dual connectivity environment. [Means for solving the problem]

[0017] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) apparatus transmits a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI), receives a second message including the PLMN ID and the S-NSSAI associated with the identifier, and transmits the S-NSSAI associated with the identifier.

[0018] In an aspect of the disclosure, a method in a Next Generation-Radio Access Network (NG-RAN) node receives a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI), transmits a second message including the PLMN ID and the S-NSSAI associated with an identifier, and transmits a third message including the identifier associated with the PLMN ID.

[0019] In an aspect of the present disclosure, a method for a User Equipment (UE) includes receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier, receiving a second message including the identifier associated with the PLMN ID, and performing cell selection or cell reselection after receiving the first message and the second message.

[0020] In an aspect of the present disclosure, a method in an Access and Mobility Management Function (AMF) apparatus receives a first message including information indicating a range of an identifier, transmits a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier, and transmits the S-NSSAI associated with the identifier.

[0021] In an aspect of the present disclosure, a method in a Next Generation-Radio Access Network (NG-RAN) node transmits a first message including information indicating a range of identifiers, receives a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier, and transmits a third message including the identifier associated with the PLMN ID.

[0022] In an aspect of the present disclosure, a method of a Master Node (MN) transmits a Group Identifier (GP ID) that identifies a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a frequency band priority, and information indicating a frequency band to be used by a Secondary Node (SN).

[0023] In an aspect of the present disclosure, a method for a Master Node (MN) transmits a Group Identifier (GP ID) for identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI) and information indicating a priority of a frequency band, wherein the information indicating the priority of the frequency band includes a priority of a frequency band combination including a frequency band of the MN and a frequency band of a Secondary Node (SN).

[0024] In an aspect of the present disclosure, a method for a User Equipment (UE) includes receiving a Group Identifier (GP ID) identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a frequency band priority, and information indicating a frequency band used by a Secondary Node (SN), and performing cell selection or cell reselection based on the GP ID, the information indicating the frequency band priority, and the information indicating the frequency band used by the SN.

[0025] In an aspect of the present disclosure, a method for a User Equipment (UE) includes receiving a first Group Identifier (GP ID) identifying a group including a first Single Network Slice Selection Assistance Information (S-NSSAI) and information indicating a priority of a frequency band, receiving a list of Master Nodes (MNs) and a second Group Identifier (GP ID) identifying a group including a second S-NSSAI, and performing cell selection or cell reselection based on the first GP ID, the information indicating the priority of the frequency band, the list, and the second GP ID.

[0026] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) device includes means for transmitting a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI), means for receiving a second message including the PLMN ID and the S-NSSAI associated with the identifier, and means for transmitting the S-NSSAI associated with the identifier.

[0027] In an aspect of the present disclosure, a Next Generation-Radio Access Network (NG-RAN) node includes means for receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI), means for transmitting a second message including the PLMN ID and the S-NSSAI associated with an identifier, and means for transmitting a third message including the identifier associated with the PLMN ID.

[0028] In an aspect of the present disclosure, a User Equipment (UE) includes means for receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier, means for receiving a second message including the identifier associated with the PLMN ID, and means for performing cell selection or cell reselection after receiving the first message and the second message.

[0029] In an aspect of the present disclosure, an Access and Mobility Management Function (AMF) apparatus includes means for receiving a first message including information indicating a range of an identifier; means for transmitting a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier; and means for transmitting the S-NSSAI associated with the identifier.

[0030] In an aspect of the present disclosure, a Next Generation-Radio Access Network (NG-RAN) node includes means for transmitting a first message including information indicating a range of identifiers, means for receiving a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifiers, and means for transmitting a third message including the identifiers associated with the PLMN ID.

[0031] In an aspect of the present disclosure, a Master Node (MN) includes means for transmitting a Group Identifier (GP ID) that identifies a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a priority of a frequency band, and information indicating a frequency band used by a Secondary Node (SN).

[0032] In an aspect of the present disclosure, a Master Node (MN) includes means for transmitting a Group Identifier (GP ID) for identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI) and information indicating a priority of a frequency band, wherein the information indicating the priority of the frequency band includes a priority of a frequency band combination including a frequency band of the MN and a frequency band of a Secondary Node (SN).

[0033] In an aspect of the present disclosure, a User Equipment (UE) includes: means for receiving a Group Identifier (GP ID) identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a priority of a frequency band, and information indicating a frequency band used by a Secondary Node (SN); and means for performing cell selection or cell reselection based on the GP ID, the information indicating the priority of the frequency band, and the information indicating the frequency band used by the SN.

[0034] In an aspect of the present disclosure, a User Equipment (UE) includes: means for receiving a first Group Identifier (GP ID) that identifies a group including a first Single Network Slice Selection Assistance Information (S-NSSAI) and information indicating a priority of a frequency band; means for receiving a list of Master Nodes (MNs) and a second Group Identifier (GP ID) that identifies a group including a second S-NSSAI; and means for performing cell selection or cell reselection based on the first GP ID, the information indicating the priority of the frequency band, the list, and the second GP ID. [Brief explanation of the drawings]

[0035] [Figure 1] FIG. 1 shows the new information in the 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 second example of the first embodiment. [Figure 5] FIG. 5 is a signaling diagram of a first example of the second embodiment. [Figure 6] FIG. 6 is a signaling diagram of a second example of the second embodiment. [Figure 7] FIG. 7 is a flowchart of a second example of the second embodiment. [Figure 8] FIG. 8 is a signaling diagram of a first variant of the second example of the second embodiment. [Figure 9] FIG. 9 is a signaling diagram of a second variant of the second example of the second embodiment. [Figure 10] FIG. 10 is a diagram showing an outline of the system. [Figure 11]FIG. 11 is a block diagram illustrating a user equipment (UE). [Figure 12] FIG. 12 is a block diagram illustrating an (R)AN node. [Figure 13] FIG. 13 is a diagram illustrating a system overview of an (R)AN node based on the O-RAN architecture. [Figure 14] FIG. 14 is a block diagram showing a radio unit (RU). [Figure 15] FIG. 15 is a block diagram showing a distributed unit (DU). [Figure 16] FIG. 16 is a block diagram showing a centralized unit (CU). [Figure 17] FIG. 17 is a block diagram illustrating the Access and Mobility Management Function (AMF). [Figure 18] FIG. 18 is a block diagram illustrating Unified Data Management (UDM). DETAILED DESCRIPTION OF THE INVENTION

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

[0037] 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 BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre 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 RAT Radio Access Technology 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

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

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

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

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

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

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

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

[0045] Each aspect and the 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.

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

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

[0048] This disclosure enables 5GS to perform cell selection and cell reselection based on per-user (UE) network slice priorities based on broadcast information applicable to various 5GS network configurations, such as a RAN shared by multiple PLMN operators, or a RAN configured with multi-radio dual connectivity.

[0049] <First aspect> Non-Patent Document 4 discloses RAN sharing by multiple PLMN operators. In this case, multiple 5GCs are connected to the RAN. This option in 5GS is called a Multi-Operator Core Network (MOCN). When an MOCN is implemented, broadcast system information is broadcast in each cell in the shared radio access network and includes information about available core network operators in the shared network. The system information may be referred to as broadcast system information in this disclosure.

[0050] The broadcast system information includes a basic set of PLMN IDs and, optionally, one or more additional sets of PLMN IDs. The available core network operators are the same for all cells of a tracking area within a shared RAN. Due to the basic set and additional sets, different PLMNs or sets of PLMNs can have different cell IDs and TACs.

[0051] A supporting UE (eg, a UE supporting RAN sharing) decodes the broadcast system information and takes information about available core network operators into account in network selection, cell selection, and cell reselection procedures.

[0052] The system design disclosed in Non-Patent Document 2 does not appear to function properly in a shared RAN. According to Non-Patent Document 2, group IDs are provided by the core network through the NAS layer, and each group ID is associated with a network slice. On the other hand, supported group IDs are provided by the RAN through the AS layer. Since each group ID and the associated network slice are different among connected operators, it requires a mechanism to coordinate group IDs so that they are valid for all connected operators.

[0053] This disclosure discloses mechanisms that enable cell selection and cell reselection based on network slice priorities in 5GS where the RAN is shared by multiple PLMN operators.

[0054] <First Example of First Aspect> The present disclosure discloses a method for supporting broadcasting of network slice group identity (or network slice group identities) in a cell shared by multiple PLMNs. A Next Generation-Radio Access Network (NG-RAN) is shared by multiple PLMNs. Each AMF of a PLMN connected to the same NG-RAN sends an NGAP message to the NG-RAN. The NGAP message may be an existing NGAP message or a new NGAP message. The NGAP message includes a PLMN ID and grouped network slice(s) supported by the AMF. The NG-RAN assigns a network slice group identity to each grouped network slice and indicates the network slice group identity and the associated network slice to the AMF. The AMF stores the network slice and the associated network slice group identity.

[0055] When a UE indicating support for the network slice group identity function registers with the AMF of a PLMN through a registration procedure, the AMF sends the network slice and associated slice group identity to the UE through a registration accept message. When the UE receives the network slice and associated slice group identity, the UE stores this information (e.g., the network slice and associated slice group identity) and uses this stored information to determine whether a cell supports a specific network slice by checking whether the network slice group identity associated with the specific network slice is broadcast in a SIB. The SIB may be an existing SIB or a new SIB. The SIB may be a system information block and may be referred to as a SIB message in this disclosure. If the network slice group identity associated with the specific network slice is broadcast in a SIB, the UE determines that the cell supports the specific network slice and remains tuned to the cell. Tuning to a cell may be referred to as cell selection or reselection.

[0056] The detailed process of the first example of the first aspect is as follows.

[0057] Step 0. NG-RAN 5 is shared by PLMN1 and PLMN2, and NG-RAN 5 is connected to AMF 7001 of PLMN1 and AMF 7002 of PLMN2. AMF 7001 may be included in Core network (CN) 1. AMF 7002 may be included in CN2.

[0058] Step 1a. AMF 7001 sends an existing NGAP message or a new NGAP message to NG-RAN 5, including PLMN ID1 and a list of grouped S-NSSAI(s) supported by AMF 7001, requesting NG-RAN 5 to allocate network slice group identities. The NGAP message may be represented as an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message. The NGAP-SLICE GROUP ID CONFIGURATION REQUEST message may include the information elements PLMN ID1, {S-NSSAI1}, and {S-NSSAI2, S-NSSAI3}. For example, if AMF7001 supports network slice 1 indicated by S-NSSAI1, network slice 2 indicated by S-NSSAI2, and network slice 3 indicated by S-NSSAI3, AMF7001 groups the network slices into, for example, a first network slice group including S-NSSAI1 and a second network slice group including S-NSSAI2 and S-NSSAI3. AMF7001 may send an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message to NG-RAN5, which includes PLMN ID1 and a list of two network slice groups, {S-NSSAI1} and {S-NSSAI2, S-NSSAI3}. PLMN ID1 may indicate the PLMN ID of AMF7001. "{S-NSSAI1}" and "{S-NSSAI2, S-NSSAI3}" may mean that S-NSSAI1, 2, and 3 are grouped into a first network slice group including S-NSSAI1 and a second network slice group including S-NSSAI2 and 3.AMF7001 may send an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message to NG-RAN5 including PLMN ID1 and information indicating a first network slice group including S-NSSAI1 and a second network slice group including S-NSSAI2 and 3.

[0059] Step 1b. NG-RAN 5 assigns or allocates network slice group identification information to each grouped S-NSSAI received in step 1a and sends an existing NGAP message or a new NGAP message to AMF 7001. The NGAP message may be represented as an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message. The NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message may include information elements of PLMN ID1, GP ID1 = {S-NSSAI1}, and GP ID2 = {S-NSSAI2, S-NSSAI3}. For example, when NG-RAN 5 receives an NGAP-SLICE GROUP ID CONFIGURATION REQUEST from AMF 7001, NG-RAN 5 may assign GP ID1 (or group ID1) to the first network slice group including S-NSSAI1 and assign GP ID2 (or group ID2) to the second network slice group including S-NSSAI2 and S-NSSAI3. NG-RAN5 may be represented as a gNB, a base station, an (R)AN node, an NG-RAN node, or any other. NG-RAN5 sends an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message to AMF7001, including PLMN ID1, a first network slice group to which GP ID1 is assigned, and a second network slice group to which GP ID2 is assigned. "GP ID1={S-NSSAI1}" and "GP ID2={S-NSSAI2, S-NSSAI3}" may mean that GP ID1 is assigned to the first network slice group including S-NSSAI1, and GP ID2 is assigned to the second network slice group including S-NSSAI2 and 3.NG-RAN5 may send an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message to AMF7001 including PLMN ID1 and information indicating that GP ID1 is assigned to a first network slice group including S-NSSAI1 and that GP ID2 is assigned to a second network slice group including S-NSSAI2 and 3.

[0060] Instead of or in addition to "GP ID1={S-NSSAI1}, GP ID2={S-NSSAI2, S-NSSAI3}", the NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message may include a list of S-NSSAIs and associated network slice group identities. For example, the NGAP-SLICE GROUP ID CONFIGURATION RESPONSE may include a first list that includes S-NSSAI1 and is associated with GP ID1 (or network slice group identity 1). The NGAP-SLICE GROUP ID CONFIGURATION RESPONSE may further include a second list that includes S-NSSAI2 and 3 and is associated with GP ID2 (or network slice group identity 2).

[0061] Step 2a. Similarly, AMF7002 sends an existing NGAP message or a new NGAP message including PLMN ID2 and a list of grouped S-NSSAIs supported by AMF7002, requesting NG-RAN5 to assign or allocate network slice group identities. The NGAP message may be represented as an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message. The NGAP-SLICE GROUP ID CONFIGURATION REQUEST message may include information elements of PLMN ID2 and {S-NSSAI1}. For example, if AMF7002 supports network slice 1 indicated by S-NSSAI1, AMF7002 groups network slices into a network slice group including, for example, S-NSSAI1. AMF7002 may send an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message including PLMN ID2 and a list of network slice groups of {S-NSSAI1} to NG-RAN5. PLMN ID2 may indicate the PLMN ID of AMF7002. "{S-NSSAI1}" may mean that S-NSSAI1 is grouped into a network slice group. AMF7002 may send an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message to NG-RAN5, which includes PLMN ID2 and information indicating the network slice group that includes S-NSSAI1.

[0062] Step 2b. NG-RAN 5 assigns or allocates a network slice group identity to each grouped S-NSSAI received in step 2a and sends an existing NGAP message or a new NGAP message to AMF 7002. The NGAP message may be represented as an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message. The NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message may include information elements of PLMN ID2 and GP ID1={S-NSSAI1}. For example, when NG-RAN 5 receives an NGAP-SLICE GROUP ID CONFIGURATION REQUEST message from AMF 7002, NG-RAN 5 may assign GP ID1 (or group ID1) to the network slice group including S-NSSAI1. NG-RAN 5 may be represented as a gNB, a base station, an (R)AN node, an NG-RAN node, or any other. NG-RAN5 sends an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message to AMF7002, including PLMN ID2 and the network slice group to which GP ID1 is assigned. "GP ID1={S-NSSAI1}" may mean that GP ID1 is assigned to the network slice group that includes S-NSSAI1. NG-RAN5 may send an NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message to AMF7002, including PLMN ID2 and information indicating that GP ID1 is assigned to the network slice group that includes S-NSSAI1.

[0063] Instead of or in addition to "GP ID1={S-NSSAI1}", the NGAP-SLICE GROUP ID CONFIGURATION RESPONSE message may include a list of S-NSSAIs and associated network slice group identities. For example, the NGAP-SLICE GROUP ID CONFIGURATION RESPONSE may include a list that includes S-NSSAI1 and is associated with GP ID1 (or network slice group identity 1).

[0064] Step 3. The cell connected to the NG-RAN 5 broadcasts a list of network slice group identities supported by the cell for each PLMN in a new SIB or an existing SIB. The following format is an example of a SIB: The cell broadcasts the supported network slice group identity (or supported network slice group identities) for each PLMN.

[0065] SIB X(PLMN ID1(GP ID1, GP ID2), PLMN ID2(GP ID1))

[0066] For example, a gNB, base station, (R)AN node, or NG-RAN node may broadcast a SIB or SIB message in a cell that includes a list of network slice group identities for each PLMN. The list of network slice group identities may include GP ID1 and GP ID2 associated with PLMN ID1 and GP ID1 associated with PLMN ID2. "SIB X(PLMN ID1(GP ID1, GP ID2), PLMN ID2(GP ID1))" may mean that the SIB or SIB message includes GP ID1 and GP ID2 associated with PLMN ID1 and GP ID1 associated with PLMN ID2.

[0067] Step 4. UE3 initiates the registration procedure with AMF7001 of PLMN1 by sending a registration request message including UE capability information indicating whether UE3 supports the network slice group identity function. The UE capability information may indicate UE support for the network slice group identity function in the present disclosure. For example, if UE3 is configured to recognize or understand the above SIB format or the content of the SIB or SIB message, UE3 supports the network slice group identity function. The SIB format may be SIB X(PLMN ID1 (GP ID1, GP ID2), PLMN ID2 (GP ID1)). The content of the SIB or SIB message may include a list of network slice group identities in the cell for each PLMN. In this case, UE3 sends a registration request message including UE capability information indicating that UE3 supports the network slice group identity function. The network slice group identity function may mean that UE3 recognizes or understands network slice group identities and interacts with associated nodes. The associated nodes may be represented as AMF and / or NG-RAN and / or any other core network node. The registration request message may include a Requested NSSAI.

[0068] During the registration procedure, the AMF 7001 sends a list of S-NSSAIs and associated network slice group identities to the UE 3 in an existing NAS message or a new NAS message. The NAS message may be expressed as a registration accept message or a UE configuration update message. For example, if the UE 3 indicates that it supports the network slice group identity function, the AMF 7001 sends a list of S-NSSAIs and associated network slice group identities to the UE 3.

[0069] For example, the list of S-NSSAIs and associated network slice group identities sent by AMF7001 may be the same as those received from NG-RAN5 in step 1b. For example, the list of S-NSSAIs and associated network slice group identities may indicate GP ID1 = {S-NSSAI1} and GP ID2 = {S-NSSAI2, S-NSSAI3}. For example, the list of S-NSSAIs and associated network slice group identities may indicate a first list that includes S-NSSAI1 and is associated with GP ID1 (or network slice group identity 1). The list of S-NSSAIs and associated network slice group identities may also indicate a second list that includes S-NSSAI2 and 3 and is associated with GP ID2 (network slice group identity 2).

[0070] The AMF 7001 may also send the Allowed NSSAI and the Configured NSSAI to the UE 3 in a NAS message during the registration procedure. The AMF 7001 may send the list of S-NSSAIs and associated network slice group identification information for all S-NSSAIs in the Configured NSSAI to the UE 3.

[0071] Instead of the registration procedure with AMF7001, UE3 may perform a registration procedure with AMF7002 of PLMN2. The registration procedure with AMF7002 of PLMN2 may be performed in a similar manner as described above. For example, AMF7001 may be changed to AMF7002, and the list of S-NSSAIs and associated network slice group identification information sent by AMF7002 may be the same as those received from NG-RAN5 in step 2b. UE3 may perform both the registration procedure with AMF7001 of PLMN1 and the registration procedure with AMF7002 of PLMN2. For simplicity, the following steps and variations may be described in the case where UE3 performs the registration procedure with AMF7001 of PLMN1, but are not limited to this.

[0072] Step 5. If UE3 receives and stores the list of S-NSSAIs and associated network slice group identities from AMF7001, or decides by itself to perform a cell selection procedure or a cell reselection procedure, UE3 performs the cell selection procedure or the cell reselection procedure. The cell selection procedure may be expressed as cell selection, and the cell reselection procedure may be expressed as cell reselection. UE3 may select or reselect a cell to be used. UE3 may select or reselect a cell based on the list of S-NSSAIs and associated network slice group identities. UE3 may use the list of S-NSSAIs and associated network slice group identities to determine whether the cell supports a specific network slice by checking whether the network slice group identity associated with the specific network slice is broadcast in the SIB in step 3. If the network slice group identity associated with the specific network slice is broadcast in the SIB, UE3 determines that the cell supports the specific network slice and remains tuned to the cell. Tuning to a cell may be expressed as cell selection or reselection. A specific network slice may be represented as a specific S-NSSAI. The specific network slice may be determined based on an authorized NSSAI, a requested NSSAI, a configured NSSAI, or any other policy. The UE 3 may select or reselect a cell based on the list of S-NSSAIs, the associated network slice group identity, and the authorized NSSAI, the requested NSSAI, the configured NSSAI, or any other policy. For example, the UE 3 selects or reselects a cell that broadcasts a network slice group identity corresponding to the S-NSSAI in the authorized NSSAI, the requested NSSAI, or the configured NSSAI. The UE 3 may select or reselect a cell that broadcasts a network slice group identity associated with a high-priority S-NSSAI in the authorized NSSAI. The authorized NSSAI may include priority information for the S-NSSAI included in the authorized NSSAI.

[0073] The UE 3 may select or reselect a cell that broadcasts a network slice group identity associated with a high-priority S-NSSAI in the configuration NSSAI. The configuration NSSAI may include priority information for the S-NSSAI included in the configuration NSSAI.

[0074] For example, UE3 determines the correspondence between the network slice (or S-NSSAI) and the network slice group identity based on the list of S-NSSAIs and the associated network slice group identity received in step 4.

[0075] For example, UE3 determines that GP ID1 is associated with (or corresponds to) S-NSSAI1 based on the first list received in step 4, which includes S-NSSAI1 and is associated with GP ID1. For example, UE3 determines that GP ID2 is associated with (or corresponds to) S-NSSAI2 and 3 based on the second list received in step 4, which includes S-NSSAI2 and 3 and is associated with GP ID2.

[0076] For example, if UE3 determines that GP ID1 is associated with (or corresponds to) S-NSSAI1 based on the first list received in step 4 that includes S-NSSAI1 and is associated with GP ID1, UE3 selects or reselects, based on the information received in step 3, a cell in which GP ID1 corresponding to PLMN ID1 and S-NSSAI1 are broadcast.

[0077] For example, if UE3 determines that the received authorized NSSAI includes S-NSSAI1, the UE selects or reselects a cell in which GP ID1 corresponding to S-NSSAI1 is broadcast.

[0078] For example, if UE3 determines that the received authorized NSSAI includes S-NSSAI1, UE3 selects or reselects, based on the information received in step 3, a cell in which GP ID1 corresponding to PLMN ID1 and S-NSSAI1 are broadcast.

[0079] For example, if the allowed NSSAI includes S-NSSAI1 and S-NSSAI2 and priority information for S-NSSAI1, UE3 may select or reselect a cell that broadcasts GP ID1 corresponding to S-NSSAI1.

[0080] If the Grant NSSAI is not received by the UE 3, the UE 3 may select or reselect a cell based on the Request NSSAI or any other policy.

[0081] Steps 6a to 6c: When the UE 3 initiates an initial NAS procedure, the UE 3 initiates an RRC connection establishment procedure. The initial NAS procedure may be referred to as a registration procedure.

[0082] For example, after UE 3 selects or reselects a cell in step 5, it initiates an initial NAS procedure in the cell.

[0083] For example, if the selected cell supports the S-NSSAI in the configuration NSSAI received in step 4, but the S-NSSAI is not in the authorized NSSAI received in step 4, UE3 initiates an initial NAS procedure in the cell after selecting or reselecting a cell in step 5.

[0084] To initiate an RRC connection establishment procedure, the UE 3 may send an RRC Setup Request message to the NG-RAN 5 in step 6a. The UE 3 may receive an RRC Setup message from the NG-RAN 5 in response to the RRC Setup Request message in step 6b.

[0085] For example, the UE 3 sends an RRC Setup Complete message in step 6c during the RRC connection establishment procedure. The RRC Setup Complete message is used to confirm the successful completion of the RRC connection establishment procedure.

[0086] The RRC setup complete message may include a list of network slice group identities corresponding to the network slices (or S-NSSAIs) in the authorization NSSAI, configuration NSSAI, or request NSSAI.

[0087] For example, if UE3 selects or reselects a cell that broadcasts GP ID1 corresponding to S-NSSAI1 in step 5, UE3 includes GP ID1 in the RRC Setup Complete message.

[0088] For example, if UE3 determines that the received authorized NSSAI includes S-NSSAI1, UE3 includes GP ID1 corresponding to S-NSSAI1 in the RRC Setup Complete message.

[0089] For example, if UE3 includes S-NSSAI1 in the Requested NSSAI, UE3 includes GP ID1 corresponding to S-NSSAI1 in the RRC Setup Complete message.

[0090] The RRC Setup Complete message may include a Registration Request message, which may be referred to in this disclosure as a Registration Request, a Registration Request message, or a Registration Request.

[0091] The registration request message may include UE capability information indicating that the UE 3 supports the network slice group identity function.

[0092] The registration request message may include a request NSSAI including an S-NSSAI1 corresponding to GP ID 1. The request NSSAI including an S-NSSAI1 corresponding to GP ID 1 may be represented as "request NSSAI(S-NSSAI1=GP ID1)".

[0093] The registration request message may include a list of network slice group identities (or GP IDs or GP IDs) corresponding to the S-NSSAI in the authorization NSSAI, configuration NSSAI, or request NSSAI.

[0094] For example, the registration request message may include GP ID1 corresponding to S-NSSAI1.

[0095] The list of network slice group identities may also be referred to as allowed network slice group identities.

[0096] Step 7. The NG-RAN 5 forwards the registration request message received by the RRC setup complete message from the UE 3 to the AMF 7001 by the NGAP INITIAL UE message. Upon receiving the registration request message, the AMF 7001 processes the registration procedure by using the S-NSSAI1 corresponding to the GP ID 1.

[0097] <Modification 1 of the first example of the first aspect> In some examples, the messages in step 1a and step 2a may be an NG SETUP RESPONSE message, a RAN CONFIGURATION UPDATE ACKNOWLEDGE message, or an AMF CONFIGURATION UPDATE message as described in Non-Patent Document 3.

[0098] <Modification 2 of the first example of the first aspect> In some examples, the messages in step 1b and step 2b may be an NG SETUP REQUEST message, a RAN CONFIGURATION UPDATE message, or an AMF CONFIGURATION UPDATE ACKNOWLEDGE message as described in Non-Patent Document 3.

[0099] <Modification 3 of the first example of the first aspect> In some examples, in step 5, if UE 3 in RRC-INACTIVE state performs cell reselection or selection to a cell that does not broadcast slice group identity information corresponding to any S-NSSAI present in the allowed NSSAI, UE 3 changes state to RRC IDLE mode (or RRC IDLE state). When UE 3 receives a request to establish an N1 signaling connection, UE 3 initiates an RRC connection setup procedure. The RRC connection setup procedure may be referred to as an RRC connection establishment procedure.

[0100] In some examples, in step 5, if UE 3 in the RRC-INACTIVE state performs cell reselection or selection to a cell that does not broadcast slice group identification information corresponding to any S-NSSAI present in its authorized NSSAI, UE 3 initiates a resume procedure (e.g., a resume procedure for an RRC connection) upon receiving a trigger to start signaling or user data communication, and sends an RRC Resume Request message. The resume procedure may be referred to as a resume procedure for an RRC connection. If NG-RAN 5 determines that the cell does not support any S-NSSAI present in UE 3's authorized NSSAI, upon receiving the RRC Resume Request message, NG-RAN 5 releases the DRB. NG-RAN 5 sends an RRC Setup message to UE 3 to establish an SRB. NG-RAN 5 may send an RRC Setup message to UE 3 to establish an SRB after the DRB release. NG-RAN 5 initiates a DRB release procedure related to the N2 interface. After initiating the DRB release procedure, the NG-RAN 5 may initiate a DRB release procedure related to the N2 interface.

[0101] <Modification 4 of the first example of the first aspect> After step 5, if the AMF 7001 wants to start paging for the UE 3 associated with the S-NSSAI and if the AMF 7001 wants to start signaling related to the S-NSSAI, the AMF 7001 includes the S-NSSAI or the network slice group identity associated with the S-NSSAI in the paging message. The S-NSSAI may refer to the S-NSSAI in the Authorized NSSAI, the Configured NSSAI, or the Requested NSSAI, or may be determined based on any other policy. When the NG-RAN 5 receives the paging message, the NG-RAN 5 sends a paging message to the UE 3 including the network slice group identity corresponding to the S-NSSAI together with the UE identity. The paging message may include the UE identity. The UE identity may be represented as the identity of the UE 3. The S-NSSAI may be received from the AMF 7001, or the NG-RAN 5 maps the S-NSSAI to the network slice group identity. For example, the NG-RAN 5 may map the S-NSSAI to a network slice group identity based on the correspondence between the S-NSSAI and the slice group identity. For example, the correspondence between the S-NSSAI and the slice group identity may be expressed as "GP ID1={S-NSSAI1}" for the same UE 3 as in step 1b or step 2b. When the UE 3 receives the paging message, the UE 3 matches the network slice group identity to the S-NSSAI and initiates a NAS procedure associated with the S-NSSAI corresponding to the network slice group identity. The NAS procedure may be expressed as a service request procedure.

[0102] <Second Example of First Aspect> The present disclosure discloses a method in which an NG-RAN allocates a network slice group identity range to each PLMN that shares the NG-RAN. Each PLMN allocates a network slice group identity from the network slice group identity range allocated by the NG-RAN to an S-NSSAI supported by the AMF. The AMF configures the S-NSSAI and the corresponding network slice group identity as defined in the first example of the first aspect. A cell connected to the NG-RAN broadcasts a network slice group identity (or network slice group identities) corresponding to each PLMN to which the NG-RAN is connected.

[0103] The detailed process of the second example of the first aspect is defined as follows:

[0104] Step 0. NG-RAN 5 is shared by PLMN1 and PLMN2, and NG-RAN 5 is connected to AMF 7001 of PLMN1 and AMF 7002 of PLMN2. AMF 7001 may be included in Core network (CN) 1. AMF 7002 may be included in CN2.

[0105] Step 1a. NG-RAN5 allocates a network slice group identity range to each PLMN sharing NG-RAN5. NG-RAN5 may allocate the network slice group identity range to PLMN1. NG-RAN5 sends an existing NGAP message or a new NGAP message to AMF7001 of PLMN1 indicating the support range of the network slice group identity for PLMN1. The NGAP message may be represented as an NGAP-SLICE GROUP ID ALLOCATION message. For example, the NGAP-SLICE GROUP ID ALLOCATION message may include an information element for GP ID range 1 to 4. "GP ID range 1 to 4" may mean that the support range of the network slice group identity is 1 to 4. The network slice group identity may be represented as a GP ID. The support range of the network slice group identity may be referred to as the network slice group identity range in this disclosure.

[0106] Step 1b. The AMF 7001 associates a network slice group identity from the network slice group identity range with the S-NSSAI and sends an existing NGAP message or a new NGAP message to the NG-RAN 5 indicating the association between the S-NSSAI and the network slice group identity. The association of the network slice group identity to the S-NSSAI may be expressed as an assignment of the network slice group identity to the S-NSSAI. The PLMN 1 may assign a network slice group identity from the network slice group identity range assigned by the NG-RAN 5 to the S-NSSAI supported by the AMF 7001. The AMF 7001 configures the S-NSSAI and the corresponding network slice group identity as defined in the first example of the first aspect. The NGAP message may be expressed as an NGAP-SLICE GROUP ID CONFIGURATION message. The NGAP-SLICE GROUP ID CONFIGURATION message may include the information elements PLMN ID1, {GP ID1, S-NSSAI1}, and {GP ID2, (S-NSSAI2, S-NSSAI3)}. For example, if AMF7001 supports network slice 1 indicated by S-NSSAI1, network slice 2 indicated by S-NSSAI2, and network slice 3 indicated by S-NSSAI3, AMF7001 groups the network slices, for example, into a first group including S-NSSAI1 and a second group including S-NSSAI2 and S-NSSAI3. Based on the support range of network slice group identification information set to 1 to 4, AMF7001 associates GP ID1 with the first group including S-NSSAI1 and associates GP ID2 with the second group including S-NSSAI2 and 3. AMF7001 sends an NGAP-SLICE GROUP ID CONFIGURATION message to NG-RAN5, which includes PLMN ID1 and information indicating the association between S-NSSAI and network slice group identity information.PLMN ID1 may be expressed as the PLMN ID of AMF 7001. "{GP ID1, S-NSSAI1}" and "{GP ID2, (S-NSSAI2, S-NSSAI3)}" may mean that S-NSSAI1, 2, and 3 are grouped into a first group including S-NSSAI1 and a second group including S-NSSAI2 and 3, and GP ID1 is associated with the first group and GP ID2 is associated with the second group. AMF 7001 may send an NGAP-SLICE GROUP ID CONFIGURATION message to NG-RAN 5 that includes PLMN ID1 and information indicating that the first group including S-NSSAI1 is associated with GP ID1 and the second group including S-NSSAI2 and 3 is associated with GP ID2.

[0107] Step 2a. NG-RAN5 allocates a network slice group identity range to each PLMN sharing NG-RAN5. NG-RAN5 may allocate the network slice group identity range to PLMN2. NG-RAN5 sends an existing NGAP message or a new NGAP message to AMF7002 of PLMN2 indicating the support range of the network slice group identity for PLMN2. The NGAP message may be expressed as an NGAP-SLICE GROUP ID ALLOCATION message. For example, the NGAP-SLICE GROUP ID ALLOCATION message may include an information element for GP ID range 5 to 6. "GP ID range 5 to 6" may mean that the support range of the network slice group identity is 5 to 6. The network slice group identity may be expressed as a GP ID.

[0108] Step 2b. The AMF 7002 associates a network slice group identity from the network slice group identity range with the S-NSSAI and sends an existing NGAP message or a new NGAP message to the NG-RAN 5 indicating the association between the S-NSSAI and the network slice group identity. The association of the network slice group identity to the S-NSSAI may be expressed as an assignment of the network slice group identity to the S-NSSAI. The PLMN 2 may assign a network slice group identity from the network slice group identity range assigned by the NG-RAN 5 to the S-NSSAI supported by the AMF 7002. The AMF 7002 configures the S-NSSAI and the corresponding network slice group identity as defined in the first example of the first aspect. The NGAP message may be expressed as an NGAP-SLICE GROUP ID CONFIGURATION message. The NGAP-SLICE GROUP ID CONFIGURATION message may include the information elements PLMN ID2 and {GP ID5, S-NSSAI1}. For example, if AMF7002 supports network slice 1 indicated by S-NSSAI1, AMF7002 associates GP ID5 with S-NSSAI1 based on the supported range of network slice group identity set to 5 to 6. AMF7002 sends an NGAP-SLICE GROUP ID CONFIGURATION message to NG-RAN5, including PLMN ID2 and information indicating the association between S-NSSAI and the network slice group identity. PLMN ID2 may be expressed as the PLMN ID of AMF7002. "{GP ID5, S-NSSAI1}" may mean that GP ID5 is associated with S-NSSAI1. AMF7002 may send an NGAP-SLICE GROUP ID CONFIGURATION message to NG-RAN5, including PLMN ID2 and information indicating that S-NSSAI1 is associated with GP ID5.

[0109] Step 3. A cell connected to NG-RAN5 broadcasts a list of network slice group identities supported by the cell via an existing SIB or a new SIB. The following format is an example of a SIB: The cell broadcasts the supported network slice group identity (or supported network slice group identities). Some network slice group identities may be valid and applicable for one associated PLMN. A cell connected to NG-RAN5 may broadcast a network slice group identity (or network slice group identities) corresponding to each PLMN to which NG-RAN5 is connected.

[0110] SIB X (GP ID1, GP ID5)

[0111] For example, a gNB, base station, (R)AN node, or NG-RAN node broadcasts a SIB or SIB message in a cell that includes a list of network slice group identities. The list of network slice group identities may include GP ID1 and GP ID5. "SIB X (GP ID1, GP ID5)" may mean that the SIB or SIB message includes GP ID1 and GP ID5.

[0112] Step 4. UE3 registers with AMF7001 of PLMN1, and during the registration procedure, AMF7001 sends a list of S-NSSAIs and associated network slice group identities to UE3 in an existing NAS message or a new NAS message. The NAS message may be expressed as a registration accept message or a UE configuration update message. AMF7001 may also send the authorized NSSAIs and configured NSSAIs to UE3 in the NAS message during the registration procedure. AMF7001 may send a list of S-NSSAIs and associated network slice group identities to UE3 for all S-NSSAIs in the configured NSSAIs. For example, UE3 and AMF7001 perform step 4 in the first example of the first aspect.

[0113] Step 5. The UE 3 performs the cell selection or cell reselection procedure and subsequent NAS procedure as defined in the first example of the first aspect, e.g., the UE 3 performs steps 5, 6a to 6c in the first example of the first aspect.

[0114] <Modification 1 of the second example of the first aspect> In some examples, the messages in step 1a and step 2a may be an NG SETUP REQUEST message, a RAN CONFIGURATION UPDATE message, or an AMF CONFIGURATION UPDATE ACKNOWLEDGE message as described in Non-Patent Document 3.

[0115] <Modification 2 of the second example of the first aspect> In some examples, the messages in step 1b and step 2b may be an NG SETUP RESPONSE message, a RAN CONFIGURATION UPDATE ACKNOWLEDGE message, or an AMF CONFIGURATION UPDATE message as described in Non-Patent Document 3.

[0116] <Second aspect> Non-Patent Document 6 discloses Multi-Radio Dual Connectivity. Multi-Radio Dual Connectivity (MR-DC) is a generalization of the intra-E-UTRA Dual Connectivity (DC) described in Non-Patent Document 5, in which multiple receive / transmit capable UEs can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing NR access and the other providing either E-UTRA or NR access. One node functions as a Master Node (MN) and the other node functions as a Secondary Node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to a core network.

[0117] The system design disclosed in Non-Patent Document 2 does not appear to function properly in a multi-radio dual connectivity environment. According to Non-Patent Document 2, the absolute priority of each frequency is provided to the UE by the RAN as part of the slice info. On the other hand, Non-Patent Document 6 discloses that the SN may use a frequency band different from that used by the MN. The system design disclosed in Non-Patent Document 2 does not appear to function properly in a multi-radio dual connectivity environment. It is unclear what the slice info and the absolute priority of each frequency mean for a cell establishing multi-radio dual connectivity. In a multi-radio dual connectivity environment, there are multiple frequencies available for the UE. The slice info and the absolute priority of each frequency may not be useful to the UE for cell selection and cell reselection in a multi-radio dual connectivity environment. For cell selection and cell reselection, the frequencies used by the SN need to be taken into account.

[0118] The present disclosure discloses that a mechanism that enables cell selection and cell reselection based on network slice priority will function in 5GS where multi-radio dual connectivity is built.

[0119] When multi-radio dual connectivity is established, the MN broadcasts system information taking the SN into consideration.

[0120] In order to make the UE aware of the frequency bands supported by the SN in a multi-radio dual connectivity configuration, there are several ways to broadcast the frequency bands supported by the SN through the system information.

[0121] <First example of the second aspect> This disclosure discloses a mechanism for how an MN acquires a frequency band supported by an SN. Figure 5 shows the procedure.

[0122] The detailed process of the first example of the second embodiment is described below.

[0123] Step 1. During the Xn setup procedure or the NG-RAN node configuration procedure, the MN 501 receives the served cell information NR or the served cell information E-UTRA in the XN SETUP REQUEST message, the XN SETUP RESPONSE message, the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, or any XNAP message, and stores the served cell information NR or the served cell information E-UTRA as SN-related configuration data in the MN 501.

[0124] This procedure can be performed in the MN 501 for all connected SNs 502.

[0125] Step 2. At least one of the served cell information NR and the served cell information E-UTRA includes frequency band information (or information related to frequency bands). The frequency band information may include frequency bands supported by the SN 502. All frequency band information received from the connected SN 502 is broadcast by the MN 501 to the UE 3 through a Broadcast Control Channel (BCCH). For example, the MN 501 broadcasts system information including frequency band information received from the SN 502 connected to the MN 501 to the UE 3. The frequency information may be included in the slice info or may be included in the system information independent of the slice info.

[0126] There are several ways to broadcast frequency band information of connected SNs 502. This first example may be applicable to the following examples or variations thereof disclosing system information structures over BCCH.

[0127] <Modification 1 of the first example of the second aspect> In addition to the frequency band information of the connected SN 502, the MN 501 stores Radio Access Technology (RAT) information associated with the frequency band in step 1. For example, the MN 501 receives the RAT information during the Xn setup procedure or the NG-RAN node configuration procedure. In step 2, the MN 501 broadcasts both the frequency band information and the RAT information supported by the connected SN 502. The RAT information may indicate the RAT type. The RAT type may be expressed as E-UTRA, NR, etc.

[0128] <Second Example of the Second Aspect> The present disclosure discloses a slice info structure for cell selection and cell reselection based on network slice priority when multi-radio dual connectivity is established.

[0129] This disclosure discloses a structure of slice info system information that includes a list of SN bands along with a list of supported network slice groups and group priorities. Figure 6 shows this structure.

[0130] The detailed process of the second example of the second embodiment is described below.

[0131] Step 1. The MN 501 broadcasts the following information as system information for cell selection and cell reselection. In addition, the following information may also be provided to the UE 3 exclusively by an RRC release message or an existing RRC message. Step 1 in FIG. 6 may be performed in step 2 in FIG. 5. The information included in the system information may be represented as cell selection and reselection information. The UE 3 may receive the system information from at least one of a serving cell and a neighboring cell. For example, the UE 3 may receive the system information from at least one of a serving MN (e.g., the MN 501 that controls the serving cell) and a neighboring MN (e.g., the MN 501 that controls the neighboring cell).

[0132] - Group ID list: A list of group IDs supported by MN501. As a variant, the group ID list may include group IDs supported by MN501 and associated SN502. The group ID may be referred to as network slice group identification information in this disclosure. The group ID may indicate identification information indicating a network slice group including an S-NSSAI or a network slice in this disclosure. For example, priorities may be configured for group IDs in the group ID list. For example, group ID1 has the highest priority, group ID3 has the lowest priority, and group ID2 has an intermediate priority between group ID1 and group ID3.

[0133] Frequency band priority: The frequency band priority indicates the priority order of the frequency band. The frequency band may be represented as FB. For example, the frequency band priority may indicate the priority order of the frequency band of the MN 501. For example, the frequency band priority indicates that FB1 has the highest priority, FB3 has the lowest priority, and FB2 has an intermediate priority between FB1 and FB3. The frequency band priority may be configured for each group ID in the group ID list.

[0134] SN Band List: The SN band list indicates a list of frequency bands configured as an SN in multi-radio dual connectivity operation. The SN band list may indicate a list of frequency bands configured as an SN in multi-radio dual connectivity operation. For example, the MN 501 may obtain the SN band list from the SN 502. For example, the MN 501 may obtain the SN band list from the SN 502 based on the process in step 1 of FIG. 5.

[0135] The SN band list can be configured as the following system information:

[0136] -Band list MRDC: A list of NR bands that can be configured as SNs in multi-radio dual connectivity operation that serves the forwarding of upper layer indications to upper layers.

[0137] Nr-Bandlist: This field indicates a list of bands and is encoded as a bitmap, where bit N is set to '1' if the current serving cell supports multi-radio dual connectivity operation on the Nth NR band in the band list MRDC (bandListMRDC). Bits without a corresponding band in the band list MRDC (bandListMRDC) are set to 0, and bit 1 of the bitmap is the first bit of the bit string.

[0138] Eutra-Bandlist: This field indicates a list of bands and is encoded as a bitmap, where bit N is set to '1' if the current serving cell supports Multi-Radio Dual Connectivity operation on the Nth E-UTRA band in the band list MRDC (bandListMRDC). Bits without a corresponding band in the band list MRDC (bandListMRDC) are set to 0, and bit 1 of the bitmap is the first bit of the bit string.

[0139] Once the UE 3 receives this system information, the UE 3 performs the following steps in Figure 7 to determine whether cell selection or cell reselection is necessary and to which cell the UE 3 should move. As will be described below, when the UE 3 makes a cell selection or cell reselection decision, the UE 3 may take into account the strength of the signal from the cell.

[0140] Step 1: The UE 3 determines the priority of the group ID based on the network slice priority in the NAS part of the UE 3. The UE 3 may determine the priority of the group ID based on the following steps 1-1 to 1-4.

[0141] For example, in step 1-1, UE3 has or configures network slice priorities through its local configuration. For example, UE3 has or configures network slice priorities indicating that S-NSSAI1 has a higher priority than S-NSSAI2. In addition to the local configuration of UE3, UE3 may also determine network slice priorities based on the state of PDU sessions associated with the network slice. For example, a network slice with an associated active PDU session may have the highest priority, while a network slice that is established but has no active PDU session may have the second highest priority. In addition to the local configuration of UE3, UE3 may also determine network slice priorities based on the state of applications in UE3. For example, a network slice with an associated active application in UE3 may have the highest priority.

[0142] In step 1-2, UE3 receives information indicating which network slices are included in the group by the NAS message. For example, UE3 receives information indicating that Group 1 identified by Group ID1 (or GP ID1) includes S-NSSAI1 and Group 2 identified by Group ID2 (or GP ID2) includes S-NSSAI2.

[0143] In steps 1-3, UE3 receives system information including group IDs as mentioned in step 1 of Figure 6. For example, UE3 receives system information including group ID1 and group ID2, and information indicating that group ID1 has a higher priority than group ID2.

[0144] In step 1-4, UE3 determines the priority of group IDs based on the information in steps 1-1, 1-2, and 1-3. For example, UE3 determines that S-NSSAI1 is included in group 1 identified by group ID 1 based on the information in steps 1-1 and 1-2. For example, UE3 determines that group ID 1 corresponding to S-NSSAI1 has a higher priority than group ID 2 based on the information in step 1-3.

[0145] Step 2: The UE 3 determines a frequency band or a combination of frequency bands to be used when the multi-radio dual connectivity operation is activated. The frequency band may be referred to as a best frequency band, and the combination of frequency bands may be referred to as a best combination of frequency bands.

[0146] For example, the UE 3 determines a frequency band or a combination of frequency bands based on the order of frequency band priorities broadcast by a RAN node in one of the system information messages related to cell selection and reselection. The RAN node may include the MN 501 that provides a serving cell and, if available, neighboring cells. The RAN node may also include another RAN node or other RAN nodes that provide neighboring cells. For example, if the frequency band priorities indicate that FB1 has the highest priority, the UE 3 determines that the cell of FB1 is the best target cell (or best frequency band) for cell selection or reselection.

[0147] For example, if the frequency band priorities indicate that FB1 has the highest priority, FB3 has the lowest priority, and FB2 has an intermediate priority between FB1 and FB3, UE3 determines that FB1 and FB2 are the best combination of frequency bands.

[0148] For example, if UE3 determines in step 1 that group ID1 corresponding to S-NSSAI1 has a higher priority than group ID2, and the frequency band priority for group 1 indicates that FB1 has the highest priority, the UE determines FB1 as the best frequency band.

[0149] For example, if UE3 determines that group ID1 corresponding to S-NSSAI1 has a higher priority than group ID2, the frequency band priorities for group ID1 indicate that FB1 has the highest priority, and the frequency band priorities for group ID2 indicate that FB1 has the highest priority, FB3 has the lowest priority, and FB2 has an intermediate priority between FB1 and FB3, UE3 may determine FB1 for group ID1 and FB2 for group ID2 as the best combination of frequency bands. In this case, UE3 determines that FB1 is used for group ID1, and therefore, UE3 may determine that FB1 is not available for group ID2, and may determine FB2, which has the second priority in the frequency band priorities for group ID2, for group ID2.

[0150] In another example, UE 3 may determine the best frequency band or the best combination of frequency bands based on the local configuration of UE 3. For example, if UE 3 determines in step 1 that group ID 1 corresponding to S-NSSAI 1 has a higher priority than group ID 2, UE 3 determines, based on the local configuration of UE 3, that FB 1 is preferred for group ID 1 corresponding to S-NSSAI 1 and FB 2 is preferred for group ID 2 corresponding to S-NSSAI 2.

[0151] Step 3: Based on the information in steps 1 and 2, UE 3 may determine whether cell selection or cell reselection is necessary and to which cell UE 3 should move. UE 3 may determine whether cell selection or cell reselection is necessary and to which cell UE 3 should move by comparing the information in steps 1 and 2. Based on the determination in step 2, UE 3 may choose a cell to select or reselect based on system information received from the cell and cells available to UE 3 (e.g., serving cell and neighboring cell) and UE radio capabilities. The received system information may be referred to as cell selection and reselection information. The cells may be referred to as serving cell and neighboring cell. For example, if UE 3 determines FB1 as the best frequency band, UE 3 may choose a cell that supports or operates on FB1. The cells may be referred to as serving cell or neighboring cell. For example, if UE3 receives an SN band list including FB1, FB2, and FB3, and UE3 determines FB1 for group ID1 and FB2 for group ID2 as the best combination of frequency bands, UE3 may select a first cell controlled by MN 501 that supports or operates on FB1, and a second cell controlled by an SN corresponding to MN 501 that supports or operates on FB2. For example, if the cell selected by UE3 is a serving cell, UE3 may not perform cell selection or cell reselection. The fact that the cell selected by UE3 is the serving cell may mean that MN 501, which controls the serving cell, transmits system information including a frequency band priority including FB1 and an SN band list including FB2. UE3 that does not perform cell selection or cell reselection may be represented as a UE that remains in the serving cell. If the cell selected by UE3 is the serving cell, UE3 may determine or decide that cell selection or cell reselection is not necessary and UE3 will not move to the cell.

[0152] If UE3 is in the cell that continues with the best priority network slice and the best priority FB based on the cell selection and reselection information broadcast in the system information, and the signal strength of the current cell is still above the threshold required for cell reselection, UE3 does not need to perform cell reselection, i.e., UE3 stays in the current cell.

[0153] Step 4: Based on the determination in step 3, if cell selection or cell reselection is necessary (e.g., if the serving cell becomes weaker and one or more better suited cells exist according to steps 1 to 3), UE 3 may perform cell selection or cell reselection. Alternatively, UE 3 may trigger cell selection or cell reselection immediately if a more suitable cell becomes available according to steps 1 to 3. For example, UE 3 performs cell selection or cell reselection to the cell selected in step 3. For example, if the cell selected by UE 3 in step 3 is a neighboring cell (e.g., if the node controlling the neighboring cell or a neighboring MN transmits system information including a frequency band priority including FB1 and an SN band list including FB2), UE 3 may perform cell selection or cell reselection to the neighboring cell.

[0154] If cell selection or cell reselection may be required taking into account the RAT type, the following information may be broadcast: In addition, the following information may also be provided to the UE 3 exclusively by an RRC release message or an existing RRC message:

[0155] Frequency band priority with RAT type: The combination of frequency band and RAT type priority indicates the priority order of the frequency band / RAT type combination. For example, by using frequency band priority with RAT type, UE3 can select at least one of the frequency band and cell corresponding to the RAT type.

[0156] SN Band List: The SN Band List indicates a list of combinations of frequency bands and RAT types configured as SNs in multi-radio dual connectivity operation. For example, by using this list, the UE 3 can select at least one of a frequency band, a cell, and an SN 502 corresponding to the RAT type.

[0157] <Modification 1 of the second example of the second aspect> This disclosure discloses a structure of slice info system information that includes a list of SN bands along with a list of supported groups and group priorities. Figure 8 shows this structure.

[0158] The detailed process of the first variant of the second example is described below.

[0159] Step 1. The MN 501 broadcasts the following information as system information for cell selection and cell reselection. In addition, the following information may also be provided to the UE 3 exclusively by an RRC release message or an existing RRC message. Step 1 in Fig. 8 may be performed in step 2 in Fig. 5. The UE 3 may receive system information from at least one of a serving cell and a neighboring cell. For example, the UE 3 may receive system information from at least one of a serving MN (e.g., the MN 501 that controls the serving cell) and a neighboring MN (e.g., the MN 501 that controls the neighboring cell).

[0160] Group ID list: A list of group IDs supported by the MN 501. As a variant, the group ID list may include group IDs supported by the MN 501 and all associated SNs. For example, priorities may be configured for the group IDs in the group ID list. For example, group ID 1 has the highest priority, group ID 3 has the lowest priority, and group ID 2 has an intermediate priority between group ID 1 and group ID 3.

[0161] Frequency band priority: The frequency band priority indicates the priority order of frequency bands. Each frequency band information may be configured with the frequency band of the MN 501 and the frequency band of the SN for a cell under multi-radio dual connectivity operation. "FB1, FB1+FB3(SN), FB2+FB3(SN) in priority order (FB1, FB1+FB3(SN), FB2+FB3(SN) in priority order)" may mean that FB1 has the highest priority, the frequency band combination of FB2 of the MN 501 and FB3 of the SN has the lowest priority, and the frequency band combination of FB1 of the MN 501 and FB3 of the SN has an intermediate priority between the highest and lowest priorities. For example, "FB1" may mean that FB1 can be used when multi-radio dual connectivity operation is not used. "FB1+FB3(SN)" may mean that the combination of FB1 of the MN 501 and FB3 of the SN can be used when multi-radio dual connectivity operation is used. "FB2+FB3(SN)" may mean that when multi-radio dual connectivity operation is used, a combination of FB2 of MN501 and FB3 of SN may be used. Frequency band priority may be configured for each group ID in the group ID list. For example, MN501 may obtain the frequency band of the SN from SN502 based on the process in step 1 of FIG. 5. MN501 may construct each frequency band information based on the frequency band of MN501 and the frequency band of the SN. For example, if MN501 supports FB1 and FB2 and SN supports FB3, MN501 configures frequency band information including FB1, a combination of FB1 and FB3, and a combination of FB2 and FB3.

[0162] The UE behavior when UE3 receives this system information is the same as the UE behavior described in the second example of the second aspect. For example, UE3 determines the combination of FB1 of MN501 and FB3 of SN as the best combination of frequency bands based on the received frequency band priority or the UE3's local configuration. UE3 may select a cell operating on FB1 and FB3 for multi-radio dual connectivity operation. For example, if UE3 determines the combination of FB1 of MN501 and FB3 of SN as the best combination of frequency bands, UE3 may select a cell where system information including a frequency band priority including the combination of FB1 of MN501 and FB3 of SN is broadcast (e.g., "FB1+FB3(SN)" is broadcast). If the cell selected by UE3 is a serving cell, UE3 may not perform cell selection or cell reselection (i.e., UE3 stays in the serving cell). If the cell selected by UE3 is a neighboring cell, UE3 may perform cell selection or cell reselection for the neighboring cell.

[0163] If cell selection or cell reselection may be required taking into account the RAT type, the following information may be broadcast: In addition, the following information may also be provided to the UE exclusively by an RRC release message or an existing RRC message:

[0164] Frequency band priority with RAT type: A combination of frequency band and RAT type priority indicates the priority order of frequency band / RAT type combinations. For a standalone cell, each entry constitutes a combination of frequency band and RAT type information. For a cell under multi-radio dual connectivity operation, each entry constitutes a frequency band / RAT type combination of an MN and a frequency band / RAT type combination of an SN. For example, by using the frequency band priority with the RAT type, the UE 3 can select at least one of a frequency band and a cell corresponding to the RAT type. For example, by using the frequency band priority with the RAT type, the UE 3 can select at least one of a frequency band, a cell, an MN, and an SN corresponding to the RAT type.

[0165] <Modification 2 of the second example of the second aspect> This disclosure discloses the structure of slice info system information for multi-radio dual connectivity operation. Figure 9 shows the system information provided to the UE.

[0166] The detailed process of the second variant of the second example is described below.

[0167] Step 1. The MN 501 broadcasts the following information as system information for cell selection and cell reselection. In addition, the following information may also be provided to the UEs exclusively by an RRC release message or an existing RRC message. For example, the MN 501 may broadcast its own identification information. The UE 3 may receive system information from at least one of a serving cell and a neighboring cell. For example, the UE 3 may receive system information from at least one of a serving MN (e.g., the MN 501 that controls the serving cell) and a neighboring MN (e.g., the MN 501 that controls the neighboring cell).

[0168] Group ID list: A list of group IDs supported by the MN 501. As a variant, the group ID list may be configured with group IDs supported by the MN 501 and all associated SNs. For example, priorities may be configured for the group IDs in the group ID list. For example, group ID 1 has the highest priority, group ID 3 has the lowest priority, and group ID 2 has an intermediate priority between group ID 1 and group ID 3.

[0169] Frequency Band Priority: The frequency band priority indicates the priority order of the frequency bands. Each frequency band information can be configured with the frequency band of the MN for a cell under multi-radio dual connectivity operation. For example, the frequency band priority indicates that FB1 has the highest priority, FB3 has the lowest priority, and FB2 has an intermediate priority between FB1 and FB3.

[0170] Step 2. The SN 502 broadcasts the following information as system information for cell selection or cell reselection based on network slice priority. In addition, the following information may also be provided to the UE 3 exclusively by an RRC release message or an existing RRC message. For example, the UE 3 may receive system information from at least one of an SN corresponding to a serving MN (e.g., an SN 502 corresponding to an MN 501 that controls a serving cell in multi-radio dual connectivity operation) and an SN corresponding to a neighboring MN (e.g., an SN 502 corresponding to an MN 501 that controls a neighboring cell in multi-radio dual connectivity operation).

[0171] MN list: a list of associated MNs. For example, the MN list includes at least one identification information of the associated MNs.

[0172] Group ID List: A list of group IDs supported by the SN 502. For example, priorities can be configured for the group IDs in the group ID list. For example, group ID 1 has the highest priority, group ID 3 has the lowest priority, and group ID 2 has an intermediate priority between group ID 1 and group ID 3.

[0173] The UE behavior when the UE 3 receives this system information is the same as the UE behavior described in the second example of the second aspect. Note that the UE 3 scans the system information broadcast by the MN 501 and the system information broadcast by the SN 502 in steps 1 and 2. The association of the MN 501 and the SN 502 can be known by the UE 3 from the MN list information broadcast by the SN 502. This association helps the UE 3 understand the frequency band combination between the MN 501 and the SN 502. For example, if the UE 3 receives identification information of the MN 501 from the MN 501 and receives an MN list including the identification information of the MN 501 from the SN 502, the UE 3 can recognize or understand the association of the MN 501 and the SN 502. For example, if the UE 3 recognizes or understands the association of the MN 501 and the SN 502, the UE 3 can recognize or understand that multi-radio dual connectivity operation is available by using the MN 501 and the SN 502. For example, if UE3 recognizes or understands the association of MN501 and SN502, UE3 may recognize or understand that the frequency band priority received from MN501 is also applicable to SN502. For example, if UE3 determines a priority for group ID1 and a priority for group ID4, UE3 may determine the best combination of frequency bands for multi-radio dual connectivity operation (e.g., UE3 determines a combination of FB1 for group ID1 and FB2 for group ID4) and select a cell operating on FB1 and FB2 for multi-radio dual connectivity operation. For example, if UE3 determines a combination of FB1 and FB2 as the best combination of frequency bands, UE3 may select a first cell controlled by MN501 and a second cell controlled by SN502 corresponding to MN501, in which system information including a frequency band priority including FB1 is broadcast. In this case, SN502 supports or operates on FB2. If the cell selected by UE3 (eg, the first cell) is the serving cell, UE3 may not perform cell selection or cell reselection (ie, UE3 remains in the serving cell).If the cell selected by UE3 (e.g., the first cell) is a neighboring cell, UE3 may perform cell selection or cell reselection for the neighboring cell. After selecting or reselecting the first cell, UE3 may add a second cell as a secondary cell. After selecting or reselecting the first cell, UE3 may add an SN that controls the second cell as a secondary node.

[0174] If cell selection or cell reselection may be required taking into account the RAT type, the following information may be broadcast: In addition, the following information may also be provided to the UE 3 exclusively by an RRC release message or an existing RRC message:

[0175] Frequency band priority with RAT type: A combination of frequency band and RAT type priority indicates the priority order of frequency band / RAT type combinations. For a standalone cell, each entry constitutes a combination of frequency band and RAT type information. For a cell under multi-radio dual connectivity operation, each entry constitutes a frequency band / RAT type combination of an MN and a frequency band / RAT type combination of an SN. For example, by using the frequency band priority with the RAT type, the UE 3 can select at least one of a frequency band and a cell corresponding to the RAT type. For example, by using the frequency band priority with the RAT type, the UE 3 can select at least one of a frequency band, a cell, an MN, and an SN corresponding to the RAT type.

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

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

[0178] 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).

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

[0180] 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."

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

[0182] 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).

[0183] 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).

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

[0185] 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).

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

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

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

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

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

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

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

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

[0194] 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)

[0195] - 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)

[0196] 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

[0210] <User equipment (UE)> FIG. 11 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.

[0211] 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).

[0212] 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).

[0213] 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.).

[0214] 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.).

[0215] 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.).

[0216] 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.).

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

[0218] 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)).

[0219] 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)."

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

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

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

[0223] 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).

[0224] 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).

[0225] <(R)AN node> FIG. 12 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.

[0226] 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 with the core network 7 for a specific UE 3, particularly 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).

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

[0228] (R)AN node 5 may support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The Master Node (MN) 501 and the Secondary Node (SN) 502 may have the same components as (R)AN node 5.

[0229] <System Overview of (R)AN Node 5 Based on the O-RAN Architecture> FIG. 13 illustrates schematically an (R)AN node 5 based on an O-RAN architecture to which (R)AN node 5 aspects are applicable.

[0230] 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 combining / combining unit, and the DU 61 may be combined with the CU 62 as another combining / combining unit. Any functionality described for a unit (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the combining / combining 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).

[0231] 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).

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

[0233] <Radio Unit (RU)> FIG. 14 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.

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

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

[0236] 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).

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

[0238] <Distributed Unit (DU)> FIG. 15 is a block diagram illustrating the main components of an exemplary DU 61, e.g., the DU 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 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 in accordance with 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.

[0239] 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).

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

[0241] <Centralized Unit (CU)> FIG. 16 is a block diagram illustrating the main components of an exemplary CU 62, e.g., the CU 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 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.

[0242] 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).

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

[0244] <amf> 17 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).

[0245] The AMF 70 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). The AMF 7001 and AMF 7002 may have the same components as the AMF 70.

[0246] <udm> 18 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).

[0247] 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).

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

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

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

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

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

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

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

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

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

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

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

[0259] 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).

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

[0261] Appendix 1. Sending a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI); receiving a second message including the S-NSSAI associated with the PLMN ID and an identifier; transmitting the S-NSSAI associated with the identifier; A method for an Access and Mobility Management Function (AMF) device.

[0262] Appendix 2. receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI); sending a second message including the S-NSSAI associated with the PLMN ID and an identifier; transmitting a third message including the identifier associated with the PLMN ID; A method for a Next Generation-Radio Access Network (NG-RAN) node.

[0263] Appendix 3. receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier; receiving a second message including the identifier associated with the PLMN ID; performing cell selection or cell reselection after receiving the first message and the second message; A User Equipment (UE) method.

[0264] Appendix 4. receiving a first message including information indicating a range of identifiers; transmitting a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with said identifier; transmitting the S-NSSAI associated with the identifier; A method for an Access and Mobility Management Function (AMF) device.

[0265] Appendix 5. transmitting a first message including information indicating a range of identifiers; receiving a Public Land Mobile Network Identifier (PLMN ID) and a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the PLMN ID; transmitting a third message including the identifier associated with the PLMN ID; A method for a Next Generation-Radio Access Network (NG-RAN) node.

[0266] Appendix 6. Transmitting a group identifier (GP ID) that identifies a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating the priority of frequency bands, and information indicating the frequency bands used by a Secondary Node (SN); Master Node (MN) method.

[0267] Appendix 7. Transmitting a group identifier (GP ID) that identifies a group including Single Network Slice Selection Assistance Information (S-NSSAI) and information indicating the priority of a frequency band; The information indicating the priority of the frequency band includes a priority of a frequency band combination including a frequency band of an MN and a frequency band of a secondary node (SN), Master Node (MN) method.

[0268] Appendix 8. Receive a group identifier (GP ID) for identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a priority of a frequency band, and information indicating a frequency band used by a Secondary Node (SN); Performing cell selection or cell reselection based on the GP ID, the information indicating the priority of the frequency band, and the information indicating the frequency band used by the SN; A User Equipment (UE) method.

[0269] Appendix 9. Receive a first group identifier (GP ID) that identifies a group including first single network slice selection assistance information (S-NSSAI) and information indicating a priority of a frequency band; receiving a list of Master Nodes (MNs) and a second Group Identifier (GP ID) identifying a group including the second S-NSSAI; performing cell selection or cell reselection based on the first GP ID, the information indicating the priority of the frequency band, the list, and the second GP ID; A User Equipment (UE) method.

[0270] Appendix 10. means for transmitting a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI); means for receiving a second message including the S-NSSAI associated with the PLMN ID and an identifier; means for transmitting the S-NSSAI associated with the identifier; An Access and Mobility Management Function (AMF) device comprising:

[0271] Appendix 11. means for receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI); means for transmitting a second message including the S-NSSAI associated with the PLMN ID and an identifier; means for transmitting a third message including the identifier associated with the PLMN ID; A Next Generation-Radio Access Network (NG-RAN) node comprising:

[0272] Appendix 12. means for receiving a first message including a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI) associated with the identifier; means for receiving a second message including the identifier associated with the PLMN ID; means for performing cell selection or cell reselection after receiving the first message and the second message; A user equipment (UE) comprising:

[0273] Appendix 13. means for receiving a first message including information indicating a range of identifiers; means for transmitting a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI) associated with said identifier; means for transmitting the S-NSSAI associated with the identifier; An Access and Mobility Management Function (AMF) device comprising:

[0274] Appendix 14. means for transmitting a first message including information indicating a range of identifiers; means for receiving a Public Land Mobile Network Identifier (PLMN ID) and Single Network Slice Selection Assistance Information (S-NSSAI) associated with said identifier; means for transmitting a third message including the identifier associated with the PLMN ID; A Next Generation-Radio Access Network (NG-RAN) node comprising:

[0275] Appendix 15. A means for transmitting a group identifier (GP ID) for identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating the priority of frequency bands, and information indicating frequency bands used by a Secondary Node (SN). A master node (MN) includes:

[0276] Appendix 16. A means for transmitting a group identifier (GP ID) for identifying a group including single network slice selection assistance information (S-NSSAI) and information indicating a priority of a frequency band, The information indicating the priority of the frequency band includes a priority of a frequency band combination including a frequency band of an MN and a frequency band of a secondary node (SN), Master Node (MN).

[0277] Appendix 17. A means for receiving a group identifier (GP ID) for identifying a group including Single Network Slice Selection Assistance Information (S-NSSAI), information indicating a priority of a frequency band, and information indicating a frequency band used by a Secondary Node (SN); A means for performing cell selection or cell reselection based on the GP ID, the information indicating the priority of the frequency band, and the information indicating the frequency band used by the SN; A user equipment (UE) comprising:

[0278] Appendix 18. A means for receiving a first group identifier (GP ID) that identifies a group including first single network slice selection assistance information (S-NSSAI) and information indicating a priority of a frequency band; means for receiving a list of Master Nodes (MNs) and a second Group Identifier (GP ID) identifying a group including the second S-NSSAI; A means for performing cell selection or cell reselection based on the first GP ID, the information indicating the priority of the frequency band, the list, and the second GP ID; A user equipment (UE) comprising:

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

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

[0281] 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 361 Operating Systems 362 Communication Control Module 501 Masternode 502 Secondary Node 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 751 Transceiver Circuit 752 network interfaces 753 Controller 754 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 7541 Operating Systems 7542 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 75421 Transceiver Control Module< / udm> < / amf>

Claims

1. means for communicating with a Next Generation-Radio Access Network (NG-RAN) node; means for receiving a message from the NG-RAN node; The message includes a Public Land Mobile Network (PLMN) identifier and information about a network slice group for cell reselection; the information indicates at least one Single Network Slice Selection Assistance Information (S-NSSAI); The information is related to the PLMN identifier and is different from the Requested Network Slice Selection Assistance Information (Requested NSSAI). Access and Mobility Management Function (AMF).

2. The message is a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message. The AMF of claim 1.

3. means for transmitting said information to a user device; 3. The AMF according to claim 1 or 2.

4. The information is transmitted to the user device in a registration accept message. The AMF of claim 3.

5. means for communicating with an Access and Mobility Management Function (AMF); means for sending a message to the AMF; The message includes a Public Land Mobile Network (PLMN) identifier and information about a network slice group for cell reselection; the information indicates at least one Single Network Slice Selection Assistance Information (S-NSSAI); The information is related to the PLMN identifier and is different from the Requested Network Slice Selection Assistance Information (Requested NSSAI). Next Generation-Radio Access Network (NG-RAN) node.

6. The message is a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message. The NG-RAN node of claim 5.

7. communicating with a Next Generation-Radio Access Network (NG-RAN) node; receiving a message from the NG-RAN node; The message includes a Public Land Mobile Network (PLMN) identifier and information about a network slice group for cell reselection; the information indicates at least one Single Network Slice Selection Assistance Information (S-NSSAI); The information is related to the PLMN identifier and is different from the Requested Network Slice Selection Assistance Information (Requested NSSAI). A method for Access and Mobility Management Function (AMF).

8. Communicating with an Access and Mobility Management Function (AMF); Send a message to the AMF; The message includes a Public Land Mobile Network (PLMN) identifier and information about a network slice group for cell reselection; the information indicates at least one Single Network Slice Selection Assistance Information (S-NSSAI); The information is related to the PLMN identifier and is different from the Requested Network Slice Selection Assistance Information (Requested NSSAI). A method for a Next Generation-Radio Access Network (NG-RAN) node.

Images