The present disclosure relates to request of coordination messages. More particularly, it relates to a transmitting wireless device, a receiving wireless device and methods for enabling coordination between the transmitting wireless device and the receiving wireless device.
Third Generation Partnership Project (3GPP) specified support in Long Term Evolution (LTE) for Proximity Services (ProSe) in Releases 12 and 13, targeting public safety use cases (e.g., first responders) as well as a small subset of commercial use cases (e.g., discovery). The main novelty of ProSe was the introduction of Device-to-Device (D2D) communications using the SL interface. During Rel-14 and Rel-15 in 3GPP, major changes were introduced to the LTE SL framework with the aim of supporting Vehicle-to-Everything/Anything (V2X) communications, where V2X collectively denotes communication between a vehicle to any other endpoint (e.g., a vehicle, a pedestrian, etc.). The feature targeted mostly basic V2X use cases such as day-1 safety, etc.
During Rel-16, 3GPP worked on specifying the SL interface for the 5G New Radio (NR). The NR SL in Rel-16 mainly targets advanced V2X services, which can be categorized into four use case groups: vehicles platooning, extended sensors, advanced driving and remote driving. The advanced V2X services require a new SL in order to meet the stringent requirements in terms of latency and reliability. The NR SL is designed to provide higher system capacity and better coverage, and to allow for an easy extension to support the future development of further advanced V2X services and other related services.
Given the targeted V2X services by NR SL, it is commonly recognized that groupcast/multicast and unicast transmissions are desired, in which the intended receiver of a message consists of only a subset of the vehicles in proximity to the transmitter (groupcast) or of a single vehicle (unicast). For example, in the platooning service there are certain messages that are only of interest to the members of the platoon, making the members of the platoon a natural groupcast. In another example, the see-through use case most likely involves only a pair of vehicles, for which unicast transmissions naturally fit. Therefore, NR SL not only supports broadcast as in LTE SL, but also groupcast and unicast transmissions. Like in LTE SL, the NR SL is designed in such a way that its operation is possible with and without network coverage and with varying degrees of interaction between User Equipment (UEs) and a Network (NW), including support for standalone, network-less operation.
In Rel-17, 3GPP is working on multiple enhancements for the SL with the aim of extending the support for V2X and to cover other Use Cases (UCs) such as public safety (see RP-193231). Among these, improving the performance of power limited UEs (e.g., pedestrian UEs, first responder UEs, etc.) and improving the performance using resource coordination are considered critical.
Like in LTE SL, there are two resource allocation modes for NR SL:
In SL transmission mode 2, distributed resource selection is employed, i.e., there is no central node for scheduling and UEs play the same role as in autonomous resource selection. Transmission Mode 2 is based on two functionalities: reservation of future resources and sensing-based resource allocation. Reservation of future resources is done so that the UE sending a message also notifies the receivers about its intention to transmit message using certain time-frequency resources at a later point in time. For example, a UE transmitting at time T informs the receivers that it will transmit using the same frequency resources at time T+100 ms. Resource reservation allows a UE to predict the utilization of the radio resources in the future. That is, by listening to the current transmissions of another UE, it also obtains information about potential future transmissions. This information can be used by the UE to avoid collisions when selecting its own resources. Every UE sends a message that is received by every other UE indicating the resources to be used by the further messages. Specifically, a UE predicts the future utilization of the radio resources by reading received booking messages (e.g., information about the reserved resources for future messages) and then schedules its current transmission to avoid using the same resources. This is known as sensing-based resource selection.
The sensing-based resource selection scheme specified in NR Rel-16 can be roughly summarized in the following steps and is defined in the specification TS 38.214 (v16.1.0).
Table 1 includes the text of the NR Rel-16 specification that is related to sensing and selection windows. More specifically,
The previous section described sensing-based resource allocation, which aims at predicting future utilization of the channel and selecting resources as to avoid collisions. However, collisions may be detected after the initial allocation of resources in the following two cases:
The specification defines two mechanisms to avoid collisions in the preceding two situations:
Herein, re-evaluation and pre-emption refer to the following.
In the time between the selection of the resource(s) and the transmission of a corresponding reservation, other UEs may reserve the same resources. To avoid such a collision, a UE is allowed to re-consider its selection. The purpose of such procedure is to evaluate if the earlier selected resource(s) is still suitable for transmission or not. If a UE determines that the earlier selected resource(s) is (are) not suitable for its own transmission anymore (e.g., some other UE also selected the same resource in the meantime), it triggers the resource selection mechanism again. Meaning, a new set of candidate resources is created, and the resource(s) is(are) randomly selected from the newly created candidate resource set. This procedure is referred to as re-evaluation or re-evaluation and re-selection.
After a reservation has been sent, the UE cannot re-evaluate its selection anymore. However, it may still be prevented to transmit if other UEs have higher importance transmissions to perform. In these mechanisms, known as pre-emption, a UE (re-)triggers the resource selection if another UE with higher priority selects the same resource for its transmission. In this case, a UE with low priority transmission (re-)triggers resource selection and a new set of candidate resource set is created/determined by the UE based on the recent sensing information. This procedure is referred to as pre-emption or pre-emption and re-selection.
For SL transmission, each packet transmitted via Physical Sidelink Shared Channel (PSSCH) is associated with an SCI via Physical Sidelink Control Channel (PSCCH). The SCI is divided into two stages:
In Rel-17, 3GPP is working on multiple enhancements for sidelink with the aim of extending the support for V2X and to cover other Use Cases (UCs) such as public safety (see RP-202846). Among these, improving the performance of power limited UEs (e.g., pedestrian UEs, first responder UEs, etc.) and enhancing the performance using resource coordination are considered critical. Table 2 includes the objective in the work item description for SL enhancement that is relevant for this disclosure (marked as underlined).
Specification of solutions is currently at an early stage. So far only a few agreements regarding general considerations have been made. The most relevant ones are captured in Table 3.
Based on the discussions and the content related to the first agreement—marked as underlined—there is arguably a need to have a method/mechanism that allows for triggering each of the Inter-UE coordination schemes while at the same time allowing to have a fast/flexible switching between both depending on certain conditions.
Consequently, there is a need for providing an improved method to dynamically request a coordination message for the different Inter-UE coordination mechanisms. The method proposed in the disclosure allows a flexible co-existence between Inter-UE Scheme 1 and Inter-UE Scheme 2. Extra signaling and/or overhead to the system is reduced.
According to a first aspect of the present disclosure, a method performed by a transmitting wireless device for enabling coordination with a receiving wireless device is provided. The method comprises transmitting a coordination message to the receiving wireless device that indicates whether coordination information is expected; and receiving, in response to the coordination message indicating that coordination information is expected, the coordination information from the receiving wireless device in accordance with a format indicated in the coordination message.
In some embodiments, the coordination message may comprise a Sidelink Control Information, SCI, that indicates whether the coordination information is expected.
In some embodiments, the SCI may comprise one or more reserved bits encoded as one of: 00 or 0000 to indicate that the coordination information is not expected; 01 or 0001 to indicate that 1-bit coordination information is expected to be sent in accordance with an Inter-User Equipment, UE, Coordination Scheme 2 format; 10 or 0010 to indicate that map-based coordination information is expected to be sent in accordance with an Inter-UE Coordination Scheme 1 format independently of whether a collision is expected; and 11 or 0011 to indicate that map-based coordination information is expected to be sent in accordance with the Inter-UE Coordination Scheme 1 format in case of the collision is expected.
In some embodiments, the SCI may comprise a field configured to indicate that the coordination information is expected.
In some embodiments, the method may further comprise determining (400, 600) that the receiving wireless device is within a distance where it is able to decode the SCI.
In some embodiments, the coordination message may indicate, based on one or more reserved bits in the SCI, that the coordination information is expected.
In some embodiments, the step of receiving the coordination information may further comprise, in response to the coordination message indicating that 1-bit coordination information is expected while Hybrid Automatic Repeat Request, HARQ, is enabled and a collision is expected, receiving the coordination information in accordance with an Inter-UE Coordination Scheme 2 format.
According to a second aspect of the present disclosure, a method performed by a receiving wireless device for enabling coordination with a transmitting wireless device is provided. The method comprises receiving, from the transmitting wireless device, a coordination message that indicates whether coordination information is expected; and transmitting, in response to the coordination message indicating that coordination information is expected, the coordination information to the transmitting wireless device in accordance with a format indicated in the coordination message.
In some embodiments, the coordination message may comprise a Sidelink Control Information, SCI, that indicates whether the coordination information is expected.
In some embodiments, the SCI may comprise one or more reserved bits encoded as one of: 00 or 0000 to indicate that the coordination information is not expected; 01 or 0001 to indicate that 1-bit coordination information is expected to be sent in accordance with an Inter-User Equipment, UE, Coordination Scheme 2 format; 10 or 0010 to indicate that map-based coordination information is expected to be sent in accordance with an Inter-UE Coordination Scheme 1 format independently of whether a collision is expected; and 11 or 0011 to indicate that map-based coordination information is expected to be sent in accordance with the Inter-UE Coordination Scheme 1 format in case of the collision is expected.
In some embodiments, the SCI may comprise a field configured to indicate that the coordination information is expected.
In some embodiments, the step of transmitting the coordination information may comprise determining, based on one or more reserved bits in the SCI, that the coordination information is expected.
In some embodiments, the step of transmitting the coordination information may further comprise one of: transmitting 1-bit coordination information in accordance with the Inter-UE Coordination Scheme 2 format when the one or more reserved bits are encoded as 01 or 0001 and Hybrid Automatic Repeat Request, HARQ, is enabled; and not transmitting the coordination information when the one or more reserved bits are encoded as 01 or 0001 or the HARQ feedback is disabled.
In some embodiments, the step of transmitting the coordination information may further comprise determining, based on a time/frequency field in the SCI, whether the collision is expected when the one or more reserved bits are encoded as 11 or 0011.
In some embodiments, the step of transmitting the coordination information may further comprise not transmitting the coordination information when the one or more reserved bits are encoded as 10, 0010, 11, or 0011 and the collision is not expected.
In some embodiments, the step of transmitting the coordination information may further comprise transmitting the coordination information in accordance with the Inter-UE Coordination Scheme 1 format when the one or more reserved bits are encoded as 10, 0010, 11, or 0011 and the collision is expected.
In some embodiments, the step of transmitting the coordination information may further comprise, in response to the coordination message indicating that 1-bit coordination information is expected while Hybrid Automatic Repeat Request, HARQ, is enabled and a collision is expected, transmitting the coordination information in accordance with an Inter-UE Coordination Scheme 2 format.
According to a third aspect of the present disclosure, a wireless device for enabling coordination with a receiving wireless device is provided. The wireless device is configured to: transmit a coordination message to the receiving wireless device that indicates whether coordination information is expected; and receive, in response to the coordination message indicating that coordination information is expected, the coordination information from the receiving wireless device in accordance with a format indicated in the coordination message.
According to a fourth aspect of the present disclosure, a wireless device for enabling coordination with a transmitting wireless device is provided. The wireless device is configured to: receive, from the transmitting wireless device (1000-A), a coordination message that indicates whether a coordination information is expected; and transmit, in response to the coordination message indicating that coordination information is expected, the coordination information to the transmitting wireless device in accordance with a format indicated in the coordination message.
Embodiments of the invention will be described in more detail hereinafter with reference to examples but to which the scope is not limited.
In this disclosure methods which involve both schemes (Scheme 1 and Scheme 2) as defined per the agreement(s) are discussed. In
Moreover,
As shown in
There currently exists a certain challenge(s). In the current 3GPP Rel-17, there have been discussions regarding the signaling to request coordination information within the Inter-UE coordination procedure. Some of the options involve sending a separate enquiry/request message which is slow and introduces a heavy signaling overhead while other solutions do not include an explicit signaling, e.g., triggering due to potential collisions.
Moreover, an independent explicit enquiry/request message is mostly designed for Inter-UE Scheme 1 as defined in the above, while for Inter-UE Scheme 2 there is no discussion/solution to include such a request message in order to trigger the Inter-UE coordination mechanism. The issue for Inter-UE Scheme 2 when there is no request/enquiry message within the Inter-UE coordination procedure is that in case a UE reserves resources for its next transmission which creates conflicting resources, i.e., a collision is expected due to the same frequency/time resources reserved by several UEs, then the UE may receive a coordination message and one or more of the following may happen:
Therefore, under these situations it is not optimal that the coordinator UE, i.e., the UE that sends the coordination information, sends information since it just adds more overhead to the system without any benefit since the other UE(s) will not receive it; or are not able to decode it; or will not use it.
Another issue is that using an explicit request/enquiry signaling, makes it is too cumbersome to have a flexible/fast co-existence between the two schemes, e.g., changing the inter-UE coordination schemes between consecutive transmissions. Therefore, a way to have a more flexible and simpler way without adding extra signaling is needed.
Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. In this disclosure, a mechanism to dynamically request a coordination message for the different Inter-UE coordination mechanisms, i.e., Inter-UE Scheme 1 and Inter-UE Scheme 2 per agreements, is defined. The mechanism is flexible and dynamic since it can signal to the peer UE(s) to use either Scheme 1 (i.e. map-based coordination); or Scheme 2 (i.e. one-bit coordination); or no inter-UE coordination mechanism at all for each transmission by using the 1st stage SCI, e.g., using the (pre-)configured reserved bits field. Moreover, upon receiving the request for a coordination message within the SCI, the receiving UE sends the coordination message (if any) in the desired format when certain conditions are fulfilled.
The main aspects of this disclosure are:
There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. In embodiments disclosed herein, coordination may be enabled between a transmitting wireless device and a receiving wireless device.
In one aspect, a method performed by the transmitting wireless device for enabling coordination is provided. The method includes transmitting a coordination message to the receiving device to indicate whether coordination information is expected.
In another aspect, a method performed by the receiving wireless device is provided. The method includes receiving a coordination message from the transmitting wireless device that indicates whether a coordination information is expected. The method also includes transmitting the coordination information to the transmitting wireless device in response to the coordination message indicating that the coordination information is expected.
Certain embodiments may provide one or more of the following technical advantage(s). The main advantages of the disclosed method are:
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.
Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments, a TRP may be a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple TRP (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better Physical Downlink Shared Channel (PDSCH) coverage, reliability and/or data rates. There are two different operation modes for multi-TRP: single Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and Medium Access Control (MAC). In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, UE is scheduled by independent DCIs from each TRP.
In some embodiments, a set Transmission Points (TPs) is a set of geographically co-located transmit antennas (e.g., an antenna array (with one or more antenna elements)) for one cell, part of one cell or one Positioning Reference Signal (PRS)-only TP. TPs can include base station (eNB) antennas, Remote Radio Heads (RRHs), a remote antenna of a base station, an antenna of a PRS-only TP, etc. One cell can be formed by one or multiple TPs. For a homogeneous deployment, each TP may correspond to one cell.
In some embodiments, a set of TRPs is a set of geographically co-located antennas (e.g., an antenna array (with one or more antenna elements)) supporting TP and/or Reception Point (RP) functionality.
Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.
Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.
The base stations 302 and the low power nodes 306 provide service to wireless communication devices 312-1 through 312-5 in the corresponding cells 304 and 308. The wireless communication devices 312-1 through 312-5 are generally referred to herein collectively as wireless communication devices 312 and individually as wireless communication device 312. In the following description, the wireless communication devices 312 are oftentimes UEs, but the present disclosure is not limited thereto.
As discussed in detail below, coordination can be performed between a pair of wireless devices. One of the wireless devices is a transmitting wireless device that requests coordination information. Another one of the wireless devices is a receiving wireless device that provides coordination information in response to the request from the transmitting wireless device.
The present invention is related to operations and methods using resource allocation Mode 2 or any other mode in which the UE(s) performs sensing and resource allocation.
The transmitting wireless device transmits a coordination message to the receiving wireless device to indicate whether a coordination information is expected (step 402). In an embodiment, the coordination message can include the SCI (step 402-1). The transmitting wireless device may receive the coordination information in response to the coordination message indicating that the coordination information is expected (step 404).
The receiving wireless device can transmit the coordination information to the transmitting wireless device in response to the coordination message indicating that the coordination information is expected (step 502). In one embodiment, the receiving wireless device may check one or more reserved bits in the SCI to determine whether the coordination information is requested (step 502-1). The receiving wireless device may transmit the coordination information in accordance with Inter-UE Scheme 2 if the reserved bits are encoded as (00)01 and Hybrid Automatic Repeat Request (HARQ) is enabled (step 502-2). The receiving wireless device may not transmit the coordination information if the reserved bits are encoded as (00)01 and HARQ is not enabled (step 502-3). The receiving wireless device may check a time/frequency field in the SCI to determine whether a collision is expected if the reserved bits are encoded as (00)01 or (00)11 (step 502-4). The receiving wireless device may not transmit the coordination information if the reserved bits are encoded as (00)10 or (00)11 and the collision is not expected (step 502-5). The receiving wireless device may transmit the coordination information in accordance with Inter-UE Scheme 1 if the reserved bits are encoded as (00)10 or (00)11 and the collision is expected (step 502-6).
This disclosure describes methods to request coordination information dynamically/flexibly in a number of formats (e.g., Scheme 1 or Scheme 2 as defined in Table 3). An indication/flag is included within the Sidelink (SL) Control Information (SCI) to signal the wanted/expected coordination information format (if any). By using the SCI to transport the request message, it is possible to avoid an extra signaling and overhead, and therefore, obtain a more dynamic and lean procedure to request coordination information.
The embodiment of the present disclosure is described in the context of 3GPP SL, where UEs (operating in either of the SL modes described earlier) communicate directly with each other, without sending the information through the base station. However, the solutions are applicable beyond SL as far as a UE can obtain a grant (e.g., by itself, from another node such as UE or a base station, etc.) and based on some information about the channel (e.g., acquired through sensing, transmitted from another node such as a UE or a base station, etc.) to determine whether none/some/all of the resources can be used and/or some other resources must be selected.
In the following, a UE requesting the coordination information will be denoted as UE-A, whereas the UE(s) receiving the request and transmitting the coordination information will be denoted as UE-B.
In this invention, UE-A requests to any UE-B in range, i.e., any UE that can decode the SCI transmitted by UE-A, to send a coordination information based on the information contained in its SCI. For instance, following the legacy NR SL specification, in the SCI there are reserved bits for forward compatibility (2-4 bits). Making use of these bits the procedure can be defined as follows:
The reserved bits in the 1st stage SCI are defined (or any combination thereof) as:
Another possibility, in addition to the one stated above, is to define a new SCI format which includes an explicit field(s) to be used for requesting a coordination message in a specific format.
Therefore, based on the information contained in the 1st stage SCI, the receiving UE(s) will trigger a specific type (if any) of the inter-UE coordination schemes. It is noteworthy that in some of the potential combinations the inter-UE coordination is not only triggered due to the signaling within the 1st stage SCI, i.e., for instance 0001 or 0011, but it also requires that for instance a potential conflict is identified and/or HARQ feedback is enabled.
From any UE-B perspective, upon receiving/decoding the 1st stage SCI, the following steps are performed:
The method in
The transmitting wireless device 1000-A receives, in response to the coordination message indicating that coordination information is expected, the coordination information from the receiving wireless device 1000-B in accordance with a format indicated in the coordination message (step 604).
In some examples, receiving (step 604) the coordination information further comprises, in response to the coordination message indicating that 1-bit coordination information is expected in a situation when Hybrid Automatic Repeat Request (HARQ) is enabled and a collision is expected, receiving the coordination information in accordance with an Inter-UE Coordination Scheme 2 format.
Optionally, the method in
The method in
The receiving wireless device 1000-B transmits, in response to the coordination message indicating that coordination information is expected, the coordination information to the transmitting wireless device 1000-A in accordance with a format indicated in the coordination message (step 7002).
In some examples, transmitting (step 7002) the coordination information may comprise determining, based on one or more reserved bits in the SCI, that the coordination information is expected.
In further examples, transmitting (step 7002) the coordination information may further comprise determining, based on a time/frequency field in the SCI, whether the collision is expected when the one or more reserved bits are encoded as 11 or 0011.
Specifically, transmitting (step 7002) the coordination information may further comprise, in response to the coordination message indicating that 1-bit coordination information is expected in a situation when Hybrid Automatic Repeat Request (HARQ) is enabled and a collision is expected, transmitting the coordination information in accordance with an Inter-UE Coordination Scheme 2 format.
As an example, the coordination message described in the
In the main example, the SCI contains information that indicates whether coordination information for the associated transmission is requested (or not) and in case of requesting coordination information, it determines the format of the coordination information.
In a related example, the information regarding the coordination information within the SCI is included in the reserved bits.
In a related example, the information regarding the coordination information within the SCI spans between 2 and 4 bits of information.
In a related example, the information included in the reserved bits is defined as follows (or any combination thereof):
In another example, a new SCI format is defined including a field that indicates whether coordination information for the associated transmission is requested (or not) and in case of requesting coordination information, it determines the format of the coordination information.
In another example, a UE upon receiving/decoding an SCI, which contains a field indicating whether a coordination information is needed and the desired format of the coordination information, transmits the coordination information in the indicated format if the conditions are fulfilled.
In a related example, for the case of one-bit coordination information required by UE-A, in addition to the information contained in the SCI, the UE decoding the SCI checks whether a potential collision is expected in order to send the coordination information.
In a related example, for the case of one-bit coordination information required by UE-A, the UE decoding the SCI checks whether a potential collision is expected and sends the coordination information only if HARQ feedback is enabled.
In a related example, for the case of map-based coordination information required by UE-A, in addition to the information contained in the SCI, the UE decoding the SCI checks whether a potential collision is expected and the exact format of the requested coordination information in order to send the coordination information.
In another example, a UE which is in a power saving mode, e.g., non-sensing prior to resource selection, upon sending the SCI with a request for a coordination information turns on its reception modules.
In a related example, a UE which is in a power saving mode and sends a request within the SCI to receive a one-bit coordination information, turns on its reception capabilities in order to receive Physical SL Feedback Channel (PSFCH) resources.
In a related example, a UE which is in a power saving mode and sends a request within the SCI to receive a map-based coordination information, turns on its reception capabilities fully in order to receive the coordination information.
As used herein, a “virtualized” radio access node is an implementation of the radio access node 700 in which at least a portion of the functionality of the radio access node 700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 700 may include the control system 702 and/or the one or more radio units 710, as described above. The control system 702 may be connected to the radio unit(s) 710 via, for example, an optical cable or the like. The radio access node 700 includes one or more processing nodes 800 coupled to or included as part of a network(s) 802. If present, the control system 702 or the radio unit(s) are connected to the processing node(s) 800 via the network 802. Each processing node 800 includes one or more processors 804 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 806, and a network interface 808.
In this example, functions 810 of the radio access node 700 described herein are implemented at the one or more processing nodes 800 or distributed across the one or more processing nodes 800 and the control system 702 and/or the radio unit(s) 710 in any desired manner. In some particular embodiments, some or all of the functions 810 of the radio access node 700 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 800. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 800 and the control system 702 is used in order to carry out at least some of the desired functions 810. Notably, in some embodiments, the control system 702 may not be included, in which case the radio unit(s) 710 communicate directly with the processing node(s) 800 via an appropriate network interface(s).
In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 700 or a node (e.g., a processing node 800) implementing one or more of the functions 810 of the radio access node 700 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1000 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/SE2022/050741 | 8/5/2022 | WO |
Number | Date | Country | |
---|---|---|---|
63229829 | Aug 2021 | US |