METHOD AND DEVICE FOR SELECTING RESOURCE IN WIRELESS COMMUNICATION SYSTEM
20230239900 · 2023-07-27
Inventors
Cpc classification
International classification
Abstract
Provided may be a method of supporting, by a user equipment (UE), sidelink communication in a wireless communication system. The method. of supporting, by the UE, sidelink communication in the wireless communication system may include receiving a coordination request from a transmitting UE (Tx UE); generating a coordination message based on the coordination request; and transmitting the generating coordination message to the Tx UE. Here, the coordination request may include 1-bit information and the coordination request may be received based on at least one of a physical resource set of Physical Sidelink Feedback Channel (PSFCH), a Sidelink Control Information (SCI) format, Cyclic Redundancy Checking (CRC) scrambling, and a Demodulation Reference Signal (DMRS) sequence, and the Tx UE may perform resource reselection based on the coordination message.
Claims
1. A method comprising: receiving, by a first wireless user device from a second wireless user device, a coordination request comprising: a first bit indicating that the second wireless user device requests coordination information; and a second bit indicating a preferred resource or a non-preferred resource; generating, based on the coordination request, a coordination message; and transmitting the generated coordination message to the second wireless user device.
2. The method of claim 1, wherein the coordination request comprises sidelink control information comprising the first bit and the second bit.
3. The method of claim 2, wherein the sidelink control information is a sidelink control information format 2-C.
4. The method of claim 2, wherein the sidelink control information is a second stage sidelink control information format.
5. The method of claim 4, further comprising: receiving a sidelink control information format 1 comprising a second stage sidelink control information format field indicating a sidelink control information format 2-C as the second stage sidelink control information format.
6. The method of claim 1, wherein the coordination request further comprises at least one of: priority information; a number of subchannels per slot; a resource reservation period; or an indication associated with a resource coordination message (CM) window location.
7. The method of claim 6, wherein the coordination request further comprises: a source identifier; and a destination identifier.
8. The method of claim 6, wherein the CM window location comprises at least one of: a CM window starting point; or a CM window end point.
9. The method of claim 1, further comprising: receiving, by the first wireless user device from the second wireless user device, sidelink data, wherein the coordination message is for the second wireless user device for performing resource reselection for transmission of sideilnk data.
10. The method of claim 1, wherein when the first wireless user device receives the coordination request, the second wireless user device is in a mode in which the second wireless user device directly determines a sidelink transmission resource.
11. The method of claim 1, wherein the first bit comprised in the coordination request is configured to indicate whether the first wireless user device provides coordination information or the second wireless user device requests coordination information.
12. The method of claim 1, further comprising: transmitting, from the first wireless user device, coordination information comprising a bit indicating that the first wireless user device provides, based on a condition, the coordination information, wherein the bit comprised in the coordination information is configured to indicate whether the first wireless user device provides coordination information or the second wireless user device requests coordination information.
13. The method of claim 12, further comprising: generating, based on the condition being satisfied, the coordination information, wherein the condition is a condition for triggering a resource coordination procedure.
14. The method of claim 12, wherein the condition comprises a half-duplex communication.
15. The method of claim 12, wherein the coordination information comprises sidelink control information comprising the bit indicating that the first wireless user device provides, based on the condition, the coordination information.
16. The method of claim 15, wherein the sidelink control information is a sidelink control information format 2-C corresponding to a second stage sidelink control information format.
17. The method of claim 1, further comprising: transmitting, from the first wireless user device via a physical sidelink feedback channel (PSFCH), signaling information indicating that a resource reselection is necessary.
18. The method of claim 17, wherein the transmitting the signaling information is further based on an expected resource conflict.
19. The method of claim 17, wherein the transmitting the signaling information is further based on a reference signal received power (RSRP) of received sidelink control information higher than a threshold.
Description
BRIEF DESCRIPTION OF DRAWINGS
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
[0033]
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS
[0043] Various examples of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings such that one of ordinary skill in the art to which the present disclosure pertains may easily implement the examples. However, the present disclosure may be implemented in various forms and is not limited to the examples described herein.
[0044] In describing the examples of the present disclosure, detailed description on known configurations or functions may be omitted for clarity and conciseness. Throughout the drawings and the detailed description, unless otherwise described, the same drawing reference numerals are understood to refer to the same elements, features, and structures.
[0045] It will be understood that when an element is referred to as being “connected to,” “coupled to,” or “accessed to” another element, it can be directly connected, coupled, or accessed to the other element or intervening elements may be present. Also, it will be further understood that when an element is described to “comprise/include” or “have” another element, it specifies the presence of still another element, but do not preclude the presence of another element uncles otherwise described.
[0046] Further, the terms, such as first, second, and the like, may be used herein to describe elements in the description herein. The terms are used to distinguish one element from another element. Thus, the terms do not limit the element, an arrangement order, a sequence or the like. Therefore, a first element in an example may be referred to as a second element in another example. Likewise, a second element in an example may be referred to as a first element in another example.
[0047] Herein, distinguishing elements are merely provided to clearly explain the respective features and do not represent that the elements are necessarily separate from each other. That is, a plurality of elements may be integrated into a single hardware or software unit. Also, a single element may be distributed to a plurality of hardware or software units. Therefore, unless particularly described, the integrated or distributed example is also included in the scope of the present disclosure.
[0048] Herein, elements described in various examples may not be necessarily essential and may be partially selectable. Therefore, an example including a partial set of elements described in an example is also included in the scope of the present disclosure. Also, an example that additionally includes another element to elements described in various examples is also included in the scope of the present disclosure.
[0049] The description described herein is related to a wireless communication network, and an operation performed in a wireless communication network may be performed in a process of controlling a network and transmitting data by a system that controls a wireless network, e.g., a base station, or may be performed in a user equipment connected to the wireless communication network.
[0050] It is apparent that various operations performed for communication with a terminal in a network including a base station and a plurality of network nodes may be performed by the base station or by other network nodes in addition to the base station. Here, the term ‘base station (BS)’ may be interchangeably used with other terms, for example, a fixed station, a Node B, eNodeB (eNB), gNodeB (gNB), and an access point (AP). Also, the term ‘terminal’ may be interchangeably used with other terms, for example, user equipment (UE), a mobile station (MS), a mobile subscriber station (MSS), a subscriber station (SS), and a non-AP station (non-AP STA).
[0051] Herein, transmitting or receiving a channel includes a meaning of transmitting or receiving information or a signal through the corresponding channel. For example, transmitting a control channel indicates transmitting control information or a signal through the control channel. Likewise, transmitting a data channel indicates transmitting data information or a signal through the data channel.
[0052] In the following description, although the term “new radio (NR) system” is used to distinguish a system according to various examples of the present disclosure from the existing system, the scope of the present disclosure is not limited thereto.
[0053] A new radio (NR) system supports various subcarrier spacings (SCSs) by considering various scenarios, service requirements, potential system compatibility, and the like. Also, to overcome a poor channel environment, such as high pathloss, phase-noise, and frequency offset, occurring on a high carrier frequency, the NR system may support transmission of a physical signal/channel through a plurality of beams. Through this, the NR system may support applications, for example, enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC)/ultra Machine Type Communications (uMTC), and Ultra Reliable and Low Latency Communications (URLLC).
[0054] Here, 5G mobile communication technology may be defined by including the existing Long Term Evolution-Advanced (LTE-A) system as well as the aforementioned NR system. That is, 5G mobile communication technology may operate by considering backward compatibility with a previous system as well as a newly defined NR system. Therefore, following 5G mobile communication may include technology operating based on the NR system and a technology operating based on a previous system (e.g., LTE-A, LTE), and is not limited to a specific system.
[0055] First of all, the physical resource structure of the NR system to which the present disclosure is applied will be briefly described.
[0056]
[0057] In NR, a basic unit of a time domain may be T.sub.c=1/(Δf.sub.max.Math.N.sub.f) Here, Δf.sub.max=480.Math.10.sup.3 and N.sub.f=4096. Also, κ=T.sub.s/T.sub.c=64 may be a constant about a multiple relationship between an NR time unit and an LTE time unit. In LTE, T.sub.s=1/(Δf.sub.ref.Math.N.sub.f, ref), Δf.sub.ref=15.Math.10.sup.3 and N.sub.f,ref=2048 may be defined as a reference time unit.
[0058] Referring to
[0059] N.sub.TA represent the timing advance (TA) between downlink (DL) and uplink (UL). Here, a transmission timing of uplink transmission frame i is determined based on a downlink reception timing at a UE according to the following Equation 1.
T.sub.TA=(N.sub.TA+N.sub.TA,offset)T.sub.c [Equation 1]
[0060] N.sub.TA,offset denotes a TA offset value occurring due to a duplex mode difference and the like. Basically, in a frequency division duplex (FDD), N.sub.TA,offset=0. In a time division duplex (TDD), N.sub.TA,offset may be defined as a fixed value by considering a margin for a DL-UL switching time. For example, in the TDD (Time Division Duplex) of RF1 (Frequency Range 1) which is a sub-6 GHz or less frequency, N.sub.TA,offset may be 39936T.sub.c or 2600T.sub.C. 39936T.sub.C=20.327 μs and 25600T.sub.C=13.030 μs. Also, in FR2 (Frequency Range 2) which is millimeter wave (mmWave), N.sub.TA,offset may be 13792T.sub.C. At this time, 39936T.sub.C=7.020 μs.
[0061]
[0062] A resource element within a resource grid may be indexed based on each subcarrier spacing. Here, a single resource grid may be generated for each antenna port and for each subcarrier spacing. Uplink/downlink transmission and reception may be performed based on a corresponding resource grid.
[0063] A resource block (RB) on a frequency domain is configured of 12 REs and for every 12 Res, an index for one RB (n.sub.PRB) may be configured. The index for RB may be utilized within a specific frequency band or system bandwidth. The index for RB may be defined as shown in Equation 2 below. Here, N.sup.RB.sub.sc represents the number of subcarriers per one RB and k represents subcarrier index.
[0064] Numerologies may be variously configured to meet various services and requirements of the NR system. For example, one subcarrier spacing (SCS) may be supported in the LTE/LTE-A system, but a plurality of SCSs may be supported in the NR system.
[0065] A new numerology for the NR system that supports the plurality of SCSs may operate in frequency range or carrier, such as 3 GHz or less, 3 GHz-6 GHz, 6 GHZ-52.6 GHz, or 52.6 GHz or more, to solve an issue that a wide bandwidth is unavailable in frequency range or carrier such as 700 MHz or 2 GHz.
[0066] Table 1 below shows an example of the numerologies supported by the NR system.
TABLE-US-00001 TABLE 1 u Δf = 2.sup.u .Math. 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal
[0067] Referring to the above Table 1, the numerologies may be defined based on an SCS, a cyclic prefix (CP) length, and the number of OFDM symbols per slot, which are used in an OFDM system. The aforementioned values may be provided to a UE through upper layer parameters, DL-BWP-mu and DL-BWP-cp, for the downlink, and through upper layer parameter, UL-BWP-mu and UL-BWP-cp, for the uplink.
[0068] Also, for example, referring to the above Table 1, if μ=2 and SCS=60 kHz, a normal CP and an extended CP may be applied. In other bands, only the normal CP may be applied.
[0069] Here, a normal slot may be defined as a basic time unit used to transmit a single piece of data and control information in the NR system. A length of the normal slot may basically include 14 OFDM symbols. Also, dissimilar to a slot, a subframe may have an absolute time length corresponding to 1 ms in the NR system and may be used as a reference time for a length of another time section. Here, for coexistence and backward compatibility of the LTE and the NR system, a time section, such as an LTE subframe, may be required for an NR standard.
[0070] For example, in the LTE, data may be transmitted based on a transmission time interval (TTI) that is a unit time. The TTI may include at least one subframe unit. Here, even in the LTE, a single subframe may be set to 1 ms and may include 14 OFDM symbols (or 12 OFDM symbols).
[0071] Also, in the NR system, a non-slot may be defined. The non-slot may refer to a slot having the number of symbols less by at least one symbol than that of the normal slot. For example, in the case of providing a low latency such as an Ultra-Reliable and Low Latency Communications (URLLC) service, a latency may decrease through the non-slot having the number of slots less than that of the normal slot. Here, the number of OFDM symbols included in the non-slot may be determined based on a frequency range. For example, a non-slot with 1 OFDM symbol length may be considered in the frequency range of 6 GHz or more. As another example, the number of symbols used to define the non-slot may include at least two OFDM symbols. Here, the range of the number of OFDM symbols included in the non-slot may be configured with a length of a mini slot up to (normal slot length)−1. Here, although the number of OFDM symbols may be limited to 2, 4, or 7 as a non-slot standard, it is provided as an example only.
[0072] Also, for example, an SCS corresponding to μ=1 and 2 may be used in the unlicensed band of 6 GHz or less and an SCS corresponding to μ=3 and 4 may be used in the unlicensed band above 6 GHz. Here, for example, if μ=4, it may be used for a synchronization signal block (SSB)
TABLE-US-00002 TABLE 2 u N.sup.slot.sub.symb N.sup.frame, u.sub.slot N.sup.subframe, u.sub.slot 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16
[0073] Table 2 shows the number of OFDM symbols per slot (N.sup.slot.sub.symb), the number of slots per frame (N.sup.frame,μ.sub.slot), and the number of slots per subframe (N.sup.subframe,μ.sub.slot) for the normal CP by subcarrier spacing setting. In Table 2, the values are based on the normal slot having 14 OFDM symbols.
TABLE-US-00003 TABLE 3 u N.sup.slot.sub.symb N.sup.frame,u.sub.slot N.sup.subframe,u.sub.slot 2 12 40 4
[0074] In Table 3, in the case of the extended CP applied (that is, μ=2 and SCS=60 kHz), shows the number of slots per frame and the number of slots per subframe based on the normal slot of which the number of OFDM symbols per slot is 12.
[0075] As described above, a single subframe may correspond to 1 ms on a time axis. Also, a single slot may correspond to 14 symbols on the time axis. For example, a single slot may correspond to 7 symbols on the time axis. Therefore, the number of slots and the number of symbols that may be considered may be differently set within 10 ms corresponding to a single radio frame. Table 4 may show the number of slots and the number of symbols according to each SCS. Although SCS of 480 kHz may not be considered in Table 4, the present disclosure is not limited to such examples.
TABLE-US-00004 TABLE 4 Number of Number of slots Number of slots in 10 ms 14 in 10 ms 7 symbols symbols in SCS symbols in 1 slot) in 1 slot) 10 ms 15 kHz 10 20 140 30 kHz 20 40 280 60 kHz 40 80 560 120 kHz 80 160 1120 240 kHz 160 320 2240 480 kHz 320 640 4480
[0076] The V2X service may support a set of basic requirements for V2X services. The requirements are designed basically in sufficient consideration of a road safety service. Here, V2X UEs may exchange autonomous status information through a sidelink. Also, V2X UEs may exchange the information with infrastructure nodes and/or pedestrians.
[0077] The V2X service (e.g., LTE Rel-15) may support at least one of a carrier aggregation in a sidelink, a high order modulation, a latency reduction, a transmit (Tx) diversity, and sTTI (Transmission Time Interval). For this purpose, new features may be applied to the V2X communication. More particularly, V2X UE may operate in consideration of coexistence with other V2X UEs. For example, V2X UE may use the same resource pool as other V2X UEs.
[0078] For example, technical features may be classified largely based on four categories as represented by the following Table 5 by considering use cases for supporting a V2X service as system aspect (SA) 1, but are not limited thereto. In Table 5, “Vehicles Platooning” may be technology that enables a plurality of vehicles to dynamically form a group and similarly operate. “Extended Sensors” may be technology that enables exchange of data gathered from sensors or video images. “Advanced Driving” may be technology that enables a vehicle to drive based on semi-automation or full-automation. “Remote Driving” may be technology for remotely controlling a vehicle and technology for providing an application. Based thereon, further description related thereto may be given by the following Table 5.
TABLE-US-00005 TABLE 5 Vehicles Platooning Vehicles Platooning enables the vehicles to dynamically form a platoon travelling together. All the vehicles in the platoon obtain information from the leading vehicle to manage this platoon. The information allows the vehicles to drive closer than normal in a coordinated manner, going to the same direction and travelling together. Extended Sensor Extended Sensor enables the exchange of raw or processed data gathered through local sensors or live video images among vehicles, road site units, devices of pedestrian and V2X application servers. The vehicles can increase the perception of their environment beyond of what their own sensors can detect and have a more broad and holistic view of the local situation. High data rate is one of the key characteristics. Advanced Driving Advanced Driving enables semi-automated or full-automated driving. Each vehicle and/or RSU shares its own perception data obtained from its local sensors with vehicles in proximity and that allows vehicles to synchronize and coordinate their trajectories or maneuvers. Each vehicle shares its driving intention with vehicles in proximity too. Remote Driving Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive by themselves or remote vehicles located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. High reliability and low latency are the main requirements.
[0079] Also, the SA1 may support the case of operating in various systems (e.g., LTE and NR) as enhanced V2X (eV2X) support technology for supporting the V2X service. For example, an NR V2X system may be a first V2X system. Also, an LTE V2X system may be a second V2X system. That is, the NR V2X system and the LTE V2X system may be different V2X systems.
[0080] The following describes a method for satisfying low latency and high reliability required in an NR sidelink based on the NR V2X system. However, the same or similar composition may be expanded and applied to the LTE V2X system, and is not limited to following examples. That is, in the LTE V2X system, the present disclosure may apply to an interactable portion.
[0081] Here, NR V2X capability may not be limited to essentially supporting only V2X services and V2X RAT to be used may be selected.
[0082] As a detailed example, a physical channel, a signal, a basic slot structure, and a physical resource may be configured for the NR V2X. Here, an NR Physical Sidelink Shared Channel (NR PSSCH) may be a physical layer NR sidelink (SL) data channel. V2X UEs may exchange data and control information (e.g., 2.sup.nd SCI, CSI) through the NR PSSCH. An NR Physical Sidelink Control Channel (NR PSCCH) may be a physical layer NR SL control channel. The NR PSCCH refers to a channel for transmitting scheduling information of the NR SL data channel and control information (1.sup.st Sidelink Control Information (SCI)) including 2.sup.nd SCI indication. That is, a V2X UE may transmit control information for sidelink data communication to another V2X UE through PSCCH. An NR Physical Sidelink Feedback Channel (NR PSFCH) refers to a channel for transmitting physical layer NR Hybrid Automatic Repeat Request (HARQ) feedback information and a channel for transmitting HARQ-ACK feedback information corresponding to the NR SL data channel (i.e., PSSCH). The V2X UE may transmit data to another V2X UE and then may receive HARQ feedback information of the corresponding data through NR PSFCH. An NR Sidelink Synchronization Signal/Physical Sidelink Broadcast Channel (SLSS/PSBCH) block refers to a channel block in which an NR sidelink synchronization signal and a broadcast channel are transmitted in a single consecutive time. Here, the SLSS/PSBCH block may be periodically transmitted based on a set of one or more block indexes to support beam-based transmission in an NR frequency band. The synchronization signal includes a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The synchronization signal is generated based on at least one SLSSID value. The NR Physical Sidelink Broadcast Channel (PSBCH) refers to a channel for transmitting system information required to perform V2X sidelink communication. The NR PSBCH is transmitted with the SLSS and periodically transmitted based on a set of SLSS/PSBCH block indexes to support beam-based transmission.
[0083]
[0084] Referring to
[0085] Here, the number of PSSCH DMRSs may be configured according to an upper layer configuration and one or more PSSCH DMRSs may be configured according to a channel environment of UE. PSCCH (1.sup.st SCI) receives demodulation using DMRS of PSCCH (i.e., PSCCH DMRS) and is equally allocated and transmitted every four resource elements (REs) within a single resource block (RB). On the contrary, 2.sup.nd SCI is decoded using PSSCH DMRS.
[0086]
[0087] In detail, for example, referring to
[0088] Also, NR V2X quality of service (QoS) requirements may be considered. That is, delay, reliability, and a data rate may need to satisfy a predetermined condition as requirements for an NR V2X service. Here, the requirements may be configured as in Table 6 below and Table 7 may show PC5 QoS for NR V2X.
[0089] Here, to satisfy QoS requirements, access stratum (AS) level QoS management may be required. To this end, HARQ and CSI feedback associated with link adaptation may be required. Also, each of NR V2X UEs may have a different maximum bandwidth capability (max. BW capability). Considering this, AS level information that includes at least one of UE capability, QoS related information, radio bearer configuration, and physical layer configuration may be exchanged between NR V2X UEs.
TABLE-US-00006 TABLE 6 Delay: [3, 100 ms] Reliability: [90%, 99.999%] Data rate: up to 1 Gbps (TS22.186)
TABLE-US-00007 TABLE 7 Default Maximum Default Packet Packet Data Default PQI Resource Priority Delay Error Burst Averaging Value Type Level Budget Rate Volume Window Example Services 1 GBR 3 20 ms 10.sup.−4 N/A 2000 ms Platooning between UEs- (NOTE Higher degree of automation; 1) Platooning between UE and RSU-Higher degree of automation 2 4 50 ms 10.sup.−2 N/A 2000 ms Sensor sharing-higher degree of automation 3 3 100 ms 10.sup.−4 N/A 2000 ms Information sharing for automated driving-between UEs or UE and RSU-higher degree of automation 55 Non- 3 10 ms 10.sup.−4 N/A N/A Cooperative lane change- GBR higher degree of automation 56 6 20 ms 10.sup.−1 N/A N/A Platooning informative exchange-low degree of automation; Platooning-information sharing with RSU 57 5 25 ms 10.sup.−1 N/A N/A Cooperative lane change- lower degree of automation 58 4 100 ms 10.sup.−2 N/A N/A Sensor information sharing- lower degree to an RSU 59 6 500 ms 10.sup.−1 N/A N/A Platooning-reporting to an RSU 82 Delay 3 10 ms 10.sup.−4 2000 2000 ms Cooperative collision Critical bytes avoidance; GBR Sensor sharing-Higher degree (NOTE of automation; 1) Video sharing-higher degree of automation 83 2 3 ms 10.sup.−5 2000 2000 ms Emergency trajectory bytes alignment; Sensor sharing-Higher degree of automation NOTE 1: GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications. Editor's note: It is FFS if GBR and Delay Critical GBR can also be used for broadcast and groupcast. NOTE 1: For standardized PQI to QoS characteristics mapping, the table will be extended/updated to support service requirements for other identified V2X services. NOTE 2: The PQIs may be used for other services than V2X.
[0090] Hereinafter, a sidelink HARQ procedure is described. Whether V2X UE is to report HARQ feedback is indicated by upper layer (e.g., RRC) configuration and SCI signaling (e.g., 2.sup.nd SCI). For example, when the V2X UE performs communication based on a groupcast, whether to report the HARQ feedback may be determined based on a distance between a transmitting UE (Tx UE) and a receiving UE (Rx UE).
[0091] When the V2X UE performs at least one of unicast and groupcast, sidelink HARQ feedback may be enabled or disabled. Here, enabling/disabling of the HARQ feedback may be determined based on at least one of a channel condition (e.g., RSRP), a distance between Tx UE and Rx UE, and QoS requirements.
[0092] In the case of groupcast, whether to transmit HARQ feedback may be determined based on a physical distance between the Tx UE and the Rx UE. Here, when the HARQ feedback is performed based on the groupcast, the Rx UE may operate by feeding back a negative response only when PSSCH decoding fails. It may be an option 1 operation. On the other hand, when HARQ feedback is performed based on the groupcast, the Rx UE may operate by feeding back a positive response or a negative response based on whether PSSCH decoding succeeds and it may be an option 2 operation. In the option 1 operation of feeding back only a negative response as HARQ NACK based on the groupcast, if the physical distance between the Tx UE and the Rx UE is less than or equal to communication range requirements, feedback on PSSCH may be performed. On the contrary, if the physical distance between the Tx UE and the Rx UE is greater than the communication range requirements, the V2X UE may not perform feedback on PSSCH.
[0093] Here, a location of the Tx UE is indicated to the Rx UE through SCI associated with the PSSCH. The Rx UE may estimate a distance from the Tx UE based on information included in SCI and its location information and may operate as above.
[0094] Also, when unicast communication is performed based on V2X, a case in which sidelink HARQ feedback is enabled may be considered. The Rx UE may generate and transmit HARQ ACK/NACK for PSSCH depending on whether decoding of a corresponding transport block (TB) succeeds.
[0095] Then, an NR sidelink resource allocation mode refers to a mode in which a base station schedules a sidelink transmission resource. Here, a mode in which the base station schedules a sidelink transmission resource may be mode 1. For example, when the V2X UE is located within base station coverage, the V2X UE may receive sidelink resource information from the base station. On the contrary, there is a mode in which the V2X UE directly determines a resource for sidelink transmission between a sidelink resource configured by the base station/network and a pre-configured sidelink resource. Here, a mode in which the UE directly determines a sidelink transmission resource may be mode 2.
[0096] Also, a sidelink received signal strength indicator (SL RSSI) is defined as an average value (in [W]) of total received power measured from subchannels configured within OFDM symbols of a slot configured for PSCCH and PSSCH.
[0097] Also, the V2X UE may measure a sidelink Channel busy ratio (SL CBR) in slot n. Here, CBR measurement is performed within CBR measurement window ([n−a, n−1]). The CBR measurement window is configured based on an upper layer parameter value “timeWindowSize-CBR” and the above a value has one value of 100 or 100.Math.2.sup.μ slots. The CBR measurement refers to a value used to define a ratio of subchannels having an SL-RSSI value exceeding a predetermined threshold among subchannels in the entire resource pool.
[0098] For example,
[0099] Referring to
[0100] In detail, a has a positive value at all times in a time section (slots [n−a, n−1]) used for sidelink transmission. On the contrary, b within time (slots [n, n+b]) for counting the number of subchannels of a resource allowed for UE has a value of 0 or a positive value. Values of a and b are determined to satisfy all the conditions of a+b+1=1000 or 1000.Math.2.sup.μ slots and b<(a+b+1)/2 by UE implementation. As another example, values of a and b are set to use one value of 1000 or 1000.Math.2.sup.μ slots by upper layer parameter “timeWindowSize-CR”. Also, a value of n+b should not exceed a last transmission occasion of grant for current transmission. Here, a slot for CBR and CR may be a physical slot and the CBR and the CR may be measured every time transmission is performed.
[0101] When the V2X UE performs sidelink HARQ feedback transmission, the V2X UE may transmit feedback information based on PSFCH format 0. Here, PSFCH format 0 sequence may be generated based on Zadoff-Chu (ZC) sequence and sequence x(n) is generated based on the following Equation 3. The ZC sequence is generated through a that is a cyclic sequence, based on
x(n)=r.sub.u,v.sup.α,δ(n),n=0,1, . . . ,N.sub.sc.sup.RB−1 [Equation 3]
r.sub.u,v.sup.(α,δ)(n)=e.sup.jαn
[0102] Here, a plurality of base sequences is divided into sequence group number (u∈{0, 1, . . . , 29}) and base sequence V number in a corresponding group. One base sequence v=0 or two base sequences v=0/v=1 are configured in a sequence group according to a ZC sequence length. For example, when a PSFCH format is mapped on a single Physical Resource Block (PRB), only a single base sequence (v=0) may be present in the sequence group. Also, for example, sequence group number (u) may be determined based on hopping ID, but is not limited thereto. Here, if a sequence length is less than 36 (e.g., M.sub.ZC∈{6,12,18,24}), the base sequence may be determined based on the following Equation 5.
[0103] In Equation 5, a value of φ(n) may be determined based on the following Table 8. (e.g., sequence length M.sub.ZC=12). However, it is provided as an example only, if the sequence length differs, the value may be determined based on another table value.
TABLE-US-00008 TABLE 8 u φ(0), . . . , φ(11) 0 −3 1 −3 −3 −3 3 −3 −1 1 1 1 −3 1 −3 3 1 −3 1 3 −1 −1 1 3 3 3 2 −3 3 3 1 −3 3 −1 1 3 −3 3 −3 3 −3 −3 −1 3 3 3 −3 3 −3 1 −1 −3 4 −3 −1 −1 1 3 1 1 −1 1 −1 −3 1 5 −3 −3 3 1 −3 −3 −3 −1 3 −1 1 3 6 1 −1 3 −1 −1 −1 −3 −1 1 1 1 −3 7 −1 −3 3 −1 −3 −3 −3 −1 1 −1 1 −3 8 −3 −1 3 1 −3 −1 −3 3 1 3 3 1 9 −3 −1 −1 −3 −3 −1 −3 3 1 3 −1 −3 10 −3 3 −3 3 3 −3 −1 −1 3 3 1 −3 11 −3 −1 −3 −1 −1 −3 3 3 −1 −1 1 −3 12 −3 −1 3 −3 −3 −1 −3 1 −1 −3 3 3 13 −3 1 −1 −1 3 3 −3 −1 −1 −3 −1 −3 14 1 3 −3 1 3 3 3 1 −1 1 −1 3 15 −3 1 3 −1 −1 −3 −3 −1 −1 3 1 −3 16 −1 −1 −1 −1 1 −3 −1 3 3 −1 −3 1 17 −1 1 1 −1 1 3 3 −1 −1 −3 1 −3 18 −3 1 3 3 −1 −1 −3 3 3 −3 3 −3 19 −3 −3 3 −3 −1 3 3 3 −1 −3 1 −3 20 3 1 3 1 3 −3 −1 1 3 1 −1 −3 21 −3 3 1 3 −3 1 1 1 1 3 −3 3 22 −3 3 3 3 −1 −3 −3 −1 −3 1 3 −3 23 3 −1 −3 3 −3 −1 3 3 3 −3 −1 −3 24 −3 −1 1 −3 1 3 3 3 −1 −3 3 3 25 −3 3 1 −1 3 3 −3 1 −1 1 −1 1 26 −1 1 3 −3 1 −1 1 −1 −1 −3 1 −1 27 −3 −3 3 3 3 −3 −1 1 −3 3 1 −3 28 1 −1 3 1 1 −1 −1 −1 1 3 −3 1 29 −3 3 −3 3 −3 −3 3 −1 −1 1 3 −3
[0104] The single PSFCH format may transmit the HARQ-ACK information based on the ZC sequence. Here, the ZC sequence for HARQ-ACK information may be generated by determining sequence group u and sequence number v in the group. Then, a cyclic shift (CS) value is determined and a final ZC sequence for HARQ-ACK information is generated.
[0105] For example, a case in which the ZC sequence has 30 base sequences may be considered. Therefore, to generate a single base sequence, a sequence group u number to be selected needs to be determined and a detailed method may be the same as the following Equation 6.
[0106] In Equation 6, n.sub.s,f.sup.μ denotes a slot number within a radio frame and r.sub.u,v.sup.(α,β)(n) may be determined based on a parameter value of Equation 6. In detail, m.sub.cs may be differently configured according to a sidelink HARQ feedback transmission option based on the following Table 9 and Table 10. That is, different CS values may be allocated based on different HARQ-ACK. m.sub.0 may be determined based on Table 11. In Table 11, N.sub.CS.sup.PSFCH denotes the number of different CS values on a single PSFCH resource. Here, as a value of N.sub.CS.sup.PSFCH increases, it represents that the number of PSFCH resources multiplexed on the same resource increases. l denotes an OFDM symbol index within PSFCH transmission. l=0 corresponds to a first OFDM symbol within the PSFCH transmission. l′ denotes an OFDM symbol index within a slot and corresponds to a first OFDM symbol of PSFCH transmission within the slot. u=n.sub.ID mod 3 and v=0. Here, when n.sub.ID is configured through an upper layer, n.sub.ID is determined based on upper layer parameter “sl-PSFCH-HopID”. On the contrary, when n.sub.ID is not configured through the upper layer, n.sub.ID=0. Here, c.sub.init is n.sub.ID. Therefore, when n.sub.ID is configured through the upper layer, c.sub.init is determined based on the upper layer parameter “sl-PSFCH-HopID”. On the contrary, when n.sub.ID is not configured through the upper layer, c.sub.init=0. Also, m=0. As a detailed example, in the case of an ACK/NACK-based PSFCH transmission option, HARQ-ACK information (m.sub.cs) mapped from a CS pair may be the same as in the following Table 9. That is, HARQ-ACK information may be transmitted to a different sequence according to a CS value as shown in the following Table 9.
TABLE-US-00009 TABLE 9 HARQ-ACK Value 0 (NACK) 1 (ACK) Sequence cyclic shift 0 6
[0107] Also, for example, in the case of a PSFCH transmission option of feedback that transmits only a negative response (e.g., groupcast option 1), HARQ-ACK information (m.sub.cs) mapped from the CS pair may be the same as in the following Table 10. That is, a CS value may be set only for the negative response (NACK) in the HARQ-ACK information and a CS value may not be set for ACK that is not transmitted.
TABLE-US-00010 TABLE 10 HARQ-ACK Value 0 (NACK) 1 (ACK) Sequence cyclic shift 0 N/A
[0108] Also, a set (m.sub.0) of CS pairs may be the same as in the following Table 11. Here, N.sub.CS.sup.PSFCH denotes the number of different cyclic shift (CS) values on a single PSFCH resource. As described above, as a value of N.sub.CS.sup.PSFCH increases, the number of PSFCH resources multiplexed on the same resource may increase.
TABLE-US-00011 TABLE 11 m.sub.0 Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift N.sub.CS.sup.PSFCH Pair Index 0 Pair Index 1 Pair Index 2 Pair Index 3 Pair Index 4 Pair Index 5 1 0 — — — — — 2 0 3 — — — — 3 0 2 4 — — — 6 0 1 2 3 4 5
[0109] In the following, a new NR sidelink resource allocation operation method that considers requirements for various services using a device-to-device (D2D) sidelink, such as a V2X service, a public safety, a wearable, and an augmented reality/virtual reality (AR/VR) service is described. The NR sidelink may be applied for the aforementioned additional various service cases as well as the service based on Table 5. An NR sidelink frequency for NR sidelink operation may be present within FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz˜52.6 GHz). Also, the NR sidelink frequency for NR sidelink operation may be present within frequency unlicensed ITS bands and licensed bands ITS. Therefore, the NR sidelink may be configured in consideration of applicability in various frequency bands. Also, the NR sidelink may operate using an Uu link that is a wireless access interface between a base station and a UE. In particular, when the UE is connected within base station coverage, configuration related to sidelink data transmission and reception and sidelink physical resource allocation may be configured by the base station through the Uu link. Therefore, an NR V2X sidelink transmission and reception procedure needs to be configured in consideration of Uu link of LTE (ng-eNB)/NR (gNB) that is 3GPP NG-RAN. Although the term “base station” is used in the following for clarity of description, the base station may be ng-eNB or gNB in the NG-RAN. The present disclosure is not limited to the aforementioned embodiment.
[0110] Regarding an NR sidelink operation, a mode 2 resource allocation method may be a resource allocation mode in which a Tx UE senses and selects a resource (on the contrary, as described above, mode 1 is a mode in which the base station indicates a resource for NR sidelink transmission and reception), which is described above. That is, the Tx UE may directly configure a resource for the NR sidelink without scheduling from the base station. The mode 2 resource allocation method may have low reception reliability (e.g., packet reception rate (PRR), packet inter-reception (PIR)) compared to the mode 1 method in which a sidelink resource is allocated and controlled by the base station.
[0111] Here, since the Tx UE directly senses and selects a sidelink resource, the Tx UE that operates in mode 2 may not recognize a hidden node UE and accordingly, may have low reliability compared to a case in which an NR sidelink resource is selected by the base station. Also, since the Tx UE directly senses and selects the resource, the Tx UE may not recognize collision/interference compared to a case in which scheduling is performed by the base station. Also, when the Tx UE operates based on a half-duplex method, the Tx UE may not avoid a situation in which transmission and reception collide and may have low reliability accordingly. In providing various services through NR sidelink, requirements for service provision need to be satisfied. A new resource allocation method is required to enhance reception reliability and transmission and reception delay of mode 2 operation.
[0112]
[0113] The mode 2 resource allocation method refers to a method in which a Tx UE performs resource sensing and then directly selects and transmits a resource. Regarding an issue of decreasing reliability of the mode 2 resource allocation method, (a) of
[0114] As another example, when the Tx UEs (UE1 610-1 and UE3 610-3) simultaneously select the same resource or when a single Tx UE performs resource reservation and then there is no enough time for another Tx UE to verify reservation information, the Tx UEs (UE1 610-1 and UE3 610-3) may not readily recognize each other and a resource collision may occur accordingly. For example, when a Tx UE performs aperiodic transmission or performs fast transmission based on short packet delay budge (PDB), time may be insufficient for the Tx UE to verify reservation information of another Tx UE.
[0115] Referring to (b) of
[0116] Referring to (c) of
[0117] Referring to (d) of
[0118] An inter-UE coordination technique may need to be considered in consideration of the above issue. That is, a Tx UE may receive resource-related information from a coordination UE (C-UE) and may select a resource. In the following, a detailed method is described. Also, in the following, the inter-UE coordination technique is referred to as a resource coordination procedure. That is, a procedure in which the Tx UE receives resource-related information from the C-UE and selects a resource may be a resource coordination procedure. However, it is a name only for clarity of description, and the present disclosure is not limited thereto.
[0119] In the mode 2 resource allocation method of sensing, by the Tx UE, and directly selecting a resource as in
[0120] The non-hierarchical mutual UE coordination method may refer to a method of providing only information helpful to D2D resource allocation and not providing scheduling information related to a direct resource allocation. That is, the hierarchical mutual UE coordination method and the non-hierarchical UE coordination method may be distinguished depending on whether the C-UE directly performs sidelink resource scheduling on a mode 2 Tx UE. Here, the hierarchical mutual UE coordination method and the non-hierarchical UE coordination method are provided as examples only and may be named differently.
[0121] In the following, a resource allocation method of a mode 2 UE is described based on the non-hierarchical UE coordination method. That is, a Tx UE may perform sidelink transmission by receiving information related to resource allocation from a C-UE and by selecting a resource based on the received information. For example, the following new resource allocation method for the mode 2 UE may be applied based on any one or at least one of unicast, groupcast, and broadcast as a specific cast type. For example, a new mode 2 Tx UE that needs to select a resource for a unicast transmission packet may receive in advance information that may be helpful for a resource selection from an Rx UE that is a unicast pair UE and then may perform the resource selection for transmission of the unicast transmission packet. Additionally, a new mode 2 Tx UE having a groupcast transmission packet may acquire resource coordination information for the corresponding groupcast transmission from a specific UE (e.g., a UE having a specific member ID) within the corresponding group.
[0122] As another example, the following resource allocation method of the mode 2 UE may apply to all the cast types regardless of a cast type and is not limited to the aforementioned embodiment.
[0123] Therefore, at least one of or more combinations of the following methods may be selectively or equally applied according to a cast type that is considered between UEs that perform a mutual UE coordination method.
[0124] In the following, an operation of a UE having capability of performing an operation related to coordination information request and coordination information transmission is described. That is, a sidelink UE may determine whether a specific UE may perform a proposed operation according to UE capability. Also, a UE having the capability may perform the aforementioned operation based on at least one or a combination of an additional execution condition (or configuration) and signaling.
[0125] In detail, when a resource of the mode 2 UE is allocated based on the non-hierarchical mutual UE coordination method, a non-hierarchical mutual UE coordination request may be triggered. Regarding a situation in which the non-hierarchical mutual UE coordination method is required, a C-UE needs to recognize a situation in which resource selection of the mode 2 Tx UE (hereinafter, Tx UE) is required. That is, the Tx UE or the C-UE may recognize a point in time at which the new resource allocation method applies and a corresponding situation and may trigger a non-hierarchical mutual UE coordination procedure. For example, when signaling or a specific condition is satisfied, the non-hierarchical mutual UE coordination procedure may be performed by the Tx UE or the C-UE. Here, the C-UE may be an Rx UE or a unit (e.g., RSU) capable of performing sidelink transmission and reception. As another example, the C-UE may be another UE adjacent to the Tx UE or unit capable of performing sidelink transmission and reception. The C-UE may be a UE for cooperating resource allocation of the Tx UE and is not limited to a specific type UE. For example, at least one of the Tx UE, the Rx UE, the C-UE, and the base station may be present in consideration of a mutual C-UE.
[0126]
[0127] Referring to (a) of
[0128] Hereinafter, resource set information provided by a C-UE may include information resource preferred by a Tx UE or a resource that needs to be excluded, that is, nonpreferred by the Tx UE.
[0129] Referring to (b) of
[0130] Referring to (c) of
[0131] Also, for example, in
[0132] The D2D coordination resource allocation procedure may be performed based on explicit signaling. As another example, D2D coordination resource allocation may be performed depending on whether a specific condition and configuration are satisfied.
[0133] When the D2D coordination resource allocation procedure is explicitly performed, the Tx UE may transmit explicit signaling. The Tx UE may be the mode 2 Tx UE that senses and directly selects a resource or the mode 1 Tx UE that receives resource scheduling from the base station. That is, the mode 2 Tx UE or the mode 1 Tx UE may transmit explicit signaling for the D2D coordination resource allocation procedure. As another example, the base station may transmit explicit signaling for the D2D coordination resource allocation procedure. In the following, description is made based on the Tx UE for clarity of description. Here, the Tx UE may be the mode 2 Tx UE and the mode 1 Tx UE. Also, although the base station may perform the same operation as the following operation of the Tx UE, the following description is made based on the Tx UE for clarity of description.
[0134] Also, for example, explicit signaling for the coordination resource allocation procedure may be performed based on at least one of unicast transmission and groupcast transmission.
[0135] In detail, for example, for explicit signaling for the D2D coordination resource allocation procedure, a Medium Access Control (MAC)/Radio Resource Control (RRC) layer of a UE may request a physical (PHY) layer for coordination request (CR) transmission. The MAC/RRC layer of the UE may provide resource configuration information for the CR transmission to the PHY layer and, based thereon, may request the PHY layer for the CR transmission.
[0136] As another example, without a request from an upper layer, the PHY layer of the UE may perform the CR transmission based on configuration provided from the upper layer.
[0137]
[0138] Referring to
[0139] Here, when the C-UE 820 transmits the coordination message, the C-UE 820 may transmit the coordination message to the Tx UE 810 based on at least one of a periodic method, an aperiodic method, and a semi-persistent method. For example, a coordination message transmission method may be pre-configured or may be indicated through additional signaling and is not limited to the aforementioned embodiment.
[0140] In the following, a method of delivering, by a C-UE, a resource coordination request message from a Tx UE is described. Here, even a case of using a message transmission method (or a transmission format) based on the following resource coordination request message transmission method may also apply according to a format or a type of coordination information provided from the C-UE to the Tx UE.
[0141] For example, when the C-UE simply provides only coordination information (minimum information) on resource reselection or reevaluation to the Tx UE, a size of a coordination information message may be similar to that of a coordination resource request message. Therefore, a transmission method or a transmission format for transmitting the coordination resource request may also apply to coordination information transmission. Hereinafter, although description is made with the assumption of the transmission method or format for the coordination resource request for clarity of description, it may apply to coordination resource information according to a format or a type of coordination resource information.
[0142] When the Tx UE requests coordination message transmission through the explicit signaling, the Tx UE needs to determine a signaling format for transmitting corresponding triggering information to the C-UE.
[0143] For example,
[0144] In detail, for example, when the Tx UE verifies a consistent collision occurrence probability or detects an occurrence of collision and when the Tx UE performs a (re)transmission resource selection, the Tx UE may need to transmit a resource coordination request message capable of minimizing the corresponding delay. That is, the resource coordination request message transmitted from the Tx UE may be for the (re)transmission resource selection. Considering this, the Tx UE may use the specific PSFCH resource for transmission of the resource coordination request message to assist (re)transmission resource selection in addition to HARQ feedback information.
[0145] As another example, when the Tx UE performs PSSCH transmission to an Rx UE, the Tx UE may transmit, to the Rx UE, resource coordination request information with PSSCH (sidelink data transmission). The Tx UE may transmit resource coordination request information to the Rx UE through a single field in SCI or a single field in 2.sup.nd SCI within PSCCH. Also, the Tx UE may transmit resource coordination request information with the PSSCH based on one of the following methods.
[0146] As another example, when the Rx UE transmits, to the Tx UE, feedback information on the PSSCH transmitted from the Tx UE, the Rx UE may transmit resource coordination information for resource reselection with HARQ feedback information on a transport block (TB) included in the corresponding PSSCH. Here, the Rx UE may transmit resource coordination information to the Tx UE based on resource allocation and reservation information received from the Tx UE. That is, without a request from the Tx UE, the Rx UE may transmit resource coordination information for additional resource reselection to the Tx UE based on the resource allocation and reservation information received from the Tx UE. The Tx UE that receives such HARQ feedback information and resource coordination information from the Rx UE may modify the resource reservation and allocation information in SCI in which the corresponding TB is scheduled.
[0147] Here, since resource coordination request information transmits only information on a resource coordination request/resource reselection request status, the corresponding information may be represented as 1 bit (or on/off keying). That is, the information may be 1-bit information indicating two cases, a case in which the Tx UE requests the resource coordination to the C-UE and a case in which the Tx UE does not request the resource coordination to the C-UE.
[0148] As another example, in addition to the above 1-bit information on the resource coordination request status, the Tx UE may request the C-UE for more detailed resource coordination request information that the Tx UE desires to receive. For example, the Tx UE may request the C-UE for a resource coordination request and a type or a format of desired resource coordination information. Here, type/format information of resource coordination may include at least one of a preferred resource, a nonpreferred resource, and channel measurement information (e.g., RSRP, RSSI, CBR, CR). The Tx UE may request the C-UE for a type or a format of preferred resource coordination information in the above information. Here, when the Tx UE transmits only a resource coordination request, only 1-bit information may be required. However, when the Tx UE transmits a type or a format of desired resource coordination information with the resource coordination request, the Tx UE needs to use 1 bit or more additional information bits to transmit the type or the format of desired resource coordination information. In the following, transmission formats in which the Tx UE transmits a 1-bt resource coordination request or a resource coordination request and type or format information of desired resource coordination information using more bits than 1 bit are described.
[0149] Here, since a PSFCH resource area is applied to all UEs in which a corresponding pool is configured for each resource pool (i.e., resource pool specific), a resource selection procedure for PSFCH transmission only may not be performed in OFDM symbol(s) for PSFCH transmission in a single PSFCH transmission slot. Therefore, a format for transmitting the 1-bit resource coordination request information may be configured by modifying a PSFCH format defined for sidelink HARQ-ACK transmission or may be configured in a new format.
[0150] As another example, when the Tx UE transmits, to the C-UE, a resource coordination status and a type or a format of resource coordination information that the Tx UE desires to receive in the future, the Tx UE may transmit 1-bit or more bits of information. Here, the Tx UE may transmit resource coordination information through an additional CS value or additional PSFCH. In detail, for example, when a resource coordination request and resource coordination information include a total of 2 bits, the Tx UE may transmit the resource coordination request and the resource coordination information to the C-UE using additional CS or two PSFCHs.
[0151] As another example, when the Tx UE transmits, to the C-UE, a type or a format of resource coordination information that the Tx UE desires to receive from the C-UE in the future, the C-UE may determine that the Tx UE requests resource coordination. In detail, when the Tx UE transmits the type or the format of desired resource coordination information to the C-UE, the resource coordination request may also be necessary and the resource coordination request may be regarded to be performed without separate signaling. Through this, the Tx UE may use a corresponding information bit excluding a code point that does not require a coordination information request to transmit resource coordination information. That is, the resource coordination request may be performed through an operation of the Tx UE that transmits the type or the format of desired resource coordination information and an associated information bit may be allocated for the type or the format of desired resource coordination information, but the present disclosure is not limited to the aforementioned embodiment. The following coordination request (CR) may be considered to include not only the resource coordination request but also the type or the format of desired resource coordination information.
[0152] For example, in
[0153] Here, a CR transmission period value may be configured based on the number of slots or the number of OFDM symbols. The UE may transmit CR information to the C-UE through the configured resource. The C-UE may receive the CR information and then provide coordination resource information (i.e., CM) to the Tx UE. When the Tx UE periodically performs CR transmission, the Tx UE may share an independent CR transmission resource or ID value with the C-UE to identify a corresponding link per cast link (e.g., unicast #0˜N, groupcast #0˜N, broadcast).
[0154] For example, PSFCH resource allocation that includes sidelink HARQ-ACK information may verify an associated PSFCH transmission resource based on a subchannel index and a slot index used to transmit PSSCH. Here, a resource for CR transmission may use a format distinguished from a feedback resource allocation method related to PSSCH transmission that includes sidelink HARQ-ACK information. For example, the corresponding format may be a PSFCH format 1 resource. However, it is only a name for clarity of description and the present disclosure is not limited to the corresponding name.
[0155] Here, PSFCH format 1 may be configured based on the same sequence as the PSFCH format (i.e., PSFCH format 0) that includes sidelink HARQ-ACK information. Here, since information on CR transmission is included, a format distinguished from the PSFCH format that includes sidelink HARQ-ACK information may be used.
[0156]
[0157] When a UE performs transmission for PSFCH that transmits sidelink HARQ-ACK information, the UE may configure a PSFCH physical resource block (PRB) set based on upper layer parameter “rbSetPSFCH”. PSFCH that transmits sidelink HARQ-ACK information may be allocated to a specific slot based on a predetermined period. Also, associated subchannels may be present in a slot in which the PSFCH that transmits sidelink HARQ-ACK information is configured and a PSFCH physical resource block may be configured in a subchannel. Through this, sidelink HARQ-ACK information may be transmitted.
[0158] Here, a PSFCH PRB resource for PSFCH format 1 for the resource coordination request may be additionally configured based on the parameter “rbSetPSFCH”.
[0159] For example, referring to
[0160] Also, resource allocation may be differently performed depending on whether CR transmission is performed standalone on a PSFCH format 1 PRB that is additionally configured for CR. For example, when CR transmission is performed standalone (standalone CR transmission), a resource indicating the CR transmission may indicate only 1-bit on/off information. That is, when transmission is performed on a dedicated allocation PSFCH resource for CR transmission and the UE acquires a request of CR information (positive CR), the UE may determine that the CR request is present. On the contrary, when the UE does not detect any signal on the corresponding resource, the UE may determine that the CR request is absent (negative CR).
[0161] As another example, an additional PSFCH resource configuration for CR may be required. That is, information on a CR request status may be mapped to a specific value and transmitted, similar to sidelink HARQ ACK/NACK.
[0162] For example, the following Table 12 may show a case in which a CR request status corresponding to 1 bit is mapped based on a CS value. Here, if the CR request is absent, the CS value may be set to 0 and if the CR request is present, the CS value may be set to 6.
TABLE-US-00012 TABLE 12 CR value No(0) Yes(1) Sequence cyclic shift 0 6
[0163] Here, when the Tx UE transmits CR information greater than 1 bit, the Tx UE may transmit the CR information through at least one of an additional CS/PRB value and/or an additional PSFCH format resource (e.g., simultaneous PSFCH transmissions). That is, when the Tx UE transmits resource coordination information to the C-UE with a resource coordination request status, the Tx UE may transmit CR information greater than 1 bit and, to this end, may use at least one of an additional CS/PRB value and/or an additional PSFCH format resource. For example, the following Table 13 may show a case in which the Tx UE transmits 2-bit CR information. Here, the CR information refers to 2-bit CR information for requesting at least one of a recommended resource set and channel information that the Tx UE desires to receive from the C-UE and each piece of information may be mapped to a CS value.
[0164] As another example, the Tx UE may use even information on a set of nonpreferred resources (i.e., a set of resources to be excluded) as a format for CR transmission through additional different CS values and additional PSFCH resources.
[0165] Also, the Tx UE may request a type or a format of preferred resource coordination information (i.e., CM) in addition to a CR status in CR information. For example, Table 13 may be used to request the C-UE using at least one of a set of resources recommended as preferred resource coordination information, a set of resources not-recommended (desired to be excluded), and channel measurement information (RSRP, CBR, or channel occupancy ratio) as a CR transmission resource.
TABLE-US-00013 TABLE 13 Recommended resource set and channel measurement {0, 0} {0, 1} {1, 0} {1, 1} Sequence cyclic shift 0 3 6 9
[0166] As another example, when the C-UE receives sidelink data from the Tx UE and reselection of a corresponding resource is required based on future resource reservation and allocation information on the corresponding sidelink data (e.g., when a consistent collision or a collision with another Tx UE is predicted), the C-UE may transmit, as a response, HARQ feedback transmission (if it is present) related to corresponding sidelink data transmission and signaling information indicating necessity of modification of scheduling information or resource reselection in an SCI format for the corresponding sidelink data transmission to the Tx UE based on a PSFCH channel. In this case, similar to the aforementioned embodiment, at least one of an additional CS/PRB value and/or an additional PSFCH format resource may be used.
[0167] As another example, a case in which sidelink HARQ ACK information and at least one of CR and CM are multiplexed may be considered. Here, the aforementioned CM may include only minimum information for resource coordination information (e.g., providing information on a resource reselection status by the C-UE).
[0168] In the case of multiplexing sidelink HARQ-ACK information in a CR (or CM) transmission slot (=PSFCH resource slot), positive CR (or CM) and sidelink HARQ-ACK information may be multiplexed on a PSFCH resource for CR information transmission.
[0169] For example, the number of resources of PSFCH format 1 within a single transmission slot for CR (or CM) transmission may be determined based on the following Equation 7.
R.sub.PRB,CS.sup.PSFCH1=M.sub.PRB.sup.PSFCH1.Math.N.sub.CS.sup.PSFCH1 [Equation 7]
[0170] In Equation 7, R.sub.PRB,CS.sup.PSFCH1 denotes the number of PSFCH format 1 resources configured for a resource coordination procedure request per single PSFCH format 1 occasion, and M.sub.PRB.sup.PSFCH1 denotes the number of PRBs of PSFCH format 1 configured by an upper layer for the resource coordination procedure request. M.sub.PRB.sup.PSFCH1 may be provided through upper layer signaling. N.sub.CS.sup.PSFCH1 denotes the number of CS pair indexes (CS-pair) for PSFCH format 1 transmission as shown in the following Table 14, and may be configured and provided in an upper layer. Here, a value of m.sub.0 may be determined per CS pair index by combining the following Table 14 and a value of N.sub.CS.sup.PSFCH1 (upper layer configuration). As shown in Equation 6, m.sub.0 may be a single value used to compute a CS value α. Indexing of PSFCH format 1 resources for CR transmission may be performed in ascending order from a PRB index within a physical resource block set of PSFCH format 1 configured for the purpose of CR and then CS values may be indexed.
TABLE-US-00014 TABLE 14 m.sub.0 Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift N.sub.CS.sup.PSFCH Pair Index 0 Pair Index 1 Pair Index 2 Pair Index 3 Pair Index 4 Pair Index 5 1 0 — — — — — 2 0 3 — — — — 3 0 2 4 — — — 6 0 1 2 3 4 5
[0171] Here, when the Tx UE transmits the triggering request information (CR or CM) through a PSFCH resource based on at least 1-bit information, the corresponding information may be distinguished based on CS mapping as in the following Table 16. As another example, when the Tx UE multiplexes and thereby transmits sidelink HARQ-ACK information and CR (CM) in the same PSFCH format 1 slot, it may be distinguished according to CS mapping corresponding to each bit combination as shown in the following Table 15.
[0172] Alternatively, in the case of performing sidelink HARQ-ACK transmission in a PSFCH format 1 resource for CR, the UE may simultaneously multiplex sidelink HARQ-ACK information bits using positive CR information and the following Table 16.
TABLE-US-00015 TABLE 15 SL HARQ-ACK and CR (or CM) value {0, 0} {0, 1} {1, 0} {1, 1} Sequence cyclic shift 0 3 6 9
TABLE-US-00016 TABLE 16 SL HARQ-ACK value No(0) Yes(1) Sequence cyclic shift 0 6
[0173] The UE that transmits CR information may need to determine a single PSFCH format 1 resource index among a total number of resources R.sub.PRB,CS.sup.PSFCH1 for transmitting a resource coordination procedure request (CR/CM). Here, the single resource may be determined according to the following Equation 8.
(P.sub.ID+M.sub.ID)mod R.sub.PRB,CS.sup.PSFCH1 [Equation 8]
[0174] In Equation 8, P.sub.ID denotes a layer 1 (L1) source ID or a destination ID of the C-UE and/or the Tx UE or an ID value determined through combination thereof. Also, M.sub.ID denotes a member ID of the C-UE and/or the Tx UE when a different resource needs to be allocated for each member in the case of groupcast, and may be 0 when a different resource allocation for each member is not required.
[0175]
[0176] At least one of CS pair values and a specific PRB among PSFCH PRBs for sidelink HARQ feedback information may be used as a resource for CR transmission.
[0177] Referring to
[0178] For example, the UE may configure PSFCH PRB resources (M.sub.PRB,set.sup.PSFCH PRBs) in a single resource pool. The UE determines PSFCH PRBs associated with a single subchannel or a plurality of subchannels per slot through [(i+j.Math.N.sub.PSSCH.sup.PSFCH).Math.M.sub.subch,slot.sup.PSFCH(i+1+j.Math.N.sub.PSSCH.sup.PSFCH).Math.M.sub.subch,slot.sup.PSFCH−1] PRBs within the configured resources. Also, the UE determines an associated PSFCH transmission PRB value (M.sub.subch.sup.PSFCH) for each subchannel and for each slot. The above M.sub.subch,slot.sup.PSFCH is determined based on the following Equation 9.
M.sub.subch,slot.sup.PSFCH=M.sub.PRB,set.sup.PSFCH/(N.sub.subch.Math.N.sub.PSSCH.sup.PSFCH), 0≤i<N.sub.PSSCH.sup.PSFCH,0≤j<N.sub.subch [Equation 9]
[0179] Here, in Equation 9, allocation order may index associated PSFCH PRBs for each subchannel for each slot in order In which associated slot index i initially increases and then associated subchannel index j increases. That is, a value of M.sub.subch,slot.sup.PSFCH corresponds to the number of associated PSFCH PRBs for each index combination of i and j.
[0180] Here, specific slot index (i) and subchannel index (j) values may be set to allocate a dedicated PRB resource for PSFCH format 1 for CR transmission. That is, to transmit sidelink HARQ-ACK information, a portion of allocated PSFCH PRB resources may be used as PSFCH format 1 PRBs for CR transmission. To this end, specific slot index(es) and subchannel index(es) for CR transmission may be configured as resources in the UE through upper layer configuration. To this end, the UE may receive resource allocation through scheduling, and, in the case of configuring a resource for CR transmission, may avoid additional resource overhead and may maximally reuse a PSFCH format for sidelink HARQ feedback information. For example, a resource of PSFCH format 1 for CR transmission may be determined based on the following Equation 10.
R.sub.PRB,CS.sup.PSFCH1=M.sub.PRB.sup.PSFCH1.Math.N.sub.CS.sup.PSFCH1 [Equation 10]
[0181] In Equation 10, R.sub.PRB,CS.sup.PSFCH1 denotes the number of PSFCH format 1 resources configured for a resource coordination procedure request (or inter-UE coordination) per single PSFCH1 occasion, and M.sub.PRB.sup.PSFCH1 denotes the number of PRBs of PSFCH format 1 associated with the configured specific slot/subchannel index. For example, in
TABLE-US-00017 TABLE 17 m.sub.0 Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift N.sub.CS.sup.PSFCH Pair Index 0 Pair Index 1 Pair Index 2 Pair Index 3 Pair Index 4 Pair Index 5 1 0 — — — — — 2 0 3 — — — — 3 0 2 4 — — — 6 0 1 2 3 4 5
[0182] Here, when the Tx UE transmits the triggering request information through a PSFCH resource based on at least 1-bit information, the corresponding information may be distinguished based on CS mapping as shown in the following Table 18 and Table 19. As another example, when the Tx UE multiplexes and thereby transmits sidelink HARQ-ACK information and CR (CM) in the same PSFCH format 1 slot, it may be distinguished according to CS mapping as shown in the following Table 17.
[0183] Alternatively, in the case of performing sidelink HARQ-ACK transmission in a PSFCH format 1 resource for CR, the UE may verify sidelink HARQ-ACK information bits using positive CR information and the following Table 18.
TABLE-US-00018 TABLE 18 SL HARQ-ACK and CR value {0, 0} {0, 1} {1, 0} {1, 1} Sequence cyclic shift 0 3 6 9
TABLE-US-00019 TABLE 19 SL HARQ-ACK value No(0) Yes(1) Sequence cyclic shift 0 6
[0184] The UE that transmits CR information may need to determine a single PSFCH format 1 resource index among a total number of resources R.sub.PRB,CS.sup.PSFCH1 for transmitting a resource coordination procedure request (CR/CM). Here, a single resource may be determined according to the following Equation 11.
(P.sub.ID+M.sub.ID)mod R.sub.PRB,CS.sup.PSFCH1 [Equation 11]
[0185] Here, P.sub.ID denotes a layer 1 (L1) source ID or a destination ID of the C-UE and/or the Tx UE or an ID value determined through combination thereof. Also, M.sub.ID denotes a member ID of the C-UE and/or the Tx UE when a different resource needs to be allocated for each member in the case of groupcast, and may be 0 when a different resource allocation for each member is not required.
[0186] As another example, the UE may perform explicit signaling for a CR request by defining a new SCI format/field. Here, SCI format 1 and SCI format 2-A or 2-B may be used for sidelink control information. Here, when the new SCI format (e.g., SCI format 2-C or SCI format 1-B) for the new transmission resource allocation method is defined, CR and/or CM information may be included in the corresponding SCI format. For example, a SCI format name is not limited to a specific name.
[0187] Here, to transmit the new SCI format that considers the new transmission resource allocation method, PSCCH (1.sup.st SCI)/2.sup.nd SCI/PSSCH transmission may be accompanied. In detail, a mode 2 UE that senses and directly selects a resource may need to perform corresponding SCI format transmission using a resource acquired through a resource selection procedure for PSCCH and PSSCH transmission to transmit CR information to the inside of the SCI format.
[0188] Here, for example, to minimize a delay that occurs based on a sidelink data transmission resource selection procedure, the UE may perform SCI format and/or PSSCH transmission that includes CR information by configuring and using a resource through periodic or aperiodic resource reservation. As another example, the UE may additionally include CR information in standalone PSCCH, PSSCH, or 2.sup.nd SCI format and thereby transmit the same. Here, a MAC/RRC layer of the UE may request a PHY layer for CR transmission. The MAC/RRC layer of the UE may provide resource configuration for CR transmission to the PHY layer and may request the CR transmission.
[0189] As another example, the PHY layer of the UE standalone may perform CR transmission without a request from an upper layer. Here, a method of determining a resource for SCI format or PSSCH transmission in which CR information is included may need to be configured. The SCI format/PSSCH transmission resource that includes CR information may use a resource within a candidate resource set that is determined through a resource sensing and resource selection procedure performed in the PHY layer. The UE may designate a specific resource within a set of candidate resources selected through the resource selection procedure as a resource for corresponding CR transmission. For example, the UE may select a single candidate resource from among temporally fastest resources within the selected set of candidate resources. Here, when the UE transmits CR information with other sidelink data transmission, the UE may transmit PSSCH (1.sup.st SCI format) that transmits control information of sidelink PSSCH data transmission on the resource acquired through the resource selection procedure to transmit a sidelink data TB or may transmit the CR information through the PSSCH. As another example, the UE may transmit CR information through the 2.sup.nd SCI format that transmits control information of sidelink PSSCH data transmission on the resource acquired through the resource selection procedure to transmit the sidelink data TB. For example, the 2.sup.nd SCI format that transmits CR information may be “2.sup.nd SCI format 2-C”. However, it is provided as an example only and may not be limited to the following name. For clarity of description, the 2.sup.nd SCI format that transmits CR information is referred to as 2.sup.nd SCI format 2-C.
TABLE-US-00020 TABLE 20 Value of 2-stage SCI format field 2-stage SCI format 00 SCI format 2-A 01 SCI format 2-B 10 SCI format 2-C (proposed new format) 11 Reserved
[0190] Here, the UE may determine a format to be use between SCI format 2-A and SCI format 2-B based on HARQ feedback option information and cast type information and may indicate the same through SCI format 1. SCI format 1 may include a 2.sup.nd SCI format indicator field as shown in Table 20 and, through this, may indicate the 2.sup.nd SCI format. Here, one reserved value in the 2.sup.nd SCI format indicator field of SCI format 1 may be newly defined for the purpose of a D2D coordination transmission format, which may be the aforementioned SCI format 2-C. Therefore, SCI format 2-C that is a new SCI format for a resource coordination procedure may be indicated through SCI format 1. The UE that receives SCI format 2-C may verify SCI field information for the resource coordination procedure within SCI format 2-C and may operate based thereon. For example, a CR field value may be present in SCI format 2-C as shown in Table 21 and a coordination triggering status may be verified based on CR field value information. That is, the C-UE that receives SCI format 2-C may receive explicit signaling from the Tx UE.
TABLE-US-00021 TABLE 21 Value of CR field CR information 0 No-coordination 1 Triggering of coordination
[0191] The Tx UE may transmit the above SCI format 2-C to the C-UE. Here, SCI format 2-C may further include information on the following Table 21 as well as CR information. The C-UE may configure a CM transmitted to the Tx UE based on information included in the following Table 21.
[0192] As another example, the Tx UE may additionally configure SCI format 1-B to 1.sup.st SCI format 1-A that is transmitted through PSCCH. The Tx UE may include information on the following Table 22 in SCI format 1-B and may transmit the same, and through this, may provide information for a CM configuration to the C-UE.
[0193] In detail, the Tx UE may provide L1 priority information to the C-UE for the resource sensing and selection procedure for CM configuration. The C-UE may use the L1 priority information of the Tx UE to determine an RSRP threshold and may replace the same with a pi value and thereby apply. Also, the Tx UE may provide remaining PDB (or validity timer or T2) information to indicate a CM window termination point in time to the C-UE. Also, the Tx UE may provide slot information in which a CM window start point in time is considered to the C-UE. Also, the Tx UE may provide information on at least one of a source ID, a destination ID, the number of subchannels per slot, a resource reservation period, and zone ID information to the C-UE. Also, the Tx UE may provide information on a communication range value with zone ID information. Here, the C-UE may determine a CM reporting status in consideration with a distance from the Tx UE and may receive information for this from the Tx UE. Also, the Tx UE may provide RS type information for sensing to the C-UE. Through this, the C-UE may verify an RSRP used to perform sensing between a PSSCH RSRP and a PSCCH RSRP. Also, the Tx UE may compare L1 priority information in SCI received from UEs around the C-UE and may provide a “p-preemption” value that is available when selecting a resource. Here, information shown in the following Table 22 is provided as an example only and other information may be further included.
TABLE-US-00022 TABLE 22 Inter-UE coordination request: This field refers to a field that indicates a coordination request status. Inter-UE coordination is enabled by upper layer signaling such as PC5-RRC and is available for CR when the inter-UE coordination request field is set to a value of 1. L1 priority: Then, for a resource sensing/selection procedure for CM configuration, the C-UE may replace received L1 priority information of the Tx UE with a pi value and may apply the same when determining an RSRP threshold, (pi from Tx UE, pj from SCI of other UEs) Remaining PDB (or validity timer or T2): To indicate a CM window termination point in time. In particular, it may be provided for configuration in consideration of validity information of CM information. T1 or T3 value (slot): To indicate a CM window start point in time. Source ID: source ID of Tx UE Destination ID: destination ID of a reception side Number of subchannels for PSSCH/PSCCH within a single slot (i.e., L sub-CHs) Resource reservation period value: resource reservation period value X percentage (%): a ratio of resource candidate sets to total resources. To satisfy the ratio, the ratio is adjusted by changing an RSRP ratio. Zone ID: ID corresponding to a physical area in which a UE is present. Communication range: Dissimilar to communication range that is considered to determine whether to perform the existing SL HARQ-feedback transmission with the zone ID, a CM reporting status may be determined based on a communication range value. If a distance between the Tx UE and the C-UE is far, validity of CM information provided from the C-UE may be degraded. Therefore, the CM reporting status may be determined based on communication range information and a corresponding threshold. RS type for sensing: Information on an RSRP value used for the C-UE to perform sensing between PSSCH- RSRP and PSCCH-RSRP may be provided. p-preemption: The C-UE may receive a p-preemption value that is available when selecting a resource through comparison of Li priority information in SCI received from neighboring UEs.
[0194] As another example, some bits (e.g., 1 bit) within a reserved field within SCI format 1-A may be used for the purpose of triggering. That is, some bits (e.g., 1 bit) within the reserved field may be used as a field for verifying a CR transmission status. For example, the reserved bit may be configured by upper layer parameter “sl-NumReservedBits”. Here, although some bits (e.g., 1 bit) within the reserved field may be defined as “inter-UE coordination triggering field”, it is provided as an example only and is not limited to a corresponding name. That is, CR information may be indicated through a bit newly added to the existing SCI format.
[0195] As another example, CR information may be indicated based on CRC scrambling. In detail, a CRC bit on PSSCH/PSCCH/PSBCH transmitted from the Tx UE may be masked (or scrambled) as the triggering (CR) information and thereby transmitted to the UE.
[0196] Here, additional information may be scrambled to a CRC bit for verifying an error check at the end of a payload of each channel. That is, CRC is attached at a rear of a data payload and generally transmitted. Here, CRC information bits to be attached may be scrambled with RNTI x.sub.rnti,0, x.sub.rnti,1, . . . , x.sub.rnti,15 and CR information bits (y.sub.cr,0, y.sub.cr,1, . . . , y.sub.cr,15) as below. If an RNTI value does not need to be used, scrambling is performed using CR information bits (y.sub.cr,0, y.sub.cr,1, . . . , y.sub.cr,15) only. Here, b.sub.k denotes a bitstream that includes a data payload and CRC parity bits. Relationship between b.sub.k and c.sub.k may be represented as the following Equation 12 and Equation 13.
c.sub.k=b.sub.k for k=0,1,2, . . . ,A+7 [Equation 12]
c.sub.k=(b.sub.k+x.sub.rnti,k-A-8+y.sub.cr,k-A-8)mod 2 for k=A+8,A+9,A+10, . . . ,A+23. [Equation 13]
[0197] As another example, the Tx UE may generate a sequence by additionally using the triggering (CR) information as an input value of DMRS sequence initialization and may provide the signaling. Here, sequence r.sub.i(m) may be generated as an initialization value for DMRS sequence generation based on Equation 14.
[0198] Also, pseudo-random sequence c(m) for DMRS sequence generation may be generated based on the following Equation 15. In Equation 15, 1 denotes an OFDM symbol within a slot, n.sub.s,f.sup.μ denotes a slot number within a frame, and N.sub.ID is provided by upper layer parameter “sl-DMRS-ScrambleID” and may be N.sub.ID∈{0, 1, . . . , 65535}. For example, if CR is triggered in the following Equation 15, N.sub.CR=1. On the contrary, if CR is not triggered, N.sub.CR=0 and, through this, a CR triggering status may be indicated.
c.sub.init=(2.sup.17(N.sub.symb.sup.slotn.sub.s,f.sup.μ+l+1)(2N.sub.ID+1)+2N.sub.ID+N.sub.CR)mod 2.sup.31 [Equation 15]
[0199] As another example, the C-UE may transmit CR-related information to the Tx UE through upper layer signaling different from other signaling options, and the present disclosure is not limited to the aforementioned embodiment.
[0200] The Tx UE may transmit the CR information to the C-UE and may explicitly signal a resource coordination procedure request to the C-UE.
[0201] Explicit signaling of the Tx UE provided for the resource coordination procedure request is discussed above and the C-UE that receives the corresponding explicit resource coordination procedure request may generate information for resource coordination and may transmit the generated information to the Tx UE.
[0202] As another example, when a specific condition or a specific configuration is satisfied without explicit signaling of the Tx UE, the C-UE may perform the resource coordination procedure. Hereinafter, the specific condition or the specific configuration for the C-UE to perform the resource coordination procedure is described.
[0203]
[0204] Referring to
[0205] Here, the C-UE 1220 may sense conditions that occur based on at least one of the aforementioned hidden node issue, half-duplex communication issue, and resource collision issue. When the C-UE 1220 senses a case that the proposed condition/configuration is satisfied, the C-UE 1220 may generate CM information and may transmit the CM information to the Tx UE 1210. The Tx UE 1210 may perform resource reselection based on the CM information. That is, when the specific condition is satisfied even without explicit signaling for a resource coordination procedure request from the Tx UE 1210, the C-UE 1220 may generate CM information and may transmit the CM information to the Tx UE 1210. Here, the specific condition/configuration may be configured based on at least one of continuous collision detection, poor channel environment detection, and high CBR measurement and may be configured in other forms.
[0206] When the C-UE 1220 transmits the CM information to the Tx UE 1210, the C-UE 1220 may transmit the CM information to the Tx UE 1210 based on at least one of a periodic method, an aperiodic method, and a semi-persistent method.
[0207] In detail, for example, a triggering condition (or configuration condition) for the C-UE 1220 to generate and transmit CM information may be configured in consideration of each situation. Regarding the hidden node issue, when a resource collision is predicted or when a collision occurs as a result of verifying, by the C-UE 1220, an SCI format received from neighboring Tx UE(s), it may be determined that the triggering condition is satisfied. That is, when the C-UE verifies resource reservation information and resource allocation information in the SCI format received from the neighboring Tx UEs and a resource collision between different Tx UEs is verified, the C-UE may generate and transmit CM information that includes information on the corresponding colliding resource.
[0208] For example,
[0209] In detail, the UE2 1320 may receive SCI format 1-A and/or SCI format 2 (e.g., 2-A, 2-B, or 2-C) from neighboring Tx UEs (UE1 1310 and UE3 1330). The UE2 1320 may verify at least one of resource reservation and allocation information received from an SCI format, ID information associated with each Tx UE, cast type information, and HARQ operation status information. Here, the ID information may include at least one of a source ID and a destination ID. Here, when a portion of or all of the reserved and scheduled resource information and allocation information overlaps, an RSRP measurement value of SCI received to indicate and reserve the overlapping resource may be verified. Here, a case in which a portion of or all of the reserved and scheduled resource information and allocation information overlaps may include a case before the collision occurs or a case in which the collision has already occurred by verifying reservation and scheduling resource information from the SCI format. Here, if an RSRP measurement value of received SCI is greater than a first threshold and a difference in RSRP measurement values of SCI formats received from the Tx UEs or each RSRP measurement value is less than a second threshold, the C-UE may trigger the coordination resource procedure. This threshold application method may apply to a case in which the C-UE is an Rx UE that is a UE intended by the corresponding SCI formats. Here, the first threshold and the second threshold may be configured by priority values within the SCI formats received from the neighboring Tx UEs, each priority value (prio_RX), or upper layer parameters (e.g., ThresRSRP(prio_Rx #0, prio_Rx #1, . . . ) for each combination. The first threshold may preferentially consider an SCI format having an RSRP value greater than the corresponding threshold in consideration of priority for data transmission associated with the received SCI formats, for the coordination resource procedure. Additionally, the second threshold may be considered to configure a difference in RSRP values of one or more received SCI formats or a level of an RSRP value of each of the received SCI formats. In the latter case, the second threshold may correspond to a threshold of an RSRP measurement value of a minimum considerable SCI format. When the above condition is satisfied and resource coordination information is triggered, the C-UE may provide resource coordination information to a specific Tx UE or an arbitrary Tx UE by considering at least one of a source ID and a destination ID within a 2.sup.nd SCI format. Here, for example, the C-UE may not verify the source ID and destination ID information based on at least one of a cast type of the Tx UE and an HARQ operation status. Here, the source ID and destination ID information may be included in the 2.sup.nd SCI format for at least one of the cast type and the HARQ operation and thereby transmitted. Therefore, the C-UE needs to decode all of 1.sup.st SCI and 2.sup.nd SCI received from the neighboring Tx UEs to verify the corresponding information. Here, when the C-UE decodes only the Pt SCI, the C-UE may transmit resource coordination information to neighboring Tx UEs through broadcast instead of transmitting the resource coordination information to the specific Tx UE.
[0210] As another example, if an RSRP measurement value of an SCI format received to indicate and reserve an overlapping resource is greater than a threshold, the C-UE may trigger the resource coordination procedure. Here, the threshold may be configured by upper layer parameter (e.g., ThresRSRP (prio_Rx)) based on a priority (prio_RX) value within the received SCI format.
[0211] As another example, if sidelink HARQ feedback is enabled in the C-UE and the C-UE receives NACK information greater than a specific threshold (e.g., ThresNACK(prio_Rx)), the C-UE may trigger the resource coordination procedure. Also, for example, when a data reception collision is detected, such as in a case in which the C-UE detects at least one PSCCH/PSSCH transmission having a low RSRP value and fails in data decoding, the C-UE may trigger the resource coordination procedure.
[0212] As another example,
[0213] Referring to
[0214] Here, the C-UE 1430 may receive SCI from a neighboring Tx UE and may verify SCI format information. At least one of a resource in which which transmission is reserved by the corresponding Tx UE and resource allocation information, ID information, cast type information, and HARQ operation status information may be verified within the received SCI format (SCI format 1-A and/or SCI format 2 (e.g., 2-A, 2-B or 2-C). Here, the ID information may include at least one of a source ID and a destination ID. When transmission is performed through a reousrce reserved or allocated by the Tx UE, the C-UE may verify whether the resource overlaps on the same time. Here, a case in which a portion of or all of the reserved and schedule resource information and allocation information overlaps may include a case before the collision occurs or a case in which the collision has already occurred by verifying reservation and scheduling resource information from the SCI format. Here, the C-UE may verify an RSRP measurement value of SCI that indicates the overlapping resource and indicates reservation. Here, if the RSRP measurement value of received SCI is greater than a first threshold and a difference in RSRP measurement values of SCI formats received from Tx UEs or each RSRP measurement value is less than a second threshold, the C-UE may trigger the coordination resource procedure. Here, the first threshold and the second threshold may be configured by priority values within the received SCI formats, each priority (prio_RX) value, or upper layer parameters (e.g., ThresRSRP(prio_Rx #0, prio_Rx #1, . . . ) for each combination. The first threshold may preferentially consider an SCI format having an RSRP value greater than the corresponding threshold in consideration of priority for data transmission associated with the received SCI formats, for the coordination resource procedure. Additionally, the second threshold may be considered to configure a difference in RSRP values of one or more received SCI formats or a level of an RSRP value of each of the received SCI formats. In the latter case, the second threshold may correspond to a threshold of an RSRP measurement value of a minimum considerable SCI format. When the above condition is satisfied and resource coordination information is triggered, the C-UE may provide resource coordination information to a specific Tx UE or an arbitrary Tx UE by considering at least one of a source ID and a destination ID within a 2.sup.nd SCI format. Here, for example, the C-UE may not verify the source ID and destination ID information based on at least one of a cast type of the Tx UE and an HARQ operation status. Here, the source ID and destination ID information may be included in the 2.sup.nd SCI format for at least one of the cast type and the HARQ operation and thereby transmitted. Therefore, the C-UE needs to decode all of Pt SCI and 2.sup.nd SCI received from the neighboring Tx UEs to verify the corresponding information. Here, when the C-UE decodes only the Pt SCI, the C-UE may transmit resource coordination information to neighboring Tx UEs through broadcast instead of transmitting the resource coordination information to the specific Tx UE.
[0215] As another example, if an RSRP measurement value of an SCI format received to indicate and reserve an overlapping resource is greater than a threshold, the C-UE may trigger the resource coordination procedure. Here, the threshold may be configured by upper layer parameter (e.g., ThresRSRP (prio_Rx)) based on a priority (prio_RX) value within the received SCI format.
[0216] Here, for example, only when all the conditions corresponding to
[0217] Also, for example, a resource overlapping status may be determined based on a specific period of time. That is, validity for resource overlapping may be identified during the specific period of time. In detail, the specific period of time may be considered to determine resource overlapping. The C-UE may define that a resource overlapping status verified from received SCI format information is valid up to a time before a specific period of time (e.g., T4 time (unit: ms, the number of OFDM symbols or the number of slots) compared to a period of time corresponding to the actually overlapping resource. Here, the time before the specific period of time may include an upper layer processing time and a processing time required for sidelink channel transmission and reception of a UE.
[0218] As another example, the C-UE may verify an overlapping resource and then define that it is valid during a specific period of time (e.g., T4 time (unit: ms, the number of OFDM symbols or the number of slots). Here, the specific period of time may be defined to be valid up to a time that includes an upper layer processing time and a processing time required for sidelink channel transmission and reception of a UE.
[0219] Also, the C-UE may verify whether an SCI format that is received by the C-UE and from which resource overlapping is verified is intended as an Rx UE and, based thereon, may differently determine a type of coordination information. For example, when the C-UE performs the resource coordination procedure as a third party, the C-UE may provide at least one Tx UE with information regarding at least which resource overlaps and ID information (e.g., source ID/destination ID/member ID) on overlapping another Tx UE and may perform the resource coordination procedure using the same although SCI reception is not intended.
[0220]
[0221] Referring to
[0222] Here, in this process, when the UE2 1520 transmits SCI for performing sidelink transmission to the UE3 1530, the UE1 1510 may receive the SCI transmitted from the UE2 1520. Here, the corresponding SCI may include SCI format 1-A. Also, the corresponding SCI may additionally include SCI format 2-A or SCI format 2-B. Here, SCI format 1A may include resource allocation and resource reservation information and SCI format 2 (2-A/2-B) may include source ID information and destination ID information of a UE for corresponding sidelink data transmission. That is, the UE1 1510 may decode SCI transmitted from the UE2 1520 and may recognize that the UE2 1520 selects a resource for sidelink data transmission to the UE3 1530.
[0223] Here, when a transmission resource of the UE1 1510 and a transmission resource of the UE2 1520 overlap, a corresponding resource may not be excluded from a transmission candidate resource set although an RSRP value of SCI is greater than a threshold. In detail, through a resource sensing procedure performed to generate CM information, the C-UE 1540 may provide the CM information on a preferred resource or a nonpreferred resource for sidelink data reception to the UE1 1510. Here, the UE1 1510 may determine a transmission resource based on information received from the C-UE 1540. Here, although the C-UE 1540 may receive a transmission signal transmitted from the UE2 1520, a signal of the UE2 1520 may be weak considering a mutual distance. Therefore, although the corresponding resource overlaps a resource of the UE2 1520, the C-UE 1540 may select the corresponding resource as a preferred resource in consideration of the fact that the transmission signal is weak. Therefore, although the UE1 1510 verifies SCI of the UE2 1520 based on the CM information received from the C-UE 1540, the UE1 1510 may not exclude the overlapping resource as the transmission resource.
[0224] Regarding a detailed operation, the UE1 1510 may receive CM information from the C-UE 1540. Here, the CM information may include coordination resource information. The UE1 1510 may receive and decode SCI of neighboring UEs by sensing transmission of the neighboring UEs. When resource allocation and reservation information verified from the SCI received by the UE1 1510 overlaps preferred resource information through coordination resource information, the UE1 1510 may not exclude the overlapping resource from the candidate resource set based on CM information of the C-UE 1540. That is, the UE1 1510 may provide a candidate set to an upper layer and may use the same as a final transmission candidate resource without excluding the corresponding resource from the candidate resource set for sidelink data transmission.
[0225]
[0226] Referring to
[0227] In operation S1620, the C-UE may generate a coordination message based on the coordination request. Here, the coordination message may include information on resource configuration of the Tx UE. For example, when the C-UE is an Rx UE, preferred resource information or nonpreferred resource information may be included in the coordination message. As another example, when the C-UE is a third UE, the C-UE may include resource allocation information using SCI information received from neighboring Tx UEs, which is described above.
[0228] In operation S1630, the C-UE may transmit the generated coordination message to the Tx UE. Here, the Tx UE may perform resource reselection based on the coordination message. For example, the Tx UE may directly reselect a resource based on the coordination message received from the C-UE. That is, as described above, it may be a non-hierarchical mutual coordination method.
[0229]
[0230] Referring to
[0231]
[0232] A base station device 1800 may include a processor 1820, an antenna device 1812, a transceiver 1814, and a memory 1816.
[0233] The processor 1820 may perform baseband-related signal processing and may include an upper layer processing unit 1830 and a physical (PHY) layer processing unit 1840. The upper layer processing unit 1830 may process an operation of a medium access control (MAC) layer, a radio resource control (RRC) layer, or more upper layers. The PHY layer processing unit 1840 may process an operation (e.g., uplink received signal processing, downlink transmission signal processing, etc.) of a PHY layer. The processor 1820 may also control the overall operation of the base station device 1800, in addition to performing the baseband-related signal processing.
[0234] The antenna device 1812 may include at least one physical antenna. If the antenna device 1812 includes a plurality of antennas, multiple input multiple output (MIMO) transmission and reception may be supported. Also, beamforming may be supported.
[0235] The memory 1816 may store operation-processed information of the processor 1820, software, an operating system (OS), and an application related to an operation of the base station device 1800, and the like, and may include a component, such as a buffer.
[0236] The processor 1820 of the base station device 1800 may be configured to implement an operation of a base station in the embodiments set forth herein.
[0237] The terminal device 1850 may include a processor 1870, an antenna device 1862, a transceiver 1864, and a memory 1866. For example, in the present disclosure, the terminal device 1850 may communicate with the base station device 1800. As another example, in the present disclosure, the terminal device 1850 may perform sidelink communication with another terminal device. That is, the terminal device 1850 of the present disclosure refers to any device capable of communicating with at least one of the base station device 1800 and another terminal device and is not limited to communication with a specific device.
[0238] The processor 1870 may perform baseband-related signal processing and may include an upper layer processing unit 1880 and a PHY signal processing unit 1890. The upper layer processing unit 1880 may process an operation of a MAC layer, an RRC layer, or more upper layers. The PHY processing unit 1890 may process an operation (e.g., downlink received signal processing, uplink transmission signal processing, etc.) of a PHY layer. The processor 1870 may control the overall operation of the terminal device 1850 in addition to performing the baseband-related signal processing.
[0239] The antenna device 1862 may include at least one physical antenna. If the antenna device 1862 includes a plurality of antennas, MIMO transmission and reception may be supported. Also, beamforming may be supported.
[0240] The memory 1866 may store operation-processed information of the processor 1870, software, an OS, and an application related to an operation of the terminal device 1850, and the like, and may include a component such as a buffer.
[0241] Here, the processor 1870 of the terminal device 1850 may receive a coordination request (CR) from another terminal device (e.g., Tx UE) through the antenna device 1862. A coordination request may include 1-bit information to indicate a case in which the other terminal device performs the coordination request with respect to the terminal device 1850 or a case in which the other terminal device does not perform the coordination request with respect to the terminal device 1850. The processor 1870 of the terminal device 1850 may verify the coordination request based on at least one of a physical resource set of a PSFCH, an SCI format, CRC scrambling, and a DMRS sequence. For example, the physical resource set of the PSFCH for the coordination request may be separately configured. As another example, some physical resource sets among physical resource sets of the PSFCH for sidelink HARQ feedback may be configured for the coordination request. As another example, a new SCI format may be configured to indicate the coordination request and, through this, the coordination request may be indicated. As another example, the coordination request may be indicated through one of reserved bits within the SCI format. As another example, the coordination request may be indicated through CRC scrambling based on the above Equation 12 and Equation 13. As another example, as described above, the coordination request may be indicated through the DMRS sequence based on the above Equation 14 and Equation 15.
[0242] In operation S1620, the C-UE may generate the coordination message based on the coordination request. Here, the coordination message may include information related to resource configuration of the Tx UE. For example, when the C-UE is an Rx UE, preferred resource information or nonpreferred resource information may be included in the coordination message. As another example, when the C-UE is a third UE, the C-UE may include resource allocation information SCI received from neighboring Tx UEs, which is described above.
[0243] The processor 1870 of the terminal device 1850 may transmit the generated coordination message to another terminal device through the antenna device 1862. Here, the other terminal device may perform resource reselection based on the coordination message.
[0244] As another example, the processor 1870 of the terminal device 1850 may verify a triggering condition. Here, the processor 1870 of the terminal device 1850 may generate the coordination message depending on whether the triggering condition is satisfied, without receiving the coordination request from the other terminal device. The processor 1870 of the terminal device 1850 may set the triggering condition of comparing an RSRP value of SCI received from another neighboring terminal device and a set threshold and, when the triggering condition is satisfied, may generate the coordination message.
[0245] The processor 1870 of the terminal device 1850 may generate the generated coordination message to another terminal device through the antenna device 1862. Here, the other terminal device may perform resource reselection based on the coordination message.
[0246] The terminal device 1850 according to an example of the present disclosure may be associated with a vehicle. For example, the terminal device 1850 may be integrated in the vehicle, may be located in the vehicle, or may be located on the vehicle. Also, the terminal device 1850 according to the present disclosure may be the vehicle itself. Also, the terminal device 1850 according to the present disclosure may be at least one of a wearable terminal, AV/VR, an Internet of things (IoT) terminal, a robot terminal, and a public safety terminal. The terminal device 1850 to which the present disclosure may apply may include various types of communication devices that support an interactive service using sidelink, for services, for example, Internet access, service execution, navigation, real-time information, autonomous driving, and safety-and-risk diagnosis. Also, the terminal device 1850 may include an AR/VR device capable of performing a sidelink operation or any type of communication devices capable of performing a relay operation as a sensor.
[0247] Here, the vehicle to which the present disclosure applies may include an autonomous vehicle, a semi-autonomous vehicle, and a non-autonomous vehicle. Meanwhile, the terminal device 1850 according to an example of the present disclosure is described in association with the vehicle, at least one of the UEs may not be associated with the vehicle. It is provided as an example only and should not be interpreted to limit application of the present disclosure.
[0248] Also, the terminal device 1850 according to an example of the present disclosure may include various types of communication devices capable of performing coordination that supports an interactive service using sidelink. That is, the terminal device 1850 may directly support the interactive service using a sidelink and may be employed as a coordination device for supporting the interactive service using the sidelink.
[0249] Also, various examples of the present disclosure may be implemented by hardware, firmware, software, or combination thereof. In the case of implementation by hardware, the examples may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general processors, controllers, microcontrollers, microprocessors, etc.
[0250] The scope of the present disclosure includes software or machine-executable instructions (e.g., OS, application, firmware, program, etc.) such that operations of the method of the various examples may be executed on an apparatus or a computer, and a non-transitory computer-readable medium storing such software or instructions to be executable on an apparatus or a computer.
[0251] Various embodiments of the present disclosure are to explain representative aspects of the present disclosure rather than listing all the possible combinations and matters described in the various embodiments may be applied alone or in combination of at least two of the embodiments.