Method for wireless communication at user equipment

Abstract

Aspects relate to a random access procedure. Different random access channel (RACH) configurations may be defined for different service groups. For example, one or more service groups (e.g., network slice groups) may be defined, where each service group includes one or more services (network slices). One RACH configuration may be defined for one service group, another RACH configuration may be defined for another service group, and the like. Each service group may be configured with a different set of RACH parameters. Within each service group, one or more services may be configured with dedicated (e.g., non-cell-specific) RACH resources, and other services may be configured with cell-specific RACH resources. Each service group may be configured with a different RACH resource. Within each service group, one or more services may be configured with a set of dedicated (e.g., non-cell-specific) RACH parameters, and other services may be configured with a set of cell-specific RACH resources.

Description

[0001] This application is a divisional application of the China Invention Patent Application with the application date of October 30, 2020, the application number of 202080106732.2, and the invention name of “Service Group for Random Access”. TECHNICAL FIELD

[0002] The technology discussed below relates generally to wireless communication, and more particularly to service group based configuration for transmission of random access messages. BACKGROUND

[0003] A next generation wireless communication system (e.g., 5GS) can include a 5G core network and a 5G radio access network (RAN), such as a New Radio (NR)-RAN. The NR-RAN supports communication via one or more cells. For example, a wireless communication device, such as a user equipment (UE), can access a first cell of a first base station (BS), such as a gNB, and / or access a second cell of a second base station.

[0004] A base station can schedule access to a cell to support access by multiple UEs. For example, a base station can allocate different resources (e.g., time and frequency domain resources) for different UEs operating within a cell of the base station. A UE can initiate a random access procedure to initially gain access to a cell. If the random access procedure is successful, the UE can connect to the cell for subsequent scheduling by the base station. SUMMARY

[0005] The following presents a summary of one or more aspects of the present disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the present disclosure, and is not intended to identify key or critical elements of the present disclosure or to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form that is brief, in that the summary is presented in a summary form in order to later present a more detailed description of the present disclosure.

[0006] Various aspects of the present disclosure relate to random access procedures. In some examples, different random access channel (RACH) configurations can be defined for different service groups. For example, one or more service groups (e.g., network slice groups) can be defined, where each service group includes one or more services (network slices). Additionally, one RACH configuration can be defined for one service group, another RACH configuration can be defined for another service group, and so on.

[0007] In some examples, each service group can be configured with a different set of RACH parameters. Additionally, within each service group, one or more services can be configured with dedicated (e.g., non-cell specific) RACH resources, and other services can be configured with cell specific RACH resources.

[0008] In some examples, each service group can be configured with different RACH resources. Additionally, within each service group, one or more services can be configured with a dedicated (e.g., non-cell-specific) set of RACH parameters, and other services can be configured with a cell-specific set of RACH resources.

[0009] In some examples, a method for wireless communication at a user equipment can include identifying a service; selecting a first random access channel (RACH) configuration for the service from a set of RACH configurations for a plurality of groups of services; and performing a RACH operation for the service in accordance with the first RACH configuration.

[0010] In some examples, a user equipment can include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory can be configured to identify a service; select a first random access channel (RACH) configuration for the service from a set of RACH configurations for a plurality of groups of services; and perform, via the transceiver, a RACH operation for the service in accordance with the first RACH configuration.

[0011] In some examples, a user equipment can include means for identifying a service; means for selecting a first random access channel (RACH) configuration for the service from a set of RACH configurations for a plurality of groups of services; and means for performing a RACH operation for the service in accordance with the first RACH configuration.

[0012] In some examples, an article for use by a user equipment includes a computer- readable medium having instructions stored therein, the instructions executable by one or more processors of the user equipment to: identify a service; select a first random access channel (RACH) configuration for the service from a set of RACH configurations for a plurality of groups of services; and perform a RACH operation for the service in accordance with the first RACH configuration.

[0013] One or more of the following features can be applicable to one or more of the methods, apparatuses, and computer readable media of the preceding paragraphs. The multiple groups of services can be multiple groups of network slices. The first RACH configuration can specify RACH resources for RACH operations and / or RACH parameters for RACH operations. The RACH parameters can be preamble ramping step and / or backoff scaling factor. The RACH resources can be preamble groups and / or RACH occasions (ROs). The RACH configuration and RACH operations can be for 4-step RACH and / or 2-step RACH. The indication of the set of RACH configurations can be received from the base station via a radio resource control (RRC) message, a system information block (SIB), or a non-access stratum (NAS) message. The set of RACH configurations can specify a first RACH configuration for a first group of slices and a second RACH configuration for a second group of slices different from the first group of slices.

[0014] In some examples, a method for wireless communication at a base station can include defining a set of RACH configurations for multiple groups of services; transmitting an indication of the set of RACH configurations; and receiving a RACH message in accordance with a first RACH configuration of the set of RACH configurations. The RACH message can be for at least one service of a first group of the multiple groups of services.

[0015] In some examples, a base station can include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory can be configured to define a set of RACH configurations for multiple groups of services; transmit, via the transceiver, an indication of the set of RACH configurations; and receive, via the transceiver, a RACH message in accordance with a first RACH configuration of the set of RACH configurations. The RACH message can be for at least one service of a first group of the multiple groups of services.

[0016] In some examples, a base station can include means for defining a set of RACH configurations for multiple groups of services; means for transmitting an indication of the set of RACH configurations; and means for receiving a RACH message in accordance with a first RACH configuration of the set of RACH configurations. The RACH message can be for at least one service of a first group of the multiple groups of services.

[0017] In some examples, an article for use by a base station includes a computer- readable medium having instructions stored therein, the instructions executable by one or more processors of the base station to: define a set of RACH configurations for multiple groups of services; transmit an indication of the set of RACH configurations; and receive a RACH message in accordance with a first RACH configuration of the set of RACH configurations. The RACH message can be for at least one service of a first group of the multiple groups of services.

[0018] One or more of the following features can be applicable to one or more of the methods, apparatuses, and computer-readable media of the preceding paragraphs. The multiple groups of services can be multiple groups of network slices. The first RACH configuration can specify RACH resources for RACH operations and / or RACH parameters for RACH operations. The RACH parameters can be preamble ramping steps and / or backoff scaling factors. The RACH resources can be preamble groups and / or RACH occasions (ROs). The RACH configuration and RACH operations can be for 4-step RACH and / or 2-step RACH. The indication of the set of RACH configurations can be transmitted to the UE via a radio resource control (RRC) message, a system information block (SIB), or a non-access stratum (NAS) message. The set of RACH configurations can specify a first RACH configuration for a first slice group and a second RACH configuration for a second slice group different from the first slice group.

[0019] These and other aspects of the disclosure will become more fully understood upon review of the following detailed description in conjunction with the accompanying drawings. Other aspects, features, and embodiments of the disclosure will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary embodiments of the disclosure in conjunction with the accompanying figures. While features of the disclosure are discussed relative to certain embodiments and figures below, any of the features discussed herein can be used in conjunction with any of the other features discussed herein. In other words, while one or more embodiments can be discussed as having certain advantageous features, one or more of these features can be used alone or in combination with any of the other features discussed herein according to the various embodiments of the disclosure discussed herein. In a similar manner, embodiments can be discussed above as devices, systems, or methods. It should be understood that such embodiments can be implemented in combination with each other in devices, systems, and methods. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects.

[0021] Figure 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects.

[0022] Figure 3 is a schematic illustration of an example of wireless resources in an air interface that utilizes orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0023] Figure 4A is a diagram illustrating an example of a frame structure for synchronization signals for use in a wireless communication network in accordance with some aspects.

[0024] Figure 4Bis a diagram illustrating an example of a portion of a frame or subframe structure and various channels and associated messages for use in a wireless communication network, in accordance with some aspects.

[0025] Figure 5 is a signaling diagram of an example of random access channel (RACH) signaling, in accordance with some aspects.

[0026] Figure 6 is a signaling diagram of an example of slice related signaling, in accordance with some aspects.

[0027] Figure 7 is a flow diagram of an example method for defining a slice specific RACH configuration, in accordance with some aspects.

[0028] Figure 8 is a flow diagram of an example method for transmitting a random access message using a slice specific RACH configuration, in accordance with some aspects.

[0029] Figure 9 is a signaling diagram illustrating an example of RACH related signaling, in accordance with some aspects.

[0030] Figure 10 is a block diagram illustrating an example of a hardware implementation for a user equipment employing a processing system, in accordance with some aspects.

[0031] Figure 11 is a flow diagram of an example radio access method, in accordance with some aspects.

[0032] Figure 12 is a block diagram illustrating an example of a hardware implementation for a base station employing a processing system, in accordance with some aspects.

[0033] Figure 13 is a flow diagram of an example radio access method, in accordance with some aspects. DETAILED DESCRIPTION

[0034] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts being described.

[0035] While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases can come about in many different arrangements and scenarios. Innovations described herein can be implemented across many differing platform types, devices, systems, form factors, and packaging arrangements. For example, embodiments and / or use cases can come about in the context of integrated chip embodiments, and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence-enabled devices, and / or the like). Some examples can or can not be exclusively for or solely related to a particular use case or application. A wide assortment of implementations can come about through the implementation of innovations described herein across a range of platform types, devices, systems, form factors, and packaging arrangements. Implementations can range from full-fledged microprocessor-chip level implementations to smaller or larger implementations that can to some extent be more or less related to a particular use case or application. In some physical settings, devices incorporating aspects and features described can necessarily include additional components and features to realize and practice the claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, and / or the like). Innovations described herein are intended to be workable across a wide array of devices, chip-level components, systems, distributed arrangements, end-user devices, and / or the like of varying sizes, shapes, and constitutions.

[0036] The various concepts presented throughout this disclosure can be implemented across a wide range of telecommunications systems, network architectures, and communication standards. Referring now to Figure 1 by way of illustrative example, and not limitation, various aspects of the present disclosure are illustrated with reference to the wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and at least one scheduled entity 106. The at least one scheduled entity 106 can be referred to as a user equipment (UE) 106 in the following discussion. The RAN 104 includes at least one scheduling entity 108. The at least one scheduling entity 108 can be referred to as a base station (BS) 108 in the following discussion. By way of the wireless communication system 100, UEs 106 can be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.

[0037] The RAN 104 can implement any suitable wireless communication technology or technologies to provide radio access to the UEs 106. As one example, the RAN 104 can operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications (often referred to simply as 5G). As another example, the RAN 104 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (often referred to as LTE). The 3GPP refers to this hybrid RAN as a Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of the present disclosure.

[0038] As shown, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network that carries out the radio transmission and reception for a cell or cells to and from UEs. In different technologies, standards, or contexts, a base station can variously be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B, an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP), or some other suitable terminology. In some examples, a base station can include two or more TRPs that can be co-located or non-co-located. The TRPs can communicate on the same carrier frequency or different carrier frequencies, within the same frequency band or different frequency bands.

[0039] The radio access network 104 is further illustrated in the figure to support wireless communication for multiple mobile apparatuses. A mobile apparatus can be referred to as user equipment (UE) in 3GPP standards, but can also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. The UE can be a device that provides access to network services for a user.

[0040] Within this document, a “mobile” device does not necessarily need to be mobile and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE can include multiple hardware structural components of a size and shape designed and arranged to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the “Internet of Things” (IoT). A mobile device can also be an autonomous or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remotely controlled device, consumer and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, and so on. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, urban infrastructure equipment controlling electrical power (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weapons, etc. Furthermore, mobile devices can provide networked healthcare or telemedicine support, i.e., remote healthcare. Remote healthcare devices can include remote healthcare monitoring devices and remote healthcare supervision devices, whose communications can be prioritized, for example, through priority access to critical service data transmission and / or related QoS for critical service data transmission, or prioritized over other types of information.

[0041] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. In some examples, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (described further below; e.g., base station 108). Another way to describe such a point-to-multipoint transmission scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. In some examples, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (described further below; e.g., UE 106).

[0042] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UE 106 (which may be a scheduled entity) can utilize the resources allocated by scheduling entity 108.

[0043] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).

[0044] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities 106. In a broader sense, scheduling entity 108 is a node or device responsible for scheduling services in the wireless communication network, including downlink service 112, and in some examples, uplink service 116 and / or uplink control information 118 from one or more scheduled entities 106 to scheduling entity 108. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., authorization), synchronization or timing information), or other control information from another entity in the wireless communication network (such as scheduling entity 108).

[0045] Additionally, uplink and / or downlink control information and / or service information can be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in which one resource element (RE) is carried per subcarrier in an Orthogonal Frequency Division Multiplexing (OFDM) waveform. In some examples, a time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 millisecond (ms). Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Of course, these limitations are not mandatory, and any suitable scheme can be used to organize the waveform, and the various time divisions of the waveform can have any suitable duration.

[0046] Generally, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network may provide interconnection between the respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0047] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G evolved packet core (EPC) or any other suitable standard or configuration.

[0048] Now for reference Figure 2 The RAN 200 is provided as an illustrative example rather than a limitation. In some examples, the RAN 200 may be the same as described above and in... Figure 1 The same applies to RAN 104 shown. The geographical area covered by RAN 200 can be divided into cellular areas (cells), which can be uniquely identified by user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206, and small cell 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by separate antenna groups, where each antenna is responsible for communication with UEs in a portion of the cell.

[0049] Various base stations can be used for deployment. For example, in Figure 2In the illustration, two base stations 210 and 212 are shown in cells 202 and 204, and a third base station 214 is shown as a remote radio head (RRH) 216 in control cell 206. That is, the base stations can have integrated antennas, or they can be connected to the antenna or RRH via feed cables. In the illustrated example, cells 202, 204, and 206 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in small cell 208 (e.g., microcell, picocell, femtocell, home base station, home B node, home eNodeB, etc.), which may overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell size design can be accomplished based on system design and component constraints.

[0050] It will be understood that the radio access network 200 may include any number of wireless base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be as described above and in... Figure 1 The base station / scheduling entity 108 shown is the same.

[0051] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, and 218 can be configured to provide core network (e.g., ...) services to all UEs within the corresponding cell. Figure 1 The access points are as shown above. For example, UE 222 and UE 224 can communicate with base station 210; UE 226 and UE 228 can communicate with base station 212; UE 230 and UE 232 can communicate with base station 214 via RRH 216; and UE 234 can communicate with base station 218. In some examples, UE 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can be the access points described above and in... Figure 1 The UE / scheduled entity 106 shown is the same.

[0052] In some examples, the unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter, can be a mobile network node and can be configured to act as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210. In some examples, UAV 220 can be configured to act as a BS (e.g., serving UE 236). That is, in some examples, the cell may not be fixed, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as UAV 220).

[0053] In a radio access network 200, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. Various physical channels between the UE and the radio access network are typically established, maintained, and released under the control of the Access and Mobility Management Function (AMF). Figure 2 (Not shown) may include a Security Context Management (SCMF) function for managing security contexts for both control plane and user plane functions, and a Security Anchoring (SEAF) function for performing authentication.

[0054] Radio access network 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the UE's connection is transferred from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to the neighboring (target) cell. For example, UE 224 (shown as a vehicle, but any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds the signal strength or quality from serving cell 202 for a given amount of time, UE 224 can send a report message indicating this condition to its serving base station 210. In response, UE 224 may receive a handover command, and the UE may undergo a handover to cell 206.

[0055] In a network configured for UL-based mobility, a UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive the carrier frequency and time slot timing from it, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. When UE 224 moves through radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 can, with or without notification to UE 224, hand over UE 224 from the serving cell to that neighboring cell.

[0056] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, these signals do not necessarily identify a specific cell. Instead, they can identify an area of ​​multiple cells operating on the same frequency and / or with the same timing. Using areas in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network, as the number of mobility messages that need to be exchanged between the UE and the network can potentially be reduced.

[0057] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by means of a mobile network operator that has purchased a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-authorized license. While some technical rules generally still need to be followed to access unlicensed spectrum, any operator or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide License-Shared Access (LSA) to share that spectrum with other parties, for example, by utilizing conditions determined by a suitable licensee.

[0058] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as the frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the “below 6 GHz” band. Similar naming issues sometimes arise regarding FR2, although it differs from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0059] In light of the foregoing, unless otherwise specifically stated, it should be understood that, if used herein, the terms "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, if used herein, the terms "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0060] The air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between individual devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and to provide multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 can be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0061] The air interface in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex is typically simulated for wireless links using Time Division Duplex (TDD). In TDD, transmissions in different directions on a given channel are separated using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver, and appropriate interference cancellation techniques. Full-duplex is typically simulated for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions operate at different carrier frequencies. In SDD, transmissions in different directions on a given channel are separated using Space Division Multiplexing (SDM). In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication can be called subband full-duplex (SBFD), also known as flexible duplex.

[0062] In a further aspect of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink signal 227 without relaying the communication through a base station (e.g., base station 212). In a further example, UE 238 is shown communicating with UEs 240 and 242. Here, UE 238 can act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and / or a mesh network. In a mesh network example, UEs 240 and UE 242 can optionally communicate directly with each other in addition to communicating with UE 238 (e.g., acting as a scheduling entity). Thus, in a wireless communication system with scheduled access to time-frequency resources and with cellular, P2P, or mesh configurations, a scheduling entity and one or more scheduled entities can utilize the scheduled resources for communication. In some examples, sidelink signal 227 includes sidelink services (e.g., a physical sidelink shared channel) and sidelink control (e.g., a physical sidelink control channel).

[0063] In some examples, two or more UEs (e.g., UE 226 and UE 228) within the coverage area of ​​serving base station 212 can communicate with both base stations 212 using cellular signals, and with each other using direct link signals (e.g., sidelink signal 227) without relaying the communication through the base station. In examples of V2X networks within the coverage area of ​​base station 212, base station 212 and / or one or both of UE 226 and UE 228 can act as a scheduling entity to schedule sidelink communication between UE 226 and UE 228.

[0064] Various aspects of this disclosure are described with reference to OFDM waveforms. Figure 3 An example of an OFDM waveform is illustrated herein. It will be understood by those skilled in the art that various aspects of this disclosure can be applied to SC-FDMA waveforms in essentially the same manner as described herein. That is, although some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0065] Now for reference Figure 3An extended view of example DL subframe (SF) 302A is shown, illustrating the OFDM resource grid 304. However, as those skilled in the art will readily understand, the physical layer (PHY) transmission architecture for any particular application can differ from the example described herein, depending on numerous factors. Here, time is in the horizontal direction in units of OFDM symbols, and frequency is in the vertical direction in units of subcarriers. 5G NR supports scalable parameter sets, where different parameter sets can be used for different radio spectrums, different bandwidths, and so on. For example, subcarrier spacing (SCS) of 15 kHz, 30 kHz, 60 kHz, etc., can be used in different scenarios.

[0066] Resource grid 304 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, the corresponding multiple resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the parameter set used. In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. In this disclosure, it is assumed that a single RB, such as RB 308, corresponds exactly to a single communication direction (either transmission or reception for a given device).

[0067] Scheduling a UE (e.g., a scheduled entity) for downlink, uplink, or sidelink transmissions typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Each BWP may include two or more contiguous or consecutive RBs. Therefore, the UE typically utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest resource unit that can be allocated to the UE. Thus, the more RBs scheduled for the UE and the more sophisticated the modulation scheme selected for the air interface, the higher the UE's data rate. RBs can be scheduled by base stations (e.g., gNB, eNB, RSU, etc.) or can be self-scheduled by the UE implementing D2D sidelink communication.

[0068] In this illustration, RB 308 is shown occupying less than the entire bandwidth of subframe 302A, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302A can have a bandwidth corresponding to any number of one or more RB 308s. Furthermore, in this illustration, RB 308 is shown occupying less than the entire duration of subframe 302A, although this is merely one possible example.

[0069] Each 1 ms subframe 302A can consist of one or more adjacent time slots. Figure 3 In the example shown, as an illustrative example, a subframe 302B includes four time slots 310. In some examples, time slots can be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, resources scheduled for ongoing time slot transmissions for the same or different UEs may be used to transmit these micro-time slots. Any number of resource blocks can be utilized within a subframe or time slot.

[0070] An extended diagram of one of the time slots 310 illustrates a time slot 310 comprising a control region 312 and a data region 314. Typically, the control region 312 may carry a control channel (e.g., PDCCH), and the data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, the time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely an example, and different time slot structures can be used, and may include one or more of each of a control region and a data region.

[0071] although Figure 3 Although not shown, each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), or sounding reference signals (SRS). These pilot or reference signals can provide channel estimation for the corresponding channels to the receiving equipment, enabling coherent demodulation / detection of the control and / or data channels within RB 308.

[0072] In some examples, time slot 310 can be used for broadcast or unicast communication. In V2X or D2D networks, broadcast communication can refer to point-to-multipoint transmission from one device (e.g., a vehicle, base station (e.g., RSU, gNB, eNB, etc.), UE, or other similar device) to other devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0073] In one example, the control area 312 of time slot 310 may include a physical downlink control channel (PDCCH) comprising downlink control information (DCI) transmitted by a base station (e.g., gNB, eNB, RSU, etc.) to one or more UEs in a set of UEs, which may include one or more sidelink devices (e.g., V2X / D2D devices). In some examples, the DCI may include synchronization information to synchronize communication by multiple sidelink devices on the sidelink channel. Additionally, the DCI may include scheduling information indicating one or more resource blocks within control area 312 and / or data area 314 allocated to sidelink devices for sidelink communication. For example, the control area 312 of time slot may also include control information transmitted by sidelink devices via the sidelink channel, while the data area 314 of time slot 310 may include data transmitted by sidelink devices via the sidelink channel. In some examples, control information may be transmitted within the physical sidelink control channel (PSCCH), while data may be transmitted within the physical sidelink shared channel (PSSCH).

[0074] In DL transmission (e.g., via a Uu interface), a transmitting device (e.g., a scheduling entity) may allocate one or more REs 306 (e.g., within control area 312) to carry DL control information, including one or more DL control channels (such as PBCH and / or Physical Downlink Control Channel (PDCCH), etc.), to one or more scheduled entities. The transmitting device may also allocate one or more REs 306 to carry other DL signals, such as DMRS, Phase Tracking Reference Signal (PT-RS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), and Secondary Synchronization Signal (SSS).

[0075] Synchronization signals PSS and SSS (and in some examples PBCH and PBCH DMRS) can be transmitted in a synchronization signal block (SSB) comprising three consecutive OFDM symbols, the OFDM symbols being numbered via an ascending time index from 0 to 3. In the frequency domain, the SSB can extend to more than 240 contiguous subcarriers, where the subcarriers are numbered via an ascending frequency index from 0 to 239. Of course, this disclosure is not limited to this particular SSB configuration. Other non-limiting examples may utilize more or fewer synchronization signals; one or more supplementary channels may be included in addition to PBCH; PBCH may be omitted; and / or different numbers of symbols and / or non-contiguous symbols may be used for the SSB within the scope of this disclosure.

[0076] The SSB can be used to transmit System Information (SI) and / or provide a reference to SI transmitted via another channel. Examples of System Information may include, but are not limited to, subcarrier spacing, system frame number, Cell Global Identifier (CGI), cell stripe indication, list of common control resource sets (core sets), list of common search spaces, search space for System Information Block 1 (SIB1), paging search space, random access search space, and uplink configuration information. Two specific examples of core sets include PDCCHCORESET 0 and CORESET 1.

[0077] System Information Blocks (SIs) can be subdivided into three sets, known as Minimal SIs (MSIs), Residual MSIs (RMSIs), and Other SIs (OSIs). A Power Buffer Chamber (PBCH) can carry some of the MSIs and RMSIs. For example, a PBCH can carry a Master Information Block (MIB) containing various types of system information, as well as parameters for decoding System Information Blocks (SIBs). In some examples, the MIB can be configured with CORESET0.

[0078] The RMSI can be carried, for example, by SystemInformationType1 (SIB1). The base station can transmit SIB1 on the PDSCH (and therefore transmit the RMSI). CORESET0 contains scheduling information for the PDSCH carrying SIB1.

[0079] The PDCCH can carry downlink control information (DCI), including but not limited to: power control commands, scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions. The PHY carries HARQ feedback transmissions such as acknowledgments (ACK) or denials (NACK). HARQ is a technique well-known to those skilled in the art, where the integrity of packet transmissions can be checked at the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as checksums or cyclic redundancy checks (CRC). If the integrity of the transmission is acknowledged, an ACK can be sent; otherwise, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which enables catch-up combining, incremental redundancy, etc.

[0080] In UL transmissions (e.g., via a Uu interface), a transmitting device (e.g., a scheduled entity) may utilize one or more RE 306s to carry UL control information, including one or more UL control messages such as the Physical Uplink Control Channel (PUCCH), to a scheduling entity. UL control information may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. For example, UL control information may include DMRS or SRS. In some examples, the control information may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the control channel, the scheduling entity may send downlink control information that can schedule resources for uplink packet transmissions. UL control information may also include HARQ feedback, Channel State Feedback (CSF), or any other suitable UL control information.

[0081] In addition to control information, one or more REs 306 can be allocated for user data or service data (e.g., within data area 314). Such services can be carried on one or more service channels (e.g., PDSCH for DL ​​transmissions; or Physical Uplink Shared Channel (PUSCH) for UL transmissions). In some examples, one or more REs 306 within data area 314 can be configured to carry an SIB (e.g., SIB1) that carries system information enabling access to a given cell.

[0082] The physical channels described above are typically multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channel carries blocks of information called transport blocks (TBs). The transport block size (TBS), which corresponds to multiple bits of information, can be a controlled parameter based on the modulation and decoding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0083] The above is for reference only. Figures 1-3The channels or carriers described are not necessarily all channels or carriers that can be used between the scheduling entity and the scheduled entity, and those skilled in the art will recognize that other channels or carriers (such as other service, control and feedback channels) may be used in addition to those shown.

[0084] Figure 4A Example 400 shows various downlink channels within a subframe of a frame, including channels for initial access and synchronization. For example... Figure 4A As shown, the Physical Downlink Control Channel (PDCCH) 402 is transmitted in at least two symbols (e.g., symbol 0 and symbol 1) and carries a DCI within one or more Control Channel Elements (CCEs), where each CCE includes nine RE groups (REGs), and in OFDM symbols, each REG includes four consecutive REs. Furthermore, Figure 4A An exemplary synchronization signal block (SSB) 404 that can be periodically transmitted by a base station or gNB is shown. SSB 404 carries synchronization signals PSS 406 and SSS 408, as well as a broadcast channel (PBCH) 410. In this example, SSB 404 contains one PSS symbol (as shown in symbol 2), one SSS symbol (as shown in symbol 4), and two PBCH symbols (as shown in symbols 3 and 5). The combination of PSS and SSS can be used to identify the physical cell identifier. The UE uses the PSS to determine subframe / symbol timing and the physical layer identifier. The UE uses the SSS to determine the physical layer cell identifier group number and the radio frame timing. Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Furthermore, based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) is logically grouped with the PSS and SSS to form the synchronization signal, i.e., SSB 404. The MIB provides multiple RBs and system frame numbers (SFNs) in the system bandwidth.

[0085] Figure 4B This is a diagram illustrating various broadcast messages 450 associated with initial cell access, based on some examples. Broadcast messages 450 can be transmitted by RAN nodes (e.g., base stations, such as eNBs or gNBs) on resources (e.g., time-frequency resources) allocated for the transmission of broadcast messages 450 in the cell. Broadcast messages 450 include... Figure 4ASSB 404 is shown. Note that the PBCH in SSB 404 includes a MIB carrying various system information (SIs), such as cell barred indications, subcarrier spacing, system frame numbers, and scheduling information for CORESET0 452. For example, the PBCH in SSB 404 may include scheduling information indicating time-frequency resources allocated to CORESET0 452. In some examples, CORESET0 452 may be transmitted within the first four symbols of the time slot (e.g., within the control area). Furthermore, CORESET0 452 carries a PDCCH with a DCI containing scheduling information for scheduling SIB1 454. SIB1 454 is carried within the Physical Downlink Shared Channel (PDSCH) within the data area of ​​the time slot. Additionally, SIB1 454 may be referred to as RMSI and includes, for example, a set of radio resource parameters providing network identification and configuration. For example, the set of radio resource parameters may include the bandwidth (e.g., the number of BWPs) on which the UE can communicate with the base station.

[0086] Figure 4B It is also shown that the RMSI of SIB1 message 454 may also include bit field 468. The time / frequency position of this bit field 468 is merely exemplary to show that bit field 462 utilizes some of the time and frequency resources of SIB1 message 454.

[0087] The MIB in the PBCH can include system information (SI) and parameters for decoding the SIB (e.g., SIB1). Examples of SIs transmitted in the MIB may include, but are not limited to, subcarrier spacing, system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and the search space of SIB1. Examples of SIs transmitted in SIB1 may include, but are not limited to, random access search space, downlink configuration information, and uplink configuration information. Together, the MIB and SIB1 provide the minimum SI for initial access.

[0088] The initial access procedure for a UE using the above information is briefly discussed below. As discussed above, the BS can transmit synchronization signals (e.g., including PSS and SSS) in the network to enable the UE to synchronize with the BS, and SIs (e.g., including MIB, RMSI, and OSI) to facilitate initial network access. The BS can transmit PSS, SSS, and / or MIB via SSB through PBCH, and can broadcast RMSI and / or OSI via PDSCH.

[0089] A UE attempting to access the RAN can perform an initial cell search by detecting the PSS (Physical Layer Identifier) ​​from the BS (Base Station) in the RAM (e.g., the PSS of the BS's cell). The PSS enables the UE to synchronize with the BS's periodic timing and can indicate the physical layer identifier value assigned to the cell. The UE can also receive an SSS from the BS, which enables the UE to synchronize with the cell at the radio frame level. The SSS can also provide a cell identifier value, which the UE can combine with the physical layer identifier value to identify the cell.

[0090] After receiving the PSS and SSS, the UE can receive the SI from the BS. System information can take the form of MIB and SIB discussed above. System information includes basic or critical information for UE network access, such as downlink (DL) channel configuration information, uplink (UL) channel configuration messages, access category information, and cell stripe information, as well as other less critical information. The MIB may include the SI for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE can receive the RMSI and / or OSI.

[0091] SI includes enabling the UE to determine how to perform operations on the RAN (e.g., Figure 2 The SIB2 provides initial access information to the RAN (RAN 200). In some examples, the SIB2 includes random access configuration information (e.g., RACH configuration) that indicates the resources the UE will use to communicate with the RAN during initial access. The random access configuration information may indicate, for example, resources allocated by the RAN for the PRACH procedure. For instance, the RACH configuration may indicate resources allocated by the network for the UE to send the PRACH preamble and receive the random access response. In some examples, the RACH configuration identifies the monitoring timing (MO), which specifies the set of symbols (e.g., within the PRACH slot) scheduled by the base station for the PRACH procedure. The RACH configuration may also indicate the size of the random access response window during which the UE will monitor responses to the PRACH preamble. In some examples, the RACH configuration may also specify that the random access response window begins a certain number of subframes after the end of the PRACH preamble. After obtaining the MIB, RMSI, and / or OSI, the UE can then perform the random access procedure for initial access to the RAN.

[0092] Figure 5 Signaling diagram 500 illustrates an example of signaling for a contention-based RACH procedure in a wireless communication system including base station (BS) 502 and UE 504. In some examples, base station 502 may correspond to... Figure 1 , Figure 2 , Figure 6 , Figure 9 and Figure 12Any of the base stations or scheduling entities shown in the diagram. In some examples, UE 504 may correspond to... Figure 1 , Figure 2 , Figure 6 , Figure 9 and Figure 10 Any of the UEs shown in the diagram or any of the scheduled entities.

[0093] exist Figure 5 In step 506, UE 504 sends Message 1 (Msg1) of the RACH procedure to BS 502. In some examples, Msg1 is the PRACH preamble. RACH Msg1 can be referred to as PRACH. As described above, UE 504 can send the PRACH preamble on the resources specified by the RACH configuration included in SIB2.

[0094] In step 508, BS 502 responds to the PRACH preamble with message 2 (Msg2) of the RACH procedure. Msg2 can be informally referred to as the Random Access Response (RAR). In some examples, BS 502 sends a DCI on the PDCCH, where the DCI schedules the PDSCH (e.g., the DCI specifies the resources used for PDSCH transmission). BS 502 then sends the PDSCH, which includes RAR data, such as, for example, a UL grant for instructing the UE to send message 3 (Msg3) of the RACH procedure.

[0095] In some examples, the UE monitors Msg2 on the resource specified by the RACH configuration during the RAR window specified by the RACH configuration. For example, the UE can decode the DCI carried on the PDCCH and then decode the RAR carried on the PDSCH.

[0096] In step 510, after receiving all RAR information, UE 504 sends Msg3 for the RACH procedure. In some examples, Msg3 is an RRC connection request message.

[0097] In step 512, BS 502 responds with message 4 (Msg4) of the RACH procedure. In some examples, Msg4 is an RRC connection setup message.

[0098] In step 514, UE 504 responds with message 5 (Msg5) of the RACH procedure. In some examples, Msg5 is an RRC connection complete message.

[0099] As indicated in step 516, BS 502 and UE 504 finally establish a connection and enter the active operational phase in which data can be exchanged. For example, the BS may schedule the UE to perform UL communication and / or DL ​​communication, as discussed herein.

[0100] Wireless communication networks can support different types of services. For example, a network can carry services with different priorities, different latency requirements (e.g., IoT services and Voice over IP (VoIP) services), different bandwidth requirements, different throughput requirements, and so on. In some examples, these different types of services can be referred to as network slices (e.g., one "slice" of the network supports one service, another "slice" supports another service, etc.). In some respects, a slice can refer to a set of network entities that can provide a specific service to a UE. In other respects, a slice can refer to a logical network that supports certain capabilities and has certain characteristics.

[0101] To support different services (slices), the network can provide appropriate functionality to handle the requirements of different services. However, a given network may not support all types of services. Therefore, the network can indicate to the UE which services it supports.

[0102] In some examples, network slices are negotiated using a NAS registration process. Here, different types of slices can be qualified using corresponding Network Slice Selection Auxiliary Information (NSSAI). For example, a given slice can be identified by a single NSSAI (S-NSSAI). For convenience, the set of S-NSSAIs can be simply referred to as NSSAI. In some examples, S-NSSAIs may include Slice / Service Type (SST), which can specify the characteristics and services of the slice. In some examples, S-NSSAIs may include Slice Differentiators (SDs), which can, for example, distinguish slices with the same SST. Examples of SSTs include Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communication (URLLC), and Massive Internet of Things (MIoT). Other types of SSTs can also be qualified.

[0103] Figure 6 Signaling diagram 600 illustrates an example of NAS-related signaling in a wireless communication system including UE 602, base station (BS) 604 such as gNB, and Access and Mobility Management Function (AMF) 606. In some examples, UE 602 may correspond to Figure 1 , Figure 2 , Figure 5 , Figure 9 and Figure 10 This refers to any of the UEs shown in the table or any of the scheduled entities. In some examples, BS 604 may correspond to... Figure 1 ,Figure 2 , Figure 5 , Figure 9 and Figure 12 Any of the base stations or scheduling entities shown in the diagram.

[0104] exist Figure 6 In step 608, BS 604 sends a 5G Core Network Next Generation (NG) Establishment Request message to AMF 606. This message can specify a list of individual NSSAIs for each Tracking Area Identifier (TAI). In some examples, slicing can be uniform within a given tracking area.

[0105] In step 610, AMF 606 responds to the NG setup request message by sending an NG setup response message to BS 604.

[0106] In step 612, as part of the RACH procedure, UE 602 may send RRC Msg5 to BS 604. In some examples, Msg5 may include a NAS registration request. This message may include an indication of NSSAI requested by the Access Stratum (AS) layer of UE 602.

[0107] In some examples, UE 602 may send a NAS registration request message. This message may include instructions for the requested NSSAI.

[0108] In step 614, BS 604 sends an initial UE message to AMF 606. This message may include an indication of NSSAI requested by UE 602.

[0109] In step 616, AMF 606 sends an Initial UE Context Setting Request message to BS 604. This message indicates whether the network allows the NSSAI or not.

[0110] In some examples, the allowed NSSAIs may include the requested NSSAI (or the default S-NSSAI if no valid S-NSSAI is requested), the subscribed NSSAIs, and the minimum common set of NSSAIs currently supported by TAI.

[0111] In step 618, UE 602 and BS 604 exchange security mode command information.

[0112] In step 620, BS 604 sends an RRC configuration message to UE 602 accepting NAS registration.

[0113] As shown in box 622, the UE context at UE 602 indicates NSSAI configured by the network, NSSAI requested by the UE, NSSAI allowed by the network, and NSSAI rejected by the network.

[0114] As shown in box 624, the UE context at BS 604 indicates the NSSAI of the network-permitted NSSAI and all active Protocol Data Unit (PDU) sessions.

[0115] As shown in box 626, the UE context at AMF 606 indicates NSSAI subscribed to at the network, NSSAI requested by the UE, NSSAI allowed by the network, and NSSAI rejected by the network.

[0116] In some examples, the AS request NSSAI in Msg5 can be used for AMF selection. Due to security concerns (e.g., if Msg5 is not securely protected), this request may be a subset of the NSSAI requested by the NAS.

[0117] In some examples, PDU session establishment is associated with a slice in the allowed NSSAI. For example, a PDU session can be established for each S-NSSAI.

[0118] In 3GPP Rel.15, there is no RACH resource allocation; that is, only cell-specific RACH resources are allowed. RACH parameter prioritization (e.g., prioritization of 'preamble ramp step size' and 'backoff scaling factor') was introduced in Rel-15 and can be used for prioritized RACH access in handover (HO) and beam fault reporting (BFR). RACH parameter prioritization can be used for 4-step RACH or 2-step RACH. RACH parameter prioritization can be used for RACH triggered by Mission-Critical Service (MCS) and RACH triggered by Multimedia Priority Service (MPS). However, in implementations such as 3GPP Rel.15, all slices share the same Random Access (RA) resources and cannot be distinguished by the network.

[0119] Therefore, traditional RACH configuration techniques do not differentiate between services (slices). However, using different RACH configurations for different slices can be advantageous. For example, URLLC can use more frequent RACH timings, thereby improving URLLC RACH performance.

[0120] This disclosure relates to slice-aware RACH in some aspects. Below are two examples of slice-aware RACH. In the first example, RACH resource partitioning / isolation can be used to provide access resource isolation (e.g., for industrial applications). In some aspects, this example can provide guaranteed random access (RA) resources for their slices. In the second example, parameter prioritization can be used to prioritize slices during the RA process. However, when the number of slices is large, these examples may result in resource fragmentation for RACH resource isolation and excessive prioritization parameters for the UE.

[0121] This disclosure relates in some aspects to slice-based RACH configuration. In some examples, slice-aware RACH is provided with group-based RACH resource partitioning and parameter prioritization.

[0122] This disclosure relates in several aspects to the use of RACH resource partitioning / isolation and parameter prioritization for different objectives. For example, slices with similar use cases can be grouped using the same set of prioritization parameters, and a dedicated (e.g., isolated) RACH resource can be reserved for the most sensitive slice within the slice group (e.g., the slice with the most stringent(s) business requirements). Examples of use cases may include industrial services, mission-critical services, emergency alert services, low-latency services, high-throughput services, sensor services, best-effort services, etc. Other use cases may be specified in other examples.

[0123] This disclosure relates in some aspects to group-based RACH resource allocation and parameter prioritization. In some examples, RRC, SIB, or NAS signaling can be used to configure one or more slice groups, where each slice group includes one or more slices. Additionally, each slice group can be configured with the same dedicated (isolated) RACH resources or the same set of RACH parameters via RRC or SIB signaling, and other methods (prioritization parameters) can be applied to slices within a slice group. Depending on the different triggers of the RACH, the UE's AS can select the appropriate RACH resources / parameters for RACH access.

[0124] This disclosure relates in several aspects to group slice-aware RACH. A UE can be configured with one or more slice groups via RRC, SIB, or NAS signaling, where each slice group comprises one or more slices. Slices within a group may have similar use cases (e.g., industrial use cases, medical use cases, etc.), but different slices may have different priorities. For example, URLLC slices and smart metering slices can be configured in the same group, but the URLLC slice can be given higher priority. Each slice group can be configured with the same isolated RACH resources or the same set of RACH parameters via RRC or SIB signaling, and other methods (different RACH resources) can be applied to one or more slices within a slice group.

[0125] Depending on the triggering of the RACH, the UE's AS can select the appropriate RACH resources / parameters for RACH access. In some examples, if the RACH is triggered by an arriving service / traffic, the UE's NAS provides service / slice information to the AS. The AS uses the service / slice information to select the appropriate RACH resources / parameters for access. If the RACH is not triggered by a traffic arrival (e.g., initial access RACH), the NAS provides the AS with the requested NSSAI(s). In some examples, the AS uses the service / slice with the highest priority among its requested NSSAI(s) to select the appropriate RACH (e.g., to obtain better RACH performance when there are relatively few UEs under the gNB). In some examples, the AS uses the service / slice with the lowest priority among its requested NSSAI(s) to select the appropriate RACH (e.g., to provide fairer RACH resource sharing when there are relatively many UEs under the gNB).

[0126] This disclosure relates in some aspects to RACH configuration for specifying group-specific parameters and slice-specific resources. Each slice group is configured with a different set of RACH parameters via RRC or SIB signaling. Additionally, within each slice group, one or more slices are configured with isolated RACH resources, and other slices use cell-specific RACH resources.

[0127] This disclosure relates in some aspects to RACH configuration for specifying group-specific resources and slice-specific parameters. Each slice group is configured with an isolated set of RACH resources via RRC or SIB signaling. Additionally, within each slice group, one or more slices are configured with a prioritized set of RACH parameters, and other slices use cell-specific RACH parameters.

[0128] This disclosure relates in some aspects to specific slice groups for Mobile Oriented (MO) / Mobile Termination (MT). In the absence of explicit slice-based RACH configuration, two slice groups can be implicitly defined at the UE: one group includes all slices triggered by MO traffic (UL direction), and the other group includes all slices triggered by MT traffic (DL direction). For each slice group, RRC / SIB signaling can be configured with isolated sets of RACH resources or different sets of RACH parameters.

[0129] Figure 7 This is a flowchart illustrating an example wireless communication method 700 for a base station according to some aspects of this disclosure. As described below, within the scope of this disclosure, some or all of the shown features may be omitted in certain implementations, and some shown features may not be necessary for implementing all embodiments. In some examples, method 700 may be implemented by... Figure 12The method is executed by BS 1200 shown below. In some examples, method 700 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0130] In box 702, the BS is specified for the first RACH configuration of the first slice group. In some examples, the first RACH configuration or other RACH configurations can be specified for other slice groups.

[0131] In one example, the BS can specify that the first slice group will use specific RACH resources (e.g., cell-specific RACH resources or dedicated RACH resources). RACH resources can include, for example, one or more RACH preambles and / or one or more RACH times (ROs). In some examples, these RACH resources can be prioritized. For example, more RACH resources can be allocated to higher-priority slice groups, potentially providing better RACH performance for higher-priority slice groups (e.g., faster connections to the network).

[0132] Additionally, the BS can assign a first RACH parameter (e.g., a cell-specific RACH parameter) to the first slice of the first slice group and a second RACH parameter (e.g., a dedicated RACH parameter) to the second slice of the first slice group, and so on. For example, RACH parameters may include a preamble ramp step size and / or a backoff scaling factor. In some examples, these RACH parameters can be prioritized. For instance, a preamble ramp step size can be assigned to higher-priority slices, causing the PRACH retransmission power to ramp up more quickly, potentially providing better RACH performance for higher-priority slices (e.g., faster connections to the network). As another example, a smaller (e.g., close to zero) backoff scaling factor can be assigned to higher-priority slices to reduce PRACH retransmission backoff time, potentially providing better RACH performance for higher-priority slices (e.g., faster connections to the network).

[0133] In another example, the BS can specify that the first slice group will use specific RACH parameters (e.g., cell-specific RACH parameters or dedicated RACH parameters). In some examples, these RACH parameters can be prioritized. For example, a preamble ramp step size can be assigned to higher-priority slice groups, causing the PRACH retransmission power to ramp up more quickly, potentially providing better RACH performance (e.g., faster connections to the network) for higher-priority slice groups. As another example, a smaller (e.g., close to zero) backoff scaling factor can be assigned to higher-priority slice groups to reduce PRACH retransmission backoff time, potentially providing better RACH performance (e.g., faster connections to the network) for higher-priority slice groups.

[0134] Additionally, the BS can assign a first RACH resource (e.g., a cell-specific RACH resource) to the first slice of the first slice group, and a second RACH resource (e.g., a dedicated RACH resource) to the second slice of the first slice group, and so on. In some examples, these RACH resources can be prioritized. For example, more RACH resources can be allocated to higher-priority slices, potentially providing better RACH performance for higher-priority slices (e.g., faster connections to the network).

[0135] In box 704, the BS specifies the second RACH configuration for the second slice group. In some examples, the second RACH configuration or other RACH configurations can be specified for other slice groups.

[0136] In one example, the BS can specify that the second slice group will use a specific RACH resource (e.g., a cell-specific RACH resource or a dedicated RACH resource). Additionally, the BS can specify a first RACH parameter (e.g., a cell-specific RACH parameter) for the first slice of the second slice group and a second RACH parameter (e.g., a dedicated RACH parameter) for the second slice of the second slice group, and so on.

[0137] In another example, the BS can specify that the second slice group will use specific RACH parameters (e.g., cell-specific RACH parameters or dedicated RACH parameters). Additionally, the BS can specify a first RACH resource (e.g., cell-specific RACH resource) for the first slice of the second slice group and a second RACH resource (e.g., dedicated RACH resource) for the second slice of the second slice group, and so on.

[0138] In box 706, the BS sends an indication of the first slice group and the second RACH configuration for the first slice group and the second slice group. For example, the BS may send an SIB, RCC, or NAS message, which specifies a default RACH configuration (e.g., a cell-specific RACH configuration) and / or configure a dedicated RACH configuration for the UE (e.g., a RACH dedicated to one or more slice groups).

[0139] In box 708, the BS receives a PRACH message from the UE according to a first RACH configuration or a second RACH configuration. For example, the BS may receive a PRACH message on a RACH resource specified for a specific slice group. As another example, the BS may receive a PRACH message sent by the UE using at least one RACH parameter specified for a specific slice group. As yet another example, the BS may receive a PRACH message sent by the UE on a RACH resource specified for a specific slice group, using at least one RACH parameter specified for that specific slice group.

[0140] Figure 8 This is a flowchart illustrating an example wireless communication method 800 for a UE according to some aspects of this disclosure. As described below, within the scope of this disclosure, some or all of the shown features may be omitted in certain implementations, and some shown features may not be necessary for implementing all embodiments. In some examples, process 800 may be performed by... Figure 10 The method 800 is executed by the UE 1000 shown below. In some examples, the method 800 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0141] In box 802, the UE determines the slice-specific RACH configuration. In some examples, the UE receives the RACH configuration from the gNB (e.g., in...). Figure 7 (The RACH configuration sent in box 706). In some examples (e.g., when slices are grouped according to MO and MT services), the UE determines the service-based RACH configuration.

[0142] In box 804, the UE determines that RACH is triggered for a specific slice (e.g., for a specific network service). For example, RACH may be triggered as a result of an application that generates data at the UE that will be sent to the network. This application may be associated with a specific slice (service) or multiple slices.

[0143] In box 806, the UE determines the RACH configuration used for the slice. For example, the UE can identify which RACH configuration in the RACH configuration determined in box 802 is specified for the slice group to which the slice belongs.

[0144] In box 808, the UE uses the RACH configuration determined in box 806 to transmit PRACH. For example, the UE may transmit PRACH messages on RACH resources specified for a specific slice group (e.g., a specific PRACH preamble and / or (one or more) specific ROs). As another example, the UE may use at least one RACH parameter specified for a specific slice group (e.g., a specific preamble ramp step size and / or a specific backoff scaling factor for PRACH retransmission) to transmit PRACH messages. As yet another example, the UE may transmit PRACH messages on RACH resources specified for a specific slice group and using at least one RACH parameter specified for that specific slice group.

[0145] Figure 9 Signaling diagram 900 illustrates an example of RACH-related signaling in a wireless communication system including base station (BS) 902 and UE 904. In some examples, BS 902 may correspond to Figure 1 , Figure 2 , Figure 5 , Figure 6and Figure 12 Any of the base stations or scheduling entities shown in the diagram. In some examples, UE 904 may correspond to... Figure 1 , Figure 2 , Figure 5 , Figure 6 and Figure 10 Any of the UEs shown in the diagram or any of the scheduled entities.

[0146] exist Figure 9 In step 906, BS 902 can specify the initial slice-specific RACH configuration. For example, BS 902 can define multiple slice groups, where different RACH configurations are assigned to different slice groups. In some examples, BS 902 can specify that some slice groups will use one or more cell-specific RACH resources, and other slice groups will use one or more dedicated RACH resources. In some examples, BS 902 can specify that some slice groups will use one or more cell-specific RACH parameters, and other slice groups will use one or more dedicated RACH parameters.

[0147] In step 908, BS 902 broadcasts the SSB, RMSI, and OSI. In some examples, the SIB in the OSI may specify an indication of the RACH configuration specified in step 906.

[0148] In step 910, UE 904 determines its initial slice-specific RACH configuration. In some examples, the UE receives an indication of the RACH configuration from BS 902 in step 908. In some examples (e.g., when the slice is grouped according to MO and MT services), the UE determines one or more RACH configurations to be used for MO services and one or more RACCH configurations to be used for MT services.

[0149] In step 912, RACH is triggered at UE 904. For example, RACH can be triggered as a result of services generated at UE 904 for a specific service (slice). As discussed above, the UE determines the RACH configuration for the service (slice).

[0150] In step 914, BS 902 and UE 904 perform the RACH procedure based on the corresponding RACH configuration for the service (slice). For example, UE 904 may send PRACH on RACH resources and / or using RACH parameters specified for the service (slice).

[0151] Subsequently, in step 916, BS 902 can specify UE-specific slice-specific RACH configurations. For example, BS 902 can define multiple slice groups for the UE, where different RACH configurations are assigned to different slice groups. In some examples, BS 902 can specify that some slice groups for the UE will use one or more cell-specific RACH resources, and other slice groups for the UE will use one or more dedicated RACH resources. In some examples, BS 902 can specify that some slice groups for the UE will use one or more cell-specific RACH parameters, and other slice groups for the UE will use one or more dedicated RACH parameters.

[0152] In step 918, BS 902 sends one or more RRC messages and / or NAS messages to UE 904 indicating the RACH configuration specified in step 916.

[0153] In step 920, UE 904 determines the slice-specific RACH configuration indicated in one or more RRC messages and / or one or more NAS messages in step 918.

[0154] In step 922, RACH is triggered at UE 904. Here, the UE can determine the RACH configuration of the corresponding service (slice) based on the slice-specific RACH configuration determined in step 920.

[0155] In step 924, BS 902 and UE 904 perform the RACH procedure based on the corresponding RACH configuration for the service (slice). For example, UE 904 may send PRACH on a dedicated RACH resource and / or using dedicated RACH parameters specified for the service (slice).

[0156] Figure 10 This is a block diagram illustrating an example of a hardware implementation of a UE 1000 employing a processing system 1014. For example, the UE 1000 may be a device configured to communicate wirelessly with a base station, as in... Figures 1-9 As discussed in any one or more of the above. In some implementations, UE 1000 may correspond to Figure 1 , Figure 2 , Figure 5 , Figure 6 and Figure 9 Any of the UEs shown in the diagram or any of the scheduled entities.

[0157] According to various aspects of this disclosure, any element, any part of an element, or any combination of elements may be implemented using processing system 1014. Processing system 1014 may include one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, UE 1000 may be configured to perform any one or more of the functions described herein. That is, processor 1004, as utilized in UE 1000, may be used to implement any one or more of the processes and procedures described herein.

[0158] In some instances, processor 1004 may be implemented via a baseband or modem chip, and in other implementations, processor 1004 may include multiple devices that are different from and distinct from the baseband or modem chip (e.g., in such scenarios, processor 804 may operate consistently to implement the embodiments discussed herein). Furthermore, as mentioned above, various hardware arrangements and components other than the baseband modem processor (including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.) may be used in each implementation.

[0159] In this example, processing system 1014 can be implemented with a bus architecture generally represented by bus 1002. Depending on the specific application and overall design constraints of processing system 1014, bus 1002 may include any number of interconnect buses and bridges. Bus 1002 communicatively couples together various circuits including one or more processors (generally represented by processor 1004), memory 1005, and computer-readable media (generally represented by computer-readable media 1006). Bus 1002 may also link various other circuits, such as timing sources, peripheral devices, pressure regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1008 provides an interface between bus 1002 and transceiver 1010, and between bus 1002 and interface 1030. Transceiver 1010 provides a communication interface or component for communicating with various other devices over a wireless transmission medium. In some examples, the UE may include two or more transceivers 1010, each configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). Interface 1030 provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices housed within the same device as the UE or other external devices) via an internal bus or an external transmission medium such as an Ethernet cable. Depending on the nature of the device, interface 1030 may include a user interface (e.g., a keyboard, display, speaker, microphone, joystick). Of course, such a user interface is optional and may be omitted in some examples (e.g., IoT devices).

[0160] Processor 1004 is responsible for managing bus 1002 and general processing, including the execution of software stored on computer-readable medium 1006. When executed by processor 1004, the software causes processing system 1014 to perform various functions described below for any particular device. Computer-readable medium 1006 and memory 1005 may also be used to store data manipulated by processor 1004 during software execution. For example, memory 1005 may store RACH information 1015 (e.g., slice-related parameters) used by processor 1004 to cooperate with transceiver 1010 to send and / or receive RACH messages.

[0161] One or more processors 1004 in the processing system can execute 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, functions, etc., whether described using terms such as software, firmware, middleware, microcode, hardware description languages, or other terms. Software may reside on a computer-readable medium 1006.

[0162] Computer-readable medium 1006 may be a non-transitory computer-readable medium. As examples, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical discs (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. Computer-readable medium 1006 may reside in processing system 1014, be external to processing system 1014, or be distributed across multiple entities including processing system 1014. Computer-readable medium 1006 may be implemented in a computer program product. As an example, a computer program product may include a computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented depending on the specific application and the overall design constraints imposed on the system as a whole.

[0163] UE 1000 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 1-9 The description and the following combination Figure 11 As described, in some aspects of this disclosure, such as the processor 1004 utilized in UE 1000, circuitry may be configured for various functions.

[0164] Processor 1004 may include communication and processing circuitry 1041. Communication and processing circuitry 1041 may be configured to communicate with a base station, such as a gNB. Communication and processing circuitry 1041 may include one or more hardware components that provide a physical structure for performing various processes related to the wireless communication described herein (e.g., signal reception and / or signal transmission). Communication and processing circuitry 1041 may also include one or more hardware components that provide a physical structure for performing various processes related to signal processing as described herein (e.g., processing received signals and / or processing signals for transmission). In some examples, communication and processing circuitry 1041 may include two or more transmit / receive chains, each configured to process signals of a different RAT (or RAN) type. Communication and processing circuitry 1041 may also be configured to execute communication and processing software 1051 included on computer-readable medium 1006 to implement one or more of the functions described herein.

[0165] In some examples, the communication and processing circuitry 1041 may be configured to receive and process downlink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 1010 and antenna array 1020. For example, the communication and processing circuitry 1041 may be configured to receive, during downlink beam scanning, a corresponding reference signal (e.g., SSB or CSI-RS) on each of a plurality of downlink beams from a base station via at least one first antenna panel of antenna array 1020. The communication and processing circuitry 1041 may also be configured to transmit beam measurement reports to the base station.

[0166] In some examples, the communication and processing circuitry 1041 may also be configured to generate uplink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz, and to transmit them via transceiver 1010 and antenna array 1020. For example, the communication and processing circuitry 1041 may be configured to transmit a corresponding reference signal (e.g., SRS or DMRS) to the base station via at least one second antenna panel of antenna array 1020 in each of a plurality of uplink beams during uplink beam scanning.

[0167] The communication and processing circuitry 1041 can also be configured to generate a request and send the request to the base station. For example, the request can be included in a MAC-CE carried in the PUSCH, a UCI in the PUCCH, a random access message, or an RRC message. The communication and processing circuitry 1041 can also be configured to generate a scheduling request and (e.g., via a UCI in the PUCCH) send it to the base station to receive uplink grants for a PUSCH carrying a MAC-CE including a request for uplink beam refinement.

[0168] The communication and processing circuitry 1041 can also be configured to generate an uplink signal and transmit it on one or more uplink transmit beams applied to the uplink signal. The uplink signal may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH.

[0169] The communication and processing circuitry 1041 can also be configured to control the antenna array 1020 and transceiver 1010 to search for and identify multiple downlink transmit beams during downlink beam scanning. The communication and processing circuitry 1041 can also be configured to obtain multiple beam measurements of each of the multiple downlink receive beams via the antenna array 1020 for each of the identified downlink transmit beams. The communication and processing circuitry 1041 can also be configured to generate a beam measurement report for transmission to a base station.

[0170] The communication and processing circuitry 1041 can also be configured to identify one or more selected uplink beams based on beam measurements obtained from a downlink beam reference signal. In some examples, the communication and processing circuitry 1041 can be configured to compare the respective Reference Signal Received Power (RSRP) (or other beam measurements) measured for each of the serving downlink transmit beams in each of the downlink receive beams to identify the serving downlink receive beam, and to further utilize the serving downlink receive beam as the selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement) for one of the downlink transmit beams.

[0171] The communication and processing circuitry 1041 can be configured to generate one or more uplink transmit beams for transmission in an uplink beam scan. Each uplink transmit beam can carry an uplink reference signal (e.g., SRS) for measurement by the base station. The communication and processing circuitry 1041 can also be configured to identify one or more selected uplink transmit beams(s) chosen by the base station based on uplink beam measurements. For example, the communication and processing circuitry 1041 can be configured to receive indications of one or more selected uplink transmit beams(s) from the base station.

[0172] In some implementations where communication involves receiving information, communication and processing circuitry 1041 may obtain information from components of UE 1000 (e.g., transceiver 1010 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 1041 may output information to another component of processor 1004, to memory 1005, or to bus interface 1008. In some examples, communication and processing circuitry 1041 may receive one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1041 may receive information via one or more channels. In some examples, communication and processing circuitry 1041 may include the functionality of components for receiving. In some examples, communication and processing circuitry 1041 may include the functionality of components for decoding.

[0173] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1041 may acquire information (e.g., from another component of processor 1004, memory 1005, or bus interface 1008), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1041 may output information to transceiver 1010 (e.g., transceiver 814 transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1041 may transmit one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1041 may transmit information via one or more channels. In some examples, communication and processing circuitry 1041 may include the functionality of components for transmission (e.g., components for transmission). In some examples, communication and processing circuitry 1041 may include the functionality of components for encoding.

[0174] Processor 1004 may include RACH configuration circuitry 1042, which is configured to perform RACH configuration-related operations as discussed herein (e.g., in conjunction with...). Figures 7-9 (One or more of the described operations). RACH configuration circuit 1042 may include functions for identifying components of the service (e.g., as in...). Figure 8 Box 804 and / or Figure 9 Step 912 and / or Figure 11 (described at box 1102). The RACH configuration circuit 1042 may include functionality for selecting the RACH configuration (e.g., as described in...). Figure 8 Box 806 and / or Figure 9 Steps 912 and 922 and / or Figure 11 (As described in box 1104). The RACH configuration circuit 1042 can also be configured to execute the RACH configuration software 1052 included on the computer-readable medium 1006 to perform one or more of the functions described herein.

[0175] Processor 1004 may include RACH processing circuitry 1043, which is configured to perform RACH processing-related operations as discussed herein (e.g., in conjunction with...). Figures 7-9 (One or more of the described operations). The RACH processing circuit 1043 may include the functionality of components for performing RACH operations (e.g., as in...). Figure 8 Box 808 and / or Figure 9 Steps 914 and 924 and / or Figure 11(As described in block 1106). The RACH processing circuitry 1043 may also be configured to execute the RACH processing software 1053 included on the computer-readable medium 1006 to perform one or more of the functions described herein.

[0176] Figure 11 This is a flowchart illustrating an example wireless communication method 1100 according to some aspects of this disclosure. As described herein, within the scope of this disclosure, some or all of the shown features may be omitted in certain implementations, and some shown features may not be necessary for implementing all embodiments. In some examples, method 1100 may be... Figure 10 The method is executed by the UE 1000 shown below. In some examples, method 1100 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0177] In box 1102, the UE can identify services (e.g., network slicing). For example, the above combined Figure 10 The RACH configuration circuit 1042 shown and described can determine that an application running on the UE has generated data associated with a specific service. Furthermore, the RACH configuration circuit 1042 can identify a specific network slice associated with that service.

[0178] In box 1104, the UE can select a first RACH configuration for a service from a set of multiple service random access channel (RACH) configurations. For example, RACH configuration circuitry 1042 can access mappings of different RACH configurations to different services (e.g., network slices). RACH configuration circuitry 1042 can then use the service (e.g., network slice) (e.g., NSSAI) identified in box 1102 as an entry in the mapping to identify the RACH configuration that will be used to transmit the service's PRACH.

[0179] In box 1106, the UE can perform a service-specific RACH operation based on the first RACH configuration. For example, the above combined Figure 10 The RACH processing circuitry 1043 shown and described, together with the communication and processing circuitry 1041 and the transceiver 1010, can transmit PRACH on the resources specified by the first RACH configuration. Alternatively or additionally, the RACH processing circuitry 1043, together with the communication and processing circuitry 1041 and the transceiver 1010, can use at least one RACH parameter specified by the first RACH configuration to transmit PRACH.

[0180] In some examples, RACH configuration and RACH operation may include at least one of 4-step RACH, 2-step RACH, or a combination thereof.

[0181] In some examples, the first RACH configuration specifies at least one of RACH resources, RACH parameters, or combinations thereof for RACH operations. In some examples, RACH parameters may include at least one of a preamble ramp step size, a backoff scaling factor, or combinations thereof. In some examples, RACH resources may include at least one of a preamble group, a RACH timing (RO), or combinations thereof.

[0182] In some examples, the method may also include receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message, a System Information Block (SIB) message, or a Non-Access Stratum (NAS) message.

[0183] In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group and a second RACH configuration for a second slice group that is different from the first slice group. In some examples, the first slice group is associated with a first use case, and the second slice group is associated with a second use case that is different from the first use case.

[0184] In some examples, the first RACH configuration for the first slice group specifies a first RACH resource, and the second RACH configuration for the second slice group specifies a second RACH resource that is different from the first RACH resource. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource that is different from the cell-specific RACH resource. In some examples, the first RACH configuration for the first slice group specifies first RACH parameters for the first slice of the first slice group and second RACH parameters for the second slice of the first slice group.

[0185] In some examples, the first RACH configuration for the first slice group specifies first RACH parameters, and the second RACH configuration for the second slice group specifies second RACH parameters. In some examples, the first RACH configuration for the first slice group specifies first RACH resources for the first slice of the first slice group and second RACH resources for the second slice of the first slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0186] In some examples, the method may further include determining whether the RACH operation is triggered by a service call at the user equipment or by a service arriving at the user equipment, and information about the service being provided to the access layer (AS) via a non-access stratum (NAS) message. In some examples, the AS layer selects a first RACH configuration for the service based on the service information.

[0187] In some examples, the method may further include determining that the RACH operation was not triggered by a service call at the user equipment or by a service arriving at the user equipment, and providing network slice selection assistance information (NSSAI) and slice priority information (e.g., indicating at least one priority of at least one slice) to the access stratum (AS) layer via non-access stratum (NAS) messages. In some examples, the AS layer selects the first RACH configuration for the service based on the service's NSSAI and slice priority information. In some examples, the AS layer selects the first RACH configuration for the service based on the highest priority slice associated with the NSSAI. In some examples, the AS layer selects the first RACH configuration for the service based on the lowest priority slice associated with the NSSAI.

[0188] In some examples, the method may further include receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group and a second RACH configuration for a second slice group different from the first slice group. In some examples, the first RACH configuration specifies a first RACH parameter set for the first slice group. In some examples, the second RACH configuration specifies a second RACH parameter set for the second slice group. In some examples, the first RACH configuration for the first slice group specifies a first RACH resource for a first slice of the first slice group and a second RACH resource for a second slice of the first slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0189] In some examples, the method may further include receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group. In some examples, the first RACH configuration specifies a first RACH resource for the first slice group and a second RACH configuration for a second slice group different from the first slice group. In some examples, the second RACH configuration specifies a second RACH resource for a second slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource. In some examples, the first RACH configuration for the first slice group specifies a cell-specific RACH parameter set for a first slice of the first slice group and a dedicated RACH parameter set for a second slice of the first slice group.

[0190] In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group associated with a mobile-oriented service and a second RACH configuration for a second slice group associated with a mobile-terminating service.

[0191] In some examples, the method may also include receiving an indication of RACH resources from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the indication of RACH resources specifies a first RACH resource for a first slice group and a second RACH resource for a second slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0192] In some examples, the method may also include receiving an indication of RACH parameters from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the indication of RACH parameters specifies a first set of RACH parameters for a first slice group and a second set of RACH parameters for a second slice group. In some examples, the first set of RACH parameters is a cell-specific set of RACH parameters, and the second set of RACH parameters is a dedicated set of RACH parameters different from the cell-specific set of RACH parameters.

[0193] In some examples, the first RACH configuration specifies a RACH resource. In some examples, performing a service-specific RACH operation based on the first RACH configuration may include sending a Physical Random Access Channel (PRACH) message on the RACH resource.

[0194] In some examples, the first RACH configuration specifies at least one RACH parameter. In some examples, performing a service-specific RACH operation based on the first RACH configuration may include sending a Physical Random Access Channel (PRACH) message using at least one RACH parameter.

[0195] Figure 12 This is a conceptual diagram illustrating an example of a hardware implementation of a base station (BS) 1200 employing a processing system 1214. In some implementations, the BS 1200 may correspond to... Figure 1 , Figure 2 , Figure 5 , Figure 6 and Figure 9 Any of the BS (e.g., gNB) or any of the scheduling entities shown in the diagram.

[0196] According to various aspects of this disclosure, an element, any part of an element, or any combination of elements can be implemented using the processing system 1214. The processing system may include one or more processors 1204. The processing system 1214 can be coupled with… Figure 10 The processing system 1014 shown is substantially the same, including a bus interface 1208, a bus 1202, a memory 1205, a processor 1204, and a computer-readable medium 1206. The memory 1205 may store RACH information 1215 (e.g., slice-related parameters) used by the processor 1204 to cooperate with the transceiver 1210 to send and / or receive RACH messages. Furthermore, the BS 1200 may include an interface 1230 (e.g., a network interface) that provides components for communicating with at least one other device within the core network and with at least one radio access network.

[0197] The BS 1200 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figures 1-9 The description and the following combination Figures 12-13 (As described). In some aspects of this disclosure, such as the processor 1204 utilized in BS1200, circuitry may be configured for various functions.

[0198] Processor 1204 can be configured to generate, schedule, and modify resource allocations or authorizations for time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1204 can schedule time-frequency resources across multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or micro-slots to carry user data services and / or control information to and / or from multiple UEs.

[0199] Processor 1204 can be configured to schedule resources for the transmission of downlink reference signals (e.g., SSB or CSI-RS) on multiple downlink beams of a downlink beam scan, based on a selected downlink beam scan type and a selected number of downlink reference signal resources indicated in a request for uplink beam refinement received from the UE. Processor 1204 can also be configured to schedule resources for uplink transmission of uplink reference signals (e.g., SRS) on multiple uplink beams of an uplink beam scan, based on a selected beam scan type and a selected number of uplink reference signal resources indicated in the request. Processor 1204 can also be configured to schedule resources that the UE can use to send the request. For example, uplink beam refinement request resources may include resources scheduled for the transmission of PUCCH, PUSCH, PRACH timing, or RRC messages. In some examples, processor 1204 can be configured to schedule PUSCH resources for the uplink beam refinement request in response to receiving a scheduling request from the UE.

[0200] Processor 1204 can also be configured to schedule resources for uplink signal transmission. In some examples, resources may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signals (e.g., based on uplink BPL) based on indications of uplink signals associated with one or more uplink transmit beams included in the request. In some examples, resources may be associated with an uplink transmission scheme indicating the number of uplink transmit beams to be used for uplink signals, the number of repetitions of each uplink transmit beam for the uplink signals, and the multiplexing scheme when more than one uplink transmit beam is used to transmit uplink signals.

[0201] In some aspects of this disclosure, processor 1204 may include communication and processing circuitry 1241. Communication and processing circuitry 1241 may be configured to communicate with a UE. Communication and processing circuitry 1241 may include one or more hardware components that provide a physical structure for performing various processes related to the communication described herein (e.g., signal reception and / or signal transmission). Communication and processing circuitry 1241 may also include one or more hardware components that provide a physical structure for performing various processes related to signal processing as described herein (e.g., processing received signals and / or processing signals for transmission). Communication and processing circuitry 1241 may also be configured to execute communication and processing software 1251 included on computer-readable medium 1206 to implement one or more of the functions described herein.

[0202] In some examples, the communication and processing circuitry 1241 may be configured to receive and process uplink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz via transceiver 1210 and antenna array 1220. For example, the communication and processing circuitry 1241 may be configured to receive a corresponding reference signal (e.g., SRS or DMRS) from the UE on each of a plurality of uplink beams during uplink beam scanning.

[0203] In some examples, the communication and processing circuitry 1241 may also be configured to generate downlink beamforming signals at millimeter-wave frequencies or frequencies below 6 GHz, and to transmit them via transceiver 1210 and antenna array 1220. For example, the communication and processing circuitry 1241 may be configured to transmit a corresponding downlink reference signal (e.g., SSB or CSI-RS) to the UE via at least one first antenna panel of antenna array 1220 on each of a plurality of downlink beams during downlink beam scanning. The communication and processing circuitry 1241 may also be configured to receive beam measurement reports from the UE.

[0204] The communication and processing circuit 1241 can also be configured to receive a request from the UE. For example, the request may be included in a MAC-CE carried in the PUSCH, a UCI in the PUCCH, a random access message, or an RRC message. The communication and processing circuit 1241 can also be configured to receive from the UE a scheduling request for uplink grants for a PUSCH (e.g., via a UCI in the PUCCH), the PUSCH carrying a MAC-CE including a request for uplink beam refinement.

[0205] The communication and processing circuitry 1241 can also be configured to receive uplink signals on one or more uplink transmit beams applied to the uplink signals. For example, the communication and processing circuitry 1241 can be configured to receive uplink signals on one or more uplink receive beams via at least one second antenna panel of the antenna array 1220. The uplink signals may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH.

[0206] Communication and processing circuitry 1241 may also be configured to control antenna array 1220 and transceiver 1210 to generate multiple downlink transmit beams during downlink beam scanning. Communication and processing circuitry 1241 may also be configured to receive beam measurement reports from the UE using communication and processing circuitry 1244. Communication and processing circuitry 1241 may also be configured to identify one or more selected uplink beams based on beam measurements. In some examples, communication and processing circuitry 1241 may be configured to compare individual RSRPs (or other beam measurements) measured for each of the serving downlink transmit beams in each of the downlink receive beams to identify the serving downlink receive beam, and further identify the serving downlink receive beam as the selected uplink transmit beam. Each serving downlink receive beam may have the highest measured RSRP (or other beam measurement) for one of the downlink transmit beams.

[0207] The communication and processing circuitry 1241 can be configured to receive one or more uplink transmit beams in an uplink beam scan. Each uplink transmit beam may carry an uplink reference signal (e.g., SRS) for measurement by the communication and processing circuitry 1241. The communication and processing circuitry 1241 can also be configured to obtain multiple beam measurements on each of a plurality of uplink receive beams of the antenna array 1220 for each of the uplink transmit beams. The communication and processing circuitry 1241 can also be configured to select (one or more) selected uplink transmit beams and corresponding uplink receive beams forming individual uplink BPLs based on the uplink beam measurements.

[0208] In some implementations where communication involves receiving information, communication and processing circuitry 1241 may obtain information from components of BS1200 (e.g., transceiver 1210 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 1241 may output information to another component of processor 1204, to memory 1205, or to bus interface 1208. In some examples, communication and processing circuitry 1241 may receive one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1241 may receive information via one or more channels. In some examples, communication and processing circuitry 1241 may include the functionality of components for receiving. In some examples, communication and processing circuitry 1241 may include the functionality of components for decoding.

[0209] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1241 may acquire information (e.g., from another component of processor 1204, memory 1205, or bus interface 1208), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1241 may output information to transceiver 1210 (e.g., transceiver 814 transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1241 may transmit one or more of the following: signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1241 may transmit information via one or more channels. In some examples, communication and processing circuitry 1241 may include the functionality of components for transmission (e.g., components for transmission). In some examples, communication and processing circuitry 1241 may include the functionality of components for encoding.

[0210] Processor 1204 may include RACH configuration circuitry 1242, which is configured to perform RACH configuration-related operations as discussed herein (e.g., in conjunction with...). Figures 7-9 (One or more of the described operations). The RACH configuration circuit 1242 may include the functionality of components for defining the RACH configuration set (e.g., as in...). Figure 7 Boxes 702 and 704 and / or Figure 9 Steps 906 and 916 and / or Figure 13 (As described in box 1302). The RACH configuration circuit 1242 may include the functionality of components for sending an indication of the RACH configuration set (e.g., as described in...). Figure 7 Box 706 and / or Figure 9Steps 908 and 918 and / or Figure 13 (As described in block 1304). The RACH configuration circuit 1242 can also be configured to execute the RACH configuration software 1252 included on the computer-readable medium 1206 to perform one or more of the functions described herein.

[0211] Processor 1204 may include RACH processing circuitry 1243, which is configured to perform RACH processing-related operations as discussed herein (e.g., in conjunction with...). Figures 7-9 (One or more of the described operations). The RACH processing circuit 1243 may include the functionality of a component for receiving RACH messages (e.g., as in...). Figure 7 Box 708 and / or Figure 9 Steps 914 and 924 and / or Figure 13 (As described in block 1306). The RACH processing circuitry 1243 may also be configured to execute the RACH processing software 1253 included on the computer-readable medium 1206 to perform one or more of the functions described herein.

[0212] Figure 13 This is a flowchart illustrating an example wireless communication method 1300 according to some aspects of this disclosure. As described herein, within the scope of this disclosure, some or all of the illustrated features may be omitted in certain implementations, and some illustrated features may not be necessary for implementing all embodiments. In some examples, method 1300 may be... Figure 12 The method is executed by BS 1200 as shown. In some examples, method 1300 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0213] In box 1302, the BS can limit the set of RACH configurations used for multiple service groups. For example, the above combined Figure 12 The RACH configuration circuit 1242 shown and described can define different network slice groups, each slice group including at least one network slice. Additionally, the RACH configuration circuit 1242 can specify a RACH configuration for each slice group. In some examples, the RACH configuration can be prioritized, whereby the RACH resources and / or parameters specified for one slice group can provide better RACH performance than those specified for another slice group. Furthermore, the RACH configuration circuit 1242 can prioritize the RACH resources and / or parameters specified for different slices within a slice group.

[0214] In box 1304, the BS can send an indication of the RACH configuration set. For example, RACH configuration circuit 1242 can generate a message including a RACH configuration index (which specifies a particular RACH configuration). (The above is combined...)Figure 12 The RACH processing circuitry 1242 shown and described, together with the communication and processing circuitry 1241 and the transceiver 1210, can then send messages on resources (e.g., PDCCH) monitored by one or more UEs.

[0215] In box 1306, the BS can receive RACH messages based on the first RACH configuration of the RACH configuration set, where the RACH message is for the service in the first group of multiple service groups. For example, the above combination Figure 12 The RACH processing circuitry 1243 shown and described, together with the communication and processing circuitry 1241 and the transceiver 1210, can receive PRACH on the resources specified by the first RACH configuration. Here, the RACH processing circuitry 1243 can attempt to decode the specified PRACH preamble sequence on one or more specified ROs.

[0216] In some examples, multiple service groups may include multiple network slices.

[0217] In some examples, the first RACH configuration specifies at least one of RACH resources, RACH parameters, or combinations thereof for RACH operations. In some examples, RACH parameters may include at least one of a preamble ramp step size, a backoff scaling factor, or combinations thereof. In some examples, RACH resources may include at least one of a preamble group, a RACH timing (RO), or combinations thereof.

[0218] In some examples, the indication to send the RACH configuration set may include an indication to send the RACH configuration set via a Radio Resource Control (RRC) message, a System Information Block (SIB) message, or a Non-Access Stratum (NAS) message.

[0219] In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group and a second RACH configuration for a second slice group that is different from the first slice group. In some examples, the first slice group is associated with a first use case, and the second slice group is associated with a second use case that is different from the first use case.

[0220] In some examples, the first RACH configuration for the first slice group specifies a first RACH resource, and the second RACH configuration for the second slice group specifies a second RACH resource that is different from the first RACH resource. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource that is different from the cell-specific RACH resource. In some examples, the first RACH configuration for the first slice group specifies first RACH parameters for the first slice of the first slice group and second RACH parameters for the second slice of the first slice group.

[0221] In some examples, the first RACH configuration for the first slice group specifies first RACH parameters, and the second RACH configuration for the second slice group specifies second RACH parameters. In some examples, the first RACH configuration for the first slice group specifies first RACH resources for the first slice of the first slice group and second RACH resources for the second slice of the first slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0222] In some examples, the indication to send a RACH configuration set may include an indication to send the RACH configuration set via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group. In some examples, the first RACH configuration specifies a first RACH parameter set for the first slice group and a second RACH configuration for a second slice group different from the first slice group. In some examples, the second RACH configuration specifies a second RACH parameter set for a second slice group. In some examples, the first RACH configuration for the first slice group specifies a first RACH resource for a first slice of the first slice group and a second RACH resource for a second slice of the first slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0223] In some examples, the indication to send a RACH configuration set may include an indication to send the RACH configuration set via a Radio Resource Control (RRC) message or a System Information Block (SIB). In some examples, the RACH configuration set specifies a first RACH configuration for a first slice group. In some examples, the first RACH configuration specifies a first RACH resource for the first slice group and a second RACH configuration for a second slice group different from the first slice group. In some examples, the second RACH configuration specifies a second RACH resource for a second slice group. In some examples, the first RACH resource is a cell-specific RACH resource, and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource. In some examples, the first RACH configuration for the first slice group specifies a cell-specific RACH parameter set for a first slice of the first slice group and a dedicated RACH parameter set for a second slice of the first slice group.

[0224] Aspect 1: A method for wireless communication at a user equipment, the method comprising: identifying a service; selecting a first RACH configuration for the service from a set of random access channel (RACH) configurations for multiple sets of services; and performing RACH operations for the service according to the first RACH configuration.

[0225] Aspect 2: According to the method described in aspect 1, wherein the multiple service groups include multiple network slices.

[0226] Aspect 3: The method according to aspect 1 or 2, wherein the first RACH configuration specifies at least one of the following: RACH resources for RACH operation, RACH parameters for RACH operation, or a combination thereof.

[0227] Aspect 4: According to the method of aspect 3, wherein the RACH parameter includes at least one of the following: preamble ramp step size, backoff scaling factor, or a combination thereof.

[0228] Aspect 5: According to the method of aspect 5, the RACH resource includes at least one of the following: a preamble group, a RACH timing (RO), or a combination thereof.

[0229] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the RACH configuration and RACH operation include at least one of the following: 4-step RACH, 2-step RACH, or a combination thereof.

[0230] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message, a System Information Block (SIB) message, or a Non-Access Stratum (NAS) message.

[0231] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the RACH configuration set specifies: a first RACH configuration for a first slice group; and a second RACH configuration for a second slice group different from the first slice group.

[0232] Aspect 9: According to the method described in aspect 8, wherein: the first slice group is associated with the first use case; and the second slice group is associated with the second use case, which is different from the first use case.

[0233] Aspect 10: The method according to aspect 8, wherein: a first RACH configuration for a first slice group specifies a first RACH resource; and a second RACH configuration for a second slice group specifies a second RACH resource different from the first RACH resource.

[0234] Aspect 11: The method according to aspect 10, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0235] Aspect 12: According to the method of aspect 10, wherein the first RACH configuration for the first slice group specifies: a first RACH parameter for the first slice of the first slice group; and a second RACH parameter for the second slice of the first slice group.

[0236] Aspect 13: The method according to aspect 8, wherein: a first RACH configuration for a first slice group specifies a first RACH parameter; and a second RACH configuration for a second slice group specifies a second RACH parameter.

[0237] Aspect 14: According to the method of aspect 13, wherein the first RACH configuration for the first slice group specifies: a first RACH resource for the first slice of the first slice group; and a second RACH resource for the second slice of the first slice group.

[0238] Aspect 15: The method according to aspect 14, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0239] Aspect 16: The method according to any one of Aspects 1 to 15 further includes: determining that the RACH operation is triggered by a service call at the user equipment or by a service arriving at the user equipment; and providing information about the service to the access layer (AS) layer via a non-access stratum (NAS) message; wherein the AS layer selects a first RACH configuration for the service based on the service information.

[0240] Aspect 17: The method according to any one of Aspects 1 to 16 further includes: determining that the RACH operation is not triggered by a service call at the user equipment or by a service reaching the user equipment; and providing network slice selection assistance information (NSSAI) and slice priority information for the service to the access layer (AS) via a non-access stratum (NAS) message; wherein the AS layer selects a first RACH configuration for the service based on the service's NSSAI and slice priority information.

[0241] Aspect 18: According to the method of aspect 17, wherein the AS layer selects the first RACH configuration for service based on the highest priority slice associated with NSSAI.

[0242] Aspect 19: The method described in aspect 17, wherein the AS layer selects the first RACH configuration for service based on the lowest priority slice associated with NSSAI.

[0243] Aspect 20: The method according to any one of aspects 1 to 19 further includes receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the RACH configuration set specifies: a first RACH configuration for a first slice group, wherein the first RACH configuration specifies a first RACH parameter set for the first slice group; and a second RACH configuration for a second slice group different from the first slice group, wherein the second RACH configuration specifies a second RACH parameter set for the second slice group.

[0244] Aspect 21: According to the method of aspect 20, wherein the first RACH configuration for the first slice group specifies: a first RACH resource for the first slice of the first slice group; and a second RACH resource for the second slice of the first slice group.

[0245] Aspect 22: According to the method of aspect 21, wherein the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource that is different from the cell-specific RACH resource.

[0246] Aspect 23: The method according to any one of Aspects 1 to 22 further includes receiving an indication of a RACH configuration set from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the RACH configuration set specifies: a first RACH configuration for a first slice group, wherein the first RACH configuration specifies a first RACH resource for the first slice group; and a second RACH configuration for a second slice group different from the first slice group, wherein the second RACH configuration specifies a second RACH resource for the second slice group.

[0247] Aspect 24: The method according to aspect 23, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0248] Aspect 25: According to the method of aspect 23, wherein the first RACH configuration for the first slice group specifies: a cell-specific RACH parameter set for the first slice of the first slice group; and a dedicated RACH parameter set for the second slice of the first slice group.

[0249] Aspect 26: The method according to any one of Aspects 1 to 25, wherein the RACH configuration set specifies: a first RACH configuration for a first slice group associated with a mobile-oriented service; and a second RACH configuration for a second slice group associated with a mobile-terminating service.

[0250] Aspect 27: The method according to aspect 26 further includes receiving an indication of RACH resources from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the indication of RACH resources specifies a first RACH resource for a first slice group and a second RACH resource for a second slice group.

[0251] Aspect 28: The method according to aspect 27, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0252] Aspect 29: The method according to aspect 26 further includes receiving an indication of RACH parameters from a base station via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the indication of RACH parameters specifies a first set of RACH parameters for a first slice group and a second set of RACH parameters for a second slice group.

[0253] Aspect 30: The method according to aspect 29, wherein: the first RACH parameter set is a cell-specific RACH parameter set; and the second RACH parameter set is a dedicated RACH parameter set different from the cell-specific RACH parameter set.

[0254] Aspect 31: The method according to any one of Aspects 1 to 30, wherein: a first RACH configuration specifies a RACH resource; and performing a RACH operation for a service according to the first RACH configuration includes sending a Physical Random Access Channel (PRACH) message on the RACH resource.

[0255] Aspect 32: The method according to any one of Aspects 1 to 31, wherein: a first RACH configuration specifies at least one RACH parameter; and performing a RACH operation for a service according to the first RACH configuration includes sending a Physical Random Access Channel (PRACH) message using at least one RACH parameter.

[0256] Aspect 33: A user equipment (UE) comprising: a transceiver configured to communicate with a radio access network; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1 to 32.

[0257] Aspect 34: An apparatus configured for wireless communication, comprising at least one component for performing any one of aspects 1 to 32.

[0258] Aspect 35: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to perform any one of aspects 1 to 32.

[0259] Aspect 36: A method for wireless communication at a base station, the method comprising: defining a RACH configuration set for multiple groups of services; sending an indication of the RACH configuration set; and receiving a RACH message according to a first RACH configuration of the RACH configuration set, wherein the RACH message is for a service of a first group of multiple groups of services.

[0260] Aspect 37: The method according to aspect 36, wherein the multiple service groups include multiple network slices.

[0261] Aspect 38: The method according to aspect 36 or 37, wherein the first RACH configuration specifies at least one of the following: RACH resources for RACH operation, RACH parameters for RACH operation, or a combination thereof.

[0262] Aspect 39: The method according to aspect 38, wherein the RACH parameter includes at least one of the following: preamble ramp step size, backoff scaling factor, or a combination thereof.

[0263] Aspect 40: The method according to any one of Aspects 36 to 39, wherein the indication for sending the RACH configuration set includes: sending the indication for the RACH configuration set via a Radio Resource Control (RRC) message, a System Information Block (SIB) message, or a Non-Access Stratum (NAS) message.

[0264] Aspect 41: The method according to any one of aspects 36 to 40, wherein the RACH configuration set specifies: a first RACH configuration for a first slice group; and a second RACH configuration for a second slice group different from the first slice group.

[0265] Aspect 42: According to the method of aspect 41, wherein: the first slice group is associated with the first use case; and the second slice group is associated with the second use case, which is different from the first use case.

[0266] Aspect 43: The method according to aspect 41, wherein: a first RACH configuration for a first slice group specifies a first RACH resource; and a second RACH configuration for a second slice group specifies a second RACH resource different from the first RACH resource.

[0267] Aspect 44: The method according to aspect 43, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0268] Aspect 45: According to the method of aspect 43, wherein the first RACH configuration for the first slice group specifies: a first RACH parameter for the first slice of the first slice group; and a second RACH parameter for the second slice of the first slice group.

[0269] Aspect 46: The method according to aspect 41, wherein: a first RACH configuration for a first slice group specifies a first RACH parameter; and a second RACH configuration for a second slice group specifies a second RACH parameter.

[0270] Aspect 47: According to the method of aspect 46, wherein the first RACH configuration for the first slice group specifies: a first RACH resource for the first slice of the first slice group; and a second RACH resource for the second slice of the first slice group.

[0271] Aspect 48: The method according to aspect 47, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0272] Aspect 49: The method according to any one of Aspects 36 to 48, wherein the indication of sending the RACH configuration set includes an indication of sending the RACH configuration set via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the RACH configuration set specifies: a first RACH configuration for a first slice group, wherein the first RACH configuration specifies a first RACH parameter set for the first slice group; and a second RACH configuration for a second slice group different from the first slice group, wherein the second RACH configuration specifies a second RACH parameter set for the second slice group.

[0273] Aspect 50: According to the method of aspect 49, wherein the first RACH configuration for the first slice group specifies: a first RACH resource for the first slice of the first slice group; and a second RACH resource for the second slice of the first slice group.

[0274] Aspect 51: According to the method of aspect 50, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0275] Aspect 52: The method according to any one of Aspects 36 to 15, wherein the indication of sending a RACH configuration set includes sending an indication of sending a RACH configuration set via a Radio Resource Control (RRC) message or a System Information Block (SIB), wherein the RACH configuration set specifies: a first RACH configuration for a first slice group, wherein the first RACH configuration specifies a first RACH resource for the first slice group; and a second RACH configuration for a second slice group different from the first slice group, wherein the second RACH configuration specifies a second RACH resource for the second slice group.

[0276] Aspect 53: The method according to aspect 52, wherein: the first RACH resource is a cell-specific RACH resource; and the second RACH resource is a dedicated RACH resource different from the cell-specific RACH resource.

[0277] Aspect 54: According to the method of aspect 52, wherein the first RACH configuration for the first slice group specifies: a cell-specific RACH parameter set for the first slice of the first slice group; and a dedicated RACH parameter set for the second slice of the first slice group.

[0278] Aspect 55: A base station (BS) comprising: a transceiver configured to communicate with a UE; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 36 to 54.

[0279] Aspect 56: An apparatus configured for wireless communication, comprising at least one component for performing any one of aspects 36 to 54.

[0280] Aspect 57: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to perform any one of aspects 36 to 54.

[0281] Several aspects of wireless communication networks have been presented with reference to example implementations. As will be readily understood by those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0282] As examples, these aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0283] Within this disclosure, the term “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as superior to or better than other aspects of this disclosure. Similarly, the term “aspect” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term “coupled” is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never directly contacts the second object. The terms “circuit” and “circuit system” are used broadly and are intended to include both hardware implementations of electronic devices and conductors, and software implementations of information and instructions, which, when connected and configured, enable the performance of the functions described in this disclosure without limitation on the type of electronic circuit, and which, when executed by a processor, enable the performance of the functions described in this disclosure. As used herein, the term “determine” can include a variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, search (e.g., searching in a table, database, or another data structure), ascertainment, resolution, selection, picking, creation, receiving (e.g., receiving information), access (e.g., accessing data in memory), and so on.

[0284] Figures 1-12 One or more of the components, steps, features, and / or functions shown may be rearranged and / or combined into a single component, step, feature, or function, or may be implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1-12Any of the apparatus, device, and / or component shown herein can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0285] It should be understood that the specific order or hierarchy of steps in the disclosed method is an illustration of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the method can be rearranged. The appended method claims present elements of various steps in a sample order and are not intended to be limited to the presented specific order or hierarchy, unless specifically stated herein.

[0286] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the text of the claims, wherein, unless specifically stated otherwise, references to elements in the singular form are not intended to mean “one and only one,” but rather “one or more.” Unless otherwise expressly stated, the term “some” refers to one or more. The phrase “at least one” in the list of referenced items means any combination of those items, including a single member. As an example, “at least one of a, b, or c” is intended to cover a; b; c; a and b; a and c; b and c; and a and b and c. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and intended to be included by the claims, and are known or to be known by those skilled in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims.

Claims

1. A method for wireless communication at a user equipment, the method comprising: identifying a service; receiving, from a base station, an indication of a set of random access channel (RACH) configurations for a plurality of groups of services; selecting a first RACH configuration for the service from the set of RACH configurations; and performing a RACH for the service according to the first RACH configuration, wherein the first RACH configuration specifies at least one of: a RACH resource for the RACH operation, a RACH parameter for the RACH operation, or a combination thereof, and depending on different triggers for RACH, the user equipment selects a corresponding RACH resource or RACH parameter for RACH access among the RACH resource or the RACH parameter, performing the RACH operation for the service according to the first RACH configuration comprises transmitting a physical random access channel (PRACH) message on the RACH resource, or transmitting the PRACH message using the RACH parameter, in each group of services of the plurality of groups of services, one or more services are configured with a set of non-cell-specific RACH resources and non-cell-specific RACH parameters, and other services are configured with a set of cell-specific RACH resources and cell-specific RACH parameters. ​

Images