System and method for inter-device communication
The system enables UEs to manage sidelink carrier aggregation and report abnormal conditions, enhancing sidelink communication reliability and data rates to meet high data rate and proximity service demands.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2022-09-16
- Publication Date
- 2026-06-01
AI Technical Summary
Conventional network-centric cellular networks have limited capabilities for high data rates and proximity services, and device-to-device communication is needed to address these shortcomings, but existing solutions lack efficient methods for managing carrier aggregation in sidelink communications.
The system and method enable UEs to determine network support for sidelink carrier aggregation, report abnormal conditions, and perform carrier reselection procedures to improve reliability and data rates in sidelink communications.
Enhances the reliability, data rate, and latency of sidelink communications by implementing carrier aggregation and managing abnormal conditions, reducing the burden on cellular networks and improving user experience.
Smart Images

Figure 0007868168000001 
Figure 0007868168000002 
Figure 0007868168000003
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to wireless communication, and more specifically, to abnormal states in device - to - device communication.
Background Art
[0002] Side - link (SL) communication refers to radio - wave communication between two or more user equipment (UE). In this type of communication, two or more UEs that are geographically close to each other can communicate without being routed through a network (e.g., a base station (BS)) or a core network. Data transmission in SL communication is thus different from typical cellular network communication, which includes transmitting data to the network and receiving data from the network. In SL communication, data is transmitted directly from a source UE to a target UE, for example, through an integrated air interface (e.g., a PC5 interface), without passing through the network.
Summary of the Invention
Means for Solving the Problems
[0003] The exemplary arrangements disclosed herein are aimed at solving one or more of the problems presented in the prior art and providing additional features that will become readily apparent when considered in conjunction with the accompanying drawings and the following detailed description. According to various arrangements, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is to be understood that these arrangements are presented by way of example and not limitation, and that various modifications to the disclosed arrangements can be made within the scope of the present invention, which will be apparent to those skilled in the art upon a thorough reading of the present disclosure.
[0004] Some arrangements of this disclosure relate to systems, methods, apparatus, and non-transient computer-readable media relating to a first UE receiving information from a network indicating that the network supports SL carrier aggregation (CA). The first UE communicates SL communications with a second UE.
[0005] Some arrangements of this disclosure relate to systems, methods, apparatus, and non-transient computer-readable media relating to a first UE communicating with a second UE in SL communication. The first UE reports to the network, based on quality of service (QoS) flow, at least one frequency to be used in the SL communication with the second UE.
[0006] Some arrangements of this disclosure relate to systems, methods, apparatus, and non-transient computer-readable media relating to a network receiving information from a first UE indicating that the network supports SL CA. The first UE communicates SL communication with a second UE. The network receives from the first UE a report of at least one of an abnormal condition on the first carrier or an abnormal condition recovery on the first carrier.
[0007] The above and other aspects, as well as their implementation, will be described in detail by the drawings, descriptions, and claims. The present invention provides, for example, the following: (Item 1) A wireless communication method, The first wireless communication device receives information from the network, To determine whether the aforementioned network supports sidelink (SL) carrier aggregation (CA) and Methods that include... (Item 2) The method according to item 1, further comprising the first wireless device reporting to the network, by the first wireless communication device, at least one of an SL abnormal condition on the first carrier or a recovery of an SL abnormal condition on the first carrier, in response to the first wireless device determining that the network supports the SL CA. (Item 3) The method according to item 1, wherein the first wireless communication device determines that the network supports SL CA, and the information includes an indication that the network supports SL CA. (Item 4) The method according to item 1, in response to a determination that the aforementioned information includes configurations for two or more SL carriers, the first wireless communication device determines that the network supports the SL CA. (Item 5) A wireless communication method, The first wireless communication device determines that at least one condition is met to trigger a reselection procedure, In response to a determination that at least one condition for triggering the carrier reselection procedure is met, the carrier reselection procedure is triggered. Methods that include... (Item 6) The carrier reselection procedure is the method according to item 5, wherein the first wireless communication device selects at least one carrier as a candidate carrier. (Item 7) The method according to item 5, wherein the career reselection procedure includes selecting a career from at least one candidate career. (Item 8) The above at least one condition is, An abnormal condition is detected on the second carrier. The second carrier for the destination is included in the list of undesirable carriers provided by the second UE. The second carrier for the aforementioned destination is included in the list of unauthorized carriers provided by the second UE. Receiving an indication from the SL Radio Link Control (RLC) entity that the maximum number of retransmissions for the destination has been reached, The Radio Resource Control (RRC) reconfiguration timer has expired for the destination. Receiving an indication from a Media Access Control (MAC) entity that the maximum number of continuous hybrid automatic repeating request (HARQ) intermittent transmissions (DTX) for a specific destination has been reached, or Receiving a consistency check failure indication from an SL Packet Data Convergence Protocol (PDCP) entity regarding an SL radio bearer (RB) for the said destination. The method described in item 5, including one or more of the following. (Item 9) The method according to item 6, wherein the carrier is selected as the candidate carrier based on a list of preferred carriers provided by the second UE. (Item 10) The carrier is selected as a candidate carrier based on at least one condition for selecting a carrier for SL communication. At least one condition for selecting the aforementioned carrier is, No abnormal condition is detected on the carrier. The channel congestion on the carrier falls below a threshold. The carrier is excluded from the list of unauthorized carriers provided by the second UE, or The carrier is excluded from the list of undesirable carriers provided by the second UE. The method described in item 6, including one or more of the following. (Item 11) The carrier among the candidate carriers will be selected based on at least one condition for a candidate carrier for SL communication, At least one condition for selecting the aforementioned carrier is, The abnormal condition is not detected on the third carrier. The channel congestion on the third carrier falls below a threshold. The third carrier is excluded from the list of unauthorized carriers provided by the second UE, or The third carrier is excluded from the list of undesirable carriers provided by the second UE. The method described in item 7, including one or more of the following. (Item 12) A wireless communication method, The first wireless communication device communicates with the second wireless communication device via SL communication. The first wireless communication device reports to the network, based on the quality of service (QoS) flow, at least one frequency used in SL communication with the second UE. Methods that include... (Item 13) The method of item 12, wherein reporting at least one frequency used in SL communication with the second UE based on the QoS flow includes reporting the at least one frequency associated with the QoS flow for each of the multiple services of the SL communication. (Item 14) The method of item 12, wherein reporting at least one frequency used in SL communication with the second UE based on the QoS flow includes reporting the QoS flow for each of the multiple services of the SL communication for each of the at least one frequency. (Item 15) The method of item 12, wherein reporting at least one frequency used in SL communication with the second UE based on the QoS flow includes reporting a mapping for each of the multiple services of the SL communication that maps the at least one frequency to the QoS flow. (Item 16) The method of item 12, further comprising passing the at least one frequency from an upper layer to a lower layer, wherein the SL communication is performed within the lower layer for the QoS flow using the at least one frequency. (Item 17) The method according to item 16, wherein the QoS flow associated with the at least one frequency is passed by the first UE from the upper layer to the lower layer using the at least one frequency. (Item 18) The method according to item 16, wherein each of the at least one frequency is an overlapping frequency between two or more of the multiple services for the QoS flow of the SL communication. (Item 19) The first wireless communication device uses at least one frequency for all of the multiple services for the same QoS flow, as described in item 18. (Item 20) The first wireless communication device, At least one frequency for each of at least one service type, At least one service type for each of the aforementioned at least one frequency, The at least one service type and the at least one frequency associated with the at least one service type, or The at least one frequency and the at least one service type associated with the at least one frequency The method described in item 12, further comprising passing at least one of the above from a higher layer to a lower layer. (Item 21) The method according to item 12, wherein the at least one frequency is at least one overlapping frequency of all of the at least one service type associated with the destination identifier. (Item 22) A wireless communication method, The first wireless communication device receives the synchronization configuration from the network, The first wireless communication device selects a synchronization reference source based on a synchronization configuration for the frequency used for sidelink (SL) communication. Methods that include... (Item 23) The synchronization reference source is the method described in item 22, comprising at least one of a Global Navigation Satellite System (GNSS), a cell, or a user instrument (UE). (Item 24) The method according to item 23, wherein the cell is selected as a synchronization reference source for the frequency used for the SL communication in response to a determination that the frequency is within a message scheduled by the cell. (Item 25) The method according to item 23, wherein the cell is selected as a synchronization reference source for the frequency used for the SL communication in response to a determination that the frequency is within a message scheduled by the cell's physical downlink control channel (PDCCH). (Item 26) The method according to item 23, wherein the cell is selected as a reference for the frequency used for the SL communication in response to the first communication device determining that the first wireless communication device is within the coverage of the cell. (Item 27) The aforementioned message may be a system information block, as described in item 24. (Item 28) A wireless communication method, The first wireless communication device receives a System Information Block (SIB) from the network, The first wireless communication device ignores the SIB in response to connecting to another network via the second wireless communication device. Methods that include... (Item 29) The method described in item 28, wherein the SIB is SIB12. (Item 30) A wireless communication method, The network receives information from a first wireless communication device indicating that the network supports sidelink (SL) carrier aggregation (CA), and the first wireless communication device communicates with a second wireless communication device SL communication. The network receives reports from the first wireless communication device of at least one of the following: an abnormal condition on the first carrier or recovery of an SL abnormal condition on the first carrier. Methods that include... [Brief explanation of the drawing]
[0008] Various exemplary arrangements of this solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of this solution to facilitate the reader's understanding of the solution. Therefore, the drawings should not be considered as limitations on the scope, scope, or availability of this solution. Note that, for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0009] [Figure 1A] Figure 1A is a schematic diagram illustrating exemplary wireless communication networks with various arrangements.
[0010] [Figure 1B] Figure 1B is a schematic diagram illustrating an exemplary wireless communication system for transmitting and receiving downlink, uplink, and / or SL communication signals in various arrangements.
[0011] [Figure 2]Figure 2 illustrates exemplary scenarios for SL communication with various arrangements.
[0012] [Figure 3] Figure 3 is a flowchart illustrating exemplary methods for managing CA-based SL wireless communication using various arrangements.
[0013] [Figure 4] Figure 4 is a flowchart illustrating exemplary methods for managing CA-based SL wireless communication using various arrangements.
[0014] [Figure 5] Figure 5 is a flowchart illustrating exemplary methods for managing CA-based SL wireless communication using various arrangements.
[0015] [Figure 6] Figure 6 is a flowchart illustrating exemplary methods for managing SL wireless communication using various arrangements. [Modes for carrying out the invention]
[0016] Detailed explanation Various exemplary arrangements of this solution are described below with reference to accompanying diagrams to enable those skilled in the art to prepare and use this solution. As will be obvious to those skilled in the art, after careful reading of this disclosure, various changes or modifications to the embodiments described herein can be made without departing from the scope of this solution. Therefore, this solution is not limited to the exemplary arrangements and uses described and illustrated herein. In addition, the particular order or hierarchy of steps in the methods disclosed herein is merely an exemplary approach. Based on design preferences, the particular order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and that this solution is not limited to the particular order or hierarchy presented unless expressly otherwise stated.
[0017] With the emergence of wireless multimedia services, user demand for high data rates and user experience continues to increase, which represents a higher requirement for the system capacity and coverage of conventional cellular networks. In addition, public safety, social networking, near-field data sharing, and local advertising are gradually expanding the need for proximity services, which enable users to identify and communicate with nearby users or objects. Conventional network-centric cellular networks have limited high data rate capabilities and support for proximity services. In this context, device-to-device (D2D) communication has emerged to address the shortcomings of the network-centric model. The application of D2D technology can reduce the burden on cellular networks, reduce battery power consumption of UEs, increase data rates, improve the robustness of network infrastructure, and thus meet the aforementioned requirements for high data rate services and proximity services. D2D technology is also referred to as proximity services (ProSe), unidirectional / sidechain / SL communication, etc.
[0018] To improve the reliability, data rate, and latency of SL communications, carrier aggregation (CA) can be implemented for SL communications. In CA, two or more component carriers (CCs) are aggregated to support a wider transmission bandwidth in the frequency domain. In some embodiments, a vehicle UE can perform SL reception and transmission simultaneously on one or more CCs. The arrangements disclosed herein relate to data partitioning and data duplication based on CA.
[0019] Referring to Figure 1A, an exemplary wireless communication network 100 is shown. Wireless communication network 100 illustrates group communication within a cellular network. In a wireless communication system, network-side communication nodes or networks may include next-generation NodeBs (gNBs), E-Utran NodeBs (also known as evolved NodeBs, eNodeBs, or eNBs), picostations, femtostations, transmission / receiving points (TRPs), access points (APs), etc. Terminal-side nodes or UEs may include devices such as mobile devices, smartphones, cellular phones, personal digital assistants (PDAs), tablets, laptop computers, wearable devices, and vehicles with in-vehicle communication systems. In Figure 1A, the network-side and terminal-side communication nodes are represented by network 102 and UEs 104a and 104b, respectively. In some arrangements, network 102 and UEs 104a / 104b are sometimes also referred to as “wireless communication nodes” and “wireless communication devices,” respectively. Such communication nodes / devices can perform wireless communication.
[0020] In the arrangement illustrated in Figure 1A, network 102 may define a cell 101 in which UEs 104a and 104b are located. UEs 104a and / or 104b can be moving or stationary within the coverage of cell 101. UE 104a can communicate with network 102 via communication channel 103a. Similarly, UE 104b can communicate with network 102 via communication channel 103b. In addition, UEs 104a and 104b can communicate with each other via communication channel 105. The communication channels 103a and 104b between the individual UEs and the network can be implemented using an interface such as a Uu interface, also known as a Universal Mobile Telecommunications System (UMTS) air interface. The communication channel 105 between UEs is an SL communication channel, which can be implemented using the PC5 interface, and is introduced to address high-speed and high-density applications such as D2D communication, vehicle-to-vehicle (V2V) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, or equivalent. In some instances, vehicle network communication modes may be collectively referred to as vehicle-to-vehicle and vehicle-to-infrastructure (V2X) communication. Network 102 is connected to the core network (CN) 108 through an external interface 107, for example, the Iu interface.
[0021] In some embodiments, a remote UE (e.g., UE104b) that does not communicate directly with network 102 or CN108 (e.g., communication channel link 103b is not established) communicates directly with network 102 and CN108, or indirectly with network 102 and CN108 via another relay UE (e.g., UE104a) that can communicate directly with network 102 and CN108, or indirectly with network 102 and CN108 using SL communication channel 105 via another relay UE (e.g., UE104a) that can communicate directly with network 102 and CN108.
[0022] Figure 1B illustrates a block diagram of an exemplary wireless communication system for transmitting and receiving downlink, uplink, and SL communication signals in several arrangements of the present disclosure. In some arrangements, the system can transmit and receive data within a wireless communication environment, such as the wireless communication network 100 in Figure 1A, as described above.
[0023] The system generally includes a network 102 and UEs 104a and 104b, as illustrated in Figure 1A. Network 102 includes a network transceiver module 110, a network antenna 112, a network memory module 116, a network processor module 114, and a network communication module 118, each module being coupled and interconnected to one another via a data communication bus 120 as needed. UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a, each module being coupled and interconnected to one another via a data communication bus 140a as needed. Similarly, UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b, each module being coupled and interconnected to one another via a data communication bus 140b as needed. Network 102 communicates with UEs 104a and 104b via one or more of the communication channels 150, which may be any radio channel or other medium known in the art, suitable for transmitting data as described herein.
[0024] The system may further include any number of modules other than those shown in Figure 1B. Those skilled in the art will understand that various illustrative blocks, modules, circuits, and processing logics described in relation to the arrangements disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate the interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software depends on the specific application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a manner suitable for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.
[0025] Radio transmission from one of the UE104a and 104b antennas to the antenna of network 102 is known as uplink transmission, and radio transmission from the antenna of network 102 to one of the UE104a and 104b antennas is known as downlink transmission. According to some arrangements, UE transceiver modules 130a and 130b may be referred to herein as uplink transceivers or UE transceivers, respectively. Uplink transceivers may each include a transmitter and receiver network coupled to separate antennas 132a and 132b. A duplex switch may, alternatively, couple the uplink transmitter or receiver to the uplink antenna in a time-duplex configuration. Similarly, network transceiver module 110 may, according to this specification, be referred to as a downlink transceiver or network transceiver. Downlink transceivers may each include an RF transmitter and receiver network coupled to antenna 112. A downlink duplex switch may, alternatively, couple the downlink transmitter or receiver to antenna 112 in a time-duplex configuration. The operation of transceivers 110 and 130a and 130b is coordinated in time so that the downlink transmitter is coupled to antenna 112 and the uplink receiver is coupled to antennas 132a and 132b for receiving transmissions over radio communication channel 150. In some arrangements, UEs 104a and 104b can communicate with network 102 via radio communication channel 150 through separate antennas 132a and 132b using UE transceivers 130a and 130b. Radio communication channel 150 can be any radio channel or other medium known in the art that is suitable for downlink and / or uplink transmission of data as described herein. UEs 104a and 104b can communicate with each other via radio communication channel 170. Radio communication channel 170 can be any radio channel or other medium that is suitable for SL transmission of data as described herein.
[0026] The UE transceivers 130a and 130b and the network transceiver 110 are each configured to communicate via the radio data communication channel 150 and to cooperate with a suitably configured antenna arrangement capable of supporting specific radio communication protocols and modulation schemes. In some arrangements, the UE transceivers 130a and 130b and the network transceiver 110 are configured to support industrial standards such as Long-Term Evolution (LTE) and emerging 5G and 6G standards or equivalents. However, it should be understood that this disclosure is not necessarily limited to applications of specific standards and associated protocols. Rather, the UE transceivers 130a and 130b and the network transceiver 110 may be configured to support alternative or additional radio data communication protocols, including future standards or variations thereof.
[0027] Processor modules 136a, 136b, and 114 may each be implemented or realized with a general-purpose processor, associative memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate, or transistor logic, discrete hardware component, or any combination thereof, designed to perform the functions described herein. Thus, the processor may be realized as a microprocessor, controller, microcontroller, state machine, or equivalent. The processor may also be implemented as a combination of computing devices, for example, a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.
[0028] Furthermore, the methods and algorithms described in relation to the arrangements disclosed herein may be embodied directly in hardware, in firmware, in software modules executed by processor modules 114 and 136a and 136b, respectively, or in any practical combination thereof. Memory modules 116 and 134a and 134b may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In this regard, memory modules 116 and 134a and 134b may be coupled to processor modules 114 and 136a and 136b, respectively, so that processor modules 114 and 136a and 136b can read information from and write information to memory modules 116 and 134a and 134b, respectively. Memory modules 116, 134a, and 134b may also be integrated into their individual processor modules 114, 136a, and 136b. In some arrangements, memory modules 116, 134a, and 134b may each include cache memory to store temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 116, 134a, and 134b, respectively. Memory modules 116, 134a, and 134b may also each include non-volatile memory to store instructions to be executed by processor modules 114, 136a, and 136b, respectively.
[0029] The network interface 118 generally represents the hardware, software, firmware, processing logic, and / or other components of network 102 that enable bidirectional communication between the network transceiver 110 and other network components and communication nodes configured to communicate with network 102. For example, the network interface 118 may be configured to support Internet or WiMAX traffic. In a typical deployment, but not limited to, the network interface 118 provides an 802.3 Ethernet® interface so that the network transceiver 110 can communicate with conventional Ethernet®-based computer networks. Thus, the network interface 118 may include a physical interface for connection to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a specified operation or function, the terms “configured for” or “configured to” refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted, and / or arranged to perform a specified operation or function. The network interface 118 can enable network 102 to communicate with other networks or core networks via wired or wireless connections.
[0030] In some arrangements, UE104a and 104b can operate within a hybrid communication network, where the UEs communicate with network 102 and other UEs, e.g., 104a and 104b. As will be described in more detail below, UE104a and 104b support SL communication with other UEs as well as downlink / uplink communication between network 102 and UE104a and 104b. Generally, SL communication allows UE104a and 104b to establish direct communication links with other UEs, either from each other or from different cells, without requiring network 102 to relay data between the UEs.
[0031] Figure 2 is a schematic diagram illustrating an exemplary system 200 for SL communication in various arrangements. As shown in Figure 2, network 210 (network 102 in Figure 1A, etc.) broadcasts signals that are received by a first UE 220, a second UE 230, and a third UE 240. In Figure 2, UEs 220 and 230 are shown as vehicles with an in-vehicle communication network, while UE 240 is shown as a mobile device. As shown by SL, UEs 220-240 can communicate with each other (e.g., directly transmit and receive) via an air interface without automatic forwarding by a base station 210 or core network 250. This type of V2X communication is referred to as PC5-based V2X communication or V2X SL communication.
[0032] As used herein, when two UEs 104a or 104b communicate with each other via communication channel 105 / 170, the UE that transmits data to the other UE is referred to as the transmitting (TX) UE, and the UE that receives the data is referred to as the receiving (RX) UE.
[0033] In some embodiments, the network may not support SL CA. For example, the network may be unable to schedule SL resources across multiple carriers or provide SL configurations for multiple carriers. Several arrangements disclosed herein relate to the UE determining whether the network supports SL CA.
[0034] Figure 3 is a flowchart illustrating exemplary method 300 for managing CA-based SL radio communication in various arrangements. Referring to Figure 1A-3, method 300 can be implemented by a first UE (e.g., UE104a / 220), a second UE (e.g., UE104b / 230), and a network 102 / 210. Communication via SL radio communication channel 170 or the SL network is shown across the dashed line between the first UE and the second UE. Communication via radio communication channel 103a / 150 is shown across the dashed line between the first UE and the network.
[0035] In 310, the network transmits information indicating that the network supports SL CA. In 320, the UE receives information indicating that the network supports SL CA. In response to receiving such information, the UE may decide that the network supports SL CA. In some embodiments, the first UE decides that the network supports SL CA in response to a decision that the information includes an indication that the network supports SL CA. In some embodiments, the information indicating that the network supports SL CA includes a System Information Block (SIB). In response to a decision that the information includes a configuration for two or more SL carriers, the first UE decides that the network supports SL CA. For example, in response to receiving an SIB with a configuration for two or more SL carriers, the first UE may decide that the network supports SL CA. In some embodiments, information indicating that the network supports SL CA may include other information, messages, or signaling, such as radio resource control (RRC) signaling or media access control (MAC) control elements (CE), that explicitly indicate that SL CA is supported by the network.
[0036] In step 330, the first UE communicates with the second UE via SL communication. In step 340, the second UE communicates with the first UE via SL communication. For example, the first and second UEs send and receive signals and data to and from each other.
[0037] In step 345, the first UE determines at least one of the following: that an abnormal condition is detected on one carrier, or that the abnormal condition is recovered.
[0038] In 350, in response to the first wireless communication device deciding that the network supports SL CA, the first UE reports to the network at least one of the following: an SL anomaly on the first carrier or an SL anomaly recovery on the first carrier.
[0039] In 360, the network receives a report from the first UE of at least one of the following: an SL anomaly on the first carrier or an SL anomaly recovery on the first carrier. Thus, in embodiments in which two or more SL carriers are included in the SIB, the first UE reports an SL carrier anomaly to the network. In some arrangements, the first UE reports at least one of the following: an SL anomaly on the first carrier or an SL anomaly recovery on the first carrier, in response to the first UE deciding that the network supports SL CA.
[0040] In some arrangements, abnormal conditions include wireless link failure. In some embodiments, a UE such as a first UE may detect an abnormal condition relating to a carrier in the manner described herein and, in response, directly trigger an RLF on that carrier. In some embodiments, in response to the detection of an abnormal condition as described, the first UE may trigger an RLF on the carrier depending on whether the first UE determines that it is unable to recover from the abnormal condition relating to the carrier.
[0041] In some arrangements, the first UE determines an abnormal condition on the first carrier in response to detecting that the amount of missing feedback information relating to the first carrier reaches a maximum value (e.g., a predetermined threshold). The missing feedback information includes at least one of missing physical sidelink feedback channel (PSFCH) reception or missing hybrid automatic repeat request (HARQ) feedback reception. In some arrangements, the maximum value can consist of at least one of a network (e.g., a network), a second UE, etc.
[0042] For example, the first UE determines an abnormal state on the first carrier in response to the detection that the number of missing PSFCH receptions on at least one PSFCH receiving resource (e.g., opportunity) for the first carrier has reached a maximum missing PSFCH reception threshold. That is, the first UE communicates with the second UE via an SL connection and detects that an abnormal state has occurred on the first carrier in response to the determination that the maximum number of missing PSFCH receptions has been reached with respect to at least one PSFCH receiving resource for the first carrier. For example, the first UE determines an abnormal state on the first carrier in response to the determination that the number of missing HARQ feedbacks on at least one HARQ feedback resource (e.g., opportunity) for the first carrier has reached a maximum missing HARQ feedback threshold. That is, the first UE communicates with the second UE via an SL connection and detects that an abnormal state has occurred on the first carrier in response to the determination that the maximum number of missing HARQ feedbacks has been reached with respect to the HARQ feedback resource for the first carrier. For example, the first UE determines an abnormal condition on the first carrier in response to a decision that the number of missing PSFCH receptions for at least one PSFCH receiving resource for the first carrier has reached a maximum missing PSFCH reception threshold, with an affirmative-negative response selected. That is, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that the maximum number of missing PSFCH receptions for the PSFCH receiving resource for the first carrier has been reached, with the affirmative-negative response selected by at least one of the first UE, the second UE, or the network. For example, the first UE determines an abnormal condition on the first carrier in response to a decision that the number of missing PSFCH receptions for at least one PSFCH receiving resource for the first carrier has reached a maximum missing PSFCH reception threshold, with an affirmative-negative response selected.In other words, the first UE, communicating with the second UE via an SL connection, detects that an abnormal condition has occurred on the first carrier in response to a decision that it has reached the maximum number of missing PSFCH receptions with respect to PSFCH reception resources for the first carrier, and a negative limited response is selected, for example, by at least one of the first UE, the second UE, or the network.
[0043] In some arrangements, the first UE determines an abnormal state on the first carrier in response to a determination that the ratio of the amount of missing feedback information for the first carrier to the amount of intended feedback information for the first carrier reaches a maximum value (e.g., a predetermined threshold). The ratio may include at least one of the following: the number of missing PSFCH receptions for at least one PSFCH receiving resource for the first carrier to the number of intended PSFCH receptions for at least one PSFCH receiving resource, or the number of missing HARQ feedbacks for at least one HARQ feedback resource for the first carrier to the number of intended HARQ feedbacks for at least one HARQ feedback resource.
[0044] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that an affirmative-negative response is selected when the ratio of the number of missing PSFCH receptions for at least one PSFCH receiving resource for the first carrier to the number of intended PSFCH receptions for at least one PSFCH receiving resource reaches a PSFCH ratio threshold. That is, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that an affirmative-negative response is selected when the ratio of the number of missing PSFCH receptions on the first carrier to the number of intended PSFCH receptions on the first carrier reaches a threshold. With respect to group casts, in which affirmative-negative responses are used, in an embodiment, each RX UE (e.g., the first UE) sends HARQ feedback for a different PSFCH resource (e.g., at least one PSFCH receiving resource). For a given transmission, a TX UE (e.g., a second UE) is intended to receive N PSFCH receptions (intended HARQ feedback) for N PSFCH resources, where N is the group size. The group size is the number of RX UEs in the group.
[0045] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that an affirmative-negative response is selected when the ratio of the number of missing HARQ feedbacks for at least one HARQ feedback resource for the first carrier to the number of intended HARQ feedbacks for at least one HARQ feedback resource reaches a HARQ feedback ratio threshold. That is, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that an affirmative-negative response is selected when the ratio of the number of missing HARQ feedbacks to the number of intended HARQ feedbacks is higher than a threshold. With respect to group casts, in which affirmative-negative responses are used, in an embodiment, each RX UE (e.g., the first UE) transmits HARQ feedback for different PSFCH resources (e.g., at least one HARQ feedback resource). With respect to a given transmission, the TX UE (e.g., the second UE) is intended to receive N PSFCH receptions (intended HARQ feedback) for N HARQ feedback resources, where N is the group size. The group size is the number of RX UEs within the group.
[0046] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a determination that a ratio assessing channel congestion on the first carrier exceeds a threshold. For example, the first UE may detect that the channel utilization rate (CBR) of the resource pool on the first carrier is higher than a configured threshold, and the CBR indicates channel congestion (e.g., the higher the CBR, the greater the channel congestion). The CBR may include the ratio of subchannels with signal intensity higher than a threshold (e.g., measured using the Received Signal Strength Indicator (RSSI)) to the total number of subchannels on the carrier. The first UE can determine the CBR on the first carrier.
[0047] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that the number of retransmissions for a destination has reached the maximum retransmission value. For example, an SL radio link control (RLC) entity residing in the network, the first UE, or at least one of the second UE may indicate to the first UE that the maximum number of retransmissions for a particular destination has been reached.
[0048] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a determination that the RRC reconfiguration timer (e.g., T400) for the destination has expired. Timer T400 is started in response to the transmission of an RRC reconfiguration message for the SL and stopped in response to the reception of an RRC reconfiguration failure message or an RRC reconfiguration completion message for the SL.
[0049] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a decision that the number of consecutive HARQ intermittent transmissions (DTXs) for a destination has reached the maximum HARQ DTX value. A media access control (MAC) entity residing in the network, the first UE, or at least one of the second UE may indicate to the first UE that the maximum number of consecutive HARQ DTXs on the first carrier for a destination has been reached.
[0050] For example, the first UE detects that an abnormal condition has occurred on the first carrier in response to a determination that consistency has failed for at least one signaling radio bearer (SRB) for a destination (e.g., SL-Signaling Radio Bearer 2 (SL-SRB2) or SL-SRB3). An SL Packet Data Convergence Protocol (PDCP) entity residing on the first UE, the second UE, and one or more of the networks may send a consistency check failure indication to the first UE indicating consistency failure for at least one of SL-SRB2 or SL-SRB3 for the destination.
[0051] For example, the first UE determines that an abnormal condition on the first carrier has been recovered in response to receiving an indication corresponding to recovering an abnormal condition. In some embodiments, receiving an indication includes, by the first UE, receiving an SL carrier list from a network (e.g., the network) including the first carrier; by the first UE, receiving a first activation indication from a network (e.g., the network) indicating that the first carrier should be activated; by the first UE, receiving a first recovery indication from the network indicating that the first carrier should be recovered; by the first UE, receiving a second activation indication from a peer UE (e.g., the second UE) indicating that the first carrier should be activated; or by the first UE, receiving a second recovery indication from the second UE indicating that the first carrier should be recovered.
[0052] For example, the first UE determines that the abnormal condition on the first carrier has been recovered in response to the first UE determining that a timer, which is started in response to the determination of an abnormal condition on the first carrier, has expired. For example, the first UE starts a timer in response to the detection of an abnormal condition on the first carrier, and in response to the determination that the timer has expired, the first UE considers that the first carrier has recovered from the abnormal condition.
[0053] In some embodiments, in response to the first UE detecting an abnormal condition on the first carrier, the first UE transmits an abnormal condition recovery signaling to a peer UE (e.g., a second UE). After receiving the abnormal condition recovery response signaling from the peer UE, the first UE determines that the abnormal condition on the first carrier has been recovered. In some embodiments, the response signaling may include HARQ feedback. Thus, in some arrangements, in response to the determination of an abnormal condition on the first carrier, the first UE transmits at least one abnormal condition recovery signaling to the second UE. The first UE receives at least one abnormal condition response signaling from the second UE. In response to receiving at least one abnormal condition response signaling, the first UE determines that the abnormal condition on the first carrier has been recovered.
[0054] For example, recovery signaling can be RRC signaling. For example, recovery signaling can be MAC CE.
[0055] For example, response signaling can be RRC signaling. For example, recovery signaling can be MAC CE. For example, recovery signaling can be HARQ feedback. For example, response signaling can be RRC re-establishment signaling.
[0056] In some embodiments, in response to the first UE detecting an abnormal condition on the first carrier, the first UE initiates a recovery procedure, which transmits a first number (e.g., N) of abnormal condition recovery signaling to a peer UE (e.g., a second UE). After receiving at least a second number (e.g., M) of abnormal condition recovery response signaling from the peer UE, the first UE determines that the abnormal condition on the first carrier has been recovered. In response to the first UE receiving a third number of abnormal condition response signaling, and the third number being less than the second number, the first UE determines at least one of the following: the abnormal condition recovery cannot be recovered, or an RLF should be detected on the carrier. In some embodiments, the response signaling may include HARQ feedback. The first number N and the second number M may be integers received from a network (e.g., a network) or predetermined. Therefore, in some arrangements, in response to the determination of an abnormal state on the first carrier, the first UE transmits at least one abnormal state recovery signaling of a first number (e.g., N) to the second UE. The first UE receives at least one abnormal state response signaling of a second number from the second UE. The second number reaches a threshold (e.g., M). In response to receiving at least one abnormal state response signaling of the second number, the first UE determines that the abnormal state on the first carrier has been recovered. If the first UE does not receive at least one abnormal state response signaling of the second number from the second UE and does not reach the threshold M, the first UE assumes that the carrier cannot be recovered from the abnormal state.
[0057] In some arrangements, the first UE transmits a first number (e.g., N) of at least one abnormal state recovery signaling to the second UE within a first period (e.g., K milliseconds). In some arrangements, the transmission period can be controlled by a timer, for example, the first UE starts the timer in response to the triggering of a recovery procedure. In response to the determination that the first timer has expired, the first UE transmits a recovery signaling and restarts the first timer. In response to the determination that the maximum number of recovery signaling transmissions has been reached, the first UE stops the first timer.
[0058] In some arrangements, in response to the triggering of a recovery procedure, the first UE starts a timer. In response to the determination that the first timer has expired and that a second number of received response signalings are less than a threshold (e.g., a maximum number), the first UE determines that an RLF should be detected on this carrier.
[0059] In some arrangements, in response to the triggering of a recovery procedure, the first UE starts a timer. In response to the determination that the first timer has expired and the number of received response signalings is less than a threshold (e.g., a maximum number), the first UE decides that this carrier will not be recovered.
[0060] In some arrangements, the first UE receives from the network (e.g., the network) at least one of the following: a first number value for recovery signaling, a second number value for response signaling, a first period value for recovery signaling, a first timer value for transmission of recovery signaling, priority for recovery signaling, priority for response signaling, latency boundary for recovery signaling, HARQ feedback attribute for recovery signaling (e.g., HARQ enabled or disabled), maximum retransmission count for recovery signaling, latency boundary for response signaling, HARQ feedback attribute for response signaling (e.g., HARQ enabled or disabled), maximum retransmission count for response signaling, etc.
[0061] In some embodiments, in response to a decision that an abnormal condition on a first carrier has been recovered, the first UE reports the recovery of the abnormal condition on the first carrier to the network (e.g., the network). In some embodiments, in response to the detection of an abnormal condition on the first carrier, the first UE starts a timer, and in response to a decision that the timer has expired, the first UE determines an abnormal condition for a destination (e.g., a second UE). In response to a decision that no carrier meets the carrier selection criteria (e.g., no carrier can be selected or reselected) for communication with the destination (e.g., a second UE), the first UE determines an abnormal condition at the destination.
[0062] Figure 4 is a flowchart illustrating an exemplary method 400 for managing CA-based SL radio communication in various arrangements. Referring to Figure 1A-4, method 400 can be implemented by a first UE (e.g., UE104a / 220), a second UE (e.g., UE104b / 230), and a network 102 / 210. Communication over the SL radio communication channel 170 or SL network is shown across the dashed line between the first UE and the second UE.
[0063] In 330, as explained, the first UE communicates with the second UE via SL communication. In 340, as explained, the second UE communicates with the first UE via SL communication.
[0064] In 410, the first UE determines that at least one condition is met to trigger a reselection of a carrier (e.g., a second carrier). The first UE may determine that at least one condition is met to trigger a reselection procedure. In response to the determination that at least one condition is met to trigger a carrier reselection procedure, the first UE triggers the carrier reselection procedure. The carrier reselection procedure includes by the first UE selecting at least one candidate carrier and selecting a carrier from at least one candidate carrier.
[0065] For example, the first UE may trigger a carrier selection or reselection of the second carrier in response to the determination of at least one condition for triggering a reselection. Examples of conditions for triggering reselection include: an abnormal condition being detected on the second carrier; an abnormal condition being detected on the destination; the selected carrier for the destination (e.g., the second carrier) being included in an undesirable carrier list provided by the peer UE (e.g., the second UE); the selected carrier for the destination (e.g., the second carrier) being included in an unauthorized carrier list provided by the peer UE (e.g., the second UE); in response to receiving an indication from a sidelink RLC entity that the maximum number of retransmissions for a particular destination has been reached; in response to receiving an indication that the RRC reconfiguration timer (e.g., T400) for a particular destination has expired; in response to receiving an indication from a MAC entity that the maximum number of consecutive HARQ DTXs for a particular destination has been reached; or in response to receiving an integrity check failure indication from an SL PDCP entity regarding an SL RB (e.g., SL-SRB2 or SL-SRB3) for a particular destination.
[0066] In 420, a third carrier is selected as a candidate carrier. In some embodiments, the first UE selects a carrier (e.g., a third carrier) as a candidate carrier that is included in a preferred carrier list provided by a peer UE (e.g., a second UE). That is, in embodiments where the carrier is present in a preferred carrier list provided by a peer UE, the first UE selects a carrier shown in the preferred carrier list as the third carrier.
[0067] In some embodiments, the first UE selects a third carrier that satisfies at least one condition for selecting a candidate carrier for SL communication with the second UE. Embodiments of the condition for selecting a candidate carrier include at least one of the following: no abnormal conditions are detected on the third carrier; the channel congestion of the third carrier (such as measured by CBR) is below a configured or predetermined threshold; the third carrier is not included in an unauthorized carrier list provided by the peer UE (e.g., the second UE); or the third carrier is not included in an undesirable carrier list provided by the peer UE (e.g., the second UE).
[0068] In some arrangements, the first UE determines that a carrier (e.g., a third carrier) is a candidate carrier for selection or re-selection in response to a determination that at least one condition for a candidate carrier is met. Embodiments of the conditions for a candidate carrier include: no abnormal conditions are detected on the third carrier; the channel congestion of the third carrier (e.g., as measured by CBR) is below a configured or predetermined threshold; the third carrier is not included in an unapproved carrier list provided by a peer UE (e.g., a second UE); or the third carrier is not included in an undesirable carrier list provided by a peer UE (e.g., a second UE).
[0069] In 430, the first UE selects a carrier from at least one candidate carrier. In some embodiments, one of the candidate carriers (e.g., the third carrier) is selected in response to a decision that the carrier is included in a preferred carrier list provided by the peer UE (e.g., the second UE). In some embodiments, one of the candidate carriers (e.g., the third carrier) is selected in response to a decision that the carrier is not included in at least one of the undesirable or unacceptable carrier lists provided by the peer UE (e.g., the second UE). In some embodiments, in response to a decision that none of the candidate carriers are included in a preferred carrier list provided by the peer UE, the UE randomly selects a carrier from at least one of the candidate carriers. In some embodiments, in response to a decision that all of at least one candidate carriers are included in at least one of the undesirable or unacceptable carrier lists provided by the peer UE, the UE randomly selects a carrier from at least one of the candidate carriers. In some embodiments, a candidate carrier included in a preferred carrier is initially selected by the first UE.
[0070] In 440, the first UE excludes a carrier from at least one candidate carrier. In some embodiments, a carrier is excluded from at least one candidate carrier if at least one condition is met. Embodiments of the condition for excluding a carrier from at least one candidate carrier include at least one of the following: an abnormal condition is detected on the third carrier by the UE; the channel congestion of the third carrier (such as measured by CBR) is higher than a configured or predetermined threshold; the third carrier is included in an unapproved carrier list provided by a peer UE (e.g., a second UE); or the third carrier is included in an undesirable carrier list provided by a peer UE (e.g., a second UE); or an abnormal condition is detected on the third carrier.
[0071] In some arrangements, data can be mapped to one or more frequencies or frequency ranges for each service type. Service types associated with different radio frequencies or frequency ranges can be classified into distinctly different Quality of Service (QoS) flows, such as PC5 QoS flows. QoS flows can be defined by QoS parameters and QoS characteristics, referred to as QoS profiles. In other words, different QoS flows can be associated with different frequencies or frequency ranges. Examples of service types include Multimedia Priority Service (MPS), Evolutionary Multimedia Broadcast Multicast Service (eMBMS), and Advanced eMBMS (FeMBMS). For a UE performing SL communication (e.g., in 330), the UE reports to the network the corresponding SL frequency (e.g., at least one frequency or frequency range) and the QoS flow for requesting configuration, resources, etc. In some configurations, where two or more services share the same destination Layer 2 ID, reporting SL frequencies to the network at the granularity of the destination Layer 2 ID would result in the network being unable to distinguish whether the reported SL frequencies can be used for all services using the same destination Layer 2 ID. In some arrangements, the UE reports SL frequencies to the network at the granularity of QoS flows (e.g., PC5 QoS flows). In some arrangements, the UE reports QoS flows to the network at the granularity of sidelink frequencies. In some arrangements, the UE reports a mapping of QoS flows to SL frequencies to the network.
[0072] Figure 5 is a flowchart illustrating an exemplary method 500 for managing CA-based SL radio communication in various arrangements. Referring to Figure 1A-5, method 500 can be implemented by a first UE (e.g., UE104a / 220), a second UE (e.g., UE104b / 230), and a network 102 / 210. Communication via SL radio communication channel 170 or the SL network is shown across the dashed line between the first UE and the second UE. Communication via radio communication channel 103a / 150 is shown across the dashed line between the first UE and the network.
[0073] In 330, as explained, the first UE communicates with the second UE via SL communication. In 340, as explained, the second UE communicates with the first UE via SL communication.
[0074] In 510, the first UE reports to the network, based on the QoS flow, at least one frequency (e.g., at least one frequency range) to be used in SL communication with the second UE. In 520, the network receives from the first UE, based on the QoS flow, at least one frequency to be used in SL communication with the second UE.
[0075] In some embodiments, reporting at least one frequency used in SL communication with a second UE based on QoS flows includes the first UE reporting to the network at least one frequency for QoS flows for each of the multiple destinations of the SL communication. In other words, for each of the at least one frequency used in SL communication with the second UE, the first UE reports a QoS flow associated with the at least one frequency being reported. For example, for each of the at least one frequency being reported, the first UE reports a frequency (or frequency range) for SL communication and a QoS flow associated with the frequency for SL communication.
[0076] In some embodiments, reporting at least one frequency used in SL communication with a second UE based on a QoS flow includes reporting a QoS flow for each of several services of SL communication for each of the at least one frequency. In other words, for each QoS flow, the first UE reports the SL frequency associated with the reported QoS flow. For example, the first UE reports to the network a QoS flow (e.g., a QoS flow identifier and / or other attributes) and at least one frequency (or frequency range) for SL communication associated with the QoS flow.
[0077] In some embodiments, reporting at least one frequency used in SL communication with a second UE based on the QoS flow includes reporting a mapping that maps at least one frequency to the QoS flow for each of several services of the SL communication.
[0078] In some arrangements, the first UE passes at least one frequency from a higher layer (e.g., the V2X layer) to a lower layer to perform SL communication at the granularity of each QoS flow. In some arrangements, the first UE passes the QoS flow and at least one frequency associated with the QoS flow to a lower layer to perform SL communication at the granularity of each QoS flow. In some arrangements, the first UE passes at least one frequency and the PC5 QoS flow associated with the SL frequency to a lower layer to perform SL communication at the granularity of each QoS flow.
[0079] In some arrangements, different service types may have the same destination Layer 2 ID, and the service types may have different radio frequencies and be classified into the same QoS flow. In this case, the first UE passes only the overlapping frequencies (e.g., at least one overlapping frequency range) of the different services from the upper layer (e.g., V2X layer) to the lower layer. That is, each of the at least one frequencies passed to the lower layer is an overlapping frequency between two or more of the multiple services of the SL communication. In embodiments where there are no overlapping frequencies for the service type, the service type is not classified into the same QoS flow. In other words, the first UE ensures that frequencies classified into the same PC5 QoS flow can be used by all service types mapped within this PC5 QoS flow. For example, the first UE initiates SL communication with the second UE for the first and second services (e.g., at 330). The first service is mapped to a first frequency (e.g., a first frequency range) and a second frequency (e.g., a second frequency range) (e.g., it can communicate using them). The second service is mapped to a second frequency and a third frequency (e.g., it can communicate using them). The first UE determines that the first and second services may use the same PC5 QoS flow (e.g., the first QoS flow). In this case, with respect to the first UE passing the first QoS flow to the lower layer, only the second frequency associated with the first QoS flow is passed into the lower layer.
[0080] In some embodiments, the first UE passes from a higher layer (e.g., a V2X layer) to a lower layer at least one frequency for each of at least one service type, at least one service type for each of at least one frequency, at least one frequency associated with at least one service type, or at least one frequency and at least one service type associated with at least one frequency. That is, the first UE passes from a higher layer (V2X) to a lower layer at least one of the following: a sidelink frequency (or frequency range) at the service type granularity, a service type at the sidelink frequency granularity, a service type and its associated sidelink frequency, or a sidelink frequency and its associated service type.
[0081] In some arrangements, with respect to a first UE reporting SL frequencies to the network, only overlapping frequencies (e.g., at least one overlapping frequency range) used by all service types associated with the same destination identifier (e.g., destination L2 ID) are reported. In some embodiments, the destination identifier identifies a second UE. For example, the first UE initiates SL communication with the second UE for the first and second services (e.g., in 330). The first service is mapped to a first frequency (e.g., a first frequency range) and a second frequency (e.g., a second frequency range) (e.g., can be communicated using them). The second service is mapped to a second frequency and a third frequency (e.g., can be communicated using them). The first UE determines that the first and second services may use the same destination L2 ID-1. In this case, if the first UE reports at least one frequency to the network, only the second frequency is reported for this destination L2 ID-1.
[0082] In some arrangements, for SL relay communication, the remote UE connects to the network via a relay UE, and the remote UE communicates with the relay UE via SL communication. For the UE performing SL communication, the UE selects a synchronization reference source. Examples of sources include the Global Navigation Satellite System (GNSS), a cell, or a UE. A remote UE that is not within a cell's coverage cannot select a cell as its reference source. However, based on the configuration (e.g., the synchronization priority in SIB12 or RRC reconfiguration is set to the network), it is possible for the remote UE to select a cell as its reference.
[0083] In some arrangements, the remote UE is not allowed to request SIB12 via the relay UE.
[0084] In some embodiments, message-A includes at least one of an RRC message or an SIB message.
[0085] In some embodiments, source-A can be at least one of the following: a network, a primary cell, a serving cell, a single frequency (e.g., a frequency range), a GNSS, user equipment, etc.
[0086] In some arrangements, with respect to the frequency used to transmit NR SL communications, the UE may select Source-A as the reference in response to the UE determining that it is within the coverage of a first source (e.g., Source-A).
[0087] With respect to the frequencies used to transmit NR SL communications, if the frequencies are related to Source-A (e.g., associated with, associated with, by or used for) and the UE determines or considers them to be within the coverage of Source-A, the UE may select them relative to Source-A.
[0088] With respect to the frequencies used to transmit NR sidelink communications, if the frequency is related to Source-A, and the UE determines or considers it to be within Source-A's coverage, the UE may select a downlink frequency paired with Source-A as a reference.
[0089] With respect to the frequencies used to transmit NR SL communications, if the UE is outside the coverage on the frequencies in question, and the UE determines or considers it to be within the coverage of Source-A, the UE may select Source-A as the reference.
[0090] With respect to the frequencies used to transmit NR SL communications, if the UE is outside the coverage on the frequencies in question, and the UE determines or considers it to be within the coverage of source-A, and source-A is involved in at least one of the primary or secondary cells, the UE may select at least one of the primary or secondary cells as its basis.
[0091] With respect to the frequencies used to transmit NR SL communications, if a UE is outside the coverage on the frequencies in question, and the UE determines or considers it to be within the coverage of Source-A, and Source-A is not involved in at least one of the primary or secondary cells, the UE may select Source-A as the reference.
[0092] The UE determines that a message A scheduled by source A is within source A's coverage in response to the UE receiving message A scheduled by source A's PDCCH. The UE determines that a message A scheduled by source A's PDCCH is within source A's coverage in response to the UE receiving (e.g., receiving) message A. In some embodiments, a message scheduled by source A or source A's PDCCH includes a message that the UE receives (e.g., receives) directly from source A, i.e., without going through a relay UE.
[0093] With respect to the frequencies used to transmit NR SL communications, if the frequency is included in message-A scheduled by source-A, the UE may select it relative to source-A.
[0094] With respect to the frequencies used to transmit NR SL communications, if the frequency is related to source-A and is included in message-A scheduled by source-A, the UE may select it relative to source-A.
[0095] With respect to the frequency used to transmit NR sidelink communication, if the frequency is related to source-A and SIB12 is directly scheduled by source-A, the UE may select the frequency based on the downlink frequency paired with source-A.
[0096] With respect to the frequencies used to transmit NR SL communications, the UE may select, based on Source A, if it determines that the frequency is outside of coverage on the frequencies involved and is included in Message A scheduled by Source A.
[0097] With respect to the frequencies used to transmit NR SL communications, if the UE is outside the coverage on the frequencies involved and the frequencies are included in message A scheduled by source A, and the frequencies involve at least one of the primary or secondary cells, the UE may select based on at least one of the primary or secondary cell scheduling SIB12.
[0098] With respect to the frequencies used to transmit NR SL communications, the UE may select based on frequency scheduling message-A in response to a decision that the frequency is outside of coverage on the frequencies involved, is included in message-A scheduled by source-A, and does not involve at least one of the primary or secondary cells.
[0099] In the embodiment, where the frequency is included in message-A scheduled by source-A, the value indicating whether the UE can transmit synchronization information is set to true, and this value is included in message-A scheduled by source-A, the UE transmits the SL synchronous / physical broadcast channel (PBCH) block SSB on the frequency used for NR SL communication. In the embodiment, where the frequency is included in message-A scheduled by source-A, if the reference signal received power (RSRP) of source-A is lower than a configured threshold, the UE transmits the SL SSB on the frequency used for NR SL communication. If the UE is within the coverage of source-A, the UE transmits the sidelink SSB on the frequency used for NR SL communication based on the configuration scheduled by source-A.
[0100] With respect to a UE connected to the network via a relay UE, the UE can ignore message-A scheduled directly by source-A. With respect to a UE connected to the network via a relay UE, the UE is not permitted to retrieve message-A scheduled directly by source-A. The primary cell of a UE is the cell from which the UE can retrieve message-A scheduled directly by source-A. The serving cell of a UE is the cell from which the UE can retrieve SIB scheduled directly by the network. With respect to a UE connected to the network via a relay UE, the UE can ignore message-A scheduled directly by source-A in response to the decision that source-A is not the cell to which the UE is connected. With respect to a UE connected to the network via a relay UE, if message-A scheduled by source-A is received, the UE considers message-A not to have been received in response to the decision that source-A is not the cell to which the UE is connected. For a UE connected to the network via a relay UE, if message A scheduled by source A is received, the UE will consider it not to be within source A's coverage in response to the determination that source A is not the cell to which the UE is connected.
[0101] Figure 6 is a flowchart illustrating exemplary methods 600 for managing SL radio communication in various arrangements. Referring to Figure 1A-6, method 600 can be carried out by a first UE (e.g., UE104a / 220) and a second UE (e.g., UE104b / 230). Communication over SL radio communication channel 170 or the SL network is shown across the dashed line between the first UE and the second UE.
[0102] In step 330, as described, the first UE communicates with the second UE via SL communication. In step 340, as described, the second UE communicates with the first UE via SL communication. In step 610, the first UE selects the synchronization reference source.
[0103] In some embodiments, the first UE selects source-A (e.g., network 102 / 210) as the reference source in response to a determination that the first UE is within the coverage of source-A. For example, the UE considers that message-A, scheduled by source-A, is within the coverage of source-A in response to the UE receiving message-A.
[0104] In some embodiments, the first UE selects source-A as a reference source for the frequency used to transmit NR SL communication, in response to a decision that the frequency is included in message-A scheduled by source-A.
[0105] In some embodiments, the first UE selects Source-A as the reference source for the frequency used to transmit NR SL communication, in response to a determination that the frequency is associated with Source-A and that the frequency is included in Message-A scheduled by Source-A.
[0106] In some embodiments, the first UE selects a downlink frequency paired with Source-A as a reference source for the frequency used to transmit NR SL communication, in response to a decision that the frequency is associated with Source-A and that the frequency is included in Message-A scheduled by Source-A.
[0107] In some embodiments, the first UE selects Source A as a reference source for the frequency used to transmit NR SL communication in response to the UE's decision that the frequency is outside of its frequency coverage and is included in Message A scheduled by Source A. In some embodiments, the first UE selects Source A scheduling SIB12 as a reference source for the frequency used to transmit NR SL communication in response to the UE's decision that the frequency is outside of its frequency coverage and is included in Message A scheduled by Source A.
[0108] While various arrangements of this solution are described above, it should be understood that they are presented only as examples, not as limitations. Similarly, various schematic diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand the exemplary features and functions of this solution. However, such those skilled in the art will understand that this solution is not limited to the illustrated exemplary architectures or configurations and can be implemented using various alternative architectures and configurations. In addition, as will be understood by those skilled in the art, features of one or more of several arrangements can be combined with features of one or more of another arrangement described herein. Therefore, the scope and scope of this disclosure should not be limited by any of the exemplary arrangements described above.
[0109] Furthermore, it should be understood that any reference to elements in this specification using designations such as “first,” “second,” etc., does not generally limit the quantity or order of those elements. Rather, these designations can be used in this specification as a convenient means of distinguishing between two or more elements or instances of elements. Therefore, the references to first and second elements do not mean that only two elements may be employed, or that the first element must precede the second element in any given form.
[0110] In addition, those skilled in the art will understand that information and signals can be represented using any of the various different techniques and methods. For example, data, instructions, commands, information, signals, bits, and symbols, which may be referenced in the above description, can be represented, for example, by voltage, electric current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0111] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in relation to the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination thereof), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein as “software” or “software modules” for convenience), or any combination of these techniques. To clearly illustrate the interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described above, generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these techniques depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of this disclosure.
[0112] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented in or carried out within an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and / or transceivers that can communicate with various components in a network or within a device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a computing device, e.g., a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable combination of configurations for carrying out the functions described herein.
[0113] When implemented in software, the functionality can be stored on a computer-readable medium as one or more instructions or code. Therefore, steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. The computer-readable medium includes both computer storage media and communication media, and includes any medium that can enable the transfer of computer programs or code from one location to another. The storage medium can be any available medium that can be accessed by a computer. Such a computer-readable medium, but not limited to, as an example, may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.
[0114] In this document, the term “module” means, as used herein, software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purposes of discussion, various modules are described as discrete modules. However, as will be obvious to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to the arrangement of this solution.
[0115] In addition, memory or other storage devices and communication components may be incorporated into the arrangement of this solution. For the purpose of clarity, please understand that the above description refers to the arrangement of this solution with reference to different functional units and processors. However, it will be apparent that any preferred distribution of functionality between different functional units, processing logic elements, or domains may be used without deviating from this solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are not to indicate a strict logical or physical structure or organization, but merely to preferred means for providing the functionality described.
[0116] Various modifications to the implementations described herein will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the implementations shown herein, but should be given the broadest possible scope consistent with the novel features and principles disclosed herein, as enumerated in the following claims.
Claims
1. A wireless communication method, The first wireless communication device communicates with the second wireless communication device via sidelink (SL) communication, The first wireless communication device reports to the network at least one frequency for the SL communication with the second wireless communication device, which is mapped to a quality of service (QoS) flow, and such reporting includes reporting the at least one frequency mapped to the QoS flow to the destination of the SL communication. Wireless communication methods including
2. The wireless communication method according to claim 1, wherein reporting the at least one frequency for the SL communication with the second wireless communication device, which is mapped to the QoS flow, includes reporting the mapping between the at least one frequency and the QoS flow to the destination of the SL communication.
3. The wireless communication method according to claim 1, further comprising passing the at least one frequency from an upper layer to a lower layer, wherein the SL communication is performed in the lower layer for the QoS flow using the at least one frequency.
4. A first wireless communication device, The first wireless communication device comprises at least one processor, The aforementioned at least one processor is To communicate with a second wireless communication device via a transceiver using sidelink (SL) communication, Reporting to the network, via the transceiver, at least one frequency for the SL communication with the second wireless communication device, which is mapped to a quality of service (QoS) flow, wherein the reporting includes reporting the at least one frequency, which is mapped to the QoS flow, to the destination of the SL communication. A first wireless communication device configured to perform the following:
5. The first wireless communication device according to claim 4, wherein reporting the at least one frequency for the SL communication with the second wireless communication device, which is mapped to the QoS flow, includes reporting the mapping between the at least one frequency and the QoS flow to the destination of the SL communication.
6. The first wireless communication device according to claim 4, wherein the at least one processor is configured to pass the at least one frequency from an upper layer to a lower layer, and the SL communication is performed in the lower layer for the QoS flow using the at least one frequency.
7. A wireless communication method, wherein the wireless communication method is The network receives a report from a first wireless communication device that includes at least one frequency for sidelink (SL) communication with a second wireless communication device, which is mapped to a quality of service (QoS) flow. Includes, The report includes, with respect to the destination of the SL communication, the at least one frequency mapped to the QoS flow, A wireless communication method comprising the first wireless communication device communicating with the second wireless communication device via the SL communication.
8. The wireless communication method according to claim 7, wherein the report, which includes the at least one frequency for the SL communication with the second wireless communication device mapped to the QoS flow, includes a mapping between the at least one frequency and the QoS flow for the destination of the SL communication.
9. The wireless communication method according to claim 7, wherein the at least one frequency spans from an upper layer to a lower layer, and the SL communication is performed in the lower layer for the QoS flow using the at least one frequency.
10. A network node, The network node comprises at least one processor, The aforementioned at least one processor is Receiving a report from a first wireless communication device via a receiver, which includes at least one frequency for sidelink (SL) communication with a second wireless communication device, mapped to a quality of service (QoS) flow. It is configured to do the following: The report includes, with respect to the destination of the SL communication, the at least one frequency mapped to the QoS flow, The first wireless communication device is a network node that communicates with the second wireless communication device via the SL communication.
11. The report, which includes the at least one frequency for the SL communication with the second wireless communication device, mapped to the QoS flow, includes a mapping between the at least one frequency and the QoS flow for the destination of the SL communication, according to claim 10.
12. The network node according to claim 10, wherein the at least one frequency is passed from an upper layer to a lower layer, and the SL communication is performed within the lower layer for the QoS flow using the at least one frequency.