CN116058006A - Efficient access for single operator network slicing - Google Patents

Abstract

An apparatus and system are described that enable single operator network slice access. The initial network slice information is contained in the new cell in the SIB. The UE transmits an on-demand SIB request for further SIB information related to a slice/service type (SST) via a RACH procedure when in rrc_connected mode and when in rrc_idle or INACTIVE mode. The network provides roaming guidance (SoR) information in a list for guiding the UE to PLMNs, depending on whether the UE is capable of accessing multiple PLMNs simultaneously. The single network slice selection assistance information (S-nsai) information including slice/service type (SST) and slice Specifier (SD) also includes an indication of the SD capable of skipping the S-nsai. The UE may register in different PLMNs using the same Radio Access Technology (RAT) or different RATs.

Description

Efficient access for single operator network slicing

Priority claim

The present application claims the benefit of priority from U.S. provisional patent application Ser. No.63/078,147, filed on 9/14/2020, and U.S. provisional patent application Ser. No.63/080,588, filed on 9/18/2020, each of which is incorporated herein by reference in its entirety.

Technical Field

Embodiments relate to fifth generation (5G) wireless communications. In particular, some embodiments relate to multi-network slice access and roaming steering based on network slices of multiple networks supported.

Background

The use and complexity of wireless systems, including fourth generation (4G) and fifth generation (5G) networks and the like, has increased due to the increase in the device types of User Equipment (UEs) that use network resources and the amount of data and bandwidth used by various applications (e.g., video streaming) operating on these UEs. As the number and diversity of communication devices has increased substantially, the corresponding network environments, including routers, switches, bridges, gateways, firewalls, and load balancers, have become more and more complex, particularly in the presence of Next Generation (NG) (or new air interface (NR)) systems. As expected, there are a number of problems with the advent of any new technology.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example and not by way of limitation, the various embodiments discussed in the present document.

Fig. 1A illustrates a network architecture according to some aspects.

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

Fig. 3 illustrates a Radio Access Network (RAN) node connecting to two network slices simultaneously, in accordance with some aspects.

Fig. 4 illustrates System Information (SI) provisioning in accordance with some aspects.

Fig. 5 illustrates a random access procedure in accordance with some aspects.

Fig. 6 illustrates a roaming UE with services on network slices available on different networks, in accordance with some aspects.

Fig. 7 illustrates a procedure for providing a list of preferred Public Land Mobile Network (PLMN)/access technology combinations, in accordance with some aspects.

Fig. 8 illustrates a process for providing a list of preferred PLMN/access technology combinations after registration, in accordance with some aspects.

Fig. 9 illustrates a process for providing a list of preferred PLMN/access technology combinations in accordance with some aspects.

Detailed Description

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of others. The embodiments set forth in the claims encompass all available equivalents of those claims.

Fig. 1A illustrates a network architecture according to some aspects. Network 140A includes 3GPP LTE/4G and NG network functions that may extend to 6G functions. Thus, although 5G will be mentioned, it should be understood that this will be able to extend to 6G structures, systems and functions. The network functions may be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, and/or as virtualized functions instantiated on a suitable platform (e.g., dedicated hardware or cloud infrastructure).

Network 140A is shown to include User Equipment (UE) 101 and UE 102. The UEs 101 and 102 are shown as smartphones (e.g., handheld touch screen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless phone, a drone, or any other computing device including a wired and/or wireless communication interface. The UEs 101 and 102 may be collectively referred to herein as UE 101, and the UE 101 may be configured to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any of the example radio communication techniques and/or standards. Any spectrum management scheme may be used including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., licensed Shared Access (LSA) in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and other frequencies, and Spectrum Access System (SAS) in 3.55-3.7GHz and other frequencies). Different single carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.), in particular 3GPP NR, may be used by allocating OFDM carrier data bit vectors to corresponding symbol resources.

In some aspects, either of the UEs 101 and 102 may include an internet of things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low power IoT applications that utilize short term UE connections. In some aspects, either of the UEs 101 and 102 may include Narrowband (NB) IoT UEs (e.g., such as enhanced NB-IoT (eNB-IoT) UEs and further enhanced (FeNB-IoT) UEs). IoT UEs may exchange data with MTC servers or devices via Public Land Mobile Network (PLMN), proximity services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks using technologies such as machine-to-machine (M2M) or machine-type communications (MTC). The M2M or MTC data exchange may be a machine initiated data exchange. The IoT network includes interconnected IoT UEs (which may include (within the internet infrastructure) uniquely identifiable embedded computing devices) with short-term connections. The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network. In some aspects, either of the UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

The UEs 101 and 102 may be configured to connect (e.g., communicatively couple) with a Radio Access Network (RAN) 110. RAN 110 may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN.

The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as implementing communicatively coupled air interfaces and may follow cellular communication protocols, such as global system for mobile communications (GSM) protocols, code Division Multiple Access (CDMA) network protocols, push-to-talk (PTT) protocols, PTT Over Cellular (POC) protocols, universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, 6G protocols, and so on.

In an aspect, the UEs 101 and 102 may also directly exchange communication data via the ProSe interface 105. ProSe interface 105 may alternatively be referred to as a Side Link (SL) interface, which includes one or more logical channels including, but not limited to, a physical side link control channel (PSCCH), a physical side link shared channel (PSSCH), a physical side link discovery channel (PSDCH), a physical side link broadcast channel (PSBCH), and a physical side link feedback channel (PSFCH).

UE 102 is shown configured to access an Access Point (AP) 106 via a connection 107. Connection 107 may comprise a local wireless connection, such as a connection conforming to any of the IEEE 802.11 protocols, according to which AP 106 may comprise wireless fidelity

And a router. In this example, the AP 106 is shown connected to the internet, rather than to the core network of the wireless system (described in further detail below).

RAN 110 may include one or more access nodes implementing connections 103 and 104. These Access Nodes (ANs) may be referred to as Base Stations (BS), nodebs, evolved nodebs (enbs), next generation nodebs (gnbs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., cell). In some aspects, communication nodes 111 and 112 may be transmission/reception points (TRP). In the case where the communication nodes 111 and 112 are nodebs (e.g., enbs or gnbs), one or more TRPs may function within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes for providing a macro cell (e.g., macro RAN node 111) and one or more RAN nodes for providing a femto cell or pico cell (e.g., a cell with smaller coverage area, smaller user capacity, or higher bandwidth than a macro cell) (e.g., low Power (LP) RAN node 112).

Either of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, either of RAN nodes 111 and 112 may implement various logic functions for RAN 110 including, but not limited to, radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, as well as mobility management. In an example, any of nodes 111 and/or 112 may be a gNB, an eNB, or another type of RAN node.

RAN 110 is shown communicatively coupled to a Core Network (CN) 120 via a Sl interface 113. In aspects, the CN 120 may be an Evolved Packet Core (EPC) network, a next generation packet core (NPC) network, or some other type of CN (e.g., as shown with reference to fig. 1B-1C). In this regard, the S1 interface 113 is divided into two parts: an S1-U interface 114 carrying traffic data between RAN nodes 111 and 112 and a serving gateway (S-GW) 122; and an S1-Mobility Management Entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and MME 121.

In this regard, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124.MME 121 may be similar in function to the control plane of a legacy serving General Packet Radio Service (GPRS) support node (SGSN). MME 121 may manage mobility aspects in the access such as gateway selection and tracking area list management. HSS 124 may include a database for network users (including subscription related information) to support the handling of communication sessions by network entities. The CN 120 may include one or several HSS 124 depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, the HSS 124 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like.

S-GW 122 may terminate S1 interface 113 towards RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 may be a local mobility anchor for inter-RAN node handover and may also provide anchoring for inter-3 GPP mobility. Other responsibilities of S-GW 122 may include lawful interception, charging, and some policy enforcement.

The P-GW123 may terminate the SGi interface towards the PDN. The P-GW123 may route data packets between the CN 120 and external networks, e.g., networks including an application server 184 (alternatively referred to as an Application Function (AF)), via an Internet Protocol (IP) interface 125. The P-GW123 may also communicate data to other external networks 131A (which may include the internet, IP multimedia Subsystem (IPs) networks, and other networks). In general, the application server 184 may be an element that provides applications (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.) that use IP bearer resources with the core network. In this regard, P-GW123 is shown to be communicatively coupled to application server 184 via IP interface 125. The application server 184 may also be configured to: one or more communication services (e.g., voice over internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 101 and 102 via CN 120 are supported.

The P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF associated with an internet protocol connectivity access network (IP-CAN) session of the UE in a Home Public Land Mobile Network (HPLMN). In a roaming scenario where traffic is off-home, there may be two PCRFs associated with the IP-CAN session of the UE: a home PCRF (H-PCRF) within the HPLMN and a visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). PCRF 126 may be communicatively coupled to application server 184 via P-GW 123.

In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network, including a 5G new air interface network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current implementations of IoT is the narrowband IoT (NB-IoT). Operations in the unlicensed spectrum may include dual-connection (DC) operations and independent LTE systems in the unlicensed spectrum (accordingly, LTE-based techniques operate only in the unlicensed spectrum without using "anchors" in the licensed spectrum) (referred to as multewire). Further enhanced operation of LTE systems in licensed and unlicensed spectrum may be expected in future releases and 5G systems. Such enhancement operations may include techniques for side link resource allocation and UE processing behavior for NR side link V2X communications.

The NG system architecture (or 6G system architecture) may include RAN 110 and 5G core network (5 GC) 120.NG-RAN 110 may include multiple nodes, such as a gNB and NG-eNB. The CN 120 (e.g., 5G core network/5 GC) may include Access and Mobility Functions (AMFs) and/or User Plane Functions (UPFs). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via the NG interface. More specifically, in some aspects, the gNB and NG-eNB may connect to the AMF through a NG-C interface and to the UPF through a NG-U interface. The gNB and NG-eNB may be coupled to each other via an Xn interface.

In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, or the like. In some aspects, the gNB may be a Master Node (MN) in a 5G architecture, and the NG-eNB may be a Secondary Node (SN).

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, fig. 1B illustrates a 5G system architecture 140B in reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 may communicate with RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of Network Functions (NF), such as AMF132, session Management Function (SMF) 136, policy Control Function (PCF) 148, application Function (AF) 150, UPF 134, network Slice Selection Function (NSSF) 142, authentication server function (AUSF) 144, and Unified Data Management (UDM)/Home Subscriber Server (HSS) 146.

UPF 134 may provide a connection to a Data Network (DN) 152, and DN 152 may include, for example, operator services, internet access, or third party services. The AMF 132 may be used to manage access control and mobility and may also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. The SMF 136 may be configured to establish and manage various sessions according to network policies. Thus, the SMF 136 may be responsible for session management and assigning IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. Each session may be assigned a different SMF. The use of different SMFs may allow each session to be managed separately. Thus, the functionality of each session may be independent of the other.

The UPF 134 can be deployed in one or more configurations depending on the type of service desired and can be connected to a data network. PCF 148 may be configured to: network slicing, mobility management and roaming are used to provide a policy framework (similar to PCRF in 4G communication systems). The UDM may be configured to: store subscriber profiles and data (similar to HSS in 4G communication systems).

AF 150 may provide information about the packet flow to PCF 148 responsible for policy control to support the desired QoS. PCF 148 may set mobility and session management policies for UE 101. To this end, PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and a plurality of IP multimedia core network subsystem entities (e.g., call Session Control Functions (CSCFs)). More specifically, the IMS 168B includes CSCFs that may act as proxy CSCF (P-CSCF) 162B, serving CSCF (S-CSCF) 164B, emergency CSCF (E-CSCF) (not shown in FIG. 1B), or query CSCF (I-CSCF) 166B. P-CSCF 162B may be configured as a first point of contact for UE 102 within IM Subsystem (IMs) 168B. S-CSCF 164B may be configured to handle session states in the network and E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. I-CSCF 166B may be configured to act as a contact point within an operator network for all IMS connections destined for subscribers of the network operator or roaming subscribers currently located within the service area of the network operator. In some aspects, I-CSCF 166B may be connected to another IP multimedia network 170E, such as an IMS operated by a different network operator.

In some aspects, the UDM/HSS 146 may be coupled to an application server 160B, which application server 160B may include a Telephony Application Server (TAS) or another Application Server (AS). AS 160B may be coupled to IMS 168B via S-CSCF 164B or I-CSCF 166B.

The reference point representation indicates that there may be interactions between the corresponding NF services. For example, fig. 1B shows the following reference points: n1 (between UE 102 and AMF 132), N2 (between RAN110 and AMF 132), N3 (between RAN110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between PCF 132 in the case of a non-roaming scenario, between PCF148 and AMF 132, or between PCF 132 in the case of a non-roaming scenario, or between N16 and AMF 132, not shown), N16 (between AMF 132, not shown), and N142, between nsf 132 and network (not shown). Other reference point representations not shown in fig. 1B may also be used.

Fig. 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in fig. 1B, the system architecture 140C may also include a network open function (NEF) 154 and a Network Repository Function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented by corresponding point-to-point reference points Ni, or as service-based interfaces.

In some aspects, as shown in fig. 1C, the service-based representation may be used to represent network functions within the control plane that enable other licensed network functions to access their services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: namf 158H (service-based interface shown by AMF 132), nsmf 158I (service-based interface shown by SMF 136), nnef 158B (service-based interface shown by NEF 154), npcf158D (service-based interface shown by PCF 148), nudm 158E (service-based interface shown by UDM 146), naf 158F (service-based interface shown by AF 150), nnrf 158C (service-based interface shown by NRF 156), nnssf 158A (service-based interface shown by NSSF 142), nausf 158G (service-based interface shown by AUSF 144). Other service-based interfaces not shown in fig. 1C (e.g., nudr, N5g-eir, and Nudsf) may also be used.

The NR-V2X architecture may support high reliability low latency side link communications with multiple traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein may be used to support high reliability in distributed communication systems with dynamic topologies, including side link NR V2X communication systems.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE, such as a dedicated computer, a personal or laptop computer (PC), a tablet PC or smart phone, a dedicated network device (e.g., eNB), a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that the communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for receipt by a receiving entity (e.g., gNB, UE) and decoded by the receiving entity after receipt.

Examples described herein may include or may operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations, and may be configured or arranged in some manner. In an example, the circuitry may be arranged in a specified manner (e.g., internally, or with respect to an external entity (e.g., other circuitry)) as a module. In an example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform specified operations.

Thus, the term "module" (and "component") is understood to encompass a tangible entity, whether physically constructed, a concrete configuration (e.g., hardwired), or a temporary (e.g., transient) configuration (e.g., programmed) as an entity that operates in a specified manner or performs some or all of any of the operations described herein. Consider an example where modules are temporarily configured, each of which need not be instantiated at any one time. For example, where a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as corresponding different modules at different times. Thus, software may configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

The communication device 200 may include a hardware processor (or equivalently, processing circuitry) 202 (e.g., a Central Processing Unit (CPU), GPU, hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. Main memory 204 may include any or all of removable storage and non-removable storage, volatile memory, or nonvolatile memory. The communication device 200 may also include a display unit 210 (e.g., a video display), an alphanumeric input device 212 (e.g., a keyboard), and a User Interface (UI) navigation device 214 (e.g., a mouse). In an example, display unit 210, input device 212, and UI navigation device 214 may be touch screen displays. The communication device 200 may further include a storage device (e.g., a drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors (e.g., a Global Positioning System (GPS) sensor, compass, accelerometer, or other sensor). The communication device 200 may also include an output controller, such as a serial connection (e.g., universal Serial Bus (USB)), parallel connection, or other wired or wireless connection (e.g., infrared (IR), near Field Communication (NFC), etc.), to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.).

The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter referred to simply as a machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within the static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine-readable medium 222 is shown to be a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

The term "machine-readable medium" can include any medium that can store, encode, or carry instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of this disclosure, or that can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of machine readable media may include solid state memory, optical and magnetic media. Specific examples of machine-readable media may include: nonvolatile memory such as semiconductor memory devices (e.g., electrically Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as built-in hard disks and removable disks; magneto-optical disk; random Access Memory (RAM); CD-ROM and DVD-ROM discs.

The instructions 224 may also be transmitted or received over a communication network using a transmission medium 226 via the network interface device 220 using any of a variety of Wireless Local Area Network (WLAN) transmission protocols (e.g., frame relay, internet Protocol (IP), transmission Control Protocol (TCP), user Datagram Protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a Local Area Network (LAN), a Wide Area Network (WAN), a packet data network (e.g., the internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network. The communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards (referred to as Wi-Fi), the IEEE 802.16 family of standards (referred to as WiMax), the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, point-to-point (P2P) networks, the Next Generation (NG)/fifth generation (5G) standards, and so forth. In an example, the network interface device 220 may include one or more physical jacks (e.g., ethernet jacks, coaxial jacks, or telephone jacks) or one or more antennas to connect to the transmission medium 226.

Note that the term "circuitry" as used herein refers to, is part of or includes the following hardware components: such as electronic circuitry, logic circuitry, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a Field Programmable Device (FPD) (e.g., a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a Complex PLD (CPLD), a high-capacity PLD (hcld), a structured ASIC, or a programmable SoC), a Digital Signal Processor (DSP), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements and program code (or a combination of circuitry and program code for use in an electrical or electronic system) for performing the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as specific types of circuitry.

Thus, the term "processor circuit" or "processor" as used herein refers to a circuit, part of or comprising, that is capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing and/or transmitting digital data. The term "processor circuit" or "processor" may refer to one or more application processors, one or more baseband processors, a physical Central Processing Unit (CPU), a single or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and/or functional processes).

Any of the radio links described herein may operate in accordance with any one or more of the following radio communication technologies and/or standards, including, but not limited to: global system for mobile communications (GSM) radio communications technology, general Packet Radio Service (GPRS) radio communications technology, enhanced data rates for GSM evolution (EDGE) radio communications technology and/or third generation partnership project (3 GPP) radio communications technology, such as Universal Mobile Telecommunications System (UMTS), multimedia free access (FOMA), 3GPP long term evolution (LTE Advanced), code division multiple access 2000 (CDMA 2000), cellular Digital Packet Data (CDPD), mobitex, third generation (3G), circuit Switched Data (CSD), high Speed Circuit Switched Data (HSCSD), universal mobile telecommunications system (third generation) (UMTS (3G)), wideband code division multiple access (universal mobile telecommunications system) (W-CDMA (UMTS)), high Speed Packet Access (HSPA), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), high speed packet access Plus (hspa+), universal mobile telecommunications system-time division duplex (UMTS-TDD), time division-code division multiple access (TD-CDMA), time division-synchronous code division multiple access (TD-CDMA), third generation partnership project release 8 (Pre-4 th generation) (3 GPP rel.8 (Pre-4G)), 3GPP rel.9 (third generation partnership project release 9), 3GPP rel.10 (third generation partnership project release 10) 3GPP rel.11 (third generation partnership project release 11), 3GPP rel.12 (third generation partnership project release 12), 3GPP rel.13 (third generation partnership project release 13), 3GPP rel.14 (third generation partnership project release 14), 3GPP rel.15 (third generation partnership project release 15), 3GPP rel.16 (third generation partnership project release 16), 3GPP rel.17 (third generation partnership project release 17) and subsequent releases (e.g., rel.18, rel.19, etc.), 3GPP 5G, 5G new air interface (5G NR), 3GPP 5G new air interface, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed Assisted Access (LAA), muLTEfire, UMTS Terrestrial Radio Access (UTRA), evolved UMTS terrestrial radio access (E-UTRA), advanced long term evolution (fourth generation) (LTE Advanced (4G)), cdmaOne (2G), code division multiple access 2000 (third generation) (CDMA 2000 (3G)), evolved data optimized or evolution data only (EV-DO), advanced mobile phone system (first generation) (1G)), full access communication system/extended full access communication system (TACS/ETACS), digital AMPS (second generation) (D-AMPS (2G)), push-to-talk (PTT), mobile phone System (OLTs), advanced mobile phone system (AMTS), MTS (norway Offentlig Landmobil Telefoni, public land mobile phone), MTD (Mobiltelefonisystem D, or mobile telephone system D), public automatic land mobile telephone (Autotel/PALM), ARP (autonomous audiopuhelin, "car radio telephone", finland mobile telephone), NMT (nordic mobile telephone), high capacity version of NTT (japanese telegraph telephone) (Hicap), cellular Digital Packet Data (CDPD), mobitex, dataTAC, integrated Digital Enhanced Network (iDEN), personal Digital Cellular (PDC), circuit Switched Data (CSD), personal Handyphone System (PHS), broadband integrated digital enhanced network (WiDEN), iBurst, unlicensed Mobile Access (UMA) (also known as 3GPP generic access network or GAN standard), zigbee, bluetooth, wireless gigabit alliance (WiGig) standard, universal mmWave standard (wireless system operating at 10-300GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating in the higher than 300GHz and THz bands (based on 3GPP/LTE or IEEE 802.11p or IEEE 802.11bd and others), vehicle-to-vehicle (V2V) and vehicle-to-X (V2X) and vehicle-to-infrastructure (V2I) and infrastructure-to-vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (dedicated short-range communication) communication systems (e.g., intelligent transportation systems and others (typically operating at or above 5850MHz to 5925MHz (as suggested by the changes in the CEPT report 71, typically up to 5935 MHz)), european ITS-G5 systems (i.e., europe based on DSRC of IEEE 802.11p, including ITS-G5A (i.e., ITS-G5 operates in the european ITS band dedicated to ITS for safety-related applications in the frequency range 5,875ghz to 5,255 ghz), ITS-G5B (i.e., operates in the european ITS band dedicated to ITS non-safety applications in the frequency range 5,855ghz to 5,875 ghz), ITS-G5C (i.e., operates in ITS applications in the frequency range 5,470ghz to 5,725 ghz), DSRC (including 715MHz to 725 MHz) in the 700MHz band in japan, IEEE 802.11 bd-based systems, and the like.

Aspects described herein may be used in the context of any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, licensed exempt spectrum, (licensed) shared spectrum (e.g., lsa=licensed shared access in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and further frequencies, and sas=spectrum access system/cbrs=citizen broadband radio in 3.55-3.7GHz and further frequencies). Applicable frequency bands include IMT (international mobile telecommunications) spectrum and other types of spectrum/frequency bands such as frequency bands with national allocations including 450-470MHz, 902-928MHz (note: e.g., FCC Part 15) allocated in the united states), 863-868.6MHz (note: e.g., ETSI EN 300 220) allocated in the european union), 915.9-929.7MHz (note: e.g., allocated in japan), 917-923.5MHz (note: e.g., allocated in korea), 755-779MHz and 779-787MHz (note: e.g., allocated in china), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (note: it is an ISM band with global availability), and also used by bluetooth in the european union), 2500-26790 MHz, 698-929.7 MHz, 3400 MHz, 3800-0 MHz, 3.7GHz, and 779-787MHz (note: e.g., allocated in china), total, and 3.5.g., 3-2025 MHz, 2110-2200MHz, 2300.5.725, 2.4-2.4835GHz (note: e.g., wi-5) and 3.725 are allocated in the radio frequency bands such as the internet of the international mobile telecommunications system of the international mobile telecommunications, which are allocated in the international mobile telecommunications system, and the total of the radio frequency bands such as the internet (e.g., 5.25.725.5.725.5.25.5.725, 60.25.725, 60.25.25.25.25.5.25.725, and the internet, 5.5.5.25.25.25.25.25.5.25.25.25.25.25.25.15.25.25.15.15.15.15, and (b, and so as the whole, inclusive, which is all of the ISM band The 5925-7125MHz and 5925-6425MHz bands (note: the next generation Wi-Fi systems are expected to include the 6GHz spectrum as the operating band under consideration of the united states and the european union, respectively, but note that by the month of 2017, wi-Fi systems are not allowed to be implemented in this band, regulations are expected to be completed within the 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (which is expected to include the 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, frequency bands in the 24.25-86GHz range, etc.), spectrum available under the FCC "front of spectrum" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 81-86GHz, 92-94GHz, etc.), the current traffic bands (smart traffic systems) of 5.9GHz (which are typically 5.85-5.925 GHz) and 63-64GHz, the wis bands (which are allocated to the wis bands (40.35-58G, 55G and the wish-96G bands) of the wis (40-58.35G and wis) band (58-58) and the wis-58G bands (58-35 and 58G and/35G and/or wish-96); this band is nearly globally designated for the Multiple Gigabit Wireless System (MGWS)/WiGig.) a total of 14GHz spectrum is allocated in the united states (FCC part 15), while the european union (ETSI EN 302 567 and ETSI EN301 217-2 (for fixed P2P)) allocates a total of 9GHz spectrum), the 70.2GHz-71GHz band, any band between 65.88GHz and 71GHz, the band currently allocated for automotive radar applications (e.g., 76-81 GHz) and future frequency bands (including 94-300GHz and beyond). Furthermore, the scheme may be used in an ancillary manner in a frequency band such as the TV white space frequency band (typically below 790 MHz), where especially 400MHz and 700MHz frequency bands are promising candidates. In addition to cellular applications, specific applications for the vertical market may also be addressed, such as PMSE (program production and special activities), medical, health, surgery, automotive, low latency, drone, etc. applications.

The aspects described herein may also enable hierarchical applications of the scheme, e.g., by introducing hierarchical prioritized usage (e.g., low/medium/high priority, etc.) for different types of users based on prioritized access to spectrum, e.g., highest priority to primary users, secondary users, then tertiary users, etc.

Aspects described herein may also be applied to different single carrier or OFDM styles (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multicarrier (FBMC), OFDMA, etc.), in particular 3GPP NR (new air interface), by assigning OFDM carrier data bit vectors to corresponding symbol resources.

Some features in this document are defined for the network side, e.g., AP, eNB, NR or gnb—note that this term is commonly used in the context of 3GPP fifth generation (5G) communication systems and the like. Still, the UE may also play this role, acting as an AP, eNB or gNB; that is, some or all of the features defined for the network device may be implemented by the UE.

Fig. 3 illustrates a RAN node connecting to two network slices simultaneously, according to some aspects. In fig. 3, for subscription and configuration: UEs A1 and A3 subscribe to slice M, UEs A2 and A3 subscribe to slice N, and the application of UE A3 is configured to use a particular network slice. In fig. 3, for deployment: slice N and slice M are isolated, the RAN can be connected to both slice M and slice N, and slice M and slice N are provided by the same Public Land Mobile Network (PLMN).

Based on 3gpp TS 23.501 and TS 38.300, the ue may access network slices during registration based on network provided information. Based on TS22.261 clause 6.1 network slicing, the 5G system allows operators to assign network slices to UEs, move UEs from one network slice to another, and remove UEs from network slices based on subscriptions, UE capabilities, access technologies used by the UEs, policies of the operators, and services provided by the network slices. Furthermore, the 5G system enables UEs to be simultaneously assigned to multiple network slices of one operator and to access services therein. However, when an active application for a UE uses a different network slice within the same operator's network, the UE may not be able to access or change the network slice. That is, the above does not consider the case when the network slices of the UE are disjoint within the network of one operator because the UE has no information to access the network slices based on its user preferences and active applications, which results in latency and poor service experience.

Thus, the network may provide auxiliary system information to allow the UE to perform network slice based cell reselection. Specifically, for a UE subscribed to multiple network slices that cannot be provided to the UE simultaneously: the 5G system provides the UE with the most appropriate network slice for one operator (e.g., based on ongoing applications, user preferences); or to support changing an operator provided network slice with minimal disruption, e.g., when triggered by a change in active applications and/or priorities.

Various solutions include using new cells (IEs) with network slice related information in system information block 2 (SIB 2), SIB3, SIB4, and SIB 5. In another solution, on-demand SIB request for SIB information related to slice/service type (SST) may be used for UEs in rrc_connected mode. In another solution, on-demand SIB requests for SIB information related to one or more SSTs using a Random Access Channel (RACH) procedure may be used for UEs in rrc_idle and rrc_inactive modes.

As understood herein, the UE follows the cell reselection procedure in 3gpp TS 38.304 and the principles for network slicing based on 3gpp TS 23.501. These principles include the identification of a network slice by a single network slice selection assistance information (S-NSSAI). The S-NSSAI has: slice/service type (SST), which refers to the network slice behavior expected in terms of features and services; and a Slice Discriminator (SD), which is optional information that supplements the SST to discriminate between multiple network slices of the same SST.

The S-NSSAI may have standard values (i.e., such S-NSSAI may contain only SSTs with standardized SST values, see clause 5.15.2.2, and no SDs) or non-standard values (i.e., such S-NSSAI may contain both SSTs and SDs, or only SSTs without standardized SST values and no SDs). The S-nsai having a non-standard value identifies a single network slice within the PLMN with which the S-nsai is associated. The S-nsai with non-standard values is not used by the UE for access layer procedures in any PLMN other than the PLMN with which the S-nsai is associated.

Based on TS23.501, clause 5.15.2.2: normalized SST value: the standardized SST values provide a way to establish global interoperability for slices so that PLMNs can more efficiently support roaming use cases for the most common SSTs. The following table 5.15.2.2-1 provides a standardized SST.

Table 5.15.2.2-1-normalized SST values

Slice/service type	SST value	Characteristics of
			eMBB	1	The slice is suitable for handling 5G enhanced mobile broadband.
URLLC	2	The slices are suitable for handling ultra-reliable low latency communications.
			MIoT	3	Slices are suitable for processing large-scale IoT.
V2X	4	The slice is suitable for handling V2X services.

These solutions are applicable and extensible for standardized SST values defined in future versions. The solution herein is for providing the UE with assistance information related to supported network slices in SIBs and allowing the UE to perform cell reselection procedures within the same network of one operator.

Solution 1: new IEs with network slice related information in SIB2, SIB3, SIB4 and SIB 5. In this solution, new IEs related to network slices are provided in SIB2, SIB3, SIB4, SIB5 for allowing the UE to perform cell reselection using SST related system information based on active applications and user preferences of the network slices.

As described in 3gpp TS 38.300, SIB2 contains cell reselection information mainly related to the serving cell; SIB3 contains information about the serving frequency and on co-frequency neighboring cells related to cell reselection (including cell reselection parameters common to the frequencies and cell specific reselection parameters); SIB4 contains information about other NR frequencies and inter-frequency neighbor cells related to cell reselection (including cell reselection parameters common to the frequencies and cell-specific reselection parameters); and SIB5 contains information about the E-UTRA frequency and E-UTRA neighbor cells related to cell reselection (including cell reselection parameters common to the frequency and cell specific reselection parameters).

Solution 1.1: network slice information in a system information block (SIB 2)

According to solution 1, sib2 contains cell reselection information common to co-frequency, inter-frequency and/or inter-RAT cell reselection (i.e., applicable to more than one type of cell reselection, but not necessarily all) and co-frequency cell reselection information other than the relevant neighboring cells. In this solution, IEs having a corresponding SST type of frequencyBandList as an interfreqcellresulectioninfo, such as frequencybandlist_sst1, frequencybandlist_sst2, frequencybandlist_sst3, frequencybandlist_sst4, and the like, are added.

-frequencyBandList_SST1 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST2 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST3 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST4 MultiFrequencyBandListNR-SIB

The frequencyBandList SSTX indicates a list of frequency bands of network slices with SST applied to support NR cell reselection parameters. Based on user preferences and active applications, the UE uses a corresponding frequencybandlist_sstx, where SSTX may be SST1, SST2, SST3, SST4, etc., based on standardized values.

If the network slice does not have a standardized value, the UE uses a frequencyBandList that does not provide differentiation based on the supported network slice types. These solutions are applicable and extensible for standardized SST values defined in future versions.

Solution 1.2: network slice information in a system information block (SIB 3)

According to solution 1, sib3 contains neighbor cell related information related only to on-channel cell reselection. The IE includes cells with specific reselection parameters and blacklisted cells. In this solution, an inter freqneighcelllist SSTX with a corresponding SST type is added, such as inter freqneighcelllist SST1, inter freqneighcelllist SST2, inter freqneighcelllist SST3, inter freqneighcelllist SST4, etc.

-intraFreqNeighCellList_SST1 IntraFreqNeighCellList

-intraFreqNeighCellList_SST2 IntraFreqNeighCellList

-intraFreqNeighCellList_SST3 IntraFreqNeighCellList

-intraFreqNeighCellList_SST4 IntraFreqNeighCellList

IntraFreqNeighCellList::＝SEQUENCE(SIZE(1..maxCellIntra))OF

IntraFreqNeighCellInfo

IntraFreqNeighCellInfo::＝ SEQUENCE{

-physCellId PhysCellId,

-q-OffsetCell Q-OffsetRange,

-q-RxLevMinOffsetCell INTEGER(1..8)OPTIONAL,--Need R

-q-RxLevMinOffsetCellSUL INTEGER(1..8)OPTIONAL,--Need R

-q-QualMinOffsetCell INTEGER(1..8)OPTIONAL,--Need R

-...

-}

The intra freqneighcellist SSTX indicates a list of co-frequency neighbor cells supporting network slices with a specific SST and with specific cell reselection parameters. Based on user preferences and active applications, the UE uses the corresponding intrafreqneighcellist_sstx. SSTX may be SST1, SST2, SST3, SST4, etc. based on standardized values.

If the network slice does not have a standardized value, the UE uses an intra FreqNeighCollList that does not provide differentiation based on the supported network slice type. These solutions are applicable and extensible for standardized SST values defined in future versions.

Solution 1.3: network slice information in a system information block (SIB 4)

According to solution 1, the sib4 contains information related to inter-frequency cell reselection only, i.e. information about other NR frequencies and inter-frequency neighbor cells related to cell reselection. The IE includes cell reselection parameters common to the frequencies and cell specific reselection parameters.

In this solution, for an inter freqcarrier freqlist with an inter freqcarrier freqinfo structure, the following new IE is used:

adding a frequencyBandList with a corresponding SST type as a new IE, e.g. frequencybandlist_sst1, frequencybandlist_sst2, frequencybandlist_sst3, frequencybandlist_sst4, etc.

-frequencyBandList_SST1 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST2 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST3 MultiFrequencyBandListNR-SIB

-frequencyBandList_SST4 MultiFrequencyBandListNR-SIB

The frequencyBandList SSTX indicates a list of frequency bands of network slices with a particular SST applied to support NR cell reselection parameters. Based on user preferences and active applications, the UE uses the corresponding frequencyBandList SSTX. SSTX may be SST1, SST2, SST3, SST4, etc. based on standardized values.

If the network slice does not have a standardized value, the UE uses a frequencyBandList that does not provide differentiation based on the supported network slice types.

An interFreqNeighcellList_SSTX with corresponding SST type is added, such as interFreqNeighcellList_SST1, interFreqNeighcellList_SST2, interFreqNeighcellList_SST3, interFreqNeighcellList_SST4, etc.

/>

The interfreqneigcelllist SSTX indicates a list of co-frequency neighbor cells supporting network slices with a particular SST and with particular cell reselection parameters. Based on user preferences and active applications, the UE uses the corresponding interfreqneighbor hcellist_sstx. SSTX may be SST1, SST2, SST3, SST4, etc. based on standardized values.

If the network slice does not have a standardized value, the UE uses the InterFreqNeighcellList_SSTX that does not provide differentiation based on the supported network slice type. These solutions are applicable and extensible for standardized SST values defined in future versions.

Solution 1.4: network slice information in a system information block (SIB 5)

According to solution 1, the sibs 5 contain information related to inter-RAT cell reselection only, i.e. information about E-UTRA frequencies and E-UTRA neighbor cells related to cell reselection. The IE includes cell reselection parameters common to the frequencies.

In this solution, for carrier freqeutra, the following IEs are used:

adding an eutra-multibandInfoList with a corresponding SST type as a new IE, e.g., eutra-multibandInfoList_SST1, eutra-multibandInfoList_SST2, eutra-multibandInfoList_SST3, eutra-multibandInfoList_SST4, etc.

-eutra-multiBandInfoList_SST1 EUTRA-MultiBandInfoList

-eutra-multiBandInfoList_SST2 EUTRA-MultiBandInfoList

-eutra-multiBandInfoList_SST3 EUTRA-MultiBandInfoList

-eutra-multiBandInfoList_SST4 EUTRA-MultiBandInfoList

The eutra-multibardrilist SSTX indicates a list of frequency bands of network slices with a specific SST applied to support NR cell reselection parameters. Based on user preferences and active applications, the UE uses the corresponding eutra-multibank list SSTX. SSTX may be SST1, SST2, SST3, SST4, etc. based on standardized values.

If the network slice does not have a standardized value, the UE uses an eutra-MultiBandInfoList that does not provide differentiation based on the supported network slice types. An eutra-FreqNeighCellList SSTX, such as eutra-FreqNeighCellList SST1, eutra-FreqNeighCellList SST2, eutra-FreqNeighCellList SST3, eutra-FreqNeighCellList SST4, etc. with the corresponding SST type is added.

The eutra-freqneigcelllist SSTX indicates a list of E-UTRA frequencies of neighboring cells supporting network slices with a specific SST and with specific cell reselection parameters. Based on user preferences and active applications, the UE uses the corresponding eutra-freqneighcellist SSTX. SSTX may be SST1, SST2, SST3, SST4, etc. based on standardized values.

If the network slice does not have a standardized value, the UE uses an eutra-FreqNeighCollList that does not provide differentiation based on the supported network slice types. These solutions are applicable and extensible for standardized SST values defined in future versions.

Solution 2: on-demand SIB request for SIB information related to required SST

According to solutions 1.1, 1.2, 1.3, 1.4 for SIB2, SIB3, SIB4, SIB5, for a UE in rrc_connected mode, the solution allows the UE to send an on-demand SIB request for SIB2/SIB3/SIB4/SIB5 with the requested SST. The gNB may respond with the requested SIB with the requested network slice information in a dedicated or broadcast manner.

The UE sets the content of the dedicatedsbrequest message with the requestedSST IE to indicate the requested SIB information related to the requested SST of the network slice as follows:

1> if a procedure is triggered to request the required SIB:

2>inclusion of requestedSIB-List and onDemandSIB-List in onDemandSIB-RequestListrequestedSST- ListTo indicate the requested SIB and the requested SST;

for UE information related to a network slice with a particular SST, the UE submits a dedicatedsibequest message including a requestedssib-List and a requestedSST-List to a lower layer for transmission.

Fig. 4 illustrates SI provisioning according to some aspects.

For UEs in rrc_connected modeRequests for other SIs (if the network is configured) may be sent to the network in a dedicated manner (i.e., via UL-DCCH messages including DedicatedSIBRequest IE), and the granularity of the request is one SIB.

The gNB may respond with RRCReconfiguration including the requested SIB in the following IE. Deciding which requested SIBs to transmit in a dedicated or broadcast manner is a network choice.

The dedicated SIB includes the requested network slice information as indicated in solutions 1.1, 1.2, 1.3, 1.4 for SIB2, SIB3, SIB4, SIB5, respectively. For example, if SIB-ReqInfo: =sib2 and ServiceLICEType-ReqInfo: =SST2 are requested, the network provides system information for SIB2, where the intaFreqCellReselectionInfo indicates frequencyBandList_SST2. For example, if SIB-ReqInfo: = SIB2 and ServiceLICEType-ReqInfo: = SST2 and SST4 are requested, the network provides system information for SIB2, where the intra FreqCellReselectionInfo indicates frequencyBandList_SST2 and frequencyBandList_SST4. In this case, the UE determines its preference to use frequencyBandList SST2 and/or frequencyBandList SST4 for cell reselection. For example, if SIB-ReqInfo: =sib4 and ServiceLICEType-ReqInfo: =SST2 are requested, the network provides system information for SIB4, where InterFreqCellReselectionInfo indicates frequencyBandList_SST2.

Solution 3: on-demand SIB request for SIB information related to required SST using RACH procedure

According to solutions 1.1, 1.2, 1.3, 1.4 for SIB2, SIB3, SIB4, SIB5, for UEs in rrc_idle and rrc_inactive modes, the solution allows the UE to request on-demand SIBs for SIB2/SIB3/SIB4/SIB5 with the requested SST.

According to 3gpp TS 38.311: if SIB1 includes SI-scheduling info including SI-RequestConfig and satisfies the criteria for selecting a normal uplink as defined in TS 38.321 clause 5.1.1, then the UE in rrc_idle and rrc_inactive modes sends a request for other SI triggers in the lower layer, which initiates a random access procedure according to TS 38.321 using PRACH preambles and PRACH resources in SI-RequestConfig corresponding to SI messages that the UE uses to operate in the cell and SI-BroadcastStatus is set to notb roadcasting (TS 38.300, clause 9.2.6). When the UE receives an acknowledgement of the SI request from the lower layer, the UE acquires the requested SI message.

In the RACH procedure, MSG3 includes an SI request message unless the requested SI is associated with a subset of PRACH resources, in which case MSG1 is used to indicate the other SI requested.

When MSG1 is used, the minimum granularity of the request is one SI message (i.e., a set of SIBs), one RACH preamble and/or PRACH resource may be used to request multiple SI messages, and the gNB acknowledges the request in MSG2 with the requested SIB including the requested network slice related information.

When the dedicatedsibequest message is sent using MSG3, the gNB acknowledges the request with the requested SIB including the requested network slice related information in MSG 4.

Fig. 5 illustrates a random access procedure in accordance with some aspects.

In this solution, an IE sstOption is added in the sibMappinInfo to indicate the SIB-TypeInfo with SIB type (including sibType2, sibType3, etc.) and sstOption in the corresponding sibType. For example, if sstption is set to 2, the SIB contains network slice information related to sst=2, as indicated in solutions 1.1, 1.2, 1.3, 1.4 for SIB2, SIB3, SIB4, SIB 5. For example, if sstption is set to 2 and 4, the SIB contains network slice information related to sst=2 and sst=4, as indicated in solutions 1.1, 1.2, 1.3, 1.4 for SIB2, SIB3, SIB4, SIB 5.

The details shown in the SI-SchedulingInfo cell are as follows: the IE SI-scheduling info contains information for acquiring the SI message.

SI-scheduling info cell

/>

The IE SI-RequestConfig contains a configuration for an Msg1 based SI request.

/>

Thus, in various embodiments, SIB2 contains cell reselection information that is common to co-frequency, inter-frequency, and/or inter-RAT cell reselections (i.e., applicable to more than one type of cell reselection, but not necessarily all) as well as co-frequency cell reselection information other than the relevant neighboring cells. SIB2 contains IEs of frequencyBandList with corresponding SST types, new IEs added as interfreqcellresulectioninfo, e.g., frequencybandlist_sst1, frequencybandlist_sst2, frequencybandlist_sst3, frequencybandlist_sst4, etc. SIB3 contains neighbor cell related information related only to on-channel cell reselection, and the IE includes cells with specific reselection parameters and blacklisted cells.

In 5G, network slicing is supported starting from release 15. Existing solutions do not take into account that the network slices required by the UE are disjoint within the network of one operator. The UE has no information to access the network slices based on its user preferences and active applications, which results in latency and poor service experience. Considering enhanced access and support for network slices, in 3gpp TR 22.835, fig. 6 illustrates a roaming UE with services on network slices available on different networks according to some aspects.

Case a, for 3gpp TR 22.835 clause 5.5, considers that the UE uses different network slices of different operators simultaneously (at different times), as follows:

the UE subscribes to a plurality of network slices from its home operator. The home operator agrees with various other operators to support the same slice for roaming UEs. In this case, the most preferred Visited PLMN (VPLMN) in the specific area does not support all desired slices; however, the second VPLMN does support slices that are not available in the most preferred VPLMN. In this case, the home operator may provide information to allow the UE to use the second VPLMN to obtain services available on the network slice, otherwise served by the most preferred VPLMN.

As shown in fig. 6, when UE a enters the visited area for the first time, UE a registers with network a and may use the service from slice N.

At a later time (T2), the user decides to activate the service using slice M. The UE finds the network providing the slice M detected that it is not available on network a. The UE registers on network B and the user can use the services of slice M.

When the service ends and slice M is no longer used (T3), if the UE is still used for slice N, it returns to network a.

Case B, which considers that the UE uses network slices of different operators simultaneously (at the same time) for 3gpp TR 22.835 clause 5.6: the UE accesses a plurality of network slices while on the HPLMN. When the UE is roaming and the VPLMN that the UE is currently registered with provides only a subset of the network slices that the UE is to use, the UE may connect to another VPLMN simultaneously to access other slices.

As shown in fig. 6, when UE a enters the visited area for the first time, UE a registers with network a and may use the service from slice N. At a later time (T2), the user decides to activate the service using slice M. The UE finds network B providing slice M, detecting that slice M is not available on network a. While maintaining slice N of network a, the UE accesses network B to use the services of slice M. The UE may use both slice N of network a and slice M of network B.

When the service ends and slice M is no longer needed (T3), the UE stops using slice M of network B and continues using slice N of network a.

Based on the service requirements of the roaming guidance in 3gpp TS 22.011 and 3gpp TS 22.261, and based on the solution of the roaming guidance in 3gpp TS 23.122, a solution is provided to realize the following:

when a roaming UE desires a network slice that is not provided by the serving network but is available in the area of another network, the HPLMN should be able to direct the UE to that other network and back to the previous network when the network slice is no longer in use.

When a UE is to use two network slices that are simultaneously accessed from two VPLMNs and these are not available in a single network, the 5G system should enable a roaming UE with a single PLMN subscription to access these network slices simultaneously.

The HPLMN should be able to authorize roaming UEs with a single PLMN subscription to access network slices from both VPLMNs simultaneously.

The HPLMN should be able to provide the UE with authorization and priority information for the VPLMN that the UE is authorized to access a particular network slice.

Note that: the above depends on certain UE capability assumptions, e.g. the capability to connect to two PLMNs simultaneously.

Thus, the following solution enhances disjoint network slicing with one or more operators.

Solution 1: included in the roaming guidance (SoR) information is network slice information, i.e. "operator controlled PLMN selector with access technology and network slice" list. This is to solve case a and case B and meet the corresponding service requirements.

Solution 2: SD information of S-NSSAI is allowed to be skipped.

Solution 3: the problem of the use case A is solved, and the corresponding service requirement is met. The solution uses the same Radio Access Technology (RAT) in the first and second PLMNs for the UE.

Solution 4: the problem of the use case B is solved, and the corresponding service requirement is met. It allows the UE to register simultaneously with the first and second PLMNs using different RATs for their different network slices.

Background:

3GPP TS 22.011：sub-clause 3.2.2.8

3GPP TS 22.261：Sub-clauses 6.30 (for SoR) and 6.1 (for network slicing)

3GPP TS 23.122：

The purpose of the control plane solution for roaming steering in the 5GS procedure is to allow the HPLMN to update the "operator controlled PLMN selector with access technology" list in the UE by providing a list of HPLMN protections for preferred PLMN/access technology combinations via NAS signaling.

If the selected PLMN is a VPLMN, the HPLMN may provide roaming guidance information to the UE using control plane mechanisms during and after registration.

If the selected PLMN is the HPLMN, the HPLMN may provide roaming guidance information to the UE using a control plane mechanism only after registration.

The HPLMN updates the "operator controlled PLMN selector with access technology" based on an operator policy, which may be based on the registered VPLMN, the location of the UE, etc.

The HPLMNs may configure Universal Subscriber Identity Modules (USIMs) of UEs to which they subscribe to indicate that the UE is expected to receive roaming guide information due to initial registration in the VPLMN.

A UE supporting the N1 mode should support a control plane solution for roaming guidance in 5 GS. If the HPLMN supports and wants to use a control plane solution for roaming guidance in 5GS, the HPLMN should provide roaming guidance information to the UE using the control plane mechanism defined in the present attachment.

The VPLMN should transparently relay the roaming guide information received from the HPLMN to the UE.

The UE should be able to detect whether the VPLMN has removed the roaming guide information during the initial registration procedure in the VPLMN.

The UE should be able to detect whether the VPLMN has changed the roaming guide information. If the UE detects that the VPLMN changes or the roaming guide information is removed, the UE should consider the current VPLMN as the lowest priority PLMN and perform PLMN selection as defined in this attachment.

If: the USIM of the UE is configured to indicate that the UE should expect to receive the roaming guide information during the initial registration procedure but not receive it, or that security check of the roaming guide information fails; the currently selected VPLMN is not included in the "PLMN with registration suspended by SOR" list; the currently selected VPLMN is not part of the "user controlled PLMN selector with access technology" list; the UE is not in manual mode of operation; the UE will perform PLMN selection and the current VPLMN is considered to be the lowest priority.

The VPLMN is forced to transparently forward roaming guidance information received from the HPLMN to the UE when the UE attempts to register with the VPLMN and to transparently forward acknowledgement of successful receipt of the roaming guidance information received from the UE to the HPLMN after the UE has registered with the VPLMN.

The procedure of bootstrapping the UE in the VPLMN may be initiated by the network when the UE attempts to register with the VPLMN or after the UE has registered with the HPLMN or VPLMN.

C.2 phase 2 procedure for guiding a UE in a VPLMN during registration

Fig. 7 illustrates a procedure for providing a list of preferred Public Land Mobile Network (PLMN)/access technology combinations, in accordance with some aspects. A phase 2 flow for the case when the UE registers with the VPLMN AMF is described in fig. 7. The selected PLMN is a VPLMN. The AMF is located in the selected VPLMN.

C.3 phase 2 procedure for guiding UE in HPLMN or VPLMN after registration

Fig. 8 illustrates a process for providing a list of preferred PLMN/access technology combinations after registration, in accordance with some aspects. A phase 2 flow for booting the UE in the HPLMN or VPLMN after registration is indicated in fig. 8. The selected PLMN may be an HPLMN or a VPLMN. The AMF is located in the selected PLMN. The procedure is triggered under the following conditions: if the HPLMN UDM supports obtaining a list or security packet of preferred PLMN/access technology combinations from the SOR-AF, there is an HPLMN policy in the HPLMN UDM for SOR-AF invocation, and the SOR-AF provides the new list or security packet of preferred PLMN/access technology combinations for the SUPI identified UE to the HPLMN UDM; or when a new list of preferred PLMN/access technology combinations or security packets becomes available in the HPLMN UDM.

The solution is based on the following two assumptions:

the ue may obtain the roaming guidance information based on the SoR procedure with the new addition in 3gpp TS 22.122. For roaming guidance: the SOR list includes PLMN and access technology combinations, there are indications to receive reports, and there are two flows: the UE-triggered SOR update during the registration procedure or the SOR-AF-triggered update after registration.

Ue and network follow the following network slicing principle based on 3gpp TS 23.501:

S-NSSAI identifies a network slice.

The S-NSSAI includes: SST and SD.

The S-NSSAI may have standard values (such S-NSSAI includes only SSTs with standardized SST values, see clause 5.15.2.2, and no SDs) or non-standard values (such S-NSSAI includes both SSTs and SDs, or includes only SSTs without standardized SST values and no SDs). The S-nsai having a non-standard value identifies a single network slice within the PLMN with which the S-nsai is associated. The S-nsai with a non-standard value should not be used by the UE in the access stratum procedure of any PLMN other than the PLMN with which the S-nsai is associated.

Furthermore, clause 5.15.2.2, based on 3gpp TS 23.501: normalized SST value

The standardized SST values provide a way to establish global interoperability for slices so that PLMNs can more efficiently support roaming use cases for the most common slice/service types. Standardized SST is in table 5.15.2.2-1.

Table 5.15.2.2-1-normalized SST values

Slice/service type	SST value	Characteristics of
			eMBB	1	The slice is suitable for handling 5G enhanced mobile broadband.
URLLC	2	The slice is suitable forProcessing ultra-reliable low latency communications.
			MIoT	3	Slices are suitable for processing large-scale IoT.
V2X	4	The slice is suitable for handling V2X services.

These solutions are applicable and extensible for standardized SST values defined in future versions. The above solutions 0-4 enhance disjoint network slices with one or more operators.

Solution 0: new service requirements

The following service requirements are used:

for use case A, [ New-A1 ]: when a roaming UE is to use a network slice that is not provided by the serving network but is available in the area of another network, the HPLMN should be able to direct the UE to that other network and initiate a higher priority PLMN selection based on the type of network slice for the ongoing or restored application when the network slice is no longer in use.

For use case B, [ new-B1 ]: when a UE is to use simultaneous access to the HPLMN and another VPLMN, and network slices from both networks are not available in a single network, the 5G system should enable UEs with a single PLMN subscription to access these network slices simultaneously.

For use case B, [ new-B2 ]: when a UE with a single PLMN subscription registers on the HPLMN or VPLMN, is in an automatic mode (see clause 3.1 of 3gpp TS 23.122) and is currently in CONNECTED mode, and initiates a higher priority PLMN selection for the other VPLMN based on the network slice type for the ongoing application to access network slices from both PLMNs simultaneously, the 5G system should support the mechanism of HPLMN control timing.

Solution 1: soR list with additional network slice information

The registered AMF may provide a SoR list, a "operator controlled PLMN selector with access technology and network slicing" list, in which each PLMN is provided with an associated S-nsai based on subscription information of UEs related to the subscribed S-nsai during the registration procedure.

Two SoR list options are available:

1) A SoR list containing VPLMN information of VPLMNs with access technology and supported S-NSSAI combinations

2) A plurality of SoR lists, wherein each SoR list has VPLMN information with access technology and associated S-NSSAI.

The UE stores a SoR list containing a list of "operator controlled PLMN selectors with access technology and network slicing".

Solution 1.1: indication of skip SD

According to solution 1, the sor list comprises an operator controlled PLMN selector with access technology and network slicing, which is a preferred PLMN/access technology/S-nsai combination.

The list also contains an indication of skipped SDs in each S-nsai. If the indication is active, the UE may select a VPLMN with the desired SST in the S-NSSAI without regard to the SD information of the S-NSSAI.

Solution 1.2: registration update

According to solution 1 or 1.1, when a UE is to change a network slice with a different S-nsai and currently not supported by the current registration of its first PLMN, the UE initiates a registration procedure with a registration type indicating a mobility registration update.

Solution 1.3:

according to solution 1.2, the registration request message may provide additional information to trigger the process of updating the SoR list, with the following options:

1) An indicator for SoR with a network slice indicator is included for updating a SoR list containing VPLMN information with access technology and supported S-NSSAI combinations. This is used in the case of only one SoR list, as indicated in solution 1.

2) Including a new IE indicating one or more S-NSSAIs for the network slice to be used. This is for a plurality of SoR lists, where each SoR list has VPLMN information with access technology and associated S-NSSAI, as indicated in solution 1.

Solution 1.4:

the network performs the procedure based on the PLMN currently registered by the UE according to solution 1.3,5G:

if the currently registered network is the HPLMN, the HPLMN AMF provides the UE with an update of the SoR list, i.e. "operator controlled PLMN selector with Access technology and network slicing" list via NAS signaling.

If the currently registered network is a VPLMN, the VPLMN AMF includes an indicator for updating the SoR list or a new IE indicating one or more S-NSSAIs of the desired network slice in a Nudam_SDM_get request message to the HPLMN UDM, and the indication is forwarded by the HPLMN UDM to the SOR-AF in a Nsoraf_SoR_Obtain request message.

In response to the nsoraf_sor_obtain request message, the following procedure is performed: the SOR-AF may provide an update of the SOR list with all information or one or more lists of S-nsais with different associations in a nsoraf_sor_obtain response message to the HPLMN UDM. This information is forwarded by the HPLMN UDM to the VPLMN AMF. The VPLMN AMF provides the UE with an update of the "operator controlled PLMN selector with access technology and network slicing" list via NAS signaling.

Solution 1.5:

fig. 9 illustrates a process for providing a list of preferred PLMN/access technology combinations in accordance with some aspects. According to solution 1.4, according to the existing registration procedure in 3gpp TS 23.122 clause c.2.1 and fig. 9, in this solution the UE may initiate the following added registration procedure with SoR list for "operator controlled PLMN selector with access technology and network slicing":

The procedure may also be initiated for UEs that are to change network slices that have different slice/service types or S-nsais and are not currently supported by the current registration of the first PLMN provided by operator a.

In fig. 9, step 1: the UE initiates a registration procedure with a registration type indicating a mobility registration update and a SoR indicator IE for the network slice or a new IE indicating one or more S-nsais for the network slice of SoR information. By means of an indication, the HPLMN/VPLM AMF triggers an update of the SoR list from the HPLMN during the registration procedure.

Step 2: if the UE is currently registered with the VPLMN, the VPLMN AMF sends a Nudm_SDM_get request to the HPLMN UDM and includes an indication of a SoR update indicator or one or more S-NSSAIs for network slices of SoR information.

Step 3a: the HPLMN UDM considers an indication of SoR for a network slice or one or more S-NSSAIs for a list of sors.

Step 3b: the HPLMN UDM sends a NSoraf_SoR_Obtain request with an indication of SoR for a network slice or an indication of one or more S-NSSAIs for a network slice of a SoR list.

Step 3c: the SOR-AF provides one or more SOR lists for updating the SOR list or S-NSSAI with a different association to the HPLMN UDM in a nsoraf_sor_obtain response message.

Step 4: the HPLMN UDM provides a secure SoR list in the nudm_sdm_get response message.

Step 6: the VPLMN AMF forwards the SoR list to the UE via a registration accept message.

Step 11: the UE may perform a PLMN selection procedure if a higher priority PLMN is available for the desired network slice of the UE application.

Solution 2:

according to solution 1.1, subscription information related to a network slice includes an indication for allowing the VPLMN to skip the SD of the subscribed S-nsai, wherein SD is optional information of a supplementary slice/service type to distinguish between multiple network slices of the same slice/service type.

If the indication to skip SD is indicated in the S-NSSAI subscription, the VPLMN may modify its own SD in the S-NSSAI and send it to the UE as an allowed S-NSSAI.

Solution 2.1:

according to solution 2, the SoR list with associated S-NSSAI may contain an indication of skipped SDs for the VPLMN. With this indication, the UE is allowed to register with a selected VPLMN in the SoR list associated with S-nsais having different SDs among the subscribed S-nsais of the UE.

If the indication to skip SD is indicated in the S-NSSAI subscription, the VPLMN may modify its own SD in the S-NSSAI and send it to the UE as an allowed S-NSSAI. That is, the UE is allowed to use the allowed S-nsai for its services in the PDU session.

Solution 2.2:

according to solution 1.5, the ue may initiate a registration procedure with addition of SoR list for "operator controlled PLMN selector with access technology and network slicing".

Solution 3: use case A solution

The solution is used to solve the problem of use case a and meet the following service requirements. The solution is for UEs using the same RAT in the first and second PLMNs.

When a roaming UE is to use a network slice that the serving network does not provide but is available in the area of another network, the HPLMN should be able to direct the UE to the other network and return to the previous network when the network slice is no longer in use.

When a roaming UE is to use a network slice that is not provided by the serving network but is available in the area of another network, the HPLMN should be able to direct the UE to that other network and initiate a higher priority PLMN selection based on the type of network slice used for the ongoing or restored application when the network slice is no longer in use.

Solution 3.1:

according to solution 3, when the UE determines to initiate a registration procedure to a selected PLMN in the SoR list having a desired S-NSSAI that the current first PLMN for the UE application cannot provide, the UE sends a reservation indicator in a NAS message before the UE leaves to the second PLMN. In the NAS response message, the AMF provides a reservation timer for UE registration and starts the reservation timer. During the period when the reservation timer is active, the network maintains the UE context of the UE.

If the UE does not return to the AMF, the AMF performs implicit registration for the UE.

Solution 3.2:

according to solution 3.1, the reservation indicator is a reservation timer. The AMF may modify the reservation timer based on the network policy and return the allowed reservation timer to the UE.

Solution 3.3:

according to solution 3.1 or 3.2, when the UE receives the response message, the UE starts a reservation timer and maintains the UE context for that PLMN.

Solution 3.4:

according to solution 3.3, when the UE completes the service in the second PLMN before the retention timer expires, the UE may determine whether to return to the first PLMN when the retention timer runs based on the UE active application and the network slices that the first PLMN is capable of providing.

If the UE uses an application that utilizes network slices that the first PLMN can provide, the UE performs a registration procedure with mobility registration update to the first PLMN. The network stops the reservation timer and resumes service to the UE.

If the UE uses an application of network slices that cannot be provided with the first PLMN, the UE may initiate a priority PLMN selection procedure based on the SoR list with network slice information.

Solution 4: use case B solution

The solution is used for solving the problem of the use case B and meeting the corresponding service requirements. The solution allows UEs using different RATs to register simultaneously with the first and second PLMNs for their different network slices.

When a UE is to use two network slices that are simultaneously accessed from two VPLMNs and these are not available in a single network, the 5G system should enable a roaming UE with a single PLMN subscription to access these network slices simultaneously.

The HPLMN should be able to authorize roaming UEs with a single PLMN subscription to access network slices from both VPLMNs simultaneously.

The HPLMN should be able to provide the UE with permission and priority information of the VPLMN that the UE is authorized to access a particular network slice.

When a UE is to use simultaneous access to the HPLMN and another VPLMN, and the network slices are not available in a single network, the 5G system should enable a UE with a single PLMN subscription to access network slices from both networks simultaneously.

When a UE with a single PLMN subscription registers on the HPLMN or VPLMN, is in an automatic mode (see clause 3.1 of TS 23.122) and is currently in CONNECTED mode, and initiates a higher priority PLMN selection for the other VPLMN based on the network slice type for the ongoing application to access network slices from both PLMNs simultaneously, the 5G system should support the mechanism of HPLMN control timing.

Solution 4.1:

according to solution 4, the ue stores a SoR list containing a list of "operator controlled PLMN selectors with access technology and network slicing". The SoR list may have two options: 1) One SoR list containing VPLMN information with a combination of access technology and supported S-nsai, 2) a plurality of SoR lists, wherein each SoR list contains VPLMN information with an access technology and associated S-nsai.

When the UE determines to initiate a registration procedure with a selected PLMN associated with its desired S-nsai in the second RAT and SoR list (where 1) the desired S-nsai cannot be provided by the current first PLMN using the first RAT for its applications and 2) the allowed RAT is different from the first RAT), the UE may initiate a registration procedure with a second PLMN using a second RAT different from the first RAT for its first registration with the first PLMN.

For example, the UE may register with a first PLMN using 3GPP access that provides a desired first S-nsai for applications a and B, and with a second PLMN using non-3GPP access that provides a desired second S-nsai for application C.

The solution may follow the principles of clause 4.7.2.1 in 3gpp TS 23.501:

the mobility management procedure defined on the 3GPP access is reused on the non-3GPP access, with the following exceptions:

a) Registration status and 5GMM parameters of the UE's 3GPP access and non-3GPP access 5GMM state machine instance are independent and may be different in each of these accesses;

b) The single registration mode and the dual registration mode are not applicable to non-3GPP access on a 5 GMM;

c) The Registered PLMN (RPLMN) on the non-3GPP access can be different from the RPLMN on the 3GPP access. The Mobile Country Code (MCC) of the RPLMN on the 3GPP access and the MCC of the RPLMN on the non-3GPP access may also be different;

d) In consideration of 5GMM on non-3GPP access in UE, when the lower layer indicates that connection establishment of an access layer is successful, establishing N1 NAS signaling connection;

e) A UE-initiated service request procedure via non-3GPP access is supported. After an indication from the lower layer of the non-3GPP access that an access layer connection is established between the UE and the network, the UE in the 5GMM-REGISTERED state and the 5GMM-IDLE mode on the non-3GPP access should initiate a service request procedure via the non-3GPP access. The UE may indicate a PDU session associated with the non-3GPP access with a service request message to re-establish user plane resources for which the UE has pending user data to send.

Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments shown are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The detailed description is, therefore, not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Subject matter may be referred to herein, individually and/or collectively, by the term "embodiment" merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

In this document, the terms "a" or "an" are used to include one or more than one, independent of any other instances or usages of "at least one" or "one or more," as is common in patent documents. In this document, the term "or" is used to refer to a non-exclusive "or" such that "a or B" includes "a but not B", "B but not a" and "a and B" unless otherwise indicated. In this document, the terms "comprise" and "wherein" are used as simple English equivalents of the respective terms "comprising" and "wherein". Furthermore, in the following claims, the terms "comprise" and "comprise" are open-ended, i.e., a system, UE, article, composition, constitution, or process that comprises elements other than those listed after such term in the claims, still be considered to fall within the scope of the claims. Furthermore, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The abstract is provided to comply with 37c.f.r. ≡1.72 (b), which requires an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. The disclosed method should not be interpreted as reflecting the intent: the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims (20)

1. An apparatus for a User Equipment (UE), the apparatus comprising:

processing circuitry configured to:

decoding system information from a fifth generation NodeB (gNB), the system information comprising a System Information Broadcast (SIB) containing network slice related information or SIB information related to a slice/service type (SST) to access a plurality of isolated network slices provided by a Public Land Mobile Network (PLMN);

Accessing at least one network slice according to information provided by the PLMN during registration;

determining to access another network slice based on at least one of an active application or user preference on the UE; and

performing cell reselection using the system information in response to determining to access another network slice; and

and a memory configured to store the system information.

2. The apparatus of claim 1, wherein:

the system information is provided in frequencyBandList IE with corresponding SST type in an inter FreqCellReselectionInfo cell (IE) in SIB2, and

frequencyBandList IE with a corresponding SST type of value X, referred to as frequencyBandList SSTX, indicates a list of frequency bands with corresponding SST type of value X applied to support cell reselection parameters, and SIB2 contains cell reselection information common to at least one of co-frequency, inter-frequency or inter-Radio Access Technology (RAT) cell reselection.

3. The apparatus of claim 1, wherein:

the system information is provided in an intra FreqNeighcelLIST cell (IE) with corresponding SST type in SIB3, and

intraFreqNeighCellList IE with a corresponding SST type of value X, called intra freqneighcellist SSTX, indicates a list of co-frequency neighbor cells with network slices of the corresponding SST type that support a network slice with a specific cell reselection parameter.

4. The apparatus of claim 1, wherein:

the system information is provided in a frequencyBandList cell (IE) with a corresponding SST type in interFreqCarrierFreqList IE in SIB4,

frequencyBandList IE with corresponding SST type of value X, called inter freqcarrier freqlist SSTX IE, indicates a list of frequency bands of network slices with corresponding SST type of value X applied to support cell reselection parameters, and

interFreqNeighCellList IE with a corresponding SST type of value X, referred to as the interfreqneighbor list SSTX IE, indicates a list of inter-frequency neighbor cells supporting network slices with a corresponding SST type of value X with a particular cell reselection parameter.

5. The apparatus of claim 1, wherein:

the system information is provided in the eutra-multiBandInfoList IE with corresponding SST type in the carrier freqeutra cell (IE) in SIB5,

eutra-multiBandInfoList IE, called eutra-multibarringInfoList_SSTX, with corresponding SST type of value X, indicates a list of E-UTRA bands supporting network slices with corresponding SST type of value X applied by E-UTRA cell reselection parameters, and

the eutra-FreqNeighCellList IE, called eutra-freqneighcellist SSTX, with a corresponding SST type of value X indicates a list of E-UTRA frequencies of neighboring cells supporting network slices with a corresponding SST type of value X with a specific E-UTRA cell reselection parameter.

6. The apparatus of claim 1, wherein:

the UE is in RRC CONNECTED mode,

the processing circuit is further configured to: encoding an on-demand SIB request for at least one of SIB2, SIB3, SIB4, or SIB5 with one or more SSTs for transmission to the gNB, and

the system information is received in a dedicated response or a broadcast response in response to the transmission of the on-demand SIB request.

7. The apparatus of claim 6, wherein:

the on-demand SIB request includes a requestedSIB-List IE and a requestedSST-List IE in an ondemandSIB-RequestList IE of a DedimededSIBRequest cell (IE), an

The requestedSIB-List IE and the requestedSST-List IE indicate each SIB and SST requested, respectively.

8. The apparatus of claim 6, wherein the processing circuit is configured to:

decoding a decode system information delivery Information Element (IE) of an rrcrecon configuration message from the gNB in response to an on-demand SIB request containing a plurality of SSTs, the dedicatedSystemInformationDelivery IE including frequencyBandList IE for each SST; and

it is determined which frequency band list among frequencyBandList IE for each SST is to be used for cell reselection.

9. The apparatus of claim 1, wherein:

the UE is in RRC _ INACTIVE mode,

SIB1 includes si-SchedulingInfo IE containing scheduling info Information Element (IE),

the SchedulingInfo IE includes SIB-Mapping info including SIB-Mapping IE,

the SIB-Mapping IE includes SIB-TypeInfo IE, an

The SIB-TypeInfo IE includes a sibType IE indicating the SIB type and a sstpoption IE indicating the SST for the SIB type.

10. The apparatus of claim 9, wherein:

the SI-SchedulingInfo IE contains a SI-RequestConfig IE indicating the configuration of Msg1 resources used by the UE to request an SI message with SI-BroadcastStatus IE set to notBroad casting, and

the SI-RequestConfig IE contains SI-RequestResources IE, the SI-RequestResources IE indicating a request resource for a System Information (SI) message, wherein a unique entry in the list of request resources is used for all SI messages for which SI-BroadcastStatus is set to notbaradd, otherwise each added entry in the list of request resources corresponds to an added SI message.

11. An apparatus for a User Equipment (UE), the apparatus comprising:

Processing circuitry configured to:

during registration with a Public Land Mobile Network (PLMN), decoding a SoR information containing a roaming guide (SoR) list provided by a Home PLMN (HPLMN) and including a combination of PLMNs and access technologies associated with each PLMN;

when roaming, determining that the network slice to be used is provided by a network other than the serving network; and

based on the SoR information, initiate a higher priority PLMN selection based on the type of network slice to be used; and

and a memory configured to store the SoR information.

12. The apparatus of claim 11, wherein:

the UE has a single PLMN subscription, and

the processing circuit is configured to:

determining that a network slice to be used is not available in a single network; and

in response to determining that the network slice to be used is not available in the single network, enabling, by the HPLMN, simultaneous access to network slices from multiple PLMNs including the HPLMN and a Visited PLMN (VPLMN).

13. The apparatus of claim 11, wherein:

the UE has a single PLMN subscription,

the UE registers with the HPLMN or a Visited PLMN (VPLMN),

the UE is in an automatic mode and in an RRC_CONNECTED mode, and

The processing circuit is configured to:

determining that a network slice to be used is not available in a single network; and

based on the type of network slice used for the ongoing application, a higher priority PLMN selection is initiated for another VPLMN to access network slices from multiple PLMNs simultaneously.

14. The apparatus of claim 11, wherein:

in the SoR list, each PLMN is provided with one or more single network slice selection assistance information (S-nsai) based on subscription information of the UE related to S-nsai subscribed during registration of the UE, and

the S-NSSAI identifies network slices and has a slice/service type (SST) that refers to network slice behavior expected in terms of features and services, and a Slice Discriminator (SD) that distinguishes between multiple network slices of a single SST.

15. The apparatus of claim 14, wherein:

each S-NSSAI in the SoR list includes an indication of whether the SD is to be skipped, an

The processing circuit is configured to:

determining that an indication for a particular S-NSSAI is set to active; and

in response to determining that the indication for a particular S-nsai is set to active, a Visited PLMN (VPLMN) having an SST in the particular S-nsai is selected without regard to SD information of the particular S-nsai.

16. The apparatus of claim 14, wherein the processing circuit is configured to:

determining that a change in network slice is to be performed for an S-nsai that is not supported by the serving network registered by the UE;

initiating registration using a registration request message having a registration type indicating a mobility registration update in response to determining that a change in network slice is to be performed, the registration request message providing information for triggering a procedure to update the SoR list; and

in response to the transmission of the registration request message:

receiving an update of the SoR list from an Access and Mobility Function (AMF) of the HPLMN if the UE registers with the HPLMN; and

if the UE registers with a Visited PLMN (VPLMN), an update of the SoR list forwarded from the HPLMN is received from an AMF of the VPLMN.

17. The apparatus of claim 11, wherein:

the single network slice selection assistance information (S-nsai) identifies network slices and has a slice/service type (SST), which refers to network slice behavior expected in terms of features and services, and a slice identifier (SD), which distinguishes between multiple network slices of a single SST,

the SoR list includes an indication of whether to skip the SD of each S-NSSAI of each Visited PLMN (VPLMN), an

The processing circuit is configured to: registers with a selected VPLMN associated with S-NSSAI in the SoR list regardless of the SD.

18. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a User Equipment (UE), the one or more processors configuring the UE to, when executed:

decoding a roaming guide (SoR) information containing a SoR list provided by a Home PLMN (HPLMN) during registration with a Public Land Mobile Network (PLMN), the SoR list including a combination of Visited PLMNs (VPLMNs) and access technologies associated with each VPLMN;

upon roaming, determining that the network slice to be used is provided by an alternative VPLMN other than the serving VPLMN; and

in response to the UE being able to register with the serving VPLMN and the alternative VPLMN simultaneously, decoding, from the HPLMN, steering information for the alternative VPLMN, and when network slices are no longer in use:

decoding from the HPLMN other steering information for returning to the serving VPLMN, or

Higher priority PLMN selection is initiated based on the type of network slice used for the ongoing or recovering application.

19. The medium of claim 18, wherein the instructions, when executed, further configure the one or more processors to configure the UE to:

Encoding a reservation indicator in a non-access stratum (NAS) message for transmission to the serving VPLMN before being directed to the alternative VPLMN;

decoding, from the serving VPLMN, a NAS response message containing a reservation timer for registration prior to being directed to the alternative VPLMN, during which at least one of the serving VPLMN or the UE reserves a UE context of the UE; and

in response to completion of service in the alternative VPLMN before expiration of the reservation timer:

determining whether to return to the serving VPLMN based on active applications and network slices that the serving PLMN can provide;

in response to determining that the serving VPLMN is capable of providing network slices for the active applications, registering with the serving VPLMN using a mobility registration update for the serving VPLMN to stop the reservation timer and resume service of the UE; and

responsive to determining that the serving VPLMN is not capable of providing network slices for the active application, initiating a priority PLMN selection procedure based on a SoR list with network slice information; and

after expiration of the reservation timer, an implicit registration with the serving VPLMN is accepted.

20. The medium of claim 18, wherein the instructions, when executed, further configure the one or more processors to configure the UE to:

decoding from the HPLMN in response to the UE being able to register with multiple PLMNs simultaneously:

using authorization of a single PLMN subscription, to enable the UE to access network slices from the serving VPLMN and the alternative VPLMN or from the serving VPLMN and the HPLMN simultaneously,

permission and priority information of the serving VPLMN and the alternative VPLMN for accessing a specific network slice, and

timing information indicated for the UE while in the automatic mode and the rrc_connected mode to initiate higher priority PLMN selection based on the type of network slice for the ongoing application for accessing the multiple PLMNs simultaneously.

Images