WO2024169586A1 - Communication method and apparatus - Google Patents

Abstract

Provided in the present application are a communication method and apparatus. On the basis of first information from a second terminal device, a first terminal device can determine that a COT of the second terminal device can be shared, thereby accurately and uniquely indicating a first terminal device which is capable of using the COT, and also reducing a conflict collision problem caused when a plurality of terminal devices use the COT. Further, the first terminal device can send sidelink data to at least one terminal device within the COT, which indicates that a resource corresponding to the COT is successfully shared.

Description

A communication method and device

This application claims priority to the Chinese patent application with application number 202310172240.9 filed with the State Intellectual Property Office of China on February 17, 2023, and priority to the Chinese patent application with invention name “A communication method and device”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a communication method and device.

Background Art

In the sidelink (SL) unlicensed spectrum communication scenario, a terminal device can access a channel and determine the channel occupancy time (COT) through the listen before talk (LBT) process. Generally speaking, a terminal device can share the resources corresponding to the COT with other terminal devices, but there is currently no solution for other terminal devices to determine that the resources corresponding to the COT can be used.

Summary of the invention

The present application provides a communication method and apparatus, which enable a terminal device to determine whether it can share the COT of another terminal device.

In a first aspect, a communication method is provided, comprising: a first terminal device receives first information from a second terminal device, the first information is used by the first terminal device to determine a COT for sharing the second terminal device; the first terminal device sends side link data to at least one terminal device within the COT, the at least one terminal device including the second terminal device.

In the above implementation, the first terminal device can determine the COT that can share the second terminal device based on the first information from the second terminal device, which accurately and uniquely indicates the first terminal device that can use the COT, and also reduces the conflict and collision problem caused by multiple terminal devices using the COT. Further, the first terminal device can send sidelink data to at least one terminal device within the COT, which indicates that the resources corresponding to the COT are successfully shared.

In combination with the first aspect, in a possible implementation, the first information includes identification information, the identification information includes a first identification and a second identification, and the method further includes: the first terminal device determines the shared COT based on at least one of the first identification and the second identification.

In the above implementation, the first terminal device that can use the COT is accurately and uniquely indicated, and the conflict and collision problem caused by multiple terminal devices using the COT is reduced.

In one possible implementation, the first identifier is used to indicate the first terminal device that shares the COT, and the second identifier is used to indicate the second terminal device. If the transmission type indication information indicates unicast, the first identifier is used to indicate the first terminal device that shares the COT, and the second identifier is used to indicate the second terminal device. In one possible implementation, the first identifier is a source identifier, and the second identifier is a destination identifier; or, the first identifier is a source identifier of the first terminal device, and the second identifier is a destination identifier of the first terminal device; or, the first identifier is a destination identifier of the second terminal device, and the second identifier is a source identifier of the second terminal device. In another possible implementation, the first identifier is an identifier of the first terminal device or at least one bit of the identifier of the first terminal device, and the second identifier is an identifier of the second terminal device or at least one bit of the identifier of the second terminal device. In another possible implementation, the first identifier is a first shared identifier or at least one bit of the first shared identifier, and the second identifier is a second shared identifier or at least one bit of the second shared identifier.

In another possible implementation, the first identifier is used to indicate the second terminal device, and the second identifier is used to indicate the first terminal device that shares the COT. If the transmission type indication information indicates unicast, the first identifier is used to indicate the second terminal device, and the second identifier is used to indicate the first terminal device that shares the COT. In one possible implementation, the first identifier is the source identifier of the second terminal device, and the second identifier is the destination identifier of the second terminal device. Or, the first identifier is the destination identifier of the first terminal device, and the second identifier is the source identifier of the first terminal device. In another possible implementation, the first identifier is the identifier of the second terminal device or at least one bit of the identifier of the second terminal device, and the second identifier is the identifier of the first terminal device or at least one bit of the identifier of the first terminal device. In another possible implementation, the first identifier is the second shared identifier or at least one bit of the second shared identifier, and the second identifier is the first shared identifier or at least one bit of the first shared identifier.

In another possible implementation, the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group. The number of terminal devices included in the terminal device group may be one or more. If the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate the first terminal device sharing the COT, and the second identifier is used to indicate the second terminal device. The number of terminal devices included in the terminal device group may be one or more. In a possible implementation, the first identifier is a source identifier and the second identifier is a destination identifier; or, the first identifier is a source identifier of the first terminal device and the second identifier is a destination identifier; or, the first identifier is a destination identifier of the second terminal device. The first identifier is the destination identifier, and the second identifier is the destination identifier; or, the first identifier is the destination identifier 1, the second identifier is the destination identifier 2, the destination identifier 1 is the source identifier of the first terminal device or the destination identifier of the second terminal device, and the destination identifier 2 is the destination identifier corresponding to the multicast data. It can also be understood that: the destination identifier 2 indicates the multicast service or indicates the terminal device group. In another possible implementation, the first identifier is the group member identifier corresponding to the first terminal device, at least one bit of the group member identifier, or the quantized value of the group member identifier, and the second identifier is the destination identifier. In another possible implementation, the first identifier is the first shared identifier or at least one bit of the first shared identifier, and the second identifier is the second shared identifier or at least one bit of the second shared identifier. Among them, the target identifier described by the second identifier can be understood as: the destination identifier corresponding to the data to be sent by the first terminal device, or, the destination identifier corresponding to the data to be received by the second terminal device, or, the destination identifier corresponding to the multicast service type, or, the destination identifier associated with the multicast service, or, the destination identifier associated with the multicast data, or, an identifier used to indicate that a group of terminal devices share the COT. The first identifier can be called a source identifier or a destination identifier, but is not limited to these two names. It can also be called a terminal identifier, a terminal identifier dedicated to indicating the first terminal device, or an identifier dedicated to indicating the first terminal device, or an identifier used to indicate that the first terminal device in the terminal device group shares the COT, or an identifier used to indicate the first terminal device in the terminal device group.

Among them, the first shared identifier and the second shared identifier involved in this application can be understood as a pair of identifiers used by the first terminal device to determine the COT of the shared second terminal device, and their names are not limited in this application.

In combination with the first aspect, in a possible implementation, the first terminal device determines the shared COT based on at least one of the first identifier and the second identifier, including: when the first condition is met, the first terminal device determines the shared COT; wherein the first condition includes at least one of the following: the first identifier matches the third identifier; the second identifier matches the fourth identifier. For example, the third identifier is determined based on the source identifier of the first terminal device, the identifier of the first terminal device, the group member identifier corresponding to the first terminal device, or the first shared identifier, and the fourth identifier is determined based on the destination identifier of the first terminal device, the identifier of the second terminal device, or the second shared identifier. Optionally, the first identifier is based on the third identifier from the first terminal device, and the second identifier is based on the fourth identifier from the first terminal device. For example, when the propagation type indication information indicates unicast, multicast, or broadcast, the first identifier is based on the third identifier from the first terminal device, and the second identifier is based on the fourth identifier from the first terminal device.

In the above implementation, when the first condition is met, the first terminal device determines the shared COT, which achieves accurate and unique indication of the first terminal device that can use the COT, and also reduces the conflict and collision problems caused by multiple terminal devices using the COT. Generally speaking, in the existing sidelink multicast transmission, an identifier is used to determine whether to receive the multicast transmission (or to determine the reception of the multicast transmission). However, this identifier cannot indicate a terminal device, but can only indicate a terminal device group. Therefore, an additional identifier is added on the basis of the identifier to indicate a terminal device in the group of terminal devices. At this time, the terminal device that shares the COT can be uniquely determined, avoiding the problem that the terminal device that can share the COT is unclear and multiple terminal devices use overlapping resources to cause conflicts.

It should be noted that the matching of an identifier with another identifier involved in the present application can be understood as: all bits in one identifier are part or all bits of another identifier, or all bits in one identifier are equal to part or all bits of another identifier. For example, the first identifier is equal to the third identifier, or all bits of the first identifier are equal to the high Y1 bit or the low Y2 bit of the third identifier, and Y1 and Y2 can be the same or different. Y1 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the third identifier. Y2 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the third identifier. Optionally, Y1 and Y2 can be 8, such as the first identifier is 00001111, and the 8-bit MSB or 8-bit LSB of the third identifier is also 00001111. For another example, the second identifier is equal to the fourth identifier, or all bits of the second identifier are equal to the high Y3 bit or the low Y4 bit of the fourth identifier, and Y3 and Y4 can be the same or different. Y3 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the fourth identifier. Y4 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the fourth identifier. Vice versa, that is, part or all of the bits of one identifier are all of the bits in another identifier, or part or all of the bits of one identifier are equal to all of the bits in another identifier. No further details are given here.

The following describes the matching of the first identifier with the third identifier and the matching of the second identifier with the fourth identifier in conjunction with specific examples.

Exemplarily, when the first identifier is used to indicate the first terminal device that shares the COT, and the second identifier is used to indicate the second terminal device, the first identifier is the source identifier and the second identifier is the destination identifier; or, the first identifier is the source identifier of the first terminal device and the second identifier is the destination identifier of the first terminal device; or, the first identifier is the destination identifier of the second terminal device and the second identifier is the source identifier of the second terminal device. The first terminal device obtains the first identifier and the second identifier, and the first terminal device can match the first identifier and the second identifier with its own source layer 2 identifier (i.e., the third identifier) and destination layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT of the second terminal device can be shared.

As another example, when the first identifier is used to indicate the second terminal device and the second identifier is used to indicate the first terminal device that shares the COT, the first identifier is the source identifier of the second terminal device and the second identifier is the destination identifier of the second terminal device. The first terminal device obtains the first identifier and the second identifier, and the first terminal device can match the first identifier and the second identifier with its own destination layer 2 identifier (i.e., the third identifier) and source layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT of the second terminal device can be shared.

In another exemplary embodiment, when the first identifier is used to indicate the first terminal device in the terminal device group and the second identifier is used to indicate the terminal device group, the first identifier is the source identifier and the second identifier is the destination identifier; or the first identifier is the source identifier of the first terminal device and the second identifier is Destination identifier; or, the first identifier is the destination identifier of the second terminal device, and the second identifier is the destination identifier; or, the first identifier is destination identifier 1, and the second identifier is destination identifier 2. The first terminal device obtains the first identifier and the second identifier, and the first terminal device can match the first identifier and the second identifier with its own source layer 2 identifier (i.e., the third identifier) and destination layer 2 identifier (i.e., the fourth identifier), respectively. If the match is successful, it is determined that the COT of the second terminal device can be shared.

As another example, when the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group, the first identifier is the group member identifier corresponding to the first terminal device or at least one bit of the group member identifier, and the second identifier is the destination identifier. The first terminal device obtains the first identifier and the second identifier, and the first terminal device can match the first identifier and the second identifier with its own group member identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier), respectively. If the match is successful, it is determined that the COT of the second terminal device can be shared.

As another example, when the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group, the first identifier is the quantized value of the group member identifier corresponding to the first terminal device, and the second identifier is the destination identifier. The first terminal device obtains the first identifier and the second identifier, and the first terminal device can match the first identifier and the second identifier with the quantized value of its own group member identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier), respectively. If the match is successful, it is determined that the COT of the second terminal device can be shared.

In combination with the first aspect, in a possible implementation, the first terminal device sends side link data to at least one terminal device within the COT, including: the first terminal device sends side link data to at least one terminal device on a first resource within the COT; wherein the first resource is part or all of the resources corresponding to the COT.

In the above implementation, the first terminal device can send sidelink data to at least one terminal device on the first resource within the COT, which indicates that the resources corresponding to the COT are successfully shared.

In combination with the first aspect, in a possible implementation, the first information is also used to indicate a first resource, where the first resource is a resource reserved for the first terminal device.

In combination with the first aspect, in a possible implementation, the method also includes: the first terminal device performs type 2 listen before talk (LBT) before the time domain resource of the first resource; the first terminal device sends side link data to at least one terminal device on the first resource within the COT, including: when LBT is successful, the first terminal device sends side link data to at least one terminal device on the first resource.

In the above implementation, using type 2 LBT can improve the success rate of the first terminal device accessing the channel compared to using type 1 LBT, thereby ensuring that the first terminal device can send side link data to at least one terminal device on the first resource.

In a second aspect, a communication method is provided, including: a second terminal device sends first information to a first terminal device, the first information is used to determine a COT sharing the second terminal device; and the second terminal device receives side link data from the first terminal device within the COT.

In combination with the second aspect, in a possible implementation, the first information includes identification information, and the identification information includes a first identification and a second identification; the first identification is used to indicate a first terminal device sharing a COT, and the second identification is used to indicate a second terminal device; or, the first identification is used to indicate a first terminal device in a terminal device group, and the second identification is used to indicate a terminal device group.

In combination with the second aspect, in a possible implementation, the first information also includes transmission type indication information; when the transmission type indication information indicates unicast, the first identifier is used to indicate the first terminal device sharing the COT, and the second identifier is used to indicate the second terminal device; when the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group.

In combination with the second aspect, in a possible implementation, the first identifier is determined based on a third identifier from the first terminal device, and the second identifier is determined based on a fourth identifier from the first terminal device; wherein the third identifier is the source identifier of the first terminal device, the identifier of the first terminal device, the group member identifier corresponding to the first terminal device, or the first shared identifier, and the fourth identifier is the destination identifier of the first terminal device, the identifier of the second terminal device, or the second shared identifier.

In combination with the second aspect, in a possible implementation, the second terminal device receives sidelink data from the first terminal device within the COT, including: the second terminal device receives the sidelink data on the first resource within the COT; wherein the first resource is part or all of the resources corresponding to the COT.

In combination with the second aspect, in a possible implementation, the first information is also used to indicate a first resource, where the first resource is a resource reserved for the first terminal device.

According to a third aspect, a communication method is provided, comprising: a first terminal device receives first information from a second terminal device, the first information comprises N groups of identification information, one group of identification information in the N groups of identification information is used by the first terminal device to determine the COT of a shared second terminal device, N being an integer greater than or equal to 1; the first terminal device sends side link data to at least one terminal device within the COT, the at least one terminal device comprising the second terminal device.

In the above implementation, the second terminal device may send the first information including N groups of identification information to the first terminal device, so that the first terminal device The terminal device can determine the COT of the shared second terminal device through a set of identification information in the N sets of identification information, that is, the first terminal device correctly decodes the N sets of identification information, thereby accurately determining that the COT can be shared. Further, the first terminal device can send sidelink data to at least one terminal device within the COT, which indicates that the resources corresponding to the COT are successfully shared.

In combination with the third aspect, in a possible implementation manner, N is indicated to the first terminal device by the second terminal device or the network device, or N is predefined or preconfigured.

In the above implementation, the first terminal device can learn the number of groups of identification information, thereby ensuring that the first terminal device correctly decodes N groups of identification information. In addition, because N is predefined or preconfigured, no signaling indication is required, saving signaling overhead.

In a fourth aspect, a communication method is provided, comprising: a second terminal device sends first information to a first terminal device, the first information comprising N groups of identification information, one group of identification information in the N groups of identification information is used by the first terminal device to determine a channel occupancy time COT shared with the second terminal device, N being an integer greater than or equal to 1; the second terminal device receives side link data from the first terminal device within the COT.

In combination with the fourth aspect, in a possible implementation manner, N is indicated by the second terminal device to the first terminal device.

In conjunction with the fourth aspect, in a possible implementation manner, the method further includes: the second terminal device determines N according to the COT. If N is L or L-1, L is the COT.

In combination with the fourth aspect, in a possible implementation, the method further includes: the second terminal device determines N based on a candidate number set; wherein the candidate number set is indicated to the second terminal device by the network device; or, the candidate number set is predefined or preconfigured.

In the above implementation, the first terminal device can learn the number of groups of identification information, thereby ensuring that the first terminal device correctly decodes the N groups of identification information. In addition, because the candidate number set is predefined or preconfigured, no signaling indication is required, saving signaling overhead.

According to a fifth aspect, a communication device is provided, comprising a unit or module for implementing the method as described in any one of the first to fourth aspects.

In a sixth aspect, a communication device is provided, comprising at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that any method described in any one of the first aspect to the fourth aspect is executed.

In a seventh aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed, the computer executes the method as described in any one of the first to fourth aspects.

In an eighth aspect, a computer program product is provided, the computer program product comprising: a computer program code, and when the computer program code is executed by a computer, the computer executes a method as described in any one of the first to fourth aspects.

In a ninth aspect, a communication system is provided, comprising a first terminal device and a second terminal device, the first terminal device being used to execute a method as described in any one of the first aspect, and the second terminal device being used to execute a method as described in any one of the second aspect; or, the first terminal device being used to execute a method as described in any one of the third aspect, and the second terminal device being used to execute a method as described in any one of the fourth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

The following is a brief introduction to the drawings required for describing the embodiments.

Figure 1 is a schematic diagram of COT after successful LBT;

FIG2 is a schematic diagram of the structure of a communication system provided in an embodiment of the present application;

FIG3 is a schematic diagram of an L2 logo;

FIG4 is a schematic diagram of a hardware structure of a communication device applicable to an embodiment of the present application;

FIG5 is a flow chart of a communication method provided in an embodiment of the present application;

FIG6 is a schematic diagram of a relationship between a reserved resource and a resource corresponding to a COT provided in an embodiment of the present application;

FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

FIG8 is a schematic diagram of determining N through COT provided in an embodiment of the present application;

FIG9 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

FIG10 is a schematic diagram of a simplified structure of a UE provided in an embodiment of the present application;

FIG. 11 is a schematic diagram of the structure of a simplified network device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, the terms "system" and "network" in the embodiments of the present application can be used interchangeably. Unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship. For example, A/B can represent A or B; "and/or" in this application is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. These three situations, where A and B can be singular or plural. Moreover, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, a, b, or at least one of c, can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be one or more. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish between network elements and the same or similar items with basically the same functions. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit them to be different.

References to "one embodiment" or "some embodiments" etc. described in the embodiments of the present application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

The following specific implementation methods further describe in detail the objectives, technical solutions and beneficial effects of the present application. It should be understood that the following are only specific implementation methods of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

In the various embodiments of the present application, unless otherwise specified or provided in a logical conflict, the terms and/or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

The following is an explanation of some of the terms involved in this application.

1. SL

SL refers to: a link defined for direct communication between terminal devices. That is, a link for direct communication between terminal devices without forwarding by a base station. The interface between terminal devices can be called a PC5 interface.

The communication types supported on the SL may include broadcast communication, multicast communication, and unicast communication. In the LTE system, the SL supports broadcast communication. In the New Radio (NR) system, the SL supports broadcast communication, multicast communication, and unicast communication.

Broadcast communication is similar to network equipment broadcasting system information, that is, the terminal device sends broadcast services to the outside without encryption. Any other terminal device within the effective receiving range can receive the broadcast service if it is interested in the broadcast service.

Multicast communication refers to the communication between all terminals in a communication group. Any terminal device in the group can send and receive multicast services.

Unicast communication is similar to data communication between a terminal device and a network device after establishing a radio resource control (RRC) connection. It requires a unicast connection to be established between the two terminal devices. After the unicast connection is established, the two terminal devices can communicate data based on the negotiated identifier. The data can be encrypted or unencrypted. Compared with broadcast, in unicast communication, only two terminal devices that have established a unicast connection can communicate.

2. LBT

In unlicensed spectrum, each terminal device is eligible to use the spectrum, but different devices using the same frequency resources may cause conflicts, and transmission reliability cannot be guaranteed. Therefore, in unlicensed spectrum, terminal devices can determine whether the channel is idle before using it, so as to avoid conflicts and ensure transmission reliability. The process of terminal devices detecting whether the channel is idle is called the LBT process (also called the channel access process). If LBT is successful, it means that the channel is idle and can be accessed.

LBT can also be called a channel access process. For the convenience of description, it is collectively referred to as LBT below.

Generally, LBT is performed at the granularity of a channel (e.g., 20MHz), which can be understood as a resource block (RB) set, a subchannel (e.g., 20M), or a minimum frequency domain unit for performing LBT. Before a terminal device sends a signal (e.g., a data signal) on a certain channel (e.g., denoted as the first channel), it can first detect whether the first channel is idle. This process can be called clear channel assessment (CCA).

Specifically, there are two types of LBT, namely, the first type (type 1) LBT (also referred to as LBT based on a fixed duration) and the second type (type 2) LBT (also referred to as LBT based on fallback).

Type 1 LBT can be: energy detection based on a fixed duration. For a certain bandwidth, such as 20MHz, if the signal energy received by the terminal device within a fixed duration is less than or equal to the first preset threshold, the channel is considered idle and the terminal device can use the idle channel to transmit data; otherwise, the channel is considered busy and the terminal device does not use the busy channel to transmit data.

Type 2 LBT (also called backoff-based LBT) can be: energy detection based on a backoff mechanism. For a certain bandwidth, a window is defined, which defines the range of the number of time slots to be detected. The terminal device randomly selects a value A from the window (or value range). After the terminal device detects at least A idle energy detection time slots, it considers that the channel is idle and the terminal device can use the idle channel to transmit data; otherwise, it considers that the channel is busy and the terminal device does not use the busy channel to transmit data. Among them, idle energy detection means that the signal energy received within a fixed time length is less than or equal to the second preset threshold.

The first preset threshold and the second preset threshold may be predefined, such as predefined by a protocol, and this is not limited. In addition, there is no restriction between the first preset threshold and the second preset threshold, and they may be the same or different.

When performing LBT, two results can be obtained: LBT success and LBT failure. Among them, if there are multiple time domain starting positions in the time-frequency resources used for data transmission, if the channel is determined to be idle before any time domain starting position, then LBT can be considered successful; if the channel is determined to be busy before all time domain starting positions, then LBT can be considered failed.

In the scenario of unlicensed spectrum communication, the terminal device can use the resources on the unlicensed spectrum for communication only if LBT succeeds. Conversely, the terminal device cannot use the resources on the unlicensed spectrum for communication when LBT fails.

After a terminal device successfully accesses a channel, it can continue to occupy the channel for a period of time. From a time domain perspective, there is an upper limit to the length of time that a terminal device can occupy the channel, which can be called the maximum channel occupancy time (MCOT). Different channel access priority classes (CAPC) may have different corresponding MCOTs after accessing the channel. The values of MCOT under different CAPCs can be found in Table 1, but the values of MCOT in this application and the correspondence between CAPC and MCOT are not limited to the following table.

Table 1

COT is a concept in the time domain. The initial COT of a terminal device means that the terminal device can occupy a period of time in the spectrum in the time domain. From the frequency domain, the occupied position depends on factors such as the number of channels that perform LBT and whether it is frequency-division multiplexed with other terminal devices. The terminal device can access one channel or multiple channels according to demand. Therefore, the frequency domain resources corresponding to COT can include one or more RB sets. RB set is a collection of RBs. RB can also be understood as a physical resource block (PRB).

As shown in Figure 1, in 1-1 of Figure 1, the terminal device performs LBT on an RB set, and after success, accesses the channel, occupying a period of time. If the time domain length of the COT is L, the frequency domain length corresponding to the COT is the length of an RB set. In 1-2 of Figure 1, the terminal device successfully performs LBT on both RB set1 and RB set2, so two RB sets can be used for data transmission. In other words, the time domain length of the COT is L, and the frequency domain length corresponding to the COT is the length of two RB sets. Furthermore, the PRBs included in the intra-cell guard band between two adjacent RB sets also belong to the COT.

3. Layer 2 Identification

The source layer 2 identification may include the source layer 1 identification (layer 1 identification, L1ID) and the SRC field of the media access control (media access control, MAC) protocol data unit (PDU) subheader shown in Figure 2, the source layer 1 identification carries the 8-bit LSB of the source layer 2 identification, and the SRC field carries the 16-bit MSB of the source layer 2 identification.

The destination layer 2 identifier may include the destination layer 1 identifier and the DST field of the MAC PDU subheader shown in Figure 2, the destination L1ID carries the 16-bit LSB of the destination layer 2 identifier, and the DST field carries the 8-bit MSB of the destination layer 2 identifier.

4. Sidelink control information (SCI)

Among them, SCI can include first stage SCI (first stage SCI) and second stage SCI (second stage SCI). In this application, the first stage SCI can be called first-stage SCI, and the second stage SCI can be called second-stage SCI.

The above content briefly explains the meanings of some nouns involved in the embodiments of the present application. It is for a better understanding of the technical solutions provided in the embodiments of the present application, and does not constitute a limitation on the technical solutions provided in the embodiments of the present application.

In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:

The embodiments of the present application can be applied to communication systems evolved after 5G, such as long term evolution (LTE) system, fifth generation mobile communication (5G) system, sixth generation mobile communication (6G) system, satellite communication and short-range wireless communication systems. Among them, the wireless communication system mentioned in the embodiments of the present application includes but is not limited to: three major application scenarios of 5G/6G mobile communication system: enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC) and massive machine type communication (mMTC), long range Internet of Things (LoRa) system or vehicle networking system. The embodiments of the present application can also be applied to wireless local area network (WLAN) system, etc. The wireless communication system may include one or more network devices, and one or more terminal devices.

The following is an example explanation of the system architecture shown in Figure 3. In 3-1 of Figure 3, the network device and the terminal device can communicate through the uplink and/or downlink, and the terminal device and the terminal device can communicate through the side link. In 3-2 of Figure 3, the network device and the vehicle can communicate through the uplink and/or downlink, and the vehicle and the vehicle can communicate through the side link. 3-3 of Figure 3 is a vehicle networking communication scenario, Such as vehicle to vehicle (V2V) communication, vehicle to pedestrian (V2P) communication or vehicle to network communication. Vehicle to network communication can be referred to as vehicle to infrastructure (V2I) information exchange or vehicle to network (V2N) information exchange. In 3-4 of FIG. 3 , a processing device or a display device and an augmented reality (AR) device can communicate via a side link, or a processing device or a display device and a virtual reality (VR) device can communicate via a side link, or a processing device or a display device and a mixed reality (MR) device can communicate via a side link. In 3-5 of FIG. 3 , a router and a terminal device can communicate via an uplink and/or a downlink, a network device and a terminal device can communicate via an uplink and/or a downlink, and a terminal device and a terminal device can communicate via a side link.

It should be noted that the network equipment can be a cellular system related to the 3rd Generation Partnership Project (3GPP), for example, a 4G, 5G mobile communication system, or an evolved system after 5G (for example, a 6G mobile communication system). The network equipment can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), etc. The network equipment can also be a communication system that is a fusion of two or more of the above systems. It should be stated that the number of network devices and terminal devices in Figure 3 is only for illustration and should not be regarded as a specific limitation on this application. The terminal devices and network devices involved in the system architecture are described in detail below.

1. Terminal equipment

Terminal equipment can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or equipment used to provide voice or data connectivity to users, or IoT devices. For example, terminal equipment includes handheld devices with wireless connection functions, vehicle-mounted devices, etc. At present, terminal devices can be: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed railways, etc.), satellite terminals, virtual reality (VR) equipment, augmented reality (AR) equipment, smart point of sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electric meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. The terminal device may also be other devices having terminal functions. For example, the terminal device may also be a device that serves as a terminal in D2D communication.

The embodiments of the present application do not limit the device form of the terminal. The device for realizing the function of the terminal device can be a terminal device; it can also be a device that can support the terminal device to realize the function, such as a chip system. The device can be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices.

2. Network equipment

A network device is an entity on the network side that is used to send signals, receive signals, or both send and receive signals. A network device can be a device deployed in a radio access network (RAN) to provide wireless communication functions for terminal devices.

In a possible scenario, the network device may be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next generation NodeB (gNB), a next generation base station in the sixth generation (6G) mobile communication system, a base station in the future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, a network device in a mobile switching center non-terrestrial network (NTN) communication system, that is, it can be deployed on a high altitude platform or a satellite. The network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. The network device may also be a device that functions as a base station in device to device (D2D) communication, Internet of Vehicles communication, drone communication, and machine communication. Optionally, the network device may also be a server, a wearable device, a vehicle or an onboard device, etc. For example, the network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, and different network devices respectively implement part of the functions of the base station. For example, the network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be set separately, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It is understood that the network device may be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into a network device in the access network RAN, or the CU may be divided into a network device in the core network CN, without limitation here.

In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art will You can understand its meaning. For example, in the ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For the convenience of description, this application takes CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit in the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

Optionally, each device in FIG3 may be implemented by one device, or by multiple devices, or by a functional module in one device, and the present application embodiment does not specifically limit this. It is understandable that the above functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

For example, each device in FIG3 can be implemented by the communication device 400 in FIG4. FIG4 is a schematic diagram of the hardware structure of a communication device that can be applied to an embodiment of the present application. The communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.

Processor 401 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

The communication link 402 may include a pathway to transmit information between the above-mentioned components.

The communication interface 404 is any transceiver-like device (such as an antenna, etc.) used to communicate with other devices or communication networks. The communication network can be, for example, Ethernet, RAN, wireless local area networks (WLAN), etc.

The memory 403 may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via a communication line 402. The memory may also be integrated with the processor. The memory provided in the embodiment of the present application may generally have non-volatility.

The memory 403 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 401. The processor 401 is used to execute the computer-executable instructions stored in the memory 403, thereby implementing the method provided in the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

In a possible implementation, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .

In a possible implementation, the communication device 400 may include multiple processors, such as the processor 401 and the processor 407 in FIG. 4. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a possible implementation, the communication device 400 may further include an output device 405 and an input device 406. The output device 405 communicates with the processor 401 and may display information in a variety of ways. For example, the output device 405 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 406 communicates with the processor 401 and may receive user input in a variety of ways. For example, the input device 406 may be a mouse, a keyboard, a touch screen device, or a sensor device.

The communication device 400 can be a general device or a dedicated device. In a specific implementation, the communication device 400 can be a desktop computer, a portable computer, a network server, a PDA (personal digital assistant), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure as shown in FIG. 4. The embodiment of the present application does not limit the type of the communication device 400.

The communication method provided in the embodiment of the present application will be specifically described below in conjunction with Figures 3 to 4. Specifically, the first terminal device and the second terminal device in the following text may be the terminal devices in Figure 3. Among them, the first terminal device and the second terminal device may be located within the coverage of the same network device; or, the first terminal device and the second terminal device may be located within the coverage of different network devices; or, the first terminal device is located within the coverage of the network device, and the second terminal device is located outside the coverage of the network device (out of coverage); or, the first terminal device is located outside the coverage of the network device, and the second terminal device is located within the coverage of the network device; or the first terminal device and the second terminal device are both located outside the coverage of the network device, without limitation. For ease of description, the following is an example in which the first terminal device is UE1 and the second terminal device is UE2.

The COT of UE2 involved in this application may also be called the initial COT of UE2, the COT determined by UE2, or the COT owned by UE2, etc. This application does not limit the name.

The determination of UE1 to share UE2's COT involved in the present application can be understood as at least one of the following: UE1 determines that the COT can be used, UE1 Determine that the COT is allowed to be used, UE1 determines that the first resource in the COT can be shared, UE1 determines that the first resource in the COT can be used, UE1 determines that the first resource in the COT is allowed to be used, etc. The first resource is part or all of the resources corresponding to the COT, such as the first resource is part or all of the time-frequency resources corresponding to the COT, and for example, the first resource is part or all of the frequency domain resources in the time domain resources corresponding to the COT, and the frequency domain resources are the frequency domain resources successfully accessed by UE1.

It should be noted that the time domain resources involved in the present application may include, for example, at least one of the following: frame, subframe, time slot, micro time slot, symbol. The frequency domain resources may include, for example, at least one of the following: resource block group (RBG), RB set, RB, PRB, subcarrier, etc. The source identifier involved in the present application may be a source layer 2 identifier or at least one bit of a source layer 2 identifier. For example, the source identifier is the X1 bit intercepted from the highest bit of the source layer 2 identifier to the lower bit, referred to as the high X1 bit, that is, the source identifier is equal to the most significant bit (most significant bit, MSB) of the X1 bit of the source layer 2 identifier. For another example, the source identifier is the X2 bit intercepted from the lowest bit of the source layer 2 identifier to the higher bit, referred to as the high X2 bit, that is, the source identifier is equal to the least significant bit (least significant bit, LSB) of the X2 bit of the source layer 2 identifier. X1 and X2 may be the same or different. X1 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the source layer 2 identifier. X2 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the source layer 2 identifier.

The destination identifier involved in the present application may be a destination layer 2 identifier or at least one bit of a destination layer 2 identifier. For example, the destination identifier is the X3 bits sequentially intercepted from the highest bit of the destination layer 2 identifier to the lower bits, referred to as the high X3 bits, that is, the destination identifier is equal to the MSB of the X3 bits of the destination layer 2 identifier. For another example, the destination identifier is the X4 bits sequentially intercepted from the lowest bit of the destination layer 2 identifier to the higher bits, referred to as the high X4 bits, that is, the destination identifier is equal to the LSB of the X2 bits of the destination layer 2 identifier. X3 and X4 may be the same or different. X3 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the destination layer 2 identifier. X4 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the destination layer 2 identifier.

The identifier of UE1 involved in this application can be a device identifier configured, preconfigured, predefined by a network device or indicated by a high-level layer of UE1. The identifier of UE1 can uniquely locate UE1, that is, a UE (such as UE2) communicating with UE1 can uniquely indicate UE1.

The identifier of UE2 involved in this application can be a device identifier configured, preconfigured, predefined by a network device or indicated by a high-level layer of UE2. The identifier of UE2 can uniquely locate UE2, that is, a UE (such as UE1) communicating with UE2 can uniquely indicate UE1.

The first shared identifier and the second shared identifier involved in this application can be understood as a pair of identifiers used by UE1 to determine the COT shared by UE2, and their names are not limited in this application.

The quantized value of the group member identifier involved in the present application is determined based on the group member identifier and the group size. For example, the quantized value of the group member identifier is equal to mod(group member identifier/group size), where mod represents modulus, and the group size is the number of group members included in the UE group where the group member identifier is located.

As shown in FIG5 , a communication method is provided in an embodiment of the present application, and the communication method includes but is not limited to the following steps:

501. UE2 sends first information to UE1. Correspondingly, UE1 receives the first information from UE2. The first information is used by UE1 to determine the COT of sharing UE2.

The first information may be referred to as COT indication information, COT sharing indication information or COT sharing information. Optionally, the first information may be carried in a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), an SCI (such as a first-order SCI or a second-order SCI, etc.) or a MAC control element (CE).

Optionally, the first information includes identification information, and the identification information is used by UE1 to determine the COT shared by UE2. The identification information may include at least one of the first identification and the second identification. Optionally, the first information also includes transmission type indication information, and the transmission type indication information may indicate unicast, multicast or broadcast. It should be noted that in this application, the transmission type indication information may be referred to as broadcast type indication information or communication type indication information, etc., and this application does not limit the name.

Optionally, the identification information may include a first identification and a second identification, that is, the identification information always includes a pair of identifications, namely, the first identification and the second identification.

In this application, the first identifier and the second identifier are implemented in the following ways:

Mode 1.1, the first identifier is used to indicate UE1 that shares the COT, and the second identifier is used to indicate UE2. If the transmission type indication information indicates unicast, the first identifier is used to indicate UE1 that shares the COT, and the second identifier is used to indicate UE2. In one possible implementation, the first identifier is a source identifier, and the second identifier is a destination identifier; or, the first identifier is the source identifier of UE1, and the second identifier is the destination identifier of UE1; or, the first identifier is the destination identifier of UE2, and the second identifier is the source identifier of UE2. In another possible implementation, the first identifier is the identifier of UE1 or at least one bit of the identifier of UE1, and the second identifier is the identifier of UE2 or at least one bit of the identifier of UE2. In another possible implementation, the first identifier is the first shared identifier or at least one bit of the first shared identifier, and the second identifier is the second shared identifier or at least one bit of the second shared identifier.

Mode 1.2: The first identifier is used to indicate UE2, and the second identifier is used to indicate UE1 sharing the COT. In one possible implementation, the first identifier is used to indicate UE2, and the second identifier is used to indicate UE1 that shares the COT. In one possible implementation, the first identifier is the source identifier of UE2, and the second identifier is the destination identifier of UE2. Or, the first identifier is the destination identifier of UE1, and the second identifier is the source identifier of UE1. In another possible implementation, the first identifier is the identifier of UE2 or at least one bit of the identifier of UE2, and the second identifier is the identifier of UE1 or at least one bit of the identifier of UE1. In another possible implementation, the first identifier is the second shared identifier or at least one bit of the second shared identifier, and the second identifier is the first shared identifier or at least one bit of the first shared identifier.

Mode 1.3, the first identifier is used to indicate UE1 in the UE group, and the second identifier is used to indicate the UE group. If the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate UE1 in the UE group, and the second identifier is used to indicate the UE group. The number of UEs included in the UE group may be one or more. In one possible implementation, the first identifier is a source identifier, and the second identifier is a destination identifier; or, the first identifier is a source identifier of UE1, and the second identifier is a destination identifier; or, the first identifier is a destination identifier of UE2, and the second identifier is a destination identifier; or, the first identifier is a destination identifier 1, and the second identifier is a destination identifier 2, and the destination identifier 1 is the source identifier of UE1 or the destination identifier of UE2, and the destination identifier 2 is the destination identifier corresponding to the multicast data, which can also be understood as: the destination identifier 2 indicates the multicast service or indicates the UE group. In another possible implementation, the first identifier is a group member identifier corresponding to UE1, at least one bit of the group member identifier, or a quantized value of the group member identifier, and the second identifier is a destination identifier. In another possible implementation, the first identifier is a first shared identifier or at least one bit of the first shared identifier, and the second identifier is a second shared identifier or at least one bit of the second shared identifier. Among them, in method 1.3, the target identifier described by the second identifier can be understood as: the destination identifier corresponding to the data to be sent by UE1, or the destination identifier corresponding to the data to be received by UE2, or the destination identifier corresponding to the multicast service type, or the destination identifier associated with the multicast service, or the destination identifier associated with the multicast data, or an identifier used to indicate that a group of UEs share the COT. In method 1.3, the first identifier can be called a source identifier or a destination identifier, but is not limited to these two names, and can also be called a terminal identifier, a terminal identifier dedicated to indicating UE1, or an identifier dedicated to indicating UE1, or an identifier used to indicate that UE1 in the UE group shares the COT, or an identifier used to indicate UE1 in the UE group.

In the above implementation, for mode 1.1 or mode 1.2, since the source identifier and the destination identifier are a pair of identifiers, the pair of identifiers can uniquely indicate the unicast link between UE1 and UE2. That is, in this pair of identifiers, assuming that the destination identifier and the source identifier are both layer 2 identifiers (both are 24 bits), the destination identifier of UE1 is equal to the source identifier of UE2; assuming that the lengths of the destination identifier and the source identifier are different, then X1 bits of the destination identifier of UE1 are equal to the source identifier of UE2 (the length of the destination identifier of UE1 is greater than the length of the source identifier of UE2) or the destination identifier of UE1 is equal to Y1 bits of the source identifier of UE2 (the length of the destination identifier of UE1 is less than the length of the source identifier of UE2). Correspondingly, assuming that the destination identifier and the source identifier are both layer 2 identifiers (both are 24 bits), the source identifier of UE1 is equal to the destination identifier of UE2; assuming that the lengths of the destination identifier and the source identifier are different, then X2 bits of the source identifier of UE1 are equal to the destination identifier of UE2 (the length of the source identifier of UE1 is greater than the length of the destination identifier of UE2) or the source identifier of UE1 is equal to Y2 bits of the destination identifier of UE2 (the length of the source identifier of UE1 is less than the length of the destination identifier of UE2).

It should be pointed out that a certain identifier (such as a first identifier) involved in the present application is used to indicate the UE1 sharing the COT, which can be understood as at least one of the following: the identifier is used to indicate the UE1 that can use the COT, the identifier is used to indicate the UE1 that is allowed to use the COT, the identifier is used to indicate the UE1 that shares the COT, the identifier is used to indicate the UE1 that can use the first resource in the COT, the identifier is used to indicate the UE1 that is allowed to use the first resource, and the identifier is used to indicate the UE1 that shares the first resource. A certain identifier (such as a second identifier) involved in the present application is used to indicate a UE group, which can be understood as at least one of the following: the identifier is used to indicate the type of service (or multicast data, or multicast service) that UE2 expects to receive (or to be received), the identifier is used to indicate that UE2 is the receiving end of the data to be transmitted in UE1, the identifier is used to indicate the data (or data type) to be received by UE2, the identifier is used to indicate the type of service (or data type, or data) that UE2 is interested in, the identifier is used to indicate a group of sending ends to send a type of multicast data, and the identifier is used to indicate the multicast data to be sent by UE1. In a possible implementation, when the transmission type indication information indicates unicast, the bit position of the first identifier is located before the bit position of the second identifier. If the first identifier is located at a low position, the second identifier is located at a high position; or, the bit position of the first identifier is located after the bit position of the second identifier. If the first identifier is located at a high position, the second identifier is located at a low position. When the transmission type indication information indicates multicast or broadcast, the bit position of the first identifier is located before the bit position of the second identifier. If the first identifier is located at a low position, the second identifier is located at a high position.

In a possible implementation, the method further includes: UE1 determines the shared COT according to at least one of the first identifier and the second identifier. If the identification information includes the first identifier, UE1 determines the shared COT according to the first identifier. If the identification information includes the second identifier, UE1 determines the shared COT according to the second identifier. This achieves accurate indication of the UE1 that can use the COT, thereby improving the utilization efficiency of the spectrum.

Optionally, UE1 determines the shared COT according to at least one of the first identifier and the second identifier, including: when the first condition is met, UE1 determines the shared COT. It can also be understood that: when the first condition is met and the transmission type indication information indicates unicast, multicast or broadcast, UE1 determines the shared COT. The first condition includes at least one of the following: the first identifier matches the third identifier; the second identifier matches the fourth identifier.

It should be noted that the matching of one identifier and another identifier in this application can be understood as: all bits in one identifier are part or all of the bits in another identifier, or all bits in one identifier are equal to part or all of the bits in another identifier. If the first identifier and the third identifier are equal, or all bits in the first identifier are equal to the high Y1 bit or the low Y2 bit of the third identifier, Y1 and Y2 can be Same or different. Y1 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the third identifier. Y2 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the third identifier. Optionally, Y1 and Y2 can be 8, such as the first identifier is 00001111, and the 8-bit MSB or 8-bit LSB of the third identifier is also 00001111. For another example, the second identifier and the fourth identifier are equal, or all the bits of the second identifier are equal to the high Y3 bit or the low Y4 bit of the fourth identifier, and Y3 and Y4 can be the same or different. Y3 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the fourth identifier. Y4 is an integer greater than or equal to 1 and less than or equal to the total number of bits of the fourth identifier. Vice versa, that is, part or all of the bits of one identifier are all the bits in another identifier, or part or all of the bits of one identifier are equal to all the bits in another identifier. I will not go into details here.

In this application, the third identifier has the following implementation methods:

Mode 2.1: The third identifier is determined according to the source identifier, such as the source identifier or at least one bit of the source identifier.

Mode 2.2: The third identifier is determined according to the source identifier of UE1, such as the source identifier or at least one bit of the source identifier.

Mode 2.3: The third identifier is determined according to the purpose identifier of UE2, such as the purpose identifier or at least one bit of the purpose identifier.

Mode 2.4: The third identifier is determined according to the identifier of UE1, such as the identifier of UE1 or at least one bit of the identifier of UE1.

Mode 2.5: The third identifier is determined according to the first shared identifier, such as the first shared identifier or at least one bit of the first shared identifier.

Mode 2.6: The third identifier is determined according to the source identifier of UE2, such as the source identifier or at least one bit of the source identifier.

Mode 2.7: The third identifier is determined according to the purpose identifier of UE1, such as the purpose identifier or at least one bit of the purpose identifier.

Mode 2.8: The third identifier is determined according to the group member identifier corresponding to UE1, such as the group member identifier, at least one bit of the group member identifier, or a quantized value of the group member identifier. The group member identifier may be a group member identifier indicated by a higher layer of UE1, or the group member identifier may be a network device configuration, preconfiguration, or predefined.

Mode 2.9: The third identifier is determined according to the destination identifier 1, such as the destination identifier 1 or at least one bit of the destination identifier 1.

The length of the identifier determined by each implementation of the third identifier can be the same or different, and this is not restricted in this application. For example, the identifier length in methods 2.1 to 2.3, 2.6, 2.7 or 2.9 is 24, that is, the source identifier is the source layer 2 identifier, and the destination identifier is the destination layer 2 identifier.

In this application, the fourth identifier has the following implementation methods:

Mode 3.1: The fourth identifier is determined according to the destination identifier, such as the destination identifier or at least one bit of the destination identifier.

Mode 3.2: The fourth identifier is determined according to the purpose identifier of UE1, such as the purpose or at least one bit of the purpose identifier.

Mode 3.3: The fourth identifier is determined according to the source identifier of UE2, such as the source identifier or at least one bit of the source identifier.

Mode 3.4: The fourth identifier is determined according to the identifier of UE2, such as the identifier of UE2 or at least one bit of the identifier of UE2.

Mode 3.5: The fourth identifier is determined according to the second shared identifier, such as the second shared identifier or at least one bit of the second shared identifier.

Mode 3.6: The fourth identifier is determined according to the purpose identifier of UE2, such as the purpose identifier or at least one bit of the purpose identifier.

Mode 3.7: The fourth identifier is determined according to the source identifier of UE1, such as the source identifier or at least one bit of the source identifier.

Mode 3.8: The fourth identifier is determined according to the destination identifier 2, such as the destination identifier 2 or at least one bit of the destination identifier 2.

The length of the identifier determined by each implementation method of the above-mentioned fourth identifier may be the same or different, and this is not restricted in the present application. Exemplarily, the identifier length in methods 3.1 to 3.4, 3.6, 3.7 or 3.8 is 24, that is, the source identifier is the source layer 2 identifier, and the destination identifier is the destination layer 2 identifier. Optionally, when the first identifier is used to indicate UE1 sharing the COT, and the second identifier is used to indicate UE2, any one of methods 2.1 to 2.5 can be combined with any one of methods 3.1 to 3.5. Exemplarily, method 2.1 is combined with method 3.1. Method 2.2 is combined with method 3.2. Method 2.3 is combined with method 3.3. Method 2.4 is combined with method 3.4. Method 2.5 is combined with method 3.5.

Optionally, when the first identifier is used to indicate UE2, and the second identifier is used to indicate UE1 sharing the COT, any one of methods 2.5 to 2.7 may be combined with any one of methods 3.5 to 3.7. Exemplarily, method 2.5 is combined with method 3.5. Method 2.6 is combined with method 3.6. Method 2.7 is combined with method 3.7.

Optionally, when the first identifier is used to indicate UE1 in the UE group, and the second identifier is used to indicate the UE group, any one of Modes 2.1 to 2.3, Mode 2.5, Mode 2.8 and Mode 2.9 may be combined with any one of Modes 3.1 to 3.3, Mode 3.5 and Mode 3.8. Exemplarily, Mode 2.1 is combined with Mode 3.1. Mode 2.2 is combined with Mode 3.2. Mode 2.5 is combined with Mode 3.5. Mode 2.8 is combined with Modes 3.1 to 3.2 or 3.8. Mode 2.1 is combined with Mode 3.8.

When the identification information includes the first identification and the second identification, the following describes the matching of the first identification with the third identification and the matching of the second identification with the fourth identification in conjunction with specific examples.

Exemplarily, the first identifier is the source identifier and the second identifier is the destination identifier; or, the first identifier is the source identifier of UE1 and the second identifier is the destination identifier of UE1; or, the first identifier is the destination identifier of UE2 and the second identifier is the source identifier of UE2. UE1 obtains the first identifier and Second identifier, UE1 can match the first identifier and the second identifier with its own source layer 2 identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT can be shared. At this time, the implementation method of the first identifier and the second identifier is method 1.1, and the implementation methods of the third identifier and the fourth identifier correspond to methods 2.2 and 3.2 respectively.

As another example, the first identifier is the source identifier of UE2, and the second identifier is the destination identifier of UE2. UE1 obtains the first identifier and the second identifier, and UE1 can match the first identifier and the second identifier with its own destination layer 2 identifier (i.e., the third identifier) and source layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT can be shared. At this time, the implementation method of the first identifier and the second identifier is method 1.2, and the implementation methods of the third identifier and the fourth identifier correspond to methods 2.7 and 3.7 respectively.

As another example, the first identifier is a source identifier and the second identifier is a destination identifier; or, the first identifier is the source identifier of UE1 and the second identifier is a destination identifier; or, the first identifier is the destination identifier of UE2 and the second identifier is a destination identifier; or, the first identifier is destination identifier 1 and the second identifier is destination identifier 2. UE1 obtains the first identifier and the second identifier, and UE1 can match the first identifier and the second identifier with its own source layer 2 identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT can be shared. At this time, the implementation method of the first identifier and the second identifier is method 1.3, and the implementation methods of the third identifier and the fourth identifier correspond to methods 2.2 and 3.2 respectively.

In another exemplary embodiment, the first identifier is the group member identifier corresponding to UE1 or at least one bit of the group member identifier, and the second identifier is the destination identifier. UE1 obtains the first identifier and the second identifier, and UE1 can match the first identifier and the second identifier with its own group member identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier) respectively. If the match is successful, it is determined that the COT can be shared. At this time, the implementation method of the first identifier and the second identifier is method 1.3, and the implementation methods of the third identifier and the fourth identifier correspond to methods 2.8 and 3.2 respectively.

As another example, the first identifier is the quantized value of the group member identifier corresponding to UE1, and the second identifier is the destination identifier. UE1 obtains the first identifier and the second identifier, and UE1 can match the first identifier and the second identifier with the quantized value of its own group member identifier (i.e., the third identifier) and the destination layer 2 identifier (i.e., the fourth identifier), respectively. If the match is successful, it is determined that the COT can be shared. At this time, the implementation method of the first identifier and the second identifier is method 1.3, and the implementation methods of the third identifier and the fourth identifier correspond to methods 2.8 and 3.2, respectively.

When the identification information includes the second identification in mode 1.3 (such as the second identification is the destination identification), the following describes the matching of the second identification and the fourth identification in combination with a specific example. That is, when the second identification matches the fourth identification, UE1 determines to share the COT of UE2. For example, each UE in a certain UE group (the UE group includes UE1) matches its own destination layer 2 identification with the destination identification. If the match is successful, it is determined that the COT of UE2 can be shared. Specifically, each UE in the UE group can determine the sub-channel unit that can be used by taking a modulus in the sub-channel unit included in the first resource according to the group member identification. The sub-channel unit can be a sub-channel or M sub-channels, where M is a positive integer. For example, M=1, the first resource includes 6 sub-channels in the first time slot, and 3 group members take a modulus in the 6 sub-channels according to their own group member identifications. Or M=2. The 6 sub-channels are divided into 3 sub-channel units, and the 3 group members take a modulus in the 3 sub-channel units according to their own group member identifications to obtain the sharable sub-channels. The three group members use frequency division multiplexing (FDM) access channels.

In a possible implementation, the first identifier is determined based on the third identifier from UE1, and the second identifier is determined based on the fourth identifier from UE1. For example, UE1 may send the third identifier and the fourth identifier to UE2 through SCI (such as second-order SCI), a resource request message, or past interaction information (past interaction information may be understood as information sent by UE1 to UE2), so that UE2 may determine the first identifier and the second identifier based on the third identifier and the fourth identifier, respectively.

The following describes how UE2 determines the first identifier and the second identifier based on the third identifier and the fourth identifier respectively with reference to specific examples.

For the scenario of "the first identifier is the source identifier, and the second identifier is the destination identifier; or, the first identifier is the source identifier of UE1, and the second identifier is the destination identifier of UE1; or, the first identifier is the destination identifier of UE2, and the second identifier is the source identifier of UE2" in method 1.1, UE2 can generate the source identifier (i.e., the first identifier) and the destination identifier (i.e., the second identifier) in the first information according to the source identifier (i.e., the third identifier) and the destination identifier (i.e., the fourth identifier) of UE1, respectively. In other words, the source identifier and the destination identifier in the first information are the source ID and the destination ID from the perspective of UE1, respectively. It can also be understood that: UE2 forwards the detected source identifier and destination identifier of UE1. Among them, the source identifier of UE1 is the source layer 1 identifier or the source layer 2 identifier, and the destination identifier of UE1 is the destination layer 1 identifier or the destination layer 2 identifier. Optionally, the length of the source identifier and the destination identifier may be the same or different. The lengths of the source identifier and the destination identifier are determined independently.

Exemplarily, in the first case, the source identifier of UE1 is a source layer 1 identifier or a source layer 2 identifier, and the destination identifier of UE1 is a destination layer 1 identifier or a destination layer 2 identifier. Therefore, the first identifier is the source layer 1 identifier of UE1, and the second identifier is the destination layer 1 identifier of UE1. It should be understood that the source layer 1 identifier of UE1 and the destination layer 1 identifier of UE1 are a pair of identifiers. It can also be said that the source layer 1 identifier of UE1 and the destination layer 1 identifier of UE1 have an associated relationship or a corresponding relationship. The source layer 1 identifier of UE1 can be equal to a destination layer 1 identifier of UE2, and the destination layer 1 identifier of UE1 can be equal to a source layer 1 identifier of UE2.

As another example, in the second case, the source identifier of UE1 is the source layer 2 identifier, and the destination identifier of UE1 is the destination layer 2 identifier. Therefore, the first identifier is the source layer 2 identifier of UE2, and the second identifier is the destination layer 2 identifier of UE2. It should be understood that the source layer 2 identifier of UE2 and the destination layer 2 identifier of UE2 are a pair of identifiers. It can also be said that the source layer 2 identifier of UE2 and the destination layer 2 identifier of UE2 have an associated relationship or a corresponding relationship. The source layer 2 identifier of UE2 can be equal to a destination layer 2 identifier of UE2, and the destination layer 2 identifier of UE2 can be equal to a source layer 2 identifier of UE2. Layer 2 identification.

For the scenario of "the first identifier is the source identifier of UE2, and the second identifier is the destination identifier of UE2" in method 1.2, UE2 can generate the destination identifier (i.e., the first identifier) and the source identifier (i.e., the second identifier) in the first information according to the source identifier (i.e., the third identifier) and the destination identifier (i.e., the fourth identifier) of UE1, respectively. In other words, the source identifier and the destination identifier from the perspective of UE1 correspond to the destination identifier and the source identifier from the perspective of UE2. Among them, the source identifier of UE1 is the source layer 1 identifier or the source layer 2 identifier, and the destination identifier of UE1 is the destination layer 1 identifier or the destination layer 2 identifier.

Exemplarily, in the third case, the source identifier of UE1 is the source layer 1 identifier or the source layer 2 identifier, and the destination identifier of UE1 is the destination layer 1 identifier or the destination layer 2 identifier, therefore, the first identifier is the destination layer 1 identifier of UE1, and the second identifier is the source layer 1 identifier of UE1. It should be understood that because the source identifier of UE1 and the destination identifier of UE1 are a pair of IDs between UE1 and UE2, such as the source layer 1 identifier and the destination layer 1 identifier are a pair of IDs between UE1 and UE2, and for another example, the source layer 2 identifier and the destination layer 2 identifier are a pair of IDs between UE1 and UE2, the first identifier can also be understood as the source layer 1 identifier of UE2, and the second identifier is the destination layer 1 identifier of UE2.

As another example, in the fourth case, the source identifier of UE1 is the source layer 2 identifier, and the destination identifier of UE1 is the destination layer 2 identifier, therefore, the first identifier is the destination layer 2 identifier of UE1, and the second identifier is the source layer 2 identifier of UE1. It should be understood that because the source layer 2 identifier and the destination layer 2 identifier are a pair of IDs between UE1 and UE2, the first identifier can also be understood as the source layer 1 identifier of UE2, and the second identifier is the destination layer 1 identifier of UE2.

For the scenario in method 1.3 where "the first identifier is the source identifier, and the second identifier is the destination identifier; or, the first identifier is the source identifier of UE1, and the second identifier is the destination identifier; or, the first identifier is the destination identifier of UE2, and the second identifier is the destination identifier; or, the first identifier is the destination identifier 1, and the second identifier is the destination identifier 2", it is similar to the first and second cases mentioned above and will not be elaborated here.

In a possible implementation, the first identifier and the second identifier can be understood as a group of identifiers or a pair of identifiers, or the first identifier and the second identifier are included in a group of identifier information. A group of identifiers or a pair of identifiers is used by UE1 to determine the COT shared by UE2. The first identifier and the second identifier correspond to a link. The first identifier and the second identifier have a corresponding relationship or an associated relationship.

Exemplarily, the first information includes N groups of identification information, which can also be understood as: one or more groups of identification information or N pairs of identifications, where N is an integer greater than or equal to 1. The following is explained by taking N groups of identification information as an example. Each group of identification information can be used by different UEs (including UE1) to determine the COT of the shared UE2, such as sharing different resources among the resources corresponding to the COT. That is, the shared UE indicated by each group of identification information is independent. Each group of identification information includes a first identification and a second identification. Among them, the physical meaning, corresponding propagation type or function of the first identification and the second identification in each group of identification information are independent. The way in which UE2 determines the first identification and the second identification included in each group of identification information may be a different way in the embodiment of the present application, that is, the way of determining the first identification and the second identification in each group of identification information is independent and does not affect each other.

Optionally, the relative positions of the first identifier and the second identifier included in each group of identification information in the N groups of identification information are different under different transmission types. For example, when the transmission type indication information indicates unicast, the bit position of the first identifier is located after the bit position of the second identifier (or the first identifier is first and the second identifier is later, or the second identifier is cascaded before the first identifier, or the first identifier is in the low position and the second identifier is in the high position); when the transmission type indication information indicates multicast or broadcast, the bit position of the first identifier is located before the bit position of the second identifier; or when the transmission type indication information indicates unicast, the bit position of the first identifier is located before the bit position of the second identifier; when the transmission type indication information indicates multicast or broadcast, the bit position of the first identifier is located after the bit position of the second identifier.

Exemplarily, N is 3, then the three groups of identification information are {destination identification 1, source identification 1}, {destination identification 2, source identification 2}, {source identification 3, destination identification 3}. The transmission types corresponding to these three groups of identification information are unicast, unicast, and multicast, respectively. That is, for unicast, the first identification comes first and the second identification comes later; for multicast, the second identification comes first and the first identification comes later. UE1 receives the N groups of identifications. For the first group of identification information, UE1 can match its own source identification and destination identification with destination identification 1 and source identification 1 respectively; for the second group of identification information, UE1 can match its own source identification and destination identification with destination identification 2 and source identification 2 respectively; for the third group of identification information, UE1 can match its own source identification and destination identification with destination identification 3 and source identification 3 respectively. At this time, UE1 only needs to obtain the first identification and the second identification, and does not need to obtain additional propagation type indication information. For each group of identification information, UE1 can match its own source identification with the previous identification in the group identification information, and match its own destination identification with the latter identification in the group identification information.

When the relative positions of the first identifier and the second identifier in each group of identifier information are fixed, the first information may further include transmission type indication information. In this case, UE1 may use the first identifier and the second identifier in combination with the transmission type indication information.

502. UE1 sends sidelink data to at least one UE in the COT, where the at least one UE includes UE2. For example, UE2 receives sidelink data from UE1 in the COT.

In a possible implementation, step 502 may include: UE1 sends sidelink data to at least one UE on the first resource within the COT. For example, when the propagation type indication information indicates unicast, UE1 sends sidelink data to UE2 on the first resource. For another example, when the propagation type indication information indicates multicast or broadcast, UE1 sends sidelink data on the first resource so that multiple UEs (including UE2) interested in the sidelink data can obtain the sidelink data. That is, UE1 sends sidelink data on the first resource, and multiple UEs including UE2 receive the sidelink data.

Among them, the first resource is part or all of the resources corresponding to the COT. Optionally, the first information is also used to indicate the first resource, and the first resource is a resource reserved by UE1. For example, UE1 sends SCI to enable UE2 to know the resources reserved by UE1. When the resources reserved by UE1 belong to the resources corresponding to the COT determined by UE2, UE2 can share COT with UE1. For example, UE2 sends indication information to UE1, and the indication information is used to indicate the resources reserved by UE1 (specific time-frequency resources) or to indicate UE2 to share the reserved resources of UE1 with UE1 (1-bit indication information, no need to indicate specific time-frequency resources). As shown in Figure 6, the SCI sent by UE1 to UE2 can indicate resources. For example, the SCI includes a first field and/or a second field. Among them, the first field in the SCI is used to indicate the time domain resources reserved by UE1, and/or the second field in the SCI is used to indicate the frequency domain resources reserved by UE1. Optionally, the first field and the second field can be the same field or different fields. The resources reserved by UE1 are part of the resources corresponding to the COT determined by UE2, so UE2 can share the resources reserved by UE1 with UE1, such as UE2 can indicate part or all of the frequency domain resources of one or more time slots in the reserved resources to UE1. Or, UE2 indicates other resources except the reserved resources to UE1.

In a possible implementation, the method further includes: UE1 performs type 2 LBT before the time domain resource of the first resource; UE1 sends sidelink data to at least one UE on the first resource within the COT, including: when LBT is successful, UE1 sends sidelink data to at least one UE on the first resource. By using type 2 LBT, the success rate of UE1 accessing the channel can be improved compared to using type 1 LBT, thereby ensuring that UE1 can send sidelink data to at least one UE on the first resource.

UE1 performs type 2 LBT before the time domain resources of the first resource, which can be understood as one of the following: UE1 performs type 2 LBT before using the first resource, UE1 performs type 2 LBT before the starting position of the time domain resources of the first resource, and UE1 starts to perform type 2 LBT at an interval before the starting position of the time domain resources of the first resource.

In the above embodiment, the UE1 that can use the COT is accurately and uniquely indicated, and the conflict problem caused by multiple UEs using the COT is reduced. At the same time, the resources corresponding to the COT are successfully shared.

Among them, when UE1 sends sidelink data, the source layer 1 identifier (8 bits) and the destination layer 1 identifier (16 bits) included in the second-order SCI used to schedule the sidelink data are determined according to the first identifier and the second identifier respectively. Alternatively, when UE1 sends sidelink data, the destination layer 1 identifier (16 bits) included in the second-order SCI used to schedule the sidelink data is determined according to the second identifier. Optionally, this situation is applicable to multicast. Alternatively, when UE1 sends sidelink data, the source layer 1 identifier (8 bits) included in the second-order SCI used to schedule the sidelink data is determined according to the first identifier.

Exemplarily, for the first case mentioned above, when UE1 sends side link data, the source layer 1 identifier included in the second-order SCI used to schedule the side link data is equal to the first identifier, and when UE1 sends side link data, the destination layer 1 identifier included in the second-order SCI used to schedule the side link data is equal to the second identifier.

As another example, for the second or fourth case mentioned above, when UE1 sends sidelink data, the second-order SCI used to schedule the sidelink data includes the source layer 1 identifier as the 8-bit LSB of the first identifier, and when UE1 sends sidelink data, the second-order SCI used to schedule the sidelink data includes the destination layer 1 identifier as the 16-bit LSB of the second identifier.

As another example, for the third case above, when UE1 sends sidelink data, the second-order SCI used to schedule the sidelink data includes a source layer 1 identifier as the 8-bit LSB of the second identifier, and when UE1 sends sidelink data, the second-order SCI used to schedule the sidelink data includes a destination layer 1 identifier as the 8-bit LSB of the first identifier.

Among them, when the propagation type indication information indicates multicast or broadcast, the method for determining the source layer 1 identifier and the destination layer 1 identifier included in the second-order SCI used to schedule the side link data when UE1 sends the side link data is similar to the method for determining the source layer 1 identifier and the destination layer 1 identifier in the first case or the second case, and will not be repeated here.

When UE1 sends sidelink data, the SRC field (16 bits) and DST field (8 bits) included in the MAC PDU subheader corresponding to the second-order SCI used to schedule the sidelink data are determined according to the first identifier and the second identifier respectively.

Exemplarily, for the second or fourth case above, when UE1 sends sidelink data, the SRC field included in the MAC PDU subheader corresponding to the second-order SCI used to schedule the sidelink data is the 16MSBs of the second identifier, and when UE1 sends sidelink data, the DST field included in the MAC PDU subheader corresponding to the second-order SCI used to schedule the sidelink data is the 8 MSBs of the first identifier. Among them, when the propagation type indication information indicates multicast or broadcast, the method for determining the SRC field and DST field included in the MAC PDU subheader corresponding to the second-order SCI used to schedule the sidelink data when UE1 sends sidelink data is similar to the method for determining the SRC field and DST field in the second case, and is not repeated here.

In a possible implementation, the method further includes: UE1 sends second information to UE2, the second information is used to indicate the priority value of UE1 (including but not limited to this purpose), such as the second information is the priority value of the service to be transmitted by UE1 and/or CAPC (i.e., the priority field and/or CAPC field in the SCI sent by UE1). Optionally, the first information is sent based on the priority of UE1. For example, after UE2 receives the second information from UE1, when the second condition is met, UE2 sends the first information to UE1 or UE2 shares COT with UE1.

The second condition includes at least one of the following: the priority value of UE1 is less than or equal to the preset priority value, the priority value of UE1 is less than Or equal to the priority value of UE2, the UE communicating with UE1 includes UE2, UE1 and UE2 have a sending and receiving relationship, UE2 is the receiving end of the data sent by UE1, etc. Optionally, the priority value of UE2 can be the priority value and/or CAPC of the service to be transmitted by UE2, etc. For example, the priority value of the service to be transmitted by UE1 is less than or equal to the priority value of the service to be transmitted by UE2, and/or the CAPC value of UE1 is less than or equal to the CAPC value of UE2. Here, the smaller the priority value, the higher the priority and the more important it is. The present invention uses this to illustrate the logical relationship, and the present invention does not limit this. When the larger the priority value, the higher the priority and the more important it is, the comparison direction is opposite.

It should be understood that the identifier in the embodiment of the present application can be understood as an ID, or ID information or identification information. The destination identifier can be understood as a target identifier, a destination identifier, a receiving identifier, or a receiving end identifier. The source identifier can be understood as a sending end identifier.

It should be understood that the matching of two identifiers in the embodiments of the present application can be understood as the comparison, contrast, and comparison of the two identifiers, or whether the two identifiers are the same, or whether one of the two identifiers is equal to part or all of the bits of the other identifier, or whether the two identifiers belong to the same identifier, that is, the two identifiers belong to different bits of the same identifier.

As shown in FIG. 7 , another communication method is provided in an embodiment of the present application, and the communication method includes but is not limited to the following steps:

701. UE2 sends first information to UE1. Correspondingly, UE1 receives first information from UE2. The first information includes N groups of identification information. One group of identification information in the N groups of identification information is used by UE1 to determine the COT shared by UE2. N is an integer greater than or equal to 1.

In a possible implementation, one group of identification information in the N groups of identification information is used for UE1 to determine that the COT shared by UE2 is used, which can be understood as at least one of the following: the group identification information is used for UE1 to determine that it can use the COT, the group identification information is used for UE1 to determine that it is allowed to use the COT, etc.

It should be noted that each group of identification information in the N groups of identification information can be used by different UEs (including UE1) to determine the shared COT of UE2, such as sharing different resources in the resources corresponding to the COT. That is, the shared UEs indicated by each group of identification information are independent. Exemplarily, if N is 2, one group of identification information is used for UE1 to determine the shared first resource in the COT, and another group of identification information is used for UE3 to determine the shared second resource in the COT. The first resource is part of the resources corresponding to the COT, and the second resource is part of the resources corresponding to the COT. The first resource and the second resource can be frequency division multiplexed (FDM) or time division multiplexing (TDM).

In a possible implementation, the identifiers included in any one group of identification information in the N groups of identification information are similar to the first identifier and the second identifier in step 501 of Figure 5. For example, the identifiers included in a group of identification information in the N groups of identification information used for UE1 to determine the COT shared by UE2 are the first identifier and the second identifier in step 501 of Figure 5. Optionally, the first information may also include N propagation type indication information, and the N propagation type indication information corresponds one-to-one to the N groups of identification information. When the propagation type indication information indicates unicast, the specific contents of the first identifier and the second identifier included in the group of identification information in the N groups of identification information used for UE1 to determine the COT shared by UE2 can refer to step 501 of Figure 5. When the propagation type indication information indicates multicast or broadcast, the specific contents of the first identifier and the second identifier included in the group of identification information in the N groups of identification information used for UE1 to determine the COT shared by UE2 can refer to step 501 of Figure 5.

Optionally, the first information can be carried in PSCCH, PSSCH, SCI (such as first stage SCI or second stage SCI, etc.) or MAC CE.

In a possible implementation, N is indicated by UE2 to UE1, such as N is indicated by UE2 to UE1 through PSCCH, PSSCH, SCI (such as first stage SCI or second stage SCI, etc.) or MAC CE. Optionally, N is indicated by UE2 to UE1 through a field in PSCCH, PSSCH, SCI (such as first stage SCI or second stage SCI, etc.) or MAC CE.

As an example, the method further includes: UE2 determines N according to the COT of UE2 (i.e., the length of the CO initially set by UE2 or the duration of UE2 occupying the channel). If N is L or L-1, L is the COT. Exemplarily, as shown in FIG8 , the COT is 7, that is, the number of time slots included in the COT is 7. N can be 7, that is, each time slot can correspond to a set of identification information, which is used to indicate that the corresponding time slot is shared with the corresponding UE. At this time, N is the same as the number of UEs that can use the resources corresponding to the COT. Alternatively, N can be 7-1, such as UE2 sending the first information in the first time slot (time slot 0) of the COT, the first time slot cannot be shared, and therefore, the number of shareable time slots is 6, such as time slot 1 to time slot 6. This allows UE1 to know the number of groups of identification information, thereby ensuring that UE1 correctly decodes N groups of identification information.

As another example, the method also includes: UE2 determines N according to a candidate number set. That is, N comes from a candidate number set. The candidate number set is a set of candidate values of N. The candidate number set may include one or more values. Among them, the candidate number set is indicated to UE2 by a network device, that is, the candidate number set is configured by the network device to UE2; or, the candidate number set is predefined or preconfigured. Exemplarily, the candidate number set configured by the network device includes 8 and 16, and UE2 can indicate N to UE1 through 1 bit in SCI. If 1 bit is a first value, N is 8, and 1 bit is a second value, N is 16. The first value and the second value are different, such as the first value is 0 and the second value is 1, and vice versa. This allows UE1 to know the number of groups of identification information, thereby ensuring that UE1 correctly decodes N groups of identification information. In addition, because the candidate number set is predefined or preconfigured, no signaling indication is required, saving signaling overhead.

In another possible implementation, N is indicated to UE1 by the network device, that is, N is configured by the network device to UE2. This enables UE1 to know the number of groups of identification information, thereby ensuring that UE1 correctly decodes N groups of identification information.

In another possible implementation, N is predefined or preconfigured. Optionally, if the network device configures or preconfigures the number of groups of identification information, UE1 can use the number of groups of identification information configured or preconfigured by the network device, otherwise UE1 can use the default value, preset value or fixed value of N. This allows UE1 to know the number of groups of identification information, thereby ensuring that UE1 correctly decodes N groups of identification information. In addition, when N is predefined or preconfigured, no signaling indication is required, saving signaling overhead.

Optionally, N can be referred to as the number of COT shared UEs, the number of COT shared identification pairs, the maximum number of COT shared UEs, or the maximum number of identification information groups, etc.

702. UE1 sends sidelink data to at least one UE in the COT, where the at least one UE includes UE2. For example, UE2 receives sidelink data from UE1 in the COT.

Among them, step 702 is similar to step 502 in Figure 5 and is not repeated here.

In the above embodiment, UE1 correctly decodes N groups of identification information, accurately and uniquely indicates UE1 that can use the first resource, and reduces the conflict problem caused by multiple UEs using the first resource. At the same time, the resources corresponding to COT are successfully shared.

The above mainly introduces the solution provided by the present application from the perspective of interaction between various devices. It is understandable that in order to realize the above functions, the above-mentioned implementation devices include hardware structures and/or software modules corresponding to the execution of various functions. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application can divide the functional modules of UE (such as UE1 or UE2), network equipment, etc. according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

Refer to Figure 9, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 900 can be applied to any of the methods shown above. As shown in Figure 9, the communication device 900 includes: a processing module 901 and a transceiver module 902. The processing module 901 can be one or more processors, and the transceiver module 902 can be a transceiver or a communication interface. The communication device can be used to implement the UE (such as UE1 or UE2) or network device involved in any of the above method embodiments, or to implement the functions of the network element involved in any of the above method embodiments. The network element or network function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). Optionally, the communication device 900 can also include a storage module 903 for storing program code and data of the communication device 900.

In one example, when the communication device acts as a UE (such as UE1 or UE2) or a chip applied to a UE (such as UE1 or UE2), and executes the steps performed by the UE (such as UE1 or UE2) or UE (such as UE1 or UE2) in the above method embodiments. The transceiver module 902 is used to support communication with network devices, etc. The transceiver module specifically performs the actions of sending and/or receiving performed by the UE (such as UE1 or UE2) or UE (such as UE1 or UE2) in any of the above method embodiments, for example, supporting the UE (such as UE1 or UE2) to perform other processes described herein. The processing module 901 can be used to support the communication device 900 to perform the actions other than sending and receiving performed by the UE (such as UE1 or UE2) or UE (such as UE1 or UE2) in the above method embodiments, for example, supporting the UE (such as UE1 or UE2) to perform other processes of the technology described herein.

In a possible implementation, the transceiver module 902 is used to: receive first information from UE2, where the first information is used by UE1 to determine a COT sharing UE2; and send sidelink data to at least one UE within the COT, where the at least one UE includes UE2.

Optionally, the first information includes identification information, and the identification information includes a first identification and a second identification. The processing module 901 is further configured to determine a shared COT according to at least one of the first identification and the second identification.

Optionally, when determining the shared COT based on at least one of the first identifier and the second identifier, the processing module 901 is used to determine the shared COT when the first condition is met; wherein the first condition includes at least one of the following: the first identifier matches the third identifier; the second identifier matches the fourth identifier; the third identifier is determined based on the source identifier of UE1, the identifier of UE1, the group member identifier corresponding to UE1 or the first shared identifier; the fourth identifier is determined based on the destination identifier of UE1, the identifier of UE2 or the second shared identifier.

Optionally, the first identifier is used to indicate UE1 that shares the COT, and the second identifier is used to indicate UE2; or, the first identifier is used to indicate UE1 in a UE group, and the second identifier is used to indicate the UE group.

Optionally, the first information further includes transmission type indication information; when the transmission type indication information indicates unicast, the first identifier is used to indicate UE1 sharing the COT, and the second identifier is used to indicate UE2; when the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate UE UE1 in the group, the second identifier is used to indicate the UE group.

Optionally, the first identifier is determined based on a third identifier from UE1, and the second identifier is determined based on a fourth identifier from UE1.

Optionally, when sidelink data is sent to at least one UE within the COT, the transceiver module 902 is used to send sidelink data to at least one UE on a first resource within the COT; wherein the first resource is part or all of the resources corresponding to the COT.

Optionally, the first information is also used to indicate a first resource, where the first resource is a resource reserved for UE1.

Optionally, the processing module 901 is also used to perform type 2 listen-before-talk LBT before the time domain resource of the first resource; when sending side link data to at least one UE on the first resource within the COT, the transceiver module 902 is used to send side link data to at least one UE on the first resource when the LBT is successful.

In yet another possible implementation, the transceiver module 902 is configured to: send first information to UE1, where the first information is used to determine a channel occupation time COT of the shared UE2; and receive sidelink data from UE1 within the COT.

Optionally, the first information includes identification information, and the identification information includes a first identification and a second identification; the first identification is used to indicate UE1 sharing the COT, and the second identification is used to indicate UE2; or, the first identification is used to indicate UE1 in the UE group, and the second identification is used to indicate the UE group.

Optionally, the first information also includes transmission type indication information; when the transmission type indication information indicates unicast, the first identifier is used to indicate UE1 sharing the COT, and the second identifier is used to indicate UE2; when the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate UE1 in the UE group, and the second identifier is used to indicate the UE group.

Optionally, the first identifier is determined based on a third identifier from UE1, and the second identifier is determined based on a fourth identifier from UE1; wherein the third identifier is the source identifier of UE1, the identifier of UE1, the group member identifier corresponding to UE1, or the first shared identifier, and the fourth identifier is the destination identifier of UE1, the identifier of the second UE, or the second shared identifier.

Optionally, in the COT, when receiving sidelink data from UE1, the transceiver module 902 is used to receive the sidelink data on the first resource in the COT; wherein the first resource is part or all of the resources corresponding to the COT.

Optionally, the first information is also used to indicate a first resource, where the first resource is a resource reserved for UE1.

In another possible implementation, the transceiver module 902 is used to: receive first information from UE2, the first information includes N groups of identification information, one group of identification information in the N groups of identification information is used by UE1 to determine the channel occupancy time COT of shared UE2, N is an integer greater than or equal to 1; within the COT, send sidelink data to at least one UE, the at least one UE includes UE2.

Optionally, N is indicated to UE1 by UE2 or a network device, or N is predefined or preconfigured.

In another possible implementation, the transceiver module 902 is used to: send first information to UE1, the first information includes N groups of identification information, one group of identification information in the N groups of identification information is used by UE1 to determine the channel occupancy time COT shared by UE2, N is an integer greater than or equal to 1; within the COT, receive side link data from UE1.

Optionally, N is indicated by UE2 to UE1.

Optionally, the processing module 901 is further configured to determine N according to the COT. If N is L or L-1, L is the COT determined by the UE2.

Optionally, the processing module 901 is further configured to determine N according to a candidate number set; wherein the candidate number set is indicated to UE2 by the network device; or, the candidate number set is predefined or preconfigured.

In a possible implementation, when the UE (such as UE1 or UE2) or the network device is a chip, the transceiver module 902 may be a communication interface, a pin or a circuit, etc. The communication interface may be used to input data to be processed to the processor, and may output the processing result of the processor to the outside. In a specific implementation, the communication interface may be a general purpose input output (GPIO) interface, which may be connected to multiple peripheral devices (such as a display (LCD), a camera (camara), a radio frequency (RF) module, an antenna, etc.). The communication interface is connected to the processor via a bus.

The processing module 901 may be a processor, which may execute computer-executable instructions stored in the storage module, so that the chip executes the method involved in any of the above embodiments.

Furthermore, the processor may include a controller, an arithmetic unit and a register. Exemplarily, the controller is mainly responsible for instruction decoding and issuing control signals for operations corresponding to the instructions. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, etc., and may also perform address operations and conversions. The register is mainly responsible for storing register operands and intermediate operation results temporarily stored during the execution of instructions. In a specific implementation, the hardware architecture of the processor may be an ASIC architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced RISC machines (ARM) architecture, or a second processor (NP) architecture, etc. The processor may be single-core or multi-core.

The storage module may be a storage module within the chip, such as a register, a cache, etc. The storage module may also be a storage module located outside the chip, such as a ROM or other types of static storage devices that can store static information and instructions, a RAM, etc.

It should be noted that the functions corresponding to the processor and the interface can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.

FIG10 is a schematic diagram of a simplified UE structure provided in an embodiment of the present application. For ease of understanding and illustration, in FIG10, UE takes a mobile phone as an example. As shown in FIG10, the UE includes at least one processor, and may also include a radio frequency circuit, an antenna, and an input/output device. Among them, the processor may be used to process communication protocols and communication data, and may also be used to control the UE, execute software programs, process data of software programs, etc. The UE may also include a memory, which is mainly used to store software programs and data. These programs involved may be loaded into the memory when the communication device leaves the factory, or may be loaded into the memory when needed later. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves, and the antenna is the antenna provided in an embodiment of the present application. Input/output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of UE may not have input/output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the UE, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, only one memory and processor are shown in Figure 10. In an actual UE product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.

In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver functions can be regarded as the receiving unit and the sending unit of the UE (also collectively referred to as the transceiver unit), and the processor with the processing function can be regarded as the processing unit of the UE. As shown in Figure 10, the UE includes a receiving module 31, a processing module 32 and a sending module 33. The receiving module 31 can also be called a receiver, a receiver, a receiving circuit, etc., and the sending module 33 can also be called a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The processing module 32 can also be called a processor, a processing board, a processing device, etc.

For example, the processing module 32 is used to execute the functions of the UE (such as UE1 or UE2) in any of the above methods.

FIG11 is a schematic diagram of the structure of a simplified network device provided in an embodiment of the present application. The network device includes a radio frequency signal transceiving and conversion part and a baseband part 42, and the radio frequency signal transceiving and conversion part includes a receiving module 41 part and a sending module 43 part (also collectively referred to as a transceiver module). The radio frequency signal transceiving and conversion part is mainly used for the transceiving of radio frequency signals and the conversion of radio frequency signals and baseband signals; the baseband part 42 is mainly used for baseband processing, controlling the network device, etc. The receiving module 41 can also be called a receiver, a receiver, a receiving circuit, etc., and the sending module 43 can also be called a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The baseband part 42 is usually the control center of the network device, and can also be called a processing module, which is used to execute the steps performed by the network device in any of the above methods. For details, please refer to the description of the above-mentioned relevant parts.

The baseband part 42 may include one or more single boards, each of which may include one or more processors and one or more memories, and the processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the network device. If there are multiple single boards, each single board can be interconnected to increase the processing capacity. As an optional implementation, multiple single boards may share one or more processors, or multiple single boards may share one or more memories, or multiple single boards may share one or more processors at the same time.

For example, the sending module 43 is used to execute the function of the network device in any of the above methods.

An embodiment of the present application provides a communication device, which includes at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that the method corresponding to each device or network element in any of the above methods is executed.

An embodiment of the present application provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed, the computer executes any of the methods described above.

An embodiment of the present application provides a computer program product, which includes: a computer program code, and when the computer program code is executed by a computer, the computer executes a method as described in any of the above methods.

An embodiment of the present application provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory, so that a device where the chip is located implements the method described in any of the above methods.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application. In addition, each network element unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software network element units.

If the above-mentioned integrated unit is implemented in the form of a software network element unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the part that essentially contributes to the technical solution of the present application, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a terminal device, a cloud server, or a network device, etc.) to perform all or part of the steps of the above-mentioned methods of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, network device dom Access Memory), disk or optical disk and other media that can store program code. The above is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (37)

A communication method, characterized by comprising: A first terminal device receives first information from a second terminal device, where the first information is used by the first terminal device to determine a channel occupancy time COT shared with the second terminal device; The first terminal device sends sidelink data to at least one terminal device within the COT, and the at least one terminal device includes the second terminal device. The method according to claim 1 is characterized in that the first information is COT indication information, and the first information is carried in a second-order SCI. The method according to claim 1 or 2, characterized in that the first information includes identification information, the identification information includes a first identification and a second identification, and the method further includes: The first terminal device determines to share the COT according to at least one of the first identifier and the second identifier. The method according to claim 3 is characterized in that the first terminal device determines to share the COT according to at least one of the first identifier and the second identifier, comprising: when a first condition is met, the first terminal device determines to share the COT; The first condition includes at least one of the following: the first identifier matches the third identifier; the second identifier matches the fourth identifier. The method according to any one of claims 1-4 is characterized in that the first information also includes propagation type indication information, and the propagation type indication information indicates unicast, multicast or broadcast. The method according to claim 4 or 5, characterized in that the first terminal device determines to share the COT, comprising: The first terminal device uses at least one of the first identifier and the second identifier to determine sharing the COT based on the propagation type indication information. The method according to any one of claims 1 to 6 is characterized in that the first identifier is a source identifier and the second identifier is a destination identifier. The method according to claim 7 is characterized in that the first identifier is a source identifier of the second terminal device, and the second identifier is a destination identifier of the second terminal device. The method according to any one of claims 4 to 8 is characterized in that the third identifier is a destination layer 2 identifier of the first terminal device, and the fourth identifier is a source layer 2 identifier of the first terminal device. The method according to any one of claims 1-9 is characterized in that, when the first terminal device sends multicast data to the second terminal device, the first terminal device determines the destination layer 1 identifier in the second-order SCI for scheduling the side link data based on the second identifier. The method according to any one of claims 1 to 10, characterized in that The first identifier is used to indicate the first terminal device that shares the COT, and the second identifier is used to indicate the second terminal device; or, The first identifier is used to indicate the first terminal device in a terminal device group, and the second identifier is used to indicate the terminal device group. The method according to any one of claims 1 to 11, characterized in that When the transmission type indication information indicates unicast, the first identifier is used to indicate the first terminal device sharing the COT, and the second identifier is used to indicate the second terminal device; When the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group. The method according to any one of claims 1-12 is characterized in that the first identifier is determined based on the third identifier from the first terminal device, and the second identifier is determined based on the fourth identifier from the first terminal device. The method according to any one of claims 1 to 13, characterized in that the first terminal device sends sidelink data to at least one terminal device within the COT, comprising: The first terminal device sends the sidelink data to the at least one terminal device on a first resource within the COT; The first resource is part or all of the resources corresponding to the COT. The method according to claim 14 is characterized in that the first information is also used to indicate the first resource, and the first resource is a resource reserved for the first terminal device. The method according to claim 14 or 15, characterized in that the method further comprises: The first terminal device performs type 2 listen-before-talk LBT before the time domain resource of the first resource; The first terminal device sends the sidelink data to the at least one terminal device on a first resource within the COT, include: When the LBT is successful, the first terminal device sends the sidelink data to the at least one terminal device on the first resource. A communication method, comprising: The second terminal device sends first information to the first terminal device, where the first information is used to determine a channel occupancy time COT shared with the second terminal device; The second terminal device receives sidelink data from the first terminal device within the COT. The method according to claim 17 is characterized in that the first information is COT indication information, and the first information is carried in a second-order SCI. The method according to claim 17 or 18 is characterized in that the first information includes propagation type indication information, and the propagation type indication information indicates unicast, multicast or broadcast. The method according to any one of claims 17 to 19, characterized in that the first information includes identification information, and the identification information includes a first identification and a second identification; The first identifier is used to indicate the first terminal device that shares the COT, and the second identifier is used to indicate the second terminal device; or, The first identifier is used to indicate the first terminal device in a terminal device group, and the second identifier is used to indicate the terminal device group. The method according to any one of claims 17-20 is characterized in that the first identifier is a source identifier and the second identifier is a destination identifier. The method according to claim 21 is characterized in that the first identifier is a source identifier of the second terminal device, and the second identifier is a destination identifier of the second terminal device. The method according to any one of claims 17 to 22, characterized in that When the transmission type indication information indicates unicast, the first identifier is used to indicate the first terminal device sharing the COT, and the second identifier is used to indicate the second terminal device; When the transmission type indication information indicates multicast or broadcast, the first identifier is used to indicate the first terminal device in the terminal device group, and the second identifier is used to indicate the terminal device group. The method according to any one of claims 17 to 23, characterized in that the first identifier is determined based on a third identifier from the first terminal device, and the second identifier is determined based on a fourth identifier from the first terminal device; Among them, the third identifier is the source identifier of the first terminal device, the identifier of the first terminal device, the group member identifier corresponding to the first terminal device or the first shared identifier, and the fourth identifier is the destination identifier of the first terminal device, the identifier of the second terminal device or the second shared identifier. The method according to any one of claims 17 to 24, wherein the second terminal device receives the sidelink data from the first terminal device in the COT, comprising: The second terminal device receives the sidelink data on a first resource within the COT; The first resource is part or all of the resources corresponding to the COT. The method according to claim 25 is characterized in that the first information is also used to indicate the first resource, and the first resource is a resource reserved for the first terminal device. A communication method, comprising: A first terminal device receives first information from a second terminal device, where the first information includes N groups of identification information, where one group of identification information in the N groups of identification information is used by the first terminal device to determine a channel occupation time COT shared with the second terminal device, where N is an integer greater than or equal to 1; The first terminal device sends sidelink data to at least one terminal device within the COT, and the at least one terminal device includes the second terminal device. The method according to claim 27 is characterized in that the N is indicated to the first terminal device by the second terminal device or the network device, or the N is predefined or preconfigured. A communication method, characterized by comprising: The second terminal device sends first information to the first terminal device, where the first information includes N groups of identification information, where one group of identification information in the N groups of identification information is used by the first terminal device to determine a channel occupation time COT shared with the second terminal device, where N is an integer greater than or equal to 1; The second terminal device receives sidelink data from the first terminal device within the COT. The method according to claim 29 is characterized in that the N is indicated to the first terminal device by the second terminal device. The method according to claim 29, characterized in that the method further comprises: The second terminal device determines the N according to the COT. The method according to claim 30, characterized in that the N is L or L-1, and the L is the COT. The method according to claim 30, characterized in that the method further comprises: The second terminal device determines N according to a candidate number set; The candidate quantity set is indicated to the second terminal device by a network device; or, The candidate quantity set is predefined or preconfigured. A communication device, characterized in that it comprises a unit or module for implementing the method as described in any one of claims 1 to 33. A communication device, characterized in that the communication device comprises at least one processor and a memory; The memory is used to store computer programs or instructions; and the at least one processor is used to execute the computer programs or instructions in the memory, so that the method described in any one of claims 1 to 33 is executed. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, and when the computer instructions are executed, the computer is caused to execute the method as described in any one of claims 1 to 33. A computer program product, characterized in that the computer program product comprises: a computer program code, and when the computer program code is executed by a computer, the computer executes the method as described in any one of claims 1 to 33.