Inter-UE cooperation for advanced sidelinking

Abstract

To avoid collisions or half-duplex conflicts between sidelink transmissions.SOLUTION: An apparatus for use in mobile communication includes: an antenna used for transmitting electromagnetic signals; a memory for holding a computer readable code; and a processor for executing the computer readable code. The processor causes the apparatus to transmit an indication including at least one of information indicating that a first UE has been designated as a coordinating UE for coordination of sidelink transmissions of a plurality of additional UEs or information identifying the designated coordinating UE, and to transmit one or more group-cast transmission parameters for transmitting the sidelink transmission parameters to the plurality of additional UEs.SELECTED DRAWING: Figure 18

Description

Technical Field

[0001] The present disclosure relates to a mobile communication device and method.

Background Art

[0002] Generally, a computing device and a communication network can be used for information exchange. In general applications, a computing device can request / send data to other computing devices via a communication network. More specifically, a computing device can utilize a wireless communication network to exchange information or establish a communication channel.

[0003] A wireless communication network can include components for accessing the wireless communication network or various types of devices accessing it. Such devices can utilize the wireless communication network to facilitate interaction with other devices that can access the wireless communication network or to facilitate interaction with devices that utilize other communication networks via the wireless communication network.

Summary of the Invention

Means for Solving the Problems

[0004] In some embodiments of the present disclosure, a method of mobile communication including sidelink transmission is provided. The method includes receiving, by a first user equipment (UE), from a base station, an indication that the first UE is a cooperative UE for cooperation with sidelink transmissions of one or more second UEs; receiving, by the first UE, from the base station, one or more groupcast transmission parameters; determining, by the first UE, sidelink transmission parameters for one or more second UEs and for avoiding collisions or half-duplex conflicts between sidelink transmissions of the one or more second UEs; and by the first UE, one or includes sending a groupcast message to a plurality of second UEs, based on one or more groupcast transmission parameters, including sidelink transmission parameters for one or more second UEs.

[0005] In some embodiments of the present disclosure, a method for mobile communication is provided. This method includes: a first user terminal (UE) receiving instructions from a base station that the first UE is associated with one or more coordinating UEs; the first UE receiving groupcast transmission parameters of the first coordinating UE of one or more coordinating UEs from the base station; the first UE receiving a groupcast message from the first coordinating UE, and based on the groupcast transmission parameters, including sidelink transmission parameters for avoiding collisions or half-duplex conflicts for the first UE's sidelink transmission; and the first UE transmitting sidelink data to a second UE based on the sidelink transmission parameters received from the first coordinating UE.

[0006] In some embodiments of the present disclosure, a first UE for a mobile communications network is provided. This first UE has a memory for storing instructions and, by executing those instructions, receives from a base station an instruction that the first UE is a coordinating UE for coordinating sidelink transmissions of one or more second UEs, receives one or more groupcast transmission parameters from the base station, identifies sidelink transmission parameters for one or more second UEs to avoid collisions or half-duplex conflicts between sidelink transmissions of one or more second UEs, and sends one or more groupcast transmission parameters to one or more second UEs. A processor configured to send a groupcast message containing sidelink transmission parameters for one or more second UEs based on a meter, and including

[0007] In some embodiments of the present disclosure, a first UE for a mobile communications network is provided. The first UE includes a memory for storing instructions, and a processor configured to execute those instructions, receive instructions from a base station that the first UE is associated with one or more coordinating UEs, receive groupcast transmission parameters of the first coordinating UE from the base station, receive a groupcast message from the first coordinating UE that includes sidelink transmission parameters for avoiding collisions or half-duplex conflicts relating to the sidelink transmission of the first UE based on the groupcast transmission parameters, and transmit sidelink data to a second UE based on the sidelink transmission parameters received from the first coordinating UE.

[0008] In some embodiments of the present disclosure, a base station is provided for a mobile communications system including sidelink transmission of one or more second UEs. The base station includes a memory for storing instructions and a processor configured to execute the instructions and transmit to a first UE an instruction that the first UE is a coordinating UE or is associated with at least one coordinating UE for coordinating sidelink transmission of one or more second UEs, and transmit one or more groupcast transmission parameters to the first UE, the first UE being configured to transmit sidelink transmission parameters to one or more second UEs based on one or more groupcast transmission parameters.

[0009] In some embodiments of the present disclosure, a system for mobile communications is provided. The system includes a base station configured to transmit to a first UE an instruction that the first UE is a coordinating UE or is associated with one or more coordinating UEs for sidelink transmission; one or more second UEs configured to perform sidelink transmission; and a first UE configured to transmit to one or more second UEs sidelink transmission parameters for one or more second UEs.

[0010] In some embodiments of the present disclosure, a non-temporary computer-readable medium is provided. This non-temporary computer-readable medium is executable by at least one processor of a first user terminal (UE) in a mobile communication system including sidelink transmissions of one or more second UEs and stores a set of instructions causing the first UE to perform a method. This method includes the first UE receiving an instruction from a base station that the first UE is a coordinating UE for the coordination of sidelink transmissions of one or more second UEs; the first UE receiving one or more groupcast transmission parameters from the base station; the first UE receiving one or more sidelink transmission parameters for one or more second UEs to avoid collisions or half-duplex conflicts between sidelink transmissions of one or more second UEs; and the first UE sending a groupcast message to one or more second UEs, and also including sidelink transmission parameters for one or more second UEs based on one or more groupcast transmission parameters.

[0011] In some embodiments of the present disclosure, a non-temporary computer-readable medium is provided. This non-temporary computer-readable medium is executable by at least one processor of a first user terminal (UE) in a mobile communication system including sidelink transmission of one or more UEs, and stores a set of instructions causing the first UE to perform a method. This method involves the first UE receiving an instruction from a base station that the first UE is associated with one or more coordinating UEs, the first UE receiving groupcast transmission parameters of the first coordinating UE of one or more coordinating UEs from the base station, and the first UE The process includes receiving a groupcast message from the first coordinating UE, and based on the groupcast transmission parameters, a groupcast transmission message containing sidelink transmission parameters for avoiding collisions or half-duplex conflicts for the sidelink transmission of the first UE, and the first UE transmitting sidelink data to one or more second UEs based on the sidelink transmission parameters received from the first coordinating UE.

[0012] In some embodiments of the present disclosure, a non-temporary computer-readable medium is provided. This non-temporary computer-readable medium is executable by at least one processor of a base station in a mobile communications system including sidelink transmission of one or more second UEs and stores a set of instructions causing the base station to execute a method. This method includes transmitting to a first UE an instruction that the first UE is a coordinating UE or is associated with at least one coordinating UE for coordinating sidelink transmission of one or more second UEs, and transmitting one or more groupcast transmission parameters to the first UE, the first UE being configured to transmit sidelink transmission parameters to one or more second UEs based on one or more groupcast transmission parameters. [Brief explanation of the drawing]

[0013] [Figure 1] Examples of mobile communication systems according to some aspects of one or more exemplary embodiments of the present disclosure are shown. [Figure 2] Figures 2A and 2B show examples of radio protocol stacks relating to the user plane and control plane, respectively, according to several aspects of one or more exemplary embodiments of the present disclosure. [Figure 3] Figures 3A-3C show exemplary mappings between downlink, uplink, and sidelink logical channels and transmit channels, respectively, in some aspects of one or more exemplary embodiments of the present disclosure. [Figure 4]Figures 4A-4C show exemplary mappings between downlink, uplink, and sidelink transmit channels and physical channels, respectively, in some aspects of one or more exemplary embodiments of the present disclosure. [Figure 5] Figures 5A-5D show examples of radio protocol stacks for NR sidelink communication according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 6] The following are exemplary physical signals for downlink, uplink, and sidelink according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 7] Examples of transitions between different Radio Resource Control (RRC) states are shown in some aspects of one or more exemplary embodiments of this disclosure. [Figure 8] This disclosure shows exemplary frame structures and physical resources in some aspects of one or more exemplary embodiments of this disclosure. [Figure 9] This disclosure illustrates exemplary component carrier configurations for different carrier aggregation scenarios according to several aspects of one or more exemplary embodiments of this disclosure. [Figure 10] This document illustrates exemplary bandwidth portion configurations and switching in some aspects of one or more exemplary embodiments of the present disclosure. [Figure 11] This disclosure illustrates exemplary four-step collision-type and collision-type random access processes according to several aspects of one or more exemplary embodiments of this disclosure. [Figure 12] This disclosure illustrates exemplary two-stage collision-type and collision-type random access processes according to several aspects of one or more exemplary embodiments of this disclosure. [Figure 13] The following illustrates exemplary time-frequency structures of a synchronization signal / physical broadcast channel (PBCH) block (SSB) according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 14] This document illustrates exemplary SSB burst transmissions according to several aspects of one or more exemplary embodiments of the present disclosure. [Figure 15] Exemplary components of a user terminal and a base station for transmission and / or reception according to some aspects of one or more exemplary embodiments of the present disclosure are shown. [Figure 16] Figures 16a and 16b show exemplary collision and half-duplex conflict scenarios between UEs without inter-UE coordination. [Figure 17] Exemplary transmission of auxiliary information by a cooperating user terminal (UE) to transmitting UEs according to some aspects of one or more exemplary embodiments of the present disclosure is shown. [Figure 18] An exemplary inter-UE cooperation process according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 19] An exemplary inter-UE cooperation process according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 20] An exemplary inter-UE cooperation process according to some aspects of one or more exemplary embodiments of the present disclosure.

Embodiments for Carrying out the Invention

[0014] The following disclosure provides many different embodiments or examples for implementing various features of the subject matter provided in this application. Specific arrangement examples are described below for clarity of the present disclosure. These are merely examples and are not to be considered limiting.

[0015] In this specification, terms such as "first", "second", etc. may be used to describe various elements, but these elements should not be limited by these terms. These terms are used to distinguish one element from another. For example, the first element can also be called the second element, and similarly, the second element can also be called the first element, without departing from the scope of its embodiments.

[0016] Figure 1 shows examples of a mobile communication system 100 according to several aspects of one or more exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by wireless communication system operators such as mobile network operators (MNOs), private network operators, multiple system operators (MSOs), and Internet of Things (IOT) network operators, and may provide services such as voice, data (e.g., wireless internet access), message transmission, vehicle-to-vehicle / vehicle-to-infrastructure (V2X) communication services, vehicle driving communication services, safety services, mission-critical services, IoT, industrial IoT (IIOT), and other services in residential, commercial, or industrial environments.

[0017] The mobile communication system 100 can accommodate various types of applications with differing requirements in terms of latency, reliability, throughput, and other aspects. Examples of applicable applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communication (mMTC). eMBB can support high peak data rates and stable connections at appropriate rates for cell-end users. URLLC has stringent latency and reliability requirements, while its data rate requirements can support a moderate range of applications. An exemplary mMTC application would include a network of numerous IoT devices that are only sporadically active and transmit only small data payloads.

[0018] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. The example shown in Figure 1 illustrates a next-generation RAN (NG-RAN) 105 and a 5G core network (5GC) 110 as examples of the RAN and core network, respectively. RAN and Core Network Other examples of RAN can also be implemented without departing from the scope of this disclosure. Another example of RAN is Evolved Universal Terrestrial Radio Access This includes the Network (EUTRAN), Universal Terrestrial Radio Access Network (UTRAN), etc. Other examples of core networks include the Evolved Packet Core (EPC) and the UMTS Core Network (UCN). RAN stands for Radio Access Network. The Technology (RAT) is implemented between the user terminals (UEs) 125 (e.g., UE 125A to UE 125E) and the core network. Such RATs include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), and Universal Mobile Telecommunication System (UMTS). The RAT of an exemplary mobile communication system 100 may be NR. The core network is located between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer configuration, and applications with different QoS (Quality of Services). The functional layer between UEs 125 and the RAN (e.g., NG-RAN 105) may be called the Access Stratum (AS), and the functional layer between UEs 125 and the core network (e.g., 5GC 110) may be called the Non-access Stratum (NAS).

[0019] UEs 125 may include wireless transmitting and receiving means for communication with one or more nodes, one or more relay nodes, or one or more other UEs within a RAN. Examples of UEs 125 include, but are not limited to, smartphones, tablets, laptops, computers, in-vehicle wireless transmitting and / or receiving units, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIoT devices, etc. Other names may also be used for UEs 125, such as Mobile Station (MS:Mobile These include stations, terminal equipment, terminal nodes, client devices, mobile devices, etc. Furthermore, UEs 125 may also include components or subcomponents that are incorporated into other devices such as automobiles to provide wireless communication capabilities with nodes in the RAN as described herein. Such other devices may have other functionalities or multiple functionalities in addition to wireless communication.

[0020] A RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with UEs 125. RAN nodes may be given various names depending on the RAT used for the RAN, for example. A RAN node may be called Node-B (NB) in a RAN using a UMTS RAT. A RAN node may be called Advanced Node B in a RAN using an LTE / EUTRA RAT. In the example of the mobile communication system 100 in Figure 1, the nodes of NG-RAN 105 may be either Next Generation Node B (gNB) 115 (e.g., gNB 115A, gNB 115B) or Next Generation Advanced Node B (ng-eNB) 120 (e.g., ng-eNB 120A, ng-eNB 120B). In this specification, the terms base station, RAN node, gNB, and ng-eNB may be used interchangeably. The gNB 115 may provide NR user plane and control plane protocol termination to the UE 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol termination to the UE 125. The interface between the gNB 115 and the UE 125, or between the ng-eNB 120 and the UE 125, may be called a Uu interface. The Uu interface may be established in the user plane protocol stack and the control plane protocol stack. In the case of a Uu interface, the base station (e.g., gNB 115 or n The direction from g-eNB 120) to UE 125 may be called the downlink, and the direction from UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be called the uplink.

[0021] gNBs 115 and ng-eNBs 120 can be interconnected via an Xn interface. The Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built on Internet Protocol (IP) transport, and may utilize General Packet Radio Service (GPRS). The Radio Service (Radio Service) Tunneling Protocol (GTP) can be used over User Datagram Protocol (UDP) / IP to carry User Plane Protocol Data Units (PDUs). Xn-U can provide unguaranteed transmission of User Plane PDUs and can support data forwarding and flow control. The transport network layer of the Xn-C interface can be built on the Stream Control Transport Protocol (SCTP) over IP. The application layer signaling communication protocol is XnAP (Xn It may be called the Application Protocol. The SCTP layer can provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used for the delivery of signaling PDUs. The Xn-C interface may support Xn interface management, UE mobility management including context forwarding and RAN paging, and dual connectivity.

[0022] gNBs 115 and ng-eNBs 120 can also be connected to 5GC 110 via the NG interface, more specifically to the Access and Mobility Management Function (AMF) 130 (e.g., AFM 130A, AMF 130B) of 5GC 110 via the NG-C interface, and to the User Plane Function (UPF) 135 (e.g., UPF 135A, UPF 135B) of 5GC 110 via the NG-U interface. The transport network layer of the NG-U interface may be built on IP transport, with the GTP protocol used over UDP / IP to carry user plane PDUs between NG-RAN nodes (e.g., gNB 115 or ng-eNB 120) and UPF 135. The NG-U may provide unguaranteed transmission of user plane PDUs between NG-RAN nodes and UPF. The transport network layer of the NG-C interface can be built on top of IP transport. SCTP may be added on top of IP for reliable transmission of signaling messages. The application layer signaling protocol may be called NGAP (NG Application Protocol). The SCTP layer can provide guaranteed transmission of application layer messages. In transport, point-to-point transmission of the IP layer may be used for the transmission of signaling PDUs. The NG-C interface can provide the following functions: NG interface management, UE context management, UE mobility management, NAS message transmission, paging, PDU session management, configuration transmission, and alert message transmission.

[0023] The gNB 115 or ng-eNB 120 may host one or more of the following functions: wireless bearer control, wireless admission control, connectivity mobility control, dynamic allocation of resources to UEs on both uplink and downlink (e.g., scheduling), IP and Ethernet header compression, encryption, and data integrity protection, AMF selection in UE attachments when routing to the AMF cannot be determined from information provided by the UE, routing of user plane data to the UPF, routing of control plane information to the AMF, connection setup and disconnection, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (e.g.) (Issued from AMF), measurement and measurement result reporting settings for mobility and scheduling, transport level packet marking on uplinks, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, delivery function for NAS messages, radio access network sharing, dual connectivity, close interaction between NR and E-UTRA, security maintenance and radio configuration for user plane 5G systems (5GS) cellular IoT (CIoT) optimization.

[0024] The AMF 130 can host one or more of the following functions: NAS signal termination, NAS signaling security, AS security control, CN node inter-signaling for mobility between 3GPP® access networks, idle mode UE reachability (including control and execution of paging retransmission), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights checks, mobility management control (subscriptions and policies), network slicing support, selection of Session Management Function (SMF), and selection of 5GS CIoT optimization.

[0025] UPF 135 may host one or more of the following functions: anchor points for intra- / inter-RAT mobility (where applicable), external PDU session points for interconnection with data networks, packet routing and forwarding, packet inspection and policy enforcement for the user plane portion, traffic utilization reporting, uplink classifiers to support routing of traffic flows to data networks, branching points to support multi-homed PDU sessions, QoS handling for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (mapping service data flows (SDF) to QoS flows), downlink packet buffering and downlink data notification triggering.

[0026] As shown in Figure 1, NG-RAN 105 has two UEs 125 (for example, UE A PC5 interface may be supported between UE 125A and UE 125B. On the PC5 interface, the direction of communication between two UEs (e.g., UE 125A to UE 125B or vice versa) may be called a sidelink. Sidelink transmission and reception on the PC5 interface may be supported when UE 125 is within NG-RAN 105 coverage, regardless of the RRC state of the UE, and when UE 125 is outside NG-RAN 105 coverage. Support for V2X services via the PC5 interface may be provided by NR sidelink communication and / or V2X sidelink communication.

[0027] PC5-S signaling can be used to establish unicast links via direct communication request / accept messages. A UE can self-generate its source Layer-2 ID for a PC5 unicast link, for example, based on the V2X service type. During the unicast link establishment procedure, the UE can send its transmitting Layer-2 ID for the PC5 unicast link to a peer UE, for example, an UE that has received its destination ID from a higher layer. The source Layer-2 ID and destination Layer-2 ID pair can uniquely identify the unicast link. The receiving UE can verify that the destination ID belongs to it and accept the unicast link establishment request from the transmitting UE. During the PC5 unicast link establishment procedure, the PC5-RRC procedure at the access layer may be performed for the purpose of establishing a UE sidelink context, as well as for AS layer configuration, function exchange, etc. PC5-RRC signaling can enable the exchange of UE functions between pairs of UEs that have established a PC5 unicast link, and AS layer configuration such as sidelink radio bearer configuration.

[0028] NR sidelink communication may support one of three transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) for a pair of source Layer-2 IDs and destination Layer-2 IDs within an AS. Unicast transmission mode may be characterized by support for one PC5-RRC connection between peer UEs for that pair, transmission and reception of control information and user traffic between peer UEs in the sidelink, support for sidelink HARQ feedback, support for sidelink transmit power control, support for RLC Acknowledged Mode (AM), and detection of radio link failures related to the PC5-RRC connection. Groupcast transmission is characterized by transmission and reception of user traffic between UEs belonging to that group in the sidelink and support for sidelink HARQ feedback. Broadcast transmission may be characterized by transmission and reception of user traffic between UEs in the sidelink.

[0029] The source Layer-2 ID, destination Layer-2 ID, and PC5 link identifier may be used in NR sidelink communication. The source Layer-2 ID can identify the sender of data in NR sidelink communication. The source Layer-2 ID may be 24 bits long and may be split into two-bit strings at the Media Access Control (MAC) layer, in which case one-bit string is the LSB portion (8 bits) of the source Layer-2 ID and may be transmitted to the sender's physical layer. This can identify the source of the intended data in the sidelink control information and may be used for filtering packets at the receiver's physical layer, in which case the second-bit string may be the MSB portion (16 bits) of the source Layer-2 ID and may be carried in the Media Access Control (MAC) header. This may be used for filtering packets at the receiver's MAC layer. The destination Layer-2 ID can identify the target of data in NR sidelink communication. In NR sidelink communication, the destination Layer-2 ID can be 24 bits long and can be split into 2-bit strings at the MAC layer. In this case, the 1-bit string is the LSB portion (16 bits) of the destination Layer-2 ID and can be transmitted to the sender's physical layer. This can identify the target of the intended data in the sidelink control information and can be used for packet filtering at the receiver's physical layer. In this case, the second bit string can be the MSB portion (8 bits) of the destination Layer-2 ID and can be carried in the MAC header. This can be used for packet filtering at the receiver's MAC layer. The PC5 link identifier can uniquely identify a PC5 unicast link within the UE during the lifetime of the PC5 unicast link. The PC5 link identifier can be used to identify a PC5 unicast link that has been declared a Radio Link Failure (RLF) and whose PC5-RRC connection has been released.

[0030] Figures 2A and 2B show examples of radio protocol stacks for the user plane and control plane, respectively, according to several aspects of one or more exemplary embodiments of the present disclosure. As shown in Figure 2A, the user plane protocol stack for the Uu interface (between UE 125 and gNB 115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, MAC 204 and MAC 214 of layer 2, and layers 205 and PHY 215 (layer 1 is also called L1).

[0031] PHY 205 and PHY 215 provide transport channel 244 to MAC 204 and MAC 214 sublayers. MAC 204 and MAC 214 sublayers provide logical channel 243 to RLC 203 and RLC 213 sublayers. RLC 203 and RLC213 sublayers provide RLC channel 242 to PDCP 202 and PCP 212 sublayers. The sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. The radio bearers can be classified into two groups: Data Radio Bearers (DRBs) for user plane data and Signaling Radio Bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to 5GC.

[0032] The main services and functions of the MAC 204 or MAC 214 sublayer include: mapping between logical channels and transport channels; multiplexing / demultiplexing of MAC service data units (SDUs) belonging to one or different logical channels to / from the physical layer / transport blocks (TBs) propagated from there on the transport channel; scheduling of information reporting; error correction through Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA)); priority handling between UEs through dynamic scheduling; priority handling between logical channels of a single UE through Logical Channel Prioritization (LCP); priority handling between duplicate resources of a single UE; and padding. A single MAC entity may support multiple numerologies, transmission timings, and cells. The mapping of priority decisions within a logical channel controls which numerologies, cells, and transmission timings a logical channel can use.

[0033] The HARQ feature can ensure reliable communication between peer entities at Layer 1. A single HARQ process can support one TB if the physical layer is not configured for downlink / uplink spatial multiplexing, and a single HARQ process can support one or more TBs if the physical layer is configured for downlink / uplink spatial multiplexing.

[0034] The RLC 203 or RLC 213 sublayer may support three transmission modes: Transparent Mode(TM), Unacknowledged Mode(UM), and Acknowledged Mode(AM). The RLC configuration may conform to a logical channel, independent of numerology and / or transmission time, and automatic retransmission requests (ARQs) may operate in any of the numerology and / or transmission time settings of the logical channel.

[0035] The main services and functions of the RLC 203 or RLC 213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include: transmission of higher-layer PDUs, independent sequence numbering within the PDCP (UM and AM), error correction via ARQ (AM only), segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), RLC SDU discard (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0036] An automatic retransmission request within the RLC 203 or RLC 213 sublayer may have the following characteristics: the ARQ retransmits RLC SDUs or RLC SDU segments based on RLC status reports; polling for RLC status reports may be used by the RLC as needed; and the RLC receiver may also trigger an RLC status report after detecting a missed RLC SDU or RLC SDU segment.

[0037] The main services and functions of the PDCP 202 or PDCP 212 sublayer include the following: This includes: data transmission (user plane or control plane), retention of PDCP sequence numbers (SNs), header compression and decompression using the Robust Header Compression (ROHC) protocol, encryption and decryption, integrity protection and integrity verification, SDU discarding using timers, routing for split bearers, redundancy, reordering and in-order delivery, out-of-order delivery, and duplicate discarding.

[0038] The main services and functions of SDAP 201 or SDAP 211 include: mapping between QoS flows and data radio bearers, and marking of QoS flow IDs (QFIs) on both downlink and uplink. One protocol entity of SDAP can be configured for each individual PDU session.

[0039] As shown in Figure 2B, the protocol stack of the control plane for the Uu interface (between UE 125 and gNB 115) includes the PHY layer (layer 1) and the MAC, RLC, and PDCP sublayers of layer 2, as well as the RRC 206 and RRC 216 sublayers. The main services and functions of the RRC 206 and RRC 216 sublayers on the Uu interface include: broadcasting system information about the AS and NAS; paging initiated by 5GC or NG-RAN; establishing, maintaining, and releasing RRC connections between the UE and NG-RAN (including adding, modifying, and releasing carrier aggregations and dual connectivity within the NR or between E-UTRA and NR); security functions including key management; establishing, configuring, maintaining, and releasing SRBs and DRBs; mobility functions (including handover and context transmission, UE cell selection and reselection and control of cell selection and reselection, and Inter-RAT mobility); QoS management functions; UE measurement result reporting and reporting control; detection and recovery from radio link failures; and NAS message transmission from NAS to UE / UE to NAS. The NAS 207 and NAS 227 layers are control protocols that perform functions such as authentication, mobility management, and security control (terminating at the AMF on the network side).

[0040] Sidelink-specific services and functions of the RRC sublayer on the Uu interface include: setting sidelink resource allocation via system information or individual signaling, reporting UE sidelink information, setting and reporting sidelink measurements, and reporting UE support information for SL traffic patterns.

[0041] Figures 3A, 3B, and 3C illustrate exemplary mappings between logical channels and transport channels in downlink, uplink, and sidelink, respectively, according to several aspects of one or more exemplary embodiments of the present disclosure. MACs can provide different types of data transmission services. Each logical channel type can be defined by the type of information being transmitted. Each logical channel can be classified into two groups: control channels and traffic channels. Control channels may be used for transmitting only control plane information. A Broadcast Control Channel (BCCH) is a downlink channel for broadcasting system control information. A Paging Control Channel (PCCH) is a downlink channel for carrying paging messages. A Common Control Channel (CCCH) is a channel for transmitting control information between UEs and the network. This channel may be used by UEs that do not have RRC connectivity to the network. A Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel for transmitting dedicated control information between a UE and the network, and may be used by UEs with RRC connectivity. The traffic channel is user It can be used for transmitting only lane information. A Dedicated Traffic Channel (DTCH) is a point-to-point channel for a single UE (User Entrance) for transmitting user information. DTCHs can exist on both uplinks and downlinks. Sidelink Control Channel (SCCH) A Control Channel (STCH) is a sidelink channel used to transmit control information (e.g., PC5-RRC and PC5-S messages) from one UE to another. A Channel is a sidelink channel for transmitting user information from one UE to another. A Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to another.

[0042] Downlink transport channel types include broadcast channels (BCH), downlink shared channels (DL-SCH), and paging channels (PCH). BCH may be characterized by a fixed, predefined transport format and the requirement to broadcast across the entire cell coverage area, either as a single message or by beamforming different BCH instances. DL-SCH may be characterized by support for HARQ, support for dynamic link modulation adaptation by varying modulation, encoding, and transmit power, the possibility of broadcasting across the entire cell, the availability of beamforming, support for both dynamic and semi-static resource allocation, and support for discontinuous reception (DRX) for reducing UE power consumption. DL-SCH may be characterized by support for HARQ, dynamic link modulation adaptation by varying modulation, encoding, and transmit power, the possibility of broadcasting across the entire cell, the availability of beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to reduce UE power consumption. PCH may be characterized by support for UE discontinuous reception (DRX) enabling UE power consumption reduction (DRX cycles are indicated to the UE by the network), requirements broadcast across the entire cell coverage area as single messages or by beamforming different BCH instances, and mapping to physical resources that can also be dynamically used for traffic / other control channels.

[0043] In the downlink, the following connections may exist between the logical channel and the transport channel: BCCH can be mapped to BCH, BCCH can be mapped to DL-SCH, PCCH can be mapped to PCH, CCCH can be mapped to DL-SCH, DCCH can be mapped to DL-SCH, and DTCH can be mapped to DL-SCH.

[0044] Uplink transport channel types include uplink shared channels (UL-SCH) and random access channels (RACH). UL-SCH may be characterized by beamforming availability, support for dynamic link modulation adaptation by varying transmit power and possibly modulation and coding, HARQ support, and support for both dynamic and semi-static resource allocation. RACH may be characterized by limited control information and collision risk.

[0045] In uplinks, the following connections may exist between the logical channel and the transport channel: CCCH can be mapped to UL-SCH, DCCH can be mapped to UL-SCH. DTCH, which can be pinged, can be mapped to UL-SCH.

[0046] Sidelink transport channel types include: sidelink broadcast channels (SL-BCH) and sidelink shared channels (SL-SCH). SL-BCH may be characterized by a predefined transport format. SL-SCH may be characterized by support for unicast, groupcast, and broadcast transmissions; support for both UE automatic resource selection and scheduled resource allocation by NG-RAN; support for both dynamic and semistatic resource allocation when resources are allocated to the UE by NG-RAN; support for HARQ; and support for dynamic link modulation adaptation by changing transmit power, modulation, and encoding.

[0047] In a sidelink, the following connections may exist between the logical channel and the transport channel: SCCH can be mapped to SL-SCH, STCH can be mapped to SL-SCH, and SBCCH can be mapped to SL-BCH.

[0048] Figures 4A, 4B, and 4C illustrate exemplary mappings between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, according to several aspects of one or more exemplary embodiments of the present disclosure. The physical channels in the downlink include the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH). PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. Transport channels are not mapped to the PDCCH, but Downlink Control Information (DCI) is transmitted via the PDCCH.

[0049] The physical channels of an uplink include the Physical Uplink Shared Channel, the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). UL-SCH transport channels may be mapped to PUCCH, and RACH transport channels may be mapped to PRACH. Transport channels are not mapped to PUCCH, but Uplink Control Information (UCI) is transmitted via PUCCH.

[0050] The physical channels of a sidelink include the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Feedback Channel (PSFCH), and Physical Sidelink Broadcast Channel (PSBCH). The Physical Sidelink Control Channel (PSCCH) may indicate the resources and other transmission parameters that the UE uses for the PSSCH. The Physical Sidelink Shared Channel (PSSCH) may transmit the TBs of data themselves, as well as control information and Channel State Information (CSI) feedback triggers for the HARQ procedure, etc. At least six in the slot Orthogonal Frequency Division Multiplexing (OFDM) symbols may be used for PSSCH transmission. A Physical Sidelink Feedback Channel (PSFCH) can carry HARQ feedback over the sidelink from the intended receiver UE of a PSSCH transmission to the transmitting UE. A PSFCH sequence may be transmitted in a single PRB repeated by two OFDM symbols near the end of the sidelink resource in the slot. An SL-SCH transport channel may be mapped to a PSSCH. An SL-BCH may be mapped to a PSBCH. No transport channel is mapped to a PSFCH, but Sidelink Feedback Control Information (SFCI) may be mapped to a PSFCH. No transport channel is mapped to a PSCCH, but Sidelink Control Information (SCI) may be mapped to a PSCCH.

[0051] Figures 5A, 5B, 5C, and 5D illustrate examples of radio protocol stacks for NR sidelink communication according to some aspects of one or more exemplary embodiments of the present disclosure. The AS protocol stack for the user plane in the PC5 interface (i.e., for the STCH) may consist of the SDAP, PDCP, RLC, and MAC sublayers and the physical layer. The user plane protocol stack is shown in Figure 5A. The AS protocol stack for the SBCCH in the PC5 interface may consist of the RRC, RLC, and MAC sublayers and the physical layer shown below in Figure 5B. To support the PC5-S protocol, as shown in Figure 5C, the PC5-S is above the PDCP, RLC, and MAC sublayers and the physical layer in the control plane protocol stack for the SCCH for PC5-S. The control plane AS protocol stack for the SCCH for the RRC in the PC5 interface consists of the RRC, PDCP, RLC, and MAC sublayers and the physical layer. The control plane protocol stack for the SCCH for the RRC is shown in Figure 5D.

[0052] Sidelink radio bearers (SLRBs) can be classified into two groups: sidelink data radio bearers (SL DRBs) for user plane data and sidelink signaling radio bearers (SL SRBs) for control plane data. Separate SLSRBs using different SCCHs may be configured for PC5-RRC and PC5-S signaling, respectively.

[0053] The MAC sublayer can provide the following services and functions on the PC5 interface: radio resource selection, packet filtering, priority handling between uplink and sidelink transmissions for a given UE, and sidelink CSI reporting. Due to constraints on logical channel priority determination within the MAC, only sidelink logical channels belonging to the same destination can be multiplexed into the MAC PDU for each unicast, groupcast, and broadcast transmission that may be associated with that destination. For packet filtering, an SL-SCH MAC header containing both the source Layer-2 ID and destination Layer-2 ID portions may be added to the MAC PDU. The Logical Channel Identifier (LCID) contained within the MAC subheader can uniquely identify a logical channel within a range of combinations of source Layer-2 ID and destination Layer-2 ID.

[0054] RLC sublayer services and functions may be supported for sidelinks. Both RLC Unacknowledged Mode (UM) and Acknowledged Mode (AM) may be used for unicast transmissions, but only UM may be used for groupcast or broadcast transmissions. In the case of UM, groupcast and For broadcasting purposes, only one-way transmission may be supported.

[0055] The services and functions of the PDCP sublayer on the Uu interface may be supported with some limitations for sidelinking. Specifically, out-of-order delivery can only be supported for unicast transmissions, and redundancy is not supported on the PC5 interface.

[0056] The SDAP sublayer may provide the following services and functions on the PC5 interface: mapping between QoS flows and sidelink data radio bearers. For each destination, there may be one SDAP entity for one of unicast, groupcast, and broadcast associated with that destination.

[0057] The RRC sublayer may provide the following services and functions on the PC5 interface: transmission of PC5-RRC messages between peer UEs, maintenance and release of PC5-RRC connections between two UEs, and detection of sidelink radio link failures related to PC5-RRC connections based on instructions from MAC or RLC. A PC5-RRC connection may be a logical connection between two UEs for a pair of source and destination Layer-2 IDs that is expected to be established after the corresponding PC5 unicast link has been established. There may be a one-to-one correspondence between a PC5-RRC connection and a PC5 unicast link. A UE may have multiple PC5-RRC connections with one or more UEs for different pairs of source and destination Layer-2 IDs. Separate PC5-RRC procedures and messages may be used for a given UE to transmit UE functions and sidelink configurations, including SL-DRB configurations, to a peer UE. Both peer UEs may exchange their respective UE functions and sidelink configurations using separate bidirectional procedures in both sidelink directions.

[0058] Figure 6 shows exemplary physical signals for downlink, uplink, and sidelink in some aspects of one or more exemplary embodiments of the present disclosure. A demodulation reference signal (DM-RS) may be used in the downlink, uplink, and sidelink and may be used for channel estimation. The DM-RS is a UE-specific reference signal and may be transmitted with the physical channel in the downlink, uplink, or sidelink and may be used for channel estimation and coherent detection of the physical channel. A phase tracking reference signal (PT-RS) may be used in the downlink, uplink, and sidelink and may be used for phase tracking and mitigating performance loss due to phase noise. The PT-RS may be used primarily to estimate and minimize the impact of Common Phase Error (CPE) on system performance. Due to the characteristics of phase noise, the PT-RS signal may be low density in the frequency domain and high density in the time domain. PT-RS can occur in combination with DM-RS, and when the network is configured to have PT-RS. Positioning Reference Signals (PRS) can be used for positioning using different positioning techniques on the downlink. PRS can be used to measure downlink transmission delay by correlating the received signal from the base station with a local replica in the receiver. Channel State Information Reference Signals (CSI-RS) can be used on the downlink and sidelink. CSI-RS can be used for channel state estimation, Reference Signal Received Power (RSRP) measurement for mobility and beam management, time / frequency tracking for modulation, and other purposes. CSI-RS can be configured to suit individual UEs, but multiple users may share the same CSI-RS resources. UEs can identify CSI reports and transmit them to the base station on the uplink using PUCCH or PUSCH. CSI reports are transmitted on the sidelink. It can be carried within the link MAC control element (CE). The primary synchronization signal (PSS) and secondary synchronization signal (SSS) can be used for wireless frame synchronization. The PSS and SSS can be used for cell search procedures during initial attachment or for mobility purposes. Sounding reference signal (SRS) The Signal can be used in the uplink for uplink channel estimation. Similar to CSI-RS, SRS can also serve as a QCL reference for other physical channels, thereby establishing a pseudo-colocation relationship with SRS and enabling transmission. Sidelink PSS (S-PSS) and sidelink SSS (S-SSS) can be used in the sidelink for sidelink synchronization.

[0059] Figure 7 shows examples of Radio Resource Control (RRC) states and transitions between different RRC states in some aspects of one or more exemplary embodiments of the present disclosure. The UE may be in one of three RRC states: RRC connected state 710, RRC idle state 720, and RRC inactive state 730. After power-up, the UE may be in RRC idle state 720, and the UE may use initial access to establish a connection with the network via the RRC connection establishment procedure to transmit data and / or send / receive voice calls. Once the RRC connection is established, the UE may be in RRC connected state 710. The UE may transition from RRC idle state 720 to RRC connected state 710, or from RRC connected state 710 to RRC idle state 720, using the RRC connection establishment / release procedure 740.

[0060] The RRC inactive state 730 may be used to reduce the signaling load and latency resulting from frequent transitions from the RRC connected state 710 to the RRC idle state 720 when the UE sends small amounts of data frequently. In the RRC inactive state 730, the AS context can be preserved by both the UE and the gNB. As a result, a fast state transition from the RRC inactive state 730 to the RRC connected state 710 is possible. The UE may transition from the RRC inactive state 730 to the RRC connected state 710, or from the RRC connected state 710 to the RRC inactive state 730, using the RRC connection restart / deactivation procedure 760. The UE may transition from the RRC inactive state 730 to the RRC idle state 720 using the RRC connection release procedure 750.

[0061] Figure 8 shows exemplary frame structures and physical resources according to several aspects of one or more exemplary embodiments of the present disclosure. Downlink, uplink, or sidelink transmissions can be organized into frames with a duration of 10 ms, consisting of 10 (0-9) subframes of 1 ms each. Each subframe may consist of k slots (k=1, 2, 4, ...), where the number of slots k per subframe may depend on the subcarrier interval of the carrier being transmitted therein. Slot durations can be 14 (0-13) symbols of a normally cyclic prefix (CP) and 12 symbols of an extended CP, and time can be expanded or contracted so that there are integer slots within a single subframe, depending on the subcarrier interval used. Figure 8 shows resource grids in the time and frequency domains. Each element of the resource grid, containing one symbol in time and one subcarrier in frequency, is called a resource element (RE). A resource block (RB) can be defined as 12 consecutive subcarriers in the frequency domain.

[0062] In some examples, non-slot-based scheduling allows packet transmission to occur within a portion of a slot, e.g., OFDM symbols 2, 4, or 7, which may also be called minislots. Minislots can be used for low-latency applications such as URLLC and for operation in unlicensed bands. In some embodiments, minislots The lot can also be used for services (e.g., preferred URLLC connections on eMBB) for fast and flexible scheduling.

[0063] Figure 9 shows exemplary component carrier configurations in different carrier aggregation scenarios according to several aspects of one or more exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be bundled together. A UE may transmit and receive simultaneously on one or more CCSs, depending on its capabilities. CA may support both continuous and discontinuous CCs in the same band or in different bands, as shown in Figure 9. The gNG and UE may communicate using a service cell. A service cell may be associated with at least one downlink CC (for example, it may be associated with only one downlink CC, or it may be associated with both a downlink CC and an uplink CC). A service cell may be a primary cell (PCell) or a secondary cell (SCell).

[0064] The UE may adjust the timing of its uplink transmission using an uplink timing control procedure. A timing advance (TA) may be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB may identify the desired timing advance setting and provide it to the UE. The UE may use the provided TA to determine the uplink transmission timing relative to the downlink reception timing observed for the UE.

[0065] In an RRC-connected state, the gNB may be responsible for maintaining the timing advance to keep L1 synchronized. Serving cells that have the same timing advance applied to the uplink and the same timing reference cell are grouped into a Timing Advance Group (TAG). A TAG may contain at least one serving cell to which the uplink is configured. The mapping of serving cells to TAGs may be configured by the RRC. In the case of a primary TAG, the UE may use a PCell as the timing cell, with the exception of shared spectral channel access, in which case an SCell may also be used as the timing reference cell. In a secondary TAG, the UE may use any of the activated SCells in this TAG as the timing reference cell and cannot change it unless necessary.

[0066] Timing advance updates can be signaled to the UE via MAC CE commands by the gNB. Such commands may restart the timer for each TAG, which may indicate whether L1 can be synchronized. That is, if the timer is running, L1 can be considered synchronized; otherwise, L1 can be considered not synchronized (in this case, uplink transmission can only occur via PRACH).

[0067] A UE with one timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells are grouped into one TAG) that share the same timing advance. A UE with multiple timing advance capabilities for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells are grouped into multiple TAGs) that have different timing advances. NG-RAN can ensure that each TAG contains at least one serving cell. A non-CA UE may receive on one CC (one serving cell within one TAG) corresponding to only one serving cell and transmit on one CC.

[0068] In the case of CA, the multi-carrier nature of the physical layer can be exposed to the MAC layer, and one HARQ entity may be required for each serving cell. Once CA is configured, the UE is It may have one RRC connection to the network. During RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) may provide NAS mobility information. Depending on the capabilities of the UE, SCells may be configured to form a serving cell set together with PCells. A serving cell set configured for a given UE may consist of one PCell and one or more SCells. Reconfiguration, addition, and removal of SCells are performed by the RRC.

[0069] In a dual connectivity scenario, the UE may consist of multiple cells, including a master cell group (MCG) for communication with the master base station, a secondary cell group (SCG) for communication with secondary base stations, and two MAC entities: one MAC entity for the MCG for communication with the master base station and one MAC entity for the SCG for communication with the secondary base stations.

[0070] Figure 10 shows exemplary bandwidth portion configurations and switching in some aspects of one or more exemplary embodiments of the present disclosure. A UE may be configured to have one or more bandwidth portions (BWPs) 1010 (e.g., 1010A, 1010B) on a component carrier. In some examples, one of the one or more bandwidth portions may be active at a time. The active bandwidth portion may define the operating bandwidth of the UE within the cell's operating bandwidth. During initial access, an initial bandwidth portion 1020 identified from system information may be used until the configuration of the UE in the cell is received. Bandwidth adaptation (BA) through BWP switching 1040, for example, allows the UE's reception and transmission to be adjusted so that they are not as large as the cell's bandwidth. For example, the width may be instructed to change (e.g., to reduce during periods of low activity to conserve power), the position within the frequency domain may be moved (e.g., to increase scheduling flexibility), or the subcarrier spacing may be instructed to change (e.g., to enable different services). The initial active BWP1030 may be the active BWP during RRC(re)configuration for PCell or during SCell activation.

[0071] For each downlink BWP or uplink BWP in a set of downlink BWPs or uplink BWPs, the following configuration parameters may be provided to the UE: subcarrier spacing (SCS), cyclic prefix, number of common RBs and consecutive RBs, index within the set of downlink BWPs or uplink BWPs by its BWP-Id, BWP-common parameter set, and BWP-individual parameter set. A BWP may be associated with OFDM numerology according to the subcarrier spacing and cyclic prefix set for that BWP. For a serving cell, the UE may be provided by the default downlink BWP in the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP may be the initial downlink BWP.

[0072] A downlink BWP can be associated with a BWP inactivity timer. When the BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is set, the UE may perform a BWP switch to the default BWP. When the BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not set, the UE may perform a BWP switch to the initial downlink BWP.

[0073] Figure 11 illustrates exemplary four-stage collision-based random access (CBRA) and non-collision-based random access (CFRA) in some aspects of one or more exemplary embodiments of the present disclosure. Figure 12 illustrates an n-free random access (n-free random access) process. It shows exemplary two-stage collision-type random access (CBRA) and collision-free random access (CFRA) processes according to several aspects of one or more exemplary embodiments of the present disclosure. Random access procedures can be triggered by a variety of events, including, for example, initial access from an RRC idle state, RRC connection re-establishment procedures, arrival of downlink or uplink data in an RRC connection state when the uplink synchronization state is "asynchronous", arrival of uplink data in an RRC connection state when PUCCH resources are unavailable for a scheduling request (SR), SR failures, requests by the RRC during synchronous reconfiguration (e.g., handover), transitions from an RRC inactive state, requests for other system information (SI) to establish time alignment regarding secondary TAGs, beam failure recovery (BFR), and continuous uplink listen-before-talk (LBT) failures in the PCell.

[0074] Two types of random access (RA) procedures can be supported: a four-step RA using MSGA and a two-step RA using MSGA. Both types of RA procedures can support collisional random access (CBRA) and non-collisional random access (CFRA), as shown in Figures 11 and 12.

[0075] When initiating a random access procedure, the UE may select the type of random access based on the network configuration. If CFRA resources are not configured, the UE may use an RSRP threshold to select between a two-stage RA type and a four-stage RA type. If CFRA resources are configured for a four-stage RA type, the UE may perform random access with a four-stage RA type. If CFRA resources are configured for a two-stage RA type, the UE may perform random access with a two-stage RA type.

[0076] In a 4-stage RA type, MSG1 may consist of a PRACH preamble (Step 1 of CBRA in Figure 11). After sending MSG1, the UE may monitor responses from the network within a set window (Step 2 of CBRA in Figure 11). In the case of CFRA, a separate preamble for sending MSG1 may be assigned by the network (Step 0 of CFRA in Figure 11), and upon receiving a Random Access Response (RAR) from the network, the UE may terminate the random access procedure as shown in Figure 11 (Steps 1 and 2 of CFRA in Figure 11). In the case of CBRA, upon receiving a Random Access Response (Step 2 of CBRA in Figure 11), the UE may send MSG3 using the scheduled uplink grant in the Random Access Response (Step 3 of CBRA in Figure 11), and may monitor collision resolution as shown in Figure 11 (Step 4 of CBRA in Figure 11). If collision resolution is unsuccessful after (re)transmission of MSG3, the UE may return to sending MSG1.

[0077] A two-step RA type MSGA may include a PRACH preamble and a PUSCH payload (e.g., step A of the CBRA in Figure 12). After transmitting the MSGA, the UE may monitor responses from the network within a set window. In the case of CFRA, separate preamble and PUSCH resources may be configured for MSGA transmission (steps 0 and A of the CFRA in Figure 12), and upon receiving a network response (step B of the CFRA in Figure 12), the UE may terminate the random access procedure as shown in Figure 12. In the case of CBRA, if collision resolution is successful upon receiving a network response (step B of the CBRA in Figure 12), the UE may terminate the random access procedure as shown in Figure 12, but if a fallback instruction is received in the MSGB, the UE may perform a transmission of MSG3 using the uplink grant scheduled in the fallback instruction and monitor collision resolution. If collision resolution is unsuccessful after the (re)transmission of MSG3, the UE may return to transmitting the MSGA.

[0078] Figure 13 shows exemplary time and frequency structures of synchronization signals and physical broadcast channel (PBCH) blocks (SSBs) according to several aspects of one or more exemplary embodiments of the present disclosure. An SS / PBCH block (SSB) may consist of primary and secondary synchronization signals (PSS, SSS), each occupying one symbol and 127 subcarriers (e.g., subcarrier numbers 56–182 in Figure 13), and a PBCH spanning three OFDM symbols and 240 subcarriers, except for the SSS, where one symbol leaves a central unused portion, as shown in Figure 13. Possible time positions of SSBs within a half-frame may be determined by the subcarrier spacing, and the period of the half-frame in which the SSBs are transmitted may be set by the network. Within a half-frame, different SSBs may be transmitted in different spatial directions (i.e., using different beams and across the entire coverage area of ​​the cell).

[0079] The PBCH may be used to carry the Master Information Block (MIB) used by the UE during cell search and initial access procedures. The UE may first decode the PBCH / MIB to receive other system information. The MIB may provide the UE with the parameters necessary to obtain System Information Block 1 (SIB1), more specifically, the information necessary to monitor the PDCCH in order to schedule the PDSCH to carry SIB1. In addition, the MIB may indicate Cell Barred status information. The MIB and SIB1 may collectively be called the Minimum System Information (SI), and SIB1 may be called the Remaining Minimum System Information (RMSI). Other System Information Blocks (SIBs) (e.g., SIB2, SIB3, ..., SIB10, and SIBpos) may be called Other SIs. Other SIs may be broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (e.g., in response to requests from UEs in RRC idle, RRC inactive, or RRC connected state), or sent individually on the DL-SCH to RRC connected UEs (e.g., in response to requests from RRC connected UEs if configured by the network, or if the UE has an active BWP and no common search space is configured).

[0080] Figure 14 shows exemplary SSB burst transmissions according to several aspects of one or more exemplary embodiments of the present disclosure. An SSB burst may include N SSBs (e.g., SSB_1, SSB_2, ..., SSB_N), where each of the N SSBs may correspond to a beam (e.g., Beam_1, Beam_2, ..., Beam_N). An SSB burst may be transmitted according to periodicity (e.g., SSB burst duration). During a collision-type random access process, the UE may perform a random access resource selection process, where the UE first selects an SSB and then selects an RA preamble. The UE may select an SSB with an RSRP higher than a set threshold. In some embodiments, the UE may select any SSB if no SSB with an RSRP higher than the set threshold is available. A set of random access preambles may be associated with an SSB. After selecting an SSB, the UE can obtain a random access preamble from the set of random access preambles associated with that SSB, send the selected random access preamble, and initiate the random access process.

[0081] In some embodiments, one of the N beams may be associated with a CSI-RS resource (e.g., CSI-RSA_1, SCI-RS_2, ..., CSI-RS_N). The UE may measure the CSI-RS resources and select a CSI-RS with an RSRP higher than a set threshold. The UE may select a random access preamble corresponding to the selected CSI-RS, transmit the selected random access process, and initiate the random access process. Without a random access preamble, the UE may select a random access preamble corresponding to the SSB that is in a pseudo-colocation relationship with the selected CSI-RS.

[0082] In some embodiments, based on measurements of CSI-RS resources by the UE and CSI reports by the UE, the base station may identify a Transmission Configuration Indication (TCI) state and instruct the UE to use the instructed TCI state for receiving downlink control information (e.g., via a PDCCH) or data (e.g., via a PDSCH). The UE may use the instructed TCI state to use a beam suitable for receiving data or control information. Instructing a TCI state may involve using an RRC configuration or a combination of RRC signaling and dynamic signaling (e.g., via a MAC control element (MAC CE) and / or based on the value of a field in downlink control information that schedules downlink transmissions). A TCI state may indicate a quasi-collocation (QCL) relationship between a downlink reference signal such as CSI-RS and a DM-RS associated with a downlink control or data channel (e.g., a PDCCH or PDSCH, respectively).

[0083] In some embodiments, the UE may use physical downlink shared channel (PDSCH) configuration parameters to configure a list of TCI states up to M, and the PDSCH may be decoded according to the PDCCH detected by the DCI intended for the UE and a certain serving cell, where M may depend on the capabilities of the UE. Each TCI state may include parameters for configuring a QCL relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of a CSI-RS resource. The pseudo-collocation relationship may be configured by one or more RRC parameters. The type of pseudo-collocation corresponding to each DL RS may take one of the following values: 'QCL-TypeA': {Doppler shift, Doppler extension, average delay, delay extension}, 'QCL-TypeB': {Doppler shift, Doppler extension}, 'QCL-TypeC': {Doppler shift, average delay}, 'QCL-TypeD': {Spatial Rx parameter}. The UE may receive activation commands (e.g., MAC CE) used to map TCI states to code points in the DCI fields.

[0084] Figure 15 shows exemplary components of a user terminal and a base station in several aspects of one or more exemplary embodiments of the present disclosure. In one embodiment, the exemplary components of Figure 15 may be considered to exemplify the functional blocks of an exemplary base station 1505. In other embodiments, the exemplary components of Figure 15 may be considered to exemplify the functional blocks of an exemplary user terminal (UE) 1500. Thus, the components shown in Figure 15 are not necessarily limited to either a UE or a base station.

[0085] With respect to Figure 15, antenna 1510 can be used for transmitting or receiving electromagnetic signals. Antenna 1510 may include one or more antenna elements, thereby enabling various input-output antenna configurations, including Multiple-Input Multiple Output (MIMO), Multiple-Input Single-Output (MISO), and Single-Input Multiple-Output (SIMO) configurations. In some embodiments, antenna 1510 can realize a massive MIMO configuration using tens or hundreds of antenna elements. Antenna 1510 may use other multi-antenna techniques, such as beamforming. In some embodiments, depending on the capabilities of UE 1500 and the type of UE 1500 (e.g., low-complexity UE), UE 1500 may support only a single antenna.

[0086] The transceiver 1520 may communicate bidirectionally over a radio link via the antenna 1510 as described herein. For example, the transceiver 1520 may represent a radio transceiver at a UE and communicate bidirectionally with a radio transceiver at a base station, or vice versa. The transceiver 1520 may include a modem for modulating packets, providing modulated packets to the antenna 1510 for transmission, and modulating packets received from the antenna 1510.

[0087] Memory 1530 may include RAM and ROM. Memory 1530 may store computer-readable, computer-executable code 1535, which, when executed, causes the processor to perform various functions described herein. In some examples, memory 1530 may, among other things, include a Basic Input / Output System (BIOS), which can control basic hardware or software operations such as interactions with peripheral components or devices.

[0088] The processor 1540 may include hardware devices having processing capabilities (e.g., general-purpose processors, digital signal processors (DSPs), central processing units (CPUs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some examples, the processor 1540 may be configured to operate memory using a memory controller. In other examples, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1530) to cause the UE 1500 or base station 1505 to perform various functions.

[0089] The CPU 1550 can perform basic arithmetic, logic, control, and input / output (I / O) operations as specified by computer instructions in memory 1530. The UE 1500 and / or base station 1505 may include other peripheral components such as a graphics processing unit (GPU) 1560 and a Global Positioning System (GPS) 1570. The GPU 1560 is special circuitry that rapidly operates and modifies memory 1530 to accelerate the processing performance of the UE 1500 and / or base station 1505. The GPS 1570 may be used to enable location-based services and other services based on the geographic location of the UE 1500, for example.

[0090] In some examples, UE 1500 may be configured or programmed to function as a coordinating UE in a mobile communications system that includes sidelink transmissions. In addition to UE 1500 and base station 1505, the mobile communications system may also include one or more second UEs. UE 1500 may be configured or programmed to receive instructions that UE 1500 is a coordinating UE for the coordination of sidelink transmissions of one or more second UEs. UE 1500 may receive instructions from base station 1505. UE 1500 may receive instructions through an antenna, for example, antenna 1510. UE 1500 may further be configured or programmed to receive one or more groupcast transmission parameters from base station 1505. UE 1500 may be configured or programmed to identify sidelink transmission parameters for one or more UEs to avoid collisions or half-duplex conflicts between the sidelink transmissions of one or more second UEs. The sidelink transmission parameters may include a preferred resource set for one or more second UEs or a less preferred resource set for one or more second UEs. In some embodiments, the sidelink transmission parameters may include a preferred resource set for one or more second UEs. In some embodiments, UE 1500 The UE 1500 may detect transmission parameters of one or more second UEs and, based on the detection results, identify sidelink transmission parameters for one or more second UEs. In some embodiments, the sidelink transmission parameters may include a set of resources undesirable for one or more second UEs. In these embodiments, the UE 1500 may identify sidelink transmission parameters for one or more second UEs based on at least one of the detection results of transmission parameters of one or more second UEs or predictive information of resource collisions or half-duplex conflicts in sidelink transmission. The UE 1500 may be configured or programmed to send a groupcast message containing the sidelink transmission parameters for one or more second UEs to one or more second UEs. The UE 1500 may be configured or programmed to send a groupcast message to one or more second UEs based on the identification of one or more groupcast transmission parameters. The UE 1500 may be configured or programmed to send a groupcast message to one or more second UEs at a predetermined time. In some embodiments, one or more groupcast transmission parameters indicate the occasion for sending a groupcast message and one or more radio resources. In some embodiments, UE 1500 may transmit a set of resources identified for one or more second UEs via a unicast or broadcast message. In the above example, the memory of UE 1500 (e.g., memory 1530) may store code (e.g., code 1535) for performing functions of UE 1500, which can be executed by the processor (e.g., CPU 1550).

[0091] In some examples, UE 1500 may be associated with one or more coordinated UEs in a mobile communication system. In these examples, UE 1500 may be configured or programmed to receive instructions that UE 1500 is associated with one or more coordinated UEs. UE 1500 may receive instructions from base station 1505. UE 1500 may receive these instructions via a receiver included in antenna 1510 and transceiver 1520. UE 1500 may further be configured or programmed to receive groupcast transmission parameters of a first coordinated UE among the one or more coordinated UEs from base station 1505. UE 1500 may be configured or programmed to receive groupcast messages from the first coordinated UE, including sidelink transmission parameters to avoid collisions or half-duplex conflicts in UE 1500's sidelink transmissions. UE 1500 may be configured or programmed to receive groupcast messages from the first coordinated UE based on groupcast transmission parameters. UE 1500 may be configured or programmed to transmit sidelink data to a second UE based on sidelink transmission parameters received from a first coordinating UE. In these examples, the memory of UE 1500 (e.g., memory 1530) may store computer program code (e.g., code 1535) for performing functions of UE 1500, which can be executed by a processor (e.g., CPU 1550).

[0092] In some examples, base station 1505 is for a mobile communication system that includes sidelink transmission of one or more second UEs. Base station 1505 may include a memory (e.g., memory 1530) for storing instructions (e.g., code 1535) and a processor (e.g., CPU 1550) configured or programmed to execute instructions and send an instruction to a first UE (e.g., UE 1500) that the first UE is a coordinating UE or is associated with at least one coordinating UE for coordinating sidelink transmission of one or more second UEs. The base station may further send one or more groupcast transmission parameters to the first UE. In these examples, the first UE may be configured or programmed to send sidelink transmission parameters to one or more second UEs based on one or more groupcast transmission parameters.

[0093] In some cases, DCI format 3_0 can be used for scheduling NR PSCCH and NR PSSCH within a single cell. The following information may be transmitted in DCI format 3_0 with a scrambled CRC by SL-RNTI or SL-CS-RNTI: resource pool index, type gap, HARQ process number, new data indicator, minimum index for subchannel allocation to initial transmission, SCI format fields including period resource allocation and time resource allocation, PSFCH-to-HARQ feedback timing indicator, configuration index, and counterside link allocation index.

[0094] In some cases, the SidelinkUEinformationNR message can be used to instruct the network on NR sidelink UE information.

[0095] In some examples, the s1-QoS-FlowIdentity information element may provide an identifier that uniquely identifies a single sidelink QoS flow between the UE and the network within the UE's scope, which may be specific to different destinations and cast types. In some examples, the s1-UE-AssistanceInformationNR information element may indicate the traffic characteristics of a sidelink logical channel that may be configured for NR sidelink communication. In some examples, system information block 12 (SIB12) may be used for NR sidelink communication configuration.

[0096] In Mode 2 sidelink operation, a UE may automatically select resources for transmission. Based on the detection results, the UE may avoid resource collisions with other UEs within its receiving range. In some examples, as shown in Figure 16a, resource collisions can occur due to hidden nodes when two transmitting UEs are outside each other's transmission range and the same resources are used for transmission to nearby receiving UEs, resulting in high interference. As a result of this problem, the transmitting UE may not consider the reserved resources of other UEs and may not exclude these resources from its resource set of candidates. In some cases, both transmitting UEs may select the same resources for their respective transmissions to a common receiving UE. In the example shown in Figure 16a, UE 1 could always collide with UE 2.

[0097] Another example is half-duplex operation in sidelink mode 2. As shown in Figure 16b, the half-duplex nature of V2X UEs means that when a UE (e.g., UE 1) periodically transmits packets in a given time slot, it may not be able to receive transmissions from other UEs. The UE may not be able to determine whether another UE (e.g., UE 2) transmitted sidelink control information (SCI) in that time slot. The UE may miss detections for those time slots when it transmits. In scenarios where the UE attempts to transmit many data packets, it may end up missing detections for multiple time slots, resulting in incomplete detections and an increased likelihood of collisions.

[0098] Exemplary embodiments enhance reliability and reduce latency in sidelink operation (e.g., sidelink mode 2 operation) based on inter-UE coordination. In some examples, coordination is achieved through the exchange of auxiliary information between UEs, or from UEs to a coordinating UE, where the coordinating UE coordinates sidelink transmissions by one or more UEs associated with the coordinating UE. The auxiliary information may indicate the resource set used by a particular UE. For example, a first UE may report its resource set to a second UE, which may consider the first UE's resource set when selecting resources for its own transmission. The second UE may choose not to use the resource set used by the first UE in order to avoid resource conflicts; that is, the resource set may not be a preferred resource set for the second UE.

[0099] Inter-UE coordination can be used in unicast, groupcast, and broadcast communications. Inter-UE coordination can occur before or after the initial transmission. In some cases, to avoid resource collisions and / or half-duplex conflicts before the initial packet transmission, coordinating UEs coordinate resources for sidelink transmissions between originating UEs. In some cases, one or more UEs that detect resource collisions and / or half-duplex conflicts after the initial transmission can use auxiliary information to avoid resource collisions and / or half-duplex conflicts in subsequent retransmissions and / or subsequent new transmissions. That is, coordinating UEs may transmit auxiliary information indicating the resource set when resource collisions and / or half-duplex conflicts are detected.

[0100] In some cases, a collaborative UE (also called a C-UE) may identify and / or indicate a set of resources to the outgoing UE(s) and / or transmit supplementary information to other UEs. A group UE (also called a G-UE) may receive supplementary information from the C-UE. The G-UE may use the information received from the C-UE and its own findings to select transmission resources to send a message to one or more other UEs.

[0101] In some cases, the coordinating UE can also be the receiving UE. In some examples shown in Figure 17, the coordinating UE may be another UE that transmits auxiliary information to the originating UE and the receiving UE. Based on the assistance from the coordinating UE, collisions or half-duplex conflicts can be avoided.

[0102] In some cases, for inter-UE coordination, a coordinating UE may provide the outgoing UE(s) with supplementary information about a (pre-configured) resource pool. This resource pool may be shared with different cast services. To achieve universal UE coordination within the resource pool, a unified mechanism may be used for providing supplementary information from the coordinating UE to the outgoing UEs, without any limitations on the cast type.

[0103] Auxiliary information may be provided actively or passively from a co-opting UE to an outgoing UE. In some cases, a co-opting UE may be aware of information such as available resources, interference, half-duplex and congestion conditions, and may actively provide this auxiliary information to the relevant outgoing UEs. In some cases, an outgoing UE may send a request to a co-opting UE, which may then provide the auxiliary information to the outgoing UE.

[0104] In some cases, a collaborative UE may identify available resources that can be acquired based on either (pre)configuration or detection, and / or measure interferences that need to be avoided in resource pool operation, or predict / detect resource collision information. The collaborative UE may provide this information to the participating UEs. For example, based on the resource collisions it has detected and / or predicted, the collaborative UE may transmit auxiliary information indicating a set of resources undesirable to the participating UEs. The outgoing UE may take such auxiliary information into consideration to make appropriate choices for its next potential transmission occasion. In another example, the collaborative UE may transmit auxiliary information indicating a set of resources to the participating UEs based on detected resource collision information.

[0105] To illustrate with a few examples, an outgoing UE with a packet to transmit may send a request to a coordinating UE to obtain supplementary information. This request may include QoS requirements, cast type, geographical information, and communication range related to the packet. The coordinating UE may then provide the outgoing UE with the supplementary information based on the request. This supplementary information may indicate that a certain set of resources is available to the outgoing UE; that is, that set of resources is preferable for the outgoing UE's transmission.

[0106] In some examples, the auxiliary information message provided by the coordinating UE to the originating UE may include one or more of the following: destination ID, source ID, resource set for transmission, and coordination information.

[0107] In some cases, a UE may be authorized (pre-authorized) or self-authorized as a collaborative UE, depending on the deployment scenario. Mobility may necessitate the inclusion of multiple collaborative UEs in the coordination between UEs. In some cases, collaborative UEs may establish other unicast links to exchange auxiliary information in order to avoid conflicts in auxiliary information issued by multiple collaborative UEs.

[0108] In some exemplary embodiments, a network (NW) / gNB may identify collaborative UEs, called C-UEs, by, for example, their geographical location. For example, a NW / gNB may identify overlapping cells containing multiple UEs, each cell containing one or more G-UEs, and a UE with one or more G-UEs may be identified as a C-UE. A NW / gNB may configure / identify groups of UEs, called G-UEs, each associated with a C-UE. A NW / gNB may indicate to a UE that it is a C-UE (for example, in an RRC configuration message or using dynamic signaling). A NW / gNB may provide a C-UE with group cast parameters for the C-UE, including periodicity. A NW / gNB may indicate group cast parameters for the C-UE using DCI (e.g., DCI format 3_0). G-UEs may be assigned to one or more collaborative groups by the NW / gNB. The NW / gNB may indicate to the G-UEs (e.g., G-UEs) which C-UEs are associated with a group of UEs. For example, the identification information of a C-UE within a group may be provided to the G-UE by the NW / gNB using a DL information transfer message. In some examples, the NW / gNB may send the group cast parameters and periodicity of the C-UEs to the G-UEs. The C-UE may detect and collect the transmission parameters of one or more UEs associated with the C-UE. The C-UE may incorporate the detected transmission parameters into the group cast message. The C-UE may send group cast messages in pre-configured and / or periodic instances. The G-UE may receive and decode group cast messages from the C-UE. In some examples, if a message is received with a CRC error, the G-UE may use the parameters contained in the last successfully received message. If a CRC error occurs within a pre-allocated number of consecutive messages from the C-UE, the G-UE may send a “lost C-UE” message to the NW / gNB (for example, using a FailureInformation message). The “lost C-UE” message is an example of an error message indicating that the cooperative UE has been lost.The G-UE can use the received transmission parameters and its own additional channel detection to transmit to the destination UE in a time-frequency resource where collisions or half-duplex conflicts cannot occur.

[0109] In some examples, the NW / gNB may send the group cast parameters of the C-UEs to the G-UE using DCI format 3_0. In some examples, a separate message may be sent for each C-UE assigned to each G-UE. In some examples, the group cast message of the C-UEs may be broadcast along with a system information block (SIB, e.g., SIB12).

[0110] In some cases, the C-UE may incorporate the detected transmission parameters into the groupcast message sent by the C-UE on the PSSCH, according to the assigned DCI format 3_0.

[0111] In some cases, NW / gNB may provide the C-UE with identifying information for each G-UE within its group. The amount of detection and reporting by the C-UE is what allows the C-UE to identify each G-UE within its group. This can be reduced by providing G-UE identification information.

[0112] In some exemplary embodiments, the NW / gNB may identify collaborative UEs, called C-UEs, by their geographical location. For example, the NW / gNB may identify overlapping cells containing multiple UEs, in which case each cell may contain one or more G-UEs, and one or more UEs among the G-UEs may be identified as a C-UE. The network (NW) / gNB may define groups of UEs called G-UEs, each associated with a C-UE. The NW / gNB may indicate to a UE that it is a C-UE and may provide identification information for the G-UEs in the group associated with the C-UE. The NW / gNB may provide the C-UE with group cast parameters for the C-UE, including periodicity. A G-UE may be assigned to one or more collaborative groups by the NW / gNB. Identification information for a C-UE within a group may be provided to the G-UE by the NW / gNB. NW / gNB can transmit the group cast parameters and periodicity of C-UEs to G-UEs.

[0113] A C-UE can detect and collect the transmission parameters of its G-UEs. For example, a C-UE may detect one or more transmission parameters based on an inspection of past communications received from individual G-UEs. A C-UE may incorporate its G-UEs' transmission parameters into groupcast messages. A C-UE may send groupcast messages in pre-configured and / or periodic instances. Upon receiving and successfully decoding a groupcast message from a C-UE, a G-UE may check that the reported parameters were correctly transmitted. If they were not transmitted correctly, the G-UE may send a NACK (negative acknowledgement). In some cases, an ACK (acknowledgment) may not be sent to prevent unnecessary transmissions. If a message is received with a CRC error, the G-UE may use the parameters contained in the last correctly received message. If a CRC error occurs within a pre-allocated number of consecutive messages from a C-UE, the G-UE may send a “lost C-UE” report to the network. The G-UE can use the received transmission parameters and its own channel detection to transmit to the destination G-UE within a time-frequency resource free from collisions or half-duplex conflicts.

[0114] In some cases, the G-UE may send its assigned periodic transmission parameters to the C-UE at specified intervals. If a message from the G-UE is received incorrectly, the C-UE may send a NACK, in which case the HARQ process may be initiated.

[0115] In some exemplary embodiments, the NW / gNB may identify collaborative UEs, called C-UEs, by their geographical location. For example, the NW / gNB may identify overlapping cells containing multiple UEs, each cell containing one or more G-UEs, and a UE with one or more G-UEs may be identified as a C-UE. The NW / gNB may form groups of UEs called G-UEs, each associated with a C-UE. G-UEs may be assigned to one or more collaborative groups by the NW / gNB. The NW / gNB may provide the G-UEs with identification information for each C-UE. It may also transmit group cast parameters of the C-UEs, including periodicity, to the G-UEs. The NW / gNB may allocate transmission resources used for reporting to each assigned C-UE. In addition, the NW / gNB may allocate schedule or periodicity data that the C-UEs use to identify reporting criteria. These resources may be reserved until modified or disabled by the NW / gNB. The NW / gNB can send the G-UE ID and the report transmission resource assigned to it to the corresponding C-UE.

[0116] A G-UE may transmit its assigned periodic transmission parameters, such as time slots and frequency ranges, to the C-UE at specified intervals. If a message is received incorrectly, the C-UE may send a NACK, in which case the HARQ process may be initiated. The C-UE may collect the transmission parameters of each reported G-UE and incorporate them into a groupcast message. In one embodiment, the C-UE may send a groupcast message in a pre-configured periodic instance. If a message from the C-UE is received with a CRC error, the G-UE may use the parameters contained in the last correctly received message. If a CRC error occurs within a pre-assigned number of consecutive messages from the C-UE, the G-UE may send a “lost C-UE” report to the NW / gNB. The G-UE may use the received transmission parameters and its own channel detection to send to a destination G-UE within a time-frequency resource where collisions or half-duplex conflicts may not occur.

[0117] In some exemplary embodiments, as shown in Figure 18, a base station (e.g., gNB) communicates with multiple UEs (e.g., UE 1, UE 2) using a sidelink communication channel. 2. A service may be provided to a Cooperative UE. To minimize collisions or half-duplex conflicts between sidelink communications of UEs, the base station may divide multiple UEs into one or more groups, each group containing one or more UEs, one or more UEs within that group being coordinated by a Cooperative UE. For example, UE1 and UE2 in Figure 18 may be coordinated by a Cooperative UE. The base station may indicate its role as a Cooperative UE to the Cooperative UE. The base station may indicate to UE1 and UE2 that they are being coordinated by a Cooperative UE, and the base station may provide UE1 and UE2 with the identification information of the Cooperative UE. The base station may provide the identification information of UE1 and UE2 to the Cooperative UE. The base station may transmit transmission parameters to UE1 and UE2 and the Cooperative UE. The Cooperative UE may transmit groupcast messages based on the groupcast transmission parameters. The groupcast transmission parameters may include the radio resources and time occasions of the groupcast message or the periodicity of the groupcast message transmission. Groupcast transmission parameters may be used by the coordinating UE to transmit supplementary information using groupcast messages. Groupcast transmission parameters may be used by UE1 and UE2 to receive supplementary information via groupcast messages. The coordinating UE may provide sidelink transmission parameters to UE1 and UE2 to avoid collisions or half-duplex conflicts. The coordinating UE may identify sidelink transmission parameters for UE1 and UE2 based on detection results and the collection of transmission information from UE1 and UE2.

[0118] In one exemplary embodiment, as shown in Figure 19, a first UE may receive an instruction from a base station that it has been assigned the role of a coordinating UE. The role of a coordinating UE may be assigned to a UE quasi-statically (e.g., using RRC signaling) or dynamically (e.g., using physical layer or MAC signaling). For example, in the case of RRC signaling, the first UE may receive an RRC message containing an information element, the value of which may indicate that the first UE is a coordinating UE. For example, in the case of physical layer signaling, the first UE may receive a DCI (e.g., a DCI in a format associated with side-link communication). Exemplarily, the DCI may include a field containing a value indicating that the first UE is a coordinating UE. The role of a coordinating UE for a given UE may be assigned and revoked at the discretion of the base station, as needed. The base station may indicate that the first UE is a coordinating UE for one or more second UEs. In some examples, the base station may indicate to the first UE the identifiers of one or more second UEs.

[0119] The first UE may receive groupcast transmission parameters from the base station. In some examples, the groupcast transmission parameters are supplementary for one or more second UEs. This may relate to the transmission of auxiliary / coordinating information. In some examples, groupcast transmission parameters may be shared for groupcasting auxiliary / coordinating information and for other groupcast purposes. Groupcast transmission parameters may include radio resources, modulation and coding schemes, power control parameters, etc. In some examples, the first UE may receive groupcast transmission parameters using downlink control information (e.g., DCI format 3_0 or other DCI format). In other examples, the first UE may receive groupcast transmission parameters via RRC signaling. For example, the first information element may indicate that the first UE is a coordinating UE, and the second information element may indicate groupcast transmission parameters intended for transmitting coordinating information. Other signaling mechanisms (e.g., MAC CE) may also be used to transmit groupcast transmission parameters. In some examples, groupcast transmission parameters may be indicated using groupcast messages (e.g., System Information Blocks (SIBs)). In such cases, the groupcast transmission parameters may be known to the first UE and other UEs (including one or more second UEs coordinated by the first UE).

[0120] The first UE may identify sidelink transmission parameters by one or more second UEs to avoid collisions or half-duplex conflicts in the sidelink transmission of one or more second UEs. In some examples, the identification of sidelink transmission parameters by one or more second UEs may consider attributes of one or more second UEs based on the identifier of one or more second UEs. The first UE may identify sidelink transmission parameters based on a request from one of the second UEs, or without a request from one or more second UEs (e.g., passively or actively, respectively). The first UE may identify sidelink transmission parameters based on processing or detecting (detecting) past transmissions received from one or more second UEs and collecting relevant information. In other embodiments, the first UE may identify sidelink transmission parameters at least in part on predicting the transmission patterns of one or more second UEs. The first UE may utilize information about one or more second UEs that may be provided to the first UE by the base station or through other processes. The sidelink transmission parameters of one or more second UEs may include radio resources (e.g., frequency resources and time-domain parameters such as slots and symbols used for transmission), power levels, transmission formats, such as modulation and coding schemes. The first UE may utilize optimization processes to minimize or completely avoid collisions between one or more second UEs. In some examples, the first UE may consider the type of UE among one or more second UEs or the data scheduled for transmission by a UE among one or more second UEs (e.g., data priority, quality of service associated with the data, data type, etc.).

[0121] The first UE may transmit to one or more second UEs identified sidelink transmission parameters that one or more second UEs will use in their subsequent transmissions. The first UE may transmit sidelink transmission parameters to one or more second UEs based on a groupcast message. For example, the first UE may transmit a groupcast message over a physical sidelink shared channel (PSSCH). The base station may provide the first UE and one or more second UEs with a groupcast message (e.g., radio resources / transmission timing for the groupcast message). In some examples, the groupcast message may be transmitted by the first UE to one or more second UEs at specific predetermined times, or it may be transmitted periodically, persistently, and / or semi-persistently. The base station may periodically provide information or scheduling information used for transmitting the groupcast message. In addition, the base station may provide other parameters associated with the transmission of the groupcast message. It may provide parameters. For example, one or more second UEs may decode the groupcast message using parameters received from the base station.

[0122] In some cases, a first UE may receive feedback (e.g., ACK / NACK) from one or more second UEs in response to sending a groupcast message. The first UE may receive feedback information via one or more sidelink control channels (e.g., PSCCH). The first UE may take the received feedback into consideration and retransmit the groupcast message in response to receiving a NACK. The retransmission of the groupcast message may also be a groupcast message or one or more unicast messages. Feedback and retransmission of groupcast messages may be based on a HARQ process. In some cases, the first UE may receive a command from the base station indicating the retransmission of the groupcast message (e.g., downlink control information, MAC CE, etc.). For example, the base station may receive feedback from one or more second UEs and send a command to the first UE for retransmitting the groupcast message based on the feedback received from one or more second UEs.

[0123] In some cases, the first UE may receive transmission parameters (e.g., slots, frequency resources, periodicity, identifiers of one or more second UEs) for scheduled sidelink transmissions of one or more second UEs, and based on these transmission parameters, the first UE may identify sidelink transmission parameters to avoid collisions or half-duplex conflicts. The first UE may identify that some of the parameters for scheduled sidelink transmissions of one or more second UEs need to be modified to avoid collisions / half-duplex conflicts, and may indicate the modified sidelink parameters to the first UE.

[0124] In some examples, one or more second UEs may transmit the parameters of a scheduled sidelink transmission according to a specified schedule, periodic interval, or other scheduling or triggering criterion. In some examples, one or more second UEs may be allocated radio resources for transmitting the parameters of a scheduled sidelink transmission to the first UE, and radio resources for receiving the parameters of a scheduled sidelink transmission may be indicated to the first UE by the base station. In some examples, a feedback mechanism (e.g., based on the HARQ process) may be used so that the first UE can send a negative acknowledgment (NACK) in response to an incorrect reception of the scheduled sidelink transmission parameters.

[0125] In one exemplary embodiment, as shown in Figure 20, the first UE may receive instructions from the base station that the first UE is associated with one or more coordinating UEs. In some examples, the first UE may receive instructions from the base station in an RRC message. For example, one or more information elements in the RRC message may indicate identifiers of one or more coordinating UEs. In some examples, the first UE may receive instructions from the base station based on physical layer or MAC layer signaling.

[0126] The first UE may receive groupcast transmission parameters associated with the first coordinating UE among one or more coordinating UEs. In some examples, the groupcast transmission parameters may differ each time auxiliary / coordinating information is received from the first coordinating UE. The groupcast transmission parameters may include radio resources, modulation and coding schemes, power control parameters, etc. In some examples, the groupcast transmission parameters may indicate the occasion for receiving a groupcast message. For example, the groupcast transmission parameters may indicate when a groupcast message is periodically sent from the first coordinating UE. If transmitted correctly, the transmission may exhibit periodicity. In some cases, the first UE may receive the groupcast transmission parameters using downlink control information (e.g., DCI format 3_0 or other DCI format). In some cases, the groupcast transmission parameters may be indicated to the first UE using RRC signaling. For example, the first information element may indicate that the first UE is associated with one or more coordinating UEs, and the second information element may indicate the groupcast transmission parameters for receiving the coordination information. Other signaling mechanisms (e.g., MAC CE) may also be used to receive the groupcast transmission parameters. In some cases, the groupcast transmission parameters may be indicated using broadcast messages (e.g., System Information Blocks (SIBs)). In such cases, the groupcast transmission parameters may be known to the first UE and one or more coordinating UEs.

[0127] The first UE may receive a groupcast message indicating sidelink transmission parameters from the first UE to avoid collisions or half-duplex conflicts in its sidelink transmission. In some examples, the first UE may send a request to the first coordinating UE indicating that it has packets to transmit, and may receive a groupcast message from the first coordinating UE based on this request. In some examples, the first UE may receive a groupcast message without sending a request. Sidelink transmission parameters for the first UE may include radio resources (e.g., frequency resources and time-domain parameters such as slots and symbols used for transmission), power levels, and transmission formats such as modulation and coding schemes. In some examples, the first UE may receive sidelink transmission parameters via a physical sidelink shared channel (PSSCH). In some examples, the groupcast message may be received by the first UE at a specific predetermined time, or it may be received periodically, persistently, and / or semi-persistently. The base station may indicate periodicity or other parameters associated with the reception of the groupcast message, and the first UE may use the parameters received from the base station to decode the groupcast message.

[0128] In some cases, the first UE may send feedback information (e.g., ACK / NACK) to the first co-UTU indicating the correct or incorrect reception of a groupcast message. Upon receipt of the ACK / NACK by the first co-UTU, the first co-UTU may initiate a HARQ process, and the first UE may receive a retransmission of the groupcast message (e.g., another groupcast message or unicast message). In some cases, in response to a predetermined number of incorrect receptions of the groupcast message, the first UE may send an error message (e.g., an RRC message indicating an error) to the base station. The error message may indicate that the first UE has lost track of its co-UTU. Based on the receipt of the error message from the first UE, the base station may reconfigure the first UE with another co-UTU or another set of co-UTUs.

[0129] In some examples, the first UE may provide the parameters of its scheduled sidelink transmission to the first coordinating UE. The parameters of the scheduled sidelink transmission may include the slot, frequency resource, or periodicity of the scheduled sidelink transmission by the first UE. In some examples, the parameters of the scheduled sidelink transmission may include the identifier of the first UE. The transmission of the parameters of the scheduled sidelink transmission by the first UE to the first coordinating UE may be based on radio resources provided to the first UE by the base station. In some examples, radio resources for the transmission of the scheduled sidelink transmission may be provided to the first UE quasi-statically (e.g., using RRC signaling) or dynamically.

[0130] The first Cooperative UE is scheduled by the first UE and other UEs. Based on the link transmission parameters, the content of the groupcast message (e.g., supplementary information) can be identified. The first UE may transmit the parameters of its scheduled sidelink transmission periodically or based on a certain periodicity.

[0131] The first UE may use a sidelink physical channel (e.g., PSSCH) to transmit sidelink data to the second UE based on the sidelink transmission parameters indicated to the first UE by the first coordinating UE.

[0132] In some embodiments, a first user terminal (UE) may receive instructions from a base station that the first UE is a coordinating UE for coordinating sidelink transmissions of one or more second UEs. The first UE may receive one or more groupcast transmission parameters from the base station. The first UE may identify sidelink transmission parameters for one or more second UEs and for avoiding collisions or half-duplex conflicts between the sidelink transmissions of one or more second UEs. The first UE may send a groupcast message to one or more second UEs, including sidelink transmission parameters for one or more second UEs based on one or more groupcast transmission parameters.

[0133] In some cases, sending a groupcast message may occur at a predetermined time.

[0134] In some examples, one or more groupcast transmission parameters may indicate one or more of the transmission occasions and radio resources of the groupcast message. In some examples, one or more groupcast transmission parameters may indicate the periodicity of the groupcast message.

[0135] In some cases, a first UE may detect and collect transmission parameters of one or more second UEs. In some cases, identifying sidelink transmission parameters for one or more second UEs may be based on the detected and collected transmission parameters.

[0136] In some cases, receiving an instruction may be based on receiving a radio resource control (RRC) message containing parameters indicating that instruction.

[0137] In some cases, receiving an instruction is based on receiving downlink control information, including a field, where the field value indicates the instruction.

[0138] In some cases, receiving one or more groupcast transmission parameters may be based on receiving an RRC message indicating one or more groupcast transmission parameters.

[0139] In some cases, receiving one or more groupcast transmission parameters may be based on receiving downlink control information indicating one or more groupcast transmission parameters.

[0140] In some cases, sending a groupcast message may be based on receiving downlink control information indicating the transmission parameters of a physical sidelink shared channel (PSSCH) via the PSSCH.

[0141] In some cases, the first UE may receive identifiers for one or more second UEs. In some cases, identifying sidelink transmission parameters can be based on this identifier.

[0142] In some cases, the first UE may receive feedback information indicating that one or more UEs of one or more second UEs have misreceived a groupcast message. In some cases, the first UE may retransmit the groupcast message based on having received the feedback information. In some cases, the feedback information may be a negative response (NACK). In some cases, receiving the feedback information may be via a sidelink control channel.

[0143] In some cases, the first UE may receive a command from the base station indicating the retransmission of a groupcast message. In some cases, the command may be one of the downlink control information and media access control (MAC) control elements.

[0144] In some examples, a first UE may receive transmission parameters for a scheduled sidelink transmission of one or more second UEs from one or more second UEs. In some examples, identifying the sidelink transmission parameters for one or more second UEs may be based on the scheduled sidelink transmission of one or more second UEs. In some examples, the timing of receiving the transmission parameters for a scheduled sidelink transmission may be based on periodicity. In some examples, the transmission parameters for a scheduled sidelink transmission may include one or more of slots, frequency resources, and periodicity. In some examples, a first UE may receive a radio resource allocation from a base station for receiving the transmission parameters for a scheduled sidelink transmission of one or more second UEs. In some examples, the transmission parameters for a scheduled sidelink transmission of one or more second UEs may include identifiers of one or more second UEs. In some cases, the first UE may send one or more negative acknowledgments (NACKs) in response to receiving transmission parameters for a scheduled sidelink transmission from one or more second UEs. In some cases, sending one or more NACKs may be done to one or more of the second UEs that have incorrectly received transmission parameters for a scheduled sidelink transmission with respect to them.

[0145] In some embodiments, a first user terminal (UE) may receive an instruction from a base station that the first UE is associated with one or more coordinating UEs. The first UE may receive groupcast transmission parameters of the first coordinating UE from the base station. The first UE may also receive groupcast messages from the first coordinating UE indicating sidelink transmission parameters to avoid collisions or half-duplex conflicts in the first UE's sidelink transmission, based on the groupcast transmission parameters. The first UE may transmit transmission sidelink data to a second UE based on the sidelink transmission parameters.

[0146] In some cases, the first UE may receive an identifier from the base station that is associated with one or more coordinating UEs.

[0147] In some cases, receiving a groupcast message may occur at a predetermined time.

[0148] In some examples, one or more groupcast transmission parameters may indicate one or more of the transmission occasion and radio resources for the groupcast message. In some examples, one or more groupcast transmission parameters may indicate the groupcast This shows the periodicity of the message.

[0149] In some cases, the first UE may send feedback information indicating the following incorrect reception of a groupcast message by the first UE.

[0150] In some cases, the feedback information may be based on a negative response (NACK). In some cases, the first UE may send an error message to the base station indicating that the coordinating UE has been lost.

[0151] In some examples, the first UE may transmit transmission parameters for its scheduled sidelink transmission to the first coordinating UE. In some examples, the timing of transmitting the transmission parameters for the scheduled sidelink transmission may be based on periodicity.

[0152] In some examples, the transmission parameters of a scheduled sidelink transmission may include one or more slots, frequency resources, and periodicity.

[0153] In some cases, the first UE may receive from the base station an allocation of radio resources for transmitting transmission parameters for the first UE's scheduled sidelink transmission.

[0154] In some cases, the transmission parameters of a scheduled sidelink transmission of the first UE may include the identifier of the first UE.

[0155] In some cases, the first UE may retransmit the transmission parameters for the scheduled sidelink transmission in response to receiving a negative acknowledgment (NACK).

[0156] The exemplary blocks and modules described in this disclosure with respect to various exemplary embodiments may be implemented or run using general-purpose processors, DSPs, ASICs, NACKs, or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general-purpose processors include, but are not limited to, microprocessors, any conventional processor, controllers, microcontrollers, or state machines. In some examples, the processor may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors using a DSP core, or any other such configuration).

[0157] The functions described herein may be implemented in hardware and software performed by a processor, firmware, or any combination thereof. Instructions or code may be stored on or transmitted on a computer-readable medium for the execution of these functions. Other examples of implementations of the functions disclosed herein are also included in the scope of this disclosure. The execution of the functions may be via elements located in the same physical location or distributed elements (e.g., in various locations), including the distribution of each part of the function so that it is performed in different physical locations.

[0158] Computer-readable media include, but are not limited to, non-temporary computer storage media. Non-temporary storage media can be accessed by general-purpose or special-purpose computers. Examples of non-temporary storage media include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), and flat-panel memory. Non-temporary media include, but are not limited to, memory, compact disc (CD)-ROM or other optical disc storage, magnetic disc storage, or other magnetic storage devices. Non-temporary media can be used to transport or store desired program code means (e.g., instructions and / or data structures) and can be accessed by general-purpose or application-specific computers or general-purpose or application-specific processors. In some examples, software / program code may be transmitted from remote resources (e.g., websites, servers, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. Combinations of the above examples are also included within the scope of computer-readable media.

[0159] To the extent used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. Lists of items may be used in conjunction with phrases such as "at least one of" or "one or more of". For example, the list "at least one of A, B, or C" includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A, B, and C). Also, to the extent used in this disclosure, when a list of conditions is used in conjunction with the phrase "based on", it shall be understood as "based on at least part" of that set of conditions, rather than "based solely on" that set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B, and this also does not exceed the scope of this disclosure.

[0160] In this specification, the terms “comprise, include, or contain” are used interchangeably and may have the same meaning, and are interpreted as inclusive and open. The term “comprise, include, or contain” can be used with a list of elements to indicate that at least all of the elements listed in the list are present, but other elements not included in the list may also be present. For example, if A includes B and C, then both {B, C} and {B, C, D} are included in the scope of A.

[0161] This disclosure describes exemplary configurations in relation to the accompanying drawings, but these do not necessarily represent all possible implementations or all configurations included within the scope of this disclosure. The term “exemplary” should not be interpreted as “preferred” or “advantageous compared to other examples,” but rather as “example, case, or illustration.” By reading this disclosure, including the description of embodiments and drawings, a person skilled in the art will see that the technology disclosed herein can be implemented using alternative embodiments. A person skilled in the art will see that by combining these embodiments or certain features of the embodiments described herein, one can arrive at yet another embodiment for practicing the technology described herein. Therefore, this disclosure is not limited to the examples and designs described herein, but is in the broadest possible scope that is consistent with the principles and novel features disclosed herein.

[0162] Article 1. Equipment used in wireless communication: Antennas used for transmitting electromagnetic signals, Memory that holds computer-readable code, The device is instructed to transmit an instruction that includes at least one of the following: information that the first UE is designated as a coordinating UE for coordinating sidelink transmissions of multiple additional UEs, or information that identifies the designated coordinating UE. Send one or more groupcast transmission parameters to send sidelink transmission parameters to multiple additional UEs. A processor that executes computer-readable code, Includes.

[0163] Paragraph 2 In the apparatus of Paragraph 1, one or more groupcast transmission parameters indicate one or more of the transmission occasions and radio resources for groupcast messages.

[0164] Paragraph 3 In the apparatus referred to in Paragraph 1, one or more groupcast transmission parameters include information that identifies a schedule for the transmission of groupcast messages.

[0165] Paragraph 4 In the apparatus referred to in paragraph 1, the apparatus transmitting instructions by the first UE includes transmitting a radio resource control (RRC) message containing information that the first UE is designated as a coordinating UE.

[0166] Paragraph 5: In the apparatus referred to in paragraph 1, the transmission of one or more groupcast transmission parameters by the apparatus is based on the transmission of a radio resource control (RRC) message containing information identifying one or more groupcast transmission parameters.

[0167] In the apparatus of paragraph 5, the radio resource control (RRC) message includes, in a first part, information that the first UE is designated as a coordinating UE, and in a second part, information identifying one or more groupcast transmission parameters.

[0168] Paragraph 7 In the apparatus of paragraph 1, the transmission of instructions by the apparatus includes receiving downlink control information, the value of a field in the downlink control information includes information that the first UE is designated as a coordinating UE.

[0169] Paragraph 8: In the apparatus referred to in paragraph 1, the transmission of one or more groupcast transmission parameters by the apparatus is based on the reception of downlink control information which includes information identifying one or more groupcast transmission parameters.

[0170] Section 9 The apparatus described in Section 1 is further configured to transmit information identifying one or more second UEs.

[0171] Paragraph 10 The apparatus described in paragraph 1 is further configured to identify the cooperating UE based on its geographical location.

[0172] Paragraph 11 The apparatus described in paragraph 1 is further configured to cancel at least reserved transmission resources.

[0173] Section 12 Methods of mobile communication, including sidelink transmission: The base station transmits an instruction that includes at least one of the following: information that the first UE has been designated as a coordinating UE for coordinating sidelink transmissions of multiple additional UEs, or information identifying the designated coordinating UE. The base station transmits one or more groupcast transmission parameters to send sidelink transmission parameters to multiple additional UEs, Includes.

[0174] Paragraph 13 In the method of paragraph 12, one or more groupcast transmission parameters indicate one or more of the occasion for sending a groupcast message and / or the radio resource.

[0175] Paragraph 14 In the method of paragraph 12, one or more groupcast transmission parameters include information that identifies the schedule for the transmission of groupcast messages.

[0176] Paragraph 15: In the method of paragraph 12, the transmission of instructions by the first UE includes transmitting a radio resource control (RRC) message containing information that the first UE has been designated as a coordinating UE.

[0177] Paragraph 16: In the method of paragraph 15, transmitting one or more groupcast transmission parameters is based on transmitting a radio resource control (RRC) message containing information identifying one or more groupcast transmission parameters.

[0178] Paragraph 17 In the method of paragraph 16, the radio resource control (RRC) message includes, in a first part, information that the first UE is designated as a coordinating UE, and in a second part, information identifying one or more groupcast transmission parameters.

[0179] Paragraph 18: In the method of paragraph 12, transmitting instructions includes transmitting downlink control information, the value of a field in the downlink control information includes information that the first UE is designated as a coordinating UE.

[0180] Paragraph 19: In the method of paragraph 12, transmitting one or more groupcast transmission parameters is based on receiving downlink control information which includes information identifying one or more groupcast transmission parameters.

[0181] Paragraph 20 further includes transmitting information that identifies one or more second UEs in the manner of paragraph 12.

[0182] Paragraph 21 further includes identifying the coordinated UE on a geographical basis in the method of paragraph 12.

[0183] Paragraph 22 The method of paragraph 12 further includes canceling at least reserved transmission resources.

[0184] Paragraph 23 In devices used for wireless communication, Antennas used for transmitting electromagnetic signals, Memory that holds computer-readable code, A processor for executing computer-readable code that causes the device to receive instructions that a first UE is a coordinating UE for the coordination of sidelink transmissions of one or more second UEs, receive one or more groupcast transmission parameters, identify sidelink transmission parameters associated with one or more second UEs, the first UE utilizes the identification of sidelink transmission parameters to avoid collisions or half-duplex conflicts between sidelink transmissions of one or more second UEs, causes one or more second UEs to send a groupcast message, the groupcast includes sidelink transmission parameters for one or more second UEs, and the transmission of the groupcast message is based on the received groupcast transmission parameters, Includes.

[0185] Paragraph 24: In the apparatus described in Paragraph 23, the apparatus transmits a groupcast message at a predetermined time.

[0186] Paragraph 25: In the apparatus of paragraph 23, one or more group cast transmission parameters This includes information that identifies the schedule for transmitting groupcast messages.

[0187] Paragraph 26 The apparatus described in Paragraph 23 is further configured to identify at least a portion of the transmission parameters of one or more second user terminals (UEs) based on at least one previously received transmission from one or more second UEs.

[0188] Paragraph 27: In the apparatus of paragraph 23, the apparatus receives instructions from a first UE based on at least one of receiving a radio resource control (RRC) message containing information that the first UE is designated as a coordinating UE, or receiving downlink control information in which the value of a field contains information that the first UE is designated as a coordinating UE.

[0189] Paragraph 28: In the apparatus described in paragraph 23, the apparatus receives one or more groupcast transmission parameters based on at least one of receiving a resource radio resource control (RRC) message containing information identifying one or more groupcast transmission parameters, or receiving downlink control information containing information identifying one or more groupcast transmission parameters.

[0190] In the apparatus described in paragraph 23, the apparatus transmits groupcast messages via the physical sidelink shared channel (PSSCH) and based on the reception of downlink control information including PSSCH transmission parameters.

[0191] Paragraph 30: In the apparatus described in paragraph 23, the apparatus performs sidelink transmission parameter identification, which includes identifying sidelink transmission parameters based on information identifying one or more second UEs.

[0192] In the apparatus described in paragraph 31, paragraph 23, the sidelink transmission parameters include a set of resources preferred for one or more second UEs or a set of resources unfavorable for one or more second UEs.

[0193] In the apparatus described in paragraph 32 and paragraph 23, the processor determines the sidelink transmission parameters with respect to the detection results of the transmission parameters of one or more second UEs. Expected resource collision or expected half-duplex conflict in sidelink transmission It is configured to execute instructions that are identified based on at least one of the following.

[0194] In the apparatus of paragraph 23, the processor is configured to execute instructions that identify sidelink transmission parameters based on detected resource collisions or detected half-duplex conflicts in the sidelink transmission.

[0195] Section 34 Methods of mobile communication, including sidelink transmission: The first user terminal (UE) receives an instruction that the first UE is a coordinating UE for the sidelink transmission coordination of one or more second UEs, The first UE receives one or more group cast transmission parameters, The first UE identifies sidelink transmission parameters associated with one or more second UEs, the first UE utilizes the identification of sidelink transmission parameters to avoid collisions or half-duplex conflicts between the sidelink transmissions of one or more second UEs, The first UE sends a groupcast message to one or more second UEs, the groupcast transmission parameters include sidelink transmission parameters for one or more second UEs, and the transmission of the groupcast message is received Based on the group cast transmission parameters, Includes.

[0196] Paragraph 35: Sending a groupcast message in the manner of Paragraph 34 includes sending a groupcast message at a predetermined time.

[0197] Paragraph 36: In the method of paragraph 34, one or more groupcast transmission parameters indicate one or more of the occasions for sending a groupcast message and the radio resources.

[0198] Paragraph 37 In the method of paragraph 36, one or more groupcast transmission parameters include information that identifies a schedule for the transmission of groupcast messages.

[0199] Paragraph 38 The method of paragraph 34 further includes identifying at least a portion of the transmission parameters of one or more second user terminals (UEs) based on at least one previously received transmission from one or more second UEs.

[0200] Paragraph 39: Identifying sidelink transmission parameters in the method of paragraph 38 includes identifying sidelink transmission parameters based on at least an identified portion of transmission parameters.

[0201] Paragraph 40: In the method of paragraph 34, receiving instructions by the first UE includes receiving a radio resource control (RRC) message containing information that the first UE has been designated as a coordinating UE.

[0202] Paragraph 41: In the method of paragraph 34, receiving instructions includes receiving downlink control information, the value of a field in the downlink control information includes information that the first UE is designated as a coordinating UE.

[0203] In the method of paragraph 42, receiving one or more groupcast transmission parameters is based on receiving a radio resource control (RRC) message containing information identifying one or more groupcast transmission parameters.

[0204] In the method of paragraph 42, the reception of one or more groupcast transmission parameters by the first UE is based on the reception of downlink control information which includes information identifying one or more groupcast transmission parameters.

[0205] In the method of paragraph 43, transmitting information identifying one or more groupcast transmission parameters to one or more second UEs includes transmitting a groupcast message based on receiving downlink control information including PSSCH transmission parameters via a physical sidelink shared channel (PSSCH).

[0206] Paragraph 44 The method of paragraph 34 further includes the first UE receiving information identifying one or more second UEs.

[0207] Paragraph 45: Identifying sidelink transmission parameters in the method of Paragraph 44 includes identifying sidelink transmission parameters based on information that identifies one or more second UEs.

[0208] Paragraph 46 In the method of paragraph 34, one or more second UEs by the first UE This further includes receiving feedback information in response to the incorrect reception of a groupcast message by at least one of the following:

[0209] Paragraph 47 The method of paragraph 46 further includes the first UE retransmitting a groupcast message in response to the receipt of feedback information.

[0210] In the method of paragraph 46, the feedback information corresponds to a negative response (NACK).

[0211] In the method of paragraph 46, receiving feedback information includes receiving feedback information via a physical sidelink control channel (PSCCH).

[0212] Paragraph 50 The method of paragraph 34 further includes the first UE receiving a command instructing the retransmission of the groupcast message.

[0213] Paragraph 51 In the method of paragraph 50, the command instructing retransmission corresponds to at least one of downlink control information and media access control (MAC) control elements (MAC CE).

[0214] The method described in paragraph 52, paragraph 34, further includes receiving transmission parameters for a scheduled sidelink transmission associated with one or more UEs from one or more second UEs.

[0215] In the method of paragraph 52, the first UE identifies sidelink transmission parameters for one or more second user terminals (UEs) based, at least in part, on the received transmission parameters of the scheduled sidelink transmission.

[0216] Paragraph 54: In the method of paragraph 52, receiving transmission parameters for a scheduled sidelink transmission includes receiving transmission parameters on a periodic basis.

[0217] Paragraph 55 In the method of paragraph 52, the transmission parameters of the scheduled sidelink transmission include one or more of slots, frequency resources, and periodicity.

[0218] Paragraph 56 The method of paragraph 52 further includes the first UE receiving from the base station a radio resource allocation for receiving transmission parameters for scheduled sidelink transmissions of one or more second UEs.

[0219] In the method of paragraph 52, the transmission parameters for a scheduled sidelink transmission of one or more second UEs include the respective identifier associated with one or more second UEs.

[0220] Paragraph 58 The method of paragraph 52 further includes sending one or more negation acknowledgments (NACKs) to one or more second UEs in response to the erroneous receipt of a message containing transmission parameters for a scheduled sidelink transmission to one or more second UEs.

[0221] Paragraph 59 In the method of Paragraph 58, transmitting one or more negative responses is performed with respect to one or more third user terminals (UEs) of which one or more second UEs have incorrectly received the transmission parameters for the sidelink transmission scheduled with respect to it. It breaks.

[0222] Paragraph 60 In the method, The first user terminal (UE) receives an instruction that the first UE is associated with one or more cooperative UEs, The first UE receives the groupcast transmission parameters of the first coordinating UE from one or more coordinating UEs, The first UE receives a groupcast message containing sidelink transmission parameters, the sidelink transmission parameters being configured to avoid collisions or half-duplex conflicts related to the sidelink transmission of the first UE. The first UE transmits sidelink data to the second UE based on the sidelink transmission parameters received from the first coordinating UE, Includes.

[0223] Paragraph 61 The method of paragraph 60 further includes the first UE receiving an identifier associated with one or more cooperative UEs.

[0224] Paragraph 62: In the method of paragraph 60, receiving a groupcast message includes receiving a groupcast message at a predetermined time.

[0225] Paragraph 63: In the method of paragraph 60, one or more groupcast transmission parameters include information identifying one or more of the occasions for sending a groupcast message and one or more radio resources.

[0226] Paragraph 64 In the method of Paragraph 63, one or more groupcast transmission parameters indicate the periodicity of the groupcast message.

[0227] Paragraph 65 The method of paragraph 60 further includes sending feedback information indicating that the first UE has erroneously received the groupcast message.

[0228] Paragraph 66: In the method of Paragraph 65, the feedback information indicates a negative response.

[0229] Paragraph 67 The method of paragraph 66 further includes transmitting an error message to the base station in response to a predetermined number of consecutive errors.

[0230] Paragraph 68 The method of paragraph 60 further includes the first UE transmitting the transmission parameters of the first UE's scheduled sidelink transmission to the first coordinating UE.

[0231] Paragraph 70: In the method of paragraph 68, transmitting transmission parameters for a scheduled sidelink transmission includes transmitting transmission parameters on a periodic basis.

[0232] In the method of paragraph 68, the transmission parameters of the scheduled sidelink transmission include one or more slots, frequency resources, and periodicity.

[0233] The method of paragraph 68 further includes receiving a radio resource allocation from the base station for transmitting transmission parameters for a scheduled sidelink transmission of the first UE.

[0234] Paragraph 73 In the method of paragraph 68, the scheduled sidelink of the first UE The transmission parameters include the identifier of the first UE.

[0235] Paragraph 74 The method of paragraph 68 further includes, in response to the first UE receiving a negative acknowledgment (NACK), retransmitting the transmission parameters for the scheduled sidelink transmission.

[0236] Section 75 Devices used in wireless communication: Antennas used for transmitting electromagnetic signals, Memory that holds computer-readable code, A processor that executes computer-readable code causing the device to receive instructions that a first UE is associated with one or more coordinating UEs, to receive group cast transmission parameters of the first coordinating UE among the one or more coordinating UEs, to receive a group cast message containing sidelink transmission parameters, the sidelink transmission parameters being configured to avoid collisions or half-duplex conflicts in the sidelink transmission of the first UE, and to transmit sidelink data based on the sidelink transmission parameters received from the first coordinating UE, Includes.

[0237] Paragraph 76 The device described in Paragraph 75 is further configured to receive identifiers associated with one or more cooperative UEs.

[0238] Paragraph 77: In the apparatus described in Paragraph 75, the apparatus receives groupcast messages at a predetermined time.

[0239] In the apparatus of paragraph 75, one or more groupcast transmission parameters include information that identifies one or more of the occasions for sending a groupcast message and the radio resources.

[0240] In the apparatus described in paragraph 78, one or more groupcast transmission parameters indicate the periodicity of the groupcast message.

[0241] In the apparatus described in paragraph 80, paragraph 75, the apparatus is further configured to transmit feedback information indicating that the first UE has erroneously received a groupcast message.

[0242] This application is for "INTER-UE COORDINATION FOR SIDELINK" We claim the benefits of U.S. Provisional Patent Application No. 63 / 077,747, filed on 14 September 2020, entitled “ENHANCEMENTS”. U.S. Provisional Patent Application No. 65 / 077,747 is incorporated herein by reference.

Claims

1. A method of mobile communication including sidelink transmission, The first UE receives one or more groupcast transmission parameters, Sidelink transmission parameters associated with one or more second UEs by the first UE, including auxiliary information indicating undesirable resource sets as used by the one or more second UEs based on resource collision detection and / or prediction information, to identify sidelink transmission parameters for avoiding collisions or half-duplex conflicts between the sidelink transmissions of the one or more second UEs, The first UE sends a groupcast message to one or more second UEs, Includes, The groupcast message includes sidelink transmission parameters for the one or more second UEs, and the transmission of the groupcast message is performed based on the one or more groupcast transmission parameters. method.

2. A device provided by the first UE used in wireless communication, Antennas used for transmitting electromagnetic signals, Memory that holds computer-readable code, Includes a processor for executing the computer-readable code, The processor is provided to the device, To receive one or more groupcast transmission parameters, Sidelink transmission parameters associated with one or more second UEs, including auxiliary information indicating undesirable resource sets as used by the one or more second UEs based on resource collision detection and / or prediction information, to identify sidelink transmission parameters for avoiding collisions or half-duplex conflicts between sidelink transmissions of the one or more second UEs, This includes causing the groupcast message to be sent to one or more second UEs, The group cast message is for the side of one or more second UEs. The groupcast message includes link transmission parameters, and the transmission of the groupcast message is performed based on one or more groupcast transmission parameters. Device.

Images