RAN support for network slicing

By notifying the UE of network slice information from the base station and using slice-specific RACH configuration and offset mechanism, the problem of insufficient network slice support in the RAN is solved, network performance and connection quality are improved, and the diverse needs of vertical markets are met.

CN123075730APending Publication Date: 2026-11-10GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611082679.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-08-05
Filing Date
2021-08-04
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing technologies have paid little attention to network slicing support for radio access networks (RANs), resulting in the underutilization of opportunities to improve network performance.

Method used

The base station notifies the user equipment (UE) of the supported network slice information. The UE requests network support information as needed and performs cell selection and reselection through slice-specific RACH configuration and offset mechanism to optimize network connectivity.

Benefits of technology

It improves the efficiency of UE network slice selection in RAN, enhances network performance and connection quality, and meets the flexibility and scalability of vertical markets with different performance requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075730A_ABST
    Figure CN123075730A_ABST
Patent Text Reader

Abstract

This disclosure relates to RAN support for network slicing. In a method implemented in a base station, the base station is configured to communicate with a user equipment located in a coverage area of ​​a cell associated with the base station. The base station generates one or more first messages, which collectively indicate a set of one or more network slices (e.g., NSSAI or S-NSSAI) supported by the cell and one or more offsets associated with the set of network slices. The one or more offsets are one or more cell selection offsets that the user equipment can use when determining the suitability of a cell for cell selection, or one or more cell reselection offsets that the user equipment can use when determining the ranking of one or more cells for cell reselection. The base station transmits (310) one or more first messages (e.g., including SIB or dedicated RRC messages) to the user equipment.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Case Analysis

[0002] This application is a divisional application of Chinese invention patent application 202180054436.7, filed on August 4, 2021. Technical Field

[0003] This disclosure relates generally to wireless communications, and more specifically to radio access networks and network slicing. Background Technology

[0004] The increased connectivity and mobility enable transformation and innovation across numerous industries (e.g., manufacturing, transportation, energy, government, healthcare, etc.), resulting in a corresponding increase in demand for wireless communications in vertical markets. Applications / services in these vertical markets can have performance requirements with wide variations in parameters such as throughput, capacity, latency, mobility, and reliability. Network slicing (e.g., as provided in 5G networks under 3GPP Release 15) can provide a flexible and scalable network architecture supporting these diverse requirements by overlaying logical networks with different services onto the same physical network. However, to date, efforts supporting network slicing have focused almost exclusively on the core network (CN), with relatively less attention paid to the radio access network (RAN). Therefore, there is an opportunity to improve network performance by incorporating slice-based functionality into the RAN. Summary of the Invention

[0005] The base station disclosed herein can notify a user equipment (UE) about which network slices (also referred to herein as "(multiple) slices") are supported by the base station's cells, thereby allowing the UE to make faster decisions regarding network connectivity (e.g., whether to select the cell, or, if the cell is already a serving cell, whether to reselect to a different cell). In the implementations and scenarios discussed herein, each slice may, for example, correspond to Network Slice Selection Assistance Information (NSSAI), or to a "single NSSAI" (S-NSSAI) within an NSSAI. For example, the base station may broadcast slice information in a System Information Block (SIB) such as SIB1, or transmit slice information in an RRC message during a Radio Resource Control (RRC) reconfiguration, establishment, re-establishment, or connection recovery process. In some implementations, the base station provides slice information as a bitmap, where each bit corresponds to a different network slice.

[0006] In some implementations, the UE may request information from the base station as needed regarding network support for a specific slice of interest to the UE. For example, the UE may request such information when it is ready (or expects it to be ready soon) to transmit uplink data associated with a slice but the serving cell does not support that slice (or, in some implementations / scenarios, when the UE is ready to transmit uplink data and the serving cell chooses not to broadcast system information about which slice(s) it supports). The base station may respond, for example, by indicating the radio access technology (RAT), frequency, or neighboring cell identifier that supports the specific slice, and / or may provide other information that could accelerate changes to the UE's network connectivity that could contribute to supporting the slice (e.g., the random access channel (RACH) configuration the UE can use in neighboring cells that support the slice).

[0007] A UE can request network support information by sending a random access message (e.g., MsgA for a two-step contention-based RACH procedure or Msg1 for a four-step contention-based RACH procedure) to the base station using a RACH configuration (e.g., preamble and / or PRACH timing) specifically associated with the network slice of interest. Prior to the request, the base station may (e.g., in an SIB or dedicated RRC message) provide the UE with multiple dedicated slice-specific RACH configurations so that the UE can identify and use the appropriate RACH configuration when requesting network support information for a given slice. Upon receiving a random access message, the base station can determine / identify the slice based on which RACH configuration (e.g., which preamble and / or PRACH timing) the UE used to send the random access message. For example, the base station may then include the requested network support information for the slice in its response to the random access message (e.g., a modified Msg2 or MsgB). In some implementations and / or scenarios, the UE may request network support information for one or more slices using only dedicated slice-specific RACH configurations without attempting to obtain access to a channel of the current cell via the RACH procedure. For example, regardless of the current channel availability on the cell, the UE can remain in an idle or inactive state, thus the RACH procedure can be simplified. Therefore, as used herein, the term "RACH procedure" can refer to the complete RACH procedure (e.g., essentially as specified in the current RAT standard), or it can refer to only a part of such a procedure (e.g., without a corresponding HARQ process at the base station), and it is not necessarily required to use the procedure (or message, etc.) when attempting to obtain channel access.

[0008] In some implementations, the RAN uses offsets to direct the UE toward or away from certain cells based on whether a particular cell supports network slices that the UE needs (or prefers, expects, etc.) to utilize. For this purpose, base stations can transmit offsets used in cell selection and / or offsets used in cell reselection. For cell selection, each base station can broadcast its own positive and / or negative offsets, which UEs within range can then use when calculating cell fitness values ​​(e.g., by modifying the S-standard as defined in TS 38.304). For example, a UE can apply a positive offset (or no offset) to a first cell that supports at least one network slice of interest to the UE, and apply no offset (or a negative offset) to a second cell that does not support any network slice of interest to the UE.

[0009] For cell reselection, the serving base station can transmit its own (serving) cell offset, along with an indication of "popular" neighboring cells that support the same network slice as the serving cell or a subset of network slices. The UE can then use this information, along with its own slice requirements / preferences, to positively and / or negatively offset the ranking of the serving and neighboring cells (e.g., by modifying R as defined in TS 38.304). s and R n ).

[0010] Whether used for cell selection and / or cell reselection, offsets can be slice-specific (e.g., different offsets for each slice) or more generally applicable (e.g., a single offset that the UE applies or does not apply based on whether a cell supports at least one desired slice). In implementations where offsets are slice-specific, and in scenarios where the UE wants to support multiple slices, the UE can use various techniques to determine cell suitability or cell ranking (e.g., summing all offsets associated with the desired network slice, or using the maximum or minimum values ​​of these offsets, etc.).

[0011] An example embodiment of these technologies is a method in a base station configured to communicate with a user equipment located in a coverage area of ​​a cell associated with the base station, the method comprising: generating a first message by processing hardware of the base station indicating a set of one or more network slices supported by the cell; and transmitting the first message to the user equipment.

[0012] Another example embodiment of these technologies is a method in a user equipment configured to communicate with a base station when located in a coverage area of ​​a cell associated with a base station, the method comprising: receiving a first message from the base station; processing the first message by processing hardware of the user equipment to determine a set of one or more network slices supported by the cell; and determining, by the processing hardware and at least in part based on the set of network slices, whether to transmit data associated with the desired network slice via the cell. Attached Figure Description

[0013] Figure 1 The illustration shows an example wireless communication system in which the UE and base station can implement the techniques of this disclosure to provide RAN support for network slicing; Figure 2 yes Figure 1 The UE is based on its relationship with Figure 1 A block diagram of an example protocol stack for communication with one or more base stations; Figure 3 This is a message passing diagram illustrating an example scenario where the base station provides the UE with information about which slice(s) the base station supports, and the UE subsequently requests network support information for the unsupported slices. Figure 4A and Figure 4B This is a message passing diagram of an example procedure in which the UE uses a four-step contention-based RACH process to request network support information for a specific slice; Figure 5 This is a message passing diagram of an example procedure in which the UE uses a two-step contention-based RACH procedure to request network support information for a specific slice; Figures 6 to 8 This is a message passing diagram of an example scenario where the UE has data associated with multiple slices ready for uplink transmission; Figure 9 This is a message passing diagram of an example scenario in which the base station provides the UE with an offset during cell selection, turning the UE toward or away from the cell associated with the base station; Figure 10 This is a message passing diagram of an example scenario in which the serving base station provides the UE with one or more offsets to turn the UE toward or away from the serving cell and / or neighboring cells during cell reselection; Figure 11 and Figure 12 This is a flowchart illustrating an example method for informing the user equipment (UE) from both the base station and UE perspectives which slice(s) are supported by the base station; and Figure 13 and Figure 14 This is a flowchart of an example method for obtaining network support information for a slice using the RACH procedure from the perspectives of the base station and user equipment, respectively. Detailed Implementation

[0014] Figure 1 An example wireless communication system 100 is depicted in which UE 102 is configured to communicate with base stations 104A, 104B, and 104C (collectively referred to herein as "base station 104") at different times or in some scenarios and implementations that simultaneously support dual connectivity or carrier aggregation. UE 102 can be any suitable device capable of wirelessly communicating with base station 104 (e.g., any exemplary user equipment discussed below following the description of the figures). For example, base station 104 can include any one or more suitable types of base stations, such as evolved Node B (eNB), next-generation eNB (ng-eNB), and / or 5G Node B (gNB). Figure 1 In the example shown, each of the base stations in base station 104 is connected to the core network (CN) 110.

[0015] As a more specific example, base station 104A may be an eNB supporting an SI interface for communication with EPC 110 of CN 110, and base stations 104B and 104C may each be a gNB supporting an NG interface for communication with 5GC 112 of CN 110. In other implementations and / or scenarios, base stations 104A, 104B, and / or 104C may alternatively (or further) operate according to other types of Radio Access Technologies (RATs), and / or base stations 104A, 104B, and / or 104C may alternatively (or further) connect to other types of CNs. For example, base station 104A may operate as an ng-eNB and / or base station 104B may operate as an en-gNB. In different implementations, base stations 104A, 104B, and / or 104C implement the same or different RATs and support the same or different frequency bands. To directly exchange messages with each other during the various implementations and scenarios discussed below, base station 104 may support Xn and / or X2 interfaces, such as Figure 1 As shown.

[0016] In addition to other components, EPC 111 may include a Serving Gateway (S-GW) 112 and a Mobility Management Entity (MME) 114. S-GW 112 is typically configured to transmit user plane packets related to audio calls, video calls, Internet traffic, etc., and MME 114 is typically configured to manage authentication, registration, paging, and other related functions. 5GC 160 includes a User Plane Function (UPF) 162 and Access and Mobility Management Functions (AMF) 164, and / or Session Management Functions (SMF) 166. UPF 162 is typically configured to transmit user plane packets related to audio calls, video calls, Internet traffic, etc., AMF 164 is typically configured to manage authentication, registration, paging, and other related functions, and SMF 166 is typically configured to manage PDU sessions.

[0017] Typically, the wireless communication system 100 may include any suitable number of base stations supporting NR or EUTRA cells. More specifically, CN 110 may connect to any suitable number of base stations supporting NR and / or EUTRA cells. While the examples herein primarily refer to specific CN types EPC and 5GC, and specific RAT types EUTRA and 5G NR, in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies, such as sixth-generation (6G) radio access and / or 6G core networks.

[0018] exist Figure 1 In an example implementation, base station 104A covers cell 124A, base station 104B covers cell 124B, and base station 104C covers cell 124C. In cell 124A, UE 102 can use a RACH procedure to obtain access to an uplink channel for communicating with a corresponding base station 104. For example, UE 102 and base station 104A can support one or more RACH procedures. In one implementation, UE 102 and base station 104A only support a contention-based four-step RACH procedure. In another implementation (e.g., if base station 104A supports 5G NR RAT), UE 102 and base station 104A can support a contention-based four-step RACH procedure, a contention-based two-step RACH procedure, and a "fallback" procedure for changing from a two-step to a four-step RACH procedure. In cell 124A, other UEs ( Figure 1 (Not shown in the diagram) can also operate and sometimes attempts to obtain access to the same uplink channel (e.g., the same time-frequency resources used for uplink transmission) as UE 102. Other UEs may be similar to UE 102, or may be other types of devices that are similarly able to communicate with base station 104A via cell 124A using the same RACH procedure as UE 102.

[0019] like Figure 1 As shown, base station 104A is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., a central processing unit (CPU)) and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. Processing hardware 130 includes an access layer (AS) controller 132 and a slicing support unit 134. AS controller 132 typically supports AS layers (such as those described below). Figure 2 The processes at the AS layer (e.g., PHY, RRC, MAC, etc.) discussed. For example, AS controller 132 can control the RACH process, RRC message passing, etc. for base station 104. AS controller 132 can be a single controller, include multiple different controllers (e.g., RACH controller, RRC controller, PHY controller, etc.), or can be part of another controller.

[0020] Regarding the RACH procedure, AS controller 132 can configure the UE (e.g., UE 102) with a set of available time-frequency resources (e.g., PRACH timings). The UE can select a specific time-frequency resource from the set of available time-frequency resources to transmit the first message of the RACH procedure (e.g., MsgA or Msg1). AS controller 132 can also or alternatively configure the UE with a set of preambles, each preamble associated with a different PRACH timing, wherein any UE using a specific PRACH timing for the RACH procedure includes the corresponding preamble in the first RACH message (e.g., MsgA or Msg1). In one such implementation, AS controller 132 can also associate each preamble / PRACH timing with a different PUSCH timing (i.e., time-frequency resources for uplink data transmission), or possibly with a set of multiple different PUSCH timings, and the UE using a specific preamble and PRACH timing uses the corresponding PUSCH timing (or a timing from the set of corresponding PUSCH timings) to transmit or retransmit data (e.g., in MsgA or Msg3). Each time-frequency resource set and its associated preamble (and possibly other information, such as how many times the preamble is sent each time) constitute a single RACH configuration.

[0021] In some implementations, the AS controller 132 may also configure the UE with RACH resources dedicated / reserved for purposes other than channel access or for purposes other than channel access. Specifically, and as discussed in further detail below, the AS controller 132 may configure the UE with a specific RACH configuration dedicated to requesting network support information for a particular slice (e.g., a first RACH configuration for requesting information about a first slice, a second RACH configuration for requesting information about a second slice, etc.). Although the examples provided herein refer to requests for information about a particular slice (singular), it should be understood that such requests may also relate to one or more additional slices (e.g., a first RACH configuration reserved for requesting information about a set of two particular slices, a second RACH configuration reserved for requesting information about a set of five other slices, etc.).

[0022] Slice support unit 134 typically determines slice-specific network support information requested by the UE by receiving some or all of the information from other base stations (e.g., from base stations 104B and 104C via the X2 or Xn interface). Slice support unit 134 may be implemented by AS controller 132 and / or another controller of processing hardware 130. Slice support unit 134 may determine slice support information upon request from the UE, periodically, and / or according to some other suitable timing.

[0023] Base stations 104B and 104C are equipped with processing hardware that may be similar to processing hardware 130, but may differ in some respects (e.g., if different RATs are supported, and possibly by excluding slice support unit 134, etc.).

[0024] UE 102 is equipped with processing hardware 140, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. Processing hardware 140 includes AS controller 142, Non-Access Stratum (NAS) controller 144, and Slice Support Query Unit 146.

[0025] AS controller 142 typically supports AS layer (such as those described below) Figure 2 The discussion concerns the procedures at the AS layer (e.g., PHY, RRC, MAC, etc.). AS controller 142 can be a single controller, include multiple different controllers (e.g., RACH controller, RRC controller, PHY controller, etc.), or be part of another controller. AS controller 142 can control the RACH procedure, cell selection and reselection procedure, etc., for UE 102.

[0026] AS controller 142 can perform cell selection and reselection substantially as defined in 3GPP TS 38.304. For cell selection, AS controller 142 may consider a cell “fit” if it is part of a selected Public Land Mobile Network (PLMN) or a registered PLMN (or a PLMN in an equivalent list of PLMNs, etc.) and if it meets cell suitability criteria, which relate to various cell measurements (e.g., signal power and signal quality). For cell reselection, AS controller 142 may rank serving and neighboring cells based on similar cell measurements. However, in some implementations, when evaluating cell suitability criteria for cell selection and / or when ranking cells for cell reselection, AS controller 142 also applies an offset for a particular cell based on the support level for one or more slices of interest to UE 102. (Refer to below.) Figure 9 and Figure 10 Let's discuss this type of offset in more detail.

[0027] The 3GPP NR specification supports the configuration of dedicated priorities for use in cell reselection, where each priority corresponds to a different NR and / or RAT frequency. However, in some implementations, the network (e.g., base station 104A) may configure a UE, such as UE 102, with a specific set of frequency priorities (from multiple potential / candidate sets) based at least in part on slicing information. For example, UE 102 may have a pre-configured (stored) set of indices, where each index corresponds to a different set of frequency priorities. The base station (e.g., base station 104A) may then broadcast a specific index, and UE 102 may apply the priority set corresponding to that index. For example, the base station may select which index to broadcast based on the slices supported by the base station.

[0028] Alternatively, UE 102 may have a pre-configured (e.g., stored) set of geographic tag values, where each value corresponds to a different set of frequency priorities. For example, a geographic tag could be a Tracking Area Code (TAC), RAN Area Code, cell list, or Local Data Network (LADN) information. A base station (e.g., base station 104A) can broadcast a specific tag value (e.g., a specific TAC, a specific RAN Area Code, etc.), and UE 102 can apply the set of frequency priorities corresponding to that tag value. For example, the base station can select which tag value to broadcast based on the slice(s)(s) supported by the base station.

[0029] In either case (based on an index-based or tag-based set of frequency priorities), UE 102 may use the indicated set of frequency priorities during cell reselection. For example, UE 102 may more likely reselect to a cell that supports high-priority frequencies based on a set of frequencies indicated by an index or geographic tag value as specified in the current specification (3GPPTS 38.304).

[0030] NAS controller 144 typically supports procedures at the NAS layer, such as mobility management procedures. NAS controller 144 can be a single controller, include multiple different controllers, or be part of another controller (e.g., another controller that also includes AS controller 142). NAS controller 144 can communicate with AS controller 142 via Inter-Protocol Layer (IPL) messages. In some implementations, after one or more higher (application) layers notify NAS controller 144 of slice needs / preferences, NAS controller 144 uses IPL messages to inform AS controller 142 which slices UE 102 needs or prefers. For example, NAS controller 144 may provide this information specifically for cell selection or cell reselection purposes. NAS controller 144 may also inform AS controller 142 of the priorities associated with some or all desired slices, and / or provide an indication of whether each slice is a basic or non-basic slice.

[0031] In different implementations and / or scenarios, for example, each desired slice (e.g., each NSSAI) may correspond to a specific PDU session (e.g., an operator-defined PDU session, a PDU session that is always open, a PDU session with pending data, etc.), a "requested" NSSAI configured by the (home) network (e.g., as defined in 3GPP specification TS 23.501), a URSP (UE routing policy), or a local configuration of UE 102 (e.g., user configuration or OEM configuration). Typically, the slice of interest can be determined locally by UE 102 (e.g., based on which applications are running on UE 102), and / or can be configured by the network (e.g., via NAS messages received by UE 102 and NAS controller 144).

[0032] The network can also control, at least to some extent, how UE 102 uses desired slice information. For example, for the purpose of obtaining network support for a specific slice, AMF 164 can send a NAS message to UE 102 indicating whether UE 102 is allowed to perform cell selection and / or reselection. Based on this NAS message, NAS controller 144 can then include (or omit) a specific slice of interest from a list sent from NAS controller 144 to AS controller 142. For example, if AMF 164 (or another network node) has notified UE 102 that UE 102 is not allowed to perform cell selection or reselection based on that slice, NAS controller 144 can omit the desired slice from the list. AMF 164 (or another network node) can also configure UE 102 with additional restrictions regarding how the NAS layer (i.e., NAS controller 144) shares slices of interest with lower layers (i.e., with AS controller 142). For example, AMF 164 can instruct NAS controller 144 to share all desired NSSAIs with AS controller 142, share only the highest priority S-NSSAI of desired NSSAIs with AS controller 142, or not share any desired NSSAIs with AS controller 142, etc. In some implementations and / or scenarios, NAS controller 144 also or alternatively determines the sharing and use of desired slice information based on pre-configuration at UE 102 (e.g., user and / or OEM configuration).

[0033] The slice support query unit 146 can be implemented by the AS controller 142 and / or by another controller of the UE 102. Typically, the slice support query unit 146 performs one or more procedures for requesting slice-specific network support information from a base station (e.g., base station 104A). In some implementations, the slice support query unit 146 first identifies the slice for which network support information is desired. In implementations where the slice support query unit 146 is performed, for example by the AS controller 142, and after the NAS controller 144 provides the AS controller 142 with a list of desired slices, the slice support query unit 146 can compare this list with the slice support information received by the UE 102 from the base station (e.g., base station 104A). If the overlap between the desired slice and supported slices does not meet a specific criterion (e.g., the serving base station supports at least one or all desired slices, or all desired slices have at least one threshold priority level, etc.), the slice support query unit 146 initiates a slice support query procedure. As described below... Figures 3 to 5The query process discussed can be a dedicated / reserved RACH process that uses RACH configuration (i.e., a specific set of RACH resources, such as preambles and PRACH timings) to perform such a query, or it can be another type of process (e.g., UE 102 transmitting an RRC message that explicitly identifies a slice of its network support information request).

[0034] In some implementations, UE 102 may transmit its desired slice list (which may have priority values) to the serving base station. For example, UE 102 may transmit a list of slices (which may have priority values) to base station 104A. RRCConfigurationComplete The message includes such a list. Base station 104A can then use this desired slice information to locate better network support for one or more slices and may initiate changes to the network connectivity of UE 102. For example, base station 104A may determine that it does not support one, some, or all of the slices of interest to UE 102, and in response, (1) determine neighboring cells (and / or another RAT) that support (multiple) slices, and (2) perform a handover to a neighboring cell (e.g., cell 124B or 124C), or otherwise redirect UE 102 to a neighboring cell (and / or another RAT).

[0035] Figure 2 An example radio protocol stack 200 is illustrated in a simplified manner, which UE 102 can use to communicate with base station 104A (and possibly base stations 104B and 104C). In example stack 200, physical layer (PHY) 202 provides a transport channel to media access control (MAC) layer 204, which in turn provides a logical channel to radio link control (RLC) layer 206. RLC layer 206 then provides an RLC channel to packet data convergence protocol (PDCP) layer 208, which in turn communicates with RRC layer 210. RRC layer 210 encapsulates and interprets RRC protocol data units (PDUs), which may contain any of various types of RRC messages associated with different RRC procedures (e.g., connection establishment or re-establishment procedures, measurement reporting procedures, etc.). Layers 202 to 210 form at least a portion of access layer (AS) 212.

[0036] The Non-Access Layer (NAS) 214 of protocol stack 200 includes, among other possible layers, one or more Mobility Management (MM) layers 216 for handling registration, attachment, or tracking area update processes. (As in...) Figure 2As further shown, protocol stack 200 also supports higher-level protocols 218 for various services and applications. For example, higher-level protocols 218 may include Internet Protocol (IP), Transmission Control Protocol, and User Datagram Protocol (UDP).

[0037] In some implementations... Figure 1 The AS controllers 132 and 142 implement the process of AS 212, while Figure 1 The NAS controller 144 implements the process of NAS 214. Although Figure 2 The specific order of the layers 202, 204, 206, 208, 210, 216, and 218 is depicted; however, it should be understood that in some implementations and / or scenarios, one or more of the depicted layers may operate in a manner that does not strictly conform to the order shown. Furthermore, in other implementations, the UE 102 and the base station (e.g., base station 104A) may alternatively operate according to different protocol stacks.

[0038] Next, refer to Figures 3 to 10 This section discusses the various types of RAN-level procedures / functions that can be implemented by base station 104A and UE 102 (and in some cases, base station 104B and / or 104C). Specifically, Figure 3 This illustrates an example scenario where base station 104A provides UE 102 with information specifying which slice(s) base station 104A supports, and subsequently UE 102 requests network support information for different (unsupported) slices. Figure 4A , Figure 4B and Figure 5 The alternative RACH procedure that UE 102 can initiate to make such a request is shown. Figures 6 to 8 An example scenario is shown in which UE 102 has data associated with multiple slices ready for uplink transmission. Figure 9 An example scenario is shown in which base station 104 provides UE 102 with an offset that turns UE 102 toward or away from its associated cell during cell selection. Figure 10 An example scenario is shown in which base station 104A is serving UE 102 and provides UE 102 with one or more offsets during cell reselection, turning UE 102 toward or away from serving cell 124A and / or neighboring cells (e.g., cells 124B and 124C). Although Figures 3 to 10 And its accompanying description specifically mentions Figure 1 The following technologies are applicable to UE 102 and base station 104A (and in some cases base stations 104B and 104C), but it should be understood that the following technologies can be implemented by other user equipment and / or base stations, and / or can be used in addition to UE 102 and base station 104A (and in some cases base stations 104B and 104C). Figure 1 It is implemented in systems other than the wireless communication system 100.

[0039] First refer to Figure 3 In example scenario 300, base station 104A transmits message 310 to UE 102, indicating which slice or slice capabilities base station 104A supports. "Support" for a specific slice can mean, for example, that base station 104A can provide at least some minimum performance level required by the slice (e.g., low latency, high throughput, etc.), and / or it can mean that base station 104A identifies the slice (i.e., knows the performance level required by the slice), etc. Slice support information can be a bitmap, for example, where each bit of the bitmap corresponds to a different slice (e.g., based on a ranking / mapping known to UE 102).

[0040] In some implementations, base station 104A broadcasts a 310 slice capability message. For example, the slice capability message may be a System Information Block (SIB) and may include other system information in addition to slice capability / support information (e.g., SIB1). In other implementations, base station 104A transmits the 310 slice capability message only to UE 102. For example, the slice capability message may be a 310 message transmitted by UE 102 during an RRC reconfiguration process. RRCReconfiguration Message 310 transmitted by UE 102 during the RRC connection establishment process. RRCSetup Message, UE 102 transmits 310 during RRC re-establishment process RRCReestablishment Message, or UE 102 transmitting 310 during the RRC connection restoration process. RRCResume or RRCSetup Messages (e.g., because various RRC procedures are defined in 3GPP TS 38.331). In some implementations, the slice support unit 134 generates slice capability messages, or generates specific portions of messages related to slice capabilities.

[0041] At some point thereafter (or, in other implementations and / or scenarios, before event 310), UE102 determines that 314 is associated with a specific network slice (in Figure 3Data associated with the first network slice (arbitrarily referred to as the "first" network slice) is ready for transmission. Alternatively, UE 102 may determine 314 that data associated with the first network slice is expected to be ready for transmission soon (e.g., in response to the launch of an application attempting to utilize the first network slice). Event 314 may include an application (e.g., at a layer implementing one of protocols 218) requesting the first network slice from NAS controller 144 via a first IPL message, and NAS controller 144 subsequently requesting the first network slice from AS controller 142 via a second IPL message. Data associated with the first network slice may have a slice-specific priority level configured by the network (e.g., by base station 104A). Alternatively, the priority level may be predefined (e.g., by the OEM). In either case, NAS controller 144 may notify AS controller 142 of the priority level of the first network slice.

[0042] UE 102 (e.g., AS controller 142, in response to the second IPL message) can then determine 318 whether the first network slice is supported by serving cell 124A by comparing the first network slice with a list of supported slices received from base station 104A at event 310. In example scenario 300, UE 102 determines 318 that serving cell 124A does not support the first network slice. In other scenarios, UE 102 may alternatively determine 318 that serving cell 124A does support the first network slice, in which case events 320, 330, 332, and 340 (described below) may be omitted, and UE 102 may alternatively use serving cell 124A to transmit any uplink data associated with the first network slice (and possibly receive downlink data).

[0043] In scenario 300, after determining that serving cell 124A (318) does not support the first network slice, UE 102 transmits a request message (320) to serving base station 104A. For example, slice support query unit 146 may trigger and / or generate the request message in response to determination (318). In response to the request message, base station 104A transmits a response message (330) to UE 102 providing network support information for the first network slice. In different implementations, the response message may be a RACH message (e.g., MsgB or Msg2), a broadcast message (e.g., SIB), or a dedicated RRC message (e.g., ...). RRCReconfiguration (message), or another suitable type of message.

[0044] Network support information includes information about one or more other network resources that can support the first network slice and that UE 102 may be able to use when transmitting data associated with the first network slice. For example, network support information may indicate the specific RAT supporting the first network slice, the frequency (e.g., channel, frequency band, etc.) supporting the first network slice, the physical cell identifiers of neighboring cells supporting the first network slice (e.g., cells 124B and / or 124C), the RACH configuration associated with the neighboring cells supporting the first network slice, and / or whether the neighboring cells supporting the first network slice also support one or more other specific network slices (e.g., other slices that UE 102 may also be interested in).

[0045] In some implementations, serving base station 104A collects some or all network support information (or other information from which base station 104A can derive network support information) from one or more base stations in neighboring cells before transmitting a 330 response message to UE 102. For example, base station 104A may receive information indicating support (or lack thereof) for at least a first network slice from base station 104B and / or base station 104C via the X2 or Xn interface. Base station 104A may request this information in response to receiving a request message at event 320, or may receive this information periodically, etc. In some implementations, base station 104A also or alternatively receives such information from CN 110 (e.g., in implementations where CN 110 stores information about slice support at various network nodes, or in implementations where base station 104A communicates via CN 110, etc.).

[0046] In some implementations, the slice support unit 134 generates a response message, or a specific portion of the response message related to network support for the first network slice. As described above, the slice support unit 134 may also collect network support information for the first network slice from neighboring base stations (e.g., base stations 104B and / or 104C) and / or from CN 110.

[0047] Events 320 and 330 are collectively referred to as procedure 332. Procedure 332 can be a special RACH procedure in which the request message of event 320 is a first random access message and the response message of event 330 is a second random access message. See below for reference. Figure 4A , Figure 4B and Figure 5Alternative implementations of this RACH procedure are discussed. In other implementations, the request and response messages are not random access messages. For example, UE 102 may transmit a first RRC (or other stratum) message 320 including a field specifying a first network slice, and base station 330 may respond by transmitting a second RRC (or other stratum) message 330 to UE 102 including one or more fields indicating network support information for the first network slice.

[0048] In some implementations and / or scenarios, even if base station 104A indicates (at event 310) support for the first network slice, UE 102 initiates procedure 332 (i.e., transmits request message 320). For example, if the quality of the radio link between UE 102 and base station 104A suddenly degrades at some later time and UE 102 must reselect to another cell, UE 102 may want to know which neighboring cells (and / or which RATs, frequencies, etc.) support the first network slice.

[0049] After UE 102 and base station 104A execute procedure 332 to notify UE 102 of network support for the first network slice, UE 102 and / or base station 104A may optionally execute 340 or one or more subsequent operations. For example, if base station 104A notifies UE 102 that cell 124B supports the first network slice, UE 102 may, in response, attempt to reselect to cell 124B and establish an RRC connection with base station 104B. As another example, in implementations and scenarios where execution procedure 332 includes performing a RACH procedure and where the RACH procedure results in UE 102 accessing a channel on cell 124A, base station 104A may use knowledge that UE 102 is interested in regarding the first network slice to configure UE 102 in a specific manner (e.g., to facilitate a faster connection with another base station). For example, base station 104A can schedule UE 102 to perform signal and / or channel quality measurements on cell 124B, thereby enabling UE 102 to connect to base station 104B via cell 124B faster than it would otherwise be possible. In one such implementation, if there is a reason for UE 102 to remain connected to base station 104A (e.g., if UE 102 has some data buffered at base station 104A), base station 104A can enable UE 102 to communicate with both base stations 104A and 104B simultaneously (e.g., in a multi-RAT dual connectivity scheme). As yet another example, if both base stations 104A and 104B support the same RAT (e.g., 5G NR), but only a specific frequency of base station 104B supports the first network slice, then base station 104A can initiate carrier aggregation using a first frequency supported by base station 104A and a different second frequency supported by base station 104B. In other scenarios (e.g., if no neighboring cell supports the first network slice and UE 102 decides to wait to transmit any associated data), UE 102 may take no action and event 340 may be omitted.

[0050] In other implementations and / or scenarios, UE 102 does not initiate procedure 332. For example, in response to determining that serving cell 124A does not support the first network slice, UE 102 may proceed to initiate a cell reselection procedure at event 340 to establish an RRC connection to the RAN via a different cell, instead of initiating procedure 332.

[0051] In some implementations and / or scenarios, after process 332 (e.g., during event 340), a (potentially new) serving base station (e.g., base station 104A, 104B, or 104C) transmits another message to UE 102 containing slice-specific network support information (e.g., any network support information similar to that discussed above with reference to event 330). For example, this message could be as defined in 3GPP TS 38.331. RRCReject or RRCRelease The UE 102 can then use the network support information in the message to select the cell on which it will reside, or to establish a connection to the network.

[0052] Figure 4A , Figure 4B and Figure 5 It shows Figure 3 Alternative implementations of process 332. Specifically, Figure 4A and Figure 4B Corresponding to process 332 is a four-step competition-based RACH process (in Figure 4A and Figure 4B The implementation methods are labeled as processes 432A and 432B respectively, and Figure 5 Corresponding to process 332 is a two-step competition-based RACH process (in... Figure 5 The implementation is marked as process 532. In other implementations, UE 102 and base station 104A may use a RACH process of a different type than process 332.

[0053] First refer to Figure 4A UE 102 initiates a four-step contention-based RACH procedure 432A by transmitting Msg1 (410A) to base station 104A, possibly while UE 102 is camped on cell 124A and is in an idle or inactive state. As in a regular RACH procedure (e.g., as specified in 3GPP ETE or NR specifications), Msg1 includes a preamble sequence and is transmitted via PRACH timing. Depending on the implementation, the preamble and / or PRACH timing may be specifically dedicated / reserved for requesting network support information for a first network slice (e.g., as combined below). Figure 4B (To be discussed further), or it could also be used for preamble and / or PRACH timing in standard channel access attempts.

[0054] After receiving Msg1, base station 104A transmits Msg2 (Random Access Response, or "RAR") to UE 102 via 416A. In some implementations, Msg1 transmitted by base station 104A via 410A includes CORESET and / or search space. In these implementations, after UE 102 transmits Msg1 via 410A, UE 102 detects Msg2 (at event 416A) by detecting the Physical Downlink Control Channel (PDCCH) addressed to the Radio Network Temporary Identifier (RNTI) using CORESET and / or search space, where the PDCCH indicates the transmission of Msg2 (RAR) from base station 104A.

[0055] Msg2 contains an uplink grant for UE 102. Upon receiving Msg2, UE 102 uses the uplink grant to transmit 420A Msg3. In this implementation, Msg3 includes an indicator of the network slice of interest to UE 102 (arbitrarily referred to herein as the "first" network slice). After receiving Msg3 at event 420A, base station 104A determines that 425A Msg3 indicates the first network slice (or equivalently, UE 102 is requesting network support information for the first network slice).

[0056] In response to determining 425A, base station 104A determines what network support exists for the first network slice for 428A. Base station 104A may limit the determination of 428A to network resources that can be easily accessed by UE 102 given its current location in cell 124A. For example, base station 104A may only determine which neighboring cells of 428A, and / or which resources (e.g., which frequencies) associated with neighboring cells support the first network slice.

[0057] In some implementations, base station 104A determines network support for the first network slice by accessing a static or semi-static database locally stored at base station 104A. In other implementations, base station 104A determines network support for the first network slice by requesting neighboring base stations 104B and 104C to provide information about their ability to support the first network slice (e.g., via the X2 or Xn interface). In still other implementations, base station 104A accesses CN 110 to determine whether neighboring base stations 104B and / or 104C support the first network slice.

[0058] After determining 428A, base station 104A transmits 460A to UE 102, indicating Msg4, which represents the network support determined by UE 102 at event 428A. For example, the network support information in Msg4 may include the above-mentioned combination... Figure 3Event 330 refers to any or all types of information (e.g., the specific RAT and / or frequency supporting the first network slice, the physical cell identifiers of neighboring cells supporting the first network slice, etc.).

[0059] Next reference Figure 4B UE 102 initiates an alternative four-step contention-based RACH procedure 432B by transmitting Msg1 (420B) to base station 104A, possibly while UE 102 is camped on cell 124A and is in an idle or inactive state. In a regular RACH procedure (e.g., as specified in 3GPP LTE or NR specifications), Msg1 includes a preamble sequence and is transmitted via a PRACH timing. However, in this implementation, the preamble and / or PRACH timing are specifically dedicated / reserved for requesting network support information for a first network slice. [Reference] Figure 3 For example, base station 104A may have already configured UE 102 with RACH configuration (e.g., specific preamble and / or PRACH timing) by transmitting a configuration (e.g., RRC or broadcast) message to UE 102 before the start of procedure 332. An example of this configuration message will be discussed in more detail below.

[0060] In some implementations, UE 102 selects a RACH configuration (i.e., a set of RACH resources) for Msg1 from a plurality of RACH configurations, where each RACH configuration is dedicated to checking network support for a different slice. For example, base station 104A may have configured UE 102 with a first RACH configuration dedicated to checking the availability of a first network slice, and configured UE 102 with a second RACH configuration dedicated to checking the availability of a different second network slice. Figure 4B In the example, Msg1 itself can omit any information specifying the first network slice (e.g., information elements or fields).

[0061] Upon receiving Msg1 at event 420B (or simultaneously), base station 104A determines that 426B Msg1 is associated with a first network slice (or equivalently, UE 102 is requesting network support information for the first network slice). More specifically, in some embodiments, base station 104A determines that 426B Msg1 is requesting network support information for a slice associated with a specific RACH configuration / resource (e.g., preamble and / or PRACH timing) that UE 102 has already used to generate and transmit 420BMsg1. Base station 104A may make this determination 426B, for example, by detecting the preamble and / or PRACH timing used by UE 102 to transmit 420B Msg1, and then comparing the preamble and / or PRACH timing with locally stored data indicating (1) the association between the preamble and / or PRACH timing and (2) the network slice.

[0062] In response to determining 426B, base station 104A determines 428B what network support exists for that slice. For example, event 428B can be similar to event 428A. After determining the network support information for 428B, base station 104A transmits 430BMsg2 (Random Access Response, or "RAR") to UE 102. Msg2 can be similar to the Msg2 of a conventional four-step contention-based RACH procedure, but modified to include an indication of the network support information as determined by base station 104A for 428B. For example, Msg2 may include additional fields or fields that include network support information. For example, the network support information may include a combination of the above. Figure 3 Event 330 discusses any or all types of information (e.g., the specific RAT and / or frequency supporting the first network slice, the physical cell identifiers of neighboring cells supporting the first network slice, etc.).

[0063] The RACH procedure initiated by UE 102 to request network support information for the first network slice may or may not be a complete RACH procedure (i.e., it may or may not have the potential to lead to channel access and / or a transition of UE 102 to a connected state). In an implementation where UE 102 does not use RACH procedure 432B to attempt channel access, base station 104A may not perform any HARQ procedure, and / or procedure 432B may end after base station 104A transmits Msg2 (430B) (or after UE 102 processes the received Msg2 to identify network support for the first network slice). However, in other implementations and / or scenarios, in response to receiving Msg2 at event 430B, UE 102 transmits Msg3 (431B) to base station 104A containing scheduled transmissions. In response to Msg3, base station 104A transmits Msg4 (433B) to UE 102 indicating contention resolution.

[0064] In some implementations, Msg1 transmitted by base station 104A at 420B includes CORESET and / or search space. In these implementations, after UE 102 transmits Msg1 at 420B, UE 102 detects Msg2 (at event 430B) by detecting the PDCCH addressed to RNTI using CORESET and / or search space, wherein the PDCCH indicates the transmission of Msg2 (RAR) from base station 104A.

[0065] In an alternative implementation, base station 104A provides network support information at event 430B by broadcasting system information (e.g., in the SIB) instead of sending Msg2 (or, if RACH procedure 432 is used for channel access, in addition to sending Msg2 without network support information). If RACH procedure 432B is still in progress when UE 102 receives the broadcast system information, UE 102 terminates RACH procedure 432B.

[0066] Next reference Figure 5 ,exist Figure 3 In another alternative implementation of event 332, UE 102 initiates a two-step contention-based RACH procedure 532 by transmitting 520 MsgA to base station 104A, possibly while UE 102 is camped on cell 124A and is in an idle or inactive state. As in a conventional two-step RACH procedure (e.g., as specified in the 3GPP 5G NR specification), MsgA comprises two parts transmitted at different times: a preamble sequence transmitted via the PRACH timing (e.g., similar to...). Figure 4A Msg1), and payloads (e.g., similar to those launched via PUSCH timing) of 524. Figure 4B (Msg3). However, in this embodiment, the preamble and / or PRACH timing is dedicated / reserved for requesting network support information for the first network slice. Alternatively or additionally, the PUSCH timing for the MsgA payload can be dedicated to such a request. That is, the preamble and / or PRACH timing (and possibly the PUSCH timing for the MsgA payload) can be resources that base station 104A has already included in a RACH configuration dedicated to such requests. Reference Figure 3 For example, base station 104A may have already configured UE 102 with RACH configuration (e.g., specific preamble and / or PRACH timing) by transmitting a configuration (e.g., RRC or broadcast) message to UE 102 before the start of procedure 332. An example of this configuration message will be discussed in more detail below.

[0067] In some implementations, UE 102 selects a RACH configuration (i.e., a set of RACH resources) from multiple RACH configurations to be used for MsgA, where each RACH configuration is dedicated / reserved for checking network support for different slices. For example, base station 104A may have already configured UE 102 with a first RACH configuration dedicated to checking the availability of a first network slice, and configured UE 102 with a second RACH configuration dedicated to checking the availability of a different second network slice. Figure 5 In the example, MsgA itself can omit any information (e.g., information elements or fields) that specifies the first network slice.

[0068] In other implementations, base station 104A configures UE 102 with only a single RACH configuration for requesting slice-specific network support information, and UE 102 uses the content of MsgA to indicate the specific slice that UE 102 expects (e.g., needs or desires) to use. For example, UE 102 may include a field or information element indicating the slice of interest in the MsgA payload.

[0069] Upon receiving MsgA at event 520 (or simultaneously), base station 104A determines that 526 MsgA is associated with the first network slice (or equivalently, UE 102 is requesting network support information for the first network slice). In an implementation where base station 104A configures UE 102 with different RACH configurations for each of the multiple network slices, base station 104A can determine the exact slice 526 (here, the "first" network slice) by detecting the preamble and / or PRACH timing (and / or PUSCH timing) of MsgA and then comparing that preamble and / or PRACH timing (and / or PUSCH timing) with locally stored data indicating the association between (1) the preamble and / or PRACH timing (or PUSCH timing) and (2) the network slice.

[0070] However, in an implementation in which base station 104A has configured UE 102 with a single RACH configuration to handle network support requests for any of multiple different slices, base station 104A may determine slice 526 of interest by: (1) first detecting the RACH configuration (e.g., preamble, PRACH timing, and / or PUSCH timing) used to generate and / or transmit 520 MsgA, and then (2) in response to determining that the RACH configuration generally retains the information used to request slice support, examining the MsgA payload to identify the specific slice of interest (here, the "first" network slice) in the appropriate fields or information elements.

[0071] After MsgA has been identified as a request for network support information for the first network slice, base station 104A proceeds to determine 528 the network support information for that slice. For example, event 528 could be similar to Figure 4A Event 428A.

[0072] After determining the network support information 528, base station 104A transmits 530 MsgB to UE 102. MsgB can be similar to the MsgB of a conventional two-step contention-based RACH procedure, but modified to include an indication of the network support information 528 determined by base station 104A. For example, MsgB may include additional fields or fields that include the network support information. For example, the network support information may include a combination of the above. Figure 3 Event 330 discusses any or all types of information (e.g., the specific RAT and / or frequency supporting the first network slice, the physical cell identifiers of neighboring cells supporting the first network slice, etc.).

[0073] The RACH procedure initiated by UE 102 to request network support information for the first network slice may or may not be a complete RACH procedure (i.e., it may or may not have the potential to lead to channel access and / or a transition of UE 102 to a connected state). In an implementation where UE 102 does not use the dedicated RACH procedure 532 to attempt channel access, base station 104A may generate and transmit 530 MsgB without performing other operations typically associated with contention-based RACH procedures (e.g., HARQ procedures). However, in other implementations, UE 102 and base station 104A may perform a complete two-step contention-based RACH procedure, which may result in channel access and / or allow UE 102 to enter a connected state with respect to cell 124A and base station 104A.

[0074] In an alternative implementation, base station 104A provides network support information at event 530 by broadcasting system information (e.g., in the SIB) instead of sending MsgB (or, if RACH procedure 532 is used for channel access, in addition to sending MsgB without network support information). If RACH procedure 532 is still in progress when UE 102 receives the broadcast system information, UE 102 terminates RACH procedure 532.

[0075] As described above, for procedure 432B or procedure 532 (or possibly procedure 432A), base station 104A can configure UE 102 with a dedicated RACH configuration by sending one or more configuration messages to UE 102. For example, base station 104A can specify the dedicated RACH configuration in an SIB (e.g., SIB1) broadcast by base station 104A on cell 124A. Alternatively, base station 104A can specify the RACH configuration in a dedicated RRC message, such as when UE 102 transitions from a connected state to an idle state. RRCRelease In other implementations and / or scenarios, base station 104A may send messages in another suitable type(s) of messages (e.g., in the Master Information Block (MIB), or in messages sent by base station 104A to UE 102 during RRC reconfiguration). RRCReconfiguration The message was sent by base station 104A to UE 102 during the RRC connection establishment process. RRCSetup The message was sent by base station 104A to UE 102 during the RRC re-establishment process. RRCReestablishment The message was sent by base station 104A to UE 102 during the RRC connection restoration process. RRCResume or RRCSetup The message (in the middle) specifies the RACH configuration. In some implementations, base station 104A sends a dedicated RACH configuration in the same message that includes slice capability information transmitted at event 310.

[0076] The configuration message sent by base station 104A may include specific preamble and / or PRACH timing for each dedicated slice-specific RACH configuration. In some implementations, the configuration message may also include other information. For example, each RACH configuration may include the maximum number of allowed preamble transmission attempts before UE 102 should determine that the radio link has failed. In another example, each RACH configuration may include the type of RACH procedure (e.g., two-step or four-step) to be performed by UE 102. In other examples, each RACH configuration may include a RAR window length (e.g., the time period during which UE 102 should attempt to receive a RAR from base station 104A and then, if unsuccessful, select and transmit a new preamble), a MsgB response window length (e.g., the time period during which UE 102 should attempt to receive a MsgB from base station 104A and then, if it does not receive a MsgB containing both the identifier of the preamble in the MsgA and the Common Control Channel (CCCH) Service Data Unit (SDU), the RACH process is considered unsuccessful), or a contention resolution time (e.g., the time period during which UE 102 should attempt to detect a PDCCH addressed to a suitable C-RNTI or receive a message from base station 104A including a contention resolution identifier MAC control element (CE) and then, if unsuccessful, consider the RACH process unsuccessful and make another attempt to transmit the preamble). In other examples, each RACH configuration may include a power increment (slope step) for consecutive preamble transmissions performed by UE 102 (i.e., each retries for a failed RACH process), and / or a backoff factor to be used by UE 102 when performing a backoff during a RACH process (e.g., where UE 102 selects a backoff value between zero and the maximum value provided by base station 104A, and multiplies that backoff value by the backoff factor).

[0077] In some implementations, if UE 102 is served by or camped on cell 124A and requests base station 104A to transmit information related to a desired slice, and if base station 104A supports the slice, then base station 104A transmits a configuration message with RACH configuration for UE 102 to use when accessing a channel of cell 124A. For example, the configuration message may include any type of RACH configuration information discussed above (e.g., specific preamble and / or PRACH timing, maximum number of allowed preamble transmission attempts, etc.).

[0078] Figures 6 to 8The illustration shows an example scenario where UE 102 is prepared to transmit uplink data associated with two different slices simultaneously (or at overlapping times, etc.) and where base station 104A supports (or can support) two of those slices. In these cases, UE 102 may need to prioritize its attempts to obtain channel access for data associated with different slices. Figures 6 to 8 Each of these scenarios can occur, instead of, for example, procedures 332, 432A, 432B, or 532 (e.g., if the slice capability message received by UE 102 at event 310 indicates support for both slices). Alternatively, this can occur after procedures 332, 432A, 432B, or 532, and after UE 102 reselects a different cell (e.g., cell 124B or 124C) that provides support for both slices. Figures 6 to 8 Each of the scenarios in the example can be implemented by base stations of different cells (e.g., by base station 104B or 104C).

[0079] First refer to Figure 6 In scenario 600, UE 102 determines that data associated with the first network slice at 614 is ready for transmission, and determines that data associated with a different second network slice at 616 is also ready for transmission. For example, events 614 and 616 can each be similar to Figure 3 Event 314 can occur in any order or simultaneously. In some implementations and scenarios, event 616 can occur after the first RACH process has started (e.g., after event 660 but before event 680, both of which are discussed below).

[0080] In scenario 600, UE 102 decides to attempt channel access for data associated with the first network slice before attempting channel access for data associated with the second network slice. UE 102 may determine this order based on the fact that the first network slice (or its associated data) has a higher priority than the second network slice (or its associated data), since determination 614 occurs before determination 616, and / or for different reasons. To obtain channel access for the data in the first network slice, UE 102 initiates a four-step RACH procedure. Specifically, UE 102 transmits 660 Msg1 using a first RACH configuration (e.g., a first preamble transmitted on the first PRACH timing), and base station 104A responds by transmitting 670 Msg2 (RAR). Msg2 may also contain an identifier used by UE 102 to transmit the preamble 660 Msg1.

[0081] In scenario 600, UE 102 does not receive Msg2 in RAR window 672. Although Figure 6The example illustrates base station 104A transmitting Msg2 at time 670, and UE 102 failing to receive the transmitted Msg2. However, in other scenarios, base station 104A may not receive Msg1, in which case event 670 will not occur. In either case, in response to UE 102 detecting that RAR window 672 has ended without receiving Msg2 (or at least without receiving Msg2 containing a suitable preamble identifier), UE 102 decides to select a new preamble and / or PRACH timing and attempts to access the channel using this new RACH configuration. Figure 6 Only the beginning of this subsequent RACH procedure is shown, where UE 102 transmits 680Msg1 using the new RACH configuration. UE 102 then waits for base station 104A to respond with Msg2 within another RAR window, etc.

[0082] Next reference Figure 7 In scenario 700, UE 102 determines that data associated with the first network slice at 714 is ready for transmission, and determines that data associated with a different second network slice at 716 is also ready for transmission. Events 714 and 716 can each be similar to, for example... Figure 3 Event 314 can occur in any order or simultaneously. In some implementations and scenarios, event 716 can occur after the first RACH process has started (e.g., after event 760 but before event 780, both of which are discussed below).

[0083] In scenario 700, UE 102 decides to attempt channel access for data associated with the first network slice before attempting channel access for data associated with the second network slice. UE 102 may determine this order based on the fact that the first network slice (or its associated data) has a higher priority than the second network slice (or its associated data), since determination 714 occurs before determination 716, and / or for different reasons. To obtain channel access for the data in the first network slice, UE 102 initiates a four-step RACH procedure. Specifically, UE 102 transmits 760 Msg1 using a first RACH configuration (e.g., a first preamble transmitted on the first PRACH timing), and base station 104A responds by transmitting 770 Msg2 (RAR). Msg2 may also contain an identifier used by UE 102 to transmit the preamble 760 Msg1.

[0084] In response to receiving Msg2 with a suitable preamble identifier (within RAR window 772), UE 102 transmits Msg3 containing a CCCH SDU to base station 104A using the uplink grant included in Msg2 by base station 104A. In response, base station 104A transmits Msg4 containing a CCCH SDU to UE 102. In scenario 700, UE 102 does not receive Msg2 within contention resolution window 778. Although Figure 7 The example illustrates base station 104A transmitting Msg4 (776) and UE 102 failing to receive it. However, in other scenarios, base station 104A may not receive Msg3, in which case event 776 does not occur. In either case, in response to UE 102 detecting that contention resolution window 778 has ended without receiving Msg4 (or at least without receiving Msg4 containing a suitable CCCH SDU), UE 102 decides to select a new preamble and / or PRACH timing and attempts to access the channel using this new PRACH configuration. Figure 7 Only the beginning of this subsequent RACH procedure is shown, where UE 102 uses the new RACH configuration to transmit 780 Msg1. UE 102 then waits for base station 104A to respond with Msg2 within another RAR window, etc.

[0085] Next reference Figure 8 In scenario 800, UE 102 determines that data associated with the first network slice at time 814 is ready for transmission, and determines that data associated with a different second network slice at time 816 is also ready for transmission. Events 814 and 816 can each be similar to, for example... Figure 3 Event 314 can occur in any order or simultaneously. In some implementations and scenarios, event 816 can occur after the first RACH process has started (e.g., after event 862 but before event 882, both of which are discussed below).

[0086] In scenario 800, UE 102 decides to attempt channel access for data associated with the first network slice before attempting channel access for data associated with the second network slice. UE 102 may determine this order based on the fact that the first network slice (or its associated data) has a higher priority than the second network slice (or its associated data), since determination 814 occurs before determination 816, and / or for some other reason. To obtain channel access for the data in the first network slice, UE 102 initiates a two-step RACH procedure. Specifically, UE 102 transmits 862 MsgA using a first RACH configuration (e.g., a first preamble transmitted on the first PRACH timing), and base station 104A responds by transmitting 872 MsgB (RAR). MsgA may include a preamble and a CCCH SDU, and MsgA may contain an identifier used by UE 102 for transmitting the preamble of 862 MsgA.

[0087] In scenario 800, UE 102 did not receive MsgB in MsgB window 873. Although Figure 8 The illustration shows that base station 104A transmits MsgB 872 and UE 102 fails to receive the transmitted MsgB. However, in other scenarios, base station 104A does not receive MsgA, in which case event 872 does not occur. In either case, in response to UE 102 detecting that MsgB window 873 ends without receiving MsgB (or at least without receiving MsgB containing a suitable preamble identifier), UE 102 decides to select a new preamble and / or PRACH timing and attempts to access the channel using the new PRACH configuration. Figure 8 Only the beginning of this subsequent RACH procedure is shown, where UE 102 uses the new RACH configuration to transmit 882MsgA. UE 102 then waits for base station 104A to respond with MsgB within another MsgB window, etc.

[0088] Apart from Figures 6 to 8 Other implementations and scenarios besides those shown are also possible. In some implementations, for example, if UE 102 initiates a first RACH procedure using a first RACH configuration (to attempt channel access for data associated with a first network slice), and UE 102 determines during the first RACH procedure that second data associated with a second network slice is ready for transmission, then UE 102 terminates the first RACH procedure and instead begins a second RACH procedure to attempt channel access for the second network slice data. This may occur, for example, if UE 102 determines that the second network slice and / or its associated data has a higher priority than the first network slice and / or its associated data.

[0089] In some implementations, if UE 102 initiates a RACH procedure with a serving base station (e.g., base station 104A) to attempt channel access for uplink data associated with a specific slice and UE 102 selects or reselects a cell during the RACH procedure, UE 102 terminates the RACH procedure. UE 102 can then initiate another RACH procedure on the selected or reselected cell. In another scenario, if UE 102 initiates a RACH procedure with a serving base station (e.g., base station 104A) to attempt channel access for uplink data associated with a specific slice and serving cell 124A becomes unsuitable (e.g., due to channel quality degradation), UE 102 can terminate the ongoing RACH procedure.

[0090] In some implementations, the RAN uses offsets to direct the UE toward or away from cells based on whether a particular cell supports network slices that the UE needs (or prefers, expects, etc.) to utilize. For this purpose, base stations (e.g., base stations 104A, 104B, or 104C) may transmit offsets used in cell selection and / or offsets used in cell reselection.

[0091] Figure 9 An example scenario 900 is shown in which base stations 104A to 104C provide UE 102 with an offset during cell selection, turning UE 102 toward or away from the associated cells (i.e., cells 124A to 124C). Figure 9 As shown, base station 104A transmits a first slice capability message 910A to UE 102, base station 104B transmits a second slice capability message 910B to UE 102, and base station 104C transmits a third slice capability message 910C to UE 102. Each of the slice capability messages can be broadcast by the corresponding one of the base stations 104 and can be similar to the slice capability message transmitted at event 310. For example, the slice capability message can be an SIB (e.g., SIB1) indicating which network slice(s) is supported by the corresponding base station 104.

[0092] In addition, Figure 9In one implementation, the slice capability message specifies one or more cell selection offsets that UE 102 may use when calculating a cell suitability value (e.g., by modifying the S criterion as defined in TS 38.304). Typically, the suitability of a given cell may depend on both the slice desired by UE 102 and the slices supported by that cell. In other implementations, base station 104 transmits (e.g., broadcasts) its slice-related offsets separately from its indication of supported slices. Although the following terminology refers to a single cell for each base station, in some implementations and scenarios, a base station may transmit (e.g., broadcast) different cell selection offsets or different sets of cell selection offsets for each of a plurality of cells associated with that base station.

[0093] At some point after or during events 910A to 910C, UE 102 decides to select a cell. For example, UE 102 may decide to select a cell when UE 102 powers on or in response to UE 102 determining that data is ready for uplink transmission. In some implementations, UE 102 determines a cell is suitable for cell selection if a cell (1) meets the S criterion as defined in TS 38.304 (i.e., the criteria by which a given cell is “suitable” for selection) (or other criteria based at least in part on cell measurements), and (2) supports at least some threshold number of slices of interest to UE 102 (e.g., at least one desired slice or all desired slices, etc.). In these implementations, the slice capability message sent at events 910A to 910C may omit the offset and include only an indication of the supported slices.

[0094] However, in the depicted implementation, UE 102 determines the cell fitness value of 916 in part based on one or more offsets received from base station 104. In one such implementation, if a corresponding cell 124 supports one or more slices desired by the UE, base station 104 (at events 910A to 910C) broadcasts a positive offset that will turn the UE toward those cells 124. In one such implementation, the S criterion is that both Srxlev and Squal are greater than zero, where Srxlev and Squal are defined as: ;as well as .

[0095] In the above equation, Srxlev is the cell selection reception level value and Squal is the cell selection quality value (both expressed in dB), while It measures the cell's receive level (reference signal received power or RSRP) and This measures the cell quality value (reference signal reception quality or RSRQ). It is defined in TS 38.304. , , , , ,and RSNoffset is a specific value broadcast by base station 104 at events 910A to 910C to turn the UE (e.g., UE 102) toward the corresponding cell 124 if base station 104 and cell 124 support at least one desired slice. For example, when calculating Srxlev and Squal for cell 124A, if cell 124A supports at least one slice of interest to UE 102, then UE 102 applies (adds) the RSNoffset; otherwise, it does not apply the RSNoffset. Although applying the same offset for both Srxlev and Squal illustrates this implementation and other implementations for cell selection, it should be understood that the UE may use different offsets for Srxlev and Squal (or use a slice-related offset, etc., for only one of them).

[0096] In another implementation, if the corresponding cell 124 does not support any slice desired by the UE, base station 104 (at events 910A to 910C) broadcasts a negative offset that will turn the UE away from those cells 124. In one such implementation, the S criterion is that both Srxlev and Squal are greater than zero, where Srxlev and Squal are defined as: ;as well as , RSPoffset is a cell-specific value broadcast by base station 104 at events 910A to 910C to redirect a UE (e.g., UE 102) away from cell 124 if cell 124 does not support any slice of interest to a given UE. For example, when calculating Srxlev and Squal for cell 124A, if cell 124A does not support at least one slice of interest to UE 102, then UE 102 applies (subtracts) RSPoffset; otherwise, RSPoffset is not applied. In some implementations, base station 104 (at events 910A to 910C) simultaneously broadcasts both positive RSNoffset and RSPoffset values, such that if the corresponding cell supports at least one slice of interest to a given UE (e.g., UE 102), the UE can apply (add) RSNoffset, or alternatively apply (subtract) RSPoffset if the corresponding cell does not support at least one slice of interest to the UE.

[0097] In other implementations, base station 104 (at events 910A to 910C) broadcasts slice-specific offsets to provide the network with finer-grained control over cell selection. For example, it supports... k A given cell in a slice can (e.g., at one of events 910A to 910C) broadcast k A corresponding offset, ,in If UE 102 expects j slices, and if m Indicates (from) j If a cell supports a slice from among the expected slices, then the offset corresponding to these m "overlapping" slices can be marked as... ,in In one such implementation, the S criterion is that both Srxlev and Squal are greater than zero, where Srxlev and Squal are defined as: ;as well as .

[0098] In addition to slice-specific offsets, each cell can broadcast an offset RSoffset that UE 102 can apply (subtract) when the cell does not support any slices expected by UE 102 (e.g., as shown above for RSPoffset). Depending on the implementation and / or scenario, the offsets may vary when calculating Srxlev and Squal. The offset RSoffset can be added to or subtracted (i.e., similar to RSNoffset or RSPoffset), depending on the network preference of "towards the turn" or "away from the turn" from a slice that supports or does not support the desired slice. In some implementations, for example, m Alternatively, it can be defined as the number of desired slices not supported by the cell, in which case... Values ​​can be subtracted from Srxlev and Squal (instead of being added to Srxlev and Squal), and RSoffset can be added to Srxlev and Squal (instead of being subtracted from Srxlev and Squal).

[0099] In other embodiments, base station 104 (at events 910A to 910C) broadcasts slice-specific offsets. Furthermore, UE 102 uses another operation (in addition to summation) to combine slice-specific offsets. For example, UE 102 can calculate Srxlev and Squal as: ; as well as , Among them, RSMergedOffset is based on UE 102 and is also supported by the cell. m The value is determined by the desired slice. In one implementation, RSMergedOffset is derived from all offsets. The minimum offset among them In another implementation, RSMergedOffset is derived from all offsets. The maximum offset among them, In addition, each cell can also broadcast the offset RSoffset that UE 102 can apply when the cell does not support any slice expected by UE 102, and / or m It can be alternatively defined as the number of desired slices that are not supported by the cell.

[0100] In other embodiments, base station 104 (at events 910A to 910C) broadcasts slice-specific offsets. Furthermore, UE 102 weights the offset of the desired slice supported by the cell. For example, UE 102 can calculate Srxlev and Squal as: ; as well as , in It is UE 102 targeting the first l offset (RSoffset) l The weights applied. The network may have already been configured via dedicated signaling (e.g., from one of base stations 104). RRCRelease The message assigns slice-specific weights. Similarly, each cell can also broadcast the offset RSoffset that UE 102 can apply when the cell does not support any slice expected by UE 102. m It can be alternatively defined as the number of desired slices that are not supported by the cell.

[0101] In other implementations, UE 102 may apply slice-related (e.g., slice-specific) offsets received from base station 104 in other ways, and / or apply the offsets to different S standards.

[0102] After determining the cell suitability values ​​for cells 916, UE 102 selects cells 917 based on those values. For example, UE 102 may limit consideration to cells that meet suitability criteria (e.g., both Srxlev and Squal are greater than zero after applying all suitable offsets), and then select cells from those remaining cells using any other suitability criteria (e.g., cells with the highest Srxlev and / or Squal values, or cells that support the maximum number of slices that UE 102 needs or expects to use, etc.).

[0103] Figure 10 An example scenario 1000 is shown in which (serving) base station 104A provides UE 102 with one or more offsets during cell reselection, turning UE 102 toward or away from serving cell 124A and / or neighboring cells (e.g., cells 124B, 124C). Figure 10 As shown, base station 104A transmits a 1010 slice capability message to UE 102. For example, the slice capability message can be broadcast by base station 104A or included in a dedicated RRC message. The slice capability message can be similar to the slice capability message transmitted at event 310. For example, the slice capability message can be an SIB (e.g., SIB1), or indicate which network slice(s)(s) are supported by base station 104A. RRCCReconfiguration Messages, etc.

[0104] In addition, Figure 10 In this implementation, the slice capability message specifies one or more cell reselection offsets that UE 102 may use when calculating the ranking for serving cell 124A and / or neighboring cells (e.g., cells 124B, 124C) (e.g., by modifying the ranking formula as defined in TS 38.304). Unlike the cell selection scenario 900 discussed above, in cell reselection scenario 1000, serving base station 104A provides offsets not only for itself but also for other cells (here, cells 124B and 124C) that UE 102 will consider. Typically, the ranking of a given cell may depend on both the slice desired by UE 102 and the slices supported by that cell. In some implementations, base station 104A transmits slice-related offsets (multiples) separately from its indication of supported slices. The slice capability message (or different messages from base station 104A) may also specify a list of “popular” cells, as discussed in more detail below. Although the technology below refers to a single cell for each base station, in some implementations and scenarios, a base station may transmit (e.g., broadcast) different cell reselection offsets, or different sets of cell reselection offsets, and / or transmit different lists of popular cells for each of the multiple cells associated with that base station.

[0105] At some point after or during event 1010, UE 102 decides to perform a cell reselection procedure. For example, UE 102 may decide to perform a cell reselection procedure in response to a quality degradation of the communication channel in cell 124A. To perform the cell reselection procedure, UE 102 determines, in part, a cell ranking 1018 for the serving cell 124A and one or more neighboring cells (cells 124B and 124C in this example) based on the cell reselection offset received from base station 104A. In one such implementation, if the corresponding cell 124 supports one or more slices desired by the UE, base station 104A transmits 1010 a positive offset that turns the UE toward those cells 124. For example, the cell ranking criterion for the serving cell could be that Rs is greater than zero, where Rs is defined as:

[0106] In the above equation, It measures the Serving Cell Receiver Level Value (RSRP). It is defined in TS 38.304. , and RSNoffset is the value at which base station 104A transmits 1010 to redirect UE toward cell 124A if cell 124A supports at least one slice of interest to UE (e.g., UE 102). For example, when calculating Rs for cell 124A, if cell 124A supports at least one slice of interest to UE 102, then UE 102 applies (adds) RSNoffset; otherwise, RSNoffset is not applied.

[0107] As discussed above in connection with cell selection, other implementations are also possible. For example, in a scenario where serving cell 124A does not support any slices desired by UE 102, UE 102 could instead subtract the offset (e.g., RSPoffset) from Rs. As another example, UE 102 could instead determine the total cell reselection offset based on slice-specific offsets of slices desired by UE 102 and supported by cell 124A (or, if the offset is subtracted from the ranking, for those slices desired by UE 102 but not supported by cell 124A). For example, UE 102 could add or subtract in the same manner as discussed above with respect to Srxlev and Squal for cell selection. , or To determine Rs.

[0108] UE 102 also uses the slice-related offset received at event 1010 to determine the cell ranking for neighboring cells (here, cells 124B and 124C) at 1018. However, unlike in cell selection scenario 900, neighboring base stations 104B and 104C do not (at least not directly) inform UE 102 which slices they support. Therefore, in some implementations, base station 104A includes a list of “popular” neighboring cells in its slice capability message at event 1010 (or in another message), where “popular” neighboring cells are those that support the same slices as the serving cell (in this case, the same slices as serving cell 124A). In different implementations, base station 104A may also include an indication of which neighboring cells are “unpopular” (i.e., which neighboring cells do not support the same slices as the serving cell), or may not include such an indication, in which case UE 102 may simply assume that any cell not on the popular list is an unpopular cell. In some implementations, “popular” cells are not necessarily cells that precisely support the same set of slices as serving cell 124A. For example, a popular cell could be any neighboring cell that supports at least one slice supported by Serving Cell 124A, or any neighboring cell that supports all basic slices supported by Serving Cell 124A, etc.

[0109] In an implementation where the "popular" status means that neighboring cells support the same slice as serving cell 124A, UE 102 can calculate the ranking for a given neighboring cell based on: (1) whether serving cell 124A supports any slice of interest to UE 102, and (2) whether the neighboring cell is popular. If serving cell 124A does indeed support at least one desired slice and the neighboring cell is popular, UE 102 can determine the ranking for the neighboring cell in the same manner as for serving cell 124A. For example, UE 102 can do so by adding RSNoffset to the sum. Alternatively, by not subtracting RSPoffset (or by adding or not subtracting) , or The ranking of neighboring cells is calculated using techniques (discussed above), depending on which of these techniques UE 102 uses to rank neighboring cells. If serving cell 124A supports at least one desired slice but neighboring cells are undesirable, UE 102 may determine the ranking of neighboring cells in a different way than for serving cell 124A. For example, UE 102 may do so by subtracting RSPoffset or by not adding RSNoffset (or by subtracting or not adding RSNoffset). , or The Rn for such a cell is calculated using (etc.), depending on which of these techniques (discussed above) the UE 102 uses to rank neighboring cells.

[0110] In other implementations, UE 102 may otherwise apply slice-related (e.g., slice-specific) offsets received by UE 102 from base station 104, and / or apply the offsets to different cell ranking criteria.

[0111] After determining the serving cell ranking and neighboring cell rankings at event 1018, and based on those rankings, UE 102 either reselects to a new cell (e.g., cell 124B or 124C) or remains on serving cell 124A at event 1019. For example, UE 102 may decide to reselect to (or remain on) the cell with the highest ranking. In some implementations, the user equipment also uses a frequency-specific priority set to determine the cell to reselect to (if any). For example, the priority set may be a set of priorities indicated to UE 102 by base station 104A by providing index or geographic tag values, as described above. Figure 1 The subject of discussion.

[0112] Figure 11 and Figure 12 An example method is shown for informing user equipment which slice(s) are supported by the base station.

[0113] First refer to Figure 11 Example method 1100 can be implemented in a base station (e.g., base station 104A) configured to communicate with a user equipment (e.g., UE 102) located in the coverage area of ​​a cell (e.g., cell 124A) associated with the base station. For example, method 1100 can be implemented, in whole or in part, by the processing hardware 130 of base station 104A.

[0114] At box 1102, the base station generates a first message (e.g., a message for event 310, 910A, or 1010) indicating a set of one or more network slices supported by a cell associated with the base station. At box 1104, the base station transmits the first message (e.g., event 310, 910A, or 1010) to the user equipment (e.g., via broadcast or in a dedicated RRC message).

[0115] In some implementations and / or scenarios, method 1100 includes Figure 11One or more additional boxes are not shown in the diagram. For example, method 1100 may include: a first additional box in which the base station receives a request message (e.g., event 320, 420A, 420B, or 520) from the user equipment; and a second additional box in which the base station, in response to the request message, transmits a second message (e.g., event 330, 430A, 430B, or 530) to the user equipment including information about network support for a desired network slice. Method 1100 may also include additional boxes occurring before box 1104, in which the base station receives network support information related to the desired network slice from a neighboring base station (e.g., base station 104B) via an X2 or Xn interface.

[0116] In some implementations, if the request message is a first random access message (e.g., Msg1 or MsgA) and the response message transmitted by the base station is a second random access message (e.g., Msg2 or MsgB), then method 1100 includes an additional box in which the base station determines that the first random access message is associated with a desired network slice (e.g., event 425A, 426B, or 526). Method 1100 may further include an additional box (before the base station receives the first random access message) in which the base station transmits another message to the user equipment indicating one or more RACH configurations, including slice-specific RACH configurations used by the user equipment when generating and transmitting the first random access message. Alternatively, the RACH configurations may be included in the first message transmitted by the base station at box 1104.

[0117] In some implementations, method 1100 includes an additional frame (e.g., event 910A) in which the base station transmits a message to the user equipment indicating one or more cell selection offsets that the user equipment can use to determine the suitability of a cell for cell selection. Alternatively, the cell selection offsets may be included in a first message transmitted by the base station at frame 1104.

[0118] In some implementations, method 1100 includes an additional box (e.g., event 1010) in which the base station transmits to the user equipment a message indicating one or more cell reselection offsets that the user equipment can use to determine a ranking for one or more cells (including cells associated with the base station implementing method 1100) during cell reselection. Alternatively, the cell reselection offsets may be included in the first message transmitted by the base station at box 1104. In any of these implementations, method 1100 may include yet another box in which the base station transmits to the user equipment a message indicating one or more neighboring cells (e.g., a list of “popular” cells indicating neighboring cells supporting all the same network slice) that are also supported by cells of the base station implementing method 1100. Alternatively, the indications of these neighboring cells may be included in the first message transmitted by the base station at box 1104.

[0119] Next reference Figure 12 Example method 1200 can be implemented in a user equipment (e.g., UE 102) configured to communicate with a base station (e.g., base station 104A) when it is located in the coverage area of ​​a cell (e.g., cell 124A) associated with the base station. For example, method 1200 can be implemented wholly or partially by the processing hardware 140 of UE 102.

[0120] At box 1202, the user equipment receives a first message (e.g., event 310, 910A, or 1010) from the base station. At box 1204, the user equipment determines a set of one or more network slices supported by a cell associated with the base station by processing the first message received at box 1202. At box 1206, the user equipment determines, at least in part, whether to transmit data associated with a desired network slice via a cell (e.g., during cell selection or cell reselection).

[0121] In some implementations and / or scenarios, method 1200 includes Figure 12 One or more additional boxes not shown in the diagram. For example, method 1200 may include an additional box (before box 1206) in which the user equipment determines the desired network slice, for example, by transmitting an indicator of the desired network slice (e.g., within a list of desired slices) from the NAS layer to the AS layer implemented in the user equipment (e.g., from NAS controller 144 to AS controller 142).

[0122] In some implementations, method 1200 includes an additional box in which a user equipment transmits a request message (e.g., event 320, 420A, 420B, or 520) to a base station and, in response, receives from the base station a second message (e.g., event 330, 430A, 430B, or 530) including information about network support for a desired network slice. Method 1200 may further include a box in which the user equipment performs a cell reselection process based on the information in the second message. In implementations where the request message transmitted by the user equipment is a first random access message (e.g., Msg1 or MsgA) and the response message transmitted by the base station is a second random access message (e.g., Msg2 or MsgB), method 1200 may include yet another box in which the user equipment receives from the base station, prior to transmitting the first random access message, another message indicating one or more RACH configurations (including slice-specific RACH configurations used by the user equipment to generate and transmit the first random access message).

[0123] In some implementations (e.g., if block 1206 includes performing cell selection), method 1200 includes: a first additional block (or set of blocks) in which the user equipment receives one or more other messages (e.g., events 910B and / or 910C) from one or more other corresponding base stations (e.g., base station 104B and / or 104C) associated with one or more other corresponding cells (e.g., cells 124B and / or 124C); and a second additional block (or set of blocks) in which, for each of the one or more other messages, the user equipment determines one or more other corresponding sets of network slices supported by the corresponding cell.

[0124] In some implementations (e.g., if block 1206 includes performing cell selection), method 1200 includes an additional block in which the user equipment receives from the base station another message indicating one or more cell selection offsets (e.g., the offset provided at event 910A). Alternatively, the first message received by the user equipment at block 1202 may include the cell selection offset.

[0125] In some implementations (e.g., if block 1206 includes performing cell reselection), method 1200 includes an additional block in which the user equipment receives from the base station a message indicating one or more cell reselection offsets (e.g., the offsets provided at event 1010). Alternatively, the first message received by the user equipment at block 1202 may include the cell reselection offsets. In any of these implementations, method 1200 may include yet another block in which the user equipment receives from the base station a message indicating one or more neighboring cells supporting at least one network slice also supported by the serving cell (e.g., a list of “popular” cells indicating neighboring cells supporting all the same network slices). Alternatively, the indication of these neighboring cells may be included in the first message received by the user equipment at block 1202.

[0126] Figure 13 and Figure 14 An example method for obtaining network support information for a slice using the RACH process is shown.

[0127] First refer to Figure 13 Example method 1300 can be implemented in a base station (e.g., base station 104A) configured to communicate with a user equipment (e.g., UE 102) located in the coverage area of ​​a cell (e.g., cell 124A) associated with the base station. For example, method 1300 can be implemented, in whole or in part, by the processing hardware 130 of base station 104A.

[0128] At block 1302, the base station receives a first random access message (e.g., event 320, 420A, 420B, or 520) from the user equipment (RACH procedure). At block 1304, the base station determines that the first random access message is associated with a first network slice (e.g., event 425A, 426B, or 526). At block 1306, the base station transmits a second random access message (e.g., event 330, 430A, 430B, or 530) to the user equipment (RACH procedure), which includes information about network support for the first network slice.

[0129] In some implementations and / or scenarios, method 1300 includes Figure 13 One or more additional boxes are not shown in the diagram. For example, method 1300 may include an additional box (before box 1302) in which the base station transmits to the user equipment a configuration message that provides at least the slice-specific RACH configuration (e.g., preamble, PRACH timing, etc.) used by the user equipment to generate and transmit the first random access message. Method 1300 may also include a box in which the base station transmits to the user equipment other slice-specific RACH configurations associated with other slices.

[0130] Next reference Figure 14 Example method 1400 can be implemented in a user equipment (e.g., UE 102) configured to communicate with a base station (e.g., base station 104A) when it is located in the coverage area of ​​a cell (e.g., cell 124A) associated with the base station. For example, method 1200 can be implemented wholly or partially by the processing hardware 140 of UE 102.

[0131] At block 1402, the user equipment identifies the desired network slice (e.g., event 314). At block 1404, the user equipment transmits a first random access message of the first RACH procedure to the base station to indicate the desired network slice to the base station (e.g., events 320, 420A, 420B, or 520). At block 1406, the user equipment receives a second random access message of the first RACH procedure in response to the first random access message (e.g., events 330, 430A, 430B, or 530). At block 1408, the user equipment identifies network support for the desired network slice based on the second random access message received at block 1406.

[0132] In some implementations and / or scenarios, method 1400 includes Figure 14 One or more additional boxes are not shown in the diagram. For example, method 1400 may include an additional box (before box 1404) in which the user equipment receives from a base station (or a neighboring base station) a configuration message that configures the user equipment to use a first RACH configuration (e.g., preamble, PRACH timing, etc.) to request information about network support for a desired network slice. Method 1400 may also, or alternatively, include an additional box occurring after box 1408, in which the user equipment performs a cell reselection process (e.g., to reselect to a cell that supports the desired network slice) based at least in part on the network support identified at box 1408.

[0133] The following list of examples reflects various embodiments explicitly foreseen by this disclosure: Example 1. A method in a base station configured to communicate with a user equipment located in a coverage area of ​​a cell associated with the base station, the method comprising: generating a first message by processing hardware of the base station indicating a set of one or more network slices supported by the cell; and transmitting the first message to the user equipment.

[0134] Example 2. According to the method described in Example 1, the first message includes a bitmap containing multiple bits, each bit corresponding to a different network slice.

[0135] Example 3. The method described in Example 1 or 2, wherein each network slice in the set of network slices corresponds to the corresponding Network Slice Selection Auxiliary Information (NSSAI) or a single NSSAI (S-NSSAI).

[0136] Example 4. The method according to any one of Examples 1 to 3, wherein transmitting the first message includes broadcast system information.

[0137] Example 5. The method according to any one of Examples 1 to 3, wherein transmitting the first message includes transmitting a dedicated radio resource control (RRC) message.

[0138] Example 6. According to the method of Example 5, transmitting the first message includes transmitting an RRC message during the following processes: RRC reconfiguration process; RRC establishment process; RRC re-establishment process; or RRC connection recovery process.

[0139] Example 7. The method according to any one of Examples 1 to 6 further includes: receiving a request message from a user equipment; and in response to the request message, transmitting a second message to the user equipment, the second message including information about network support for one or more network slices.

[0140] Example 8. The method according to Example 7, wherein the second message indicates one or more of the following: a radio access technology (RAT) supporting the desired network slice; a frequency supporting the desired network slice; a physical cell identifier of a neighboring cell supporting the desired network slice; a random access channel (RACH) configuration associated with the neighboring cell; or whether the neighboring cell supports another network slice.

[0141] Example 9. The method according to Example 8 further includes: receiving network support information related to the desired network slice from a neighboring base station associated with a neighboring cell via an X2 or Xn interface before transmitting the second message.

[0142] Example 10. The method according to any one of Examples 7 to 9, wherein the request message specifies the desired network slice.

[0143] Example 11. The method according to any one of Examples 7 to 9, wherein: the request message is a first random access message of the random access channel RACH procedure; the method further includes: determining by processing hardware, at least in part, that the first random access message is associated with the desired network slice by determining that the user equipment transmitted the first random access message using a first RACH configuration associated with the desired network slice; and the second message is a second random access message of the RACH procedure.

[0144] Example 12. The method according to Example 11, wherein determining that the user equipment transmitted the first random access message using the first RACH configuration includes one or both of the following: determining that the first random access message includes a preamble associated with the desired network slice; and determining that the user equipment transmitted the first random access message using the PRACH timing associated with the desired network slice.

[0145] Example 13. The method according to Example 11 or 12, wherein: the transmission of the first message occurs before the receipt of the first random access message, and the first message indicates one or more RACH configurations, the one or more RACH configurations including the first RACH configuration; or the method further includes transmitting other messages indicating one or more RACH configurations to the user equipment before the receipt of the first random access message.

[0146] Example 14. The method according to Example 13, wherein the first message or other message indicates one or more of the following for each of one or more RACH configurations: preamble; PRACH timing; maximum number of allowed preamble transmissions; type of RACH procedure; time window for receiving RACH messages from the base station; contention resolution time; power increment for consecutive preamble transmissions; or backoff factor to be used by the user equipment when performing backoff during the RACH procedure.

[0147] Example 15. The method according to any one of Examples 11 to 14, wherein the first message instructs the user equipment to use the CORESET and / or search space of the channel carrying the second random access message.

[0148] Example 16. The method according to any one of Examples 1 to 4, wherein: the first message further indicates one or more cell selection offsets associated with a set of network slices, the one or more cell selection offsets being usable by the user equipment in determining the suitability of a cell for cell selection; or the method further includes transmitting to the user equipment another message indicating one or more cell selection offsets.

[0149] Example 17. The method according to Example 16, wherein one or more cell selection offsets include one or both of the following: an offset to be applied by the user equipment when the user equipment expects at least one network slice in the set of network slices; and an offset to be applied by the user equipment when the user equipment expects one or more network slices but there is no network slice in the set of network slices.

[0150] Example 18. The method according to Example 16, wherein one or more cell selection offsets include: a first offset to be applied by the user equipment when the user equipment desires a first network slice in the set of network slices; and a second offset to be applied by the user equipment when the user equipment desires a second network slice in the set of network slices.

[0151] Example 19. The method according to any one of Examples 1 to 4, wherein: the first message further indicates one or more cell reselection offsets associated with a set of network slices, the one or more cell reselection offsets being available to the user equipment when determining one or more cell rankings for cell reselection; or the method further includes transmitting to the user equipment another message indicating one or more cell reselection offsets.

[0152] Example 20. The method according to Example 19, wherein one or more cell reselection offsets include one or both of the following: a first offset to be applied by the user equipment when the user equipment expects at least one network slice in the set of network slices; and a second offset to be applied by the user equipment when the user equipment expects one or more network slices but there is no network slice in the set of network slices.

[0153] Example 21. The method according to Example 19, wherein one or more cell reselection offsets include: a first offset to be applied by the user equipment when the user equipment desires a first network slice in the set of network slices; and a second offset to be applied by the user equipment when the user equipment desires a second network slice in the set of network slices.

[0154] Example 22. The method according to any one of Examples 19 to 21, wherein: the first message further indicates one or more neighboring cells of at least one network slice in the set that also supports network slices; or the method further includes transmitting to the user equipment one or more neighboring cells of at least one network slice in the set that also supports network slices.

[0155] Example 23. According to the method of Example 22, wherein a first message indicates all network slices in a set of one or more neighboring cells that support network slices; or other messages indicate all network slices in a set of one or more neighboring cells that support network slices.

[0156] Example 24. The method according to any one of Examples 1 to 6, wherein: the method further comprises: determining a set of priorities to be applied by the user equipment when the user equipment performs a cell reselection procedure based on at least one network slice from a set of network slices supported by the cell, the set of priorities defining priorities of a plurality of frequencies; and (i) a first message further indicating the set of priorities, or (ii) the method further comprises transmitting other messages indicating the set of priorities to the user equipment.

[0157] Example 25. The method according to Example 24, wherein the first message or other message includes a region-specific tag value indicating a priority set, and wherein the region-specific tag value is specific to (i) a tracking area code (TAC), (ii) a radio access network (RAN) area code, (iii) a cell list, or (iv) local data network (LADN) information.

[0158] Example 26. A method in a user equipment configured to communicate with a base station when located in a coverage area of ​​a cell associated with a base station, the method comprising: receiving a first message from the base station; processing the first message by processing hardware of the user equipment to determine a set of one or more network slices supported by the cell; and determining, by the processing hardware and at least in part based on the set of network slices, whether to transmit data associated with a desired network slice via the cell.

[0159] Example 27. The method according to Example 26 further includes: after determining whether to communicate, transmitting data associated with the desired network slice to the base station via the cell.

[0160] Example 28. The method according to Example 26, wherein the first message includes a bitmap containing multiple bits, each bit corresponding to a different network slice.

[0161] Example 29. The method according to any one of Examples 26 to 28, wherein each network slice in the set of network slices corresponds to a corresponding network slice selection auxiliary information (NSSAI) or a single NSSAI (S-NSSAI).

[0162] Example 30. The method according to any one of Examples 26 to 29 further includes: determining the desired network slice by the processing hardware at least in part by transmitting an indicator of at least the desired network slice from the non-access NAS layer to the access AS layer.

[0163] Example 31. The method according to any one of Examples 26 to 30, wherein receiving the first message includes receiving system information broadcast by the base station.

[0164] Example 32. The method according to any one of Examples 26 to 30, wherein receiving the first message includes receiving a Dedicated Radio Resource Control (RRC) message.

[0165] Example 33. The method according to Example 32, wherein receiving the first message includes receiving an RRC message during the following processes: an RRC reconfiguration process; an RRC establishment process; an RRC re-establishment process; or an RRC connection recovery process.

[0166] Example 34. The method according to any one of Examples 26 to 33, wherein: it is expected that a network slice is not included in the set of network slices supported by a cell; determining whether to transmit data via a cell includes determining that data is not transmitted via a cell; and the method further includes transmitting a request message to a base station, and in response to the request message, receiving a second message from the base station, the second message including information about network support for one or more network slices.

[0167] Example 35. The method according to Example 34, wherein the second message indicates one or more of the following: a radio access technology (RAT) supporting the desired network slice; a frequency supporting the desired network slice; a physical cell identifier of a neighboring cell supporting the desired network slice; a random access channel (RACH) configuration associated with the neighboring cell supporting the desired network slice; or whether the neighboring cell supports another network slice.

[0168] Example 36. The method according to Example 34 or 35 further includes: performing a cell reselection process by processing hardware based on information in a second message.

[0169] Example 37. The method according to any one of Examples 34 to 36, wherein the request message specifies the desired network slice.

[0170] Example 38. The method according to any one of Examples 34 to 36, wherein: the request message is a first random access message of the random access channel RACH procedure; the transmit request message includes transmitting the first random access message using a first RACH configuration associated with the desired network slice; and the second message is a second random access message of the RACH procedure.

[0171] Example 39. The method according to Example 38, wherein transmitting the first random access message using a first RACH configuration includes one or both of the following: transmitting a preamble associated with a desired network slice; and transmitting the first random access message using a PRACH timing associated with the desired network slice.

[0172] Example 40. The method according to Example 38 or 39, wherein: receiving the first message occurs before transmitting the first random access message, and the first message indicates one or more RACH configurations, the one or more RACH configurations including the first RACH configuration; or the method further includes receiving another message indicating one or more RACH configurations from the base station before transmitting the first random access message.

[0173] Example 41. The method according to Example 40, wherein the first message or another message indicates one or more of the following for each of one or more RACH configurations: preamble; PRACH timing; maximum number of allowed preamble transmissions; type of RACH procedure; time window for receiving RACH messages from the base station; contention resolution time; power increment for consecutive preamble transmissions; or backoff factor to be used by the user equipment when performing backoff during the RACH procedure.

[0174] Example 42. The method according to any one of Examples 38 to 41, wherein: the first message indicates CORESET and / or search space; and receiving the second random access message includes using CORESET and / or search space to detect the channel carrying the second random access message.

[0175] Example 43. The method according to any one of Examples 26 to 31, wherein determining whether to transmit data associated with the desired network slice via a cell includes performing a cell selection process.

[0176] Example 44. The method according to Example 43 further includes: receiving one or more other messages from one or more other corresponding base stations associated with one or more other corresponding cells; and for each of the one or more other messages, determining one or more other corresponding sets of one or more network slices supported by the corresponding cell by processing the message through hardware processing.

[0177] Example 45. The method according to Example 44, wherein performing the cell selection process includes excluding any cells that do not support at least one network slice desired by the user equipment.

[0178] Example 46. The method according to Example 43, wherein: (i) the first message further indicates one or more cell selection offsets associated with a set of network slices, or (ii) the method further includes receiving from a base station another message indicating one or more cell selection offsets; and performing the cell selection process includes using at least one of the one or more cell selection offsets to determine the suitability of a selection for cell selection.

[0179] Example 47. The method according to Example 46, wherein determining the fitness of a cell comprises: calculating a value based on the signal power or channel quality measured relative to the cell by at least in part: (i) adding a first offset to make the selection of the cell more likely when the set of network slices includes at least one network slice desired by the user equipment, or (ii) not adding a first offset when the set of network slices does not include any network slice desired by the user equipment; and comparing the value with a minimum fitness threshold.

[0180] Example 48. The method according to Example 46, wherein determining the cell fitness comprises: calculating a value based on the signal power or channel quality measured relative to the cell by at least part of the following operations: (i) applying a first offset to make cell selection less likely when the set of network slices does not include any network slices desired by the user equipment, or (ii) not applying the first offset when the set of network slices includes at least one network slice desired by the user equipment; and comparing the value with a minimum fitness threshold.

[0181] Example 49. The method according to Example 46, wherein one or more cell selection offsets include multiple cell selection offsets each corresponding to a different network slice.

[0182] Example 50. The method according to Example 49, wherein determining the cell fitness comprises: calculating a value based on the signal power or channel quality measured relative to the cell by adding at least part of a plurality of cell selection offsets corresponding to all offsets of the network slice desired by the user equipment; and comparing the value with a minimum fitness threshold.

[0183] Example 51. The method according to Example 49, wherein determining the cell fitness comprises: calculating a value based on the minimum or maximum value of all offsets corresponding to the network slice desired by the user equipment, at least in part, by adding a plurality of cell selection offsets; and comparing the value with a minimum fitness threshold.

[0184] Example 52. The method according to Example 49, wherein determining the cell fitness includes at least in part calculating a value based on the signal power or channel quality measured relative to the cell by: weighting all offsets among a plurality of cell selection offsets that correspond to the network slice desired by the user equipment; summing the weighted offsets; and comparing the value with a minimum fitness threshold.

[0185] Example 53. The method according to any one of Examples 26 to 31, wherein determining whether to transmit data associated with the desired network slice via a cell includes performing a cell reselection process.

[0186] Example 54. The method according to Example 53, wherein: (i) the first message further indicates one or more cell reselection offsets associated with a set of network slices, or (ii) the method further includes receiving from a base station another message indicating one or more cell reselection offsets; and performing the cell reselection process includes using at least one of the one or more cell reselection offsets to determine the ranking of the cells.

[0187] Example 55. The method according to Example 54, wherein determining the ranking of a cell includes calculating the ranking based on the signal power or channel quality measured relative to the cell by at least part of the following operations: (i) when the set of network slices includes at least one network slice desired by the user equipment, applying a first offset to make reselection of neighboring cells less likely, or (ii) when the set of network slices does not include any network slice desired by the user equipment, not applying the first offset.

[0188] Example 56. The method according to Example 54, wherein determining the ranking of a cell includes calculating the ranking based on the signal power or channel quality measured relative to the cell by at least part of the following operations: (i) applying a first offset to make reselection of neighboring cells more likely when the set of network slices does not include any network slices desired by the user equipment, or (ii) not applying the first offset when the set of network slices includes at least one network slice desired by the user equipment.

[0189] Example 57. The method according to Example 54, wherein one or more cell reselection offsets include multiple cell reselection offsets each corresponding to a different network slice.

[0190] Example 58. According to the method of Example 57, wherein determining the ranking of a cell includes calculating the ranking based on the signal power or channel quality measured relative to the cell by at least in part by adding up all offsets among a plurality of cell reselection offsets that correspond to the network slice desired by the user equipment.

[0191] Example 59. The method according to Example 57, wherein determining the cell ranking includes at least in part calculating the ranking based on the signal power or channel quality measured relative to the cell by adding the minimum or maximum of all offsets among a plurality of cell reselection offsets that correspond to the network slice desired by the user equipment.

[0192] Example 60. The method according to Example 57, wherein determining the cell ranking includes at least in part calculating the ranking based on the signal power or channel quality measured relative to the cell by weighting all offsets among a plurality of cell reselection offsets corresponding to the network slice desired by the user equipment, and summing the weighted offsets.

[0193] Example 61. The method according to any one of Examples 53 to 60, wherein: (i) the first message further indicates one or more neighboring cells that also support at least one network slice in the set of network slices, or (ii) the method further includes receiving from a base station another message indicating one or more neighboring cells that also support at least one network slice in the set of network slices; and performing the cell reselection process includes, for each neighboring cell, calculating a ranking of the neighboring cell at least in part based on whether the first message indicates that the neighboring cell also supports at least one network slice in the set of network slices.

[0194] Example 62. The method according to Example 61, wherein: (i) the first message indicates that one or more neighboring cells also support all network slices in the set of network slices, or (ii) the method includes receiving from the base station other messages indicating that one or more neighboring cells also support all network slices in the set of network slices; and performing the cell reselection process includes, for each neighboring cell, calculating the ranking of the neighboring cell at least in part based on whether the first message indicates that the neighboring cell also supports all network slices in the set of network slices.

[0195] Example 63. The method according to any one of Examples 26 to 33, further comprising: determining by processing hardware that the user equipment has first data associated with a first network slice ready for uplink transmission; determining by processing hardware that the user equipment has second data associated with a second network slice ready for uplink transmission; transmitting a first random access message of a RACH procedure to attempt channel access for the first data using a first random access channel RACH configuration; determining that the base station did not respond correctly to the user equipment during the RACH procedure; and in response to determining that the base station did not respond correctly, transmitting a second random access message using a second RACH configuration to attempt channel access for the second data.

[0196] Example 64. The method according to Example 63, wherein determining that the base station did not respond correctly includes: determining that the base station did not respond within the Random Access Response (RAR) window; determining that the base station did not include the correct preamble identifier in the RAR message; or determining that the base station did not respond within the contention resolution time.

[0197] Example 65. The method according to any one of Examples 26 to 33, further comprising: determining, by processing hardware, that the user equipment has first data associated with a first network slice ready for uplink transmission; initiating a first RACH procedure using a first random access channel RACH configuration to attempt channel access for the first data; determining, by processing hardware, after initiating the first RACH procedure, that the user equipment has second data associated with a second network slice ready for uplink transmission; and, after determining that the user equipment has second data ready for uplink transmission, terminating the first RACH procedure and initiating a second RACH procedure using a second RACH configuration to attempt channel access for the second data.

[0198] Example 66. According to the method of Example 65, terminating the first RACH process and initiating the second RACH process is in response to the processing hardware determining that (i) the second network slice has a higher priority than the first network slice, or (ii) the second data has a higher priority than the first data.

[0199] Example 67. The method according to any one of Examples 26 to 33, wherein: (i) the first message further indicates a priority set of a plurality of frequencies, or (ii) the method further includes receiving from a base station another message indicating a priority set, the priority set being specific to at least one network slice in a set of network slices supported by a cell; and the method further includes using the priority set to perform a cell reselection process.

[0200] Example 68. The method according to Example 67, wherein a first message or other message indicates a region-specific tag value for a priority set, and wherein the region-specific tag value is specific to (i) a Tracking Area Code (TAC), (ii) a Radio Access Network (RAN) area code, (iii) a cell list, or (iv) Local Data Network (LADN) information.

[0201] Example 69. A base station, including hardware and configured to implement the method according to any one of Examples 1 to 25.

[0202] Example 70. A user equipment, including hardware and configured to implement the method according to any one of Examples 26 to 69.

[0203] The following additional considerations apply to the above discussion.

[0204] User equipment implementing the technologies disclosed herein (e.g., UE 102) can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell base station, or broadband router. Furthermore, in some cases, the user equipment can be embedded in electronic systems, such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Additionally, the user equipment can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0205] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain manner. A hardware module may include permanently configured dedicated circuitry or logic (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., as included in a general-purpose processor or other programmable processor) temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry or in (e.g., software-configured) temporarily configured circuitry may be driven by cost and time considerations.

[0206] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. This software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0207] Upon reading this disclosure, those skilled in the art will recognize the additional and alternative structural and functional designs for providing RAN support for network slicing through the principles disclosed herein. Therefore, although specific embodiments and applications have been illustrated and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations can be made to the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims, as will be clear to those skilled in the art.

Claims

1. A method for wireless communication performed at a base station, the base station being configured to communicate with a user equipment (UE) located in a coverage area of ​​a cell associated with the base station, the method comprising: The base station generates a first message indicating a set of one or more network slices supported by the cell of the base station and a priority set that can be used by the UE when performing cell selection. The priority set is determined based on at least one network slice in the set of one or more network slices supported by the cell of the base station and defines the priorities of multiple frequencies. The base station transmits the first message to the UE; After determining that the cell of the base station does not support at least one network slice not included in the set of one or more network slices, the base station receives a request message from the UE. as well as In response to receiving the request message, the base station transmits a second message to the UE, the second message including information about network support for the at least one network slice not included in the set of one or more network slices.

2. The method according to claim 1, wherein, The transmission of the first message includes a dedicated radio resource control (RRC) message.

3. The method according to claim 1, wherein: The first message indicates one or more neighboring cells that support at least one network slice in the set of one or more network slices; or The first message indicates that the one or more neighboring cells support all network slices in the set of the one or more network slices.

4. The method according to claim 1, wherein, The first message includes a region-specific tag value indicating the priority set, wherein the region-specific tag value is a tracking area code (TAC), radio access network (RAN) area code, cell list, or local data network (LADN) information.

5. The method according to claim 1, wherein, The first message includes a set of indices indicating the priority set.

6. The method according to any one of claims 1 to 4, wherein, The priority set is specific to at least one network slice in the set of one or more network slices supported by the cell.

7. A method of wireless communication performed at a user equipment (UE), the UE being configured to communicate with a base station when located in a coverage area of ​​a cell associated with a base station, the method comprising: Receive a first message from the base station; The first message is processed, indicating a set of one or more network slices supported by the cell of the base station and a priority set for multiple frequencies, the priority set being specific to at least one network slice in the set of one or more network slices supported by the cell. After determining that the cell of the base station does not support at least one network slice not included in the set of one or more network slices, the UE sends a request message to the base station. The UE receives a second message from the base station, the second message including information about network support for the at least one network slice that is not included in the set of one or more network slices; The priority set is applied by the UE; as well as The UE performs the cell selection process using at least one of the priority sets.

8. The method according to claim 7, wherein, Receiving the first message includes receiving a Dedicated Radio Resource Control (RRC) message.

9. The method according to any one of claims 7-8, wherein, The first message includes a region-specific tag value indicating the priority set, wherein the region-specific tag value is a tracking area code (TAC), radio access network (RAN) area code, cell list, or local data network (LADN) information.

10. A base station, comprising hardware and configured to implement the method according to any one of claims 1 to 6.

11. A user equipment comprising hardware and configured to implement the method according to any one of claims 9.