WO2020061879A1

WO2020061879A1 - Method and apparatus for receiving and transmitting control information in a communication system supporting nr sidelink communication

Info

Publication number: WO2020061879A1
Application number: PCT/CN2018/107846
Authority: WO
Inventors: Xiaodong Yu; Zhennian SUN; Haipeng Lei; Lianhai WU; Jing HAN
Original assignee: Lenovo (Beijing) Limited
Priority date: 2018-09-27
Filing date: 2018-09-27
Publication date: 2020-04-02

Abstract

A method and apparatus a method and apparatus for receiving and transmitting a control information in a communication system supporting NR sidelink communication is disclosed. The method for receiving a control information comprising: receiving a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information; transmitting a second control information message to the transmitting UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.

Description

METHOD AND APPARATUS FOR RECEIVING AND TRANSMITTING CONTROL INFORMATION IN A COMMUNICATION SYSTEM SUPPORTING NR SIDELINK COMMUNICATION

FIELD

The subject matter disclosed herein relates generally to wireless communications, and more particularly relates to a method and apparatus for receiving and transmitting a control information in a communication system supporting NR sidelink communication.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ( “3GPP” ) , New Radio ( “NR” ) , Long Term Evolution ( “LTE” ) , Vehicle to Vehicle ( “V2V” ) , NR NodeB ( “gNB” ) , Vehicle to Everything ( “V2X” ) , Sidelink Control Information ( “SCI” ) , Uplink (UL) , Downlink (DL) , Radio Resource Control ( “RRC” ) , Cyclic Redundancy Check ( “CRC” ) , User Entity/Equipment (Mobile Terminal) (UE) .

In 3GPP LTE V2V/V2X, one of important service requirements is communication range. That is because maximized communication range can give the driver (s) ample response time (e.g. 4 seconds) . So V2X broadcast communication design should ensure that the communication range is large enough so that the broadcast signal can be detected by a large number of UEs. In 3GPP NR V2X, the required communication range is varies from 50 meters to 1000 meters, and the reliability requirement of advanced service is more stringent. Both 3GPP Rel-12/Rel-13 D2D communication and 3GPP Rel-14 V2V communication are typical broadcast-based communications, wherein one of the main objectives is to enable as many receivers as possible to successfully decode the messages. Mechanisms such as blind (re) transmission without feedback are no longer suitable for unicast communication. Enhancements to sidelink communication should be studied to support physical layer HARQ feedback procedure to meet the requirements for resource utilization efficiency, throughput, QoS, reliability, complexity and power consumption. In NR sidelink unicast communication, SCI plays an important role in resource allocation and data transmission. To meet the requirements of NR V2X, further study of transmission and reception of SCI for NR sidelink unicast communication is needed.

References

[1] R1-1808519, LG

[2] R1-1808696, Intel

BRIEF SUMMARY

A method and apparatus for receiving and transmitting control information in a communication system supporting NR sidelink communication is disclosed.

A method for receiving, at a receiving user equipment, control information from a transmitting user equipment in a communication system supporting sidelink communication, the method comprising: receiving a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information; transmitting a second control information message to the transmitting UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.

In one embodiment, the second control information is scrambled by the identification information.

In one embodiment, the second control information includes the indicator of identification information.

In one embodiment, the identification information comprises one of the following: a session ID or link ID; a source ID and a destination ID; or a destination ID and a temporary ID, wherein the session ID or link ID, the source ID and the destination ID are indicated by higher layer of the transmitting user equipment or by base station, the temporary ID is selected by physical layer of transmitting user equipment or indicated by higher layer of the transmitting user equipment or base station.

In one embodiment, the second control information message is carried on a first control channel or on a dedicated feedback channel, wherein the first control channel or the dedicated feedback channel is transmitted on a feedback resource, the feedback resource is indicated in the first control information message can be indicated according to any one of following: indicating a time offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ; indicating a time offset and frequency offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ; indicating a feedback resource set; or indicating a feedback resource time window. Further, it includes selecting a feedback resource from the feedback resource set or the feedback resource time window.

In one embodiment, the second control information message is generated based on a decoding result of data and includes one or more of following indicators: an indicator of Hybrid Automatic Repeat Request (HARQ) feedback; an indicator of Hybrid Automatic Repeat Request (HARQ) process number; an indicator of resource collision, wherein an indicator of Hybrid Automatic Repeat Request (HARQ) feedback comprising: an ‘ACK’ if successfully decode the data; a ‘NACK’ if unsuccessfully decode the data. The collision indicator indicates resource collision of associated data in data channel.

A method for transmitting, at a transmitting user equipment, a control information to a receiving user equipment in a communication system supporting sidelink communication, the method comprising: transmitting a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information; receiving a second control information message from the receiving UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.

In one embodiment, if the indicator of resource collision received by the transmitting UE is activated, the transmitting UE performs a resource reselection, or drops subsequent transmission or re-transmission.

A receiving user equipment for receiving a control information from a transmitting user equipment in a communication system supporting sidelink communication, the receiving user equipment comprising: a transceiver; a controller configured to control the transceiver to: receiving a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information; transmitting a second control information message to the transmitting UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.

A transmitting user equipment for transmitting a control information to a receiving user equipment in a communication system supporting sidelink communication, the transmitting user equipment comprising: a transceiver; a controller configured to control the transceiver to: transmitting a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information; receiving a second control information message from the receiving UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 is a schematic diagram illustrating one embodiment of aNR-V2X communication system;

Figure 2 is a schematic diagram illustrating two resource allocation modes in NR sidelink communication;

Figure 3 is a schematic diagram illustrating a collision case when a Destination ID is used in SCI;

Figure 4 is a schematic diagram illustrating a collision case when a Destination ID is used in SCI;

Figure 5 is a method for receiving a control information in NR sidelink communication.

Figure 6 is a method for transmitting a control information in NR sidelink communication.

Figure 7 is a schematic diagram illustrating one example of Session ID for feedback;

Figure 8 is a schematic diagram illustrating one example of exact feedback resource indicated by SCI;

Figure 9 is a schematic diagram illustrating one example of HARQ feedback resource set indicated by SCI.

Figure 10 is a schematic block diagram illustrating the receiving user equipment and transmitting user equipment for transmitting and receiving control information in a communication system supporting sidelink communication.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit, ” “module” or “system. ” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration ( “VLSI” ) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ( “RAM” ) , a read-only memory ( “ROM” ) , an erasable programmable read-only memory ( “EPROM” or Flash memory) , a portable compact disc read-only memory ( “CD-ROM” ) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and machine languages such as assembly languages. The code may execute entirely on the user′s computer, partly on the user′s computer, as a stand-alone software package, partly on the user′s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user′s computer through any type of network, including a local area network ( “LAN” ) or a wide area network ( “WAN” ) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment, ” “an embodiment, ” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment, ” “in an embodiment, ” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including, ” “comprising, ” “having, ” and variations thereof mean “including but not limited to, ” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all ofthe items are mutually exclusive, unless expressly specified otherwise. The terms “a, ” “an, ” and “the” also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

Aspects of the embodiments are described below with reference to schematic flowchart diagrams and schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and block diagram block or blocks.

The schematic flowchart diagrams and schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and flowchart diagrams, and combinations of blocks in the block diagrams and flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

Figure 1 depicts an embodiment of NR-V2X communication system 100. In one embodiment, the wireless communication system 100 may includes gNB 104 and Vehicles 102. Even though a specific number of gNB 104 and Vehicle 102 are depicted in Figure 1, one skilled in the art will recognize that any number of gNB 104 and Vehicle 102 may be included in the NR V2X communication system 100. In Figure 1, solid lines denote downlink communication channels from gNB 104 to Vehicle 102 and dotted line denote sidelink communication channels between the two vehicles. Here, for illustration purposes, direction of each arrow indicates the direction of data transmission, without limiting discussed embodiments. Here, Vehicles can also be User Entity/Equipments (Mobile Terminals) (UEs) .

Figure 2 is a schematic diagram illustrating two resource allocation modes of NR-V2X sidelink communication. For NR V2X discussion, two resource allocation modes are being considered, e.g. Mode 1: gNB schedules sidelink resource (s) to be used by Vehicle for sidelink transmission (s) ; and Mode 2: Vehicle determines (i.e. gNB does not schedule) sidelink transmission resource (s) within sidelink resources configured by gNB/network or pre-configured sidelink resources

To introduce unicast sidelink communication for NR V2X, the feedback transmission and resource allocation should be considered.

In Figure 2, Circle 201 denotes the coverage area supported by gNB, and the meanings of lines and arrows are the same as that of Figure 1.

Figure 2 (a) describes resource allocation Mode 1 of NR-V2X sidelink communication. In this mode, gNB schedules sidelink resource (s) to be used by vehicles for sidelink communication. For example, in one case, feedback resources used by Vehicle B can be directly indicated by a DCI grant transmitted from gNB and be valid, only when Vehicle B is within a coverage area of gNB. This scheme has a shortcoming since it only works when Vehicle A and Vehicle B are both within coverage area of gNB. In another case, the feedback resource (set) to be used by Vehicle B can be indicated by gNB via Vehicle A, so at least, Vehicle A should be in coverage of gNB. In this scheme, the exact feedback resource to be used by Vehicle B can be determined by any one of Vehicles A and B, wherein Vehicle A selects a feedback resource for Vehicle B, or Vehicle B selects a feedback resource from an indicated feedback resource set.

Figure 2 (b) describes resource allocation Mode 2 of NR-V2X sidelink communication. In Mode 2, Vehicles A or B can select sidelink transmission resource (s) from a set of sidelink resources configured by gNB or a network or a set of pre-configured sidelink resources. For example, in one case, the exact feedback resource for Vehicle B can be determined by Vehicle A. In another case, the exact feedback resource of Vehicle B can be determined by Vehicle B from Vehicle A indicated feedback resource set.

In NR-V2X sidelink communication, it is currently known that Destination, Source and Session ID may be supported for sidelink unicast communication.

Figure 3 is a schematic diagram illustrating a collision case when a Destination ID is used.

Similar to Figures 1 and 2, directions of the identified arrows denote direction of data transmission.

In a communication diagram depicted on the left portion of Figure 3, Vehicle A uses Destination ID=B in Sidelink Control Information (SCI) transmitted to Vehicle B, with Vehicle B performing blind detection of received data. In addition, Vehicle A uses Destination ID=C in SCI transmitted to Vehicle C, with Vehicle C performing blind detection of received data. This configuration allows for no transmission or reception misunderstanding among all Vehicles. Similarly, as part of feedback communication, Vehicle B also uses ID=B in SCI transmitted to Vehicle A and Vehicle C uses ID=C for feedback transmission to Vehicle A. Using a similar ID assignment approach, communication diagram depicted on the right side of Figure 3 shows Vehicle A and C transmit data to Vehicle B. Except for receiving HARQ feedback in the overlap resource set or time window, if Destination ID used for transmission and feedback is set to B, e.g. ID = B, by both Vehicles A and C, Vehicle B cannot identify a Vehicle from which the data transmission originated from. Similarly, neither Vehicle A or C can distinguish the intended destination of feedback information transmitted by Vehicle Bo

Figure 4 is a schematic diagram illustrating a collision example when a Source ID is used.

Communication diagram illustrated on the right side of Figure 4 identifies Vehicle A using Source ID set to A, i.e. ID=A, in SCI transmitted to Vehicle B. Similarly, Vehicle C uses Source ID=C in SCI transmitted to Vehicle B. Following this approach, there is no transmission or reception misunderstanding among each Vehicle. For the feedback, Vehicle B continues to use ID set to A, i.e. ID=A, for feedback transmissions to Vehicle A and Vehicle B uses ID set to C, i.e. ID=C, for feedback transmissions to Vehicle C. Similarly, there is obviously no collision. As shown on the left side in Figure 4, Vehicle A transmits data to Vehicle B and C, and except for receiving HARQ feedback in the overlap resource set or time window, if ID=A is used for transmission and feedback, Vehicle A cannot distinguish where the feedback information originates from.

To solve the above identified problems, a method for receiving and transmitting control information in NR sidelink communication is proposed.

Figure 5 is a schematic diagram illustrating a method for receiving control information in NR sidelink communication. The method includes steps 501-502 described below.

Step 501 describes receiving a first control information message in a first control channel and the associated data in data channel. The first control information message includes an indicator of identification information, and the identification information comprises one of the following: a session ID or link ID; a source ID and a destination ID; or a destination ID and a temporary ID;

Step 502 describes transmitting a second control information message to the transmitting UE in response to received first control information message and the associated data. The second control information message is associated with the identification information recieved.

Figure 6 is a schematic diagram illustrating a method for transmitting control information in NR sidelink communication.

Step 601 describes transmitting a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information, and the identification information comprises one of the following: a session ID or link ID; a source ID and a destination ID; or a destination ID and a temporary ID;

Step 602 describes receiving a second control information message by the transmitting UE in response to the first control information message and the associated data being transmitted. The second control information message is associated with the identification information.

For both methods described above in connection with schematic diagrams of Figures 5 and 6 associated with the sidelink unicast communication, an originating Vehicle (i.e. transmitting user equipment -Tx UE) transmits SCI information over the Physical Sidelink Control Channel (PSCCH) , and transmits data information over the Physical Sidelink Shared Channel (PSSCH) . The SCI includes an indication part to indicate the time and frequency resource location of data information.

The SCI also includes an indication part to indicate the time and frequency resource location for feedback information transmission. It can indicate an exact feedback resource, or it can indicate a resource set or a feedback time window.

SCI also indicates a session ID, or source ID and destination ID, or destination ID and temporary ID indicator, wherein the session ID, the source ID and the destination ID are indicated by the higher layer of the transmitting user equipment (e.g., layer-2) or by base station (e.g., gNB) . The temporary ID is selected by the physical layer of the transmitting user equipment or indicated by the higher layer of the transmitting user equipment (e.g., layer-2) or base station (e.g., gNB) .

Receiving Vehicle (i.e. receiving user equipment) receives transmitted SCI information and its associated data transmission and decodes the indicated data, if the decoded ID belong to the receiving user equipment (Rx UE) . If the decoding operation is performed successfully, Rx UE generates an ACK; else if decoding operation is not successful, Rx UE generates a NACK.

Rx UE transmits an ACK or a NACK information on an indicated feedback resource. If the indicated feedback resource is a resource set or a time window, Rx UE will select a feedback resource based on the available time slot or frequency resource.

Tx UE receives the feedback information for retransmission consideration. For this case, the collision indicator is also included in the SCI information received. It triggers either resource re-selection or drops resource re-transmission.

To achieve the objectives mentioned above, it can be considered to introduce two SCI formats.

SCI format A:

SCI format A is used for the scheduling of PSSCH and includes the following information:

-time and frequency resource location of data information;

-time and frequency resource location of feedback information;

-session ID or source ID and destination ID or destination ID and temporary ID indicator

The time and frequency resource location of feedback information can be indicated in a number of ways, specifically by:

-indicating an exact time and frequency resource location,

-indicating time offset from the received SCI transmission with the frequency resource being the same as the one used to receive SCI/data transmission;

-indicate time offset from the received data transmission where the frequency resource is the same as the resource used to receive SCI/data transmission.

-indicate a resource set or time window (this resource set and time window may start from a fixed offset, that is dependent on UE process timing, e.g. 4ms) .

-in a bitmap manner, to indicate available feedback time resource (subframe) ;

-to indicate a window size;

-a fixed window size and a time offset.

SCI format B

SCI format B is used for the scheduling of PSSCH.

The following information is transmitted by means of the SCI format B:

-3 bits HARQ process number;

-1-bit ACK/NACK indicator;

-session ID or source ID and destination ID or destination ID and temporary ID indicator. If the session ID or source ID and destination ID or destination ID and temporary ID indicators are used to scramble on attached CRC to SCI, this field is not needed;

-1-bit collision indicator.

Figure 7 is a schematic diagram illustrating one example of Session ID used for feedback transmission.

In Figure 7, the Session ID is link-specific between Vehicle A and B or between Vehicle A and C. The Session ID can be obtained during connection establishment step by Vehicles coordination or information exchange, or indicated or configured by gNB. The Session ID is carried in SCI for data and associated feedback transmission. Here, the Session ID between Vehicle A and B is 0, and the session ID between Vehicle A and C is 1. By this scheme, the problem that Vehicle A cannot distinguish the destination of feedback information is resolved.

In another embodiment, feedback ID is generated by the received Destination ID and Source ID. Destination ID and Source ID can be indicated by a higher layer of Vehicles or by gNB. The feedback ID includes two parts: the source ID and destination ID. For example, the size of Destination ID is 8 bits in received SCI, e.g., 10101010, and the size of source ID is 8bits in received SCI, e.g., 00000100. All of these 16 bits should be carried in data transmission associated SCI. The Destination ID and source ID are carried in SCI for data transmission and associated feedback.

In another embodiment, feedback ID is determined by Destination ID and temporary ID (temp ID) .

Table 1 shows an example of a feedback ID that determined by Destination ID and temp ID.

Indicator	Temp ID	Feedback ID
000	00000001	10101010 00000001
001	00000010	10101010 00000010
010	00000100	10101010 00000100
011	00001000	10101010 00001000
100	00010000	10101010 00010000
101	00100000	10101010 00100000
110	01000000	10101010 01000000
111	10000000	10101010 10000000

As shown in the table 1, the first 8 bits of the feedback ID field is the destination ID and the remaining 8 bits of the feedback ID field is temp ID. The indicator is used to indicate temp ID. The first 8 bits are dependent on the real Destination ID. The indicator can be indicated or configured by gNB or randomly selected by the transmitter. For example, Vehicle A and C want to transmit data to Vehicle B (Destination ID =10101010) , Vehicle A may select index 2 (indicator: 001) and Vehicle C may select index 6 (indicator 101) . Thus, Vehicle B can distinguish transmissions via the identified feedback IDs.

If the HARQ process number is contained within feedback SCI, HARQ and a source indicator can be combined to distinguish transmission source (i.e., feedback destination) . For example, Vehicle B and C want to feedback SCI to Vehicle A, Vehicle B and C may select two different source indicators. Thus, Vehicle A can distinguish feedbacks via the identified feedback IDs.

This mapping can be configured at the time of connection establishment procedure, similar to session ID. In that way, the session ID is shortened in transmitted SCI.

In another embodiment, the feedback ID is transmitted with ACK/NACK feedback. In detail, for feedback SCI, the attached CRC is scrambled by the feedback ID to distinguish feedback from different UEs/groups. The feedback ID is mentioned in above solutions.

Here, the feedback SCI format may be defined as SCI format B, feedback ID may be defined as session ID or source ID and destination ID or destination ID and temporary ID indicator

The feedback SCI (SCI format) content includes: HARQ ACK/NACK indicator, HARQ process number, collision indicator

Collision indicator is used to indicate resource selection collision from the receiver perspective. For example, if the decoded SCIs indicate a full or partial overlapping of resources, the collision indicator will be set to, for example a value of ‘1’ , to indicate the resource selection collision. If a transmission Vehicle receives a collision indicator, it may trigger a resource re-selection.

The collision indicator can indicate the collision for re-transmission resource, if the initial transmission resource and retransmission resource is indicated in SCI. If transmission Vehicle receives a collision indicator, it may drop the re-transmission.

Figure 8 is a schematic diagram illustrating one example of exact feedback resource indicated by SCI.

In Figure 8, only one exact feedback resource is indicated by transmission UE, from Vehicle B’s perspective. The single unit identified in Figure 8 is slot, and the directions of arrows denote the directions of SCI and data transmission. First, Vehicle A sends SCI and data to Vehicle B in slot n, and then Vehicle B receives and decodes the received SCI and data. If decoding fails, Vehicle B sends NACK to Vehicle A in the slot indicated by the received SCI, e.g. slot n+4. Vehicle A performs retransmission in slot 5 after receiving the NACK, and then Vehicle B receives and decodes the data again. If decoding succeeds, Vehicle B sends ACK to Vehicle A in the slot indicated by the received SCI (e.g., slot n+9) to end this process. The procedure between Vehicle A and Vehicle C is similar to the above described procedure. If decoding the data successfully in slot n, Vehicle B sends ACK in slot indicated by the SCI received from Vehicle C, e.g., slot n+4.

Figure 9 is a schematic diagram illustrating one example of HARQ feedback resource set indicated by SCI. Similar to Figure 8, the smallest unit in Figure 9 is slot, and the directions of arrows denote the directions of SCI and data transmission. Vehicle A sends SCI and data to Vehicle B and Vehicle C in slot n and slot n+1, respectively. Here, SCI indicates HARQ feedback resource set (or time window) . Feedback slot (s) can be indicated in a bitmap manner, e.g., a 10ms pattern, or the time window of feedback slot (s) can be a fixed size. The time offset can be indicated in SCI, or time offset can be fixed, and the size of time window can be indicated in SCI (e.g., as shown in Figure 9, 4 slots) . Here, time offset is the number of slots between SCI/data transmission and feedback transmission (e.g., as shown in Figure 9, 3 slots) . Feedback UE selects feedback resource based on an indicated set (or in time window) , e.g., as shown in Figure 9, Vehicle B and Vehicle C select slot n+6 and slot n+7 as feedback resources, respectively.

Figure 10 is a schematic block diagram illustrating the receiving user equipment and transmitting user equipment for transmitting and receiving a control information in a communication system supporting sidelink communication.

Referring to Figure 10, The user equipment includes a controller, a memory, and a transceiver. The controller implements a function, a process, and a method which are proposed in Figures 5 to 9above. Layers of a radio interface protocol may be implemented by the controller. The memory is connected with the controller to store various pieces of information for driving the controller. The transceiver is connected with the controller to transmit and receive a radio signal.

The memories may be positioned inside or outside the controllers and connected with the controllers by various well-known means. Further, the relay node may have a single antenna or multiple antennas.

In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.

The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using 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) , processors, controllers, micro-controllers, microprocessors, and the like.

In the case of implementation by firmware or software, the embodiment may be implemented in the form of a module, a procedure, a function, and the like to perform the functions or operations described above. A software code may be stored in the memory and executed by the controller. The memory may be positioned inside or outside the controller and may transmit and receive data to/from the controller by various means.

Claims

A method for receiving, at a receiving user equipment, a control information from a transmitting user equipment in a communication system supporting sidelink communication, said method comprising:

receiving a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information;

transmitting a second control information message to the transmitting UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.
The method of claim 1, wherein the second control information is scrambled by the identification information.
The method of claim 1, wherein the second control information includes the indicator of identification information.
The method of any one of claim 1-3, wherein the identification information comprising one of the following:

a session ID or link ID;

a source ID and a destination ID; or

a destination ID and a temporary ID.
The method of claim 4, wherein the session ID, the source ID and the destination ID are indicated by higher layer of the transmitting user equipment or by base station.
The method of claim 4, wherein the temporary ID is selected by physical layer of transmitting user equipment or indicated by higher layer of the transmitting user equipment or base station.
The method of claim 1, wherein the second control information message is carried on a first control channel or on a dedicated feedback channel.
The method of claim 7, wherein the first control channel or the dedicated feedback channel is transmitted on a feedback resource, the feedback resource is indicated in the first control information message.
The method of claim 8, wherein the feedback resource indicated in the first control information message can be indicated according to any one of following:

Indicating a time offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a time offset and frequency offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a feedback resource set; or

Indicating a feedback resource time window.
The method of claim 9, further comprising:

selecting a feedback resource from the feedback resource set or the feedback resource time window.
The method of claim 1, wherein the second control information message is generated based on a decoding result of data and includes one or more of following indicators:

an indicator of Hybrid Automatic Repeat Request (HARQ) feedback;

an indicator of Hybrid Automatic Repeat Request (HARQ) process number; and

an indicator of resource collision.
The method of claim 11, wherein an indicator of Hybrid Automatic Repeat Request (HARQ) feedback comprising;

an ACK’if successfully decode the data,

a ‘NACK’ if unsuccessfully decode the data.
The method of claim 11, wherein said collision indicator indicates resource collision of associated data in data channel.
A method for transmitting, at a transmitting user equipment, a control information to a receiving user equipment in a communication system supporting sidelink communication, the method comprising:

Transmitting a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information;

Receiving a second control information message from the receiving UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.
The method of claim 14, wherein the second control information is scrambled by the identification information.
The method of claim 14, wherein the second control information includes the indicator of identification information.
The method of any one of claim 14-16, wherein the identification information comprising one of the following:

a session ID or link ID;

a source ID and a destination ID; or

a destination ID and a temporary ID.
The method of claim 17, wherein the session ID, the source ID and the destination ID are indicated by higher layer of the transmitting user equipment or by base station.
The method of claim 17, wherein the temporary ID is selected by physical layer of transmitting user equipment or indicated by higher layer of the transmitting user equipment or base station.
The method of claim 14, wherein the second control information message is carried on a first control channel or on a dedicated feedback channel.
The method of claim 20, wherein the first control channel or the dedicated feedback channel is transmitted on a feedback resource, the feedback resource is indicated in the first control information message.
The method of claim 21, wherein the feedback resource indicated in the first control information message can be indicated according to any one of following:

Indicating a time offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a time offset and frequency offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a feedback resource set; or

Indicating a feedback resource time window.
The method of claim 22, further comprising:

selecting a feedback resource from the feedback resource set or the feedback resource time window.
The method of claim 14, wherein the second control information message is generated based on a decoding result of data and includes one or more of following indicators:

an indicator of Hybrid Automatic Repeat Request (HARQ) feedback;

an indicator of Hybrid Automatic Repeat Request (HARQ) process number; and

an indicator of resource collision.
The method of claim 24, wherein the collision indicator indicates resource selection collision of associated data in data channel.
The method of claim 25,

wherein if the indicator of resource collision received by the transmitting UE is activated, the transmitting UE performs a resource reselection, or drops subsequent transmission or re-transmission.
A receiving user equipment for receiving a control information from a transmitting user equipment in a communication system supporting sidelink communication, the receiving user equipment comprising:

a transceiver;

a controller configured to control the transceiver to:

receiving a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information;

transmitting a second control information message to the transmitting UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.
The receiving user equipment of claim 27, wherein the second control information is scrambled by the identification information.
The receiving user equipment of claim 27, wherein the second control information includes the indicator of identification information.
The receiving user equipment of any one of claim 27-29, wherein the identification information comprising one of the following:

a session ID or link ID;

a source ID and a destination ID; or

a destination ID and a temporary ID.
The receiving user equipment of claim 30, wherein the session ID, the source ID and the destination ID are indicated by higher layer of the transmitting user equipment or by base station.
The receiving user equipment of claim 30, wherein the temporary ID is selected by physical layer of transmitting user equipment or indicated by higher layer of the transmitting user equipment or base station.
The receiving user equipment of Claim 27, wherein the second control information message is carried on a first control channel or on a dedicated feedback channel.
The receiving user equipment of claim 33, wherein the first control channel or the dedicated feedback channel is transmitted on a feedback resource, the feedback resource is indicated in the first control information message.
The receiving user equipment of claim 34, wherein the feedback resource indicated in the first control information message can be indicated according to any one of following:

Indicating a time offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a time offset and frequency offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a feedback resource set; or

Indicating a feedback resource time window.
The receiving user equipment of claim 35, further comprising:

selecting a feedback resource from the feedback resource set or the feedback resource time window.
The receiving user equipment of claim 27, wherein the second control information message is generated based on a decoding result of data and includes one or more of following indicators:

an indicator of Hybrid Automatic Repeat Request (HARQ) feedback;

an indicator of Hybrid Automatic Repeat Request (HARQ) process number; and

an indicator of resource collision.
The receiving user equipment of claim 37, wherein an indicator of Hybrid Automatic Repeat Request (HARQ) feedback comprising;

an ACK’if successfully decode the data,

a ‘NACK’ if unsuccessfully decode the data.
The receiving user equipment of claim 37, wherein the collision indicator indicates resource collision of associated data in data channel.
A transmitting user equipment for transmitting a control information to a receiving user equipment in a communication system supporting sidelink communication, the transmitting user equipment comprising:

a transceiver;

a controller configured to control the transceiver to:

transmitting a first control information message in a first control channel and the associated data in data channel, the first control information message including an indicator of identification information;

receiving a second control information message from the receiving UE in response to the first control information message and the associated data, wherein the second control information message is associated with the identification information.
The transmitting user equipment of claim 40, wherein the second control information is scrambled by the identification information.
The transmitting user equipment of claim 40, wherein the second control information includes the indicator of identification information.
The transmitting user equipment of any one of claim 40-42, wherein the identification information comprising one of the following:

a session ID or link ID;

a source ID and a destination ID; or

a destination ID and a temporary ID.
The transmitting user equipment of claim 43, wherein the session ID, the source ID and the destination ID are indicated by higher layer of the transmitting user equipment or by base station.
The transmitting user equipment of claim 43, wherein the temporary ID is selected by physical layer of transmitting user equipment or indicated by higher layer of the transmitting user equipment or base station.
The transmitting user equipment of claim 40, wherein the second control information message is carried on a first control channel or on a dedicated feedback channel.
The transmitting user equipment of claim 46, wherein the first control channel or the dedicated feedback channel is transmitted on a feedback resource, the feedback resource is indicated in the first control information message.
The transmitting user equipment of claim 47, wherein the feedback resource indicated in the first control information message can be indicated according to any one of following:

Indicating a time offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a time offset and frequency offset between the first control message and the feedback resource (s) , or between the associated data and the feedback resource (s) ;

Indicating a feedback resource set; or

Indicating a feedback resource time window.
The transmitting user equipment of claim 48, further comprising:

selecting a feedback resource from the feedback resource set or the feedback resource time window.
The transmitting user equipment of claim 40, wherein the second control information message is generated based on a decoding result of data and includes one or more of following indicators:

an indicator of Hybrid Automatic Repeat Request (HARQ) feedback;

an indicator of Hybrid Automatic Repeat Request (HARQ) process number; and an indicator of resource collision.
The transmitting user equipment of claim 50, wherein the collision indicator indicates resource selection collision of associated data in data channel.
The transmitting user equipment of claim 51,

wherein if the indicator of resource collision received by the transmitting UE is activated, the transmitting UE performs a resource reselection, or drops subsequent transmission or re-transmission.