Method for slice specific information

Abstract

To provide a method, a system, and a device for slice-specific and / or access category-specific information.SOLUTION: A wireless communication method for use in a radio network node includes the steps of receiving cell selection information associated with at least one network slice or at least one access category from the radio network node, and selecting / re-selecting a cell based on the cell selection information.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] This document relates generally to wireless communications. [Background technology]

[0002] Network slicing is a concept that allows differentiated treatment according to customer requirements and is introduced in New Radio (NR). Network slicing allows Mobile Network Operators (MNOs) to consider their customers as belonging to different tenant types with different service requirements that dictate which slice types each tenant is entitled to use based on Service Level Agreements (SLAs) and subscriptions.

[0003] FIG. 1 illustrates a communication process between a user equipment (UE), a random access network (RAN) node (e.g., a next generation RAN (NG-RAN) node), and an access and mobility management function (AMF). In FIG. 1, after the UE selects a cell, initiates random access, and sets up a radio resource control (RRC) connection based on system information received from the RAN node, the UE provides an S-NSSAI to the RAN node to help the RAN node select an appropriate AMF. Following the initial access, establishment of the RRC connection, and selection of the correct AMF, the AMF establishes a complete UE context by sending an initial context setup request message to the RAN node via an interface between the node RAN and the core network (e.g., NG-C). The initial context setup request message includes the allowed S-NSSAI and further includes the S-NSSAI as part of the packet data unit (PDU) session resource description in the initial context setup request message. Upon successful establishment of the UE context and allocation of PDU session resources to the associated network slice, the RAN node responds to the AMF with an initial context setup response message. One S-NSSAI is added for each PDU session established, so that the RAN node can apply policies at the PDU session level according to the SLA represented by the network slice, but can also apply (for example) differentiated Quality of Service (QoS) within the network slice.

[0004] However, the system information in FIG. 1 does not provide information specifically designed for network slicing. Under such conditions, the UE performs cell selection and / or cell reselection without considering the information of the network slice. As a result, the UE may select and initiate random access to a cell belonging to an inappropriate network slice that is not preferred by the network (NW) for this UE, and may be rejected several times before finding the most suitable cell. Summary of the Invention [Problem to be solved by the invention]

[0005] To solve the above problems, the present disclosure provides a method for providing slice-specific information. [Means for solving the problem]

[0006] This document relates to methods, systems, and devices for providing slice-specific information, and more particularly, to methods, systems, and devices for slice-specific configurations and / or parameters.

[0007] The present disclosure relates to a wireless communication method for use in a wireless terminal, the wireless communication method comprising: receiving cell selection information associated with at least one network slice or at least one access category from a radio network node; selecting a cell based on the cell selection information; Includes.

[0008] Various embodiments may preferably implement the following features. Preferably, the at least one network slice is a plurality of network slices, including network slices supported by the radio network node.

[0009] Preferably, the cell selection information indicates a single network slice selection assistance information S-NSSAI for each of the at least one network slice.

[0010] Preferably, the cell selection information includes a slice / service type SST field of the S-NSSAI of each of the at least one network slice.

[0011] Preferably, the cell selection information includes a plurality of most significant bits (MSB) of an S-NSSAI of each of at least one network slice.

[0012] Preferably, at least one S-NSSAI of at least one network slice is classified by multiple S-NSSAI groups, and the cell selection information indicates at least one of the multiple S-NSSAI groups.

[0013] Preferably, the at least one network slice is a plurality of network slices and includes all network slices supported by the radio network node.

[0014] Preferably, at least one network slice requires high speed access. Preferably, the cell selection information includes a physical cell identification PCI cell range supporting a network slice configured as an allowed network slice for the wireless terminal.

[0015] Preferably, the cell selection information includes at least one cell reselection priority associated with at least one network slice or at least one access category.

[0016] Preferably, at least one reselection priority is set for each network slice.

[0017] Preferably, the cell selection information includes at least one of an S-NSSAI of a network slice, an SST field of the S-NSSAI, or multiple MSBs of the S-NSSAI corresponding to at least one reselection priority.

[0018] Preferably, at least one network slice is classified by a plurality of network slice groups, and at least one reselection priority is set for each network slice group.

[0019] Preferably, the cell selection information includes one of a group ID or a list of network slice groups corresponding to at least one reselection priority set for each network slice group.

[0020] Preferably, at least one reselection priority is set for each access category. Preferably, at least one reselection priority is set for each access category group.

[0021] Preferably, the cell is selected based on a default cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group among the at least one cell reselection priority.

[0022] Preferably, the cell is selected based on a particular cell reselection priority among the at least one reselection priority, the particular cell reselection priority corresponding to one of a network slice, a network slice group, an access category group, or an access category used by the wireless terminal in a period prior to selecting the cell.

[0023] Preferably, the cell selection information is in one of the system information or radio resource control (RRC) signaling.

[0024] Preferably, the cell selection information is in the system information block SIB or in a dedicated RRC message.

[0025] Preferably, the cell selection information for the wireless terminal's serving cell is in System Information Block 1, SIB1.

[0026] Preferably, the cell selection information of the wireless terminal's neighbouring cells is in a SIB other than SIB1. Preferably, the cell selection information is in the RRC release message.

[0027] The present disclosure relates to a wireless communication method for use in a wireless communication node, the wireless communication method including transmitting cell selection / reselection information associated with at least one network slice or at least one access category to a wireless terminal.

[0028] Various embodiments may preferably implement the following features. Preferably, the at least one network slice is a plurality of network slices, including network slices supported by the radio network node.

[0029] Preferably, the cell selection information indicates a single network slice selection assistance information S-NSSAI for each of the at least one network slice.

[0030] Preferably, the cell selection information includes a slice / service type SST field of the S-NSSAI of each of the at least one network slice.

[0031] Preferably, the cell selection information includes a plurality of most significant bits (MSB) of an S-NSSAI of each of at least one network slice.

[0032] Preferably, at least one S-NSSAI of at least one network slice is classified by multiple S-NSSAI groups, and the cell selection information indicates at least one of the multiple S-NSSAI groups.

[0033] Preferably, the at least one network slice is a plurality of network slices and includes all network slices supported by the radio network node.

[0034] Preferably, at least one network slice requires high speed access. Preferably, the cell selection information includes a physical cell identification PCI cell range supporting a network slice configured as an allowed network slice for the wireless terminal.

[0035] Preferably, the cell selection information includes at least one cell reselection priority associated with at least one network slice or at least one access category.

[0036] Preferably, at least one reselection priority is set for each network slice.

[0037] Preferably, the cell selection information includes at least one of an S-NSSAI of a network slice, an SST field of the S-NSSAI, or multiple MSBs of the S-NSSAI corresponding to at least one reselection priority.

[0038] Preferably, at least one network slice is classified by a plurality of network slice groups, and at least one reselection priority is set for each network slice group.

[0039] Preferably, the cell selection information includes one of a group ID or a list of network slice groups corresponding to at least one reselection priority set for each network slice group.

[0040] Preferably, at least one reselection priority is set for each access category. Preferably, at least one reselection priority is set for each access category group.

[0041] Preferably, the cell is selected based on a default cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group among the at least one cell reselection priority.

[0042] Preferably, the cell is selected based on a particular cell reselection priority among the at least one reselection priority, the particular cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group used by the wireless terminal in a period prior to selecting the cell.

[0043] Preferably, the cell selection information is in one of the system information or radio resource control (RRC) signaling.

[0044] Preferably, the cell selection information is in a system information block SIB or in a dedicated radio resource control RRC message.

[0045] Preferably, the cell selection information for the wireless terminal's serving cell is in System Information Block 1, SIB1.

[0046] Preferably, the cell selection information of the wireless terminal's neighbouring cells is in a SIB other than SIB1. Preferably, the cell selection information is in the RRC release message.

[0047] The present disclosure relates to a wireless communication method for use in a wireless terminal, the wireless communication method comprising: At least one network slice or at least one access category receiving associated resource information from a radio network node; performing a random access procedure based on the resource information; Includes.

[0048] Various embodiments may preferably implement the following features. Preferably, the resource information is configured for at least one of at least one network slice, at least one network slice group associated with the at least one network slice, at least one access category, or at least one access category group.

[0049] Preferably, the resource information indicates a random access channel RACH resource of the random access procedure.

[0050] Preferably, the resource information includes at least one of a specific prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, or ra-ResponseWindow.

[0051] Preferably, the resource information indicates at least one search space for the random access procedure.

[0052] Preferably, the resource information indicates a portion of the common RACH resources for the random access procedure.

[0053] Preferably, the at least one network slice is classified into a plurality of network slice groups, each of the plurality of network slice groups corresponding to a particular resource information in the resource information.

[0054] Preferably, at least one network slice is classified by a first network slice group or a second network slice group, and each of the network slices in the first network slice group corresponds to specific resource information in the resource information.

[0055] Preferably, the network slices in the first network slice group require high-speed access.

[0056] Preferably, at least one access category or at least one access category group associated with the at least one access category corresponds to a particular resource information in the resource information.

[0057] Preferably, at least one network slice is classified by a first access category or a second access category, and each network slice in the first access category corresponds to a particular resource information in the resource information.

[0058] Preferably, the network slices in the first access category require high speed access.

[0059] Preferably, the resource information includes a resource indicated by the resource information of the random access procedure, at least one network slice, at least one network slice, A one-to-one mapping between a rice group, at least one access category, or at least one access category group.

[0060] Preferably, the resource information indicates an association of a resource indicated by the resource information with one of at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

[0061] Preferably, the resource indicated by the resource information and one of at least one network slice, at least one network slice group, at least one access category or at least one access category group are associated by associating a preamble or a random access channel opportunity (RO) of the resource indicated by the resource information with one of at least one network slice, at least one network slice group, at least one access category or at least one access category group.

[0062] Preferably, the resource information indicates a preamble start index and a number of consecutive preambles.

[0063] Preferably, the resource information indicates a preamble start index and a step number.

[0064] Preferably, the resource information indicates a preamble mask that corresponds to a predefined set of preambles within the preamble of the resource indicated by the resource information.

[0065] Preferably, the random access procedure is performed based on default cell resource information corresponding to one of a network slice, a network slice group, an access category, or an access category group in the received resource information.

[0066] Preferably, the random access procedure is performed based on specific resource information in the received resource information, the specific resource information corresponding to one of a network slice, a network slice group, an access category, or an access category group used by the wireless terminal in a period prior to selecting a cell.

[0067] Preferably, the resource information is in one of the system information or RRC signaling.

[0068] The present disclosure relates to a wireless communication method for use in a radio network node, the wireless communication method including transmitting resource information associated with at least one network slice to a wireless terminal.

[0069] Various embodiments may preferably implement the following features. Preferably, the resource information is configured for at least one of at least one network slice, at least one network slice group associated with the at least one network slice, at least one access category, or at least one access category group.

[0070] Preferably, the resource information indicates a random access channel RACH resource of the random access procedure.

[0071] Preferably, the resource information includes at least one of a specific prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, or ra-ResponseWindow.

[0072] Preferably, the resource information indicates at least one search space for the random access procedure.

[0073] Preferably, the resource information indicates a portion of the common RACH resources for the random access procedure.

[0074] Preferably, the at least one network slice is classified into a plurality of network slice groups, each of the plurality of network slice groups corresponding to a particular resource information in the resource information.

[0075] Preferably, at least one network slice is classified by a first network slice group or a second network slice group, and each of the network slices in the first network slice group corresponds to specific resource information in the resource information.

[0076] Preferably, the network slices in the first network slice group require high-speed access.

[0077] Preferably, at least one access category or at least one access group associated with at least one access category corresponds to a particular resource information in the resource information.

[0078] Preferably, at least one network slice is classified by a first access category or a second access category, and each network slice in the first access category corresponds to a particular resource information in the resource information.

[0079] Preferably, the network slices in the first access category require high speed access.

[0080] Preferably, the resource information indicates a one-to-one mapping between the resources indicated by the resource information of the random access procedure and one of at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

[0081] Preferably, the resource information indicates an association of a resource indicated by the resource information with one of at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

[0082] Preferably, the resource indicated by the resource information and at least one network slice, at least one network slice group, at least one access category or at least one access category group are a preamble or a random access channel opportunity (RO) of the resource indicated by the resource information and at least one network slice, at least one network slice group, at least one access category group, The association is achieved by associating the service group with one of at least one access category or at least one access category group.

[0083] Preferably, the resource information indicates a preamble start index and a number of consecutive preambles.

[0084] Preferably, the resource information indicates a preamble start index and a step number.

[0085] Preferably, the resource information indicates a preamble mask that corresponds to a predefined set of preambles within the preamble of the resource indicated by the resource information.

[0086] Preferably, the random access procedure is performed based on default cell resource information in the received resource information.

[0087] Preferably, the random access procedure is performed based on specific resource information in the received resource information, the specific resource information corresponding to one of the network slices or access categories used by the wireless terminal in a period prior to selecting a cell.

[0088] Preferably, the resource information is in one of the system information or RRC signaling.

[0089] The present disclosure relates to a wireless communication method for use in a radio network node, the wireless communication method comprising: receiving an aggregate maximum data rate associated with at least one network slice; performing data rate control based on an aggregate maximum data rate; Includes.

[0090] Various embodiments may preferably implement the following features. Preferably, the aggregate maximum data rate associated with the at least one network slice is received from the core network.

[0091] Preferably, the aggregate maximum data rate associated with the at least one network slice is in at least one of an INITIAL CONTEXT SETUP REQUEST, a PDU SESSION RESOURCE SETUP REQUEST, a PDU SESSION RESOURCE MODIFY REQUEST, or a HANDOVER REQUEST.

[0092] Preferably, the aggregate maximum data rate associated with the at least one network slice is received from the gNB.

[0093] Preferably, the aggregate maximum data rate associated with the at least one network slice is in at least one of a HANDOVER REQUEST, an S-NODE ADDITION REQUEST, an S-NODE MODIFICATION REQUEST, or a RETRIEVE UE CONTEXT RESPONSE.

[0094] Preferably, the aggregate maximum data rate associated with at least one network slice is included in at least one inter-node radio resource control (RRC) message.

[0095] Preferably, the at least one inter-node RRC message includes at least one of a HandoverCommand, a HandoverPreparationInformation, a CG-Config, or a CG-ConfigInfo.

[0096] Preferably, the aggregate maximum data rate associated with at least one network slice is received from a gNB centralized unit, gNB-CU, and the radio network node is a gNB distributed unit, gNB-DU.

[0097] Preferably, the aggregate maximum data rate associated with the at least one network slice is in at least one of the UE CONTEXT SETUP REQUEST or the UE CONTEXT MODIFICATION REQUEST.

[0098] The present disclosure relates to a wireless terminal. a communication unit configured to receive cell selection / reselection information associated with at least one network slice or at least one access category from a radio network node; a processor configured to select a cell based on the cell selection information; Equipped with.

[0099] Various embodiments may preferably implement the following features. Preferably, the processor is further configured to perform the wireless communication method of any of the methods described above.

[0100] The present disclosure relates to a radio network node comprising a communication unit configured to transmit cell selection / reselection information associated with at least one network slice or at least one access category to a wireless terminal.

[0101] Various embodiments may preferably implement the following features. Preferably, the radio network node further comprises a processor configured to perform the wireless communication method of any of the methods described above.

[0102] The present disclosure relates to a wireless terminal. a communication unit configured to receive resource information associated with at least one network slice or at least one access category from a radio network node; a processor configured to perform a random access procedure based on the resource information; Equipped with.

[0103] Various embodiments may preferably implement the following features. Preferably, the processor is further configured to perform the wireless communication method of any of the methods described above.

[0104] The present disclosure relates to a radio network node comprising a communication unit configured to transmit resource information associated with at least one network slice or at least one access category to a wireless terminal.

[0105] Various embodiments may preferably implement the following features. Preferably, the radio network node further comprises a processor configured to perform the wireless communication method of any of the methods described above.

[0106] The present disclosure relates to a computer program product including a computer readable program medium code stored thereon which, when executed by a processor, causes the processor to perform a wireless communication method according to any of the methods described above.

[0107] The exemplary embodiments disclosed herein are intended to provide features that will be readily apparent by reference to the following description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, apparatus, and computer program products are disclosed herein. However, it is understood that these embodiments are presented by way of example and not by way of limitation, and it will be apparent to those skilled in the art upon reading this disclosure that various modifications to the disclosed embodiments may be made while remaining within the scope of the present disclosure.

[0108] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Moreover, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps of a disclosed method or process can be rearranged while remaining within the scope of the present disclosure. Thus, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in a sample order, and that the present disclosure is not limited to the specific order or hierarchy presented, unless otherwise stated.

[0109] These and other aspects and implementations thereof are explained in more detail in the drawings, description, and claims. [Brief description of the drawings]

[0110] [Figure 1] Figure 1 shows the process between a user equipment, a random access network node and an access and mobility management function. [Diagram 2] FIG. 2 illustrates an example schematic diagram of a wireless terminal according to one embodiment of the present disclosure. [Diagram 3] FIG. 3 illustrates an example schematic diagram of a radio network node according to one embodiment of the present disclosure. [Figure 4] FIG. 4 illustrates an example process according to one embodiment of the present disclosure. [Diagram 5]FIG. 5 illustrates a table of standardized values ​​for the SST field according to an embodiment of the present disclosure. [Figure 6] FIG. 6 illustrates a process according to one embodiment of the present disclosure. [Figure 7] FIG. 7 illustrates an example of a random access channel (RACH) resource configuration for msg1-based SI request in accordance with one embodiment of the present disclosure. [Figure 8] FIG. 8 illustrates an example of a one-to-one mapping between a portion of common RACH resources / specific RACH resources and network slices according to one embodiment of the present disclosure. [Figure 9] FIG. 9 illustrates an example of a common RACH resource configuration according to one embodiment of the present disclosure. [Figure 10] FIG. 10 illustrates an example table of preamble masks according to one embodiment of the present disclosure. [Figure 11] FIG. 11 illustrates an example of a common RACH resource configuration according to one embodiment of the present disclosure. [Figure 12] FIG. 12 illustrates an example of an association between some of the common RACH opportunities and one of a network slice, a network slice group, an access category, or an access category group. [Figure 13] FIG. 13 illustrates an example of a table of opportunity masks according to one embodiment of the present disclosure. [Figure 14] FIG. 14 illustrates an example of an association between a portion of a common RO and one of a network slice, a network slice group, an access category, or an access category group. [Figure 15] FIG. 15 illustrates a process according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0111] FIG. 2 relates to a schematic diagram of a wireless terminal 20 according to one embodiment of the present disclosure. The wireless terminal 20 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, and is not limited herein. The wireless terminal 20 may include a microprocessor or an application specific integrated circuit (ASIC). 2. The communication unit 220 may include a processor 200, such as an ASIC (Advanced Specific Integrated Circuit), a storage unit 210, and a communication unit 220. The storage unit 210 may be any data storage device that stores a program code 212 that is accessed and executed by the processor 200. Embodiments of the storage unit 212 include, but are not limited to, a subscriber identity module (SIM), a read only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 220 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 200. In one embodiment, the communication unit 220 transmits and receives signals via at least one antenna 222 shown in FIG. 2.

[0112] In one embodiment, the storage unit 210 and the program code 212 may be omitted and the processor 200 may include a storage unit having the program code stored therein.

[0113] The processor 200 may, for example, by executing the program code 212 to perform any of the steps in the illustrated embodiments at the wireless terminal 20 .

[0114] The communication unit 220 may be a transceiver. Alternatively or additionally, the communication unit 220 may combine a transmitting unit and a receiving unit configured to transmit and receive, respectively, signals to and from a wireless network node (e.g., a base station).

[0115] FIG. 3 relates to a schematic diagram of a radio network node 30 according to an embodiment of the present disclosure. The radio network node 30 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network, or a radio network controller (RNC), and is not limited herein. Furthermore, the radio network node 30 may comprise (perform) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user place function (UPF), a policy control function (PCF), an application function (AF), etc. The radio network node 30 may include a processor 300, such as a microprocessor or ASIC, a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device that stores program code 312 that is accessed and executed by the processor 300. Examples of the storage unit 312 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 320 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 300. In one example, the communication unit 320 transmits and receives signals via at least one antenna 322 shown in FIG. 3.

[0116] In one embodiment, the memory unit 310 and the program code 312 may be omitted. The processor 300 may include a memory unit having program code stored therein.

[0117] The processor 300 may perform any of the steps described in the illustrated embodiment on the radio network node 30, for example by executing the program code 312.

[0118] The communication unit 320 may be a transceiver. Alternatively, or in addition, the communication unit 320 may combine a transmitting unit and a receiving unit configured to transmit and receive, respectively, signals to and from a wireless terminal (e.g., user equipment).

[0119] 4 illustrates an example of a process according to an embodiment of the present disclosure. The process illustrated in FIG. 4 may be used in a UE and may include the following steps:

[0120] Step 400: Receive slice-specific or access category-specific cell selection / reselection information.

[0121] Step 402: Select / reselect a cell based on slice-specific or access category-specific cell selection / reselection information.

[0122] More specifically, the UE receives slice-specific or access category-specific cell selection / reselection information associated with a network slice and / or an access category from the NG-RAN (i.e., a radio network node) (step 400). Based on the received slice-specific or access category-specific cell selection / reselection information, the UE selects / reselects a cell, for example, by performing a cell selection / reselection procedure (step 402). Since the UE considers the slice-specific or access category-specific cell selection / reselection information associated with at least one network slice and / or at least one access category when selecting / reselecting a cell, the UE can determine a cell belonging to an appropriate network slice that is preferred by the network (NW) (e.g., a core network (CN)). In other words, the UE can achieve high-speed access to a cell supporting an intended network slice and slice-specific or access category-specific data rate control of the NW based on the slice-specific or access category-specific cell selection / reselection information associated with the network slice and / or access category.

[0123] It should be noted that in the following, cell selection can also denote cell reselection for brevity and vice versa. Similarly, "select" can also mean "reselect" in the following and vice versa.

[0124] In one embodiment, the slice-specific or access category-specific cell selection information provides information including network slices supported by a radio network node. For example, during the NG setup procedure, the NG-RAN can provide a single network slice selection assistance information (S-NSSAI) supported per tracking area (TA) to the AMF, and the AMF can respond to the NG-RAN with its supported S-NSSAI per public land mobile network (PLMN). Each network slice is uniquely identified by an NSSAI that includes one or a list of S-NSSAIs, where the S-NSSAI includes: - Mandatory slice / , which identifies the slice type and consists of 8 bits (range 0-255) A service type (SST) field; - an optional Slice Differentiator (SD) field consisting of 24 bits, which distinguishes between slices having the same SST field; It is a combination of:

[0125] FIG. 5 illustrates a table of standardized values ​​of the SST field according to an embodiment of the present disclosure. In FIG. 5, when the value of the SST field is 1, the SST field represents a network slice suitable for handling enhanced mobile broadband (eMBB). When the value of the SST field is 2, the SST field represents a network slice suitable for handling ultra-reliable low-latency communications (URLLC). When the value of the SST field is 3, the SST field represents a network slice suitable for handling large-scale Internet of Things (IoT). When the value of the SST field is 4, the SST field represents a network slice suitable for handling vehicle-to-everything (V2X) services.

[0126] After the NG setup procedure, the NG-RAN knows the S-NSSAIs supported by both the RAN and CN sides, and the NG-RAN can transmit (e.g., broadcast) the S-NSSAIs supported by the NG-RAN as cell selection information. However, the number of S-NSSAIs supported by a single RAN node can be huge, and each S-NSSAI requires 40 bits for signaling (e.g., 8 bits for the SST field and 24 bits for the SD field). If the NG-RAN is required to transmit (e.g., broadcast) the supported S-NSSAIs to the UE, signaling overhead becomes an issue because the maximum size of the System Information Block 1 (SIB1) or System Information (SI) message is 2976 bits.

[0127] In one embodiment, the cell selection information includes an SST field in the S-NSSAI of each network slice, i.e., the NG-RAN may broadcast an SST field (e.g., 8 bits) for each S-NSSAI supported by the NG-RAN instead of a full S-NSSAI (e.g., 32 bits).

[0128] In one embodiment, the cell selection information includes a number of most significant bits (MSBs) (e.g., bits 2 to 7) of the S-NSSAI for each S-NSSAI supported by the NG-RAN.

[0129] In one embodiment, the S-NSSAI of the network slice may be classified (e.g., divided or classified) by S-NSSAI group, and the cell selection information indicates at least one of the S-NSSAI groups to indicate the network slice supported by the NG-RAN. For example, the cell selection information may include a group identification of the S-NSSAI group having the network slice supported by the NG-RAN.

[0130] In one embodiment, the cell selection information provides (e.g., indicates) information of all network slices supported by the NG-RAN.

[0131] In one embodiment, the cell selection information provides (e.g., indicates) information of a network slice that requires fast access in a network slice supported by the NG-RAN. For example, a network slice that requires fast access may have an SST field with a value of 2 (SST=2). That is, a network slice that requires fast access may be configured to handle ultra-reliable low-latency communication. In one embodiment, the cell selection information includes an S-NSSAI, an SST field, an S-NSSAI The S-NSSAI indicates the network slice that requires fast access by broadcasting a few MSBs (e.g., bits 2 to 7) of the S-NSSAI or the group ID of the S-NSSAI group.

[0132] In one embodiment, some assistance information (e.g., S-NSSAI, SST field, full 32-bit S-NSSAI or some MSBs (e.g., bits 2-7) of Group ID) may be provided from the network (e.g., CN) to the NG-RAN to help the NG-RAN distinguish slices that require fast access. In one embodiment, the assistance information may be provided from the network to the NG-RAN node during the NG setup procedure.

[0133] In one embodiment, the cell selection information includes a physical cell identity (PCI) range of cells supporting a network slice configured as an allowed network slice for the UE.

[0134] In one embodiment, the cell selection information includes at least one slice-specific or access category-specific cell reselection priority. For example, the cell reselection priority may be associated with a network slice and / or an access category.

[0135] In one embodiment, multiple cell reselection priorities may be broadcast, with each reselection priority being set per network slice, per network slice group, per access category, or per access category group, and the network slices may be classified by multiple network slice groups, and the access categories may be classified by multiple access category groups.

[0136] In an embodiment in which reselection priority is set per network slice, the cell selection information may include at least one of the S-NSSAI, the SST field of the S-NSSAI, or a number of MSBs (e.g., bits 2 to 7) of the S-NSSAI and a corresponding reselection priority.

[0137] In an embodiment in which reselection priority is set per network slice group, the cell selection information may include a group ID of the corresponding network slice group, or a list of S-NSSAIs classified into the corresponding network slice group and the corresponding reselection priority.

[0138] In embodiments where reselection priorities are set per access category, the cell selection information may include the access category and the corresponding reselection priority.

[0139] In an embodiment in which reselection priorities are set per access category group, the cell selection information may include an access category group ID of the corresponding access category group and the corresponding reselection priority.

[0140] In an embodiment of a UE receiving multiple cell reselection priorities, the UE may utilize (eg, apply) a particular one of the received cell reselection priorities to select a cell.

[0141] In one embodiment, the UE applies a default cell reselection priority associated with at least one of a network slice, a network slice group, an access category group, or an access category in the received cell reselection priority to select a cell. For example, the default cell reselection priority may be predefined or configured by the NG-RAN.

[0142] In one embodiment, the UE applies a cell reselection priority corresponding to a recently used network slice, network slice group, access category, or access category group to select a cell. For example, the recently used network slice, network slice group, access category, or access category group may be a network slice, network slice group, access category, or access category group used by the UE in a period before selecting a cell. In another example, the recently used network slice, network slice group, access category, or access category group is the latest network slice, network slice group, access category, or access category group used by the UE. In yet another example, the recently used network slice, network slice group, access category, or access category group is the most recently used network slice, network slice group, access category, or access category group.

[0143] In an embodiment, consideration should be given to how to transmit the cell selection information. In one embodiment, the cell selection information is in (included in) an SI (eg, an SIB).

[0144] In one embodiment, the cell selection information is present (contained) in Radio Resource Control (RRC) signaling (eg, a dedicated RRC message), for example, the cell selection information is in an RRC release message.

[0145] In one embodiment, the cell selection information corresponding to the serving cell is in (contained in) SIB1 since information regarding cell access is included in SIB1.

[0146] In one embodiment, the cell selection information corresponding to the neighboring cell is in (included in) a SIB other than SIB1. For example, if the neighboring cell is an intra-frequency neighboring cell, the cell selection information corresponding to the neighboring cell is included in SIB2. In another example, if the neighboring cell is an inter-frequency neighboring cell, the cell selection information corresponding to the neighboring cell is included in SIB4. In yet another example, if the neighboring cell is an inter-radio access technology (inter-RAN) neighboring cell, the cell selection information corresponding to the neighboring cell is included in SIB5. In yet another example, the cell selection information corresponding to all neighboring cells is included in a newly introduced SIB, and the NG-RAN may provide (e.g., transmit or broadcast) this newly introduced SIB upon request. In one embodiment, the cell selection information is provided per frequency.

[0147] 6 shows a process according to one embodiment of the present disclosure. The process shown in FIG. 6 may be used in a UE and may include the following steps:

[0148] Step 600: Receive slice-specific or access category-specific random access channel (RACH) resource information.

[0149] Step 602: Perform a random access procedure based on slice-specific or access category-specific RACH resource information.

[0150] 6, the UE receives slice-specific or access category-specific RACH resource information (e.g., resource configuration and / or resource parameters) from a NW (e.g., a RAN) (step 600). Based on the received slice-specific or access category-specific RACH resource information, the UE performs a random access procedure, for example, by using a RACH resource indicated by the slice-specific or access category-specific RACH resource information (step 604).

[0151] In one embodiment, the slice-specific or access category-specific RACH resource information is configured for at least one of a network slice, a network slice group associated with the network slice, an access category, or at least one access category group.

[0152] In one embodiment, slice-specific or access category-specific RACH resource information may include specific prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, and / or ra-ResponseWindow configured for each network slice, network slice group, access category, and / or access category group.

[0153] In one embodiment, the slice-specific or access category-specific RACH resource information may include (e.g., indicate) a particular search space ra-SearchSpace (e.g., an ID of a search space for a random access procedure) that may be configured for a network slice, a network slice group, an access category or an access category group.

[0154] In one embodiment, the slice-specific or access category-specific RACH resource information may indicate a portion of common RACH resources (RACH opportunities and / or preambles) assigned to a network slice, a network slice group, an access category, or an access category group. Note that the common RACH resources are RACH resources broadcasted in the SI and used by all UEs to perform random access procedures. The portion of the common RACH resources may be assigned to a network slice, a network slice group, an access category, or an access category group based on a configuration from the NW. Further details are discussed below. The common RACH resources may be divided into common RACH opportunities (ROs) in the frequency and time domains and common preambles in the preamble domain.

[0155] In one embodiment, the specific RACH resource is another RACH resource in a frequency domain, timer domain, and / or preamble domain different from the common RACH resource. The specific RACH resource can be divided into a specific RO in the frequency domain and time domain, and a specific preamble in the preamble domain.

[0156] In one embodiment, a particular RACH configuration or parameter in the slice-specific RACH resource information may be linked to a network slice or a network slice group.

[0157] In one embodiment, network slices supported by the RAN may be divided into (e.g., categorized by) multiple network slice groups, each of which is linked to a slice-specific RACH resource configuration and / or parameters.

[0158] In one embodiment, the network slices supported by the RAN may be divided into two network slice groups NSG1 and NSG2. For the network slice group NSG1, slice-specific RACH resource configurations and / or parameters are configured for each or all network slices in the network slice group NSG1. In one example, a slice-specific RACH No resource configuration and / or parameters are provided to network slice group NSG2.

[0159] In one embodiment, network slice group NSG1 includes frequently used network slices, and network slice group NSG2 includes the remaining network slices.

[0160] In one embodiment, network slice group NSG1 includes network slices that require fast access, and network slice group NSG2 includes the remaining network slices. For example, the network slices that require fast access may have an SST field with a value of 2 (SST=2).

[0161] In one embodiment, a particular RACH configuration or parameter of the access category specific RACH resource information may be linked to an access category or an access category group.

[0162] In one embodiment, the access categories supported by the RAN may be divided into (e.g., categorized by) multiple access category groups, each of which is linked to an access category specific RACH resource configuration and / or parameters.

[0163] In one embodiment, the access categories may be divided into two access category groups ACG1 and ACG2. For the access category group ACG1, access category specific RACH resource configurations and / or parameters are configured for each or all access categories in the access category group ACG1. In one example, no access category specific RACH resource configurations and / or parameters are provided for the access category group ACG1.

[0164] In one embodiment, access category group ACG1 includes frequently used access categories, and access category group ACG2 includes the remaining network slices.

[0165] In one embodiment, access category group ACG1 includes access categories requiring high-speed access, and access category group ACG2 includes the remaining network slices.

[0166] In one embodiment, an access category / access category group / network slice / network slice group (e.g., network slice group NSG1 or access category group ACG1) is associated with a portion of common RACH resources (e.g., RACH opportunities and / or preambles) or specific RACH resources.

[0167] In one embodiment, similar to the RACH resource configuration for msg1-based SI request, some of the common RACH resources (RACH opportunities and / or preambles) / specific RACH resources (RACH opportunities and / or preambles) are configured as slice-SpecificPeriod / slicegroup-SpecificPeriod / accessCategory-SpecificPeriod / accessCategoryGroup-SpecificPeriod and slice-SpecificResources / slicegroup-SpecificResources / accessCategory-SpecificResources / accessCategory By introducing Group-Specific Resources, they can be associated with network slices / network slice groups / access categories / access category groups.

[0168] 7 illustrates an example of a RACH resource configuration for msg1-based SI request, where the horizontal axis relates to subframe number (SFN) and the vertical axis relates to frequency, according to one embodiment of the present disclosure. The relevant parameters of the embodiment illustrated in FIG. 7 are listed below:

[0169] K=4 (number of SI messages that can be requested on demand) NTOT=4 (total number of SSBs) ssb-perRACH-Occasion:N=2 PRACH configuration index = 12 (PRACH configuration period = 2 radio frames) Msg1-FDM=1 Association Period = 2 (number of PRACH establishment periods) For example, if si-RequestPeriod is set to 2 (the number of association periods), The number of SI requests serviced in each PRACH establishment period is K×NTOT / (si-RequestPeriod*association period)=(4*4) / (2*2)=4.

[0170] The number of RACH opportunities in each PRACH configuration period is 1 (ie, Msg1-FDM). => The number of SI requests serviced on each RACH opportunity is 4 => The number of preambles required for an SI request is equal to 4 Based on the above parameters, the following configurations can be set for different SI requirements:

[0171] For on-demand SI message 1: ra-PreambleStartIndex=60, ra-AssociationPeriodIndex=0; For on-demand SI message 2: ra-PreambleStartIndex=62, ra-AssociationPeriodIndex=0; For on-demand SI message 3: ra-PreambleStartIndex=60, ra-AssociationPeriodIndex=1; For on-demand SI message 4: ra-PreambleStartIndex=62, ra-AssociationPeriodIndex=1.

[0172] In one embodiment, the one-to-one mapping between some / specific RACH resources (RACH opportunities and / or preambles) of common RACH resources (RACH opportunities and / or preambles) may be associated with a network slice by:

[0173] slice-SpecificPeriod ENUMERATED{1,2,4,6,8,10,12,16} OPTIONAL,--Need R / / Slice-specific configuration periodicity in number of association periods slice-SpecificResources sequence of slice-SpecificResources(SIZE(1..maxnumberofslice)) / / The maximum size is the maximum number of slices if RACH resources are configured per slice.

[0174] Slice-SpecificResources::=SEQUENCE{ra-PreambleStartIndexINTEGER(0...63), / / If N SSBs are associated with the RACH opportunity, N>=1, and the i-th SSB (i=0 ,...,N-1), a preamble with preamble index=ra-PreambleStartIndex+i is used for random access to the corresponding slice. If N<1, a preamble with preamble index=ra-PreambleStartIndex is used for random access to the corresponding slice.

[0175] ra-AssociationPeriodIndex INTEGER(0..15) OPTIONAL, --Index of the association period within the Need R / / slice-SpecificPeriod. The UE can initiate random access to the specific slice corresponding to this slice-SpecificResources, using the preamble indicated by ra-PreambleStartIndex and the rach occasion indicated by ra-ssb-OccasionMaskIndex.

[0176] ra-ssb-OccasionMaskIndexINTEGER(0..15)OPTIONAL--Need R FIG. 8 shows an example of one-to-one mapping between some / specific RACH resources (RACH opportunities and / or preambles) of common RACH resources (RACH opportunities and / or preambles) and network slices, with relevant parameters shown below.

[0177] K=4 (the number of slices that are configured with a particular RACH resource) NTOT=4 (total number of SSBs) ssb-perRACH-Occasion:N=2 PRACH configuration index = 12 (PRACH configuration period = 2 radio frames) Msg1-FDM=1 Association Period = 2 (number of PRACH establishment periods) For example, if slice-SpecificPeriod is set to 2 (the number of association periods), The number of slices served in each PRACH establishment period is K×NTOT / (si-RequestPeriod*Association Period)=(4*4) / (2*2)=4.

[0178] The number of RACH opportunities in each PRACH configuration period is 1 (ie, Msg1-FDM). => The number of slices served on each RACH opportunity is 4 => The number of preambles required for slicing is equal to 4 The following configurations for different slices can be set as follows, and the association between the preamble and the network slice is as shown in FIG. 8.

[0179] For slice 1: ra-PreambleStartIndex=60, ra-AssociationPeriodIndex=0 For slice 2: ra-PreambleStartIndex=62, ra-AssociationPeriodIndex=0 For slice 3: ra-PreambleStartIndex=60, ra-AssociationPeriodIndex=1 For slice 4: ra-PreambleStartIndex=62, ra-AssociationPeriodIndex=1 In one embodiment, a one-to-one mapping between some / specific RACH resources (RACH opportunities and / or preambles) of common RACH resources (RACH opportunities and / or preambles) may be associated with a network slice group by:

[0180] slicegroup-SpecificPeriod ENUMERATED {1 ,2,4,6,8,10,12,16} OPTIONAL,--Need R / / Periodicity of slice group specific configuration in number of association periods slicegroup-SpecificResources SEQUENCE(SIZE(1..maxnumberofslicegroup)) OF Slicegroup-SpecificResources / / The max size is the maximum number of slice groups when RACH resources are configured per slice group.

[0181] Slicegroup-SpecificResources::=SEQUENCE{ra-PreambleStartIndexINTEGER(0...63), / / If N SSBs are associated with the RACH opportunity, N>=1, and for the i-th SSB (i=0,...,N-1), the preamble with preamble index = ra-PreambleStartIndex+i is used for random access to the corresponding slice group. If N<1, the preamble with preamble index = ra-PreambleStartIndex is used for random access to the corresponding slice group.

[0182] ra-AssociationPeriodIndex INTEGER(0..15) OPTIONAL, --Index of the association period in Need R / / slicegroup-Specific. The UE can initiate random access to the specific slice group corresponding to this slicegroup-SpecificResources, using the preamble indicated by ra-PreambleStartIndex and the rach occasion indicated by ra-ssb-OccasionMaskIndex.

[0183] ra-ssb-OccasionMaskIndexINTEGER(0..15)OPTIONAL--Need R In one embodiment, a one-to-one mapping between some / specific RACH resources (RACH opportunities and / or preambles) of common RACH resources (RACH opportunities and / or preambles) may be associated to an access category by:

[0184] accessCategory-SpecificPeriod ENUMERATED {1,2,4,6,8,10,12,16} OPTIONAL,--Need R / / Periodicity of access category specific configuration in number of association periods accessCategory-SpecificResources SEQUENCE(SIZE(1..maxAccessCatForSlice))OF AccessCategory-SpecificResources AccessCategory-SpecificResources::=SEQUENCE { ra-PreambleStartIndexINTEGER(0..63), / / If N SSBs are associated with a RACH opportunity, N>=1, and for the i-th SSB (i=0,...,N-1), the preamble with preamble index=ra-PreambleStartIndex+i is used for random access to the corresponding access category. If N<1, the preamble with preamble index=ra-PreambleStartIndex is used for random access to the corresponding access category.

[0185] ra-AssociationPeriodIndex INTEGER(0..15) OPTIONAL, --Need R / / Index of the association period in the accessCategory-SpecificPeriod. The UE must be able to use the specific access category resources that correspond to this accessCategory-SpecificcResources. The random access to the rach may be initiated using the preamble indicated by ra-PreambleStartIndex and the rach occasion indicated by ra-ssb-OccasionMaskIndex.

[0186] ra-ssb-OccasionMaskIndexINTEGER(0..15)OPTIONAL--Need R In one embodiment, a one-to-one mapping between some / specific RACH resources (RACH opportunities and / or preambles) of common RACH resources (RACH opportunities and / or preambles) may be associated with an access category group by:

[0187] accessCategoryGroup-SpecificPeriod ENUMERATED {1,2,4,6,8,10,12,16} OPTIONAL,--Need R / / Periodicity of access category group specific configuration in number of association periods accessCategoryGroup-SpecificResources SEQUENCE(SIZE(1..maxAccessCatGroupForSlice))OF AccessCategoryGroup-SpecificResources AccessCategoryGroup-SpecificResources::=SEQUENCE { ra-PreambleStartIndexINTEGER(0..63), / / If N SSBs are associated with a RACH opportunity, N>=1, and for the i-th SSB (i=0,...,N-1), the preamble with preamble index=ra-PreambleStartIndex+i is used for random access to the corresponding access category group. If N<1, the preamble with preamble index=ra-PreambleStartIndex is used for random access to the corresponding access category group.

[0188] ra-AssociationPeriodIndex INTEGER(0..15) OPTIONAL, --Need R / / Index of the association period within the accessCategoryGroup-SpecificPeriod. The UE can initiate random access to the specific access category corresponding to this accessCategoryGroup-SpecificcResources, using the preamble indicated by ra-PreambleStartIndex and the rach occasion indicated by ra-ssb-OccasionMaskIndex.

[0189] ra-ssb-OccasionMaskIndexINTEGER(0..15)OPTIONAL--Need R In one embodiment, the slice-specific or access category-specific RACH resource information indicates an association between the resources indicated by the slice-specific or access category-specific RACH resource information and one of a network slice, a network slice group, an access category or an access category group.

[0190] In one embodiment, a particular RACH resource, or a portion of the common RACH resources (RACH opportunities and / or preambles), may be associated with one of a network slice, a network slice group, an access category, or an access category group.

[0191] In one embodiment, a particular preamble, or a portion of a common preamble, may be associated with one of a network slice, a network slice group, an access category, or an access category group.

[0192] FIG. 9 illustrates an example of a common RACH resource configuration according to one embodiment of the present disclosure, with relevant parameters indicated as follows:

[0193] NTOT=4 (total number of SSBs) ssb-perRACH-Occasion:N=2 CB-PreamblesPerSSB:R=8 PRACH configuration index = 12 (PRACH configuration period = 2 radio frames) Msg1-FDM=1

[0194]

number

[0195] In one embodiment, the specific slice RACH resource information may include (e.g., indicate) a preamble start index (e.g., ra-PreambleStartIndex) and the number of consecutive preambles to indicate an association between a specific preamble, or a portion of a common preamble, and one of a network slice, a network slice group, an access category, or an access category group. For example, preambles 0-3 and 31-34 (i.e., preambles having indexes 0 to 3 and 31 to 34) of each SSB shown in FIG. 9 may be reserved for a specific network slice, a network slice group, an access category, or an access category group by the following configuration:

[0196] ra-PreambleStartIndex=0, Number of consecutive preambles=4; and ra-PreambleStartIndex=31, Number of consecutive preambles=4 In one embodiment, the specific slice RACH resource information may include (e.g., indicate) a preamble start index and a step number to indicate an association between a specific preamble, or a portion of a common preamble, and one of a network slice, a network slice group, an access category, or an access category group. For example, preambles 0, 2, 4, 6, and 31, 33 of each SSB shown in FIG. 35 37 may be reserved for a specific network slice, network slice group, access category or access category group in the following configurations:

[0197] ra-PreambleStartIndex=0 and 31, Step=2 In one embodiment, the specific slice RACH resource information may include (e.g., indicate) a preamble mask index that is utilized to indicate a preamble mask that constitutes an association between a specific preamble, or a portion of a common preamble, and one of a network slice, a network slice group, an access category, or an access category group. FIG. 10 illustrates an example of a table of preamble masks according to one embodiment of the present disclosure. Based on the table illustrated in FIG. 10, the preamble 0 of each SSB illustrated in FIG. 9 may be 2 4 6 and 30 32 34 36 can reserve a specific network slice, network slice group, access category or access category group by configuring preamble mask index=1.

[0198] In one embodiment, a particular opportunity (e.g., a RACH opportunity) or a portion of a common opportunity may be associated with one of a network slice, a network slice group, an access category, or an access category group.

[0199] FIG. 11 illustrates an example of a common RACH resource configuration according to one embodiment of the present disclosure, with relevant parameters shown as follows:

[0200] NTOT=4 (total number of SSBs) ssb-per-RACH-Occasion:N=1 / 2 CB-PreamblesPerSSB:R=8 PRACH configuration index = 12 (PRACH configuration period = 2 radio frames) Msg1-FDM=1

[0201]

number

[0202] In one embodiment, the particular slice RACH resource information may include (e.g., indicate) an opportunity list (e.g., ra-OccasionList) per network slice / network slice group / access category / access category group to indicate an association between a particular opportunity, or a portion of a common opportunity, and one of a network slice, a network slice group, an access category, or an access category group.

[0203] In one embodiment, the ASN.1 coding of the opportunity list may be shown as follows: Association period = 8 * PRACH setup period Association pattern cycle = 1 association period Figure 12 shows an example of an association between some of the common ROs and one of the network slices, network slice groups, access categories, or access category groups. In Figure 12, the ROs corresponding to subframe numbers 0, 6, 8, and 14 (i.e., the ROs shown with dashed lines) are held in the following configuration for a particular network slice, network slice group, access category, or access category group:

[0204] SSB#0:ra-OccasionList:#0 SSB#1:ra-OccasionList:#3 SSB#2:ra-OccasionList:#4 SSB#3:ra-OccasionList:#7 In one embodiment, the particular slice RACH resource information may include (e.g., indicate) an opportunity mask index to indicate an opportunity mask that constitutes an association between a particular opportunity, or a portion of a common opportunity, and one of a network slice, a network slice group, an access category, or an access category group.

[0205] 13 shows an example of a table of opportunity masks according to an embodiment of the present disclosure. According to the table shown in FIG. 13, by configuring the opportunity mask index with a value of 9, an even number of ROs can be reserved for a specific network slice, network slice group, access category, or access category group, respectively.

[0206] Figure 14 shows an example of an association between some of the common ROs and one of the network slices, network slice groups, access categories or access category groups. In Figure 14, the opportunity mask index is configured with a value of 9. Thus, the ROs marked with dashed lines are held for a particular network slice, network slice group, access category or access category group.

[0207] In one embodiment, when a UE receives multiple slice-specific or access category-specific RACH resource information (e.g., specific RACH resource configurations and / or parameters), the UE may utilize (e.g., apply) a particular one of the slice-specific or access category-specific RACH resource information to perform the random access procedure.

[0208] In one embodiment, the UE utilizes default slice-specific or access category-specific RACH resource information associated with at least one of the network slice, network slice group, access category, and access category group of the received slice-specific RACH resource information to perform the random access procedure.

[0209] In one embodiment, the UE utilizes slice-specific or access category-specific RACH resource information corresponding to a recently used network slice, slice group, access category, or access category group to perform the random access procedure. For example, the recently used network slice, slice group, access category, or access category group may be a network slice, slice group, access category, or access category group used by the UE in a period before selecting a cell. In another example, the recently used network slice, slice group, access category, or access category group is the latest network slice, slice group, access category, or access category group used by the UE. In yet another example, the recently used network slice, slice group, access category, or access category group is the most recently used network slice, slice group, access category, or access category group.

[0210] In one embodiment, if slice-specific or access category-specific RACH resource information is not provided to the UE, the UE initiates random access based on common RACH resources and parameters.

[0211] In one embodiment, the slice-specific or access category-specific RACH resource information is included in one of the system information or RRC signaling.

[0212] 15 illustrates a process according to one embodiment of the present disclosure. The process illustrated in FIG. 15 may be used in a radio network node (e.g., a RAN or an NG-RAN) and may include the following steps:

[0213] Step 1500: receiving an aggregate maximum data rate per UE; and Step 1502: Perform data rate control based on an aggregate maximum data rate per UE.

[0214] Specifically, the radio network node receives an aggregate maximum data rate per UE (e.g., slice-specific aggregate maximum bit rate (AMBR)) from a network (e.g., a core network) or another radio network node. It should be noted that the aggregate maximum data rate configured per UE may also be configured per network slice (step 1500). Based on the received aggregate maximum data rate per UE, the UE performs data rate control, e.g., based on the network slice.

[0215] In one embodiment where the slice-specific AMBR is received from the core network, the slice-specific AMBR is received in the INITIAL CONTEXT SETUP REQUEST. The PDU may be included in at least one of the following messages: PDU PERIOD CONTEXT SETUP REQUEST, PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE MODIFY REQUEST, or HANDOVER REQUEST.

[0216] In one embodiment, a radio network node can receive a slice-specific AMBR from another radio network node (e.g., a gNB). In one embodiment, the slice-specific AMBR can be received in response to a HANDOVER REQUEST, an S-NODE ADDITION REQUEST, an S-NODE MODIFICATION REQUEST, a RETRIEVE UE The slice-specific AMBR may be included in at least one of the following: HandoverCommand, HandoverPreparationInformation, CG-Config, or CG-ConfigInfo. In one embodiment, the slice-specific AMBR may be included in an inter-node radio resource control (RRC) message. For example, the inter-node RRC message may include at least one of HandoverCommand, HandoverPreparationInformation, CG-Config, or CG-ConfigInfo.

[0217] In one embodiment, the radio network node is a gNB distributed unit (gNB-DU) and receives the slice-specific AMBR from a gNB centralized unit (gNB-CU), in which the slice-specific AMBR is included in at least one of a UE CONTEXT SETUP REQUEST or a UE CONTEXT MODIFICATION REQUEST.

[0218] In one embodiment, to generate a session AMBR (e.g., maximum UL and DL data rates per UE per slice (i.e., slice-specific AMBR) in a session management function (SMF), a maximum UL and DL data rate per UE per PDU session is taken into account, and a radio network node (e.g., RAN) implements the session AMBR in data rate control.

[0219] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented only as examples and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand exemplary features and functions of the present disclosure. However, those skilled in the art will understand that the present disclosure is not limited to the exemplary architectures or configurations depicted, but can be implemented using various alternative architectures and configurations. Furthermore, as will be appreciated by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0220] It is also understood that any reference to an element herein using a designation such as "first," "second," etc., generally does not limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to a first and a second element does not imply that only two elements may be used or that the first element must precede the second element in any way.

[0221] Further, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. , commands, information, signals, bits and symbols may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0222] Those skilled in the art will further appreciate that any of the various illustrative logical blocks, units, processors, means, circuits, methods, and functions described in connection with the embodiments disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design code incorporating instructions (which for convenience may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0223] To clearly illustrate this interchangeability of hardware, firmware, and software, various exemplary components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, and such implementation decisions do not depart from the scope of the present disclosure. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. may be configured to perform one or more of the functions described herein. The term "configured to" or "configured for" as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0224] Further, those skilled in the art will appreciate that the various exemplary logical blocks, units, devices, components, and circuits described herein can be implemented in or performed by an integrated circuit (IC), which 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, or any combination thereof. The logical blocks, units, and circuits may further include an antenna and / or a transceiver for communicating with various components in a network or device. The general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein. When implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0225] Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0226] The term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for purposes of explanation, various units are described as separate units, but as will be apparent to one skilled in the art, two or more units may be combined to form a single unit that performs the relevant functions according to embodiments of the present disclosure.

[0227] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of the present disclosure. For clarity, it will be appreciated that the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the present disclosure. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are merely to suitable means for providing the described functions, rather than to a strict logical or physical structure or organization.

[0228] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method for use in a wireless terminal, comprising: receiving cell selection information associated with at least one network slice or at least one access category from a radio network node; selecting a cell based on the cell selection information; A wireless communication method comprising:

2. 2. The wireless communication method of claim 1, wherein the at least one network slice is a plurality of network slices, including network slices supported by the radio network node.

3. 3. The wireless communication method of claim 2, wherein the cell selection information indicates a single network slice selection assistance information S-NSSAI for each of the at least one network slice, a slice / service type SST field of the S-NSSAI, or multiple most significant bits MSBs of the S-NSSAI.

4. The wireless communication method according to claim 3, wherein at least one S-NSSAI of the at least one network slice is classified by a plurality of S-NSSAI groups, and the cell selection information indicates at least one of the plurality of S-NSSAI groups.

5. The wireless communication method according to claim 1 , wherein the cell selection information includes at least one cell reselection priority associated with the at least one network slice or the at least one access category.

6. The wireless communication method according to claim 5 , wherein the at least one reselection priority is set for each network slice.

7. The wireless communication method of claim 6, wherein the cell selection information includes at least one of an S-NSSAI of a network slice corresponding to the at least one reselection priority, an SST field of the S-NSSAI, or a plurality of MSBs of the S-NSSAI.

8. The wireless communication method according to any one of claims 5 to 7, wherein the at least one network slice is classified into a plurality of network slice groups, and the at least one reselection priority is set for each network slice group.

9. The wireless communication method according to claim 8, wherein the cell selection information includes one of a group identification ID of the network slice group corresponding to the at least one reselection priority set for each network slice group, or a list.

10. The wireless communication method according to claim 5 , wherein the at least one reselection priority is set for each access category or for each access category group.

11. The wireless communication method according to any one of claims 5 to 10, wherein the cell is selected based on a default cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group in the at least one cell reselection priority.

12. The cell is selected based on a particular cell reselection priority among the at least one reselection priority, and the particular cell reselection priority is determined based on the particular cell reselection priority of the radio communication system during a period prior to selecting the cell. The wireless communication method according to claim 5 , corresponding to one of a network slice, a network slice group, an access category, or an access category group used by a terminal.

13. The wireless communication method according to any one of claims 1 to 12, wherein the cell selection information is in one of system information or radio resource control (RRC) signalling.

14. A wireless communication method for use in a wireless communication node, comprising:

1. A wireless communication method comprising: transmitting cell selection information associated with at least one network slice or at least one access category to a wireless terminal.

15. 15. The wireless communication method of claim 14, wherein the at least one network slice is a plurality of network slices, including network slices supported by the radio network node.

16. The wireless communication method of claim 15, wherein the cell selection information indicates a single network slice selection assistance information S-NSSAI for each of the at least one network slice, or a slice / service type SST field of the S-NSSAI, or multiple most significant bits MSBs of the S-NSSAI.

17. The wireless communication method of claim 16, wherein at least one S-NSSAI of the at least one network slice is classified by a plurality of S-NSSAI groups, and the cell selection information indicates at least one of the plurality of S-NSSAI groups.

18. The wireless communication method according to claim 14 , wherein the cell selection information comprises at least one cell reselection priority associated with the at least one network slice or the at least one access category.

19. The wireless communication method of claim 18 , wherein the at least one reselection priority is set per network slice.

20. The wireless communication method of claim 19, wherein the cell selection information includes at least one of an S-NSSAI of a network slice corresponding to the at least one reselection priority, an SST field of the S-NSSAI, or a plurality of MSBs of the S-NSSAI.

21. The wireless communication method according to any one of claims 18 to 20, wherein the at least one network slice is classified into a plurality of network slice groups, and the at least one reselection priority is set for each network slice group.

22. The wireless communication method according to claim 21, wherein the cell selection information includes one of a group ID or a list of the network slice groups corresponding to the at least one reselection priority set for each network slice group.

23. The wireless communication method according to claim 18 , wherein the at least one reselection priority is set for each access category or for each access category group.

24. 18 or 19, wherein the cell is selected based on a default cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group in the at least one cell reselection priority.

24. A wireless communication method according to claim 23.

25. 24. The wireless communication method according to claim 18, wherein the cell is selected based on a particular cell reselection priority among the at least one reselection priority, the particular cell reselection priority corresponding to one of a network slice, a network slice group, an access category, or an access category group used by the wireless terminal in a period prior to selecting the cell.

26. 26. The wireless communication method of any one of claims 14 to 25, wherein the cell selection information is in one of system information or radio resource control (RRC) signaling.

27. A wireless communication method for use in a wireless terminal, comprising: receiving resource information associated with at least one network slice or at least one access category from a radio network node; performing a random access procedure based on the resource information; and A wireless communication method comprising:

28. 28. The wireless communication method of claim 27, wherein the resource information is configured for at least one of the at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

29. The wireless communication method according to claim 27 or 28, wherein the resource information indicates a random access channel RACH resource for the random access procedure.

30. 30. The wireless communication method of claim 29, wherein the resource information includes at least one of a specific prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, or ra-ResponseWindow.

31. 29. The wireless communication method of claim 27 or 28, wherein the resource information indicates at least one search space for the random access procedure.

32. The wireless communication method according to any one of claims 27 to 31, wherein the at least one network slice is classified into a plurality of network slice groups, and each of the plurality of network slice groups corresponds to a particular resource information in the resource information.

33. The wireless communication method according to any one of claims 27 to 31, wherein the at least one access category or at least one access category group corresponds to a particular resource information in the resource information.

34. The wireless communication method according to any one of claims 27 to 33, wherein the resource information indicates an association between a resource indicated by the resource information and one of the at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

35. The resource indicated by the resource information and the at least one network 35. The wireless communication method of claim 34, wherein a preamble or RACH opportunity indicated by the resource information is associated with the at least one network slice, the at least one network slice group, the at least one access category, or the at least one access category group by associating the preamble or RACH opportunity indicated by the resource information with the at least one network slice, the at least one network slice group, the at least one access category, or the at least one access category group.

36. The wireless communication method according to any one of claims 27 to 35, wherein the random access procedure is performed based on default resource information corresponding to one of a network slice, a network slice group, an access category, or an access category group in the received resource information.

37. 36. The wireless communication method according to claim 27, wherein the random access procedure is performed based on specific resource information in the received resource information, the specific resource information corresponding to one of a network slice, a network slice group, an access category, or an access category group used by the wireless terminal in a period prior to selecting the cell.

38. 38. The wireless communication method of claim 27, wherein the resource information is in one of system information or RRC signaling.

39. 1. A wireless communication method for use in a radio network node, comprising: A wireless communication method comprising: transmitting resource information associated with at least one network slice or at least one access category to a wireless terminal.

40. 40. The wireless communication method of claim 39, wherein the resource information is configured for at least one of the at least one network slice, at least one network slice group, at least one access category, or at least one access category group.

41. 41. The wireless communication method according to claim 39 or 40, wherein the resource information indicates a random access channel RACH resource for the random access procedure.

42. 42. The wireless communication method of claim 41, wherein the resource information includes at least one of a specific prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, or ra-ResponseWindow.

43. 41. The wireless communication method of claim 39 or 40, wherein the resource information indicates at least one search space for the random access procedure.

44. The wireless communication method according to any one of claims 39 to 43, wherein the at least one network slice is classified into a plurality of network slice groups, and each of the plurality of network slice groups corresponds to a particular resource information in the resource information.

45. The at least one access category or the at least one access category 44. The wireless communication method of claim 39, wherein a group corresponds to a particular resource information in the resource information.

46. 46. ​​The wireless communication method according to claim 39, wherein the resource information indicates an association of a resource indicated by the resource information with one of the at least one network slice, the at least one network slice group, the at least one access category, or the at least one access category group.

47. 47. The wireless communication method of claim 46, wherein the resource indicated by the resource information and one of the at least one network slice, the at least one network slice group, the at least one access category, or the at least one access category group are associated by associating a preamble or a RACH opportunity of the resource indicated by the resource information with one of the at least one network slice, the at least one network slice group, the at least one access category, or the at least one access category group.

48. The wireless communication method according to any one of claims 39 to 47, wherein the random access procedure is performed based on default resource information associated with one of a network slice, a network slice group, an access category, or an access category group in the received resource information.

49. 48. The wireless communication method according to claim 39, wherein the random access procedure is performed based on specific resource information in the received resource information, the specific resource information corresponding to one of a network slice, a network slice group, an access category, or an access category group used by the wireless terminal in a period prior to selecting the cell.

50. 50. The wireless communication method of claim 39, wherein the resource information is in one of system information or RRC signaling.

51. 1. A wireless communication method for use in a radio network node, comprising: receiving an aggregate maximum data rate associated with at least one network slice; performing data rate control based on the aggregate maximum data rate; A wireless communication method comprising:

52. 52. The wireless communication method of claim 51 , wherein the aggregate maximum data rate associated with the at least one network slice is in at least one of an INITIAL CONTEXT SETUP REQUEST, a PDU SESSION RESOURCE SETUP REQUEST, a PDU SESSION RESOURCE MODIFY REQUEST, or a HANDOVER REQUEST.

53. 52. The wireless communication method of claim 51 , wherein the aggregate maximum data rate associated with the at least one network slice is in at least one of a HANDOVER REQUEST, an S-NODE ADDITION REQUEST, an S-NODE MODIFICATION REQUEST, or a RETRIEVE UE CONTEXT RESPONSE.

54. 52. The wireless communication method of claim 51, wherein the aggregate maximum data rate associated with the at least one network slice is in at least one inter-node radio resource control (RRC) message.

55. 55. The wireless communication method of claim 54, wherein the at least one inter-node RRC message includes at least one of a HandoverCommand, a HandoverPreparationInformation, a CG-Config, or a CG-ConfigInfo.

56. The aggregate maximum data rate associated with the at least one network slice is determined by a UE CONTEXT SETUP REQUEST or a UE CONTEXT 52. The wireless communication method of claim 51, in at least one of a MODIFICATION REQUEST.

57. a communication unit configured to receive cell selection information associated with at least one network slice or at least one access category from a radio network node; a processor configured to select a cell based on the cell selection information; A wireless terminal comprising:

58. 58. The wireless terminal of claim 57, wherein the processor is further configured to perform a wireless communication method as defined in any one of claims 2 to 13.

59. A radio network node comprising: a communication unit configured to transmit cell selection information associated with at least one network slice or at least one access category to a wireless terminal.

60. 60. A radio network node according to claim 59, further comprising a processor configured to perform a wireless communication method according to any one of claims 15 to 27.

61. a communication unit configured to receive resource information associated with at least one network slice or at least one access category from a radio network node; a processor configured to perform a random access procedure based on the resource information; A wireless terminal comprising:

62. 62. The wireless terminal of claim 61, wherein the processor is further configured to perform a wireless communication method as defined in any one of claims 29 to 38.

63. A communication unit configured to transmit resource information associated with at least one network slice or at least one access category to a wireless terminal. A wireless network node comprising:

64. 64. The wireless network of claim 63, further comprising a processor configured to perform the wireless communication method of any one of claims 40 to 50.

65. a communication unit configured to receive an aggregate maximum data rate associated with at least one network slice; a processor configured to perform data rate control based on the aggregate maximum data rate; Processor and A wireless network node comprising:

66. 66. The radio network node of claim 65, wherein the processor is further configured to perform a wireless communication method as claimed in any one of claims 52 to 56.

67. 58. A computer program product comprising a computer readable program medium code stored thereon, said code, when executed by a processor, causing said processor to perform a method according to any one of claims 1 to 57.

Images