Cell barring for network slices

Abstract

An access node of a radio access network (RAN) that supports one or more network slices, each network slice providing a specified service within a public land mobile network (PLMN). The access node includes processor circuitry and transmitter circuitry. The processor circuitry is configured to generate system information that includes a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell barring information. The network slice cell barring information includes one or more network slice identifiers for which a cell is barred. The transmitter circuitry is configured to transmit the system information to the cell.

Description

Technical Field

[0001] This technology relates to wireless communication, and more specifically to resource utilization in sliced ​​networks. Background Technology

[0002] Radio access networks typically reside between radio devices (such as user equipment (UE), mobile phones, mobile stations, or any other device with a radio terminal) and the core network. Examples of radio access network types include: GRAN, i.e., GSM radio access network; GERAN, which includes EDGE packet radio service; UTRAN, i.e., UMTS radio access network; E-UTRAN, which includes Long Term Evolution; and g-UTRAN, i.e., New Radio (NR).

[0003] A radio access network may include one or more access nodes, such as base station nodes, which facilitate wireless communication or otherwise provide an interface between a wireless terminal and a telecommunications system. Non-limiting examples of base stations, depending on the type of radio access technology, may include Node B (“NB”), Enhanced Node B (“eNB”), Home eNB (“HeNB”), gNB (for New Radio [“NR”] technology systems), or some other similar terms.

[0004] The Third Generation Partnership Project (“3GPP”) is a group of collaborative agreements, such as 3GPP standards, aimed at developing globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents describe certain aspects of radio access networks. The overall architecture of fifth-generation systems (e.g., 5G systems, also known as “NR” or “New Radio,” and “NG” or “Next Generation”) is... Figure 20 As shown in the figure, and also described in 3GPP TS 38.300, the 5G NR network consists of NGRAN (Next Generation Radio Access Network) and 5GC (5G Core Network). As illustrated, NGRAN consists of gNBs (e.g., 5G base stations) and ng-eNBs (i.e., LTE base stations). Xn interfaces exist between gNBs, (gNB)-(ng-eNB), and (ng-eNB)-(ng-eNB). Xn is the network interface between NG-RAN nodes. Xn-U represents the Xn user plane interface, and Xn-C represents the Xn control plane interface. NG interfaces exist between the 5GC and base stations (i.e., gNBs and ng-eNBs). The gNB node provides NR user plane and control plane protocol terminals to the UE and connects to the 5GC via the NG interface. This 5G NR (New Radio) gNB connects to the AMF (Access and Mobility Management Function) and UPF (User Plane Function) in the 5GC (5G Core Network).

[0005] Network slicing is a network architecture used in fifth-generation (5G) cellular systems that enables the reuse of virtualized and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network customized to meet the different requirements of a specific application. Network operators will be able to deploy features / services that support the specific needs of their customers / market segments.

[0006] Network slicing can span multiple parts of a network, such as terminals, radio access networks (RAN), core networks (CN), and transport networks. Depending on processing power, storage, and bandwidth, network slices can include dedicated resources and / or shared resources.

[0007] The 3rd Generation Partnership Project (3GPP) worked to specify the architectural and functional elements necessary to implement basic network slicing functionality in Releases 15 and 16. In Release 17, the plan is to enhance network slicing functionality based on a standardized list of attributes that characterize network slice types. Some of these attributes, such as the radio spectrum supported by the network slice to limit terminals in terms of frequencies to be used, may affect RAN functions and procedures.

[0008] What is needed are methods, apparatuses, and / or techniques for enhancing resource selection in sliced ​​networks. Summary of the Invention

[0009] In one example, a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a designated service within a public land mobile network (PLMN), the wireless terminal includes: a receiver circuit configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each of the one or more PLMN identifiers being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slice for which the cell is prohibited; and a processor circuit configured to: select a serving PLMN; select a desired network slice for serving the PLMN; and determine whether a cell is prohibited based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0010] In one example, an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), includes: processor circuitry configured to generate system information including a list of one or more PLMN identifiers, each of which is associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slice for which the cell is prohibited; and transmitter circuitry configured to transmit the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited.

[0011] In one example, a method for a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), the method comprising: selecting a serving PLMN; selecting a desired network slice for serving the PLMN; receiving system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices to which the cell is prohibited; and determining whether the cell is prohibited for use in the network slice based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0012] In one example, a method for an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), the method comprising: generating system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited; and transmitting the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited. Attached Figure Description

[0013] The foregoing and other objectives, features, and advantages of the technology disclosed herein will become apparent from the more detailed description of the preferred embodiments shown below, as illustrated in the accompanying drawings, in which reference numerals in various views refer to the same parts. The drawings are not necessarily drawn to scale, but rather focus on illustrating the principles of the technology disclosed herein. [ Figure 1 ] Figure 1 This is a schematic diagram of a communication system, showing both the core network and the radio access network. [ Figure 2 ] Figure 2 It is by Figure 1 A diagrammatic view of the operations performed by the system's wireless terminal for resource selection. [ Figure 3 ] Figure 3 An exemplary scenario is shown where a wireless terminal performs a registration process in a sliced ​​network. [ Figure 4 ] Figure 4 This is a schematic diagram illustrating how a general communication system utilizes network slicing technology, and how wireless terminals use network slice frequency band association information to perform resource selection. [ Figure 5 ] Figure 5 This is a diagrammatic view of an exemplary implementation of network slice frequency band association information. [ Figure 6 ] Figure 6 It is shown by Figure 4 A diagrammatic view of representative exemplary steps or actions performed by a wireless terminal of a general communication system. [ Figure 7 ] Figure 7 yes Figure 4 The diagram illustrates a general communication system and further shows various exemplary methods by which wireless terminals can obtain network slice frequency band association information. [ Figure 8A ] Figure 8A This is a schematic diagram of an exemplary communication system in which network slice band association information (NSBAI) is configured at wireless terminal 30. [ Figure 8B ] Figure 8B This is for Figure 8A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system. [ Figure 9A ] Figure 9A This is a schematic diagram of an exemplary communication system in which the network slice band association information (NSBAI) is obtained by the wireless terminal from the system information. [ Figure 9B ] Figure 9B This is for Figure 9AA diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system. [ Figure 10A ] Figure 10A This is a schematic diagram of an exemplary communication system in which the network slice band association information (NSBAI) is obtained by the wireless terminal from the non-access stratum (NAS). [ Figure 10B ] Figure 10B This is for Figure 10A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system. [ Figure 11A ] Figure 11A This is a schematic diagram of an exemplary communication system in which the Network Slice Band Association Information (NSBAI) is obtained by the wireless terminal from Radio Resource Control (RRC) signaling. [ Figure 11B ] Figure 11B This is for Figure 11A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system. [ Figure 12 ] Figure 12 This is a diagrammatic view showing an exemplary format of optional information elements, which shares the same structure as shown as "NSSAI Band Association". [ Figure 13 ] Figure 13 This illustrates the general implementation schemes and modes that can be implemented by a wireless terminal according to the general implementation schemes and modes described herein (including...). Figure 4 , Figures 8A-8B , Figures 9A-9B , Figures 10A-10B and Figures 11A-11B A flowchart of exemplary representative actions or steps performed in the implementation scheme and model. [ Figure 14 ] Figure 14 It shows that it can be determined by the access node according to Figures 11A-11B A flowchart illustrating exemplary representative actions or steps performed in the implementation scheme and pattern. [ Figure 15 ] Figure 15 It demonstrates what can be managed by the core network's management entity based on Figures 10A-10B A flowchart illustrating exemplary representative actions or steps performed in the implementation scheme and pattern. [ Figure 16 ] Figure 16 This is a schematic diagram of an example communication system in which a wireless terminal utilizes network slice cell prohibition information, which is obtained from system information broadcast from the access node in combination with resource selection. [ Figure 17 ] Figure 17 It shows that it can be controlled by a wireless terminal according to Figure 16A flowchart illustrating exemplary representative actions or steps performed in an exemplary implementation scheme and pattern. [ Figure 18 ] Figure 18 It shows that it can be determined by the access node according to Figure 16 A flowchart illustrating exemplary representative actions or steps performed in an exemplary implementation scheme and pattern. [ Figure 19 ] Figure 19 This is a schematic view illustrating exemplary components including electromechanical devices, which may include wireless terminals, radio access nodes, and core network nodes according to exemplary embodiments and patterns. [ Figure 20 ] Figure 20 This is a diagrammatic view of the overall architecture of the new 5G radio system. Detailed Implementation

[0014] In one of its exemplary aspects, the technology disclosed herein relates to a wireless terminal communicating with a management entity of a core network via an access node of a radio access network (RAN). The core network supports one or more network slices, each providing a designated service within a Public Land Mobile Network (PLMN). In exemplary embodiments and modes, the wireless terminal includes receiver circuitry, transmitter circuitry, and processor circuitry. The processor circuitry is configured to select a serving PLMN; select at least one network slice; and initiate a cell selection / reselection process on one or more radio bands based on network slice band association information. The network slice band association information includes a list of network slice identifiers, each identifying a network slice, and each of some network slice identifiers being associated with a corresponding radio band. The one or more radio bands are determined from the corresponding radio bands associated with the network slice identifiers of the at least one network slice. A method of operating such a wireless terminal is also provided.

[0015] In another aspect, the technology disclosed herein relates to an access node of a radio access network (RAN). In exemplary embodiments and modes, the access node includes processor circuitry and transmitter circuitry. The processor circuitry is configured to generate a radio resource control (RRC) message that includes network slice band association information. The transmitter circuitry is configured to transmit the RRC message. The network slice band association information includes a list of network slice identifiers, each identifying a network slice supported by the core network, and each of some network slice identifiers is associated with a corresponding radio band. The network slice band association information is used by a wireless terminal to perform a cell selection / reselection process. Methods for operating such an access node are also provided. In another aspect, the technology disclosed herein relates to a management entity for a core network. The management entity communicates with radio terminals. The core network supports one or more network slices, each providing a designated service within a Public Land Mobile Network (PLMN). In exemplary embodiments and modes, the management entity includes receiver circuitry, transmitter circuitry, and processor circuitry. The receiver circuitry is configured to receive registration request messages from radio terminals. The processor circuitry is configured to generate registration acceptance message information, which includes a list of network slice identifiers, each identifying a network slice, and each of these network slice identifiers being associated with a corresponding radio frequency band. This network slice frequency band association information is used by the radio terminal to perform a cell selection / reselection process. Methods for operating such a management entity are also provided.

[0016] In another aspect, the technology disclosed herein relates to a wireless terminal that communicates with an access node of a radio access network (RAN) supporting one or more network slices. Each network slice provides a designated service within a Public Land Mobile Network (PLMN). In exemplary embodiments and modes, the wireless terminal includes receiver circuitry and processor circuitry. The receiver circuitry is configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information. The network slice cell prohibition information includes one or more network slice identifiers of network slices for which the cell is prohibited. The processor circuitry is configured to select a serving PLMN; select a network slice; and determine whether a cell is prohibited for use in that network slice based on the network slice identifier identifying the network slice and the network slice cell prohibition information associated with the serving PLMN. A method of operating such a wireless terminal is also provided.

[0017] In another aspect, the technology disclosed herein relates to an access node of a radio access network (RAN) that supports one or more network slices, each providing a designated service within a public land mobile network (PLMN). In exemplary embodiments and modes, the access node includes processor circuitry and transmitter circuitry. The processor circuitry is configured to generate system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information. The network slice cell prohibition information includes one or more network slice identifiers of network slices for which the cell is prohibited. The transmitter circuitry is configured to transmit the system information to the cell. A method of operating such an access node is also provided.

[0018] For ease of explanation and not limitation, specific details such as specific architectures, interfaces, and technologies are set forth in the following description to provide a thorough understanding of the technologies disclosed herein. However, it will be apparent to those skilled in the art that the technologies disclosed herein can be implemented in other embodiments different from these specific details. That is, those skilled in the art can conceive of various arrangements, which, although not explicitly described or shown herein, embody the principles of the technologies disclosed herein and are included within their spirit and scope. In some cases, detailed descriptions of well-known devices, circuits, and methods have been omitted to prevent the description of the technologies disclosed herein from becoming obscure due to unnecessary details. All statements herein describing the principles, aspects, and implementations of the technologies disclosed, and their specific examples, are intended to cover their structural and functional equivalents. Furthermore, it is intended that such equivalents include both currently known equivalents and future-developed equivalents, i.e., any elements developed that perform the same function, regardless of their structure.

[0019] Therefore, for example, those skilled in the art will understand that the block diagrams herein can represent conceptual views of exemplary circuits or other functional units embodying technical principles. Similarly, it should be understood that any flowchart, state transition diagram, pseudocode, etc., represents various processes that can be substantially represented in a computer-readable medium and thus executed by a computer or processor, whether or not such computer or processor is explicitly shown. 1.0 Introduction 1.1 Introduction: Network Architecture

[0020] Figure 1 An example telecommunications system 20 is illustrated, which includes one or more radio access networks (RANs) 22 connected to one or more core networks (CNs) 24. Telecommunications system 20 may be utilized by one or more Public Land Mobile Networks (PLMNs). A Public Land Mobile Network (PLMN) is a combination of wireless communication services provided by a specific operator in a specific country. For simplicity, Figure 1 The vertical dashed lines indicate that the Radio Access Network (RAN) 22 and Core Network (CN) 24 can consist of multiple PLMNs (such as PLMN1-PLMN2). j ) Utilization. In the core network (CN)24, each PLMN has its own As used herein, the terms "telecommunications system" or "communication system" can refer to any network of devices used for transmitting information. A non-limiting example of a telecommunications system is a cellular network or other wireless communication system. As used herein, the terms "cellular network" or "cellular radio access network" can refer to a network distributed across cells, each cell being served by at least one location-fixed transceiver such as a base station. A "cell" can be any communication channel specified by a standardization or regulatory body for use in International Mobile Telecommunications Advanced ("IMTA Advanced"). All or part of the cells may be adopted by 3GPP as licensed frequency bands (e.g., frequency bands) to be used for communication between a base station (such as a Node B) and a UE terminal. Cellular networks using licensed frequency bands may include configured cells. Configured cells may include cells that the UE terminal is aware of and permitted by the base station to transmit or receive information. Examples of cellular radio access networks include E-UTRAN and any of its successor networks (e.g., NUTRAN).

[0021] A core network (CN), such as core network (CN) 24, may include numerous servers, routers, and other devices. As used herein, the term "core network" may refer to a device, a group of devices, or a subsystem within a telecommunications network that provides services to users of the telecommunications network. Examples of services provided by the core network include aggregation, authentication, call handover, service invocation, gateways to other networks, etc. For simplicity and for the purposes of the techniques disclosed herein, core network (CN) 24 is shown as including one or more management entities, such as management entities 261-26. j In the exemplary embodiments and any exemplary implementations and patterns described herein, management entity 26 may be an Access and Mobility Management Function (AMF). As described above, each PLMN has one or more management entities 26 in its core network (CN) 24.

[0022] Radio access networks (RANs) (such as the radio access network (RAN) 22 shown) typically include multiple access nodes. Figure 1 An exemplary access node 28 is shown. As used herein, the terms “access node,” “node,” or “base station” can refer to any device or group of devices that facilitates wireless communication or, in other words, provides an interface between a wireless terminal and a telecommunications system. In the 3GPP specification, non-limiting examples of base stations may include Node B (“NB”), Enhanced Node B (“eNB”), Home eNB (“HeNB”), gNB (for New Radio [“NR”] technology systems), or some other similar terms.

[0023] Radio access network (RAN) 22 and its management entity 26 serve radio terminals that also form part of radio access network (RAN) 22. Figure 1An exemplary wireless terminal 30 is shown. As used herein, the term "wireless terminal" can refer to any electronic device used to transmit voice and / or data via telecommunications systems, such as (but not limited to) cellular networks. Other terms used to refer to a wireless terminal and non-limiting examples of such devices may include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, user unit, cellular phone, smartphone, personal digital assistant ("PDA"), laptop computer, tablet computer, netbook, e-reader, wireless modem, etc.

[0024] Wireless terminal 30 communicates via radio or air interface (in...) Figure 1 The radio terminal 30 (shown by dashed line 32) communicates with its serving radio access network (RAN) 22. Communication between the radio access network (RAN) 22 and the radio terminal 30 via radio interface 32 is carried out using "resources". Any use of "resource" herein refers to "radio resource" unless the context clearly indicates otherwise. Generally, as used herein, a radio resource ("resource") is a time-frequency unit that can carry information (e.g., signal information or data information) via a radio interface.

[0025] The example of radio resources occurs in the context of “frames,” typically information formatted and written by nodes. In Long Term Evolution (LTE), frames, which may have one or more downlink portions and one or more uplink portions, are transmitted between a base station and a radio terminal. Each LTE frame may include multiple subframes. For example, in the time domain, a 10ms frame consists of ten one-millisecond subframes. LTE subframes are divided into two time slots (thus making a frame have 20 time slots). The signals transmitted in each time slot are described by a resource grid consisting of resource elements (REs). Each column of the two-dimensional grid represents a symbol (e.g., OFDM symbols on the downlink (DL) from the node to the radio terminal; SC-FDMA symbols in the uplink (UL) frame from the radio terminal to the node). Each row of the grid represents a subcarrier. A resource element (RE) is the smallest hourly frequency unit used for downlink transmission in a subframe. That is, a symbol on a subcarrier in a subframe includes a resource element (RE) uniquely defined by an index pair (k,l) in the time slot (where k and l are the indices in the frequency and time domains, respectively). In other words, a symbol on a subcarrier is a resource element (RE). Each symbol comprises multiple subcarriers in the frequency domain, the exact number depending on the channel bandwidth and configuration. The smallest hourly resource supported by current standards is a collection of multiple subcarriers and multiple symbols (e.g., multiple resource elements (REs)) and is called a resource block (RB). In the case of a canonical cyclic prefix, a resource block may include, for example, 84 resource elements, i.e., 12 subcarriers and 7 symbols. In 5G New Radio (“NR”), a frame consists of a duration of 10 ms. A frame is composed of 10 subframes, each with a duration of 1 ms, similar to LTE. Each subframe consists of 2 μ slots. Each slot can have 14 (normal CP) or 12 (extended CP) OFDM symbols. A slot is a typical unit used for transmission by the scheduling mechanism. NR allows transmission to begin at any OFDM symbol and to continue only the number of symbols required for communication. This is called “micro-slot” transmission. This is advantageous for very low latency used for critical data communication and minimizes interference to other RF links. Micro-slots contribute to achieving lower latency in the 5G NR architecture. Unlike slots, micro-slots are not associated with the frame structure. They facilitate truncating existing frames without waiting for scheduling. See, for example, https: / / www.rfwireless-world.com / 5G / 5G-NR-Mini-Slot.html, which is incorporated herein by reference.

[0026] Radio Access Network (RAN) 22 further transmits through the RAN-CN interface (e.g., the N2 interface) (in Figure 1 (shown by dashed line 34) communicates with one or more core networks (CN) 24.

[0027] Communication protocols between wireless terminals and telecommunications systems are typically classified into Access Layer (AS) and Non-Access Layer (NAS). AS protocols, such as Radio Resource Control (RRC) and Media Access Control (MAC), are used for communication between wireless terminals and access nodes of the RAN, while NAS protocols, such as those specified in 3GPP TS24.501, are used for communication between wireless terminals and entities of the CN (e.g., AMF) via the RAN's access nodes. Therefore, a wireless terminal may include functions for managing AS protocols and another function for managing NAS protocols. In this document, the term "NAS" can be used in some contexts to refer to the functionality built into the wireless terminal for managing NAS protocols. Similarly, "RRC" can be used in some contexts to refer to the functionality built into the wireless terminal for managing RRC protocols. 1.2 Introduction: Typical Resource Selection

[0028] Figure 2This illustrates general actions or steps that can be performed by the radio terminal 30, i.e., the UE, to obtain appropriate resources for communication in a typical specific implementation. As shown in Action 2-1, a radio terminal in an idle state (e.g., RRC_IDLE) or an inactive state (e.g., RRC_INACTIVE) can perform PLMN selection. During the PLMN selection process in Action 2-1, the radio terminal can scan all RF channels according to its capabilities to find an available PLMN. On each carrier, the radio terminal can search for the strongest cell and read its system information (e.g., from SIB1) to determine which PLMN the cell belongs to.

[0029] If a wireless terminal can read one or more PLMN identity identifiers in the strongest cell, it can report each discovered PLMN to the NAS as a high-quality PLMN (but without an RSRP value), provided that a certain high-quality standard is met. The high-quality standard is that, for NR cells, the measured RSRP value should be greater than or equal to -110 dBm.

[0030] PLMNs that do not meet high-quality standards but whose PLMN identity can be read by wireless terminals can be reported to the NAS along with their corresponding RSRP values. The quality metric reported to the NAS can be the same for each PLMN discovered in a cell.

[0031] The PLMN search as shown in Action 2-1 can be stopped upon request from the NAS. The wireless terminal can optimize the PLMN search of Action 2-1 by using stored information (e.g., frequency) and optionally information about cell parameters from previously received measurement control information elements.

[0032] Based on reports of available PLMNs provided by the wireless terminal, the NAS can select the access layer (AS) for PLMNs available for cell selection and cell reselection, or a list of equivalent PLMNs (if available).

[0033] After the PLMN selection process is successfully completed, as follows Figure 2 As shown in Action 2-2, the wireless terminal can continue cell selection to search for suitable cells in the selected PLMN. In one configuration, cell selection can be performed using stored information by one of two possible procedures (initial cell selection procedure and cell selection procedure).

[0034] The initial cell selection process does not require or involves prior knowledge of which RF channels are NR frequencies. During the initial cell selection process, (1) the wireless terminal can scan all RF channels in the NR band to find a suitable cell according to its capabilities; (2) on each frequency, the wireless terminal can search only for the strongest cell; and (3) once a suitable cell is found, it can be selected.

[0035] Using stored information for cell selection may require stored frequency information, and optionally information about cell parameters from previously received measurement control information elements or from previously detected cells. Once the wireless terminal has found a suitable cell, it can select that cell. If no suitable cell is found, the initial cell selection process in a) can be initiated.

[0036] When the cell selection process of Action 2-1 is successful, as Action 2-3, the wireless terminal can select the cell to receive available services and can monitor the control channel of the selected cell (i.e., Action 2-3 shows the wireless terminal pre-occupying the selected cell).

[0037] As Figure 4 Actions 2-4, if necessary, allow the wireless terminal to register its presence in the tracking area of ​​the selected cell using the registration process. As a result of successful location registration, the selected PLMN then becomes the registered PLMN.

[0038] When pre-occupying a selected cell as shown in Action 2-4, if the wireless terminal finds a more suitable cell, it can reselect the more suitable cell and pre-occupy that cell according to the cell reselection criteria (preferably configured by the network via system information), as shown in Action 2-5. This Action 2-5 can be referred to as cell reselection. If the new cell does not belong to at least one tracking area where the wireless terminal is registered, location registration can be performed, as shown in Action 2-6. In the RRC_INACTIVE state, if the new cell does not belong to a configured RAN-based notification area (RNA), an RNA update procedure is performed.

[0039] The wireless terminal can search for higher priority PLMNs at regular time intervals, and if the NAS has already selected another PLMN, it will search for a suitable cell. If the wireless terminal loses coverage of the registered PLMN, it will automatically select a new PLMN (automatic mode), or provide the user with an indication of an available PLMN, allowing for manual selection (manual mode).

[0040] Cell reselection can be performed based on network configuration priorities. The absolute priority of different NR frequencies or inter-RAT (Radio Access Technology) frequencies can be provided to the radio terminal in the system information, either in a connection release message (e.g., an RRC release message) or by inheritance from another RAT during inter-RAT cell (re)selection. For the purposes of the system information, NR frequencies or inter-RAT frequencies can be listed without providing priorities. If priorities are provided in dedicated signaling, the radio terminal can ignore all priorities provided in the system information. 1.3 Introduction: Typical Community Blocking Technology

[0041] Cell prohibition, also known as cell reservation, is a mechanism used by the Radio Access Network (RAN) to prevent radio terminals from pre-emptively occupying a cell. For example, 3GPP TS38.304 specifies the procedures shown in Table 1. Table 1 5.3.1 Community Status and Community Reserved Space The MIB or SIB1 message specified in TS 38.331[3] uses three fields to indicate cell status and cell reservation: -cellBarred(IE type: "Banned" or "Not banned") Indicated in the MIB message. If multiple PLMNs are indicated in SIB1, this field is shared for all PLMNs - cellReservedForOperatorUse (IE type: "Reserved" or "Not Reserved") is indicated in the SIB1 message. If multiple PLMNs are indicated in SIB1, this field is specified for each PLMN. -cellReservedForOtherUse(IE type: "true") This is indicated in the SIB1 message. If multiple PLMNs are indicated in the SIB1, this field is shared by all PLMNs. When the cell status is indicated as "not prohibited" and "not reserved" for operator use, and is not "true" for other purposes, - During the cell selection and cell reselection process, all UEs should treat the cell as a candidate. When the cell status is indicated as "true" for other uses, - The UE should treat the cell as "banned". When the cell status is indicated as "not banned" and "reserved" for use by any PLMN operator and not "true" for other purposes, - If the cellReservedForOperatorUse field of the PLMN is set to "Reserved", then the UE assigned to Access Identity 11 or 15 operating in its HPLMN / EHPLMN should treat the cell as a candidate during the cell selection and reselection process. - If the cell is "reserved for operator use" for registered or selected PLMN, the UEs assigned access identities 1, 2, and 12 through 14 should behave as if the cell status is "banned". Note 1: Access identity identifiers 11 and 15 are only valid for HPLMN / EHPLMN; access identity identifiers 12, 13 and 14 are only valid for the home country, as specified in TS 22.261

[12] . When the cell status is indicated as "banned" or the cell status will be treated as "banned", - The UE is not allowed to select / reselect the cell, or even make emergency calls to it. -The UE should select another cell according to the following rules: - If a cell cannot obtain a MIB, its cell status will be considered "banned": - The UE can exclude banned cells as candidates for cell selection / reselection within a maximum of 300 seconds. If the selection criteria are met, the UE can select another cell on the same frequency. -otherwise: - If a cell cannot obtain SIB1, it will be considered as having a "banned" status: - The UE can exclude banned cells as candidates for cell selection / reselection within a maximum of 300 seconds. - If the intraFreqReselection field in the MIB message is set to "Allow". If the reselection criteria are met, the UE can select another cell on the same frequency. - The UE should exclude banned cells as candidates for cell selection / reselection within 300 seconds. - If the intraFreqReselection field in the MIB message is set to "Disallowed", the UE should not reselect a cell with the same frequency as the prohibited cell; - The UE should exclude banned cells and cells with the same frequency as them as candidates for cell selection / reselection within 300 seconds. Another neighborhood selection may also include changes to the RAT. 1.4 Introduction: Network Slicing Technology

[0042] Network slicing is a concept that allows for differentiated processing, depending on each customer's requirements. Using slicing, a mobile network operator (MNO) can treat customers as belonging to different tenant types, each with different service requirements. These service requirements are managed according to Service Level Agreements (SLAs) and subscriptions, governing the slice type each tenant is eligible for. In some configurations, network slice instances can be defined within a Public Land Mobile Network (PLMN) or a Standalone Non-Public Network (SNPN). 1.4.1 Introduction: General Principles of Network Slicing The following key principles apply to supporting network slicing in the RAN and provide an understanding / explanation of the terminology used in this paper: RAN sensing of slices RAN supports differentiated processing of traffic for different pre-configured network slices. How RAN supports slice enablement (i.e., including a set of network functions for each slice) in terms of RAN functions depends on the specific implementation. Selection of the RAN portion of a network slice - RAN supports selecting the RAN portion of a network slice using Network Slice Selection Assistance Information (NSSAI) provided by the UE or CN. NSSAI explicitly identifies one or more pre-configured network slices in the PLMN / SNPN. Resource management between slices - The RAN should support policy enforcement across slices according to the Service Level Agreement (SLA). A single RAN node should be able to support multiple slices. The RAN should be free to apply optimal Radio Resource Management (RRM) policies to each supported slice to ensure SLA compliance. QoS support -RAN supports QoS differentiation within slices. RAN Selection for CN Entities - For initial connection, the UE can provide NSSAI to support the selection of Access and Mobility Management Functions (AMF). If available, the NG-RAN uses this information to route the initial NAS to an AMF. If the RAN cannot use this information to select an AMF, or if the UE does not provide any such information, the RAN sends NAS signaling to one of the default AMFs. For subsequent access, the UE provides a temporary ID, which is assigned to the UE by the CN, so that the RAN can route non-access stratum (NAS) messages to the appropriate access and mobility management functions (AMFs), provided that the temporary ID is valid (and the RAN knows and can reach the AMF associated with the temporary ID). Otherwise, the method used for initial connection applies. Resource isolation between slices - The RAN supports resource isolation between slices. RAN resource isolation can be achieved using RRM policies and protection mechanisms that should prevent a shortage of shared resources in one slice from disrupting the service level agreement (SLA) of another slice. RAN resources should be able to be fully dedicated to a single slice. How the RAN supports resource isolation depends on the specific implementation. Access control - By leveraging unified access control, operator-defined access categories can be used to differentiate between different slices. The RAN can broadcast prohibition control information (i.e., a list of prohibition parameters associated with operator-defined access categories) to minimize the impact of congested slices. Slice availability Some slices are only available locally within the network. Individual network slice selection assistance information (S-NSSAI) supported by the RAN can be (pre-)configured. RAN awareness of slices supported in its neighboring cells can be beneficial for inter-frequency mobility in connectivity modes. It is assumed that slice availability will not change within the UE's registered area. The RAN and CN are responsible for handling service requests for slices that may or may not be available in a given area. Allowing or denying access to a slice may depend on factors such as slice support, resource availability, and RAN support for the requested service. Support for UEs associated with multiple network slices simultaneously - When a UE is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, the UE always attempts to pre-occupy the best cell. For inter-frequency cell reselection, a dedicated priority can be used to control the frequency pre-occupied by the UE. Granularity of slice perception By indicating the S-NSSAI corresponding to the PDU session in all signaling containing PDU session resource information, slice awareness in the RAN is introduced at the Protocol Data Unit (PDU) session level. This verifies the UE's right to access network slices. -CN is responsible for verifying that the UE has the right to access a network slice. Before receiving the Initial Context Setup Request message, it may allow the RAN to apply some temporary / local policies based on its awareness of the slice the UE is requesting access to. During the Initial Context Setup, the RAN is notified of the slice for which it is requesting resources. 1.4.2: Introduction: Network Slicing and Network Sharing

[0043] It should be noted that network slicing should not be confused with network sharing. Network sharing allows multiple participating operators (e.g., multiple PLMNs) to share the resources of a single shared network according to an agreed allocation scheme. In contrast, as mentioned above, network slices can be defined within a PLMN / SNPN. Therefore, network slices can be configured independently within the network and can coexist with network sharing. 1.4.3: Introduction: Network Slice Recognition Within a PLMN, network slices can be identified by S-NSSAIs, which consist of a slice / service type (SST) and a slice distinguisher (SD). A group of one or more S-NSSAIs is called an NSSAI. NSSAIs can be categorized into one of the following types: • Configured NSSAI: The NSSAI provided in the UE for one or more PLMNs. • Default NSSAI Configuration: The NSSAI configuration is pre-configured by the home PLMN (HPLMN) and is typically determined by all roaming partners, for example, by using SST values ​​standardized by 3GPP or other principals. Each S-NSSAI in the default NSSAI configuration may have a corresponding S-NSSAI as part of the subscribed S-NSSAI. • Requested NSSAI: NSSAI provided by the UE to the service PLMN during registration. • Permitted NSSAI: NSSAI provided by the service PLMN during, for example, the registration process. Indicates the S-NSSAI value that the UE can use in the service PLMN of the current registered area. • Subscribed S-NSSAI: Based on subscriber information, the UE subscribes to this S-NSSAI for use in the PLMN.

[0044] S-NSSAI can have a standard value, meaning it consists only of SSTs with normalized SST values ​​and no SD, or a non-standard value, meaning it consists of both SSTs and SDs, or only SSTs without normalized SST values ​​and no SD. S-NSSAIs with non-standard values ​​are identified as individual network slices within their associated PLMN. In access strata processes within any PLMN other than the PLMN associated with the S-NSSAI, the UE may not use S-NSSAIs with non-standard values.

[0045] The S-NSSAI in a subscribed S-NSSAI (see Clause 5.15.3) may contain only the HPLMN S-NSSAI value. The S-NSSAI in a configured S-NSSAI, allowed S-NSSAI, requested S-NSSAI, and denied S-NSSAI may contain only the value from the service PLMN. The service PLMN can be an HPLMN or a VPLMN.

[0046] NSSAI configuration and NSSAI management between the UE and the network (including the Home PLMN (HPLMN) and the Access PLMN (VPLMN)) can be handled by the Non-Access Stratum (NAS). For example, 3GPP TS24.501 (V15.4.0) specifies the procedures in Table 2. Table 2 4.6 Network Slicing 4.6.1 Overview 5GS supports network slicing as described in 3GPP TS 23.501[8]. Within a PLMN, network slices are identified by S-NSSAI, which consists of a slice / service type (SST) and a slice distinguisher (SD). Including the SD in an S-NSSAI is optional. A group of one or more S-NSSAIs is called an NSSAI. The following NSSAIs are defined in 3GPP TS 23.501[8]: a) Configured NSSAI; b) The requested NSSAI; c) Allowed NSSAI; and d) Subscribed to S-NSSAI; The following NSSAI definitions are used in this document: a) NSSAI for the current PLMN's rejection; and b) NSSAI for rejection in the current registered region. The serving PLMN can configure the UE using the NSSAI configured for each PLMN. Alternatively, the HPLMN can configure the UE using a single default NSSAI, and considers the default NSSAI to be valid in PLMNs where the UE has no configured NSSAI and no allowed NSSAI. The permitted and denied NSSAIs for the current registered area are managed according to the access type, i.e., 3GPP access or non-3GPP access, and apply to the registered area. If the registered area contains TAIs belonging to different PLMNs (equivalent PLMNs), the permitted and denied NSSAIs for the current registered area apply to those PLMNs in that registered area. The NSSAI used for rejection of the current PLMN applies to the entire registered PLMN, where the registered area should only contain TAIs belonging to the registered PLMN. 4.6.2 Mobility Management Aspects 4.6.2.1 Overview When registering with the PLMN, the UE should send a requested NSSAI to the AMF. The requested NSSAI includes one or more S-NSSAIs of the allowed NSSAI or configured NSSAI for the PLMN, and corresponds to the network slice the UE intends to register with, if: a) The UE has an NSSAI configured for the current PLMN; b) The UE has a permitted NSSAI for the current PLMN; or c) The UE does not have a permitted NSSAI for the current PLMN, nor does it have a configured NSSAI for the current PLMN, but instead has a default configured NSSAI. In this case, the UE instructs the AMF to create the requested NSSAI from the default configured NSSAI; If the UE does not have a configured NSSAI, nor a valid allowed NSSAI for the PLMN, and does not have any default configured NSSAI, the UE will not send the requested NSSAI when requesting registration with the PLMN. In roaming scenarios, the UE should also provide a mapped S-NSSAI for the requested NSSAI (if available). The AMF verifies whether the requested NSSAI is allowed based on the subscribed S-NSSAI in the UE subscription and the mapped S-NSSAI optionally provided by the UE, and if allowed, the AMF should provide the UE with the valid NSSAI for the PLMN, and should also provide the UE with the mapped S-NSSAI for the valid NSSAI for the PLMN (if available). The AMF should ensure that no two or more S-NSSAIs of the valid NSSAI are mapped to the same S-NSSAI for the HPLMN. The AMF may also query the NSSF to determine the valid NSSAI for a given registration area, as defined in 3GPPTS 23.501 [8]. The network slice set used for a UE can change at any time the UE registers with the PLMN, and this change can be initiated by the network or the UE. In this case, the allowed NSSAI and associated registration area can change during the registration process. The network may notify the UE of the change in supported network slices to trigger the registration process. Changes to the allowed NSSAI may result in an AMF relocation depending on operator policy. See sub-clause 5.4.4, which describes the general UE configuration update process, for more details. 4.6.2.2 NSSAI Storage If available, the configured NSSAIs should be stored in non-volatile memory in the ME, as specified in Appendix C. Each configured NSSAI stored in the UE is a set of up to 16 S-NSSAIs. Each allowed NSSAI stored in the UE is a set of up to 8 S-NSSAIs and is associated with a PLMN identity and access type. Each configured NSSAI, except for the default configured NSSAIs, and each rejected NSSAI is associated with a PLMN identity. The S-NSSAIs in the rejected NSSAIs for the current registered area are further associated with the registered area where the rejected S-NSSAIs are not available. The S-NSSAIs in the rejected NSSAIs for the current PLMN should be considered rejected for the current PLMN, regardless of the access type. There should be no duplicate PLMN identities in each of the lists of configured NSSAIs, allowed NSSAIs, and rejected NSSAIs for the current PLMN and rejected NSSAIs for the current registered area. The UE stores NSSAI as follows: a) The configured NSSAI should be stored until a new configured NSSAI is received for a given PLMN. The network may provide the UE with a mapping S-NSSAI for the new configured NSSAI, which should also be stored in the UE. When providing the UE with a new configured NSSAI for the PLMN, the UE should: 1) Replace the NSSAI of the new configuration for the PLMN with the NSSAI of any existing configuration for the PLMN; 2) Delete any stored mappings S-NSSAI used for the configured NSSAI, and if available, store the mappings S-NSSAI used for the new configured NSSAI. 3) Delete any stored allowed NSSAIs for this PLMN, and if available, store the mapping S-NSSAI for the allowed NSSAIs if the UE receives a new configured NSSAI for this PLMN and a "Registration Requested" indication in the same configuration update command message, but excluding any new allowed NSSAIs for this PLMN; and 4) Delete any NSSAI used for rejection in the current PLMN, and NSSAI used for rejection in the current registered region. If the UE receives an S-NSSAI associated with a PLMN ID from the network during the PDN connection establishment process in EPS, as specified in 3GPP TS 24.301

[15] , the UE may store the received S-NSSAI in the configured NSSAI of the PLMN identified by the PLMN ID associated with the S-NSSAI (if it is not already stored in the configured NSSAI). When a UE registers in another PLMN, the UE may continue to store the received NSSAI for the PLMN configuration and the associated mapping S-NSSAI (if available). Note 1: The maximum number of NSSAIs and associated mappings S-NSSAIs that need to be stored in the UE for the configuration of PLMNs other than HPLMNs, and how the stored entries are processed, depends on the specific UE implementation. (b) The permitted NSSAI shall be stored until a new permitted NSSAI is received for a given PLMN. The network may provide the UE with a mapping S-NSSAI for the new permitted NSSAI (see sub-clauses 5.5.1.2 and 5.5.1.3), which shall also be stored in the UE. When a new permitted NSSAI for the PLMN is received, the UE shall: 1) Replace the new allowed NSSAI for this PLMN with any stored allowed NSSAI for this PLMN; 2) Delete any stored mappings S-NSSAI used for the allowed NSSAI, and if available, store the mappings S-NSSAI used for the new allowed NSSAI; and 3) Remove the rejected S-NSSAI (if any) from the stored rejected NSSAIs that are included in the new allowed NSSAIs for the current PLMN; If the UE receives a configuration update command message indicating "registration requested" and does not contain any other parameters (see sub-clauses 5.4.4.2 and 5.4.4.3), the UE shall delete any stored permitted NSSAIs for that PLMN and any stored mapping S-NSSAIs for the permitted NSSAIs (if available). Note 2: Whether the UE stores the allowed NSSAI and the mapping S-NSSAI used for the allowed NSSAI when the UE is off depends on the specific implementation. c) When the UE receives an S-NSSAI included in a rejected NSSAI in a registration acceptance message or a configuration update command message, the UE should: 1) Store the S-NSSAI into the rejected NSSAI based on the associated rejection reason; 2) Remove any rejected S-NSSAIs (if any) that are included in the stored allowed NSSAIs for the current PLMN: i) For each access type, the NSSAI used for rejection by the current PLMN; and ii) NSSAI associated with the same access type for rejection in the current registered region; Once a UE is deregistered on all access types, the NSSAI for rejections for the current PLMN should be deleted. Once a UE is deregistered on a specific access type, the NSSAI for rejections for the current registered area corresponding to that access type should be deleted. If a UE moves out of its registered area, the UE should delete any stored NSSAIs for rejections for the current registered area; and d) When the UE receives a Network Slice Indication (IE) in a Registration Acceptance Message or Configuration Update Command Message, and the Network Slice Subscription Change Indicator is set to "Network Slice Subscription Changed," the UE should delete the network slice information for each PLMN (excluding the current PLMN) for which the UE has stored slice information. The UE should not delete the default configured NSSAI. Additionally, the UE should update the network slice information for the current PLMN (if received), as specified above in a), b), and c): 4.6.2.3 Providing NSSAI to lower layers in 5GMM-IDLE mode When a UE in 5GMM-IDLE mode sends an initial NAS message, the UE NAS layer can provide NSSAI (requested NSSAI or allowed NSSAI) to the lower layer. The AMF may indicate the NSSAI inclusion mode via the registration acceptance message NSSAI inclusion mode IE, in which the UE should operate on the current access within the current PLMN (if any) (see sub-clauses 5.5.1.2.4 and 5.5.1.3.4), where the NSSAI inclusion mode is selected from the following NSSAI inclusion modes described in Table 4.6.2.3.1. Table 4.6.2.3.1: NSSAI includes patterns and NSSAI that will be provided to lower layers. The UE should store: a) The NSSAI inclusion mode is indicated by the AMF, if the AMF includes the NSSAI inclusion mode IE in the registration acceptance message; or b) The NSSAI inclusion mode determined by the UE, if the AMF does not include the NSSAI inclusion mode IE in the registration acceptance message; The current PLMN's identity and access type are stored in non-volatile memory within the ME, as described in Appendix C. The UE should apply the NSSAI included in the registration acceptance message to the current PLMN and its equivalent PLMN (if any) within the current registration area for current access. When a UE performs a registration process for a PLMN that is not in the currently registered region, if the UE does not have the NSSAI inclusion mode for that PLMN stored in the non-volatile memory of the ME, the UE should register with a lower layer: a) NSSAI is not provided if the UE performs the registration process via 3GPP access; or b) Provide the requested NSSAI if the UE performs the registration process via a non-3GPP access. When a UE performs a registration process after a system change from S1 mode to N1 mode, if the UE does not store the NSSAI for the PLMN in the non-volatile memory in the ME and the registration process is performed via 3GPP access, the UE should not provide any NSSAI to the lower layer via 3GPP access. 4.6.3 Session Management In order to enable PDU transmission in a network slice, if no PDU session suitable for PDU transmission is established, the UE may request the establishment of a PDU session in the network slice to the data network (DN) associated with the S-NSSAI and the data network name (DNN). The included S-NSSAI is part of the allowed NSSAI of the serving PLMN, which is the S-NSSAI value valid in the serving PLMN, and in roaming scenarios, the mapped S-NSSAI is also included in the PDU session (if available). See sub-clause 6.4.1 for more details. The UE determines whether to establish a new PDU session or use one of the established PDU sessions based on the URSP rules that include the S-NSSAI (if any) (see sub-clause 6.2.9) or based on the UE’s local configuration, as described in sub-clause 4.2.2 of 3GPP TS24.526

[19] . 1.4.4: Introduction: Registration process for sliced ​​networks

[0047] Figure 3An exemplary scenario of a wireless terminal performing a registration process is illustrated. As shown in Action 3-0, the wireless terminal is in the RRC_IDLE state. Action 3-1 shows that the wireless terminal can (triggered by the NAS) send an RRCSetupRequest message to the access node of the cell currently reserved by the wireless terminal. In Action 3-1, the NAS can provide the RRC with a registration request message and an NSSAI, for example, a requested NSSAI. As Action 3-2, the access node can then respond to the RRCSetupRequest message using the RRCSetup message. Upon receiving the RRCSetup message, as in Action 3-3, the wireless terminal can send an RRCSetupComplete message, which may include the provided NSSAI and the registration request message. The access node can use the NSSAI received in the RRCSetupComplete message to select a management entity (e.g., AMF). As Action 3-4, the access node can then transparently forward the registration request message to the selected management entity. After the wireless terminal, access node, and management entity perform the security process (as shown in Action 3-5), the management entity can respond to the registration request message using the registration acceptance message, as shown in Action 3-6.

[0048] In some configurations, the registration request message piggybacked on the RRCSetupComplete message (see Action 3-3) may also include an NSSAI, such as a requested NSSAI, which can be used by the management entity and other core network entities to determine the permitted NSSAIs for the radio terminal. The permitted NSSAIs may be included in the registration acceptance message. Table 3 shows an exemplary format of the RRCSetupComplete message, where the information element s-NSSAI-List carries the NSSAI (e.g., the requested NSSAI). Table 4 shows an exemplary format of the registration request message for Action 3-4. Table 5 shows an exemplary format of the registration acceptance message. The AMF may include rejected NSSAIs to notify the radio terminal of S-NSSAIs included in the requested NSSAIs in the registration request message but rejected by the network. Additionally, if the network needs to provide the radio terminal with a new configuration NSSAI for the current PLMN, the AMF may also include a configured NSSAI. Table 3 Table 4 NSSAI Information Elements Network Slicing Instructions S-NSSAI Information Elements Table 5 2.0 Cell (Re)selection for Network Slicing

[0049] In some configurations or situations, network operators are expected to specify one or more radio spectra (e.g., frequencies, radio bands) for network slices. For example, a network slice used for Ultra Reliable Low Latency Communication (URLLC) may be provided by one or more specific radio frequency services. To this end, the GSM Association has published document NG.116, "General Network Slice Templates," which includes templates for specifying one or more radio spectra to be supported by network slices, as shown in Table 6. Table 6

[0050] The various exemplary implementations and patterns described herein relate to methods and processes by which a UE / network performs / controls cell selection under radio spectrum constraints for network slices. Figure 4 A general communication system 20(4) utilizing network slicing technology is illustrated, wherein, according to one or more aspects of the techniques disclosed herein, a wireless terminal performs resource selection using network slice frequency band association information. Similar to... Figure 1 Communication system 20, Figure 4 The communication system 20(4) includes one or more radio access networks (RAN) 22 and one or more core networks (CN) 24. Similarly, Figure 4 The core network (CN) 24 is shown as including one or more management entities 26, 26', ... . Management entity 26 may be, for example, an Access and Mobility Management Function (AMF). The radio access network (RAN) 22 is shown as including one or more access nodes 28, 28', ... Although not shown as such, Figure 3 The communication system 20(4) can and is typically utilized by multiple PLMNs.

[0051] In the general communication system 20(4) and other exemplary embodiments and modes covered therein, the wireless terminal 30 communicates with the management entity of the core network via an access node of a radio access network (RAN). This core network supports one or more network slices, each providing a designated service within a public land mobile network (PLMN).

[0052] Since the communication system 20(4) is general to the various other exemplary embodiments and modes described herein, it is mentioned again that wireless terminals can take the various forms described above, and similarly, access nodes can be implemented in many different ways. For example, in addition to the foregoing notes regarding access nodes, it should be mentioned that in any of the exemplary embodiments and modes described herein, the source and destination of the radio access network (RAN) 22 can be interconnected through multiple nodes. In such networks, the source and destination may not be able to communicate directly with each other because the distance between the source and destination is greater than the transmission range of the nodes. That is, intermediate nodes are needed to relay communication and provide information transmission. Therefore, intermediate nodes can be used to relay information signals in a relay network with a network topology in which the source and destination are interconnected through such intermediate nodes. In a hierarchical telecommunications network, the backhaul portion of the network may include intermediate links between the core network of the entire hierarchical network and smaller subnetworks. Integrated Access and Backhaul (IAB) Next-Generation NodeBs use new 5G radio communications, such as sending and receiving NR user plane (U plane) data traffic and NR control plane (C plane) data. Therefore, the radio access network (RAN) 22 may include or represent one or more IAB nodes, including IAB carrier nodes that can provide the UE with an interface to the core network and radio backhaul functionality to other IAB nodes.

[0053] Furthermore, the general communication system 20(4) and any other communication system described herein may be implemented in virtualized and / or distributed and / or logical form. For example, any access node used as a carrier node to connect to the core network may include at least one central unit (CU) and at least one distributed unit (DU). The CU is a logical entity that manages the DUs juxtaposed in the IAB carrier and the remote DUs residing in the IAB node. The CU may also be an interface to the core network, manifested as a RAN base station (e.g., an eNB or gNB). In some implementations, the DU is a logical entity that hosts radio interfaces (backhaul / access) for other sub-IAB nodes and / or UEs. In one configuration, under the control of the CU, the DU may provide physical layer and layer 2 (L2) protocols (e.g., Media Access Control (MAC), Radio Link Control (RLC), etc.), while the CU may manage upper-layer protocols (such as Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), etc.). Access nodes that are not carrier nodes (e.g., IAB nodes) may include DU and mobile terminal (MT) functions, wherein in some embodiments, the DU may have the same functions as the DU in the IAB carrier, and the MT may be a UE-like function terminating the radio interface layer. For example, the MT may be used to perform at least one of the following: radio transmission and reception, encoding and decoding, error detection and correction, signaling, and access to the SIM.

[0054] In this document, the term "band" is used to define a set of one or more frequency domain intervals. For Frequency Division Duplex (FDD), a band may comprise a pair of separate intervals for uplink and downlink transmissions, respectively, while for Time Division Duplex (TDD), a band may comprise a single interval shared by the uplink and downlink. A band may represent a radio spectrum or spectrum band represented by letters and / or numbers, such as n1, n77, and n38 in Table 6. Although it should be understood that throughout this invention, the term "band" may be replaced by any other form of interval such as a radio channel with a channel number (e.g., Absolute Radio Channel Number ARFCN), or by the bandwidth portion (BWP) of a radio band.

[0055] Figure 4 Simply using a vertical double-dotted line to illustrate that the communication system 20(3) can utilize network slicing technology. For Figure 4 In general implementations and other exemplary implementations and modes described herein, wireless terminal 30 may be configured with Network Slice Band Association Information (NSBAI) to instruct wireless terminal 30 how to select frequency bands supported by the network slice of interest. The Network Slice Band Association Information may include one or more S-NSSAIs, wherein each S-NSSAI may be associated with one or more supported frequency bands. Figure 5An exemplary implementation of network slice band association information is shown, wherein each entry of S-NSSAI is associated with a list of supported bands. An S-NSSAI not associated with any supported band (e.g., SST=7) may indicate that the S-NSSAI is not limited to a specific band.

[0056] Figure 4 The general exemplary implementation and pattern show that the wireless terminal 30 includes a terminal resource selector 40 for use in a sliced ​​network. As described above, the wireless terminal utilizes network slice frequency band association information to perform resource selection. Therefore, Figure 4 The terminal resource selector 40 is shown to have access to network slice band association information 42, which is abbreviated as NSBAI for convenience. The network slice band association information (NSBAI) 42 may be stored in memory or memory circuitry.

[0057] For reference Figure 5 As understood, network slice frequency band association information includes a list of network slice identifiers, where the network slice identifiers are in... Figure 5 The diagram shows S-NSSAI. Each network slice identifier identifies a network slice, and at least some of these network slice identifiers are associated with a corresponding radio frequency band, such as... Figure 5 As indicated by the right-pointing arrow in the diagram. The one or more radio bands are determined from the corresponding radio bands associated with the network slice identifier of the at least one network slice.

[0058] Figure 6 Representative exemplary steps or actions performed by a wireless terminal 30 of the general communication system 20(4) are shown. Action 6-1 includes selecting a serving PLMN. Action 6-2 includes selecting at least one network slice. Action 6-3 includes initiating a cell selection / reselection process on one or more radio bands based on network slice band association information.

[0059] Figure 7 Various exemplary methods by which the wireless terminal 30 can obtain network slice frequency band association information 42 are illustrated in simplified diagram form. Figure 8A and Figure 8B In the illustrated exemplary implementation and pattern, Network Slice Band Association Information (NSBAI) 42 is configured at the wireless terminal 30. Figure 9A and Figure 9B In the illustrated exemplary implementations and modes, Network Slice Band Association Information (NSBAI) 42 is provided to the wireless terminal 30 by System Information (SI). Figure 10A and Figure 10BIn the illustrated exemplary implementations and patterns, Network Slice Band Association Information (NSBAI) 42 is provided to the wireless terminal 30 by the Non-Access Stratum (NAS). Figure 11A and Figure 11B In the exemplary implementations and patterns depicted, Network Slice Band Association Information (NSBAI) 42 is provided to the wireless terminal 30 by Radio Resource Control (RRC) signaling. 2.1 Configured NSBAI

[0060] Figure 8A An exemplary communication system 20(8) is shown in more detail, wherein network slice band association information (NSBAI) 42 is configured at the wireless terminal 30. Figure 8B It shows as Figure 8B Exemplary representative actions or steps performed by the resource selection of the communication system 20(6).

[0061] Figure 8A The wireless terminal 30 is shown to include a terminal processor circuitry 50 and a terminal transceiver circuitry 52. ​​The terminal processor circuitry 50 may be implemented as or include one or more processors and at least one memory. The memory includes computer program code, wherein the memory and the computer program code are configured to work in conjunction with the at least one processor to cause a decoding device to perform at least the operations described herein.

[0062] The transceiver circuit 52 may then include a terminal transmitter circuit 54 and a terminal receiver circuit 56. The transceiver circuit 52 includes an antenna for wireless transmission. The transmitter circuit 54 may include, for example, an amplifier, modulation circuitry, and other conventional transmitting equipment. The receiver circuit 56 may include, for example, an amplifier, demodulation circuitry, and other conventional receiver equipment. Figure 8A The wireless terminal 30 is further shown to include a terminal interface 58. Such a user interface can be used for user input and output operations and may include, for example, a screen such as a touchscreen that can display information to the user and receive user input. For example, interface 58 may also include other types of devices, such as speakers, microphones, or haptic feedback devices.

[0063] Figure 8A The terminal processor circuitry 50 is shown as including a terminal resource selector 40. In addition to Network Slice Band Association Information (NSBAI) 42, the terminal resource selector 40 includes a PLMN selector 60; a network slice selector 62; and a cell selector 64 using the Network Slice Band Association Information (NSBAI) 42. Furthermore, the terminal processor circuitry 50 may include a frame / message generator / processor 66, and many other functions not shown, including those not strictly related to the techniques disclosed herein.

[0064] The access node 28 of the communication system 20(6) includes node processor circuitry 70; node transceiver circuitry 72; and an interface 74 leading to the core network (CN) 24. The node processor circuitry 70 may be implemented as or include one or more processors and at least one memory. The memory includes computer program code, wherein the memory and the computer program code are configured to work in conjunction with the at least one processor to cause the decoding device to perform at least the operations described herein.

[0065] The node transceiver circuit 72 may include a node transmitter circuit 76 and a node receiver circuit 78. The transceiver circuit 72 includes an antenna for wireless transmission. The transmitter circuit 76 may include, for example, an amplifier, modulation circuitry, and other conventional transmitting equipment. The receiver circuit 78 may include, for example, an amplifier, demodulation circuitry, and other conventional receiver equipment. As described above, various aspects of the access node 28, including the node transceiver circuit 72, may be implemented by a distributed unit (DU) and a mobile terminal unit (MT).

[0066] The management entity 26 of the communication system 20(8) may include a core network entity processor circuit 70 and an interface 82 toward the radio access network (RAN) 22. The core network entity processor circuit 70 may be implemented as or include one or more processors and at least one memory. The memory includes computer program code, wherein the memory and the computer program code are configured to work with the at least one processor to cause the decoding device to perform at least the operations described herein.

[0067] exist Figure 8A In one exemplary implementation of the scheme, network slice band association information (NSBAI) can be pre-configured to the wireless terminal 30. The NSBAI 42 is preferably pre-configured to the wireless terminal 30 by the home PLMN (HPLMN). In some deployment scenarios, the NSBAI can be shared by the HPLMN and roaming partners (e.g., VPLMNs). In this case, the S-NSSAI in the NSBAI can be considered to be derived from or derived from the default NSBAI with a normalized SST value. In other cases, the NSBAI is configured per PLMN; that is, separate NSBAI can be configured for a specific PLMN, HPLMN, or VPLMN. In this case, the NSBAI may include S-NSSAI with normalized and / or non-normalized SST values.

[0068] Figure 8BExemplary representative actions or steps performed by the wireless terminal 30 of the communication system 20 (8) are shown. Action 8B-1 shows the wireless terminal 30 performing a PLMN selection process. After performing the PLMN selection process to select a PLMN, as action 8B-2, the wireless terminal 30 may select the desired network slice. Based on the desired network slice selected in action 8B-2, as action 8B-3, the wireless terminal 30 may perform a cell selection process only on the frequency band associated with the selected network slice, or perform a cell selection process by prioritizing these frequency bands. For example, suppose the wireless terminal 30 selects... Figure 5 The S-NSSAI with an SST value of 2 is selected, instructing the wireless terminal 30 to search for cells in frequency bands n7 and n8. Action 8B-4 includes the wireless terminal 30 checking to determine whether a suitable cell has been successfully found in either frequency band. If the wireless terminal 30 successfully finds a suitable cell in either frequency band, then as action 8B-5, the wireless terminal 30 may continue to perform the aforementioned registration process using the requested NSSAI, including the selected S-NSSAI (with SST=2). If the wireless terminal 30 fails to find a suitable cell in these frequency bands, then as action 8B-6, the wireless terminal 30 may search other frequency bands, or may select a different S-NSSAI (such as the S-NSSAI with SST=5 associated with n11 and n41). 2.2 NSBAI obtained from system information

[0069] Figure 9A This is a schematic diagram of an exemplary communication system 20(9) in which the network slice band association information (NSBAI) is obtained by the wireless terminal from the system information. Figure 9B This is for Figure 9A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system.

[0070] Figure 9A The communication system 20(9) has the same or substantially the same structure and function as one or more of the exemplary embodiments described above, and may no longer be referred to by reference. Figure 9A Discussion. For example, Figure 9A Many structures of the wireless terminal 30 are similar to those of the aforementioned exemplary embodiments. Given that in Figure 9A In an exemplary implementation, the wireless terminal 30 receives its Network Slice Band Association Information (NSBAI) 42 from system information. Figure 9AAccess node 28 is further illustrated as including a system information generator 90 configured to generate system information, such as system information blocks (SIBs) for cells served by access node 28. System information generator 90 includes a unit or function referred to herein as node NSBAI controller 92, which controls the formatting or inclusion of network slice band association information (NSBAI) 42 in the system information generated by system information generator 90. In some exemplary modes, implementations, or scenarios, NSBAI may be generated by the access node based on (pre)configuration from a management entity. For example, NSBAI may be generated by node NSBAI controller 92 based on (pre)configuration from a management entity. In other exemplary modes, implementations, or scenarios, NSBAI may be generated by a management entity and provided to the access node, for example, to node NSBAI controller 92, such that node NSBAI controller 92 may include NSBAI in the system information. System information generator 90 and its node NSBAI controller 92 preferably constitute or are included in node processor circuitry 70 of access node 28. Figure 9A The node processor circuitry 70 of access node 28 is further shown to typically also include a frame / message handler / generator 94, which can be used to format system information during transmission of access node 28. Figure 9A Arrow 96 indicates Figure 9A The wireless terminal 30 receives the network slice frequency band association information in its memory (NSBAI) 42 (9).

[0071] exist Figure 9A In exemplary implementations and patterns, network slice frequency band association information can be broadcast in system information, such as in one or more System Information Blocks (SIBs). Figure 9A In the implementation schemes and modes, the network slice frequency band association information can be specific, such as (1) valid within the serving PLMN, (2) valid within the registration area of ​​the serving PLMN, or (3) valid within the cell served by the access node (e.g., the cell served by the access node). In exemplary implementation schemes and modes, as explained above, network entities (e.g., AMF 26) can utilize available network slices and supported frequency band information to (pre-)configure access nodes.

[0072] Figure 9B It shows that it can be made by Figure 9AThe exemplary actions or steps performed by the communication system 20(9). Action 9B-1 shows the wireless terminal 30 performing a PLMN selection process; Action 9B-2 includes the wireless terminal 30 performing a cell selection process as disclosed above. Action 9B-3 includes the wireless terminal 30 obtaining a system information message from the selected cell. Action 9B-4 includes the wireless terminal 30 obtaining network slice frequency band association information from the system information.

[0073] A cell that provides network slice band association information through system information may advertise more than one PLMN. For example, SIB1 may indicate multiple PLMNs. In this case, the SIB including network slice band association information may additionally include information indicating the PLMN to which the network slice band association information can be applied. Preferably, the system information may include multiple instances of network slice band association information, each instance applied to one or more designated PLMNs.

[0074] For example, Table 7 shows an exemplary format of SIB1, which includes a NetworkSliceBandAssociationInfoList for each PLMN, and the NetworkSliceBandAssociationInfoList also includes a list of S-NSSAIs and an associated frequency band (frequencyBandList) for each S-NSSAI. Table 7

[0075] Upon receiving system information messages, as action 9B-5, the wireless terminal 30 may determine whether the network slice frequency band association information indicates that the selected network slice supports the frequency band of the serving cell. If the result of action 9B-5 is affirmative, then as action 9B-6, the wireless terminal 30 may remain on the serving cell. Furthermore, as action 9B-7, the wireless terminal 30 may continue to perform the registration process using the requested NSSAI (including S-NSSAI supported on that frequency band). As further shown in action 9B-8, the wireless terminal 30 may further perform a cell reselection process on cells in the same frequency band. If the determination of action 9B-5 is negative, for example, if the system information indicates that network slices are not supported in the frequency band of the serving cell, then as action 9B-9, the wireless terminal 30 may perform cell reselection to find other inter-band adjacent cells, or may attempt to select other network slices. It should be noted that the S-NSSAI in the network slice band association information provided via system information can be specific to the serving PLMN. That is, non-normalized SST values ​​can be used. Meanwhile, the S-NSSAI of interest for the wireless terminal 30 can be based on a list of S-NSSAIs, such as subscribed S-NSSAIs or the default NSSAI configured by the HPLMN. The following illustrates alternative conditions under which the S-NSSAI remains valid (e.g., identifiable) within the serving PLMN: • A service PLMN is an HPLMN, or one of the equivalent PLMNs of HPLMN; • S-NSSAI includes the standardized SST value; or • The S-NSSAI has been configured by the serving PLMN through the registration process (the registration process may have provided the wireless terminal with a mapping of the S-NSSAI to the corresponding S-NSSAI in the serving PLMN).

[0076] Otherwise, the wireless terminal 30 might not know which entry in the network slice frequency band association information maps to the S-NSSAI of interest. In this case, after receiving system information and before performing cell reselection, the wireless terminal 30 may perform a registration process, where the registration acceptance message may include a mapping from the serving PLMN S-NSSAI to the HPLMN S-NSSAI. Using this mapping, the wireless terminal 30 can determine whether the selected S-NSSAI supports the frequency band of the serving cell. If it does, the wireless terminal can remain on that cell and / or perform cell reselection on the same frequency band. Otherwise, the wireless terminal can perform cell reselection to find other inter-band adjacent cells, or it can try to select other network slices. 2.3 NSBAI obtained from the non-access layer

[0077] Figure 10A This is a schematic diagram of an exemplary communication system 20 (10) in which network slice band association information (NSBAI) is obtained by a wireless terminal from a non-access stratum (NAS) (e.g., in a NAS message). Figure 10B This is for Figure 10A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system.

[0078] Figure 10A The communication system 20(10) shares the same reference numerals with the common or substantially identical structures and functions as one or more of the exemplary embodiments described above. For example, Figure 10A Many structures of the wireless terminal 30 are similar to the aforementioned exemplary embodiments.

[0079] Given in Figure 10AIn an exemplary implementation, wireless terminal 30 receives its Network Slice Band Association Information (NSBAI) 42 from the Non-Access Stratum (NAS). Figure 10A The management entity 26 is further illustrated as including a Non-Access Stratum (NAS) unit 120, which includes a unit or function referred to herein as the core NSBAI controller 122, which controls or includes the formatting of Network Slice Band Association Information (NSBAI) 42 in the Non-Access Stratum information generated by the NAS unit 120. The NAS unit 120 and its core NSBAI controller 122 preferably constitute or are included in the node processor circuitry 70 of the management entity 26. Figure 10A Arrow 126 shows Figure 10A The wireless terminal 30 receives the network slice frequency band association information in its memory (NSBAI) 42 (10).

[0080] As Figure 10A An exemplary implementation of the scheme and pattern, based on the Network Slice Band Association Information (NSBAI) provided in the non-access stratum message, can provide the network slice band association information during the registration process, preferably in the registration acceptance message. In this exemplary specific implementation, such as Figure 10B As shown in action 10B-1, the wireless terminal 30 can perform PLMN selection, and then, as action 10B-2, perform cell selection, for example, using the conventional cell selection described above which has no frequency / band restrictions in terms of network slicing. As action 10B-3, the wireless terminal 30 sends a registration request message to the management entity 26 through the access node 28. The registration request message may include the selected S-NSSAI as at least part of the requested NSSAI. In response to the registration request message, as action 10B-4, the wireless terminal 30 receives a registration acceptance message. In the registration acceptance message, each S-NSSAI in the allowed NSSAI and / or configured NSSAI information elements may be associated with a supported frequency band. The network slice band association information (NSBAI) received in the registration acceptance message is stored in the network slice band association information (NSBAI) memory 42 (10) of the wireless terminal 30.

[0081] As an exemplary implementation of network slice band association information, a NAS message (e.g., a registration acceptance message) may include optional information elements, such as an "Allowed NSSAI Band Association" information element for allowed NSSAI, and / or may include another optional "Configured NSSAI Band Association" information element for configured NSSAI. Figure 12An exemplary format for this optional information element is shown, which shares the same structure as the one shown as "NSSAI Band Association". In this document, each S-NSSAI value in the NSSAI information element is associated with an entry in the NSSAI Band Association information element in the order of the S-NSSAI fields, where each entry includes one or more bands. If a particular S-NSSAI does not have a band association, the length of the corresponding association x field in the NSSAI Band Association information element can be set to zero.

[0082] exist Figure 10B In a specific implementation scenario, upon receiving the registration acceptance message in action 10B-4, the radio terminal 30 may remain on the current serving cell, as indicated in action 10B-6, and / or if, as determined in action 10B-5, at least one S-NSSAI of the NSSAI requested by the registration acceptance message is permitted on that frequency band, then cell reselection is performed on the same frequency band of the current serving cell, as indicated in action 10B-7. Otherwise, as in action 10B-8, the UE may initiate cell reselection to one of the frequency bands suggested by the registration acceptance message, or may attempt to select another network slice.

[0083] For example, suppose wireless terminal 30 needs a network slice with S-NSSAI = (SST:1, SD:n / a) and is currently camped on a cell in frequency band n7. Wireless terminal 30 can initiate a registration process on that cell by sending a registration request message, which may include the requested NSSAI set to S-NSSAI. If the registration acceptance message includes an allowed NSSAI with S-NSSAI (or a service PLMN-specific S-NSSAI mapped from the S-NSSAI), and if the corresponding entry in the allowed NSSAI frequency band association includes n7, then wireless terminal 30 may consider S-NSSAI supported in n7 and may not initiate cell reselection. On the other hand, if the corresponding entry does not include n7 but includes n8, then wireless terminal 30 may initiate cell reselection to find a cell on n8. 2.3 NSBAI obtained from RRC signaling

[0084] Figure 11A This is a schematic diagram of an exemplary communication system 20(11) in which the network slice band association information (NSBAI) is obtained by the wireless terminal from radio resource control (RRC) signaling. Figure 11B This is for Figure 11A A diagrammatic view of exemplary representative actions or steps performed by resource selection in a communication system.

[0085] Figure 11AThe communication system 20(11) has the same or substantially the same structure and function as one or more of the exemplary embodiments described above, and may no longer be referred to by reference. Figure 11A Discussion. For example, Figure 11A Many structures of the wireless terminal 30 are similar to those of the aforementioned exemplary embodiments. Given that in Figure 11A In an exemplary implementation, the wireless terminal 30 receives its Network Slice Band Association Information (NSBAI) 42 from the RRC signaling received from the access node 28. Figure 11A Access node 28 is further illustrated as including a Radio Resource Control (RRC) unit 130 configured to generate RRC signals for transmission to wireless terminal 30 and to process RRC signals received from wireless terminal 30. The RRC unit 130 includes a unit or function referred to herein as node NSBAI controller 132, which controls the formatting or inclusion of Network Slice Band Association Information (NSBAI) 42 in the RRC signals generated by the system RRC unit 130. In some exemplary modes, implementations, or scenarios, the NSBAI may be generated by the access node based on (pre)configuration from a management entity. For example, the NSBAI may be generated by node NSBAI controller 132 based on (pre)configuration from a management entity. In other exemplary modes, implementations, or scenarios, the NSBAI may be generated by a management entity and provided to the access node, for example, to node NSBAI controller 132, such that node NSBAI controller 132 may include the NSBAI in the RRC signals or messages. Radio Resource Control (RRC) unit 130 and its node NSBAI controller 132 preferably constitute or are included in the core node processor circuit 70 of access node 28. Figure 11A Arrow 136 shows Figure 11A The wireless terminal 30 receives the network slice frequency band association information in its memory (NSBAI) 42 (11).

[0086] exist Figure 11A In exemplary implementations and patterns, network slice band association information may be provided by dedicated RRC signaling during the RRC_CONNECTED state, such as RRCReconfiguration messages and / or RRCLease messages. Figure 11B It shows that it can be used Figure 11AThe exemplary actions performed in the communication system 20(11) are as follows: Action 11B-1 shows the wireless terminal 30 entering the RRC_CONNECTED state. Action 11B-2 shows the wireless terminal 30 receiving RRC signaling, such as the RRCReconfiguration message. Action 11B-3 depicts the wireless terminal 30 obtaining Network Slice Band Association Information (NSBAI) from the RRC signaling for its use. Action 11B-4 shows that the wireless terminal 30 can enter the RRC_IDLE or RRC_INACTIVE state. Action 11B-5 further shows that the wireless terminal 30 can perform cell reselection based on the Network Slice Band Association Information. 2.4 NSBAI Precautions

[0087] Regarding the exemplary implementations and patterns disclosed above, such as Figure 8A , Figure 9A , Figure 10A and Figure 11A If the network slice frequency band association information does not list the S-NSSAI of interest, or if it lists the S-NSSAI of interest that does not have frequency band association, then the network slice identified by the S-NSSAI can be considered to be not limited to a specific frequency band.

[0088] Furthermore, as an alternative implementation of any of the foregoing exemplary embodiments and patterns, network slice band association information may include entries with S-NSSAI and one or more associated bands that are not supported by that S-NSSAI, i.e., a blacklist. A network slice identified by S-NSSAI may be considered supported in any available band, except for those one or more associated bands.

[0089] Figure 13 It shows that it can be made by Figure 4 The exemplary representative steps or actions performed by a general-purpose wireless terminal, such as a UE. The general-purpose wireless terminal 30 covers and is capable of operating according to any of the foregoing exemplary embodiments and modes, including... Figures 8A-8B , Figures 9A-9B , Figures 10A-10B and Figures 11A-11B Action 13-1 includes selecting a PLMN. Action 13-2 includes selecting the network slice the radio terminal wishes to use based on the PLMN. Action 13-3 includes initiating cell selection / reselection based on network slice frequency band association information. Network slice frequency band association information (NSBAI) 42 can be pre-configured to the radio terminal (e.g., ...). Figures 8A-8B In the case of (e.g., in the RRC message), it is provided, for example in a system information message (such as...). Figures 9A-9B (in cases) or dedicated RRC messages (such as Figures 11A-11B Provided in the case of ), or provided in the NAS message (such as Figures 10A-10B (The situation is as described above). Examples of RRC messages include reconfiguration messages, release messages, or any other RRC message. An example of a NAS message is a registration accept message.

[0090] Figure 14 This shows that it can be determined by access node 28 according to Figures 9A-9B or Figures 11A-11B This describes exemplary representative steps or actions performed in exemplary implementations and modes. Access node 28 may be, for example, a gNB. Action 14-1 includes generating an RRC message that includes network slice band association information. This RRC message may be a system information message, a reconfiguration message, a release message, or any other RRC message. The network slice band association information may include a list of network slice identifiers, each identifying a network slice, and each of some network slice identifiers being associated with a corresponding radio band. The network slice band association information may be used by the radio terminal to perform a cell selection / reselection process. Action 4B-2 includes transmitting the RRC message and its network slice band association information (NSBAI) to the radio terminal 30.

[0091] Figure 15 This demonstrates the management entities that can be managed by the core network (such as...) Figures 10A-10B The exemplary implementation and pattern of the management entity 26) includes exemplary representative steps or actions performed. As described above, the management entity 26 may be an Access and Mobility Management Function (AMF). Action 15-1 includes receiving a non-access stratum message from the radio terminal 30. The non-access stratum message may be, for example, a registration request message. Action 15-2 includes generating a responsive non-access stratum message, such as a registration acceptance message, which includes network slice band association information. The network slice band association information may include a list of network slice identifiers, each identifying a network slice, and each of some network slice identifiers being associated with a corresponding radio band. Action 15-3 includes transmitting a responsive non-access stratum message (e.g., a registration acceptance message) to the radio terminal 30. The network slice band association information included in the non-access stratum signaling of the registration acceptance message can be used by the radio terminal to perform a cell selection / reselection process. 3.0 Cell Restriction (Cell Reservation) for Network Slicing

[0092] In some exemplary implementations and patterns, such as in Figure 16 In exemplary implementations and patterns, it may be desirable to limit the pre-occupancy of certain cells to enable wireless terminals to support specific network slices. For example, a network operator may not want to use some cells for network slices designated for specific purposes, such as V2X (Vehicle-to-Everything). Figure 16 Exemplary implementation schemes and patterns configured to implement cell blocking for one or more network slices within a cell are shown. Figure 16Exemplary implementation schemes and patterns are Figure 4 and Figure 5 Exemplary specific implementations of general exemplary implementation schemes and patterns, and Figure 4 and Figure 5 Such explanations also apply to Figure 16 The communication system 20(16). For example, Figure 16 The communication system 20 (16) includes one or more radio access networks (RAN) 22 and one or more core networks (CN) 24, wherein a management entity 26 is shown by way of example in the core network (CN) 24, and an access node 28 is shown by way of example in the radio access network (RAN) 22. Although not shown as such, Figure 16 The communication system 20(16) can and is typically utilized by multiple PLMNs. Figure 16 In this configuration, the wireless terminal 30 communicates with the management entity of the core network through an access node in the radio access network (RAN). This core network supports one or more network slices, each providing a designated service within a Public Land Mobile Network (PLMN).

[0093] Since the communication system 20(4) is general to the various other exemplary embodiments and modes described herein, it is mentioned again that wireless terminals may take the various forms described above, and similarly, access nodes may be implemented in many different ways. For example, in addition to the foregoing notes regarding access nodes, it should be noted that in any of the exemplary embodiments and modes described herein, the source and destination of the radio access network (RAN) 22 may be interconnected through multiple nodes. Furthermore, the communication system 20(16) may be implemented in a virtualized and / or distributed and / or logical form.

[0094] Figure 16 The communication system 20(16) shares the same reference numerals with the structures and functions common to or substantially the same as those in one or more of the foregoing exemplary embodiments. For example, Figure 16 Many structures of the wireless terminal 30 and Figure 16 The structure of access node 28 is similar to that of the aforementioned exemplary implementation. However, in Figure 16 In an exemplary implementation, access node 28 generates system information, which includes a list of one or more PLMN identifiers and an association between each PLMN identifier and corresponding network slice cell prohibition information. This network slice cell prohibition information includes one or more network slice identifiers for network slices whose cells are prohibited. Therefore, in Figure 16In exemplary embodiments and modes, node processor circuitry 70 is shown to include a system information generator 140, which has access to a list 142 of one or more PLMN identifiers and access to the association of each PLMN identifier with corresponding network slice cell prohibition information 142, such that system information generated by system information generator 140 includes both list 142 and associated corresponding network slice cell prohibition information 144. Access node 28 also includes node transmitter circuitry 76, which transmits system information to the cell. Figure 16 Arrow 146 indicates the transmission of system information to wireless terminal 30, which includes network slice cell prohibition information 142 and network slice cell prohibition information 144.

[0095] Figure 16 The wireless terminal 30 of the communication system 20 (16) includes receiver circuitry (e.g., terminal receiver circuitry 56) and processor circuitry (e.g., terminal processor circuitry 50). The receiver circuitry is configured to receive system information from the cell served by the access node 28. This system information includes a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information. As described above, the network slice cell prohibition information includes one or more network slice identifiers of the network slices for which the cell is prohibited. The terminal processor circuitry 50 and specifically the terminal resource selector 40 include a PLMN selector 60; a network slice selector 62; a cell selector 64 using network slice band association information (NSBAI) 42; and a cell prohibition detector 148. Therefore, the processor terminal circuitry 50 is used to select a serving PLMN; select a network slice; and determine whether a cell is prohibited for use in that network slice based on the network slice identifier that identifies the network slice and the network slice cell prohibition information associated with the serving PLMN. The cell prohibition detector 148 of the terminal processor circuitry 50 can perform the determination regarding whether a cell is prohibited for use in a network slice.

[0096] It should be understood, for example, that reference Figure 16 The cell prohibition based on network slicing shown differs from the resource selection in some respects from previous implementations. Figure 16 In the implementation scheme and model, this ban will affect specific network slices within the cell where the ban is announced. Therefore, in Figure 16 In exemplary implementations and modes, a wireless terminal that discovers a specific network slice is prohibited in a cell can search for other cells in a frequency band that includes the prohibited cell. On the other hand, in an earlier described implementation, if network slice frequency band association information indicates that a specific network slice is not supported in a frequency band, the wireless terminal may not search for cells in that frequency band at all.

[0097] In one exemplary implementation, the cell may broadcast system information that includes one or more identifiers of network slices prohibited in the cell. For example, as shown in Table 8, for each supported PLMN, SIB1 may include network slice cell prohibition information, i.e., a list of identifiers of network slices (S-NSSAI) prohibited in the cell (e.g., cellReservedForNetworkSlices). Table 8

[0098] Whether the network slice of interest is prohibited, specifically whether the S-NSSAI of the network slice is included in the network slice cell prohibition information. However, the wireless terminal 30 may or may not know the value of the S-NSSAI assigned by the serving PLMN of the cell in the network slice cell prohibition information, which may affect the wireless terminal 30's decision and subsequent actions.

[0099] In the foregoing respect, the S-NSSAI of interest for the wireless terminal 30 may be based on a list of S-NSSAIs, such as subscribed S-NSSAIs or default configuration S-NSSAIs configured by the home PLMN (HPLMN). The wireless terminal 30 may be configured to use conditions where the S-NSSAI is valid (e.g., identifiable) within the serving PLMN, as disclosed in one or more of the foregoing embodiments. If the S-NSSAI of interest is valid, the wireless terminal 30 may check whether the S-NSSAI is included in the network slice cell prohibition information advertised by the serving cell. If so, for example, if the S-NSSAI is valid, the wireless terminal 30 may continue to determine whether the serving cell is "prohibited" or "not prohibited" based on the network slice cell prohibition information 144. Thereafter, the wireless terminal 30 may continue the process disclosed above (cell status and cell reservation in 5.3.1TS 38.304).

[0100] On the other hand, if the S-NSSAI of interest is not valid, the radio terminal 30 may postpone its decision regarding whether the network slice identified by the S-NSSAI is prohibited in the serving cell until after the radio terminal 30 has completed the registration process, as disclosed in one or more of the foregoing embodiments. In the case that the S-NSSAI of interest is not valid, a registration acceptance message received from the management entity 26 (e.g., the Access and Mobility Management Function (AMF)) may provide mapping information that allows mapping between the S-NSSAI of interest (presumably configured by the HPLMN) and the corresponding S-NSSAI used for the serving PLMN. Based on this mapping information, the radio terminal 30 may then check whether the S-NSSAI mapped for the serving PLMN is included in the network slice cell prohibition information announced by the serving cell. If so, the radio terminal 30 may consider the serving cell “prohibited”; otherwise, the radio terminal 30 may consider the serving cell “not prohibited”, and may thereafter continue the process disclosed above (Cell Status and Cell Reservation in 5.3.1TS 38.304).

[0101] Figure 17 It is shown by Figure 16 The flowchart illustrates exemplary representative steps or actions performed by a wireless terminal (e.g., user equipment) of the communication system 20 (16). Action 17-1 includes selecting a PLMN. Action 17-2 includes selecting a network slice that the wireless terminal wishes to use based on the PLMN. Action 16-3 includes receiving system information from a cell that includes network slice cell prohibition information. The network slice cell prohibition information also includes one or more network slice identifiers of the network slice that the cell is prohibited from using. Action 17-4 is an optional action that may be performed if the network slice identifier of the network slice assigned by the HPLMN is invalid / unknown / unrecognizable in the serving PLMN. Action 17-4 includes initiating a registration process to the core network. The registration process of Action 17-4 may allow the wireless terminal to obtain a network slice identifier mapped to the network slice identifier assigned by the HPLMN for use with the serving PLMN. Action 16-5, performed after Action 17-3 or Action 17-4, may, depending on the circumstances, include determining whether a cell is prohibited from using a network slice based on the network slice cell prohibition information and the network slice identifier.

[0102] Figure 18 This is a flowchart illustrating exemplary representative steps or actions performed by access node 28 of communication system 20 (16). Access node 28 may be, for example, a gNB. Action 18-1 includes generating system information including network slice cell prohibition information. The network slice cell prohibition information also includes one or more network slice identifiers of the network slice whose cell is prohibited. Action 18-2 includes transmitting the system information to wireless terminal 30. 4.0 Other Considerations

[0103] Therefore, in one of its exemplary aspects, the technology disclosed herein relates to a method for supporting network slicing in a radio access network (RAN), the method including but not limited to the following operations: The UE performs cell selection / reselection based on network slice frequency band association information.

[0104] Network slice frequency band association information includes a list of network slice identifiers, each of which is associated with a corresponding radio frequency band.

[0105] Network slice band association is pre-configured or configured by RRC signaling and / or NAS signaling.

[0106] The UE receives network slice cell prohibition information from the cell, which includes a list of network slice identifiers (S-NSSAI) that are prohibited in the cell.

[0107] If the UE is unaware that S-NSSAI is valid in the serving PLMN, the UE performs the registration process with the core network.

[0108] It should be understood that the various exemplary implementations and patterns described above can be used in conjunction with one or more exemplary implementations and patterns described herein.

[0109] Certain units and functions of System 20 may be implemented electromechanically. For example, electromechanical refers to the processor circuitry described herein, such as terminal processor circuitry 50, node processor circuitry 70, and core network entity processor circuitry 80. Furthermore, the term "processor circuitry" is not limited to a single processor but may include multiple processors operating at one or more sites. Additionally, as used herein, the term "server" is not limited to a single server unit but may encompass multiple servers and / or other electronic equipment, which may be located at one site or distributed across different sites. Based on these understandings, Figure 19 An example of electromechanical circuitry, such as a processor circuit, is shown, comprising one or more processors 190, a program instruction memory 192, other memories 194 (e.g., RAM, cache, etc.), input / output interfaces 196 and 197, a peripheral device interface 198, support circuitry 199, and a bus 200 for communication between the aforementioned units. Processor 390 may include the processor circuitry described herein, such as terminal processor circuitry 50, node processor circuitry 70, and core network entity processor circuitry 80.

[0110] The memory or register described herein may be depicted as memory 394 or any computer-readable medium, which may be one or more of readily available memory such as random access memory (RAM), read-only memory (ROM), floppy disk, hard disk, flash memory, or any other form of digital memory (local or remote), and preferably has non-volatile characteristics, and thereby may include memory. Support circuitry 199 is coupled to processor 190 to support the processor in a conventional manner. This circuitry includes cache, power supply, clock circuitry, input / output circuitry, and subsystems, etc.

[0111] While the processes and methods of the disclosed embodiments can be discussed as being implemented as software routines, some of the disclosed method steps can be executed in hardware and by a processor running the software. Therefore, these embodiments can be implemented in software executing on a computer system, in hardware such as application-specific integrated circuits (ASICs) or other types of hardware, or in a combination of software and hardware. The software routines of the disclosed embodiments can be executed on any computer operating system and can be executed using any CPU architecture.

[0112] The functionality of various elements, including function blocks (including, but not limited to, those labeled or described as "computer," "processor," or "controller"), may be provided using hardware such as circuit hardware and / or hardware capable of executing software in the form of programming instructions stored on a computer-readable medium. Therefore, such functionality and illustrated function blocks should be understood as hardware-implemented and / or computer-implemented, and thus machine-implemented.

[0113] In terms of hardware implementation, a functional block may include or encompass, but is not limited to, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry, including but not limited to one or more application-specific integrated circuits (ASICs) and / or one or more field-programmable gate arrays (FPGAs), and (where appropriate) state machines capable of performing such functions.

[0114] In terms of computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer, processor, and controller are used interchangeably herein. When provided by a computer, processor, or controller, these functions may be provided by a single dedicated computer, processor, or controller, by a single shared computer, processor, or controller, or by multiple individual computers, processors, or controllers (some of which may be shared or distributed). Furthermore, the use of the terms “processor” or “controller” may also be interpreted as referring to other hardware capable of performing such functions and / or executing software, such as the exemplary hardware described above.

[0115] Nodes communicating using an air interface also have suitable radio communication circuitry. Furthermore, the techniques disclosed herein can also be considered as being fully embodied in any form of computer-readable storage, such as solid-state memory, disk, or optical disk containing a suitable set of computer instructions that will cause a processor to execute the techniques described herein.

[0116] Furthermore, each functional block or feature of the wireless terminal 30 and the integrated access and backhaul (IAB) node employed in each of the above embodiments can be implemented or executed by circuitry (typically one or more integrated circuits). Circuitry designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic devices, or discrete hardware components, or combinations thereof. The general-purpose processor may be a microprocessor, or alternatively, it may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each of the above circuitry can be configured by digital circuitry or by analog circuitry. Furthermore, when advancements in semiconductor technology lead to the development of technologies for manufacturing integrated circuits that replace current integrated circuits, integrated circuits produced using such technologies can also be used.

[0117] It should be understood that the techniques disclosed herein aim to solve problems centered on radio communications and must be rooted in computer technology to overcome problems particularly present in radio communications. Furthermore, the techniques disclosed herein improve resource selection and utilization in communication systems.

[0118] The technologies disclosed herein encompass one or more of the following non-limiting, non-exclusive exemplary embodiments and patterns: Exemplary Implementation 1: A wireless terminal communicating with a management entity of a core network via an access node of a radio access network (RAN), the core network supporting one or more network slices, each network slice providing a specified service within a public terrestrial mobile network (PLMN), the wireless terminal comprising: Receiver circuit; Transmitter circuit, and; The processor circuit is configured as follows: Select a PLMN service; Select at least one network slice; Initiate cell selection / reselection processes on one or more radio frequency bands based on network slice frequency band association information; in; The network slice frequency band association information includes a list of network slice identifiers, each network slice identifier identifying a network slice, and each of some network slice identifiers being associated with a corresponding radio frequency band; The one or more radio bands are determined from the corresponding radio bands associated with the network slice identifier of the at least one network slice.

[0119] Exemplary Implementation 2: The wireless terminal according to Exemplary Implementation 1, wherein network slice frequency band association information is pre-configured in the wireless terminal.

[0120] Exemplary Implementation 3: The wireless terminal according to Exemplary Implementation 1, wherein the receiver circuitry is configured to receive a Radio Resource Control (RRC) message including network slice band association information from an access node.

[0121] Exemplary Implementation Scheme 4: The wireless terminal according to Exemplary Implementation Scheme 3, wherein the RRC message is a system information message.

[0122] Exemplary Implementation 5: The wireless terminal according to Exemplary Implementation 3, wherein the RRC message is a reconfiguration message.

[0123] Exemplary Implementation 6: The wireless terminal according to Exemplary Implementation 3, wherein the RRC message is a release message.

[0124] Exemplary Implementation 7: The wireless terminal according to Exemplary Implementation 3, wherein the RRC message includes multiple instances of network slice band association information, each of which is applied to one or more designated PLMNs.

[0125] Exemplary Implementation 8: The wireless terminal according to Exemplary Implementation 1, wherein network slice frequency band association information is provided to the wireless terminal by non-access stratum (NAS) signaling.

[0126] Exemplary Implementation 9: The wireless terminal according to Exemplary Implementation 8, wherein the transmitter circuit transmits a registration request message to the core network, and the receiver circuit receives a registration acceptance message including network slice frequency band association information from the core network based on the registration request message.

[0127] Exemplary Implementation 10: The wireless terminal according to Exemplary Implementation 1, wherein network slice frequency band association information is valid within multiple PLMNs.

[0128] Exemplary Implementation 11: The wireless terminal according to Exemplary Implementation 1, wherein the network slice frequency band association information is valid within the serving PLMN.

[0129] Exemplary Implementation 12: The wireless terminal according to Exemplary Implementation 1, wherein the network slice frequency band association information is valid in one or more registered areas of the serving PLMN.

[0130] Exemplary Implementation 13: The wireless terminal according to Exemplary Implementation 1, wherein a cell selection / reselection process is initiated when network slice band association information indicates that at least one network slice does not support the radio band of the currently reserved cell.

[0131] Exemplary Implementation 14: An access node of a radio access network (RAN), the access node comprising: The processor circuit is configured to generate radio resource control (RRC) messages that include network slice band association information; A transmitter circuit configured to transmit RRC messages; The network slice frequency band association information includes a list of network slice identifiers. Each network slice identifier identifies a network slice supported by the core network. Each of some network slice identifiers is associated with a corresponding radio frequency band. The network slice frequency band association information is used by the wireless terminal to perform the cell selection / reselection process.

[0132] Exemplary Implementation 15: The access node according to Exemplary Implementation 14, wherein the RRC message is a system information message.

[0133] Exemplary Implementation 16: The access node according to Exemplary Implementation 14, wherein the RRC message is a reconfiguration message.

[0134] Exemplary Implementation 17: The access node according to Exemplary Implementation 14, wherein the RRC message is a release message.

[0135] Exemplary Implementation 18: The access node according to Exemplary Implementation 14, wherein the RRC message includes multiple instances of network slice band association information, each of which is applied to one or more designated PLMNs.

[0136] Exemplary Implementation 19: The access node according to Exemplary Implementation 14, wherein the network slice frequency band association information is valid within the serving PLMN.

[0137] Exemplary Implementation 20: The access node according to Exemplary Implementation 14, wherein the wireless terminal initiates a cell selection / reselection process when network slice frequency band association information indicates that at least one network slice does not support the radio frequency band of the cell currently reserved by the wireless terminal.

[0138] Exemplary Implementation 21: A management entity for a core network that communicates with a wireless terminal, the core network supporting one or more network slices, each network slice providing a specified service within a Public Land Mobile Network (PLMN), the management entity comprising: A receiver circuit configured to receive a registration request message from a wireless terminal; A processor circuit configured to generate a registration acceptance message that includes network slice frequency band association information; A transmitter circuit configured to transmit a registration and acceptance message to a wireless terminal; The network slice frequency band association information includes a list of network slice identifiers, each of which identifies a network slice. Each of the network slice identifiers is associated with a corresponding radio frequency band. The network slice frequency band association information is used by the wireless terminal to perform the cell selection / reselection process.

[0139] Exemplary Implementation 22: The management entity according to Exemplary Implementation 21, wherein network slice band association information is provided to the wireless terminal by non-access stratum (NAS) signaling.

[0140] Exemplary Implementation 23: The management entity according to Exemplary Implementation 21, wherein network slice frequency band association information is valid within the PLMN.

[0141] Exemplary Implementation 24: The management entity according to Exemplary Implementation 21, wherein network slice frequency band association information is valid in one or more registered areas in the PLMN.

[0142] Exemplary Implementation 25: The management entity according to Exemplary Implementation 21, wherein the wireless terminal initiates a cell selection / reselection process when network slice band association information indicates that at least one network slice does not support the radio band of the cell currently reserved by the wireless terminal.

[0143] Exemplary Implementation 26: A method for a wireless terminal communicating with a management entity of a core network via an access node of a radio access network (RAN), the core network supporting one or more network slices, each network slice providing a specified service within a public land mobile network (PLMN), the method comprising: Select a PLMN service; Select at least one network slice; Initiate cell selection / reselection processes on one or more radio frequency bands based on network slice frequency band association information; in: The network slice frequency band association information includes a list of network slice identifiers, each network slice identifier identifying a network slice, and each of some network slice identifiers being associated with a corresponding radio frequency band; The one or more radio frequency bands are determined from the associated corresponding radio frequency bands.

[0144] Exemplary Implementation 27: The method according to Exemplary Implementation 26, wherein network slice frequency band association information is pre-configured in the wireless terminal.

[0145] Exemplary Implementation 28: The method according to Exemplary Implementation 26 further includes receiving a Radio Resource Control (RRC) message from the access node that includes network slice band association information.

[0146] Exemplary Implementation 29: The method according to Exemplary Implementation 28, wherein the RRC message is a system information message.

[0147] Exemplary Implementation 30: The method according to Exemplary Implementation 28, wherein the RRC message is a reconfiguration message.

[0148] Exemplary Implementation 31: The method according to Exemplary Implementation 28, wherein the RRC message is a release message.

[0149] Exemplary Implementation 32: The method according to Exemplary Implementation 28, wherein the RRC message includes multiple instances of network slice band association information, each of which is applied to one or more designated PLMNs.

[0150] Exemplary Implementation 33: The method according to Exemplary Implementation 26, wherein network slice band association information is provided to the wireless terminal by non-access stratum (NAS) signaling.

[0151] Exemplary Implementation 34: The method according to Exemplary Implementation 33 further includes transmitting a registration request message to the core network and receiving a registration acceptance message including network slice frequency band association information from the core network based on the registration request message.

[0152] Exemplary Implementation 35: The method according to Exemplary Implementation 26, wherein network slice band association information is valid within multiple PLMNs.

[0153] Exemplary Implementation 36: The method according to Exemplary Implementation 26, wherein the network slice band association information is valid within the serving PLMN.

[0154] Exemplary Implementation 37: The method according to Exemplary Implementation 26, wherein the network slice band association information is valid within one or more registered areas of the serving PLMN.

[0155] Exemplary Implementation 38: The method according to Exemplary Implementation 26, wherein a cell selection / reselection process is initiated when network slice band association information indicates that the at least one network slice does not support the radio band of the currently reserved cell.

[0156] Exemplary Implementation 39: A method for an access node in a radio access network (RAN), the method comprising: Generate a Radio Resource Control (RRC) message that includes network slice frequency band association information, and; Send an RRC message; The network slice frequency band association information includes a list of network slice identifiers. Each network slice identifier identifies a network slice supported by the core network. Each of some network slice identifiers is associated with a corresponding radio frequency band. The network slice frequency band association information is used by the wireless terminal to perform the cell selection / reselection process.

[0157] Exemplary Implementation 40: The method according to Exemplary Implementation 39, wherein the RRC message is a system information message.

[0158] Exemplary Implementation 41: The method according to Exemplary Implementation 39, wherein the RRC message is a reconfiguration message.

[0159] Exemplary Implementation 42: The method according to Exemplary Implementation 39, wherein the RRC message is a release message.

[0160] Exemplary Implementation 43: The method according to Exemplary Implementation 39, wherein the RRC message includes multiple instances of network slice band association information, each of which is applied to one or more designated PLMNs.

[0161] Exemplary Implementation 44: The method according to Exemplary Implementation 39, wherein the network slice band association information is valid within the serving PLMN.

[0162] Exemplary Implementation 45: The method according to Exemplary Implementation 39, wherein the cell selection / reselection process is initiated by the wireless terminal when the network slice band association information indicates that the at least one network slice does not support the radio band of the cell currently reserved by the wireless terminal.

[0163] The radio frequency band of the cell currently reserved by the wireless terminal.

[0164] Exemplary Implementation 46: A method for a management entity for a core network, the management entity communicating with a wireless terminal, the core network supporting one or more network slices, each network slice providing a specified service within a Public Land Mobile Network (PLMN), the method comprising: Receive registration request message from the wireless terminal; Generate a registration acceptance message that includes network slice frequency band association information; Send a registration and acceptance message to the wireless terminal; The network slice frequency band association information includes a list of network slice identifiers, each of which identifies a network slice. Each of the network slice identifiers is associated with a corresponding radio frequency band. The network slice frequency band association information is used by the wireless terminal to perform the cell selection / reselection process.

[0165] Exemplary Implementation 47: The method according to Exemplary Implementation 46, wherein network slice band association information is provided to the wireless terminal by non-access stratum (NAS) signaling.

[0166] Exemplary Implementation 48: The method according to Exemplary Implementation 46, wherein the network slice band association information is valid within the PLMN.

[0167] Exemplary Implementation 49: The method according to Exemplary Implementation 46, wherein the network slice band association information is valid within one or more registered areas in the PLMN.

[0168] Exemplary Implementation 50: The method according to Exemplary Implementation 46, wherein the cell selection / reselection process is initiated by the wireless terminal when network slice band association information indicates that the at least one network slice does not support the radio band of the cell currently reserved by the wireless terminal.

[0169] Exemplary Implementation 51: A wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public terrestrial mobile network (PLMN), the wireless terminal comprising: A receiver circuit configured to receive system information from a cell served by an access node, the system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slices to which the cell is prohibited; and; The processor circuit is configured as follows: Select a PLMN service; Select network slices; Whether a cell is prohibited from being used for a network slice is determined based on the network slice identifier that identifies the network slice and the network slice cell prohibition information associated with the serving PLMN.

[0170] Exemplary Implementation 52: The wireless terminal according to Exemplary Implementation 51, wherein a cell selection process is initiated when a cell is prohibited from being used for the network slice.

[0171] Exemplary Implementation 53: The wireless terminal according to Exemplary Implementation 51, wherein the cell is considered suitable for pre-occupancy when the cell is not prohibited from being used for the network slice.

[0172] Exemplary Implementation 54: The wireless terminal according to Exemplary Implementation 51, wherein the network slice identifier is configured by the home PLMN.

[0173] Exemplary Implementation 55: The wireless terminal according to Exemplary Implementation 51, wherein the network slice identifier is specific to the serving PLMN and is mapped from a network slice identifier configured by the home PLMN.

[0174] Exemplary Implementation 56: The wireless terminal according to Exemplary Implementation 55, wherein a network slice identifier is obtained during the registration process to the core network.

[0175] Exemplary Implementation 57: The wireless terminal according to Exemplary Implementation 56, wherein the registration process is initiated before determining whether the cell is blocked.

[0176] Exemplary Implementation 58: An access node for a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public land mobile network (PLMN), the access node comprising: The processor circuit is configured to generate system information, which includes a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slices whose cells are prohibited; A transmitter circuit configured to transmit system information to the cell.

[0177] Exemplary Implementation 59: The access node according to Exemplary Implementation 58, wherein the cell selection process is initiated by the wireless terminal when the cell is prohibited from being used for a network slice selected by the wireless terminal.

[0178] Exemplary Implementation 60: The access node according to Exemplary Implementation 58, wherein the cell is considered suitable for wireless terminal pre-occupancy when the cell is not prohibited from being used for a network slice selected by the wireless terminal.

[0179] Exemplary Implementation 61: A method for a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public land mobile network (PLMN), the method comprising: Select a PLMN service; Select network slices; Receive system information from the cell served by the access node. The system information includes a list of one or more PLMN identifiers and an association of each PLMN identifier with the corresponding network slice cell prohibition information, which includes one or more network slice identifiers of the network slices that the cell is prohibited from. Whether a cell is prohibited from being used for a network slice is determined based on the network slice identifier that identifies the network slice and the network slice cell prohibition information associated with the serving PLMN.

[0180] Exemplary Implementation 62: The method according to Exemplary Implementation 61, wherein a cell selection process is initiated when a cell is prohibited from being used for the network slice.

[0181] Exemplary Implementation 63: The method according to Exemplary Implementation 61, wherein the cell is considered suitable for pre-occupancy if the cell is not prohibited from being used for the network slice.

[0182] Exemplary Implementation 64: The method according to Exemplary Implementation 61, wherein the network slice identifier is configured by the home PLMN.

[0183] Exemplary Implementation 65: The method according to Exemplary Implementation 61, wherein the network slice identifier is specific to the service PLMN and is mapped from a network slice identifier configured by the home PLMN.

[0184] Exemplary Implementation 66: The method according to Exemplary Implementation 65, wherein a network slice identifier is obtained during the registration process to the core network.

[0185] Exemplary Implementation 67: The method according to Exemplary Implementation 66, wherein the registration process is initiated before determining whether the cell is banned.

[0186] Exemplary Implementation 68: A method for an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public land mobile network (PLMN), the method comprising: Generate system information, which includes a list of one or more PLMN identifiers and an association between each PLMN identifier and corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slices whose cells are prohibited; and, The system information is transmitted to the cell.

[0187] Exemplary Implementation 69: The method according to Exemplary Implementation 68, wherein when a cell is prohibited from being used for a network slice selected by a wireless terminal, the cell selection process is initiated by the wireless terminal.

[0188] Exemplary Implementation 70: The method according to Exemplary Implementation 68, wherein the cell is considered suitable for pre-occupancy by the wireless terminal if the cell is not prohibited from being used for a network slice selected by the wireless terminal.

[0189] Exemplary Implementation 71: A wireless terminal communicating with an access node of a radio access network (RAN), the RAN supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the wireless terminal comprising: a receiver circuit configured to receive a message including one or more sets of network slice band association information, each of the one or more sets of network slice band association information being associated with at least one PLMN, the network slice band association information further including one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice, each of the one or more network slice identifiers being associated with one or more corresponding radio frequencies; and a processor circuit configured to: select a serving PLMN; select a desired network slice for serving the PLMN; initiate a cell selection / reselection process based on the desired network slice and a set of network slice band association information associated with the serving PLMN; wherein the cell selection / reselection process is performed on one or more radio frequencies indicated by the set of network slice band association information associated with the serving PLMN, the one or more radio frequencies being associated with the network slice identifier that identifies the desired network slice.

[0190] Exemplary Implementation 72: The wireless terminal according to Exemplary Implementation 71, wherein the message is a system information message.

[0191] Exemplary Implementation 73: The wireless terminal according to Exemplary Implementation 71, wherein the message is a Radio Resource Control (RRC) release message.

[0192] Exemplary Implementation 74: The wireless terminal according to Exemplary Implementation 71, wherein each of the set or multiple sets of network slice frequency band association information is valid in one or more registration areas of at least one PLMN associated with each set.

[0193] Exemplary Implementation 75: The wireless terminal according to Exemplary Implementation 71, wherein a cell selection / reselection process is initiated when a set of network slice frequency band association information associated with the serving PLMN indicates that the required network slice is not supported on the radio frequency of the currently pre-occupied cell.

[0194] Exemplary Implementation 76: An access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a specified service within a public land mobile network (PLMN), the access node comprising: processor circuitry configured to generate a message including one or more sets of network slice band association information, each of the one or more sets of network slice band association information being associated with at least one PLMN, the network slice band association information further including one or more network slice identifiers, each network slice identifier being associated with one or more corresponding radio frequencies; and transmitter circuitry configured to transmit the message to a radio terminal, wherein a cell selection / reselection process is performed by the radio terminal based on the one or more sets of network slice band association information and a desired network slice, the desired network slice being selected by the radio terminal.

[0195] Exemplary Implementation 77: The access node according to Exemplary Implementation 76, wherein the message is a system information message.

[0196] Exemplary Implementation 78: The access node according to Exemplary Implementation 76, wherein the message is a Radio Resource Control (RRC) release message.

[0197] Exemplary Implementation 79: The access node according to Exemplary Implementation 76, wherein each of the set or multiple sets of network slice frequency band association information is valid in one or more registered areas of at least PLMN associated with each set.

[0198] Exemplary Implementation 80: According to the access node of Exemplary Implementation 76, when one or more sets of network slice frequency band association information indicate that the required network slice is not supported on the radio frequency of the cell currently reserved by the wireless terminal, the wireless terminal initiates a cell selection / reselection process.

[0199] Exemplary Implementation 81: A method for a wireless terminal communicating with an access node of a radio access network (RAN), the RAN supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the method comprising: receiving a message including one or more sets of network slice band association information, each of the one or more sets of network slice band association information being associated with at least one PLMN, the network slice band association information further including one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice, each of the one or more network slice identifiers being associated with one or more corresponding radio frequencies; selecting a serving PLMN; selecting a desired network slice for serving the PLMN; and: initiating a cell selection / reselection process based on the desired network slice and the set of network slice band association information associated with the serving PLMN; wherein the cell selection / reselection process is performed on one or more radio frequencies indicated by the set of network slice band association information associated with the serving PLMN, the one or more radio frequencies being associated with the network slice identifier that identifies the desired network slice.

[0200] Exemplary Implementation 82: The method according to Exemplary Implementation 81, wherein the message is a system information message.

[0201] Exemplary Implementation 83: The method according to Exemplary Implementation 81, wherein the message is a Radio Resource Control (RRC) release message.

[0202] Exemplary Implementation 84: The method according to Exemplary Implementation 81, wherein each of the set or multiple sets of network slice frequency band association information is valid within one or more registration areas of at least one PLMN associated with each set.

[0203] Exemplary Implementation 85: The method according to Exemplary Implementation 81, wherein a cell selection / reselection process is initiated when a set of network slice frequency band association information associated with the serving PLMN indicates that the desired network slice is not supported on the radio frequency of the currently pre-occupied cell.

[0204] Exemplary Implementation 86: A method for an access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the method comprising: generating a message including one or more sets of network slice frequency band association information, each of the one or more sets of network slice frequency band association information being associated with at least one PLMN, the network slice frequency band association information further including one or more network slice identifiers, each network slice identifier being associated with one or more corresponding radio frequencies; and transmitting the message to a radio terminal, wherein: a cell selection / reselection process is performed by the radio terminal based on the one or more sets of network slice frequency band association information and a desired network slice, the desired network slice being selected by the radio terminal.

[0205] Exemplary Implementation 87: The method according to Exemplary Implementation 86, wherein the message is a system information message.

[0206] Exemplary Implementation 88: The method according to Exemplary Implementation 86, wherein the message is a Radio Resource Control (RRC) release message.

[0207] Exemplary Implementation 89: The method according to Exemplary Implementation 86, wherein each of the set or multiple sets of network slice band association information is valid within one or more registration areas of at least PLMN associated with each set.

[0208] Exemplary Implementation 90: The method according to Exemplary Implementation 86, wherein when one or more sets of network slice frequency band association information indicate that the required network slice is not supported on the radio frequency of the cell currently occupied by the wireless terminal, the wireless terminal initiates a cell selection / reselection process.

[0209] Exemplary Implementation 91: A wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the wireless terminal comprising: a receiver circuit configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each of the one or more PLMN identifiers being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices for which the cell is prohibited; and a processor circuit configured to: select a serving PLMN; select a desired network slice for serving the PLMN; and determine whether a cell is prohibited based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0210] Exemplary Implementation 92: The wireless terminal according to Exemplary Implementation 91, wherein a cell is blocked when the desired network slice is indicated in the network slice cell blocking information associated with the serving PLMN.

[0211] Exemplary Implementation 93: The wireless terminal according to Exemplary Implementation 92, wherein a cell selection process is initiated when a cell is prohibited.

[0212] Exemplary Implementation 94: The wireless terminal according to Exemplary Implementation 91, wherein the network slice identifier corresponding to the desired network slice is selected from a list of network slice identifiers configured by the home PLMN.

[0213] Exemplary Implementation 95: The wireless terminal according to Exemplary Implementation 91, wherein the network slice identifier corresponding to the required network slice is specific to the serving PLMN, and the network slice identifier specific to the serving PLMN is mapped from a list of network slice identifiers configured by the home PLMN based on mapping information configured to the wireless terminal.

[0214] Exemplary Implementation 96: The wireless terminal according to Exemplary Implementation 95, wherein mapping information is configured during the registration process to the core network.

[0215] Exemplary Implementation 97: The wireless terminal according to Exemplary Implementation 96, wherein a registration process is initiated after receiving system information and before determining whether the cell is blocked.

[0216] Exemplary Implementation 98: An access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a specified service within a public land mobile network (PLMN), the access node comprising: processor circuitry configured to generate system information including a list of one or more PLMN identifiers, each of the one or more PLMN identifiers being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slice for which the cell is prohibited; and transmitter circuitry configured to transmit the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited.

[0217] Exemplary Implementation 99: The access node according to Exemplary Implementation 98, wherein a cell is blocked when the desired network slice selected by the wireless terminal for serving the PLMN is indicated by the network slice cell blocking information associated with the serving PLMN.

[0218] Exemplary implementation 100: The access node according to Exemplary implementation 98, wherein in the event that a cell is blocked, the cell selection process is initiated by the wireless terminal.

[0219] Exemplary Implementation 101: A method for a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the method comprising: selecting a serving PLMN; selecting a desired network slice for serving the PLMN; receiving system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices for which the cell is prohibited; determining whether a cell is prohibited for use in the network slice based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0220] Exemplary Implementation 102: The method according to Exemplary Implementation 101, wherein a cell is blocked when the desired network slice is indicated in the network slice cell blocking information associated with the serving PLMN.

[0221] Exemplary implementation 103: The method according to exemplary implementation 102, wherein a cell selection process is initiated when a cell is prohibited.

[0222] Exemplary Implementation 104: The method according to Exemplary Implementation 101, wherein the network slice identifier corresponding to the desired network slice is selected from a list of network slice identifiers configured by the home PLMN.

[0223] Exemplary Implementation 105: The method according to Exemplary Implementation 101, wherein the network slice identifier corresponding to the desired network slice is specific to the serving PLMN, and the network slice identifier specific to the serving PLMN is mapped from a list of network slice identifiers configured by the home PLMN based on mapping information configured to the wireless terminal.

[0224] Exemplary implementation 106: The method according to exemplary implementation 105, wherein the mapping information is configured during the registration process to the core network.

[0225] Exemplary Implementation 107: The method according to Exemplary Implementation 106, wherein the registration process is initiated after receiving system information and before determining whether the cell is blocked.

[0226] Exemplary Implementation 108: A method for an access node of a radio access network (RAN) supporting one or more network slices, each of the one or more network slices providing a specified service within a public land mobile network (PLMN), the method comprising: generating system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited; and transmitting the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited.

[0227] Exemplary Implementation 109: The method according to Exemplary Implementation 108, wherein a cell is blocked when the desired network slice selected by the wireless terminal for serving the PLMN is indicated by the network slice cell blocking information associated with the serving PLMN.

[0228] Exemplary implementation 110: The method according to exemplary implementation 108, wherein a cell selection process is initiated by a wireless terminal when a cell is prohibited. One or more of the following documents may be related to the technology disclosed herein (all of which are incorporated herein by reference in their entirety): 3GPP TS 38.300v16.1.0 3GPP TS 38.331v16.0.0 3GPP TS 23.501v16.4.0 3GPP TS 24,501 v16.4.1 GSMA NG, 116 Universal Network Slicing Template v2.0 3GPP RP-193254 Enhanced RAN Slicing Study Feasibility study on enhanced access and support for network slicing in 3GPP S1-202209 3GPP S2-2001726 LS on GSMA NG.116 Attribute Service Area and its Impact on PLMN Selection 3GPP S1-202026 LS for 5GC Auxiliary Cell Selection for Access Network Slicing 3GPP S2-2001467 5GC: Key Issues in Assisted Cell Selection for Access Network Slicing 3GPP S1-202264 LS for 5GC Auxiliary Cell Selection for Access Network Slicing

[0229] Although the above description contains many specific details, these should not be construed as limiting the scope of the technology disclosed herein, but merely as providing illustration of some currently preferred embodiments of the technology disclosed herein. Therefore, the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. It should be understood that the scope of the technology disclosed herein fully covers other embodiments that may become apparent to those skilled in the art, and thus the scope of the technology disclosed herein is defined only by the appended claims, wherein elements referred to in the singular do not mean "only one" (unless expressly stated otherwise), but rather "one or more". The above embodiments can be combined with each other. All structural, chemical, and functional equivalents of the elements of the above preferred embodiments known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, an apparatus or method does not necessarily solve every problem sought to be addressed by the technology disclosed herein, as will be covered by the claims. Additionally, the elements, components, or method steps of this disclosure are not intended to be offered to the public, regardless of whether such elements, components, or method steps are expressly stated in the claims.

[0230] In one example, a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a designated service within a public land mobile network (PLMN), the wireless terminal includes: a receiver circuit configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each of the one or more PLMN identifiers being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slice for which the cell is prohibited; and a processor circuit configured to: select a serving PLMN; select a desired network slice for serving the PLMN; and determine whether a cell is prohibited based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0231] In one example, the wireless terminal is blocked when the desired network slice is indicated in the network slice cell blocking information associated with the serving PLMN.

[0232] In one example, the wireless terminal initiates a cell selection process when a cell is blocked.

[0233] In one example, the wireless terminal, where the network slice identifier corresponding to the desired network slice is selected from a list of network slice identifiers configured by the home PLMN.

[0234] In one example, the wireless terminal, where the network slice identifier corresponding to the desired network slice is specific to the serving PLMN, is mapped from a list of network slice identifiers configured by the home PLMN based on mapping information configured to the wireless terminal.

[0235] In one example, the wireless terminal has mapping information configured during the registration process with the core network.

[0236] In one example, the wireless terminal initiates a registration process after receiving system information and before determining whether the cell is blocked.

[0237] In one example, an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), includes: processor circuitry configured to generate system information including a list of one or more PLMN identifiers, each of which is associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of the network slice for which the cell is prohibited; and transmitter circuitry configured to transmit the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited.

[0238] In one example, the access node is blocked when the desired network slice for serving the PLMN, selected by the wireless terminal, is indicated by the network slice cell blocking information associated with the serving PLMN.

[0239] In one example, the access node, where the cell selection process is initiated by the wireless terminal when the cell is blocked.

[0240] In one example, a method for a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), the method comprising: selecting a serving PLMN; selecting a desired network slice for serving the PLMN; receiving system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices to which the cell is prohibited; and determining whether the cell is prohibited for use in the network slice based on the network slice identifier corresponding to the desired network slice and the network slice cell prohibition information associated with the serving PLMN.

[0241] In one example, the method involves a cell being blocked if the desired network slice is indicated in the network slice cell blocking information associated with the serving PLMN.

[0242] In one example, the method initiates a cell selection process when a cell is prohibited.

[0243] In one example, the method involves selecting the network slice identifier corresponding to the desired network slice from a list of network slice identifiers configured by the home PLMN.

[0244] In one example, the method includes a network slice identifier corresponding to the desired network slice that is specific to the serving PLMN. The service PLMN-specific network slice identifier is mapped from a list of network slice identifiers configured by the home PLMN based on mapping information configured to the wireless terminal.

[0245] In one example, the method involves configuring mapping information during the registration process to the core network.

[0246] In one example, the method involves initiating a registration process after receiving system information and before determining whether the cell is blocked.

[0247] In one example, a method for an access node of a radio access network (RAN) supporting one or more network slices, each of which provides a specified service within a public land mobile network (PLMN), the method comprising: generating system information including a list of one or more PLMN identifiers, each PLMN identifier being associated with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited; and transmitting the system information to the cell; wherein the network slice cell prohibition information associated with each of the one or more PLMN identifiers is used by a radio terminal to determine whether the cell is prohibited.

[0248] In one example, the method involves a cell being blocked when the desired network slice selected by the wireless terminal for serving the PLMN is indicated by a network slice cell blocking information associated with the serving PLMN.

[0249] In one example, the method involves a cell selection process initiated by a wireless terminal when a cell is prohibited.

[0250] In one example, a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public land mobile network (PLMN), the wireless terminal includes: a receiver circuit configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices to which the cell is prohibited; and a processor circuit configured to: select a serving PLMN; select a network slice; and determine whether a cell is prohibited for use in the network slice based on the network slice identifier identifying the network slice and the network slice cell prohibition information associated with the serving PLMN.

[0251] In one example, the wireless terminal initiates a cell selection process when the cell is prohibited from being used for the network slice.

[0252] In one example, the wireless terminal is considered suitable for pre-occupancy if the cell is not prohibited from being used for the network slice.

[0253] In one example, the wireless terminal has a network slice identifier configured by the home PLMN.

[0254] In one example, the wireless terminal has a network slice identifier specific to the serving PLMN, which is mapped from a network slice identifier configured by the home PLMN.

[0255] In one example, the wireless terminal obtains a network slice identifier during the registration process with the core network.

[0256] In one example, the wireless terminal initiates a registration process before determining whether the cell is blocked.

[0257] In one example, an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a specified service within a public land mobile network (PLMN), the access node includes: a processor circuit configured to generate system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited; and a transmitter circuit configured to transmit the system information to the cells.

[0258] In one example, the access node, where the cell selection process is initiated by the wireless terminal when the cell is prohibited from being used for network slices selected by the wireless terminal.

[0259] In one example, the access node is considered suitable for wireless terminal pre-occupancy if the cell is not prohibited from being used for network slices selected by the wireless terminal.

[0260] In one example, a method for a wireless terminal communicating with an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a designated service within a public land mobile network (PLMN), the method comprising: selecting a serving PLMN; selecting a network slice; receiving system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices to which the cell is prohibited; and determining whether the cell is prohibited for use in the network slice based on the network slice identifiers identifying the network slice and the network slice cell prohibition information associated with the serving PLMN.

[0261] In one example, the method involves initiating a cell selection process when a cell is prohibited from being used for the network slice.

[0262] In one example, the method assumes that the cell is suitable for pre-occupancy if it is not prohibited from being used for the network slice.

[0263] In one example, the method involves a network slice identifier configured by the home PLMN.

[0264] In one example, the method, where the network slice identifier is specific to the service PLMN, maps the network slice identifier from the network slice identifier configured by the home PLMN.

[0265] In one example, the method involves obtaining a network slice identifier during the registration process to the core network.

[0266] In one example, the method involves initiating a registration process before determining whether a cell is banned.

[0267] In one example, a method for an access node of a radio access network (RAN) supporting one or more network slices, each network slice providing a specified service within a public land mobile network (PLMN), the method comprising: generating system information including a list of one or more PLMN identifiers and an association of each PLMN identifier with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited; and transmitting the system information to the cells.

[0268] In one example, the method involves a cell selection process initiated by the wireless terminal when the cell is prohibited from being used for a network slice selected by the wireless terminal.

[0269] In one example, the method involves a cell being considered suitable for pre-occupancy by a wireless terminal if the cell is not prohibited from being used for a network slice selected by the wireless terminal. <Cross-reference>

[0270] This non-provisional application claims priority to provisional application 63 / 049,482, filed July 8, 2020, pursuant to section 119 of title 35 of the United States Code, the entire contents of which are incorporated herein by reference.

Claims

1. A wireless terminal communicating with an access node of a radio access network (RAN), the RAN supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the wireless terminal comprising: A receiver circuit configured to receive system information from a cell served by the access node, the system information including a list of one or more PLMN identifiers and an association of each of the one or more PLMN identifiers with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices that the cell is prohibited from. as well as Processor, the processor being configured to: Select a PLMN service; Based on the service PLMN, the wireless terminal selects one or more network slices to use; and A cell reselection process is performed based on one or more network slices and the network slice cell prohibition information associated with the serving PLMN, wherein, The cell reselection process is performed as follows: It is determined whether the cell is prohibited from being used for the one or more selected network slices based on (a) identifying one or more network slice identifiers of the one or more selected network slices and (b) the network slice cell prohibition information; as well as Based on whether the cell is prohibited from being used for the determination of one or more selected network slices, it is determined whether the wireless terminal is allowed to reselect the cell for the cell reselection process.

2. A method performed by a wireless terminal communicating with an access node of a radio access network (RAN), the RAN supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the method comprising: System information is received from the cell served by the access node. The system information includes a list of one or more PLMN identifiers and an association between each of the one or more PLMN identifiers and corresponding network slice cell prohibition information. The network slice cell prohibition information includes one or more network slice identifiers of the network slices that the cell is prohibited from. as well as Select a PLMN service; Based on the service PLMN, select one or more network slices that the wireless terminal needs to use; A cell reselection process is performed based on one or more network slices and the network slice cell prohibition information associated with the serving PLMN; in The cell reselection process is performed as follows: It is determined whether the cell is prohibited from being used for the one or more selected network slices based on (a) identifying one or more network slice identifiers of the one or more selected network slices and (b) the network slice cell prohibition information; as well as Based on whether the cell is prohibited from being used for the determination of one or more selected network slices, it is determined whether the wireless terminal is allowed to reselect the cell for the cell reselection process.

3. An access node of a radio access network (RAN) for communicating with a wireless terminal, the RAN supporting one or more network slices, each of the one or more network slices providing a designated service within a public land mobile network (PLMN), the access node comprising: A processor configured to generate system information including a list of one or more PLMN identifiers and an association of each of the one or more PLMN identifiers with corresponding network slice cell prohibition information, the network slice cell prohibition information including one or more network slice identifiers of network slices whose cells are prohibited. as well as Transmitter circuitry, configured to transmit system information, wherein, The network slice cell prohibition information is information that causes a wireless terminal that has selected a serving PLMN and, based on the serving PLMN, has selected one or more network slices that the wireless terminal needs to use to perform the following: A cell reselection process is performed based on one or more network slices and the network slice cell prohibition information associated with the serving PLMN; and The cell reselection process is performed as follows: It is determined whether the cell is prohibited from being used for the one or more selected network slices based on (a) identifying one or more network slice identifiers of the one or more selected network slices and (b) the network slice cell prohibition information; and Based on whether the cell is prohibited from being used for the determination of one or more selected network slices, it is determined whether the wireless terminal is allowed to reselect the cell for the cell reselection process.

Images