Sidelink configuration of a wireless device

Abstract

A wireless device transmits a message to a base station. The message includes: a first request for a radio resource control (RRC) connection; and a second request for configuration parameters of a sidelink of the wireless device. The configuration parameters of the sidelink are received. The wireless device communicates via the sidelink based on the configuration parameters.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 910,250, filed October 3, 2019, the entire contents of which are hereby incorporated by reference. Attached Figure Description

[0003] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B An exemplary mobile communication network in which embodiments of the present disclosure may be implemented is shown.

[0005] Figure 2A and Figure 2B The new radio (NR) user plane and control plane protocol stacks are shown respectively.

[0006] Figure 3 It shows in Figure 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A It shows the flow through Figure 2A An example downlink data stream of the NR user plane protocol stack.

[0008] Figure 4B An exemplary format of the MAC subheader in a MAC PDU is shown.

[0009] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels used for downlink and uplink are shown respectively.

[0010] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0011] Figure 7 An exemplary configuration is shown in which OFDM symbols are grouped into NR frames.

[0012] Figure 8 An exemplary configuration of time slots in the time and frequency domains of an NR carrier is shown.

[0013] Figure 9 An example of bandwidth adaptation using three configured BWPs with NR carriers is shown.

[0014] Figure 10A Three carrier aggregation configurations with two component carriers are shown.

[0015] Figure 10B An example is shown of how aggregated cells can be configured into one or more PUCCH groups.

[0016] Figure 11A An example of the structure and location of the SS / PBCH block is shown.

[0017] Figure 11B An example of CSI-RS mapped in the time and frequency domains is shown.

[0018] Figure 12A and Figure 12B Examples of three downlink and uplink beam management procedures are shown respectively.

[0019] Figure 13A , Figure 13B and Figure 13C Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

[0020] Figure 14A An example of the CORESET configuration for the bandwidth portion is shown.

[0021] Figure 14B An example of CCE-to-REG mapping for DCI transport is shown on CORESET and PDCCH processing.

[0022] Figure 15 An example of a wireless device communicating with a base station is shown.

[0023] Figure 16A , Figure 16B , Figure 16C and Figure 16D An exemplary structure for uplink and downlink transmission is shown.

[0024] Figure 17 This is an example of a deployment scenario for D2D communication outside network coverage, according to an exemplary embodiment of this disclosure.

[0025] Figure 18 A resource pool for sidelink operation is shown according to an exemplary embodiment of the present disclosure.

[0026] Figure 19 A procedure for acquiring radio resources for a sidelink, executed by the UE when the UE is in an RRC idle or RRC inactive state and has sidelink data to be transmitted, is shown according to an exemplary embodiment of the present disclosure.

[0027] Figure 20 Two RRC connection procedures (A and B) according to an exemplary embodiment of the present disclosure are shown.

[0028] Figure 21 A procedure is shown for a UE to obtain sidelink radio resources from a base station in an RRC connected state according to an exemplary embodiment of the present disclosure.

[0029] Figure 22 The procedure for obtaining SIBs other than SIB1, executed by the UE in an RRC idle or RRC inactive state, according to an exemplary embodiment of the present disclosure, is illustrated.

[0030] Figure 23 The exemplary embodiment of this disclosure illustrates a procedure performed by a UE to select between a 2-step SI request procedure and a 4-step SI request procedure to obtain an SIB other than SIB1.

[0031] Figure 24 An SI request signal stream (signal stream A) for a 2-step SI request procedure and an SI request signal stream (signal stream B) for a 4-step SI request procedure are shown according to an exemplary embodiment of the present disclosure.

[0032] Figure 25 Two exemplary procedures are shown for a UE to acquire one or more SIBs in an RRC connected state, according to an exemplary embodiment of the present disclosure.

[0033] Figure 26 A procedure for a base station to receive sidelink authorization information from an AMF according to an exemplary embodiment of this disclosure is shown.

[0034] Figure 27 A procedure (Option 1) for obtaining configuration parameters of a side link according to an exemplary embodiment of this disclosure is shown.

[0035] Figure 28 A procedure (option 2) for obtaining configuration parameters of a side link according to an exemplary embodiment of this disclosure is shown.

[0036] Figure 29 A procedure is shown for transferring the RRC state of a UE between an RRC connected state and an RRC inactive state, according to an exemplary embodiment of the present disclosure.

[0037] Figure 30 An enhancement to the storage-side link bearer configuration in an RRC inactive state is illustrated, according to an exemplary embodiment of the present disclosure.

[0038] Figure 31 An enhancement procedure for restoring / recovering sidelink bearer configuration in an RRC inactive state is shown, according to an exemplary embodiment of the present disclosure.

[0039] Figure 32 The exemplary embodiments of the present disclosure are illustrated by combining with respect to... Figure 27 and about Figure 31 This is a program that obtains the configuration parameters of the side link when the RRC is inactive.

[0040] Figure 33 A procedure (Option 1) for obtaining configuration parameters of a sidelink in an RRC connection state is shown according to an exemplary embodiment of this disclosure.

[0041] Figure 34 A procedure (option 2) for obtaining configuration parameters of a side link in an RRC connection state is shown according to an exemplary embodiment of the present disclosure.

[0042] Figure 35 The diagram illustrates the waiting time for obtaining radio resources for sidelink services according to an exemplary embodiment of this disclosure.

[0043] Figure 36 The exemplary implementation of this disclosure illustrates UE behavior for requesting a sidelink SIB.

[0044] Figure 37 A procedure for managing an RRC connection according to an exemplary embodiment of this disclosure is shown (Option 1).

[0045] Figure 38 A procedure for managing an RRC connection according to an exemplary embodiment of this disclosure is shown (Option 2).

[0046] Figure 39 A procedure (Option 1) for an RRC connection of the management side link SIB according to an exemplary embodiment of this disclosure is shown.

[0047] Figure 40 A procedure for managing RRC connections for sidelink SIBs is shown according to an exemplary embodiment of this disclosure.

[0048] Figure 41 This is a flowchart of an exemplary embodiment of the present disclosure.

[0049] Figure 42 This is a flowchart of an exemplary embodiment of the present disclosure. Detailed Implementation

[0050] In this disclosure, various embodiments are presented as examples of how the disclosed techniques can be implemented and / or how they can be practiced in various environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail can be made therein without departing from the scope of the invention. Indeed, after reading this specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined within the scope of this disclosure to form other embodiments. Any drawings highlighting features and advantages are presented for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in any flowchart may be reordered or used only optionally in some embodiments.

[0051] The implementation scheme can be configured to operate as needed. The disclosed mechanism can be executed when certain criteria are met, for example, in the wireless device, base station, radio environment, network, or combinations thereof. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, or combinations thereof. Various exemplary implementation schemes can be applied when one or more of these criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocol can be implemented.

[0052] A base station can communicate with a mixture of wireless devices. The wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices can have specific capabilities depending on the type and / or capability of the wireless device. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and in a given sector of a base station using a given LTE or 5G version. The multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0053] In this disclosure, “a” and “an”, and similar expressions, should be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” should be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” should be interpreted as “may, for example.” In other words, the term “may” indicates that the expression following the term “may” is an example of one of a number of suitable possibilities that one or more embodiments in various implementations may or may not be adopted. As used herein, the terms “comprises” and “consists of” enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude the inclusion of components not listed in the element being described. In contrast, “consists of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” should be interpreted as “at least partially based on”, rather than, for example, “based on only.” As used herein, the term “and / or” refers to any possible combination of the listed elements. For example, “A, B and / or C” could mean: A; B; C; A and B; A and C; B and C; or A, B and C.

[0054] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The expression "based on" (or equivalently "at least based on") indicates that the expression following the term "based on" is an example of a suitable possibility among a number of suitable possibilities that may or may not be used in one or more embodiments of various implementations. The expression "in response to" (or equivalently "at least in response to") indicates that the expression following the expression "in response to" is an example of a suitable possibility among a number of suitable possibilities that may or may not be used in one or more embodiments of various implementations. The expression "depends on" (or equivalently "at least depends on") indicates that the expression following the expression "depends on" is an example of a suitable possibility among a number of suitable possibilities that may or may not be used in one or more embodiments of various implementations. The expression “adopt / use” (or equivalently “at least adopt / use”) indicates that the expression following “adopt / use” is an example of one of a number of suitable possibilities that may or may not be used in one or more of the various implementation schemes.

[0055] The term "configurable" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configurable" can mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics, whether the device is in an operational or non-operational state. Terms such as "control messages generated in the device" can mean that control messages have parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0056] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In an exemplary embodiment, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0057] Many of the proposed features are described as optional by using the word "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the set of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0058] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented as hardware, software combined with hardware, firmware, wet hardware (i.e., hardware with biological elements), or combinations thereof (the foregoing may be behaviorally equivalent). For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). Modules can be implemented using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. Hardware description languages ​​(HDLs) such as VHSIC Hardware Description Language (VHDL) or Verilog are frequently used to program FPGAs, ASICs, and CPLDs. These languages ​​configure connections between limited internal hardware modules on a programmable device. The aforementioned techniques are often used in combination to achieve the desired functional modules.

[0059] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented is shown. The mobile communication network 100 may, for example, be a Public Land Mobile Network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a radio device 106.

[0060] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN. As part of the interface functionality, CN 102 can establish an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide billing functionality.

[0061] RAN 104 can connect CN 102 to radio device 106 via radio communication over an air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplexing technologies.

[0062] The term "wireless device" may be used throughout this disclosure to mean and cover any mobile or fixed (non-mobile) device that requires or has wireless communication available to it. For example, a wireless device may be a telephone, smartphone, tablet, computer, laptop computer, sensor, instrument, wearable device, Internet of Things (IoT) device, roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, mobile phone, wireless transceiver unit (WTRU), and / or wireless communication device.

[0063] RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: Node B (associated with UMTS and / or 3G standards); Evolved Node B (eNB, associated with E-UTRA and / or 4G standards); Remote Radio Header (RRH); Baseband processing unit coupled to one or more RRHs; Repeater or Relay node for extending the coverage area of ​​a donor node; Next Generation Evolved Node B (ng-eNB); Generation Node B (gNB, associated with NR and / or 5G standards); Access Point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

[0064] The base stations included in RAN 104 may include one or more sets of antennas for communicating with wireless device 106 via an air interface. For example, one or more base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of a cell may be determined based on the range within which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in that cell. The cells of the base stations may together provide radio coverage over a wide geographical area to wireless device 106 to support wireless device mobility.

[0065] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, as baseband processing units coupled to several remote radio heads (RRHs), and / or as repeaters or relay nodes for extending the coverage area of ​​the donor node. The baseband processing unit coupled to the RRH can be part of a centralized RAN architecture or a cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode the radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0066] RAN 104 can be adopted as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmit power. RAN 104 can also be adopted as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0067] The Third Generation Partnership Project (3GPP) was established in 1998 to facilitate collaboration with... Figure 1A The mobile communication network 100 in this disclosure provides global standardization for similar mobile communication networks. To date, 3GPP has defined specifications for three generations of mobile networks: the third-generation (3G) network known as Universal Mobile Telecommunications System (UMTS), the fourth-generation (4G) network known as Long Term Evolution (LTE), and the fifth-generation (5G) network known as 5G System (5GS). The embodiments of this disclosure are described with reference to the RAN of the 3GPP 5G network, known as Next Generation RAN (NG-RAN). These embodiments can be applied to the RAN of other mobile communication networks, such as... Figure 1A RAN 104, the RAN of early 3G and 4G networks, and those RANs of future networks that have not yet been specified (e.g., 3GPP 6G networks). NG-RAN implements 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0068] Figure 1BAnother exemplary mobile communication network 150 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). This can be compared with... Figure 1A These components are implemented and operated in the same or similar ways as the corresponding components described.

[0069] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and these one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0070] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B. For ease of explanation, in Figure 1B These are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to the one or more DNs, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0071] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0072] 5G-CN 152 may include, for clarity, not listed here. Figure 1B One or more additional network functions are shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Openness Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0073] NG-RAN 154 can connect 5G-CN 152 to UE 156 via radio communication over an air interface. NG-RAN 154 may include: one or more gNBs, such as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, such as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). gNB 160 and ng-eNB 162 may be more generally referred to as base stations. gNB 160 and ng-eNB 162 may include one or more sets of antennas for communicating with UE 156 over the air interface. For example, one or more of gNB 160 and / or one or more of ng-eNB 162 may include three sets of antennas to control three cells (or sectors) respectively. The gNB 160 and ng-eNB 162 cells can work together to provide UE 156 with radio coverage over a wide geographical area to support UE mobility.

[0074] like Figure 1BAs shown, gNB 160 and / or ng-eNB 162 can connect to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using a direct physical connection and / or an indirect connection via a potential transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... Figure 1B As shown, the gNB 160A can connect to the UE 156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements in the system are used to exchange data and signaling messages, and can include two planes: a user plane and a control plane. The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

[0075] The gNB 160 and / or ng-eNB 162 can connect to one or more AMF / UPF functions of the 5G-CN 152, such as AMF / UPF 158, via one or more NG interfaces. For example, the gNB 160A can connect to the UPF 158B of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface can provide user plane PDU delivery (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A can connect to the AMF158A via an NG control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, NAS message delivery, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0076] The gNB 160 can provide NR user plane and control plane protocol termination to UE 156 via the Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to UE 156A via the Uu interface associated with the first protocol stack. The ng-eNB 162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE 156 via the Uu interface, where E-UTRA refers to 3GPP 4G radio access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol termination to UE 156B via the Uu interface associated with the second protocol stack.

[0077] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across those multiple AMF / UPF nodes.

[0078] As discussed, Figure 1B The interfaces between network elements (e.g., Uu, Xn, and NG interfaces) can be associated with the protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane handles data of interest to the user, while the control plane handles signaling messages of interest to the network elements.

[0079] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220 are shown respectively. Figure 2A and Figure 2B The protocol stack shown can be used with, for example, Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown are the same or similar.

[0080] Figure 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include the Medium Access Control (MAC) layer 212 and 222, the Radio Link Control (RLC) layer 213 and 223, the Packet Data Convergence Protocol (PDCP) layer 214 and 224, and the Service Data Application Protocol (SDAP) layer 215 and 225. These four protocols together can constitute Layer 2 of the OSI model or the Data Link Layer.

[0081] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3Starting from the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and the DN. The PDU session can have one or more QoS flows. The CN's UPF (e.g., UPF 158B) can map IP packets to these one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between these one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0082] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be useful for services requiring high reliability.

[0083] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are those that occur when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapping split radio bearers between RLC channels belonging to a cell group.

[0084] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on each logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and 223 can provide RLC channels respectively as services to PDCP 214 and 224.

[0085] MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing data units belonging to one or more logical channels into / from a transport module (TB) delivered to / from PHYs 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority processing between UEs via dynamic scheduling. Scheduling can be performed on downlink and uplink in gNB 220 (at MAC 222). MACs 212 and 222 can be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), priority processing between logical channels of UE 210 via logical channel priority ordering, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In the example, the mapping constraints in logical channel priority ordering can control which set of parameters and / or transmission timing the logical channel can use. For example... Figure 3 As shown, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

[0086] PHYs 211 and 221 can perform transport-to-physical channel mapping and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHYs 211 and 221 can perform multi-antenna mapping. For example... Figure 3 As shown, PHYs 211 and 221 can provide one or more transport channels as services to MACs 212 and 222.

[0087] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AThe diagram illustrates the downlink data flow through the NR user plane protocol stack to generate three IP packets (n, n+1, and m) of two TB at the gNB 220. The uplink data flow through the NR user plane protocol stack can be compared with... Figure 4A The downlink data flow described in the text is similar.

[0088] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0089] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). Figure 4A (As shown in the image regarding IP packet m) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

[0090] Figure 4BAn exemplary format of the MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a Logical Channel Identifier (LCID) field identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0091] Figure 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. These can be used at the beginning of downlink transmissions within the MAC PDU (e.g., ...). Figure 4B (As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. The MAC CE can be used for in-band control signaling. Exemplary MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP repeated detection, channel state information (CSI) reports, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

[0092] Before describing the NR control plane protocol stack, we will first describe the mapping between logical channels, transport channels, and physical channels, as well as channel types. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack, which will be described later below.

[0093] Figure 5A and Figure 5BThe mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0094] - Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level;

[0095] - Broadcast Control Channel (BCCH), which carries system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIB), wherein the system information messages can be used by the UE to obtain information about how the cell is configured and how to operate within the cell;

[0096] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0097] - Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure that UE; and

[0098] - Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0099] Transport channels are used between the MAC layer and the PHY layer, and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0100] - Paging Channel (PCH), which is used to carry paging messages originating from PCCH;

[0101] - Broadcast channel (BCH), which is used to carry MIBs from the BCCH;

[0102] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH;

[0103] - Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and

[0104] - Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0105] The PHY can use physical channels to transfer information between processing levels of the PHY. A physical channel can be a set of associated time-frequency resources used to carry information from one or more transport channels. The PHY can generate control information to support lower-level PHY operations and provide this control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

[0106] - Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH;

[0107] - The Physical Downlink Shared Channel (PDSCH) is used to carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH;

[0108] - The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling permissions, and uplink power control commands;

[0109] - The Physical Uplink Shared Channel (PUSCH) is used to carry uplink data and signaling messages from the UL-SCH, and in some cases, uplink control information (UCI) as described below.

[0110] - The Physical Uplink Control Channel (PUCCH), which carries the UCI, including HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

[0111] - Physical Random Access Channel (PRACH), which is used for random access.

[0112] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals will be described in more detail below.

[0113] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2BAs shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0114] NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 (e.g., AMF 158A) or more generally between UE 210 and CN. NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages known as NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. NAS messages can be transmitted using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0115] RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally between UE 210 and RAN. RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages known as RRC messages. RRC messages can be transmitted between UE 210 and RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC can multiplex control plane and user plane data into the same transport block (TB). RRC 216 and 226 can provide control plane functions such as: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of RRC connections between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of such reporting; detection and recovery of radio link failures (RLFs); and / or NAS messaging. As part of establishing an RRC connection, RRC 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0116] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 depicted in the text Figure 2A and Figure 2B The UE 210 depicted herein is identical or similar to any other wireless device described in this disclosure. Figure 6 As shown, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0117] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in RAN 104 as depicted herein; Figure 1B One of gNB 160 or ng-eNB 162 described herein; Figure 2A and Figure 2B The gNB220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for that UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

[0118] In RRC Idle 604, an RRC context may not have been established for the UE. In RRC Idle 604, the UE may not have an RRC connection with the base station. When in RRC Idle 604, the UE may be in a sleep state most of the time (e.g., to conserve battery power). The UE may periodically wake up (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The UE's mobility can be managed by the UE through a procedure called cell reselection. The RRC state can be transitioned from RRC Idle 604 to RRC Connection 602 through Connection Establishment Procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0119] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connection 602 via connection resumption procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0120] RRC states can be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to notify the UE of events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE is currently camped, rather than across the entire mobile network. Mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0121] A tracking area can be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0122] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identities, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0123] The base station that stores the RRC context for the UE, or the UE's last serving base station, can be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

[0124] gNB, such as Figure 1B The gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0125] In NR, physical signals and physical channels (about Figure 5A and Figure 5BThe concepts discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM or M-PSK symbols) and divided into F parallel symbol streams. These F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block takes F source symbols at a time (one source symbol from each of the F parallel symbol streams) and uses each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upsampling, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

[0126] Figure 7 An exemplary configuration of NR frames in which OFDM symbols are grouped is shown. NR frames can be identified by a System Frame Number (SFN). An SFN can repeat for a period of 1024 frames. As shown, the duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into time slots, which include, for example, 14 OFDM symbols per time slot.

[0127] The duration of a time slot can depend on the parameter set of the OFDM symbols used for that time slot. NR supports flexible parameter sets to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). Parameter sets can be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing can be scaled up by two powers from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be scaled down by two powers from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0128] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing has a shorter time slot duration and correspondingly more time slots per subframe. Figure 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slot or sub-time slot transmissions.

[0129] Figure 8 An exemplary configuration of a time slot in the time and frequency domains of an NR carrier is shown. This time slot includes a resource element (RE) and a resource block (RB). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... Figure 8 As shown. RB spans twelve consecutive REs in the frequency domain, as... Figure 8 As shown. The NR carrier can be limited to a width of 275 RB or 275 × 12 = 3300 subcarriers. If this limitation is used, the NR carrier can be limited to 50, 100, 200, and 400 MHz for subcarrier spacing of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on the limitation of 400 MHz bandwidth per carrier.

[0130] Figure 8This illustrates a single set of parameters used across the entire bandwidth of an NR carrier. In other exemplary configurations, multiple sets of parameters can be supported on the same carrier.

[0131] NR can support wide carrier bandwidths (e.g., up to 400MHz for a subcarrier spacing of 120kHz). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth can be prohibitively expensive in terms of UE power consumption. In the example, to reduce power consumption and / or for other purposes, the UE can adjust the size of its receive bandwidth based on the amount of traffic it plans to receive. This is called bandwidth adaptation.

[0132] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In the example, a BWP can be defined by a subset of consecutive Relays (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0133] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0134] For a set of configured downlink BWPs on a primary cell (PCell), the base station can configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where a UE can locate control information. The search space can be a UE-specific search space or a common search space (which may be used by multiple UEs). For example, the base station can configure a common search space for the UE on a PCell or primary / secondary cell (PSCell) within an active downlink BWP.

[0135] For an uplink BWP in a set of configured uplink BWPs, the BS can configure one or more resource sets for the UE for one or more PUCCH transmissions. The UE can receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWP based on a configured set of parameters (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE can transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on a configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0136] One or more BWP indicator fields can be provided in the downlink control information (DCI). The value of the BWP indicator field can indicate which BWP in the set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields can indicate the active uplink BWP for one or more uplink transmissions.

[0137] The base station can semi-statically configure a default downlink BWP for the UE within a set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to the UE, the default downlink BWP can be the initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0138] The base station can configure the BWP inactivity timer value for the UE for the PCell. The UE can start or restart the BWP inactivity timer at any appropriate time. For example, the UE can start or restart the BWP inactivity timer when: (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can run the BWP inactivity timer toward its expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0139] In the example, the base station can semi-statically configure the UE using one or more BWPs. The UE can switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to the expiration of a BWP inactivity timer (e.g., in the case that the second BWP is the default BWP).

[0140] Downlink and uplink BWP handovers can be performed independently in paired spectrum (where BWP handover refers to switching from the currently active BWP to a non-currently active BWP). In unpaired spectrum, downlink and uplink BWP handovers can be performed simultaneously. Handovers can occur between configured BWPs based on RRC signaling, DCI, the expiration of a BWP inactivity timer, and / or the initiation of random access.

[0141] Figure 9 An example of bandwidth adaptation using three configured BWPs on an NR carrier is shown. A UE configured with these three BWPs can switch from one BWP to another at a handover point. Figure 9 In the example shown, the BWPs include: BWP902 with a bandwidth of 40MHz and a subcarrier spacing of 15kHz; BWP904 with a bandwidth of 10MHz and a subcarrier spacing of 15kHz; and BWP906 with a bandwidth of 20MHz and a subcarrier spacing of 60kHz. BWP902 can be the initial active BWP, and BWP904 can be the default BWP. The UE can switch between BWPs at a handover point. Figure 9 In the example, the UE can switch from BWP 902 to BWP 904 at handover point 908. The handover at handover point 908 can occur for any suitable reason, such as in response to the expiration of a BWP inactivity timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 906 at handover point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE can switch from active BWP 906 to BWP 904 at handover point 912 in response to the expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 902 at handover point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

[0142] If a UE is configured for a secondary cell with a default downlink BWP and timer values ​​from a set of configured downlink BWPs, the UE procedure for switching BWPs on the secondary cell can be the same as / similar to that on the primary cell. For example, the UE can use these values ​​on the secondary cell in the same / similar way as the UE would use the timer values ​​and default downlink BWP of the primary cell.

[0143] To provide higher data rates, carrier aggregation (CA) can be used to combine two or more carriers and transmit them simultaneously to / from the same UE. The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are multiple serving cells for the UE, one serving cell per CC. A CC can have three configurations in the frequency domain.

[0144] Figure 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (band A) and located directly adjacent to each other within the band. In the intra-band discontinuous configuration 1004, the two CCs are aggregated in a frequency band (band A) and separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are located in frequency bands (band A and band B).

[0145] In the example, up to 32 CCs can be aggregated. Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD or FDD). The serving cell for the UE using CA can have downlink CCs. For FDD, one or more uplink CCs can optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers can be useful when the UE has more data traffic in the downlink than in the uplink.

[0146] When using CA, one of the aggregated cells used for the UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE initially connects during RRC connection establishment, re-establishment, and / or handover. The PCell provides the UE with NAS mobility information and security input. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells used for the UE can be referred to as secondary cells (SCells). In the example, the SCell can be configured after the PCell is configured for the UE. For example, the SCell can be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DLSCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

[0147] Configurable SCells for a UE can be activated and deactivated based on factors such as traffic and channel conditions. Deactivating an SCell can mean ceasing PDCCH and PDSCH reception on the SCell, and ceasing PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., a subset of configured SCells) are activated or deactivated. A configured SCell can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0148] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, a process known as self-scheduling. A cell's DCI can be transmitted on another cell, a process known as cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0149] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10B In the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregation unit depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCI associated with the downlink CC, and that PCell may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

[0150] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carrier. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including the first carrier is activated.

[0151] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport modules can be generated based on the assignment / license of each serving cell. The transport module and its potential HARQ retransmissions can be mapped to the serving cell.

[0152] In the downlink, the base station can transmit one or more reference signals (RS) (e.g., unicast, multicast, and / or broadcast) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, such as...). Figure 5A (As shown). In the uplink, the UE can transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, such as...). Figure 5B (As shown). PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

[0153] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A (As shown in the diagram). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11A This is an example, and these parameters (the number of SS / PBCH blocks per burst, the periodicity of the burst, the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factor. In the example, the UE can assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing.

[0154] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11AAs shown in the example, and can span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH can have a common center frequency. PSS can be transmitted first and can span, for example, 1 OFDM symbol and 127 subcarriers. SSS can be transmitted after PSS (e.g., after two symbols) and can span 1 OFDM symbol and 127 subcarriers. PBCH can be transmitted after PSS (e.g., spanning the next 3 OFDM symbols) and can span 240 subcarriers.

[0155] The UE may not know the location of the SS / PBCH block in the time and frequency domains (e.g., when the UE is searching for a cell). To find and select a cell, the UE can monitor the carrier of the PSS. For example, the UE can monitor the frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at different frequency locations within the carrier, as indicated by the synchronization grating. If the PSS is found at a certain location in the time and frequency domains, the UE can determine the locations of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block can be a cell-defined SS block (CD-SSB). In the example, the primary cell can be associated with the CD-SSB. The CD-SSB can be located on the synchronization grating. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

[0156] The SS / PBCH block can be used by the UE to determine one or more parameters of the cell. For example, the UE can determine the Physical Cell Identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE can determine the location of the cell's frame boundary based on the location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission mode in which the SS / PBCH block is at a known distance from the frame boundary.

[0157] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can include an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can include a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can include System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0158] The UE may assume that one or more SS / PBCH blocks transmitted using the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

[0159] SS / PBCH blocks (e.g., those within a half-frame) can be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​the cell). In the example, the first SS / PBCH block can be transmitted in the first spatial direction using the first beam, and the second SS / PBCH block can be transmitted in the second spatial direction using the second beam.

[0160] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block of these multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block of these multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0161] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0162] The base station can semi-statically configure the UE using one or more CSI-RS resource sets. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the UE that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0163] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI reports at specific times and / or periodically. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

[0164] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE can be configured to use the same OFDM symbols for both the downlink CSI-RS and the control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE can also be configured to use the same OFDM symbols for both the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0165] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a preceding DMRS mode. The preceding DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE using the number (e.g., maximum number) of preceding DMRS symbols used for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS modes, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0166] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. This set of PRBs can be represented as a Precoder Resource Block Group (PRG).

[0167] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0168] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or mode of downlink PT-RS can be configured based on the UE through a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks can support multiple PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS can be restricted to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0169] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS mode, and / or DMRS perturbation sequence can be the same or different.

[0170] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS on one or more layers present in the PUSCH. In the example, a higher layer may configure up to three DMRS for the PUSCH.

[0171] Depending on the UE's RRC configuration, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or mode of the uplink PT-RS can be configured based on the UE through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least one MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be restricted to the UE's scheduled time / frequency duration.

[0172] The UE can transmit SRS to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks to uplink PUSCH transmissions from the UE. The base station can semi-statically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in the SRS resource sets of the one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In the example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In the example, when PUSCH and SRS are transmitted in the same time slot, the UE can be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0173] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe level periodicity; time slots of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiating OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0174] An antenna port is defined such that a symbol on the antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port, through the same channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel used to transmit the second symbol on the antenna port (e.g., fade gain, multipath delay, etc.) from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted. These one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0175] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After setting up an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0176] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown may represent a resource block (RB) within the cell's bandwidth. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transport comb, Quasi-Co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0177] Figure 11B The three beams shown can be configured for use in a UE-specific configuration. Figure 11B The diagram shows three beams (beam #1, beam #2, and beam #3), with more or fewer beams that can be configured. CSI-RS1101 can be assigned to beam #1, which can be transmitted on one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be assigned to beam #2, which can be transmitted on one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be assigned to beam #3, which can be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., those not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time domain multiplexing (TDM), the beam for a UE can be configured such that the beam for the UE uses symbols from beams of other UEs.

[0178] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) of a configured CSI-RS resource. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In the example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE can receive downlink transmissions with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0179] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on this assessment, the UE can transmit a beam measurement report indicating one or more beampup quality parameters, including, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0180] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmit (Tx) beams for a Transport Receive Point (TRP) (or multiple TRPs), for example, to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for the beam set (shown as an ellipse rotating counterclockwise in the top rows of P1 and P2, indicated by the dashed arrows). Beamforming at the UE can include Rx beam sweeping for the beam set (shown as an ellipse rotating clockwise in the bottom rows of P1 and P3, indicated by the dashed arrows). Procedure P2 can be used to enable UE measurement of the Tx beams for a TRP (shown as an ellipse rotating counterclockwise in the top row of P2, indicated by the dashed arrows). The UE and / or base station may perform procedure P2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0181] Figure 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, for example, to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0182] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect a beam fault based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0183] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, which may include one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station may indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0184] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam fault recovery requests. The network can initiate random access procedures for handover and / or for establishing time comparisons for SCell additions.

[0185] Figure 13A A four-step contention-based random access procedure is shown. Before initiating this procedure, the base station may transmit configuration message 1310 to the UE. Figure 13AThe procedure shown involves the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0186] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. These one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast these one or more RRC messages to one or more UEs. These one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). The UE may determine the time and frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0187] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. These one or more PRACH timings may be predefined. These one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). These one or more RACH parameters may indicate a relationship between (a) one or more PRACH timings and (b) one or more reference signals. These one or more RACH parameters may indicate a relationship between (a) one or more preambles and (b) one or more reference signals. These one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, these one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

[0188] The one or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmission power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., the received target power and / or the initial power of the preamble transmission). One or more power offsets indicated by the one or more RACH parameters may exist. For example, the one or more RACH parameters can indicate: power ramp step size; power offset between SSB and CSI-RS; power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or power offset values ​​between preamble groups. The one or more RACH parameters can indicate one or more thresholds upon which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier).

[0189] Msg 1 1311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude of Msg 3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0190] The UE can determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE can determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH timing and the one or more reference signals.

[0191] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power used for the preamble retransmission. The UE may select the initial preamble transmission power based on path loss measurements and / or the target received preamble power configured by the network. The UE may determine the preamble to be retransmitted and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp step size used for the preamble retransmission. The ramp step size may be the amount by which the uplink transmission power used for the retransmission is incrementally increased. If the UE determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in the previous preamble transmission, the UE may ramp up the uplink transmission power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax), the UE can determine that the random access procedure has not been successfully completed.

[0192] The Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may include a time comparison command that the UE can use to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to initiate the time window based on the timing of the PRACH used by the UE to transmit the preamble. For example, a UE may initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). These one or more symbols can be determined based on a set of parameters. The PDCCH may be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include:

[0193] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0194] , where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0195] The UE may transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. If these multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, a UE may include a device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

[0196] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 includes a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 includes a TC-RNTI (e.g., if the UE is in RRC_IDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU transmitted in Msg 3 1313, the UE can determine that contention resolution was successful and the random access procedure was successfully completed.

[0197] The UE can be configured with Supplemental Uplink (SUL) carriers and Normal Uplink (NUL) carriers. Initial access (e.g., random access procedure) can be supported on the uplink carriers. For example, the base station can configure two separate RACH configurations for the UE: one for the SUL carrier and another for the NUL carrier. To enable random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, the UE can determine the SUL carrier if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions during the random access procedure (e.g., Msg1 1311 and / or Msg 3 1313) can be preserved on the selected carrier. In one or more cases, the UE can switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE can determine and / or switch uplink carriers for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (e.g., listen before speaking).

[0198] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The program shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg 4 1314.

[0199] It can be initiated for beam fault recovery, other SI requests, SCell addition and / or handover. Figure 13B The contention-free random access procedure is illustrated. For example, the base station may indicate or assign a preamble to the UE for Msg 1 1321. The UE may receive the preamble indication (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0200] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that this response is an indication of confirmation of the SI request.

[0201] Figure 13C Another two-step random access procedure is shown. (Compared to...) Figure 13A and Figure 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0202] Msg A 1331 can be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar to and / or equivalent to that shown in Msg 3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown is similar to and / or equivalent to Msg 4 1314.

[0203] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13C The two-step random access procedure is used in the UE. The UE may determine whether to initiate a two-step random access procedure based on one or more factors. These one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; cell size; the UE's RRC status; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0204] The UE can determine the radio resources and / or uplink transmission power of the preamble 1341 and / or transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in configuration message 1330. The RACH parameters can indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) for the transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) for the transmission of the transport block 1342 can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0205] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing advanced command; a power control command; an uplink grant (e.g., radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0206] The UE and the base station can exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0207] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling clearance indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a group-shared PDCCH (GC-PDCCH) common to the UE group.

[0208] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include a Modulo-2 appending (or an exclusive OR operation) of the identifier value and the CRC parity bits. This identifier can include the 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0209] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled using a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled using a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., with...). Figure 13AThe Msg 3 shown is similar to Msg 3. Other RNTIs configured by the base station for the UE may include: Configured Scheduling RNTI (CS-RNTI), Transmission Power Control PUCCH RNTI (TPC-PUCCH-RNTI), Transmission Power Control PUSCH RNTI (TPC-PUSCH-RNTI), Transmission Power Control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), etc.

[0210] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 can be used for PDSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

[0211] After scrambling the DCI with RNTI, the base station can process the DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station can map the coded and modulated DCI onto resource elements used for and / or configured for the PDCCH. Based on the DCI payload size and / or the base station's coverage area, the base station can transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. CCEs can include the number of resource element groups (REGs) (e.g., 6). REGs can include resource blocks in OFDM symbols. The mapping of the coded and modulated DCI onto resource elements can be based on the mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0212] Figure 14A An example of a CORESET configuration for the bandwidth portion is shown. A base station can transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode the DCI using one or more search spaces. The base station can configure the CORESET in the time-frequency domain. Figure 14A In the example, the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol in the time slot. The fourth CORESET 1404 appears at the seventh symbol in the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0213] Figure 14B An example of CCE-to-REG mapping for DCI transmission is shown in CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved (e.g., for providing frequency diversity) or non-interleaved (e.g., for facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mappings for different CORESETs. A CORESET can be associated with CCE-to-REG mapping via RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. Antenna port QCL parameters can indicate the QCL information for the demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0214] The base station can transmit an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring period and PDCCH monitoring mode; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set can be predefined and known to the UE. The set of CCEs in the UE-specific search space set can be configured based on the UE's identity (e.g., C-RNTI).

[0215] like Figure 14B As shown, the UE can determine the time-frequency resources of the CORESET based on RRC messages. The UE can determine the CCE-to-REG mapping of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters) based on the CORESET's configuration parameters. The UE can determine the number of search space sets configured on the CORESET (e.g., up to 10) based on RRC messages. The UE can monitor a set of PDCCH candidates based on the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE can determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambling bits of the CRC parity bit of the DCI that match the RNTI value). The UE can process the information contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0216] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0217] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted for the UCI and the number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. If more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the radio device can use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 can occupy between four and fourteen OFDM symbols and can include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

[0218] The base station can transmit configuration parameters for multiple PUCCH resource sets to the UE using, for example, an RRC message. These multiple PUCCH resource sets (e.g., up to four sets) can be configured on the cell's uplink BWP. A PUCCH resource set can be configured with: a PUCCH resource set index; multiple PUCCH resources (e.g., pucch-Resourceid) identified by a PUCCH resource identifier; and / or multiple (e.g., a maximum number) UCI ​​information bits that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is two or fewer, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total length of the UCI information bits is greater than two and less than or equal to the first configuration value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total length of the UCI information bits is greater than the second configuration value and less than or equal to the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0219] After determining a PUCCH resource set from multiple PUCCH resource sets, the UE can determine the PUCCH resources used for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE can determine the PUCCH resources based on the PUCCH resource indicator in the DCI received on the PDCCH (e.g., a DCI with DCI format 1_0 or a DCI for 1_1). The three-bit PUCCH resource indicator in the DCI can indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE can use the PUCCH resource indicated by the PUCCH resource indicator in the DCI to transmit UCI (HARQ-ACK, CSI, and / or SR).

[0220] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as... Figure 1A The mobile communication network 100 shown Figure 1B The mobile communication network 150 shown or any other communication network. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

[0221] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0222] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. This data can be provided to processing system 1508 via, for example, a core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The three layers are SDAP, PDCP, RLC, and MAC. These three layers may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

[0223] After being processed by processing system 1508, data to be transmitted to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0224] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0225] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, wireless device 1502 and / or base station 1504 may have a single antenna.

[0226] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although Figure 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0227] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0228] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or 1526 and / or provide user output data to the aforementioned one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0229] Figure 16AAn exemplary structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; and so on. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, it can be achieved through... Figure 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0230] Figure 16B An exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0231] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

[0232] Figure 16D Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

[0233] A wireless device can receive one or more messages (e.g., RRC messages) from a base station, including configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device can communicate with at least one base station (e.g., two or more base stations in dual connectivity) via these cells. These messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, and RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0234] A timer can begin running once started and continues running until it stops or expires. If a timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). Timers can be used to measure time periods / windows of a process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of these multiple ways of implementing a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window used to receive a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other exemplary implementations for restarting the measurement of a time window can be provided.

[0235] Figure 17 An example of device-to-device (D2D) communication is illustrated, where direct communication exists between wireless devices. In this example, D2D communication can be performed via a sidelink (SL). The wireless devices can exchange sidelink communication via a sidelink interface (e.g., a PC5 interface). A sidelink is distinct from an uplink (where the wireless device communicates to the base station) and a downlink (where the base station communicates to the wireless device). The wireless device and the base station can exchange uplink and / or downlink communication via a user plane interface (e.g., a Uu interface).

[0236] As shown in the diagram, wireless devices #1 and #2 can be within the coverage area of ​​base station #1. For example, both wireless devices #1 and #2 can communicate with base station #1 via the Uu interface. Wireless device #3 can be within the coverage area of ​​base station #2. Base stations #1 and #2 can share the network and jointly provide network coverage. Wireless devices #4 and #5 can be outside the network coverage area.

[0237] Intra-coverage D2D communication can be performed when two wireless devices share a network coverage area. Wireless devices #1 and #2 are both within the coverage area of ​​base station #1. Therefore, they can perform intra-cell D2D communication within the coverage area, designated as sidelink A. Wireless devices #2 and #3 are in the coverage areas of different base stations but share the same network coverage area. Therefore, they can perform inter-cell D2D communication within the coverage area, designated as sidelink B. Partial coverage D2D communication can be performed when one wireless device is within the network coverage area and the other is outside the network coverage area. Wireless devices #3 and #4 can perform partial coverage D2D communication, designated as sidelink C. Out-of-coverage D2D communication can be performed when both wireless devices are outside the network coverage area. Wireless devices #4 and #5 can perform out-of-coverage D2D communication, designated as sidelink D.

[0238] Physical channels can be used to configure sidelink communication, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Feedback Channel (PSFCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Shared Channel (PSSCH). A first radio device can use the PSBCH to send broadcast information to a second radio device. The PSBCH may be similar to the PBCH in some respects. Broadcast information may include, for example, slot format indications, resource pool information, sidelink system frame numbers, or any other suitable broadcast information. A first radio device can use the PSFCH to send feedback information to a second radio device. Feedback information may include, for example, HARQ feedback information. A first radio device can use the PSDCH to send discovery information to a second radio device. The radio device can use the discovery information to signal its presence and / or service availability to other radio devices in the area. A first radio device can use the PSCCH to send sidelink control information (SCI) to a second radio device. The PSCCH may be similar to the PDCCH and / or PUCCH in some respects. Control information may include, for example, time / frequency resource allocation information (RB size, number of retransmissions, etc.), demodulation-related information (DMRS, MCS, RV, etc.), identification information for transmitting and / or receiving wireless devices, process identifiers (HARQ, etc.), or any other suitable control information. The PSCCH can be used to allocate, prioritize, and / or reserve sidelink resources for sidelink transmission. A first wireless device may use the PSSCH to send and / or relay data and / or network information to a second wireless device. The PSSCH may be similar to the PDSCH and / or PUSCH in some respects. Each sidelink channel may be associated with one or more demodulation reference signals. Sidelink operation may utilize sidelink synchronization signals to establish the timing of sidelink operation. A wireless device configured for sidelink operation may, for example, use the PSBCH to transmit a sidelink synchronization signal. The sidelink synchronization signal may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS).

[0239] Sidelink resources can be configured to wireless devices in any suitable manner. Wireless devices can be pre-configured for sidelinks, for example, pre-configured with sidelink resource information. Additionally or alternatively, the network can broadcast system information related to resource pools used for sidelinks. Additionally or alternatively, the network can configure specific wireless devices to have dedicated sidelink configurations. This configuration can identify the sidelink resources to be used for sidelink operation (e.g., configuring sidelink band combinations).

[0240] Wireless devices can operate in different modes, such as an auxiliary mode (which may be referred to as mode 1) or an autonomous mode (which may be referred to as mode 2). Mode selection can be based on the coverage status of the wireless device, the radio resource control status of the wireless device, information and / or instructions from the network, and / or any other suitable factors. For example, if the wireless device is idle or inactive, or if the wireless device is outside network coverage, the wireless device can choose to operate in autonomous mode. For example, if the wireless device is in connected mode (e.g., connected to a base station), the wireless device can choose to operate in auxiliary mode (or operate under the instruction of the base station). For example, the network (e.g., a base station) can instruct connected wireless devices to operate in a specific mode.

[0241] In auxiliary mode, a radio device can request scheduling from the network. For example, the radio device can send a scheduling request to the network, and the network can allocate sidelink resources to the radio device. Auxiliary mode may be referred to as network-assisted mode, gNB-assisted mode, or base station-assisted mode. In autonomous mode, a radio device can select sidelink resources based on measurements within one or more resource pools (e.g., pre-configured or network-allocated resource pools), sidelink resource selections made by other radio devices, and / or sidelink resource usage by other radio devices.

[0242] To select sidelink resources, a wireless device can observe a sensing window and a selection window. During the sensing window, the wireless device can use a pool of sidelink resources to observe SCIs transmitted by other wireless devices. SCIs can identify resources that can be used and / or reserved for sidelink transmissions. Based on the resources identified in the SCIs, the wireless device can select resources within the selection window (e.g., resources different from those identified in the SCIs). The wireless device can then use the selected sidelink resources for transmission.

[0243] Figure 18 An example of a resource pool for sidelink operation is shown. A radio device can operate using one or more sidelink cells. A sidelink cell can include one or more resource pools. Each resource pool can be configured to operate according to a specific mode (e.g., assisted or autonomous). A resource pool can be divided into resource elements. In the frequency domain, each resource element can include one or more resource blocks, such as those referred to as subchannels. In the time domain, each resource element can include, for example, one or more time slots, one or more subframes, and / or one or more OFDM symbols. Resource pools can be contiguous or non-contiguous in the frequency and / or time domains (e.g., including contiguous or non-contiguous resource elements). Resource pools can be divided into overlapping resource pool portions. Resource pools can be shared among one or more radio devices. For example, each radio device can attempt to transmit using different resource elements to avoid collisions.

[0244] Sidelink resource pools can be arranged in any suitable manner. In the diagram, the exemplary resource pool is non-contiguous in the time domain and limited to a single sidelink BWP. In the exemplary resource pool, frequency resources are divided into Nf resource units per time unit, numbered from zero to Nf-1. The exemplary resource pool may include multiple portions that repeat every k time units (non-contiguous in this example). In the diagram, time resources are numbered n, n+1…n+k, n+k+1…etc.

[0245] A wireless device can select one or more resource units from a resource pool for transmission. In an exemplary resource pool, the wireless device selects resource unit (n,0) for sidelink transmission. The wireless device can also select periodic resource units in later portions of the resource pool, such as resource unit (n+k,0), resource unit (n+2k,0), resource unit (n+3k,0), etc. This selection can be based, for example, on the determination that transmission using resource unit (n,0) will not (or is unlikely to) conflict with sidelink transmissions of wireless devices sharing the same sidelink resource pool. This determination can be based, for example, on the behavior of other wireless devices sharing the resource pool. For example, if no sidelink transmission is detected in resource unit (nk,0), the wireless device can select resource unit (n,0), resource (n+k,0), etc. For example, if a sidelink transmission from another wireless device is detected in resource unit (nk,1), the wireless device can avoid selecting resource unit (n,1), resource (n+k,1), etc.

[0246] Different sidelink physical channels can use different resource pools. For example, PSCCH can use a first resource pool, and PSSCH can use a second resource pool. Different resource priorities can be associated with different resource pools. For example, data associated with a first QoS, service, priority, and / or other characteristics can use the first resource pool, and data associated with a second QoS, service, priority, and / or other characteristics can use the second resource pool. For example, the network (e.g., a base station) can configure priority levels for each resource pool, and configured supported services for each resource pool, etc. For example, the network (e.g., a base station) can configure a first resource pool for unicast UEs, a second resource pool for multicast UEs, etc. For example, the network (e.g., a base station) can configure a first resource pool for transmitting sidelink data, a second resource pool for transmitting discovery messages, etc.

[0247] E-UTRA RAN connected to the 5G core (5GC) can support RRC inactivity with characteristics similar to those of NR connected to the 5GC.

[0248] The base station (e.g., an NG-RAN base station) and the UE's RRC layer can support at least one of the following:

[0249] -PLMN selection;

[0250] - Broadcasting system information;

[0251] -Cell reselection mobility;

[0252] - Paging initiated by NG-RAN (RAN paging);

[0253] - RAN-based notification regions (RNAs) managed by NG-RAN;

[0254] - DRX configured by NG-RAN for RAN paging;

[0255] - Establish 5GC-NG-RAN connectivity for the UE (both C / U planes);

[0256] - UE AS context stored in NG-RAN and UE; or

[0257] - Know the NG-RAN of the RNA to which the UE belongs.

[0258] The UE can remain CM-CONNECTED and move within the area configured by the base station without notifying the base station when the UE is in an RRC inactive state in that area (RNA). In the RRC inactive state, the last serving gNB node can maintain the UE context and the NG connections associated with the UE in the serving AMF and UPF. Based on downlink data received from the UPF or downlink UE-associated signaling received from the AMF when the UE is in an RRC inactive state, the last serving gNB can perform paging in the cell corresponding to the RNA, and can send RAN paging to neighboring gNBs via the Xn interface if the RNA includes cells of neighboring gNBs.

[0259] The AMF (Application Management Function) can provide core network auxiliary information to the base station to assist in determining whether the UE can be sent to the RRC inactive state. Core network auxiliary information may include: the registration area configured for the UE; a periodic registration update timer; the UE identity index value; the UE-specific DRX; an indication of whether the UE is configured with a Mobile-Initiated Connection (MICO) mode via the AMF; or expected UE behavior. The base station can use the UE-specific DRX and the UE identity index value to determine the paging timing for RAN paging. The base station can use the periodic registration update timer to configure the periodic RNA update timer. The base station can use expected UE behavior to assist in UE RRC state transition decisions.

[0260] The base station can initiate an RRC connection release procedure to transition the UE's RRC state from RRC connected state to RRC idle state, from RRC connected state to RRC inactive state, from RRC inactive state back to RRC inactive state when the UE attempts to recover, or from RRC inactive state to RRC idle state when the UE attempts to recover. This procedure can also be used to release the UE and redirect the UE to another frequency. When transitioning the UE's RRC state to RRC inactive state, the base station can provide a pause configuration. The pause configuration can include at least one of the following: recovery identity, RNA configuration, RAN paging loop, or network hop link count (NCC), where RNA configuration can include RNA notification area information or periodic RNA update timer values. When the UE is in RRC inactive state, the base station can use recovery identity (e.g., I-RNTI) to identify the UE context.

[0261] If a UE sends a request to access a gNB other than the last serving gNB, the gNB receiving the request (the receiving gNB) can trigger a UE context retrieval procedure via the Xn interface to obtain the UE context from the last serving gNB, and can also trigger an address indication procedure via the Xn interface, including tunnel information for potential recovery of data from the last serving gNB. After successful UE context retrieval, the receiving gNB can perform slice-aware admission control and become the serving gNB, provided slice information is received. The receiving gNB can also trigger a path switching request via the N2 interface and applicable RRC procedures. After the path switching procedure, the serving gNB can trigger the release of the UE context at the last serving gNB via the Xn interface using a UE context release procedure. If the UE is unreachable at the last serving gNB, the receiving gNB can...

[0262] - Cause any UE-associated Class 1 procedure to fail any AMF-initiated signaling that allows for unsuccessful operations in the corresponding response message; or

[0263] - Trigger the NAS not delivered indication procedure to report to the UE any NAS PDU received from the AMF that has not been delivered.

[0264] If the UE accesses a gNB other than the last gNB and the receiving gNB cannot find a valid UE context, the receiving gNB can establish a new RRC connection instead of restoring the previous RRC connection. If the serving AMF changes, the UE context retrieval will also fail, and a new RRC connection will therefore need to be established.

[0265] When a UE leaves a configured RNA, a UE in an RRC inactive state can initiate an RNA update procedure. When receiving an RNA update request from the UE, the receiving gNB can trigger a UE context retrieval procedure to obtain the UE context from the last serving gNB, and can decide whether to send the UE back to the RRC inactive state, move the UE into the RRC connected state, or send the UE to the RRC idle state. In the case of periodic RNA updates, if the last serving gNB decides not to relocate the UE context, the receiving gNB can cause the UE context retrieval procedure to fail and directly send the UE back to the RRC inactive state or the RRC idle state via an encapsulated RRC release message.

[0266] The last serving base station can configure the RNA to a UE in an RRC inactive state. The RNA can cover one or more cells and / or be included in the CN registration area; the UE can periodically send RAN-based notification area updates (RNAU), and can also send them when the UE's cell reselection procedure selects a cell that does not belong to the configured RNA.

[0267] RNA can be configured with:

[0268] -List of residential communities:

[0269] -RAN Area List:

[0270] The base station can provide at least one RAN region ID from the RAN region IDs to the UE, where the RAN region is a subset of or equal to the CN tracking region. The RAN region is specified by a RAN region ID, which consists of a TAC and an optional RAN region code. The base station broadcasts one or more RAN region IDs from system information. The base station can provide different RAN definitions for different UEs.

[0271] The UE can monitor the paging channel for core network (CN) paging when it is in RRC idle state. The UE can also monitor the paging channel for RAN paging when it is in RRC inactive state.

[0272] Base stations can broadcast sidelink SIBs. Sidelink SIBs can include information elements (e.g., resources or frequencies) based on sidelink service type (e.g., sidelink discovery, sidelink communication, or V2X communication) or UE type (e.g., pedestrian or vehicle). These information elements can include at least one of the following:

[0273] Resource pools used for frequency-based reception;

[0274] Resource pools used for frequency-based transmission;

[0275] Exception pool;

[0276] Synchronization information (e.g., a list of frequencies).

[0277] Resource selection and configuration;

[0278] Zone configuration;

[0279] Frequency list information;

[0280] Synchronous reference type;

[0281] Threshold for side link tx prioritization

[0282] List of anchor carrier frequencies;

[0283] The threshold for sidelink tx prioritization;

[0284] Transmission parameters and Channel Busy Rate (CBR) configuration; or

[0285] Package copy configuration.

[0286] A base station can transmit System Information (SI) messages carrying SIBs other than SIB1 on the DL-SCH. A base station can transmit one or more SI messages within a periodically occurring time-domain window called an SI window. One or more SI windows can have the same length and can be configured to not overlap in time. A base station can transmit SI messages multiple times within an SI window. A base station can use the indication in SIB1 to configure any SIB other than SIB1 as cell-specific or region-specific. Cell-specific SIBs are applicable only within the cell providing the SIB, while region-specific SIBs are applicable within a region called an SI region (which includes one or more cells and can be identified by a System Information Region ID).

[0287] The UE may apply the SI acquisition procedure to acquire an SI in the following situations: for example, during cell selection (e.g., upon power-on), during cell reselection, upon returning from outside coverage, after reconfiguration with synchronization completed, after entering the network from another radio access technology (RAT), upon receiving an indication that system information has changed, upon receiving a Public Warning System (PWS) notification, and when the UE does not have a valid version of the stored SIB. When the UE acquires a MIB, SIB1, or SI message in the serving cell and stores the acquired SI, the UE may store one or more of the following (if present): the associated area range; the first PLMN identity in the PLMN identity information list; the cell identity; the system information area ID; and the value label. The UE may use a valid stored version of the SI other than the SI of MIB, SIB1, SIB6, SIB7, or SIB8 after cell reselection, upon returning from outside coverage, or after receiving an SI change indication.

[0288] The network can use sidelink configuration parameters to configure sidelink services (e.g., D2D or V2X). More specifically, network entities of the network can use sidelink configuration parameters to configure sidelink services. For example, the network entity can be a V2X control function, a Proximity Service (ProSe) control function, or a Policy Control Function (PCF). The network can send sidelink configuration parameters to the UE via a base station. Sidelink configuration parameters can include configuration parameters for sidelink provisioning, sidelinks on the PC5, and sidelinks on the Uu interface. Alternatively, or as an alternative to the network providing sidelink configuration parameters to the UE, the sidelink configuration parameters can be pre-configured in the UE, configured in the Subscriber Identity Module (SIM), or any combination of these technologies. Sidelink configuration parameters can include the sidelink control function address and parameters for PDN connection (and / or PDU session) for communicating with the sidelink control function. Sidelink configuration parameters for sidelinks on the PC5 can include at least one of the following: authorization policy, radio parameters for the sidelink on the PC5, or other configuration parameters (or policies). Authorization policies can include at least one of the following:

[0289] - A list of PLMNs in which the UE is authorized to use the sidelink on PC5 when the UE is served by a base station; or

[0290] - An indication of whether the UE is authorized to use the side link on PC5 when the UE is not being served by the base station.

[0291] Radio parameters may include radio parameters with geographic area usage restrictions. When the UE reliably locates itself in the corresponding geographic area where the radio parameters are to be used, the UE can use the radio parameters to perform sidelink services at the PC5 reference point.

[0292] Other configuration parameters (or policies) may include at least one of the following:

[0293] - Mapping of target layer 2 IDs and V2X services (e.g., provider service identifier (PSID) for sidelink applications or intelligent transport system application identifier (ITS-AID)).

[0294] - Mapping of ProSe per-packet priority (PPPP) and packet delay budget (PDB) for sidelink services (autonomous resource selection mode).

[0295] - A list of sidelink services (such as PSID or ITS-AID) for sidelink applications, where the geographic regions require privacy support.

[0296] - Mapping of service type (e.g., PSID or ITS-AID) to sidelink frequencies with geographic regions (get more information).

[0297] - Mapping of service types (e.g., PSID or ITS-AID) to Tx configuration files.

[0298] - A list of sidelink services (such as PSID or ITS-AID) that are allowed to use a specific proSe per packet priority (PPPR) value for a sidelink application.

[0299] Figure 19 An exemplary procedure is illustrated for a UE to obtain radio resources for sidelink service when it is in an RRC idle or RRC inactive state and has sidelink data to be transmitted. The base station may broadcast a Sidelink Service Indicator (SIB) for sidelink service (e.g., D2D or V2X). The SIB for sidelink service (SSB) may indicate a resource pool for sidelink transmission at one or more frequencies. A UE in an RRC idle or RRC inactive state can initiate a procedure to establish an RRC connection based on the Sidelink SIB. If the Sidelink SIB is broadcast by the cell where the UE resides and the valid version of the Sidelink SIB includes a resource pool for sidelink transmission at the UE's desired frequency (or the frequency the UE expects or requires), the UE in an RRC idle or RRC inactive state may not need to execute the procedure to establish an RRC connection for sidelink service. The UE can perform sidelink service using the resource pool at the desired frequency indicated in the Sidelink SIB in the RRC idle or RRC inactive state. If a sidelink SIB is broadcast by the cell where the UE resides, and none of the valid versions of the sidelink SIB include a resource pool for sidelink transmissions at a frequency of concern to the UE (or a frequency the UE desires or requires), the UE can initiate a procedure to establish an RRC connection to request that one or more radio resources from the base station for sidelink service. For example, the UE might need a resource pool on frequency f1. The base station broadcasts a sidelink SIB that includes a resource pool on frequency f2, but not f1. The UE can then initiate a procedure to establish an RRC connection to request that one or more radio resources on frequency f1 for sidelink service.

[0300] Figure 20Two exemplary RRC connection procedures (A and B) are shown. Procedure A is executed by a UE in an RRC idle state, and procedure B is executed by a UE in an RRC inactive state. To establish an RRC connection, the UE can execute a random access procedure and a contention resolution procedure. For the random access procedure as explained above in Figure 13, the UE can send Msg 1 with a random access preamble and receive Msg 2 with a random access response. Upon receiving a random access response, the UE can execute a contention resolution procedure by sending Msg 3 with an RRC request message and receiving Msg 4 with an RRC response message. After establishing an RRC connection, the UE can request radio resources for sidelink services.

[0301] The UE may perform a side-link UE information procedure for at least one of the following purposes:

[0302] - Inform the base station UE whether it is interested in or no longer interested in receiving sidelink data (e.g., for sidelink communication or sidelink discovery, or V2X sidelink communication);

[0303] - Request to assign or release transport resources for a sidelink (e.g., sidelink communication, discovery announcement, or V2X sidelink communication or sidelink discovery gap);

[0304] - Report parameters related to the sidelink (e.g., sidelink discovery from inter-frequency / inter-PLMN cell system information); or

[0305] - The report is the synchronization reference used by the UE for the side link (e.g., V2X side link communication).

[0306] A UE with sidelink capabilities (e.g., sidelink communication, V2X sidelink communication, or sidelink discovery) in an RRC connected state can initiate a sidelink UE information procedure to indicate that the UE is interested in receiving sidelink data (e.g., sidelink communication, V2X sidelink communication, or sidelink discovery) in several situations, including when a connection is successfully established, when the interest changes, or when the PCell is changed to broadcast a sidelink SIB.

[0307] A UE with sidelink capabilities (e.g., sidelink communication, V2X sidelink communication, or sidelink discovery) can initiate a sidelink UE procedure to request the allocation of dedicated resources for concerned (desired or required) sidelink communication transmissions or discovery announcements or V2X sidelink communication transmissions, or to request a sidelink discovery gap for sidelink discovery transmissions or sidelink discovery receptions.

[0308] A UE with the capability to report inter-frequency / PLMN sidelink discovery parameters can initiate a sidelink UE information procedure to report parameters related to sidelink discovery from system information between inter-frequency / PLMN cells.

[0309] When one or more sidelink SIBs do not include resources for transmission, a UE in an RRC idle state that is configured to transmit sidelink data (e.g., for sidelink communication / V2X sidelink communication / sidelink discovery announcement) can initiate a procedure to establish an RRC connection.

[0310] When executing the sidelink UE information procedure, the UE can send a sidelink UE information message to the base station via an uplink dedicated control channel (UL-DCCH) message. The sidelink UE information may include information elements (e.g., resources or frequencies) based on sidelink service type (e.g., sidelink discovery, sidelink communication, or V2X communication) or UE type (e.g., pedestrian or vehicle). These information elements may include at least one of the following:

[0311] One or more frequencies of interest for reception via a side link;

[0312] For one or more resource requests transmitted via a side link, wherein the resource request may include at least one of the following: one or more frequencies, or one or more target identities;

[0313] One or more frequencies to be reported;

[0314] QoS information (e.g., reliability) of the sidelink to be transmitted; or

[0315] Synchronous reference type.

[0316] When the UE is in RRC connection state, the base station can provide dedicated configurations for the sidelink. Dedicated configurations for the sidelink can include at least one of the following:

[0317] Mode selection information;

[0318] The configuration of the scheduled mode;

[0319] UE selected mode configuration:

[0320] Frequency list information;

[0321] Synchronous reference type;

[0322] The threshold for sidelink tx prioritization;

[0323] Transmission parameters and Channel Busy Rate (CBR) configuration;

[0324] Package duplicate configuration; or

[0325] Synchronization information (e.g., a list of frequencies).

[0326] The configuration of the scheduled mode may include at least one of the following:

[0327] Sidelink Radio Network Temporary Identifier (RNTI);

[0328] MAC configuration of the side link;

[0329] Scheduling pool information for measured values;

[0330] Modulation and coding scheme (MCS); or

[0331] Logical channel group information list.

[0332] The configuration of the UE's selected mode may include at least one of the following:

[0333] Dedicated resource pool;

[0334] Sensing configuration;

[0335] Carrier selection configuration;

[0336] Figure 21 An exemplary procedure is illustrated for a UE to obtain sidelink radio resources from a base station in an RRC connection state. After an RRC connection is established between the UE and the base station, the UE can request sidelink radio resources by sending a sidelink UE information message to the base station. The base station can provide the UE with a dedicated configuration for sidelink services based on the sidelink UE information message. This dedicated configuration may include at least one of the following: a scheduled mode configuration, or a UE-selected mode configuration. The UE-selected mode configuration may include at least one of the following dedicated resource configurations (e.g., a resource pool).

[0337] In NR, System Information (SI) can include a MIB and multiple SIBs. SIBs are divided into Minimal SIs and Other SIs. Minimal SIs can include basic system information required for initial access and information for obtaining other SIs. Minimal SIs can include a MIB and SIB1. Other SIBs can be broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (e.g., upon request from a UE in an RRC idle or inactive state), or sent in a dedicated manner on the DL-SCH to a UE in an RRC connected state. SIB1 can include information about the availability and scheduling of other SIBs (e.g., SIB-to-SI message mapping, periodicity, and SI window size), indicating whether one or more SIBs are provided on demand, and the configuration required for the UE to perform an SI request in this case.

[0338] Figure 22 An exemplary procedure is shown for a UE to retrieve SIBs other than SIB1 while in an RRC idle or RRC inactive state. The UE may not have valid versions of the SIs for other SIBs in its stored SIBs. The base station may provide SI broadcast status information in SIB1 indicating whether other SIBs are being broadcast. When the SI broadcast status in SIB1 is set to "not broadcasting," a UE in an RRC idle or RRC inactive state can execute an SI request procedure (e.g., a 2-step or 4-step SI request procedure) to retrieve SIs. A UE in an RRC idle or RRC inactive state can retrieve SI messages that include other SIBs.

[0339] Figure 23 An exemplary procedure is shown, executed by the UE, to select between a 2-step SI request procedure and a 4-step SI request procedure for obtaining an SIB other than SIB1. SIB1 may include an SI request configuration. The SI request configuration may include a PRACH preamble and PRACH resources corresponding to the SI message. When SIB1 includes an SI request configuration corresponding to the SIB the UE wishes to obtain, a UE in an RRC idle or RRC inactive state may execute the 2-step SI request procedure. Otherwise, a UE in an RRC idle or RRC inactive state may execute the 4-step SI request procedure to obtain the SIB the UE wishes to obtain.

[0340] Figure 24 Exemplary SI request signal flows are shown for a 2-step SI request procedure (signal flow A) and a 4-step SI request procedure (signal flow B). For the 2-step SI request procedure, the UE can determine the PRACH preamble and PRACH resources corresponding to the desired SIB in the SI request configuration received via SIB1. The UE can use the PRACH preamble and PRACH resources to initiate a random access procedure. Upon receiving the PRACH preamble, the base station can broadcast the desired SIB on the DL-SCH and send an acknowledgment (Ack) for the SI request to the UE. Upon receiving this acknowledgment, the UE in an RRC idle state or an RRC inactive state can acquire the broadcast SIB on the DL-SCH. For the 4-step SI request procedure, the UE can initiate the transmission of an RRC system information request message. The RRC system information request message can include a list of one or more SIBs that the UE expects to acquire. The UE can send the RRC system information request message after the random access procedure has successfully completed, such as... Figure 24 As shown in the diagram. Upon receiving an RRC System Information Request message, the base station can send one or more SIBs and an acknowledgment (Ack) for the SIB request to the UE. Upon receiving the acknowledgment, the UE in RRC idle or RRC inactive state can obtain the requested SIB.

[0341] Figure 25 Two exemplary procedures are illustrated for a UE to acquire one or more SIBs in an RRC-connected state. In the first exemplary procedure (option 1), the UE in the RRC-connected state can receive the one or more SIBs from dedicated signaling from the base station (e.g., via an RRC reconfiguration message). In the second exemplary procedure (option 2), the UE in the RRC-connected state can send an SI request message for the one or more SIBs to the base station. The base station can then send the one or more SIBs to the UE in an RRC message based on the SI request message.

[0342] In existing technology, a base station can provide a sidelink SIB. In one example, the sidelink SIB may indicate radio resources (e.g., a resource pool) for sidelink transmission at a certain frequency. In another example, the sidelink SIB may not indicate radio resources for sidelink transmission. When the sidelink SIB does not indicate radio resources (e.g., a resource pool) for sidelink transmission at a certain frequency of the UE (or a frequency desired or required by the UE), the UE may send a request for sidelink configuration parameters. A UE in an RRC idle or RRC inactive state may require an RRC connection to send this request and perform the actions discussed above. Figure 20 The procedure for establishing an RRC connection is shown below. In the prior art, a UE in an RRC connection state can send a sidelink UE information message to request the procedures described above. Figure 21 The sidelink configuration parameters are shown in the diagram. Based on the sidelink UE information message, the base station can provide the sidelink configuration parameters via dedicated signaling (e.g., RRC reconfiguration message). When the UE is in an RRC inactive or RRC idle state, the procedure for receiving the sidelink configuration parameters may unnecessarily increase the latency, signaling overhead, and UE power consumption for initiating sidelink services. In the prior art, sidelink communication experiences increased latency, for example, when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission. Exemplary embodiments reduce the communication latency of sidelink communication. Exemplary embodiments enable sidelink communication with lower sidelink communication latency for UEs in an RRC idle or RRC inactive state. For example, when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission, the latency from when the UE is in an RRC idle or RRC inactive state until the UE receives the sidelink configuration parameters and / or transmits the sidelink packet is reduced. The exemplary implementation makes it possible for a UE in an RRC inactive or RRC idle state to receive sidelink configuration parameters without establishing or restoring an RRC connection when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission.

[0343] In an exemplary implementation, the UE can transmit a first request for RRC connection and a second request for sidelink configuration parameters in Msg3. This reduces the latency for the UE to indicate to the base station that it needs sidelink configuration parameters. For a UE in RRC idle state, the base station can transmit an RRC setup request message including sidelink configuration parameters to the UE. For a UE in RRC inactive state, the base station can transmit an RRC recovery request message including sidelink configuration parameters to the UE. This reduces the waiting time for receiving configuration parameters from the base station compared to the prior art. The exemplary implementation may increase the initial Msg3 size and / or Msg4 message size and initial signaling overhead; however, for example, when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission, the exemplary implementation reduces the sidelink configuration latency and sidelink packet transmission latency for UEs in RRC idle or RRC inactive states. For example, the request may be a bit indication of using sidelink configuration parameters stored in the UE's UE (inactive) context. This bit indication may be a setup reason. When the UE is in RRC idle or RRC inactive state, the base station can store the UE's sidelink configuration parameters in the UE (inactive) context. An exemplary implementation reduces the size of Msg 3 based on this one-bit indication and the configuration parameters stored in the UE context. In the example, the request may include sidelink UE information or sidelink bearer information. The UE can indicate specific radio resources or specific radio bearers for the sidelink based on this request. Based on this request, the base station can provide configuration parameters for specific radio resources. The exemplary implementation avoids wasting radio resources used for the sidelink based on the sidelink UE information.

[0344] In an exemplary implementation, to reduce the waiting time for obtaining configuration parameters for sidelink services, the UE may determine to send a request for sidelink configuration parameters via MSG 3 or MSG 5 when sending an RRC request message or an RRC completion message. This request may include at least one of the following: sidelink radio resource request information, sidelink quality of service (QoS) information, or UE type information (e.g., vehicle UE or pedestrian UE). The request may be a sidelink UE information message as specified above. The RRC request message may be an RRC setup request message, an RRC recovery request message, or an RRC re-establishment request message. The RRC completion message may be an RRC setup completion message, an RRC recovery completion message, or an RRC re-establishment completion message. Uplink common control channel (UL-CCCH) messages may include at least one of the following: an RRC request message, or a UL-CCCH message sent via signaling radio bearer 0 (SRB0).

[0345] In this disclosure, the sidelink UE information message can be sidelink UE information.

[0346] The UE may require additional uplink grants to send a request for sidelink configuration parameters and an RRC request message in MSG 3. The UE can send MSG 1, including a random access preamble, to the base station. The random access preamble can be dedicated to the sidelink and configured by the base station for the UE. Based on the random access preamble, the base station can send MSG 2 to the UE, which includes a response to the random access preamble, where the response may include uplink grants. Based on the random access preamble, the base station can provide additional uplink grants to accommodate a request for sidelink configuration parameters and an RRC request message in MSG 3. Based on this response, the UE can send MSG 3, which includes an RRC request message and / or a request for sidelink configuration parameters. The RRC request message may include a request for sidelink configuration parameters. Based on the uplink grant in the response, the UE can determine which message or information MSG 3 includes. For example, the UE can determine to use an uplink grant to send an RRC request message. Based on the remaining grants, the UE can determine to send the request in MSG 3. RRC request messages may include the UE identity, where RRC setup request messages may include the Serving Temporary Mobile Subscriber Identity (S-TMSI), and RRC recovery request messages may include the recovery identity.

[0347] Based on a request for sidelink configuration parameters, the base station can provide the UE with the sidelink configuration parameters via an RRC response message or an RRC reconfiguration message in MSG 4. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for the configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE can communicate via the sidelink. The RRC response message may be an RRC setting message, an RRC recovery message, or an RRC re-establishment message.

[0348] In the existing technology, when the UE is in RRC connection state, the base station can receive the UE's sidelink authorization information from the AMF. Figure 26An example of a procedure for a base station to receive sidelink authorization information from the AMF is shown. Based on the receipt of MSG 4, which includes a response to an RRC request message, the UE can enter the RRC connected state. The UE can send MSG 5, which includes an RRC completion message, which may include a NAS message, where the RRC completion message can be an RRC setup completion message or an RRC recovery completion message, and the NAS message can be a registration request message or a service request message. The NAS message may include the UE's sidelink capabilities. Based on the NAS message in MSG 5, the base station can send an initial UE message to the AMF including the NAS message. Based on the NAS message, the AMF can send an initial context setting request to the base station including a sidelink authorization information element (IE). The sidelink authorization information may include sidelink authorization for one or more service types (e.g., vehicle UE, pedestrian UE, and / or ProSe service). Based on the received sidelink authorization information, the base station can store the sidelink authorization information in the UE's UE context. The base station may need the NAS message sent by the UE to trigger the AMF to provide sidelink authorization information to the base station. In the prior art, the procedure for receiving sidelink authorization information may increase the waiting time. The exemplary implementation reduces the waiting time for receiving sidelink authorization information from the AMF. Based on the reduced waiting time for receiving sidelink authorization information, the exemplary implementation also reduces the waiting time in the UE for initiating sidelink communication and / or receiving sidelink configuration parameters.

[0349] In an exemplary implementation, the base station can receive Msg 3 from the UE, where Msg 3 includes a first request for Radio Resource Control (RRC) connectivity and a second request for sidelink configuration parameters. The base station can send a sidelink grant request to the AMF even without having the UE's sidelink grant information. This reduces the delay in the base station instructing the AMF that it needs the UE's sidelink grant information. Based on the sidelink grant request, the AMF can provide the base station with sidelink grant information. Based on the sidelink grant information, the base station can provide the UE with Msg 4, where Msg 4 includes sidelink configuration parameters. This reduces the waiting time in the UE for receiving configuration parameters and initiating sidelink communication.

[0350] Figure 27This is an exemplary illustration of an enhanced procedure for obtaining sidelink configuration parameters according to an embodiment of this disclosure. The base station may broadcast a sidelink SIB. The sidelink SIB may not include radio resources (e.g., a resource pool) for sidelink transmission at a frequency of concern to the UE (or a frequency desired or required by the UE). Based on the sidelink SIB, when the UE is in an RRC idle or RRC inactive state, the UE may execute a procedure to establish an RRC connection. The UE may send an RRC request message to the base station. Based on the RRC request message (RRC recovery request message) in the RRC inactive state, the base station may execute a procedure to retrieve the UE context via the Xn interface to obtain the UE context from the UE's last serving base station. The base station may have the UE's sidelink authorization information in the UE context. The sidelink authorization information may include sidelink authorization for one or more service types. Based on the sidelink authorization information and a request for sidelink configuration parameters, the base station may provide the sidelink configuration parameters via an RRC response message in MSG 4. Based on the sidelink configuration parameters, the UE may communicate via the sidelink.

[0351] exist Figure 27In the example, when receiving an RRC request message and a request for configuration parameters, the base station may not have the UE's sidelink authorization information in the UE's UE context. For example, when the UE is in an RRC idle state, the base station may not have the UE context. When the UE is in an RRC inactive state, the base station may not have the UE's sidelink authorization information in the UE's UE context. Based on the RRC request message (RRC recovery request message) in the RRC inactive state, the base station can perform a UE context retrieval procedure via the Xn interface to obtain the UE context from the last serving base station. After obtaining the UE context, the base station may not have the UE's sidelink authorization information in the UE's UE context. Based on the base station not having the UE's sidelink service authorization information, the base station can perform a sidelink authorization request procedure by sending a sidelink authorization request for the UE to the AMF. The sidelink authorization request may include at least one of the following: the UE identity used to request sidelink authorization or one or more sidelink service types. NG Application (NGAP) messages may include sidelink authorization requests. For example, an NGAP message may include an indication to request service authorization. The base station may store the UE identity in the UE context, where the UE identity may be an S-TMSI. The AMF can use the UE identity to identify the UE. The sidelink grant request message may include the NGAP protocol identity (ID) instead of the UE identity. The sidelink service type may indicate at least one of the following: UE type (e.g., vehicle UE or pedestrian UE), broadcast type (e.g., unicast, multicast, or broadcast), and service type (e.g., communications, discovery, V2X, or ProSe). Based on the sidelink grant request message, the AMF can send a sidelink grant response to the base station including the UE's sidelink grant information. The sidelink grant information may include sidelink grants for one or more service types. Based on the sidelink grant information and a request for configuration parameters, the base station may provide the sidelink configuration parameters via an RRC response message in MSG 4, where the RRC response message may be an RRC setting message or an RRC recovery message. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for the configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE can communicate via the sidelink.

[0352] In an exemplary implementation, the UE may not transmit a second request for sidelink configuration parameters in Msg 3. For example, based on insufficient uplink clearance for Msg 3, the UE may not transmit a second request for sidelink configuration parameters in that Msg. The UE may transmit Msg 5 including the second request. This reduces the delay in the UE instructing the base station that it needs sidelink configuration parameters. The base station may transmit an RRC response message to the UE, which is one of the following: an RRC setup message; or an RRC recovery message. Based on the RRC response message, the UE may transmit an RRC completion message to the base station including the second request, wherein the RRC completion message is one of the following: an RRC setup completion message; or an RRC recovery completion message. The base station may transmit an RRC completion response message including sidelink configuration parameters, wherein the RRC completion response message is one of the following: an RRC reconfiguration message; or an RRC release message. Exemplary implementations may increase the size of Msg 5 and / or the size of the RRC completion response message and initial signaling overhead; however, for example, when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmissions, exemplary implementations reduce the sidelink configuration latency and sidelink packet transmission latency for UEs in an RRC idle or RRC inactive state.

[0353] In an exemplary implementation, the UE may send Msg 3, which includes an indication requesting more uplink permission for Msg 5 transmission. Based on this indication, the base station may send more uplink permission to the UE. Based on this more uplink permission, the UE transmits Msg 5, which includes a second request for configuration parameters for the sidelink. The base station may provide the configuration parameters to the UE. Compared to the prior art, the exemplary implementation enables sidelink communication with lower sidelink communication latency for the UE.

[0354] Figure 28This is an exemplary illustration of an enhanced procedure for obtaining sidelink configuration parameters according to an embodiment of this disclosure. When the UE is in an RRC idle or RRC inactive state, the UE can execute a procedure to establish an RRC connection. The UE can send MSG 1, which includes a random access preamble, to the base station. Based on the random access preamble, the base station can send MSG 2 to the UE, which includes a response to the random access preamble, wherein the response may include uplink grant. Based on the response, the UE can send MSG 3, which includes an indication that the UE has sidelink data. This indication may be an establishment reason and is included in an RRC request message. Based on MSG 3, the base station can send MSG 4. Based on this indication, the base station can provide additional uplink grant to accommodate a request for sidelink configuration parameters and an RRC completion message in MSG 5. Based on this response, the UE can send MSG 5, which includes an RRC completion message and / or a request for sidelink configuration parameters. The RRC completion message may include a request for sidelink configuration parameters. Based on the uplink grant in the response, the UE can determine which message or information MSG 5 includes. For example, the UE can determine to use the uplink grant to send an RRC completion message. Based on the remaining grant, the UE can determine to send a request in MSG 5. The base station may have the UE's sidelink grant information in the UE context, or from the above regarding... Figure 26 The AMF receives sidelink grant information from the UE. The RRC completion message may include a NAS message. The sidelink grant information may include sidelink grants for one or more service types. Based on the sidelink grant information and a request for sidelink configuration parameters, the base station may provide sidelink configuration parameters via a first RRC reconfiguration message. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE may communicate via the sidelink.

[0355] If the UE has a random access preamble dedicated to the side link, then the UE can perform the above-mentioned... Figure 27 The procedure described above. Otherwise, the UE can execute the above-mentioned procedure. Figure 28 The aforementioned procedure.

[0356] Figure 29This is an example of a procedure that transitions a UE's RRC state between an RRC connected state and an RRC inactive state. The base station can execute an RRC release procedure to transition the UE's RRC state from an RRC connected state to an RRC inactive state. The base station can store uplink (and downlink) configuration parameters in the UE context (or UE inactive context), which are used in the UE's RRC connected state and in uplink (and downlink) suspension signaling or data radio bearers. The base station can send an RRC release message including a suspension configuration (or RRC inactive configuration) to transition the UE's RRC state from an RRC connected state to an RRC inactive state. The suspension configuration can include at least one of the following: identity restoration, RNA notification area (RNA) configuration, or security parameters (e.g., next-hop link count (NCC)). Based on the RRC release message including the suspension configuration, a UE in the RRC connected state can store UE parameter states in the UE context (or UE inactive context), which are used in the RRC connected state and in uplink suspension signaling or data radio bearers. The UE can then enter an RRC inactive state. A UE in an RRC inactive state can perform the above-mentioned actions. Figure 20 The procedure for establishing / restoring an RRC connection, as described in Procedure B, involves the base station executing a procedure that triggers a UE context retrieval via the Xn interface to obtain the UE context from the last serving base station. Based on the UE context, the base station can send an RRC recovery message including uplink configuration parameters. Based on the RRC recovery message, the UE can restore the UE parameters in the UE context and restore all suspended uplink bearers.

[0357] In existing technologies, base stations require sidelink UE information from the UE to provide the UE with sidelink configuration parameters. The amount of data in the sidelink UE information can be large. UEs in an RRC inactive state require an RRC connection to send large amounts of sidelink UE information to the base station. In existing technologies, base stations and UEs may not have a mechanism to manage and efficiently use sidelink configuration parameters (e.g., sidelink bearer configuration) in an RRC inactive state, while simultaneously allowing efficient use of uplink (or downlink) configuration by pausing and resuming / restoring uplink (and / or downlink) bearers or bearer configurations. This inefficient process can unnecessarily increase the waiting time for initiating sidelink services by increasing the waiting time for providing the UE with sidelink configuration parameters (sidelink bearer configuration). Exemplary implementations reduce the waiting time for providing the UE with sidelink configuration parameters. Exemplary implementations reduce the communication waiting time for sidelink communication. Exemplary implementations enable sidelink communication with lower sidelink communication latency for UEs in an RRC inactive state. For example, when the sidelink SIB does not indicate the radio resources that the UE intends to use for sidelink transmission, the delay from when the UE is in an RRC idle state or an RRC inactive state until the UE receives the sidelink configuration parameters and / or the transmission of the sidelink packet is reduced.

[0358] In an exemplary implementation, when a UE's RRC connection is suspended (e.g., the UE is put into an RRC inactive state), the base station and the UE can store the UE's sidelink configuration parameters in the UE (inactive) context. This reduces the signaling overhead of requesting sidelink configuration parameters. When receiving an RRC recovery request message from the UE, the base station can restore the stored sidelink configuration parameters in the UE context. The UE can restore the configuration parameters in the UE context. This reduces the signaling overhead of requesting sidelink configuration parameters compared to the prior art. The exemplary implementation enables the UE to indicate the use of one or more configuration parameters stored in the UE context. A UE in an RRC inactive state can send an RRC recovery request message that includes an indication of the configuration parameters stored in the UE context. This indication can indicate one or more configuration parameters stored in the UE context. The base station can restore these one or more configuration parameters. This reduces the signaling overhead of indicating the configuration parameters the UE intends to use and reduces signaling overhead due to unnecessary configuration parameters.

[0359] Figure 30This is an exemplary illustration of an enhancement procedure for storing sidelink bearer configuration in an RRC inactive state, according to an embodiment of this disclosure. The base station can provide a sidelink bearer configuration for a UE in an RRC connected state. Based on the sidelink bearer configuration, the UE can communicate (transmit or receive sidelink data) via the sidelink. The sidelink bearer configuration can include at least one of the following: the signaling or data radio bearer identity of the sidelink, the QoS information of the sidelink bearer, or radio resources for the sidelink bearer. Radio resources can include at least one of the following: a resource pool, a configured license type 1, or a configured license type 2. The base station can execute an RRC release procedure to change the UE's RRC state from an RRC connected state to an RRC inactive state. The base station can store uplink UE parameters in the UE context (or UE inactive context), which are used for the RRC connected state and the UE's uplink suspended signaling or data radio bearer. The base station can determine whether to store the sidelink bearer configuration in the UE context and / or the suspended sidelink bearer. Based on this determination, the base station can store the UE parameters of the sidelink (e.g., sidelink bearer configuration) in the UE context (or UE inactivity context). Based on this determination, the base station can indicate in the RRC release message that the sidelink bearer configuration is stored in the UE context and / or one or more sidelink bearers are suspended. The base station can include one or more sidelink bearer identities in the RRC release message to indicate that the sidelink bearer is suspended or stored in the UE context. Based on the RRC release message, the UE can store the UE parameters of the sidelink (e.g., sidelink bearer configuration) in the UE context (or UE inactivity context) for use in the RRC connection state. Based on the sidelink bearer configuration, the UE can communicate via the sidelink.

[0360] Figure 31 This is an exemplary illustration of an enhanced procedure for restoring / recovering the sidelink bearer configuration in an RRC inactive state, according to an embodiment of this disclosure. The base station and UE can store the sidelink bearer configuration in the UE context, as described above regarding... Figure 30 As described above, the UE can execute the procedure for establishing an RRC connection, as mentioned above. Figure 20As described in Procedure B. The UE may send a request for configuration parameters of the sidelink in MSG 3. The request for configuration parameters may be sidelink bearer information. MSG 3 or the RRC recovery request message in MSG 3 may include a request for configuration parameters of the sidelink. The sidelink bearer information may include an indication of the sidelink bearers configured in the UE context using the UE. The UE may use the indication per sidelink bearer. For example, the indication may include one or more sidelink bearer identities to indicate one or more sidelink bearers configured in the UE context that the UE intends to restore / restore / modify. For example, the UE may use the indication to request the base station to restore / restore / modify the sidelink bearer configuration of one or more sidelink bearers configured in the UE context. The UE may use the indication for all sidelink bearers configured in the UE context. For example, the UE may use the indication to request the base station to restore / restore / modify the sidelink bearer configuration of all sidelink bearers configured in the UE context. For modification, the indication may include at least one of the following: one or more sidelink bearer identities that the UE intends to modify, and / or the QoS information of the requested sidelink bearers associated with the sidelink bearer identities. Based on the RRC recovery request message, the base station can trigger a UE context retrieval procedure via the Xn interface to obtain the UE context from the last serving base station. Based on the sidelink bearer information in MSG 3, the base station can verify the UE context and the sidelink bearer configuration configured in the UE context. Based on the sidelink bearer information and / or the UE context, the base station can determine the sidelink bearer configuration to provide to the UE. The sidelink bearer configuration may include at least one of the following: the signaling or data radio bearer identity of the sidelink, the QoS information of the sidelink bearer, or the radio resources of the sidelink bearer. The base station can update the sidelink bearer configuration and indicate the update to the UE (e.g., by providing mapping information from the old bearer configuration to update the bearer configuration). The sidelink bearer configuration may also include at least one of the following: the QoS information of the sidelink bearer, or an indication of restoring and / or recovering the configuration of one or more sidelink bearers. For example, the indication of restoration and / or recovery may include the sidelink bearer identity that the base station intends to restore and / or recover. Based on the indication of restoration and / or recovery, the UE can restore and / or recover the sidelink bearer corresponding to the sidelink identity. For example, the indication may be a single bit. Based on this instruction, the UE can restore and / or resume the sidelink bearer configuration configured in the UE context. Based on the sidelink bearer configuration, the UE can communicate via the sidelink.

[0361] Figure 32 It is based on the implementation scheme of this disclosure in conjunction with the relevant provisions. Figure 27 and Figure 31The diagram illustrates an exemplary procedure for obtaining sidelink configuration parameters during RRC inactivity. The base station and UE can store the sidelink bearer configuration in the UE context, as described above. Figure 30 As described above, the UE can execute the procedure for establishing an RRC connection, as mentioned above. Figure 20As described in Procedure B, the UE may send a request for configuration parameters of the sidelink in MSG 3. This request may include at least one of the following: sidelink bearer information and / or a sidelink UE information message. The sidelink UE information message may include sidelink bearer information. Based on the sidelink bearer configuration in the UE context and the sidelink data possessed by the UE, the UE may determine which parameters to include in the request. For example, the UE may include sidelink bearer information to request from the base station one or more sidelink bearers of the sidelink bearer configuration configured in the UE context to restore / restore / modify. The UE may include a sidelink UE information message in the request to request from the base station radio resources for sidelink data not associated with the sidelink bearer configuration in the UE context. The sidelink bearer information may include an indication of the sidelink bearers configured in the UE context. For example, the indication may be information about whether the sidelink data possessed by the UE is associated with the sidelink bearers configured in the UE context. The UE may include an indication based on the fact that all the sidelink data possessed by the UE is associated with the sidelink bearers configured in the UE context. This instruction can include one or more sidelink bearer identities that the UE intends to restore / recover in the sidelink bearers configured in the UE's UE context. Based on the RRC recovery request message, the base station can execute a procedure that can trigger a UE context retrieval via the Xn interface to obtain the UE context from the last serving base station. Based on the sidelink bearer information in MSG 3, the base station can verify the UE context and the sidelink bearer configuration configured in the UE context. Based on the sidelink UE information, sidelink bearer information, and / or UE context, the base station can determine which sidelink bearer configuration to provide to the UE. Based on a request for sidelink configuration parameters, the base station can determine which parameters are included in the sidelink bearer configuration. Based on the sidelink bearer information and / or UE context, the base station can determine which parameters or sidelink bearers in the sidelink bearer configuration configured in the UE's UE context to restore / recover. Based on the sidelink UE information message, the base station can determine which parameters or sidelink bearers of sidelink data that are not associated with the sidelink bearer configuration configured in the UE's UE context to configure. The sidelink bearer configuration may include at least one of the following: the signaling or data radio bearer identity of the sidelink, the QoS information of the sidelink bearer, or the radio resources of the sidelink bearer. The base station may update the sidelink bearer configuration and indicate the update to the UE (e.g., by providing mapping information from the old bearer configuration). The sidelink bearer configuration may also include at least one of the following: the quality of service information of the sidelink bearer, or an indication for restoring and / or recovering one or more sidelink bearers. The indication for restoration and / or recovery may include the sidelink bearer identity that the base station intends to restore and / or recover. Based on the sidelink bearer configuration, the UE may communicate via the sidelink.

[0362] In the prior art, a UE can perform sidelink communication using pre-configured radio resources or a radio resource pool. The UE can perform an RRC re-establishment procedure to re-establish the RRC connection (e.g., based on a radio link failure). The UE can perform a cell selection procedure and select a cell based on that procedure. The base station of the cell can broadcast a sidelink SIB, but this sidelink SIB may not indicate the radio resources the UE intends to use for sidelink transmission. When the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission, the UE can send sidelink UE information after re-establishing the RRC connection. This inefficient procedure can unnecessarily increase the waiting time for initiating sidelink service by increasing the waiting time for providing the UE with sidelink configuration parameters (sidelink bearer configuration). Exemplary embodiments reduce the waiting time for providing the UE with sidelink configuration parameters. Exemplary embodiments reduce the communication waiting time for performing sidelink communication. Exemplary embodiments enable sidelink communication with lower sidelink communication latency for UEs in an RRC connected state.

[0363] In an exemplary implementation, the UE may determine to send a request for sidelink configuration parameters when sending an RRC re-establishment request message. This request may include at least one of the following: sidelink radio resource request information, sidelink QoS information, or UE type information (e.g., vehicle UE or pedestrian UE). The request may be a sidelink UE information message as specified above. This reduces the waiting time for receiving configuration parameters from the base station compared to existing technologies. Exemplary implementations may increase the initial Msg 3 size and / or Msg 4 message size and initial signaling overhead; however, for example, when the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmissions, exemplary implementations reduce sidelink configuration latency and sidelink packet transmission latency for UEs in RRC connected states.

[0364] Figure 33 This is an exemplary illustration of an enhanced procedure for obtaining sidelink configuration parameters in an RRC connected state according to an embodiment of this disclosure. (Related to the above regarding...) Figure 30Similarly, the base station and UE can store the sidelink bearer configuration in the UE context. The UE can perform an RRC re-establishment procedure (e.g., due to a radio link failure). The UE can send MSG 1 to the base station, including a random access preamble. The random access preamble can be dedicated to the sidelink and configured by the base station for the UE. Based on the random access preamble, the base station can send MSG 2 to the UE, which includes a response to the random access preamble, where the response may include an uplink grant. Based on the random access preamble, the base station can provide additional uplink grants to accommodate a request for sidelink configuration parameters and an RRC re-establishment request message in MSG 3. Based on this response, the UE can send MSG 3, which includes an RRC re-establishment request message and / or a request for sidelink configuration parameters. The RRC re-establishment request message may include a request for sidelink configuration parameters. Based on the uplink grant in the response, the UE can determine which message or information MSG 3 includes. For example, the UE can determine to use an uplink grant to send the RRC re-establishment request message. Based on the remaining permissions, the UE can determine whether to send a request in MSG 3. The RRC re-establishment request message may include the UE identity. A request for configuration parameters may include at least one of the following: sidelink bearer information and / or sidelink UE information messages. The UE can determine which parameters from the sidelink bearer configuration and sidelink UE information messages are included in the request. For this determination, the UE can perform the actions described above regarding... Figure 32 The same procedures described above. Based on the RRC Re-establishment Request message, the base station can perform a UE context retrieval procedure via the Xn interface to obtain the UE context from the last serving base station. The base station may have the UE's sidelink grant information in the UE context. The sidelink grant information may include sidelink grants for one or more service types. Based on the sidelink grant information and a request for sidelink configuration parameters, the base station can provide the sidelink configuration parameters via the RRC Re-establishment message in MSG 4. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for the configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE can communicate via the sidelink.

[0365] In the prior art, a UE can use pre-configured radio resources or a radio resource pool to perform sidelink communication. The UE can execute an RRC re-establishment procedure to re-establish the RRC connection (e.g., based on a radio link failure). The UE can execute a cell selection procedure and select a cell based on that procedure. The base station of the cell can broadcast a sidelink SIB, but this sidelink SIB may not indicate the radio resources the UE intends to use for sidelink transmission. When the sidelink SIB does not indicate the radio resources the UE intends to use for sidelink transmission, the UE can send sidelink UE information after re-establishing the RRC connection. When receiving an RRC re-establishment request message and a request for configuration parameters, the base station may not have the UE's sidelink grant information in the UE's UE context. For example, when the UE is in an RRC connected state, the base station may have the UE's UE context but not the UE's sidelink grant information. In the prior art, the base station may need to wait for Msg 5, which includes a NAS message. Based on the NAS message in MSG 5, the base station can send an initial UE message including the NAS message to the AMF. Based on NAS messages, the AMF can send an initial context setting request to the base station, including a sidelink grant information element (IE). The sidelink grant information may include sidelink grants for one or more service types (e.g., vehicle UE, pedestrian UE, and / or ProSe service). Upon receiving the sidelink grant information, the base station can store it in the UE's UE context. The base station may require a NAS message sent by the UE to trigger the AMF to provide sidelink grant information to the base station. In the prior art, the procedure for receiving sidelink grant information may increase latency. Exemplary embodiments reduce the latency for receiving sidelink grant information from the AMF. Based on the reduced latency for receiving sidelink grant information, exemplary embodiments reduce the latency for initiating sidelink communication and / or receiving sidelink configuration parameters in the UE.

[0366] In an exemplary implementation, the base station can receive Msg 3 from the UE, where Msg 3 includes a first request for Radio Resource Control (RRC) connection re-establishment and a second request for sidelink configuration parameters. The base station can send a sidelink grant request to the AMF even without having the UE's sidelink grant information. This reduces the delay in the base station instructing the AMF that it needs the UE's sidelink grant information. Based on the sidelink grant request, the AMF can provide the base station with sidelink grant information. Based on the sidelink grant information, the base station can provide the UE with Msg 4, where Msg 4 includes sidelink configuration parameters. This reduces the waiting time in the UE for receiving configuration parameters and initiating sidelink communication.

[0367] exist Figure 33When receiving an RRC re-establishment request message and a request for configuration parameters, the base station may not have the UE's sidelink authorization information in the UE's UE context. For example, when the UE is in an RRC connected state, the base station may have the UE's UE context but not its sidelink authorization information. The base station can perform a sidelink authorization request procedure by sending a sidelink authorization request for the UE to the AMF. The sidelink authorization request may include at least one of the following: the UE identity used to request sidelink authorization or one or more sidelink service types. NG Application (NGAP) messages may include sidelink authorization requests. For example, an NGAP message may include an indication to request service authorization. The base station may store the UE identity in the UE context, where the UE identity may be an S-TMSI. The AMF may use the UE identity to identify the UE. The sidelink authorization request message may include the NGAP protocol identity (ID) instead of the UE identity. The sidelink service type may indicate at least one of the following: UE type (e.g., vehicle UE or pedestrian UE), broadcast type (e.g., unicast, multicast, or broadcast), and service type (e.g., communications, discovery, V2X, or ProSe). Based on the sidelink grant request message, the AMF can send a sidelink grant response to the base station, including the UE's sidelink grant information. The sidelink grant information may include sidelink grants for one or more service types. Based on the sidelink grant information and a request for configuration parameters, the base station can provide sidelink configuration parameters via the RRC re-establishment message in MSG 4. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for the configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE can communicate via the sidelink.

[0368] Figure 34 This is an exemplary illustration of an enhanced procedure for obtaining sidelink configuration parameters in an RRC connected state according to an embodiment of this disclosure. (Related to the above regarding...) Figure 30Similar to those described above, the base station and UE can store the sidelink bearer configuration in the UE context. The UE can perform an RRC re-establishment procedure (e.g., due to a radio link failure). The UE can send MSG 1 to the base station, including a random access preamble. Based on the random access preamble, the base station can send MSG 2 to the UE, which includes a response to the random access preamble, wherein the response may include an uplink grant. Based on this response, the UE can send MSG 3, which includes an indication that the UE has sidelink data. This indication may be an establishment reason and is included in the RRC re-establishment request message. The request for configuration parameters may include at least one of the following: sidelink bearer information and / or sidelink UE information messages. The UE can determine which parameters of the sidelink bearer configuration and sidelink UE information messages are included in the request. For this determination, the UE can perform the procedures described above regarding... Figure 32 The same procedures described above. Based on the RRC re-establishment request message, the base station can execute a procedure that can trigger a UE context retrieval via the Xn interface to obtain the UE context from the last serving base station. Based on MSG 3, the base station can send MSG 4. Based on this indication, the base station can provide more uplink grants to accommodate a request for sidelink configuration parameters and an RRC re-establishment completion message in MSG 5. Based on this response, the UE can send MSG 5, which includes the RRC re-establishment completion message and / or a request for sidelink configuration parameters. The RRC re-establishment completion message may include a request for sidelink configuration parameters. Based on the uplink grants in this response, the UE can determine which message or information MSG 5 includes. For example, the UE can determine to use uplink grants to send the RRC re-establishment completion message. Based on the remaining grants, the UE can determine to send a request in MSG 5. The base station may have the UE's sidelink grant information in the UE context, or from the above regarding... Figure 26 The AMF receives sidelink grant information from the UE. The RRC re-establishment completion message may include a NAS message. The sidelink grant information may include sidelink grants for one or more service types. Based on the sidelink grant information and a request for sidelink configuration parameters, the base station may provide sidelink configuration parameters via a first RRC reconfiguration message. The sidelink configuration parameters may include at least one of the following: radio resources for the sidelink, or a request from the base station for configuration of radio resources for the sidelink. Based on the sidelink configuration parameters, the UE may communicate via the sidelink.

[0369] If the UE has a random access preamble dedicated to the side link, then the UE can perform the actions described above. Figure 33 The procedure described above. Otherwise, the UE can execute the procedure described above. Figure 34 The aforementioned procedure.

[0370] Figure 33 and Figure 34 Examples of this approach can be applied to handover procedures. The UE can execute a procedure to establish an RRC connection with the target base station. The UE can send a request for sidelink configuration parameters to the target base station. This request can be included in the MSG3 or RRC reconfiguration completion message of the RRC connection procedure. The target base station can identify the UE. Based on the UE identification, the target base station can provide more uplink permissions to accommodate the request. For example, the base station can identify the UE based on receiving a normal random access preamble in response to a PDCCH command. The base station can identify UEs that may require sidelink configuration parameters based on the UE context. Based on the UE context, the base station can determine to send the sidelink configuration parameters to the UE.

[0371] In existing technology, a UE in an RRC connected state can receive one or more SIBs via dedicated signaling from the base station. After an RRC connection is established, a UE in an RRC idle or RRC inactive state can receive the one or more SIBs. A UE in an RRC idle or RRC inactive state may need to wait for an RRC connection to be established before receiving the one or more SIBs. This can increase the waiting time for initiating sidelink services. Figure 35 An example of the latency for acquiring radio resources used for sidelink services is shown. Figure 35 As shown, the UE can execute a procedure to establish an RRC connection. After activating security by executing a secure mode command procedure, the base station can provide one or more SIBs to the UE in an RRC reconfiguration message. The UE can send an SI request message to the base station to signal to the base station that the one or more SIBs are provided to the UE. The exemplary implementation reduces the waiting time for receiving the one or more SIBs (e.g., sidelink SIBs).

[0372] In an exemplary implementation, the UE may determine to send a request for configuration parameters for the sidelink via MSG3 or MSG5 when sending an RRC request message or an RRC completion message. This request may include the sidelink UE information message specified above. The request may include information requesting a sidelink SIB. The information requesting the sidelink SIB may be an RRC system information request message or an indication. This indication may be a reason for establishment. For example, the reason for establishment may be one of sidelink, sidelink request, or sidelink SIB request. This reduces the waiting time for obtaining the sidelink SIB compared to existing technologies.

[0373] In an exemplary implementation, the UE may require additional radio resources for the uplink (uplink license) of MSG 3. The UE may send a dedicated random access preamble in MSG 1 of the RRC connection procedure to request licenses for additional radio resources to accommodate the RRC request message and the request. The base station may configure the dedicated random access preamble for sidelink service via broadcast signaling or dedicated signaling. The exemplary implementation enables the UE to transmit requests for sidelink configuration parameters in MSG 3 of the RRC connection procedure.

[0374] In an exemplary implementation, the UE may require more radio resources for the uplink (uplink license) of MSG 5. The UE may send an indication in MSG 3 of the RRC connection procedure that the UE has sidelink data to transmit. This indication may be an establishment reason. For example, the establishment reason may be one of sidelink, sidelink request, or sidelink SIB request. The exemplary implementation enables the UE to transmit a request for sidelink configuration parameters in MSG 5 of the RRC connection procedure.

[0375] Based on this request, the base station can provide sidelink configuration parameters via an RRC response message or an RRC reconfiguration message in MSG 4 of the RRC connection procedure. The sidelink configuration parameters may include a sidelink SIB. The base station can provide the sidelink SIB via a physical message or a MAC PDU. The base station can also provide the sidelink SIB via other messages after the RRC connection is established, where these other messages may be RRC reconfiguration messages or other types of RRC messages. For example, the base station can send an RRC response message along with the sidelink configuration parameters. For example, the base station can include the sidelink configuration parameters in the RRC response message. The base station can also provide the sidelink SIB via a message separate from the RRC response message. This separate message may be a physical message or a MAC message (e.g., a MAC PDU). After receiving the sidelink SIB via a physical message or MAC message without changing the RRC state, a UE in an RRC idle or RRC inactive state can remain in the same RRC state. After receiving an RRC release message, a UE in an RRC idle or RRC inactive state can enter or remain in an RRC idle or RRC inactive state.

[0376] Figure 36An example of enhanced UE behavior for requesting a sidelink SIB according to an embodiment of this disclosure is shown. A UE in an RRC idle or RRC inactive state can send an MSG 3 of the RRC connection procedure to the base station. MSG 3 may include at least one of the following: an RRC request message, or a request for sidelink configuration parameters. The request for sidelink configuration parameters may include information requesting a sidelink SIB. Based on MSG 3, the base station can provide the sidelink configuration parameters. These configuration parameters may include a sidelink SIB.

[0377] In existing technologies, a UE may have sidelink data to be transmitted but not uplink data to be transmitted. Based on the sidelink data, the UE can perform the above-mentioned... Figure 20 The procedure for establishing an RRC connection is described above. Based on sidelink data, a UE in an RRC connection state can send a sidelink UE information message to the base station. Based on the sidelink UE information message, the base station can provide the UE with sidelink configuration parameters, which may include a resource pool. The base station can provide a resource pool for sidelink transmission at all frequencies of concern to the UE (or all frequencies desired or required by the UE). During or after this procedure, the base station may not know which data the UE possesses (e.g., uplink data or sidelink data) to transmit. The base station may unnecessarily establish or maintain an RRC connection while the UE possesses sidelink data instead of uplink data. This procedure may increase the signaling overhead and power consumption of unnecessarily establishing / maintaining RRC connections. Exemplary embodiments reduce the signaling overhead and power consumption of unnecessarily maintaining RRC connections.

[0378] In an exemplary implementation, the UE can send data information to the base station. This data information can indicate that the UE has no uplink data to transmit. A request for configuration parameters of a sidelink or RRC message can include the data information, where the RRC message can be an RRC request message or an RRC completion message. For example, a sidelink UE information message can include data information. Based on the request including the data information, the base station can determine not to establish an RRC connection or to release the RRC connection. This avoids unnecessarily establishing / maintaining an RRC connection.

[0379] A UE in an RRC connection state can send data information to the base station. Based on this data information, the base station can determine to release the RRC connection and send an RRC release message to the UE.

[0380] Data information can indicate at least one of the following:

[0381] The UE has no data to be transmitted (e.g., uplink data or sidelink data);

[0382] The UE has completed sidelink data transmission; or

[0383] The UE does not require radio resources for the side link.

[0384] Figure 37 An example of an enhanced procedure for managing an RRC connection according to an embodiment of this disclosure is shown. The UE may send MSG 3, which includes an RRC request message and a request for sidelink configuration parameters. Based on this request, the base station may determine to provide the UE with radio resources for a sidelink that is permitted for use in an RRC idle or RRC inactive state. The radio resources for the sidelink may include at least one of the following: a resource pool, a configured license type 1, or a configured license type 2. Based on this determination, if the base station does not have downlink data for the UE, it may determine not to establish an RRC connection and send an RRC release message to the UE. The RRC release message may include sidelink configuration parameters. The sidelink configuration parameters may include radio resources for the sidelink. Based on the RRC release message, the UE may enter an RRC idle or RRC inactive state. Based on the configuration parameters, the UE in an RRC idle or RRC inactive state may communicate via the sidelink.

[0385] Figure 38 An example of an enhanced procedure for managing an RRC connection according to an embodiment of this disclosure is shown. The UE may send MSG 5, which includes an RRC completion message and a request for sidelink configuration parameters. Based on this request, the base station may determine to provide the UE with radio resources for a sidelink that is permitted for use in an RRC idle or RRC inactive state. The radio resources for the sidelink may include at least one of the following: a resource pool, a configured license type 1, or a configured license type 2. Based on this determination, and since the base station does not have downlink data for the UE, the base station may determine to release the RRC connection and send an RRC release message to the UE. The RRC release message may include sidelink configuration parameters. The sidelink configuration parameters may include radio resources for the sidelink. Based on the RRC release message, the UE may enter an RRC idle or RRC inactive state. Based on the configuration parameters, the UE in an RRC idle or RRC inactive state may communicate via the sidelink.

[0386] Figure 37 The example of the enhancement program for managing RRC connections can be applied to the above discussion. Figure 36 The enhanced UE behavior for requesting the sidelink SIB. Figure 39An example of an enhanced procedure for managing a sidelink SIB for RRC connection is shown. A UE in an RRC idle or RRC inactive state can send MSG 3 of the RRC connection procedure to the base station. MSG 3 may include at least one of the following: an RRC request message, or a request for sidelink configuration parameters. The request for sidelink configuration parameters may include at least one of the following: a request for information about the sidelink SIB specified above, or a request for information about the sidelink UE information message specified above. This request may include the data information specified above. Based on MSG 3, the base station can provide the sidelink configuration parameters. These configuration parameters may include the sidelink SIB. The base station can provide the sidelink SIB specified above. (The last sentence appears to be incomplete and possibly refers to a different context.) Figure 37 Similarly, based on MSG 3, the base station can determine not to establish an RRC connection and send an RRC release message. For example, the base station can determine to provide a resource pool in the sidelink SIB at the frequency of interest to the UE. Based on this determination, the base station can choose not to establish an RRC connection and send an RRC release message. Based on the RRC release message, the UE can enter an RRC idle or RRC inactive state. Based on the sidelink SIB, a UE in an RRC idle or RRC inactive state can communicate via the sidelink.

[0387] Figure 39 The example of the enhanced procedure for managing RRC connections can be applied to the enhanced UE behavior used to request the sidelink SIB described above. Figure 41 An example of an enhanced procedure for managing a sidelink SIB in an RRC connection is shown. A UE in an RRC connection state can send MSG 5 of the RRC connection procedure to the base station. MSG 5 may include at least one of the following: an RRC completion message, or a request for sidelink configuration parameters. The request for sidelink configuration parameters may include at least one of the following: a request for information about the sidelink SIB specified above, or a request for information about the sidelink UE information message specified above. This request may include the data information specified above. Based on MSG 5, the base station can provide the sidelink configuration parameters. These configuration parameters may include the sidelink SIB. The base station can provide the sidelink SIB specified above. (This is related to the above...) Figure 38 Similarly, based on MSG 5, the base station can determine to release the RRC connection and send an RRC release message. For example, the base station can determine to provide a resource pool in the sidelink SIB at the frequency of interest to the UE. Based on this determination, the base station can determine to release the RRC connection and send an RRC release message. Based on the RRC release message, the UE can enter an RRC idle or RRC inactive state. Based on the sidelink SIB, a UE in an RRC idle or RRC inactive state can communicate via the sidelink.

[0388] In the prior art, a base station can provide sidelink configuration parameters to a UE in an RRC connected state. The sidelink configuration parameters may include at least one of the following: sidelink radio resources, or sidelink bearer configuration. Based on the base station's RRC release message or radio link failure, the UE may enter an RRC idle or RRC inactive state. A UE in an RRC idle or RRC inactive state may be unsure whether to use the configuration parameters. This uncertainty may cause the procedure to send sidelink UE information requesting sidelink configuration parameters. This causes the UE to establish or restore an RRC connection. Exemplary implementations reduce the signaling overhead of sending sidelink UE information and establishing or restoring RRC connections.

[0389] In an exemplary implementation, the base station can provide one or more conditions to verify the validity of the radio resources or sidelink bearer configurations for the sidelink in the configuration parameters. Radio resources can include at least one of the following: a resource pool, a configured license type 1, or a configured license type 2. Configuration parameters can include conditions. These conditions can include at least one of the following: one or more service types for the sidelink, one or more frequencies, duration, or one or more RRC states. These conditions can be associated with one or more radio resources or one or more sidelink bearers. For example, the sidelink service type can indicate at least one of the following: UE type (e.g., vehicle UE or pedestrian UE), broadcast type (e.g., unicast, multicast, or broadcast), and service type (e.g., communications, discovery, V2X, or ProSe). The RRC state can be RRC idle, RRC inactive, or RRC connected. This avoids uncertainty regarding the configuration parameters for the sidelink. Exemplary implementations enable the UE to determine the reuse of configuration parameters within the UE context. For example, based on the configuration parameters, the UE can determine to transmit sidelink data via the radio resources for the sidelink in the configuration parameters. For example, based on conditions associated with radio resources, the UE can determine whether to transmit sidelink data via radio resources. Based on these conditions, the UE can determine which radio resources in the configuration parameters will be used for sidelink transmission. The UE can store the configuration parameters in the UE context. Based on these conditions, the UE can determine whether to remove the radio resource or sidelink bearer configuration of the configuration parameters in the UE context. For example, if the condition is not met, the UE can remove the radio resource or sidelink bearer configuration of the configuration parameters in the UE context. The base station can provide separate conditions for removal. If the removal condition is met, the UE can remove the radio resource or sidelink bearer configuration of the configuration parameters in the UE context. The UE can remove the radio resource or sidelink bearer configuration corresponding to the condition.

[0390] The UE can send an RRC request message to the base station to establish an RRC connection and a request for configuration parameters for the sidelink. In response to the RRC request message and the request, the UE can receive an RRC response message including the sidelink configuration parameters. The UE can communicate via the sidelink based on the configuration parameters. The RRC request message can be an RRC setup request message, an RRC recovery request message, or an RRC re-establishment request message. The uplink common control channel message can include at least one of the following: an RRC request message, or the request itself. The request for sidelink configuration parameters can include at least one of the following: sidelink UE information, or sidelink bearer information. The sidelink UE information can include at least one of the following: sidelink radio resource request information, sidelink quality of service (QoS) information, or UE type information. The sidelink bearer information can include an indication of the sidelink bearer configured in the UE context using the UE. This indication can be the reason for establishing the sidelink. The UE can send a random access preamble dedicated to the sidelink to establish an RRC connection. The UE can determine whether to send the request or the RRC request message based on receiving a response to the random access preamble from the base station. The sidelink configuration parameters may indicate at least one of the following: radio resources for the sidelink, a request for configuration of radio resources for the sidelink to the base station, or a sidelink bearer configuration. The sidelink bearer configuration may include at least one of the following: bearer quality of service information, or an indication for rescuing and / or restoring one or more sidelink bearers. The configuration parameters may indicate at least one of the following: resource pool, configured license type 1, or configured license type 2. The UE may store the sidelink configuration parameters in the UE context. The UE may communicate via the sidelink based on the configuration parameters stored in the UE context. The configuration parameters may include one or more conditions to verify the validity of the radio resources for the sidelink. The UE may determine to transmit sidelink data via radio resources based on one or more conditions. One or more conditions may include at least one of the following: sidelink service type, frequency, duration, or RRC status. The UE may remove the sidelink configuration parameters from the UE context if the one or more conditions are not met. The RRC response message may be an RRC setting message, an RRC recovery message, an RRC release message, or an RRC re-establishment message. Requests for configuration parameters or RRC request messages can indicate that the UE has no uplink data to transmit to the base station, where the RRC response message can be an RRC release message. Requests for configuration parameters or RRC request messages can include requests for sidelink system information. Sidelink configuration parameters can include sidelink system information.

[0391] The base station can receive an RRC request message for establishing an RRC connection and a request for configuration parameters for the sidelink from the UE. In response to the RRC request message and the request, the base station can send an RRC response message including the configuration parameters for the sidelink. The RRC request message can be an RRC setup request message, an RRC recovery request message, or an RRC re-establishment request message. Uplink common control channel messages can include the RRC request message and the request. The RRC response message can be an RRC setup message, an RRC recovery message, an RRC release message, or an RRC re-establishment message. The request for configuration parameters for the sidelink includes at least one of the following: sidelink UE information, or sidelink bearer information. The sidelink UE information can include at least one of the following: sidelink radio resource request information, sidelink quality of service (QoS) information, or UE type information. The sidelink bearer information can include an indication of the sidelink bearer configured in the UE context using the UE. This indication can be the reason for establishing the sidelink. The base station can receive a random access preamble dedicated to the sidelink for establishing an RRC connection. The base station can send a response to a random access preamble, which may include a radio resource / license to accommodate RRC request message and the request. Sidelink configuration parameters may indicate at least one of the following: radio resources for the sidelink, a request for configuration of radio resources for the sidelink to the base station, or sidelink bearer configuration. Sidelink bearer configuration may include at least one of the following: bearer quality of service information, or an indication for rescuing and / or restoring one or more sidelink bearers. The configuration parameter may indicate at least one of the following: resource pool, configured license type 1, or configured license type 2. The base station may store the sidelink configuration parameters in the UE context. The configuration parameters may include one or more conditions for verifying the validity of radio resources for the sidelink. One or more conditions may include at least one of the following: sidelink service type, frequency, duration, or RRC status. A request for configuration parameters or an RRC request message may indicate that the UE has no uplink data to transmit to the base station. Based on this indication, the base station may determine to send an RRC release message to the UE. A request for configuration parameters or an RRC request message may include a request for system information for the sidelink. The configuration parameters for the sidelink may include system information for the sidelink. Based on this request, the base station may send a sidelink authorization request for the UE to the Access and Mobility Management Function (AMF). The sidelink authorization request may include at least one of the following: UE identity, an indication of authorization requested for the sidelink, or one or more sidelink service types requesting sidelink authorization. The base station may receive a sidelink authorization response, wherein the sidelink authorization response may include the UE's sidelink authorization information. Based on this sidelink authorization information, the base station may send configuration parameters to the UE.

[0392] The UE can send an RRC completion message and a request for sidelink configuration parameters to the base station. In response to the RRC completion message and the request, the UE can receive an RRC message including the sidelink configuration parameters. The UE can then communicate via the sidelink based on the configuration parameters. The RRC completion message can be an RRC setup completion message, an RRC recovery completion message, or an RRC re-establishment completion message. The RRC message can be an RRC reconfiguration message or an RRC release message. The request for sidelink configuration parameters can include at least one of the following: sidelink UE information, or sidelink bearer information. The sidelink UE information can include at least one of the following: sidelink radio resource request information, sidelink quality of service (QoS) information, or UE type information. The sidelink bearer information can include an indication of the sidelink bearer configured in the UE context using the UE. The UE can send an RRC request message to the base station. The RRC request message can be an RRC setup request message, an RRC recovery request message, or an RRC re-establishment request message. The RRC request message can indicate that the UE has sidelink data, where the indication can be a reason for sidelink establishment. The UE can determine whether to send an RRC request or an RRC completion message based on a response received from the base station to an RRC request message. This response can be an RRC setup message, an RRC recovery message, an RRC release message, or an RRC re-establishment message. Sidelink configuration parameters can indicate at least one of the following: radio resources for the sidelink, a request for configuration of radio resources for the sidelink to the base station, or a sidelink bearer configuration. Sidelink bearer configuration can include at least one of the following: bearer quality of service information, or an indication for restoring and / or recovering one or more sidelink bearers. This configuration parameter can indicate at least one of the following: a resource pool, a configured license type 1, or a configured license type 2. The UE can store the sidelink configuration parameters in the UE context. The UE can communicate via the sidelink based on the configuration parameters stored in the UE context. These configuration parameters can include one or more conditions to verify the validity of the radio resources for the sidelink. The UE can determine whether to transmit sidelink data via radio resources based on one or more conditions. One or more conditions can include at least one of the following: sidelink service type, frequency, duration, or RRC status. The UE can remove sidelink configuration parameters from the UE context if one or more of these conditions are not met. A request for configuration parameters or an RRC completion message can indicate that the UE has no uplink data to transmit to the base station, where the RRC message can be an RRC release message. The request for configuration parameters or the RRC completion message may include a request for system information for the sidelink. The sidelink configuration parameters may include system information for the sidelink.

[0393] The base station can receive an RRC completion message from the UE and a request for sidelink configuration parameters. In response to the RRC completion message and the request, the base station can send an RRC message including the sidelink configuration parameters. The RRC completion message can be an RRC setup completion message, an RRC recovery completion message, or an RRC re-establishment completion message. The RRC message can be an RRC reconfiguration message or an RRC release message. The request for sidelink configuration parameters can include at least one of the following: sidelink UE information, or sidelink bearer information. The sidelink UE information can include at least one of the following: sidelink radio resource request information, sidelink quality of service (QoS) information, or UE type information. The sidelink bearer information can include an indication of the sidelink bearer configured in the UE context using the UE. The base station can receive an RRC request message from the base station. The RRC request message can be an RRC setup request message, an RRC recovery request message, or an RRC re-establishment request message. The RRC request message can indicate that the UE has sidelink data, where the indication can be the reason for sidelink establishment. The base station can send a response to an RRC request message, which may include a radio resource / license to accommodate RRC completion message and the request, wherein the response may be an RRC setup message, an RRC recovery message, an RRC release message, or an RRC re-establishment message. Sidelink configuration parameters may indicate at least one of the following: radio resources for the sidelink, a request for configuration of radio resources for the sidelink to the base station, or a sidelink bearer configuration. Sidelink bearer configuration may include at least one of the following: bearer quality of service information, or an indication for rescuing and / or restoring one or more sidelink bearers. The configuration parameter may indicate at least one of the following: resource pool, configured license type 1, or configured license type 2. The base station may store the sidelink configuration parameters in the UE context. The configuration parameters may include one or more conditions for verifying the validity of radio resources for the sidelink. One or more conditions may include at least one of the following: sidelink service type, frequency, duration, or RRC status. A request for configuration parameters or an RRC completion message may indicate that the UE has no uplink data to transmit to the base station. Based on this instruction, the base station can determine to send an RRC release message to the UE. Requests for configuration parameters or RRC completion messages may include requests for sidelink system information. Sidelink configuration parameters may include sidelink system information. Based on the sidelink authorization information, the base station can send configuration parameters to the UE.

[0394] Figure 41This is a flowchart illustrating an exemplary embodiment of this disclosure. At 4110, the wireless device transmits a message to the base station. This message includes: a first request for a Radio Resource Control (RRC) connection; and a second request for configuration parameters for the wireless device's sidelink. At 4120, the sidelink configuration parameters are received. At 4130, the wireless device communicates via the sidelink based on the configuration parameters.

[0395] Figure 42 This is a flowchart of an exemplary embodiment of the present disclosure. At 4210, the base station receives a message from the radio device. The message includes: a first request for a Radio Resource Control (RRC) connection; and a second request for configuration parameters of the radio device's sidelink. At 4220, the configuration parameters of the sidelink are transmitted.

Claims

1. A method of sidelink configuration of a wireless device, comprising: transmitting, by a wireless device in a radio resource control (RRC) idle state or an RRC inactive state, a message to a base station, the message comprising: a request for configuration parameters of a sidelink of the wireless device; receiving, by the wireless device in the RRC idle state or the RRC inactive state, the configuration parameters of the sidelink; and communicating via the sidelink based on the configuration parameters.

2. The method of claim 1, wherein the configuration parameters are received in an RRC reconfiguration message or an RRC release message.

3. The method of any one of claims 1 to 2, wherein, communicating via the sidelink comprises communicating via the sidelink based on the configuration parameters during the wireless device is in the RRC idle state or the RRC inactive state.

4. The method of any one of claims 1 to 2, wherein, the message comprises an RRC connection request message, the RRC connection request message comprising one of: an RRC setup request message; or an RRC resume request message.

5. The method of any one of claims 1 to 2, wherein, the configuration parameters of the sidelink comprise one or more radio resources for the sidelink.

6. A wireless device, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of any of claims 1-5.

7. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 1-5.

8. A method of sidelink configuration of a wireless device, comprising: receiving, by a base station from a wireless device in a radio resource control (RRC) idle state or an RRC inactive state, a message, the message comprising: a request for configuration parameters of a sidelink of the wireless device; transmitting, based on the message, the configuration parameters of the sidelink to the wireless device in the RRC idle state or the RRC inactive state. receiving the configuration parameters in an RRC reconfiguration message or an RRC release message.

9. The method of claim 8, wherein, communicating via the sidelink comprises communicating via the sidelink based on the configuration parameters during the wireless device is in the RRC idle state or the RRC inactive state.

10. The method of any one of claims 8-9, wherein, the message comprises an RRC connection request message, the RRC connection request message comprising one of:

11. The method of any one of claims 8 to 9, wherein, an RRC setup request message; or an RRC resume request message. the configuration parameters of the sidelink comprise one or more radio resources for the sidelink.

12. The method of any one of claims 8 to 9, wherein, 13. A base station, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to perform the method of any of claims 8-12.

14. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 8-12.

15. A sidelink configuration system of a wireless device, comprising: ​ ​ A base station comprising one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to: receive, from the wireless device in a radio resource control (RRC) idle state or an RRC inactive state, a message comprising: a request for configuration parameters of a sidelink for the wireless device; transmit, to the wireless device in the RRC idle state or the RRC inactive state, the configuration parameters of the sidelink; and The wireless device, wherein the wireless device comprises one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: transmit, to the base station in the RRC idle state or the RRC inactive state, the message comprising: a request for configuration parameters of a sidelink for the wireless device; receive, by the wireless device in the RRC idle state or the RRC inactive state, the configuration parameters of the sidelink; and communicate via the sidelink based on the configuration parameters.

Images