Signaling used to indicate the expected slice information in paging.

By identifying the expected slice information in the paging message, the paging efficiency problem of UE and base station in RRC idle or inactive mode in wireless communication system is solved, realizing efficient execution of random access channel procedure and improving system communication efficiency and reliability.

CN116762427BActive Publication Date: 2026-11-17QUALCOMM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202180092030.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-02-02
Publication Date
2026-11-17
Estimated Expiration
2041-02-02

AI Technical Summary

Technical Problem

In wireless communication systems, UEs and base stations have difficulty effectively indicating expected slice information via paging messages in RRC idle or inactive modes, resulting in low efficiency of random access channel procedures.

Method used

Accurate indication and response to expected slices are achieved by identifying the expected slice information of the PDU session associated with downlink traffic in the paging message and initiating a request for random access channel procedure based on this information.

Benefits of technology

It improves the paging efficiency of UE and base station in RRC idle or inactive mode in wireless communication system, ensures the effective execution of random access channel procedure, and improves the communication efficiency and reliability of system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116762427B_ABST
    Figure CN116762427B_ABST
Patent Text Reader

Abstract

Various aspects of this disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a paging message in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging message including an indication of an expected slice of a Protocol Data Unit (PDU) session associated with downlink traffic for the UE. The UE may transmit to the base station a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] open field

[0002] Various aspects of this disclosure generally relate to wireless communications and techniques and apparatus for signaling to indicate expected slice information in paging.

[0003] background

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs can communicate with the BS via downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, while the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be referred to as a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.

[0006] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different user equipment to communicate at the city, country, region, and even global levels. NR (which can also be referred to as 5G) is an enhancement set of the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), and using CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to grow.

[0007] Overview

[0008] In some aspects, a wireless communication method performed by a UE includes: receiving a paging message in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and transmitting to a base station a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

[0009] In some aspects, a wireless communication method performed by a base station includes: transmitting a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE; and receiving from the UE a request to initiate a RACH procedure at least in part based on the expected slice.

[0010] In some aspects, a UE for wireless communication includes: a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive a paging message in an RRC idle mode or an RRC inactive mode, the paging message including an indication identifying an expected slice for a PDU session associated with downlink traffic for the UE; and transmit a request to a base station to initiate a RACH procedure at least in part based on the expected slice.

[0011] In some aspects, a base station for wireless communication includes a memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: transmit a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE; and receive from the UE a request to initiate a RACH procedure at least in part based on the expected slice.

[0012] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a paging message in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic for the UE; and transmit a request to a base station to initiate a RACH procedure at least in part based on the expected slice.

[0013] In some aspects, a non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a base station, cause the base station to: transmit a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE; and receive from the UE a request to initiate a RACH procedure at least in part based on the expected slice.

[0014] In some aspects, an apparatus for wireless communication includes: means for receiving a paging message in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic for the apparatus; and means for transmitting to a base station a request to initiate a RACH procedure at least in part based on the expected slice.

[0015] In some aspects, an apparatus for wireless communication includes: means for transmitting a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE; and means for receiving from the UE a request to initiate a RACH procedure at least in part based on the expected slice.

[0016] The aspects generally include, as substantially described herein with reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, base stations, wireless communication equipment, and / or processing systems.

[0017] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not for defining limitations on the claims. Brief description of the attached diagram

[0019] To gain a more detailed understanding of the features described above in this disclosure, reference can be made to various aspects of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as other equivalent aspects are permissible in this description. Identical reference numerals in different drawings may identify the same or similar elements.

[0020] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0021] Figure 2 This is a diagram illustrating an example of communication between a base station and a UE in a wireless network according to this disclosure.

[0022] Figure 3 This is a diagram illustrating an example of network slice assignment for a UE according to this disclosure.

[0023] Figure 4 This is a diagram illustrating an example of signaling associated with intended slice information in paging, according to the present disclosure.

[0024] Figure 5-6 This is a diagram illustrating an example process associated with signaling used to indicate expected slice information in paging, according to the present disclosure.

[0025] Figure 7-8 This is a block diagram illustrating an example device for wireless communication according to the present disclosure.

[0026] Detailed description

[0027] The various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as being limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

[0028] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and explained in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] It should be noted that although the aspects herein may be described using terms commonly associated with 5G or NR radio access technology (RAT), the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0030] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be a 5G (NR) network and / or an LTE network, etc., or may include elements thereof. The wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, B-node, gNB, 5G B-node (NB), access point, transmit / receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0031] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with a service subscription. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with a service subscription. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1In the example shown, BS110a can be a macro BS for macro cell 102a, BS110b can be a pico BS for pico cell 102b, and BS110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably herein.

[0032] In some respects, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile BS. In some respects, BSs may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks, using any suitable transport network).

[0033] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

[0034] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0035] Network controller 130 can be coupled to a set of BSs and can provide coordination and control over these BSs. Network controller 130 can communicate with each BS via backhaul. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0036] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), entertainment device (e.g., music or video device, or satellite radio), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0037] Some UEs may be considered machine-type communication (MTC) devices, or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes may provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) via wired or wireless communication links, for example. Some UEs may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0039] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this scenario, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as performed by base station 110.

[0040] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1) and / or an operating band with a second frequency range (FR2), where the first frequency range (FR1) spans from 410 MHz to 7.125 GHz and the second frequency range (FR2) spans from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency bands. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz band." Similarly, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as the "millimeter wave" band. Therefore, unless otherwise stated, it should be understood that, if used herein, the terms "sub-6 GHz" and the like can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that, if used herein, the terms "millimeter wave" and the like can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25 GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0041] As indicated above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0042] Figure 2This is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to this disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein generally T≥1 and R≥1.

[0043] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively.

[0044] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) these detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or Channel Quality Indicator (CQI). In some respects, one or more components of the UE 120 may be included in the housing 284.

[0045] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0046] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or be included therein, one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or multiple antenna elements within housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include elements coupled to one or more transmission and / or reception components (such as...). Figure 2 One or more antenna elements (one or more components).

[0047] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-encoded by TX MIMO processor 266 where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 254) of UE 120 may be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receiver processors 258, transmitter processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein, for example, as referenced. Figure 4-6 As described.

[0048] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receiver processors 238, transmitter processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein, for example, as referenced. Figure 4-6 As described.

[0049] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with signaling used to indicate expected slice information in paging, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may execute or direct, for example Figure 5 The operation of process 500, process 6 of Figure 600, and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include: a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 5 Process 500 Figure 6 The operation of process 600, and / or other processes described herein. In some aspects, the execution instructions may include run instructions, translate instructions, compile instructions, and / or interpret instructions, etc.

[0050] In some aspects, UE 120 includes: means for receiving a paging message in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and / or means for transmitting to a base station a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice. Means for UE 120 to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TXMIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0051] In some aspects, UE 120 includes means for receiving a configuration of a corresponding slice group index for each of one or more permitted slices for the UE before receiving a paging message.

[0052] In some respects, UE 120 includes means for selecting one or more RACH resources associated with an emergency slice for use in RACH procedures.

[0053] In some respects, UE 120 includes means for selecting one or more RACH parameters associated with an emergency slice for use in RACH procedures.

[0054] In some respects, UE 120 includes means for determining, at least in part, Single Network Slice Selection Auxiliary Information (S-NSSAI) for an intended slice based on the PDU session identifier.

[0055] In some respects, UE 120 includes means for determining the desired slice based on the cause value, at least in part, the mapping between Network Slice Selection Assistance Information (NSSAI) and the cause value.

[0056] In some respects, UE 120 includes means for receiving mappings in a System Information Block (SIB).

[0057] In some respects, UE 120 includes: means for discarding mappings; and / or means for receiving new mappings in the SIB of a new cell.

[0058] In some respects, UE 120 includes means for receiving mappings in Non-Access Stratum (NAS) messages.

[0059] In some respects, UE 120 includes means for receiving mappings in RRC release messages.

[0060] In some aspects, UE 120 includes means for selecting at least one of a RACH resource associated with a desired slice or a RACH parameter associated with a desired slice for RACH procedures.

[0061] In some respects, UE 120 includes means for selecting one or more RACH resources from a pool of RACH resources configured for an intended slice for RACH procedures.

[0062] In some respects, UE 120 includes means for selecting one or more RACH resources from a pool of RACH resources configured for use with a group of slices associated with an intended RACH procedure.

[0063] In some respects, UE 120 includes means for selecting one or more RACH parameters for RACH procedures that are associated with a priority level configured for an intended slice.

[0064] In some respects, UE 120 includes means for selecting one or more RACH parameters for RACH procedures that are associated with a priority level of a slice group configured to be associated with an intended slice.

[0065] In some aspects, base station 110 includes: means for transmitting a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE; and / or means for receiving from the UE a request to initiate a RACH procedure at least in part based on the expected slice. Means for base station 110 to perform the operations described herein may include, for example, one or more of a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0066] In some aspects, base station 110 includes means for determining a radio bearer identifier for a logical channel associated with a prospective slice, based at least in part on N3 tunnel information of downlink traffic.

[0067] In some aspects, base station 110 includes means for determining a cause value mapped to a desired slice, based at least in part on the mapping between NSSAI and cause values.

[0068] In some respects, base station 110 includes means for transmitting mappings to UE in SIB.

[0069] In some respects, base station 110 includes means for transmitting a mapping to the UE in an RRC release message.

[0070] In some aspects, base station 110 includes means for receiving from UE a request to initiate a RACH procedure for using one or more RACH resources associated with a desired slice.

[0071] In some aspects, base station 110 includes means for receiving from UE a request to initiate a RACH procedure using one or more RACH parameters associated with a desired slice.

[0072] In some aspects, base station 110 includes means for receiving slice information associated with a desired slice from core network equipment.

[0073] In some aspects, base station 110 includes means for receiving an N2 paging request from core network equipment, which includes slice information associated with a desired slice.

[0074] In some aspects, base station 110 includes means for transmitting a RAN paging message, which includes slice information associated with a desired slice, to one or more other base stations in a notification area based on a radio access network (RAN) associated with the UE.

[0075] In some aspects, base station 110 includes means for receiving a RAN paging message from another base station in a RAN-based notification area associated with the UE, which includes slice information associated with a desired slice.

[0076] although Figure 2 The boxes in the diagram are interpreted as different components, but the functions described above with respect to these boxes can be implemented using a single hardware component, software component, or combination of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of controller / processor 280.

[0077] As indicated above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0078] Figure 3 This is a diagram illustrating example 300 of network slicing assignment for a UE according to this disclosure.

[0079] Network slicing involves implementing a logical network over a shared physical infrastructure, where each network slice may include end-to-end connectivity for functionality deployed for a specific application, application type, traffic type, or use case. Each network slice can be identified by a network slice identity. The network slice identity may include a slice identifier known as Single Network Slice Selection Auxiliary Information (S-NSSAI). The S-NSSAI can use a Slice Service Type (SST) value to indicate the SST. For example, the SST value may indicate the network slice type associated with enhanced mobile broadband (eMMB) communications, ultra-reliable low latency communications (uRLLC), IoT communications, or V2X communications.

[0080] like Figure 3 As shown, network slicing for the UE can be negotiated in the NAS registration procedure. As indicated by reference numeral 305, during the 5G Next Generation (NG) setup procedure, the base station (e.g., gNB) may transmit an NG setup request message to the Access and Mobility Management Function (AMF) of the core network (e.g., the 5G core network). The base station may include a list of S-NSSAIs supported by the base station in the NG setup request message. The S-NSSAI list may include S-NSSAIs supported by the Tracking Area Identity (TAI). As indicated by reference numeral 310, the AMF may transmit an NG setup response message to the base station. In some examples, the NG setup response message may include a list of S-NSSAIs supported by the AMF. For example, the list of S-NSSAIs supported by the AMF may include S-NSSAIs associated with network slice instances in the Public Land Mobile Network (PLMN).

[0081] As in Figure 3 As further illustrated by reference numeral 315, the UE may transmit a NAS registration request message including the requested NSSAI to the base station in an RRC Msg5 message. For example, the UE may transmit the RRC Msg5 message to the base station during the procedure used to establish a PDU session. The requested NSSAI may include a list of one or more S-NSSAIs. In some examples, the UE may select the requesting NSSAI from the NSSAIs configured for the UE. The UE may also include an Access Layer (AS) requested NSSAI in the RRC Msg5 message. The AS-requested NSSAI may be used by the base station to perform AMF selection from multiple AMF instances in the core network. In some examples, the AS-requested NSSAI may be a subset of the NSSAIs requested in the NAS registration request (e.g., due to security considerations regarding the RRC Msg5 message).

[0082] As shown by reference numeral 320, the base station may transmit an initial UE message to the AMF in the core network, which includes a NAS registration request message received from the UE. The AMF may determine the allowed NSSAIs for the UE based on the requested NSSAI. For example, the AMF may verify the requested NSSAI based on subscribed NSSAIs. Subscribed NSSAIs may be a list of S-NSSAIs subscribed to by the UE, and the AMF may compare each S-NSSAI in the requested NSSAIs with the subscribed NSSAIs to determine whether the UE has subscribed to that S-NSSAI. The AMF may determine whether(s) of the requested NSSAIs are in the list of supported S-NSSAIs of the TAI where the UE is located. Allowed NSSAIs may include one or more S-NSSAIs in the requested NSSAIs that are included in the subscribed NSSAIs and are in the list of supported S-NSSAIs supported by the TAI. In some examples, allowed NSSAIs may include(s) default S-NSSAIs if no valid S-NSSAIs are requested. Rejected NSSAIs include S-NSSAIs among the remaining NSSAIs not included in the allowed NSSAIs. As shown by reference numeral 325, the AMF may transmit a NAS registration acceptance message to the base station in the initial UE context setup request message, which indicates the allowed NSSAIs and rejected NSSAIs. The AMF may also include the allowed NSSAIs in the initial UE context setup request message.

[0083] As in Figure 3As shown by reference numeral 330, the base station can transmit a security mode command message to the UE. The security mode command message is used to command the UE to activate AS security. As shown by reference numeral 335, the base station can transmit a NAS registration acceptance message to the UE in an RRC reconfiguration message, which includes accepted NSSAIs and rejected NSSAIs. A PDU session established for the UE can be associated with a slice in the allowed NSSAIs (e.g., identified by S-NSSAIs). The UE can store UE context information, which includes configured NSSAIs, requested NSSAIs, allowed NSSAIs, and rejected NSSAIs. The base station can store UE context information, which includes allowed NSSAIs for the UE and NSSAIs for active PDU sessions. The AMF can store UE context information, which includes subscribed NSSAIs, requested NSSAIs, allowed NSSAIs, and rejected NSSAIs.

[0084] As indicated above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0085] In situations where the UE is in RRC idle mode or RRC inactive mode, incoming traffic (e.g., uplink or downlink traffic) can trigger the UE to execute RACH procedures to establish a PDU session. For mobile originating (MO) traffic originating from the UE (e.g., uplink traffic), the UE is aware of the intended slice for the PDU session. For example, the UE's NAS can indicate the allowed S-NSSAI for the PDU session. In this case, the UE can execute slice-aware RACH procedures. For example, the UE can select RACH resources from an isolated RACH resource pool associated with the intended slice and / or use RACH parameters associated with the priority level of the intended slice. However, for mobile terminating (MT) traffic terminating at the UE (e.g., downlink traffic), the UE may not be aware of the intended slice for the PDU session. Accordingly, the UE cannot execute slice-aware RACH procedures. Therefore, the UE may not be able to use the isolated RACH resources or RACH parameters associated with the intended slice. This may result in increased latency for RACH procedures and reduced priority (compared to MO traffic) based on the application, application type, traffic type, or use case associated with MT traffic.

[0086] Some of the techniques and apparatus described herein enable a UE to receive paging messages in RRC idle mode or RRC inactive mode, the paging messages including an indication of an expected slice for a PDU session associated with downlink (e.g., MT) traffic for the UE. The base station may transmit the paging message to the UE including the indication of the expected slice. The UE may transmit a request to the base station to initiate a slice-aware RACH procedure at least in part based on the expected slice. As a result, the latency of the RACH procedure for the UE can be reduced, and the RACH procedure can be prioritized based on the application, application type, traffic type, or use case associated with the expected slice.

[0087] Figure 4 This is a diagram illustrating an example 400 associated with signaling used to indicate expected slice information in paging, according to this disclosure. Figure 4 As shown, Example 400 includes communication between base station 110, UE 120, and the AMF (Active Network Function) of the core network. In some aspects, base station 110 and UE 120 may be included in a wireless network (such as wireless network 100). Base station 110 and UE 120 may communicate via a radio access link (which may include uplink and downlink). In some aspects, the AMF may be included in or may be included on one or more core network devices (such as network controller 130) in the core network. In some aspects, the core network may be a 5G core network or an LTE evolved packet core (EPC) network.

[0088] As in Figure 4 As shown by reference numeral 405 in the accompanying drawings, the AMF can transmit expected slice information to base station 110. The expected slice information can be slice information (e.g., S-NSSAI) identifying an expected slice associated with MT traffic (e.g., downlink traffic) for the UE. The expected slice is a network slice to be used in a PDU session to deliver MT traffic to the UE. In some aspects, the AMF can receive expected slice information for a PDU session from the Session Management Function (SMF) in the core network.

[0089] In some aspects, the AMF may transmit expected slice information to base stations in an N2 paging request message. N2 is the control plane interface between the NG-RAN (e.g., base station 110) and the 5G core network. In some aspects, such as in a scenario where UE 120 is in RRC idle mode, the AMF may transmit an N2 paging request message including expected slice information to all base stations in the tracking area associated with UE 120. For example, the AMF may transmit the N2 paging request message including expected slice information to base station 110 and to one or more other base stations in the tracking area associated with UE 120.

[0090] In some aspects, such as when UE 120 is in RRC inactive mode and base station 110 is an anchor base station associated with UE 120, base station 110 may transmit a RAN paging request message including expected slice information to one or more other base stations in the RAN-based notification area (RNA) associated with UE 120. In some aspects, such as when UE 120 is in RRC inactive mode and base station 110 is not an anchor base station associated with UE 120, base station 110 may receive expected slice information in a RAN paging message from an anchor base station associated with UE 120.

[0091] As in Figure 4 As further shown by reference numeral 410, base station 110 may transmit a paging message to UE 120, the paging message including an indication of an expected slice for a PDU session associated with MT traffic (e.g., downlink traffic) for UE 120. Base station 110 may transmit the paging message to UE 120 while UE 120 is in RRC idle mode or RRC inactive mode to alert UE 120 to an incoming connection request associated with MT traffic for UE 120. For example, the paging message may be a Physical Downlink Shared Channel (PDSCH) paging message transmitted to UE 120 during a paging event in a discontinuous reception (DRX) cycle associated with UE 120. The paging message may include UE 120's paging history, and base station 110 may include an indication of the expected slice in UE 120's paging history.

[0092] In some aspects, the indication may include an SST value associated with the intended slice. For example, the indication may include an SST value in the S-NSSAI associated with the intended slice. In this case, base station 110 may include the SST value in the paging record of UE 120.

[0093] In some aspects, the indication may include a slice group index associated with the intended slice. Base station 110 may include the slice group index in the paging records of UE 120. In this case, the AMF may store the slice group index for the intended slice used for the PDU session. UE 120 may be configured (e.g., before entering RRC idle mode or RRC inactive mode) to have slice groups for each of a plurality of slices (e.g., for each slice in the configured NSSAI or allowed NSSAI of UE 120). For example, slice groups may be configured for UE 120 via NSA messages or via subscription messages associated with NSSAIs subscribed to by UE 120.

[0094] In some aspects, the indication may include an emergency slice indication in the paging record of UE 120. For example, the emergency slice indication may be an indication in a specific field of the paging record. In this case, UE 120 may be configured with an emergency slice corresponding to the emergency slice indication (e.g., in the allowed NSSAI for UE 120). UE 120 may select one or more RACH resources in a prioritized RACH resource pool associated with the emergency slice and / or one or more RACH parameters associated with the emergency slice (e.g., RACH parameters associated with a high priority level) for RACH protocol.

[0095] In some aspects, this indication may include a PDU session identifier (ID) associated with the PDU session. Base station 110 may include the PDU session ID in the paging record of UE 120. In this case, UE 120 may derive the expected slice information from the PDU session ID. For example, UE 120 may determine the S-NSSAI of the expected slice based at least in part on the PDU session ID.

[0096] In some aspects, the indication may include a radio bearer ID for a logical channel associated with the intended slice. Base station 110 may include the radio bearer ID in the paging records of UE 120. Base station 110 may determine the radio bearer ID for the logical channel associated with the intended slice based at least in part on N3 tunnel information of MT traffic. N3 is the interface between the RAN (e.g., the base station) and the user plane function (UPF) in the 5G core network. UE 120 may determine the intended slice based at least in part on the radio bearer ID.

[0097] In some respects, base station 110 may map expected slice information to a cause value in the paging record of UE 120. The cause value is the value in the paging cause field of the paging record. Base station 110 may map expected slice information to a specific cause value based at least in part on a mapping between slice information (e.g., NSSAI) of multiple network slices and the corresponding cause value associated with each slice. UE 120 may be configured with this mapping (e.g., before entering RRC idle mode or RRC coupled mode) and may determine the expected slice based at least in part on the cause value in the paging record of UE 120.

[0098] In some aspects, UE 120 may receive the mapping configuration in the SIB transmitted by base station 110. In this case, after performing cell reselection (e.g., handover to a new cell), UE 120 may discard the stored mapping configuration and capture a new mapping configuration in the SIB of the new cell. In some aspects, UE 120 may receive the mapping configuration in a NAS message from a core network device (e.g., from an AMF). In some aspects, UE 120 may receive the mapping configuration in an RRC release message transmitted by base station 110. In some aspects, the mapping may be configured in UE 120 via subscription information associated with the network slice subscribed to by UE 120. In some aspects, UE 120 may (e.g., via a NAS message or via an RRC release message) receive a dynamic indication of the mapping configuration, and this dynamic indication may overwrite a previous mapping configuration (e.g., configured via an SIB or via subscription information).

[0099] In some respects, the expected slice information for UE 120 may be the same within the same tracking area (e.g., for different base stations within the same tracking area) and may be updated during a Tracking Area Update (TAU) procedure (e.g., for UE 120 in RRC idle mode) or a RAN Area Update (RNAU) procedure. In this case, the mapping between slice information and cause values ​​may be updated during the TAU and / or RNAU procedures, and UE 120 may receive the updated mapping configuration (e.g., via a NAS message).

[0100] In some aspects, the AMF or SMF can map expected slice information to a cause value, and the AMF can transmit the cause value to the base station 110. In this scenario, the base station 110 can receive the cause value from the AMF, include the cause value in the paging field of the paging record of the UE 120, and transmit a paging message including the paging record of the UE 120 to the UE 120.

[0101] As in Figure 4 As further shown by reference numeral 415 in the accompanying drawings, UE 120 may select RACH resources and / or RACH parameters at least in part based on the expected slice. UE 120 may determine the expected slice for the PDU session at least in part based on indications in the paging message, and UE 120 may select RACH resources and / or RACH parameters for the RACH procedure at least in part based on the expected slice.

[0102] In some aspects, UE 120 may identify slice-specific RACH resource pools configured for an expected slice. For example, slice-specific RACH resource pools may include resources that are separate from or isolated from shared RACH resource pools. UE 120 may select one or more RACH resources from the slice-specific resource pools for RACH procedures. In some aspects, UE 120 may identify RACH resource pools configured for a group of slices associated with an expected slice. UE 120 may select one or more RACH resources from the RACH resource pools configured for a group of slices associated with an expected slice for RACH procedures. As a result, UE 120 may avoid conflicts in shared RACH resource pools when executing RACH procedures.

[0103] In some aspects, UE 120 can select one or more RACH parameters configured for the intended slice for RACH procedures. For example, UE 120 can select one or more RACH parameters associated with a priority level configured for the intended slice. In some aspects, UE 120 can select one or more RACH parameters configured for a group of slices associated with the intended slice for RACH procedures. For example, UE 120 can select one or more RACH parameters associated with a priority level configured for a group of slices associated with the intended slice. In some aspects, the priority level configured for a slice or for a group of slices may correspond to a priority level associated with a specific application, application type, traffic type, or use case, etc. For example, the priority level may correspond to a priority level associated with eMMB communication, uRLLC, IoT communication, or V2X communication, etc.

[0104] As in Figure 4 As further shown by reference numeral 420 in the accompanying drawing, UE 120 can execute a slice-aware RACH procedure with base station 110 to establish a PDU session. UE 120 can transmit a request to base station 110 to initiate a RACH procedure using RACH resources and / or RACH parameters selected by UE 120 at least in part based on the expected slice selection for the PDU session.

[0105] As mentioned above Figure 4As described, base station 110 may transmit a paging message to a UE in RRC idle mode or RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink (e.g., MT) traffic for UE 120. UE 120 may receive the paging message including the indication of the expected slice, and UE 120 may select RACH resources and / or RACH parameters at least in part based on the expected slice. UE 120 may transmit a request to base station 110 to initiate a slice-aware RACH procedure using the selected RACH resources and / or RACH parameters. As a result, the latency of the RACH procedure for UE 120 can be reduced, and the RACH procedure can be prioritized based on the application, application type, traffic type, or use case associated with the expected slice.

[0106] As indicated above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0107] Figure 5 This is a diagram illustrating an example procedure 500 performed by a UE according to this disclosure. Example procedure 500 is an example in which a UE (e.g., UE 120) performs operations associated with signaling used to indicate expected slice information in paging.

[0108] like Figure 5 As shown, in some aspects, process 500 may include receiving a paging message in RRC idle mode or RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic for the UE (box 510). For example, the UE (e.g., using...) Figure 7 The receiving component 702 depicted can receive paging messages in RRC idle mode or RRC inactive mode, the paging messages including an indication of an expected slice for a PDU session associated with downlink traffic for the UE, as described above.

[0109] like Figure 5 As further shown, in some aspects, process 500 may include transmitting a request to the base station to initiate a RACH procedure at least in part based on the expected slice (box 520). For example, the UE (e.g., using...) Figure 7 The transmission component 704 described herein may transmit to the base station a request to initiate a RACH procedure at least in part based on the intended slice, as described above.

[0110] Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0111] In the first aspect, the indication includes the SST value associated with the expected slice.

[0112] In the second aspect, either alone or in combination with the first aspect, the indication includes a slice group index associated with the expected slice.

[0113] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 500 includes receiving a configuration for a corresponding slice group index for each of one or more permitted slices for the UE before receiving a paging message.

[0114] In the fourth aspect, alone or in combination with one or more of the first to third aspects, the instruction is an emergency slice instruction in the paging record of the paging message.

[0115] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 500 includes selecting one or more RACH resources associated with emergency slices for use in the RACH protocol.

[0116] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 500 includes selecting one or more RACH parameters associated with emergency slices for the RACH protocol.

[0117] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the indication includes a PDU session identifier associated with the PDU session, and the process 500 includes determining the S-NSSAI of the intended slice based at least in part on the PDU session identifier.

[0118] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the indication includes a radio bearer identifier for the logical channel associated with the intended slice.

[0119] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the indication includes a cause value in the paging record of the paging message, and the process 500 includes determining the expected slice based on the cause value, at least in part, the mapping between NSSAI and the cause value.

[0120] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 500 includes receiving a mapping in the SIB.

[0121] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 500 includes: discarding the mapping and receiving the new mapping in the SIB of the new cell.

[0122] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 500 includes receiving a mapping in a NAS message.

[0123] In the thirteenth aspect, the mapping is updated during at least one of the TAU or RNAU procedures, either alone or in combination with one or more of the first to twelfth aspects.

[0124] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 500 includes receiving a mapping in an RRC release message.

[0125] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the mapping is configured in the UE via subscription information associated with network slices.

[0126] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 500 includes selecting at least one of the RACH resources associated with the intended slice or the RACH parameters associated with the intended slice for the RACH protocol.

[0127] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 500 includes selecting one or more RACH resources from a RACH resource pool configured for the intended slice for the RACH procedure.

[0128] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 500 includes selecting one or more RACH resources from a RACH resource pool configured for use with a group of slices associated with the intended slice for RACH procedures.

[0129] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, process 500 includes selecting one or more RACH parameters for the RACH procedure that are associated with the priority level configured for the intended slice.

[0130] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, process 500 includes selecting one or more RACH parameters for the RACH procedure that are associated with a priority level configured to be associated with a group of slices intended for the slice.

[0131] although Figure 5 An example box of process 500 is shown, but in some respects, process 500 may include... Figure 5The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 500 can be executed in parallel.

[0132] Figure 6 This is a diagram illustrating an example process 600 performed by a base station according to this disclosure. Example process 600 is an example in which a base station (e.g., base station 110) performs operations associated with signaling used to indicate expected slice information in paging.

[0133] like Figure 6 As shown, in some aspects, process 600 may include transmitting a paging message to a UE in an RRC idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE (box 610). For example, a base station (e.g., using...) Figure 8 The transmission component 804 depicted can transmit a paging message to a UE in RRC idle mode or RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE, as described above.

[0134] like Figure 6 As further shown, in some aspects, process 600 may include receiving from the UE a request to initiate a RACH procedure at least in part based on the intended slice (box 620). For example, the base station (e.g., using...) Figure 8 The receiving component 802 described herein may receive from the UE a request to initiate a RACH procedure at least in part based on the expected slice, as described above.

[0135] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0136] In the first aspect, the indication includes the SST value associated with the expected slice.

[0137] In the second aspect, either alone or in combination with the first aspect, the indication includes a slice group index associated with the expected slice.

[0138] In a third aspect, either alone or in combination with one or more of the first and second aspects, the indication is an emergency slice indication in the paging record of the paging message.

[0139] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the indication includes a PDU session identifier associated with the PDU session.

[0140] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication includes a radio bearer identifier for a logical channel associated with the intended slice, and process 600 includes determining the radio bearer identifier for the logical channel associated with the intended slice based at least in part on N3 tunnel information of downlink traffic.

[0141] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication includes a cause value in the paging record of the paging message, which is mapped to an expected slice, and the process 600 includes determining the cause value mapped to the expected slice based at least in part on the mapping between NSSAI and the cause value.

[0142] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 600 includes transmitting a mapping to the UE in the SIB.

[0143] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 600 includes transmitting a mapping to the UE in an RRC release message.

[0144] In the ninth aspect, receiving a request to initiate a RACH procedure, either alone or in combination with one or more of the first to eighth aspects, includes receiving from the UE a request to initiate a RACH procedure using one or more RACH resources associated with the intended slice.

[0145] In the tenth aspect, receiving a request to initiate a RACH procedure, either alone or in combination with one or more of the first to ninth aspects, includes receiving from the UE a request to initiate a RACH procedure using one or more RACH parameters associated with the intended slice.

[0146] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 600 includes receiving slice information associated with the intended slice from the core network device.

[0147] In the twelfth aspect, receiving slice information associated with a desired slice, either alone or in combination with one or more of the first to eleventh aspects, includes receiving an N2 paging request from a core network device that includes the slice information associated with the desired slice.

[0148] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 600 includes transmitting a RAN paging message, which includes slice information associated with the intended slice, to one or more other base stations in the RNA associated with the UE.

[0149] In the fourteenth aspect, alone or in combination with one or more of the first to tenth aspects, process 600 includes receiving a RAN paging message from another base station in an RNA region associated with the UE, including slice information associated with a desired slice.

[0150] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes in process 600 can be executed in parallel.

[0151] Figure 7 This is a block diagram of an example device 700 for wireless communication. Device 700 may be a UE, or a UE may include device 700. In some aspects, device 700 includes a receiving component 702 and a transmitting component 704, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 700 may use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, device 700 may include one or more of a selection component 708, a determination component 710, or a discard component 712, etc.

[0152] In some respects, device 700 can be configured to perform the functions described herein. Figure 4 One or more operations described herein. Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein (such as...). Figure 5 The process 500), or a combination thereof. In some aspects, the device 700 and / or Figure 7 One or more components shown may include the above combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 7 One or more components shown can be combined as described above. Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0153] Receiver 702 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from device 706. Receiver 702 may provide the received communications to one or more other components of device 700. In some aspects, receiver 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signal to one or more other components of device 706. In some aspects, receiver 702 may include combinations of the above. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0154] The transmission component 704 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 706. In some aspects, one or more other components of the device 706 can generate communications and provide the generated communications to the transmission component 704 for transmission to the device 706. In some aspects, the transmission component 704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to the device 706. In some aspects, the transmission component 704 can include combinations of the above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 704 may be co-located with the receive component 702 in a transceiver.

[0155] The receiving component 702 may receive paging messages in RRC idle mode or RRC inactive mode, the paging messages including an indication of an expected slice for a PDU session associated with downlink traffic to the UE. The transmitting component 704 may transmit to the base station a request to initiate a RACH procedure at least in part based on the expected slice.

[0156] The receiving component 702 may receive a configuration of the corresponding slice group index for each of one or more permitted slices for the UE before receiving a paging message.

[0157] Select component 708 allows you to select one or more RACH resources associated with emergency slices for use in the RACH protocol.

[0158] Select component 708 allows you to select one or more RACH parameters associated with emergency slices for use in the RACH protocol.

[0159] The determination component 710 can determine the S-NSSAI of the expected slice based at least in part on the PDU session identifier.

[0160] Component 710 can determine the expected slice based on the cause value, at least in part, based on the mapping between NSSAI and cause value.

[0161] The receiving component 702 can receive mappings in the SIB.

[0162] Component 712 can be discarded as a mapping.

[0163] The receiving component 702 can receive the new mapping in the SIB of the new cell.

[0164] The receiving component 702 can receive mappings in NAS messages.

[0165] The receiving component 702 can receive the mapping in the RRC release message.

[0166] Select component 708 can select at least one of the following: RACH resources associated with the expected slice or RACH parameters associated with the expected slice for the RACH procedure.

[0167] Select component 708 allows you to select one or more RACH resources from the RACH resource pool configured for the intended slice, which are used in the RACH procedure.

[0168] Select component 708 allows you to select one or more RACH resources from a RACH resource pool that are configured for use with a group of slices associated with the intended slice in the RACH protocol.

[0169] Select component 708 allows you to select one or more RACH parameters for the RACH procedure that are associated with the priority level configured for the intended slice.

[0170] Select component 708 allows you to select one or more RACH parameters for the RACH procedure that are associated with the priority level of the slice group configured to be associated with the expected slice.

[0171] Figure 7 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 7 The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 7 The two or more components shown can be implemented within a single component, or Figure 7 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 7 The collection of components shown (e.g., one or more components) can be executed as described by Figure 7 The other set of components shown in the diagram performs one or more functions.

[0172] Figure 8 This is a block diagram of an example device 800 for wireless communication. Device 800 may be a base station, or a base station may include device 800. In some aspects, device 800 includes a receiving component 802 and a transmitting component 804, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 800 may use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (such as a UE, a base station, or another wireless communication device). As further shown, device 800 may include a determining component 808 and other examples.

[0173] In some respects, device 800 can be configured to perform the functions described herein. Figure 4 The described one or more operations. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein (such as...). Figure 6 The process 600), or a combination thereof. In some aspects, the device 800 and / or Figure 8 One or more components shown may include the above combination Figure 2 One or more components of the described base station. Additional or alternative. Figure 8 One or more components shown can be combined as described above. Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0174] Receiver 802 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from device 806. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signal to one or more other components of device 806. In some aspects, receiver 802 may include combinations of the above. Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0175] The transmission component 804 can transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 806. In some aspects, one or more other components of the device 806 can generate communications and provide the generated communications to the transmission component 804 for transmission to the device 806. In some aspects, the transmission component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to the device 806. In some aspects, the transmission component 804 can include combinations of the above. Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may be co-located with the receive component 802 in a transceiver.

[0176] The transmission component 804 may transmit a paging message to a UE in RRC idle mode or RRC inactive mode, the paging message including an indication of an expected slice for a PDU session associated with downlink traffic to the UE. The receiving component 802 may receive from the UE a request to initiate a RACH procedure at least in part based on the expected slice.

[0177] The determining component 808 can determine the radio bearer identifier for the logical channel associated with the expected slice based at least in part on the N3 tunnel information of downlink traffic.

[0178] Component 808 can determine the cause value mapped to the expected slice based at least in part on the mapping between NSSAI and cause values.

[0179] The transmission component 804 can transmit mappings to the UE in the SIB.

[0180] The transmission component 804 can transmit the mapping to the UE in the RRC release message.

[0181] The receiving component 802 can receive slice information associated with the expected slice from the core network device.

[0182] The transmission component 804 can transmit a RAN paging message, which includes slice information associated with the intended slice, to one or more other base stations in the RNA associated with the UE.

[0183] The receiving component 802 can receive a RAN paging message from another base station in the RNA associated with the UE, which includes slice information associated with the expected slice.

[0184] Figure 8 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 8The components shown are compared to additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The collection of components shown (e.g., one or more components) can be executed as described by Figure 8 The other set of components shown in the diagram performs one or more functions.

[0185] The following provides an overview of some aspects of this disclosure:

[0186] Aspect 1: A wireless communication method performed by a user equipment (UE) comprising: receiving a paging message in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and transmitting to a base station a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

[0187] Aspect 2: The method of aspect 1, wherein the indication includes a slice / service type (SST) value associated with the expected slice.

[0188] Aspect 3: The method of any of Aspects 1-2, wherein the indication includes a slice group index associated with the intended slice.

[0189] Aspect 4: The method of aspect 3 further includes: receiving a configuration of the corresponding slice group index for each of one or more permitted slices for the UE before receiving the paging message.

[0190] Aspect 5: The method of any of Aspects 1-4, wherein the indication is an emergency slice indication in the paging record of the paging message.

[0191] Aspect 6: The method of aspect 5 further includes: selecting one or more RACH resources associated with emergency slices for use in the RACH protocol.

[0192] Aspect 7: The method of any of Aspects 5-6 further includes: selecting one or more RACH resources associated with emergency slices for use in the RACH protocol.

[0193] Aspect 8: The method of any of Aspects 1-7, wherein the indication includes a PDU session identifier associated with a PDU session, and the method further includes: determining single network slice selection assistance information (S-NSSAI) for the intended slice based at least in part on the PDU session identifier.

[0194] Aspect 9: The method of any of Aspects 1-8, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice.

[0195] Aspect 10: The method of any of Aspects 1-9, wherein the indication includes a cause value in the paging record of the paging message, and the method further includes: determining the expected slice based on the cause value, at least in part, based on the mapping between Network Slice Selection Auxiliary Information (NSSAI) and the cause value.

[0196] Aspect 11: The method of aspect 10 further includes receiving the mapping in a system information block (SIB).

[0197] Aspect 12: The method of aspect 11 further includes, at least in part, based on the UE performing cell reselection in which the UE switches to a new cell: discarding the mapping; and receiving the new mapping in the SIB of the new cell.

[0198] Aspect 13: The method of any of Aspects 10-12 further includes: receiving the mapping in a Non-Access Layer (NAS) message.

[0199] Aspect 14: The method of aspect 13, wherein the mapping is updated during at least one of the Tracking Area Update (TAU) procedure or the Radio Access Network (RAN) Area Update (RNAU) procedure.

[0200] Aspect 15: The method of any of Aspects 10-14 further includes: receiving the mapping in an RRC release message.

[0201] Aspect 16: The method of any of Aspects 10-15, wherein the mapping is configured in the UE via subscription information associated with a network slice.

[0202] Aspect 17: The method of any of Aspects 1-16 further includes: selecting at least one of a RACH resource associated with the expected slice or a RACH parameter associated with the expected slice for the RACH procedure.

[0203] Aspect 18: The method of any of Aspects 1-17 further includes: selecting one or more RACH resources from a RACH resource pool configured for the intended slice for the RACH procedure.

[0204] Aspect 19: The method of any of Aspects 1-17 further includes: selecting one or more RACH resources from a RACH resource pool configured for use with a group of slices associated with the intended slice for RACH procedures.

[0205] Aspect 20: The method of any of Aspects 1-19 further includes: selecting one or more RACH parameters for the RACH procedure that are associated with the priority level configured for the intended slice.

[0206] Aspect 21: The method of any of Aspects 1-19 further includes: selecting one or more RACH parameters for the RACH procedure that are associated with a priority level configured to be associated with a group of slices of the intended slice.

[0207] Aspect 22: A wireless communication method performed by a base station, comprising: transmitting a paging message to a user equipment (UE) in a Radio Resource Control (RRC) idle mode or an RRC inactive mode, the paging message including an indication of an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and receiving from the UE a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

[0208] Aspect 23: The method of aspect 22, wherein the indication includes a slice / service type (SST) value associated with the intended slice.

[0209] Aspect 24: The method of any of Aspects 22-23, wherein the indication includes a slice group index associated with the intended slice.

[0210] Aspect 25: The method of any of Aspects 22-24, wherein the indication is an emergency slice indication in the paging record of the paging message.

[0211] Aspect 26: The method of any of Aspects 22-5, wherein the indication includes a PDU session identifier associated with the PDU session.

[0212] Aspect 27: The method of any of Aspects 22-26, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice, and the method further includes: determining the radio bearer identifier for the logical channel associated with the intended slice based at least in part on N3 tunnel information of downlink traffic.

[0213] Aspect 28: The method of any of Aspects 22-27, wherein the indication includes a cause value in the paging record of the paging message, wherein the cause value is mapped to the expected slice, and further includes: determining the cause value mapped to the expected slice based at least in part on the mapping between Network Slice Selection Auxiliary Information (NSSAI) and the cause value.

[0214] Aspect 29: The method of aspect 28 further includes: transmitting the mapping to the UE in a system information block (SIB).

[0215] Aspect 30: The method of any of Aspects 28-29 further includes: transmitting the mapping to the UE in an RRC release message.

[0216] Aspect 31: The method of any of Aspects 22-30, wherein receiving a request to initiate a RACH procedure includes: receiving from the UE a request to initiate a RACH procedure using one or more RACH resources associated with the intended slice.

[0217] Aspect 32: The method of any of Aspects 22-31, wherein receiving a request to initiate a RACH procedure includes: receiving from the UE a request to initiate a RACH procedure using one or more RACH parameters associated with the intended slice.

[0218] Aspect 33: The method of any of Aspects 22-32 further includes: receiving slice information associated with the intended slice from a core network device.

[0219] Aspect 34: The method of aspect 33, wherein receiving slice information associated with a desired slice includes: receiving an N2 paging request from a core network device that includes slice information associated with the desired slice.

[0220] Aspect 35: The method of any of Aspects 33-34 further includes: transmitting a RAN paging message including slice information associated with the intended slice to one or more other base stations in a notification area based on the radio access network (RAN) associated with the UE.

[0221] Aspect 36: The method of any of Aspects 22-32 further includes: receiving a RAN paging message from another base station in a notification area of ​​the radio access network (RAN) associated with the UE, including slice information associated with the intended slice.

[0222] Aspect 37: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 1-21.

[0223] Aspect 38: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the methods described in one or more of aspects 22-36.

[0224] Aspect 39: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method as described in one or more aspects of aspects 1-21.

[0225] Aspect 40: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods described in one or more aspects of aspects 22-36.

[0226] Aspect 41: An apparatus for wireless communication, comprising at least one means for performing the method as described in one or more of aspects 1-21.

[0227] Aspect 42: An apparatus for wireless communication, comprising at least one means for performing the method as described in one or more aspects of aspects 22-36.

[0228] Aspect 43: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of aspects 1-21.

[0229] Aspect 44: A non-transient computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods described in one or more of aspects 22-36.

[0230] Aspect 45: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform the methods described in one or more aspects of aspects 1-21.

[0231] Aspect 46: A non-transient computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions which, when executed by one or more processors of a device, cause the device to perform the methods described in one or more aspects of aspects 22-36.

[0232] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice.

[0233] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, processors are implemented using hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in any way. Thus, the operation and behavior of these systems and / or methods are described herein without reference to any specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the descriptions herein.

[0234] As used in this article, depending on the context, a threshold can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0235] Although specific combinations of features are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below may be directly subordinated to only one claim, the disclosure of aspects includes each dependent claim being combined with each other claim in this set of claims. As used herein, the phrase “at least one of” refers to any combination of these items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0236] The elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “a certain” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referenced in conjunction with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Moreover, as used herein, the terms “have,” “contain,” “include,” etc., are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Moreover, as used herein, the term “or” is intended to be inclusive when used in a sequence and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., in combination with “either of” or “only one of”).

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: Receiving a paging message in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging message including an indication identifying an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and A request is transmitted to the base station to initiate a Random Access Channel (RACH) procedure at least in part based on the intended slice. The indicated value includes the cause value in the paging record of the paging message, and The method further includes: determining the expected slice based on the cause value, at least in part, the mapping between Network Slice Selection Auxiliary Information (NSSAI) and the cause value.

2. The method of claim 1, wherein the indication includes a slice / service type (SST) value associated with the intended slice.

3. The method of claim 1, wherein the indication includes a slice group index associated with the intended slice.

4. The method of claim 3, further comprising: Before receiving the paging message, the configuration of the corresponding slice group index for each of one or more allowed slices for the UE is received.

5. The method of claim 1, wherein the indication is an emergency slice indication in the paging record of the paging message.

6. The method of claim 5, further comprising: Select one or more RACH resources associated with the emergency slice for the RACH procedure.

7. The method of claim 5, further comprising: Select one or more RACH parameters associated with the emergency slice for the RACH procedure.

8. The method of claim 1, wherein the indication includes a PDU session identifier associated with the PDU session, and the method further includes: The Single Network Slice Selection Auxiliary Information (S-NSSAI) for the expected slice is determined at least in part based on the PDU session identifier.

9. The method of claim 1, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice.

10. The method of claim 1, further comprising: The mapping is received in the System Information Block (SIB).

11. The method of claim 10, further comprising performing cell reselection, at least in part, based on the UE, wherein the UE switches to a new cell: Discard the mapping; and The new mapping is received in the SIB of the new cell.

12. The method of claim 1, further comprising: The mapping is received in the Non-Access Layer (NAS) message.

13. The method of claim 12, wherein the mapping is updated during at least one of a Tracking Area Update (TAU) procedure or a Radio Access Network (RAN) Area Update (RNAU) procedure.

14. The method of claim 1, further comprising: The mapping is received in the RRC release message.

15. The method of claim 1, wherein the mapping is configured in the UE via subscription information associated with a network slice.

16. The method of claim 1, further comprising: Select at least one of the RACH resources associated with the expected slice or the RACH parameters associated with the expected slice for the RACH procedure.

17. The method of claim 1, further comprising: Select one or more RACH resources from the RACH resource pool configured for the intended slice, for the RACH procedure.

18. The method of claim 1, further comprising: Select one or more RACH resources from the RACH resource pool configured to be associated with the expected slice for the RACH procedure.

19. The method of claim 1, further comprising: Select one or more RACH parameters for the RACH procedure that are associated with the priority level configured for the intended slice.

20. The method of claim 1, further comprising: Select one or more RACH parameters for the RACH procedure that are associated with the priority level of the slice group configured to be associated with the expected slice.

21. A wireless communication method performed by a base station, comprising: A paging message is transmitted to a user equipment (UE) in Radio Resource Control (RRC) idle mode or RRC inactive mode. The paging message includes an indication of a proposed slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE. The indication includes a cause value in the paging record of the paging message, and the identification of the proposed slice is based at least in part on a mapping between Network Slice Selection Assist Information (NSSAI) associated with the proposed slice and the cause value. as well as The UE receives a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

22. The method of claim 21, wherein the indication includes a slice / service type (SST) value associated with the intended slice.

23. The method of claim 21, wherein the indication includes a slice group index associated with the intended slice.

24. The method of claim 21, wherein the indication is an emergency slice indication in the paging record of the paging message.

25. The method of claim 21, wherein the indication includes a PDU session identifier associated with the PDU session.

26. The method of claim 21, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice, and the method further includes: The radio bearer identifier for the logical channel associated with the expected slice is determined at least in part based on the N3 tunnel information of the downlink traffic.

27. The method of claim 21, further comprising: The mapping is transmitted to the UE in the System Information Block (SIB).

28. The method of claim 21, further comprising: The mapping is transmitted to the UE in the RRC release message.

29. The method of claim 21, wherein receiving the request to initiate the RACH procedure comprises: The UE receives a request to initiate a RACH procedure using one or more RACH resources associated with the intended slice.

30. The method of claim 21, wherein receiving the request to initiate the RACH procedure comprises: The UE receives a request to initiate a RACH procedure using one or more RACH parameters associated with the intended slice.

31. The method of claim 21, further comprising: Receive slice information associated with the expected slice from the core network device.

32. The method of claim 31, wherein receiving the slice information associated with the expected slice comprises: Receive an N2 paging request from the core network device, which includes slice information associated with the intended slice.

33. The method of claim 31, further comprising: Transmit a RAN paging message, including slice information associated with the intended slice, to one or more other base stations in the notification area of ​​the radio access network (RAN) associated with the UE.

34. The method of claim 21, further comprising: Receives a RAN paging message, including slice information associated with the expected slice, from another base station in the notification area of ​​the radio access network (RAN) associated with the UE.

35. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: Receiving a paging message in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging message including an indication identifying an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and A request is transmitted to the base station to initiate a Random Access Channel (RACH) procedure at least in part based on the intended slice. The indicated value includes the cause value in the paging record of the paging message, and The memory and the one or more processors are further configured to determine the expected slice based on the cause value, at least in part, the mapping between Network Slice Selection Auxiliary Information (NSSAI) and the cause value.

36. The UE of claim 35, wherein the indication includes a slice / service type (SST) value associated with the intended slice.

37. The UE of claim 35, wherein the indication includes a slice group index associated with the intended slice.

38. The UE of claim 37, wherein the one or more processors are further configured to: Before receiving the paging message, the configuration of the corresponding slice group index for each of one or more allowed slices for the UE is received.

39. The UE of claim 35, wherein the indication is an emergency slice indication in the paging record of the paging message.

40. The UE of claim 39, wherein the one or more processors are further configured to: Select one or more RACH resources associated with the emergency slice for the RACH procedure.

41. The UE of claim 39, wherein the one or more processors are further configured to: Select one or more RACH parameters associated with the emergency slice for the RACH procedure.

42. The UE of claim 35, wherein the indication includes a PDU session identifier associated with the PDU session, and the one or more processors are further configured to: The Single Network Slice Selection Auxiliary Information (S-NSSAI) for the expected slice is determined at least in part based on the PDU session identifier.

43. The UE of claim 35, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice.

44. The UE of claim 35, wherein the one or more processors are further configured to: The mapping is received in the System Information Block (SIB).

45. The UE of claim 44, wherein the one or more processors are further configured to: perform cell reselection, at least in part, based on the UE, wherein the UE switches to a new cell: Discard the mapping; and The new mapping is received in the SIB of the new cell.

46. ​​The UE of claim 35, wherein the one or more processors are further configured to: The mapping is received in the Non-Access Layer (NAS) message.

47. The UE of claim 46, wherein the mapping is updated during at least one of a Tracking Area Update (TAU) procedure or a Radio Access Network (RAN) Area Update (RNAU) procedure.

48. The UE of claim 35, wherein the one or more processors are further configured to: The mapping is received in the RRC release message.

49. The UE of claim 35, wherein the mapping is configured in the UE via subscription information associated with a network slice.

50. The UE of claim 35, wherein the one or more processors are further configured to: Select at least one of the RACH resources associated with the expected slice or the RACH parameters associated with the expected slice for the RACH procedure.

51. The UE of claim 35, wherein the one or more processors are further configured to: Select one or more RACH resources from the RACH resource pool configured for the intended slice, for the RACH procedure.

52. The UE of claim 35, wherein the one or more processors are further configured to: Select one or more RACH resources from the RACH resource pool configured to be associated with the expected slice for the RACH procedure.

53. The UE of claim 35, wherein the one or more processors are further configured to: Select one or more RACH parameters for the RACH procedure that are associated with the priority level configured for the intended slice.

54. The UE of claim 35, wherein the one or more processors are further configured to: Select one or more RACH parameters for the RACH procedure that are associated with the priority level of the slice group configured to be associated with the expected slice.

55. A base station for wireless communication, comprising: Memory; as well as One or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: A paging message is transmitted to a user equipment (UE) in Radio Resource Control (RRC) idle mode or RRC inactive mode. The paging message includes an indication of a proposed slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE. The indication includes a cause value in the paging record of the paging message, and the identification of the proposed slice is based at least in part on a mapping between Network Slice Selection Assist Information (NSSAI) associated with the proposed slice and the cause value. as well as The UE receives a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

56. The base station of claim 55, wherein the indication includes a slice / service type (SST) value associated with the intended slice.

57. The base station of claim 55, wherein the indication includes a slice group index associated with the intended slice.

58. The base station of claim 55, wherein the indication is an emergency slice indication in the paging record of the paging message.

59. The base station of claim 55, wherein the indication includes a PDU session identifier associated with the PDU session.

60. The base station of claim 55, wherein the indication includes a radio bearer identifier for a logical channel associated with the intended slice, and the one or more processors are further configured to: The radio bearer identifier for the logical channel associated with the expected slice is determined at least in part based on the N3 tunnel information of the downlink traffic.

61. The base station of claim 55, wherein the one or more processors are further configured to: The mapping is transmitted to the UE in the System Information Block (SIB).

62. The base station of claim 55, wherein the one or more processors are further configured to: The mapping is transmitted to the UE in the RRC release message.

63. The base station of claim 55, wherein the one or more processors are configured, upon receiving the request to initiate the RACH procedure, to: The UE receives a request to initiate a RACH procedure using one or more RACH resources associated with the intended slice.

64. The base station of claim 55, wherein the one or more processors are configured, upon receiving the request to initiate the RACH procedure, to: The UE receives a request to initiate a RACH procedure using one or more RACH parameters associated with the intended slice.

65. The base station of claim 55, wherein the one or more processors are further configured to: Receive slice information associated with the expected slice from the core network device.

66. The base station of claim 65, wherein the one or more processors, when receiving the slice information associated with the intended slice, include: Receive an N2 paging request from the core network device, which includes slice information associated with the intended slice.

67. The base station of claim 65, wherein the one or more processors are further configured to: Transmit a RAN paging message, including slice information associated with the intended slice, to one or more other base stations in the notification area of ​​the radio access network (RAN) associated with the UE.

68. The base station of claim 55, wherein the one or more processors are further configured to: Receives a RAN paging message, including slice information associated with the expected slice, from another base station in the notification area of ​​the radio access network (RAN) associated with the UE.

69. A non-transient computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of a user equipment (UE), cause the UE to: Receiving a paging message in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging message including an indication identifying an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE; and A request is transmitted to the base station to initiate a Random Access Channel (RACH) procedure at least in part based on the intended slice. The indicated value includes the cause value in the paging record of the paging message, and When the one or more instructions are executed by one or more processors of the user equipment (UE), the UE further causes the UE to: determine the expected slice based on the cause value, at least in part, the mapping between Network Slice Selection Assistance Information (NSSAI) and the cause value.

70. A non-transient computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of the base station, cause the base station to: A paging message is transmitted to a user equipment (UE) in Radio Resource Control (RRC) idle mode or RRC inactive mode. The paging message includes an indication of a proposed slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE. The indication includes a cause value in the paging record of the paging message, and the identification of the proposed slice is based at least in part on a mapping between Network Slice Selection Assist Information (NSSAI) associated with the proposed slice and the cause value. as well as The UE receives a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

71. A device for wireless communication, comprising: A means for receiving paging messages in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging messages including an indication of an expected slice for a Protocol Data Unit (PDU) session associated with downlink traffic to the device; as well as A means for transmitting to a base station a request to initiate a Random Access Channel (RACH) procedure at least in part based on the intended slice. The indicated value includes the cause value in the paging record of the paging message, and The device further includes means for determining the expected slice based on the cause value, at least in part, a mapping between Network Slice Selection Auxiliary Information (NSSAI) and the cause value.

72. A device for wireless communication, comprising: Means for transmitting a paging message to a user equipment (UE) in Radio Resource Control (RRC) idle mode or RRC inactive mode, the paging message including an indication of a proposed slice for a Protocol Data Unit (PDU) session associated with downlink traffic for the UE, wherein the indication includes a cause value in the paging record of the paging message, and the identification of the proposed slice is based at least in part on a mapping between Network Slice Selection Assist Information (NSSAI) associated with the proposed slice and the cause value; as well as A means for receiving from the UE a request to initiate a Random Access Channel (RACH) procedure at least in part based on the expected slice.

Citation Information

Patent Citations

  • User equipment, base station and method for paging procedure

    WO2019138060A1