Communication method and terminal

Abstract

The present application relates to a communication method and a terminal. The method comprises: a first terminal sending first control information, wherein the first control information comprises channel occupancy time (COT) sharing information. In the embodiments of the present application, first control information sent by a terminal comprises COT sharing information, such that the terminal can send and / or receive sidelink control information.

Description

Communication method and terminal Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and a terminal. Background Art

[0002] The Sidelink Over Unlicensed Spectrum (SL-U) system supports a Channel Occupancy Time (COT) sharing mechanism. After initiating COT using Listen Before Talk (LBT), a terminal can share the COT with other terminals. These other terminals then access the channel using a Type 2 LBT method. This improves resource utilization and facilitates channel contention for SL-U terminals. In sidelink transmission over unlicensed spectrum, how a terminal shares the COT with other terminals is a technical challenge that needs to be addressed.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a terminal that can send control information in sidelink transmission.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The first terminal sends first control information, where the first control information includes channel occupancy time (COT) sharing information.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The second terminal receives the first control information, where the first control information includes COT sharing information.

[0009] An embodiment of the present application provides a first terminal, including:

[0010] The sending unit is configured to send first control information, where the first control information includes COT sharing information.

[0011] An embodiment of the present application provides a second terminal, including:

[0012] The receiving unit is configured to receive first control information, where the first control information includes COT sharing information.

[0013] An embodiment of the present application provides a terminal device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory so that the terminal device executes the above-mentioned communication method.

[0014] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.

[0015] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.

[0016] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned communication method.

[0017] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.

[0018] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.

[0019] In the embodiment of the present application, the first control information sent by the first terminal includes COT sharing information, which enables the terminal to send and / or receive sideline control information. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of time slot symbols used for SL transmission according to the present application.

[0021] FIG2 is a schematic diagram of the PSCCH and PSSCH time slot structure according to the present application.

[0022] FIG3 is a schematic diagram of the time domain position of PSSCH DMRS symbols according to the present application.

[0023] FIG4 is a schematic diagram of the frequency domain position of PSSCH DMRS symbols according to the present application.

[0024] FIG5 is a schematic diagram of a PSSCH PSCCH resource pool according to the present application.

[0025] FIG6 is a schematic diagram of the time slot structure of the NR system according to the present application.

[0026] FIG7 is a schematic diagram of interleaving resource blocks according to the present application.

[0027] FIG8 is a schematic diagram of an RB set according to the present application.

[0028] FIG9 is a schematic flowchart of a communication method 900 according to an embodiment of the present application.

[0029] FIG10 is a schematic flowchart of a communication method 1000 according to an embodiment of the present application.

[0030] FIG11 is a schematic block diagram of a first terminal 1100 according to an embodiment of the present application.

[0031] FIG12 is a schematic block diagram of a second terminal 1200 according to an embodiment of the present application.

[0032] FIG13 is a schematic block diagram of a communication device 1300 according to an embodiment of the present application.

[0033] FIG14 is a schematic block diagram of a chip 1400 according to an embodiment of the present application.

[0034] FIG15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] 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.

[0036] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0037] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0038] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0039] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0040] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0041] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0042] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0043] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0044] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0045] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0046] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0047] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0048] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0049] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0050] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0051] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0052] 1. Timeslot Structure in New Radio Sidelink (NR SL)

[0053] In New Radio Vehicle to Everything (NR-V2X), the Physical Sidelink Shared Channel (PSSCH) and its associated Physical Sidelink Control Channel (PSCCH) are transmitted in the same time slot, and the PSCCH occupies 2 or 3 time domain symbols. The time domain resource allocation of NR-V2X is based on the time slot as the allocation granularity. The starting point and length of the time domain symbols used for sidelink transmission in a time slot are configured by the parameters starting symbol position (sl-startSLsymbols) and number of symbols (sl-lengthSLsymbols). The last symbol in this part of symbols is used as the guard period (GP), and PSSCH and PSCCH can only use the remaining time domain symbols. However, if a timeslot is configured with Physical Sidelink Feedback Channel (PSFCH) transmission resources, PSSCH and PSCCH cannot occupy the time domain symbol used for PSFCH transmission, as well as the Automatic Gain Control (AGC) and GP symbols preceding the symbol.

[0054] As shown in Figure 1, the network configuration sl-StartSymbol = 3, sl-LengthSymbols = 11, that is, the 11 time domain symbols starting from symbol index 3 in a time slot can be used for sideline transmission. There are PSFCH transmission resources in the time slot. The PSFCH occupies symbols 11 and 12, among which symbol 11 is used as the AGC symbol of PSFCH, and symbols 10 and 13 are used as GPs respectively. The time domain symbols that can be used for PSSCH transmission are symbols 3 to 9. PSCCH occupies 3 time domain symbols, namely symbols 3, 4, and 5, and symbol 3 is usually used as an AGC symbol.

[0055] In addition to PSCCH and PSSCH, a physical sidelink feedback channel (PSFCH) may also exist in a sidelink time slot in NR-V2X. In a time slot, the first orthogonal frequency division multiplexing (OFDM) symbol is fixed for automatic gain control (AGC). On the AGC symbol, the UE copies the information sent on the second symbol. At the end of the time slot, one symbol is reserved for transceiver conversion, which is used for the UE to switch from the transmit (or receive) state to the receive (or transmit) state. In the remaining OFDM symbols, PSCCH can occupy two or three OFDM symbols starting from the second sidelink symbol. In the frequency domain, the number of physical resource blocks (PRBs) occupied by PSCCH is within the sub-band range of a PSSCH. If the number of PRBs occupied by the PSCCH is smaller than the size of one subchannel of the PSSCH, or the frequency domain resources of the PSSCH include multiple subchannels, the PSCCH can be frequency-division multiplexed with the PSSCH on the OFDM symbol where the PSCCH is located.

[0056] PSSCH is used to carry second-order sidelink control information (SCI) and sidelink shared channel (SL-SCH). The 3rd Generation Partnership Project (3GPP) defines two second-order SCI formats, namely SCI format 2-A and SCI format 2-B. SCI format 2-B is suitable for multicast communication methods that perform sidelink hybrid automatic repeat reQuest (HARQ) feedback based on distance information. SCI format 2-A is suitable for other scenarios, such as unicast, multicast, and broadcast that do not require sidelink HARQ feedback, unicast communication methods that require sidelink HARQ feedback, and multicast communication methods that require feedback of positive acknowledgment (ACK) or negative acknowledgment (NACK). 3GPP has also introduced an additional second-order SCI format, namely SCI format 2-C, which is used to indicate reference resource sets and trigger signaling in specific circumstances. The modulation symbols of the second-order SCI are mapped starting from the symbol where the first PSSCH modulation and demodulation reference signal is located, using a frequency domain first and then a time domain mapping. They are then interleaved with the resource elements (REs) of the demodulation reference signal (DMRS) on this symbol. Furthermore, the modulation symbols of the second-order SCI cannot be mapped to the REs where the phase-tracking reference signals (PT-RS) are located, as shown in Figure 2.

[0057] In the sidewalk communication system, the UE's autonomous resource selection or the determination of transmission resources based on the network's sidewalk resource scheduling may cause different UEs to send PSCCH on the same time-frequency resources. In order to ensure that the receiver can detect at least one PSCCH in the event of a PSCCH resource conflict, LTE-V2X adopts a PSCCH DMRS randomization design. Specifically, when sending PSCCH, the UE can randomly select a value from {0, 3, 6, 9} as the cyclic shift of the DMRS. If multiple UEs use different cyclic shifts for the PSCCH DMRS sent on the same time-frequency resources, the receiving UE can still detect at least one PSCCH through the orthogonal DMRS. For the same purpose, NR-V2X introduces three PSCCH DMRS frequency domain orthogonal covering codes (OCC) for the transmitting UE to randomly select, as shown in Table 1, where the i-th bit of the OCC mask is applied to the i-th DMRS RE in the resource block (RB), thereby achieving the effect of distinguishing different UEs.

[0058] Table 1 OCC mask of PSCCH DMRS

[0059] The DMRS for the PSSCH in NR-V2X draws on the design of the NR Uu interface and uses multiple time-domain PSSCH DMRS patterns. Within a resource pool, the number of available DMRS patterns is related to the number of PSSCH symbols in the resource pool. For a specific number of PSSCH symbols (including the first AGC symbol) and PSCCH symbols, the available DMRS patterns and the position of each DMRS symbol within the pattern are shown in Table 2. Figure 3 shows a schematic diagram of the time-domain positions of four DMRS symbols when the PSSCH has 13 symbols.

[0060] Table 2 Number and position of DMRS symbols under different PSSCH and PSCCH symbol numbers

[0061] If multiple time-domain DMRS patterns are configured within the resource pool, the transmitting UE selects the specific time-domain DMRS pattern to use and indicates this in the first-order SCI. This design allows high-speed UEs to select a high-density DMRS pattern, thereby ensuring accurate channel estimation. For slow-moving UEs, a low-density DMRS pattern can be used, thereby improving spectral efficiency.

[0062] The generation method of the PSSCH DMRS sequence is almost the same as that of the PSCCH DMRS sequence. The difference lies in the initialization formula c(m) of the pseudo-random sequence. initmiddle, p i The i-th CRC bit of the PSCCH that schedules the PSSCH, where L=24 is the number of bits of the PSCCH cyclic redundancy check (CRC).

[0063] The NR physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) support two frequency domain DMRS patterns, namely DMRS frequency domain type 1 and DMRS frequency domain type 2. Moreover, for each frequency domain type, there are two different types: single DMRS symbol and double DMRS symbol. Single-symbol DMRS frequency domain type 1 supports 4 DMRS ports, and single-symbol DMRS frequency domain type 2 can support 6 DMRS ports. In the case of double DMRS symbols, the number of supported ports is doubled. However, in NR-V2X, since PSSCH only needs to support two DMRS ports at most, only single-symbol DMRS frequency domain type 1 is supported, as shown in Figure 4.

[0064] 2. Frequency Domain Resource Determination in NR SL

[0065] Similar to LTE-V2X, the frequency domain resources in the NR-V2X resource pool are contiguous, and the frequency domain resource allocation granularity is also subchannels. A subchannel consists of a number of PRBs {10, 12, 15, 20, 50, 75, 100}, with the smallest subchannel size being 10 PRBs, significantly larger than the minimum subchannel size of 4 PRBs in LTE-V2X. This is primarily because the frequency domain resources of the PSCCH in NR-V2X are located within the first subchannel of its associated PSSCH. The frequency domain resources of the PSCCH are less than or equal to the size of a single PSSCH subchannel, while the time domain resources of the PSCCH occupy two or three OFDM symbols. If the subchannel size is configured too small, the available PSCCH resources are limited, increasing the code rate and degrading PSCCH detection performance. In NR-V2X, the PSSCH subchannel size and the PSCCH frequency domain resource size are configured independently, but the PSCCH frequency domain resources must be less than or equal to the PSSCH subchannel size. The following configuration parameters in the NR-V2X resource pool configuration information are used to determine the frequency domain resources of the PSCCH and PSSCH resource pools. An example is shown below:

[0066] (1) Subchannel size (sl-Subchannel Size): indicates the number of consecutive PRBs in a subchannel in the resource pool. The value range is {10, 12, 15, 20, 50, 75, 100} PRBs;

[0067] (2) Number of subchannels (sl-Num Subchannel): indicates the number of subchannels included in the resource pool;

[0068] (3) Subchannel start RB index (sl-Start RB-Subchannel): indicates the start PRB index of the first subchannel in the resource pool;

[0069] (4) PRB number (sl-RB-Number): indicates the number of consecutive PRBs included in the resource pool;

[0070] (5) PSCCH frequency domain resource indication (sl-FreqResource PSCCH): indicates the frequency domain resource size of PSCCH, and the value range is {10, 12, 15, 20, 25} PRB.

[0071] When the UE determines the resource pool for PSSCH transmission or reception, the frequency domain resources included in the resource pool are sl-Num Subchannel consecutive subchannels starting with the PRB indicated by sl-Start RB-Subchannel. If the number of PRBs included in the final sl-Num Subchannel consecutive subchannels is less than the number of PRBs indicated by sl-RB-Number, the remaining PRBs cannot be used for PSSCH transmission or reception.

[0072] In NR-V2X, the frequency domain starting position of the first subchannel of PSCCH and its associated PSSCH is aligned. Therefore, the starting position of each PSSCH subchannel is the possible frequency domain starting position of PSCCH. According to the above parameters, the frequency domain range of the resource pool of PSCCH and PSSCH can be determined, as shown in Figure 5.

[0073] In NR-V2X, the PSCCH is used to carry sidelink control information related to resource sensing and can include:

[0074] The priority of the scheduled transmission;

[0075] Frequency domain resource allocation, indicating the number of frequency domain resources of PSSCH in the current time slot scheduled by PSCCH, and the number and starting position of frequency domain resources of up to two retransmission resources reserved;

[0076] Time domain resource allocation, indicating the time domain locations of up to two retransmission resources;

[0077] Reference signal pattern for PSSCH;

[0078] Second level SCI format;

[0079] Second-order SCI rate offset;

[0080] Number of PSSCH DMRS ports;

[0081] Modulation and Coding Scheme (MCS);

[0082] MCS form instructions;

[0083] Number of PSFCH symbols;

[0084] Resource reservation period: reserves resources for another transport block (TB) in the next period. If inter-TB resource reservation is not activated in the resource pool configuration, this information bit field does not exist.

[0085] Reserved bits: 2 to 4 bits. The specific number of bits is configured or pre-configured by the network.

[0086] Since the PSCCH is always transmitted in the same time slot as the scheduled PSSCH, and the starting position of the PRB occupied by the PSCCH is the starting position of the first subchannel of the scheduled PSSCH, the SCI format 1-A does not explicitly indicate the time-frequency domain starting position of the scheduled PSSCH.

[0087] 3. Determination of time domain resources (time slots) in NR SL

[0088] In NR-V2X, the transmission of PSCCH / PSSCH is based on the time slot level, that is, only one PSCCH / PSSCH can be transmitted in one time slot, and the transmission of multiple PSCCH / PSSCH in one time slot through time division multiplexing (TDM) is not supported. PSCCH / PSSCH between different users can be multiplexed in one time slot through frequency division multiplexing (FDM). The time domain resources of PSSCH in NR-V2X are based on the time slot granularity, but unlike the PSSCH in LTE-V2X that occupies all the time domain symbols in a subframe, the PSSCH in NR-V2X can occupy part of the symbols in a time slot. This is mainly because in the LTE system, uplink or downlink transmission is also based on the subframe granularity, so the side transmission is also based on the subframe granularity (special subframes in the time division duplex (TDD) system are not used for side transmission). The NR system uses a flexible time slot structure, that is, a time slot includes both uplink and downlink symbols, which can achieve more flexible scheduling and reduce latency. A subframe of an NR system is shown in Figure 6. The time slot can include downlink (DL) symbols, uplink (UL) symbols, and flexible symbols. The downlink symbol is located at the beginning of the time slot, and the uplink symbol is located at the end of the time slot. The flexible symbols are between the downlink and uplink symbols. The number of various symbols in each time slot is configurable.

[0089] The sidelink transmission system can share a carrier with the cellular system. In this case, sidelink transmission can only use the cellular system's uplink transmission resources. For NR-V2X, if sidelink transmission still needs to occupy all time-domain symbols in a timeslot, the network must configure a timeslot full of uplink symbols for sidelink transmission. This will significantly impact both uplink and downlink data transmission in the NR system and degrade system performance. Therefore, NR-V2X supports using a portion of the time-domain symbols in a timeslot for sidelink transmission, meaning that a portion of the uplink symbols in a timeslot are used for sidelink transmission. Furthermore, considering that sidelink transmission includes AGC and GP symbols, if the number of uplink symbols available for sidelink transmission is small, removing these symbols will leave even fewer symbols available for transmitting valid data, resulting in low resource utilization. Therefore, in NR-V2X, the minimum number of time-domain symbols occupied by sidelink transmission is seven (including GP symbols). When the sidelink transmission system uses a dedicated carrier, there is no issue of sharing transmission resources with other systems, and all symbols in the timeslot can be configured for sidelink transmission.

[0090] As mentioned above, NR-V2X uses the parameters sl-StartSymbol and sl-LengthSymbols to configure the start and length of the time domain symbols used for sidelink transmission in a time slot. The last symbol in the time domain symbols used for sidelink transmission is used as the guard interval (GP), and PSSCH and PSCCH can only use the remaining time domain symbols. However, if PSFCH transmission resources are configured in a time slot, PSSCH and PSCCH cannot occupy the time domain symbols used for PSFCH transmission, as well as the AGC and GP symbols preceding that symbol.

[0091] In the NR-V2X system, the time domain resources of the resource pool are also indicated by a bitmap. Considering the flexible time slot structure in the NR system, the length of the bitmap has been extended to support a bitmap length range of [10:160]. The method of using the bitmap to determine the time slot position belonging to the resource pool within a system frame number (SFN) period is the same as in LTE-V2X, but with the following differences:

[0092] The total number of time slots included in one SFN cycle is 10240×2 μ , where the parameter μ is related to the subcarrier spacing;

[0093] If at least one of the time-domain symbols Y, Y+1, Y+2, …, Y+X-1 included in a time slot is not configured as an uplink symbol by the network's TDD-UL-DL-ConfigCommon signaling, then the time slot cannot be used for sidelink transmission. Where Y and X represent sl-StartSymbol and sl-LengthSymbols, respectively.

[0094] The specific steps include:

[0095] Step 1: Remove the time slots that do not belong to the resource pool within the SFN cycle, including synchronization time slots and time slots that cannot be used for sideline transmission. The remaining time slots are represented as the remaining time slot set, and the remaining time slots are renumbered as

[0096] Where: N S_SSB Indicates the number of synchronization time slots in an SFN cycle; the synchronization time slot is determined according to the synchronization-related configuration parameters, and is related to the period of transmitting the Synchronization Signal Block (SSB) and the number of transmission resources of the SSB configured in the period.

[0097] N nonSLIndicates the number of time slots in an SFN cycle that do not comply with the uplink symbol start point and number configuration: If at least one of the time domain symbols Y, Y+1, Y+2, …, Y+X-1 included in a time slot is not semi-statically configured as an uplink symbol, then the time slot cannot be used for sidelink transmission, where Y and X represent sl-StartSymbol and sl-LengthSymbols, respectively.

[0098] Step 2: Determine the number of reserved time slots and the corresponding time domain positions.

[0099] If the number of time slots in the remaining time slot set cannot be divided by the bitmap length, the number of reserved time slots and the corresponding time domain positions need to be determined. r (0≤r<10240×2 μ -N S_SSB -N nonSL ) satisfies the following conditions, then the time slot is a reserved time slot,

[0100] Where: N reserved =(10240×2 μ -N S_SSB -N nonSL )mod L bitmap , represents the number of reserved time slots, L bitmap Indicates the length of the bitmap, m = 0, ..., N reserved -1.

[0101] Step 3: Remove the reserved time slots from the remaining time slot set. The remaining time slot set is represented as a logical time slot set. The time slots in the time slot set are all time slots that can be used in the resource pool. The time slots in the logical time slot set are renumbered as Among them, T max =10240×2 μ -N S_SSB -N nonSL -N reserved .

[0102] Step 4: Determine the time slots in the logical time slot set that belong to the resource pool according to the bitmap.

[0103] The bitmap in the resource pool configuration information is For a time slot in a logical time slot set (0≤k<(10240×2 μ -N S_SSB -N nonSL -N reserved )), when b is satisfied k′ =1, the time slot belongs to the resource pool, where k′=k mod Lbitmap .

[0104] Step 5: Renumber the time slots belonging to the resource pool determined in step 4 in order i∈{0,1,…,T′ max -1}, where T′ max Indicates the number of time slots included in the resource pool.

[0105] 4. First-order SCI and Second-order SCI in NR SL

[0106] In NR SL, a second-order SCI design is supported. The first-order SCI used to schedule the transmission of PSSCH and / or SL Positioning Reference Signal (PRS) is called SCI format 1-A. The information included is as follows:

[0107] 1. Priority of scheduled data: 3 bits, 000 represents priority value 1, 001 represents priority value 2, and so on.

[0108] 2. Frequency resource assignment: includes a frequency resource indicator value (FRIV).

[0109] If an SCI can indicate the current transmission resource and a reserved resource for retransmission of the current transport block (TB), FRIV is bits, used to indicate the initial sub-channel index of the reserved resource and the number of sub-channels included in the current transmission resource and the one reserved resource.

[0110] If one SCI can indicate the current transmission resource and two reserved resources for the current TB retransmission, the FRIV is bits, used to indicate the initial subchannel index of the two reserved resources and the number of subchannels included in the current transmission resource and the two reserved resources. The number of sub-channels in the current resource pool.

[0111] 3. Time resource assignment: includes a time resource indicator value (TRIV).

[0112] If a PSCCH can indicate a current transmission resource and a reserved resource for retransmission of the current TB, TRIV is 5 bits, which is used to indicate the time slot interval of the reserved resource relative to the current transmission resource.

[0113] If one PSCCH can indicate the current transmission resource and two other reserved resources for retransmission of the current TB, TRIV is 9 bits, used to indicate the time slot interval of the two reserved resources relative to the current transmission resource, and the time slot interval is expressed as the number of time slots belonging to the current resource pool.

[0114] 4. PSSCH reference signal pattern, bits, where N pattern The number of DMRS patterns allowed in the current resource pool.

[0115] 5. Second-level SCI format, 2 bits. 00 represents SCI format 2-A, 01 represents SCI format 2-B, 10 represents SCI format 2-C, and 11 is reserved for future versions.

[0116] 6. Second-order SCI rate offset: 2 bits, 00, 01, 10, and 11 represent the first, second, third, and fourth rate offset values ​​configured by the RRC layer, respectively.

[0117] 7.PSSCH DMRS port number: 1 bit, 0 indicates one port (port 1000), 1 indicates two ports (ports 1000 and 1001)

[0118] 8. Modulation and Coding Scheme (MCS): 5 bits.

[0119] 9. MCS table indication: 0 to 2 bits, depending on the number of MCS tables allowed to be used configured in the resource pool.

[0120] 10. PSFCH symbol number: 1 bit if the PSFCH period is 2 or 4 time slots, otherwise 0 bit.

[0121] 11. Resource Reservation Period: 4 bits; reserves resources for transmission by another TB in the next period. If inter-TB resource reservation is not activated in the resource pool configuration, this information bit field does not exist.

[0122] 12. Reserved bits: 2 to 4 bits. The specific number of bits is configured by the network or pre-configured. If the resource pool is configured to indicate whether a terminal supports receiving resource conflict indication using the least significant bit (LSB) of the reserved bits, the first reserved bit is set to "1" if the terminal supports this function; otherwise, it is set to "0". All other reserved bits are set to "0".

[0123] NR SL defines four second-order SCI formats, namely SCI Format 2-A, SCI Format 2-B, SCI Format 2-C and SCI Format 2-D.

[0124] For example, SCI format 2-A has 35 bits and contains the following information:

[0125] HARQ process – 4 bits;

[0126] New Data Indicator (NDI) – 1 bit;

[0127] Redundancy Version (RV) – 2 bits;

[0128] Source ID – 8 bits;

[0129] Target ID – 16 bits;

[0130] HARQ feedback activation / deactivation – 1 bit;

[0131] Unicast / multicast / broadcast indication – 2 bits; 00 indicates broadcast, 01 indicates multicast communication mode requiring feedback of ACK or NACK, 10 indicates unicast, and 11 indicates multicast communication mode requiring feedback of only NACK;

[0132] CSI feedback request - 1 bit.

[0133] For example, SCI format 2-B has 48 bits and is used only to indicate multicast service transmission. Compared with SCI format 2-A, SCI format 2-B does not include the unicast / multicast / broadcast indication field and the CSI feedback request field, but additionally includes the following two information fields:

[0134] Zone ID – 12 bits;

[0135] Communication distance requirement – ​​4 bits.

[0136] For example, SCI format 2-C is used to carry an inter-UE coordination request or inter-UE coordination information, and the information included in the indication is divided into two parts. The first part is the other bit fields in SCI format 2-A except the "unicast / multicast / broadcast indication" field.

[0137] If the SCI format 2-C carries an inter-UE coordination request, the second part contains the following additional information:

[0138] 1. Trigger signaling or reference resource set indication – 1 bit;

[0139] 2. Priority – 3 bits;

[0140] 3. Number of sub-channels – bits, of which is the number of sub-channels in the current resource pool;

[0141] 4. Resource reservation period: If periodic resource reservation is allowed in the current resource pool, then bits, where N rsv_period The total number of resource reservation cycles configured in the current resource pool;

[0142] If periodic resource reservation is not allowed in the current resource pool, the bit is 0;

[0143] 5. Resource selection window – Bits used to indicate the direct frame number (DFN) and time slot index corresponding to the start and end points of the resource selection window. μ = 0, 1, 2, 3 are subcarrier spacing indices.

[0144] 6. Resource type: If the current resource pool is configured so that the resource type is determined by UE-B, this bit is 1; otherwise, this bit is 0.

[0145] If SCI format 2-C carries inter-UE coordination information, the second part contains the following additional information:

[0146] 1. Trigger signaling or reference resource set indication – 1 bit;

[0147] 2. 2 combinations of {TRIV, FRIV, reserved period} – 2(N TRIV +N FRIV +Y) bits:

[0148] N TRIV =9;

[0149] If periodic resource reservation is allowed in the current resource pool, then bit, otherwise it is 0 bit;

[0150] 3. First resource time domain position – 8 bits, used to indicate the interval of the first resource in the second TRIV relative to the reference time slot, in time slots, with a value range of 0 to 255;

[0151] 4. Reference time slots – 10+ Bit, used to indicate the DFN and time slot index of the reference time slot, μ = 0, 1, 2, 3 is the subcarrier spacing index;

[0152] 5. First resource frequency domain position – 2 Bit used to indicate the frequency domain starting position of the first resource in the first TRIV and the second TRIV.

[0153] For example, SCI format 2-D is used to indicate SL PRS transmission and specifically includes the following information:

[0154] SL PRS Resource ID – bits, where N SL-PRS Indicates the number of SL PRS resources configured / pre-configured in a time slot in the shared resource pool for SL PRS and SL communication.

[0155] SL PRS request – 1 bit, used to trigger the receiving UE to send SL PRS.

[0156] Embedded SCI format – 2 bits, indicating the format of the embedded SCI, as shown in Table 3.

[0157] Embedded SCI Payload – The information contained in the second-level SCI indicated by the “Embedded SCI Format” field.

[0158] The corresponding relationship between the value of the "Embed SCI format" field and the "Embed SCI payload" field is shown in Table 3:

[0159] Table 3 Correspondence between the value of the embedded SCI format field and the embedded SCI payload

[0160] 5. Sidelink transmission in unlicensed spectrum (SL-U)

[0161] When performing sidelink transmission over unlicensed spectrum (SL-U), sidelink transmission needs to meet specific requirements, including the minimum occupied channel bandwidth (OCB) and maximum power spectral density (PSD) requirements. For the OCB requirement, when the UE uses the channel for data transmission, the occupied channel bandwidth must not be less than 80% of the channel bandwidth. For the maximum power spectral density requirement, the power transmitted by the UE per 1MHz cannot exceed 10dBm. In order to meet the OCB and PSD requirements, sidelink transmission over unlicensed spectrum needs to adopt an interlaced resource block (IRB) structure. An IRB includes N discrete RBs in the frequency domain, and a total of M IRBs are included in the frequency band. The RBs included in the mth IRB are {m, M+m, 2M+m, 3M+m, ...}.

[0162] As shown in Figure 7, the system bandwidth consists of 20 RBs, including 5 IRBs (i.e., M = 5). Each IRB consists of 4 RBs (i.e., N = 4). Adjacent RBs in the same IRB have the same frequency domain spacing, i.e., 5 RBs apart. The numbers in the boxes in the figure represent the IRB index. In the SL-U system, if IRB-based resource allocation granularity is adopted, the PSCCH, PSSCH, and PSFCH in the SL-U system also adopt the IRB structure.

[0163] In the unlicensed spectrum, the UE accesses the channel through LBT. LBT uses a granularity of 20 MHz in the frequency domain. Every 20 MHz is called an RB set. A carrier can include multiple RB sets, and there is a guard interval between RB sets, as shown in Figure 8.

[0164] The SL-U system supports a channel occupancy time (COT) sharing mechanism similar to that of NR-U. After a terminal initiates COT through LBT, it can share COT with other terminals. Other terminals use an access channel in the Type2 LBT method to improve resource utilization while also facilitating SL-U terminals to compete for channels. To share COT with other terminals through indication signaling, the following information fields (hereinafter referred to as COT sharing information) need to be provided in the indication signaling:

[0165] Channel Access Priority Class (CAPC): 2 bits. This field is used to indicate the channel access priority of the terminal initiating COT.

[0166] Unicast / multicast / broadcast indication: 2 bits.

[0167] COT shared ID information: 24 bits.

[0168] Remaining COT time length: bits, this field is used to indicate the remaining COT length that can be attempted after receiving the signaling.

[0169] In unlicensed spectrum, UEs must first perform LBT before they can access the channel. However, the time it takes for the UE to complete LBT is uncertain. If a UE is restricted to transmitting from the start of a time slot, it may miss a transmission opportunity if it fails to complete LBT before that time. Therefore, SL-U considers adding a transmission starting point within a time slot, i.e., multi-start transmission. For example, the additional starting point can be the third or fourth OFDM symbol in the time slot.

[0170] As can be seen from the above introduction, NR SL has currently defined four different second-order SCI formats. However, how to indicate COT sharing information in the resource pool that only allows SL communication on the unlicensed spectrum is an unresolved issue.

[0171] FIG9 is a schematic flow chart of a communication method 900 according to an embodiment of the present application. The method can optionally be applied to sideline communication in an unauthorized product area, but is not limited thereto. The method includes at least part of the following contents.

[0172] S910. The first terminal sends first control information, where the first control information includes COT sharing information.

[0173] The first terminal can send first control information containing COT sharing information to other terminals, thereby sharing COT with other terminals, and indicating COT sharing information to the opposite terminal of the side link in the resource pool that only allows SL communication on the unlicensed spectrum.

[0174] In some embodiments, the COT shared information may include at least one of the following:

[0175] Channel access priority;

[0176] Unicast / multicast / broadcast indication;

[0177] COT shared identification (ID) information;

[0178] The remaining COT time length.

[0179] For example, the channel access priority class (CAPC) may be 2 bits, used to indicate the channel access priority of the terminal initiating the COT;

[0180] The unicast / multicast / broadcast indication may be 2 bits, used to indicate whether the transmission mode is unicast, multicast, or broadcast;

[0181] The COT shared ID information may be 24 bits, and is used to indicate identification information of the COT shared information;

[0182] The remaining COT time length can be bits, used to indicate the remaining COT length that can be attempted after receiving the signaling; where μ is the subcarrier spacing index.

[0183] The first terminal may also transmit a first-order SCI, which indicates the second-order SCI. For example, the first-order SCI may indicate whether the second-order SCI includes COT sharing information and / or the format of the scheduled second-order SCI. The first-order SCI may be SCI format 1-A. For example, the first terminal transmits the first-order SCI and first control information to the second terminal, where the first control information is the second-order SCI, which includes COT sharing information. The first-order SCI indicates the second-order SCI. Based on the indication of the received first-order SCI, the second terminal can correctly receive the second-order SCI including the COT sharing information.

[0184] In some implementations, the first control information may include second-order SCI, for example, including at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, SCI format 2-D, and other newly defined second-order SCI formats. This application proposes various implementations for different approaches. The following details:

[0185] Example 1:

[0186] In this implementation, a new second-order SCI format is not sent. Instead, the existing second-order SCI is used to transmit COT shared information. To distinguish between second-order SCIs that include COT shared information and those that do not, the first-order SCI can be used to indicate whether the scheduled second-order SCI includes COT shared information. This first-order SCI can include SCI format 1-A.

[0187] For example, the first-order SCI includes a first information field, and the first information field is used to indicate whether the second-order SCI includes COT shared information.

[0188] The first information field can be a COT shared information indication field. In one example, the first terminal sends a first-order SCI, and the COT shared information indication field and the "second-order SCI format" field in the first-order SCI can determine the format of the scheduled second-order SCI and whether the scheduled second-order SCI contains COT shared information. Among them, the second-order SCI can include at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C and SCI format 2-D. Taking the second-order SCI including SCI format 2-A, SCI format 2-B and SCI format 2-C as an example, the correspondence between the values ​​of the "COT shared information indication" field and the "second-order SCI format" field and the second-order SCI format can be shown in Table 4 below:

[0189] Table 4: Correspondence between the values ​​of the "COT Shared Information Indicator" field and the "Second-level SCI Format" field and the second-level SCI format

[0190] The correspondence relationship shown in Table 4 above is for example only. The embodiment of the present application does not limit the correspondence between the different values ​​of the above two fields and the second-order SCI format. For example, when the value of the COT shared information indication field is 1, it can indicate that the scheduled second-order SCI does not contain COT shared information; when the value of the COT shared information indication field is 0, it can indicate that the scheduled second-order SCI does not contain COT shared information; and so on. Different values ​​of the second-order SCI format represent the scheduled second-order SCI. The COT shared information indication field and the second-order SCI format field can jointly indicate the format of the scheduled second-order SCI and whether the scheduled second-order SCI contains COT shared information.

[0191] In this embodiment, for the SCI format 1-A sent within a resource pool, if the current operation is accompanied by shared spectrum channel access (Shared spectrum channel access), or the current SL BWP is configured with parameters indicating the PSCCH and PSSCH structure (sl-Transmission Structure For PSCCH and PSSCH), then the SCI format 1-A contains a specific information field (or bit field) for indicating whether the second-order SCI scheduled by the SCI format 1-A contains COT shared information. This information field can be called a COT shared information indication field.

[0192] The COT shared information indication field may be a newly added information field in the first-order SCI; or part or all of the bits in the reserved information field in the first-order SCI.

[0193] For example, the COT shared information indication field can be one of the following:

[0194] (1) An additional bit field is added to the existing bit field in SCI format 1-A. The bit field contains 1 bit. When it is set to 1, it indicates that the scheduled second-order SCI contains COT sharing information. When it is set to 0, it indicates that the scheduled second-order SCI does not contain COT sharing information. Alternatively, when the bit field is set to 0, it indicates that the scheduled second-order SCI contains COT sharing information. When it is set to 1, it indicates that the scheduled second-order SCI does not contain COT sharing information.

[0195] (2) A specific bit in the reserved bit field of SCI format 1-A, for example:

[0196] The second to last bit of the reserved bit field (2 nd LSB); or,

[0197] When the UE is allowed to send SCI to indicate whether resource conflict is supported in the resource pool, that is, when the higher-layer parameter sl-IndicationUE-B is configured as "enabled", the second-to-last bit of the reserved bit field is used; otherwise, the first-to-last bit (LSB) of the reserved bit field is used.

[0198] This embodiment can avoid introducing an additional second-order SCI format, which is helpful in reducing the complexity of terminal implementation.

[0199] Example 2:

[0200] In this embodiment, the COT shared information is sent via a new second-order SCI. For example, the COT shared information may be sent using SCI format 2-E. The first terminal sends this second-order SCI, which carries the COT shared information and other information in the second-order SCI. That is, in this embodiment, the format of the second-order SCI containing the COT shared information may include SCI format 2-E.

[0201] For example, the first terminal sends SCI format 2-E, which may include COT shared information and information in SCI format 2-A, or include COT shared information and information in SCI format 2-B.

[0202] In one example, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0203] A third information field, which is used to carry COT shared information and may also be referred to as a COT shared information field;

[0204] Embed SCI format field;

[0205] Embedded SCI load domain;

[0206] Reserved bit field.

[0207] The embedded SCI format field is used to indicate whether the second-level SCI containing the COT shared information is embedded with SCI format 2-A or SCI format 2-B.

[0208] For example, taking the case where the second-order SCI containing COT shared information is SCI format 2-E, the UE indicates the COT shared information and the information in SCI format 2-A, or indicates the COT shared information and the information in 2-B by sending SCI format 2-E. Information in SCI format 2-C is not sent via SCI format 2-E. Specifically, the following information can be sent via SCI format 2-E. It should be noted that this application does not limit the order of the following information:

[0209] (1) Channel Access Priority Class (CAPC): 2 bits in length, used to indicate the channel access priority of the terminal initiating COT.

[0210] (2) Unicast / Multicast / Broadcast Indication: 2 bits long, used to indicate whether the transmission mode is unicast, multicast, or broadcast.

[0211] (3) COT shared ID information: 24 bits in length.

[0212] (4) Remaining COT time length: length is bits, used to indicate the remaining COT length that can be attempted after receiving the signaling; where μ is the subcarrier spacing index.

[0213] (5) Embedded SCI format: The length is 2 bits or 1 bit, indicating the format of the SCI embedded in the second-order SCI containing the COT shared information, as shown in Table 5.

[0214] (6) Embedded SCI Payload: The information contained in the second-level SCI indicated by the "Embedded SCI Format" field.

[0215] (7) Reserved bits. The number of bits is configured or pre-configured by the network. For example, it can be configured to a maximum of 4 or 5 bits to indicate other information. The number of bits in this bit field can be 0 or not exist.

[0216] Among the above information, (1)-(4) are COT shared information and can be carried in the COT shared information field.

[0217] Table 5: Correspondence between the value of the embedded SCI format field and the embedded SCI format

[0218] As shown in Table 5 above, in an embodiment of the present application, the length of the embedded SCI format field in the second-order SCI containing the COT shared information can be 1 bit or 2 bits, which is used to indicate whether the SCI embedded in the second-order SCI containing the COT shared information is SCI format 2-A or SCI format 2-B. The embodiment of the present application does not limit the content represented by the various values ​​of the embedded SCI format field. For example, when the length of the embedded SCI format field is 1 bit, when the value of the embedded SCI format field is 0, it can be indicated that the second-order SCI containing the COT shared information is embedded with SCI format 2-A; when the value of the embedded SCI format field is 1, it can be indicated that the second-order SCI containing the COT shared information is embedded with SCI format 2-B. Alternatively, when the value of the embedded SCI format field is 1, it can be indicated that the second-order SCI containing the COT shared information is embedded with SCI format 2-A; when the value of the embedded SCI format field is 0, it can be indicated that the second-order SCI containing the COT shared information is embedded with SCI format 2-B. When the length of the embedded SCI format field is 2 bits, there are 4 values ​​of the embedded SCI format field, namely 00, 01, 10, and 11. One of the values ​​can be used to indicate that the second-order SCI containing the COT shared information is embedded in the SCI format 2-A, another value can be used to indicate that the second-order SCI containing the COT shared information is embedded in the SCI format 2-B, and the remaining 2 values ​​are reserved values.

[0219] In addition, since the length of SCI format 2-A is shorter than that of SCI format 2-B, the second-order SCI containing COT shared information can contain information of SCI format 2-A and information of SCI format 2-B; in order to ensure that the length of the second-order SCI containing COT shared information is the same in different cases, when the information of SCI format 2-A is included, the information of SCI format 2-A and padding bits can be included in the embedded SCI format field, so as to ensure that the length after padding is the same as the length when SCI format 2-B is included.

[0220] Since a new second-order SCI format is added, namely the second-order SCI containing COT shared information, in order to indicate different second-order SCI formats, the embodiment of the present application can use the first-order SCI to indicate the format of the scheduled second-order SCI. The first-order SCI can be SCI format 1-A.

[0221] For example, the first-order SCI includes a second information field and / or a second-order SCI format field, which indicates the format of the scheduled second-order SCI. The second information field can be an additional indication field, or an additional format indication field. This embodiment proposes multiple methods for indicating the format of the second-order SCI.

[0222] Method 1:

[0223] The first terminal sends a first-order SCI. The COT additional indication field and the "Second-order SCI format" field in the first-order SCI can determine the format of the scheduled second-order SCI. For example, the second-order SCI can include at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, SCI format 2-D, and a second-order SCI containing COT shared information (such as SCI format 2-E).

[0224] According to this method, for SCI format 1-A sent within a resource pool, if the current operation is accompanied by shared spectrum channel access (Shared spectrum channel access), or the current SL BWP is configured with parameters indicating the PSCCH and PSSCH structure (sl-TransmissionStructureForPSCCHandPSSCH), then the SCI format 1-A contains a specific bit field, hereinafter referred to as the "additional format indication" field, the "additional format indication" field and the "second-order SCI format" field jointly indicate the format of the scheduled second-order SCI, and the format of the second-order SCI includes SCI format 2-E. An example of the correspondence between the values ​​of an "additional format indication" field and a "second-order SCI format" field and the second-order SCI format is shown in Table 6 below:

[0225] Table 6: The values ​​of the "Additional format indication" field and the "Second-level SCI format" field and the corresponding relationship between the second-level SCI format

[0226] The correspondence relationship shown in Table 6 above is only an example. The embodiment of the present application does not limit the correspondence relationship between different values ​​and the second-order SCI format.

[0227] The additional indication field (or additional format indication field) may be a newly added information field in the first-order SCI; or part or all of the bits in the reserved information field in the first-order SCI.

[0228] For example, the additional indication field can be one of the following:

[0229] (1) A bit field is added to the existing bit field of SCI format 1-A, and the bit field contains 1 bit.

[0230] (2) A specific bit in the reserved bit field of SCI format 1-A, for example:

[0231] The second to last bit of the reserved bit field (2 ndLSB); or,

[0232] When the UE is allowed to send SCI to indicate whether resource conflict is supported in the resource pool, that is, when the higher-layer parameter sl-IndicationUE-B is configured as "enabled", the second-to-last bit of the reserved bit field is used; otherwise, the first-to-last bit (LSB) of the reserved bit field is used.

[0233] Method 2:

[0234] The first terminal sends a first-order SCI. The "Second-order SCI Format" field in the first-order SCI can determine the format of the scheduled second-order SCI. For example, the second-order SCI can include at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and a second-order SCI containing COT shared information (such as SCI format 2-E).

[0235] According to this method, for SCI format 1-A sent within a resource pool, if the current operation is accompanied by shared spectrum channel access (Shared spectrum channel access), or the parameter indicating the PSCCH and PSSCH structure (sl-TransmissionStructureForPSCCHandPSSCH) is configured on the current SL BWP, the "Second-order SCI format" field in the SCI format 1-A indicates SCI format 2-E. An example of indicating the scheduled second-order SCI format through the "Second-order SCI format" field is shown in Table 7:

[0236] Table 7: Correspondence between the value of the "Second-order SCI format" field and the second-order SCI format

[0237] The correspondence relationship shown in Table 7 above is for example only. The embodiment of the present application does not limit the correspondence relationship between different values ​​of the "second-order SCI format" field and the second-order SCI format.

[0238] This embodiment can reduce the number of second-order SCIs supported by the UE by sending a new second-order SCI to indicate COT sharing information and data transmission information.

[0239] Based on the aforementioned approach, other extended schemes can be used to indicate COT shared information. For example, a new second-order SCI format can be added to carry COT shared information and information in SCI format 2-C, thereby supporting the transmission of COT shared information along with inter-UE coordination requests or inter-UE coordination information. In one example, a new second-order SCI format, such as SCI format 2-F, is defined. This SCI format 2-F contains COT shared information and information in SCI format 2-C.

[0240] Example 3:

[0241] In this embodiment, at least two new second-order SCIs are defined, and the UE sends the new second-order SCIs, which carry the COT shared information and other information in the second-order SCIs. For example, the first terminal sends the second-order SCI containing the COT shared information, and the format of the second-order SCI containing the COT shared information includes SCI format 2-E, SCI format 2-F, or SCI format 2-G.

[0242] For example, in this embodiment, at least two new second-order SCI formats may be defined, such as SCI format 2-E and SCI format 2-F. SCI format 2-E may include COT shared information and information in SCI format 2-A, while SCI format 2-F may include COT shared information and information in SCI format 2-B. The UE indicates the COT shared information and information in SCI format 2-A by sending SCI format 2-E, and indicates the COT shared information and information in SCI format 2-B by sending SCI format 2-F.

[0243] The information in SCI format 2-C is not sent together with the COT shared information. Alternatively, embodiments of the present application define an additional second-order SCI format, such as SCI format 2-G, which includes the COT shared information field and the information in SCI format 2-C. That is, the UE indicates the COT shared information and the information in SCI format 2-C by sending SCI format 2-G.

[0244] In one example, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0245] A third information field, which is used to carry the COT shared information. The third information field may also be referred to as a COT shared information field;

[0246] The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B, or information in SCI format 2-C.

[0247] For example, taking the second-order SCI containing COT shared information as SCI format 2-E, SCI format 2-F, or SCI format 2-G (if defined), the following information can be sent via SCI format 2-E, SCI format 2-F, or SCI format 2-G. It should be noted that this application does not limit the order of the following information:

[0248] (1) Channel Access Priority Class (CAPC): 2 bits in length, used to indicate the channel access priority of the terminal initiating COT.

[0249] (2) Unicast / Multicast / Broadcast Indication: 2 bits long, used to indicate whether the transmission mode is unicast, multicast, or broadcast.

[0250] (3) COT shared ID information: 24 bits in length.

[0251] (4) Remaining COT time length: length is bits, used to indicate the remaining COT length that can be attempted after receiving the signaling; where μ is the subcarrier spacing index.

[0252] (5) Information in SCI format 2-A (included in SCI format 2-E), or information in SCI format 2-B (included in SCI format 2-F), or information in SCI format 2-C (included in SCI format 2-G).

[0253] (6) Reserved bits. The number of bits is configured or pre-configured by the network. For example, it can be configured to a maximum of 4 or 5 bits to indicate other information. The number of bits in this bit field can be 0 or not exist.

[0254] Among the above information, (1)-(4) are COT shared information and can be carried in the COT shared information field.

[0255] In the above example, three second-order SCI formats are defined, namely SCI format 2-E, SCI format 2-F and SCI format 2-G. These three second-order SCIs all contain COT shared information. In addition, the three second-order SCIs also contain SCI format 2-A, SCI format 2-B and SCI format 2-C, respectively. The above content is only an example. The embodiment of the present application does not limit the names of the at least two newly defined second-order SCI formats, nor does it limit the other second-order SCIs contained in the format of each newly defined second-order SCI; for example, the embodiment of the present application can define the newly defined second-order SCI as other formats, and the format of each newly defined second-order SCI can contain any one of SCI format 2-A, SCI format 2-B and SCI format 2-C.

[0256] Since a new second-order SCI format has been added, namely, a second-order SCI containing COT shared information (such as SCI format 2-E, SCI format 2-F, and SCI format 2-G), in order to indicate different second-order SCI formats, embodiments of the present application can use first-order SCI to indicate the format of the scheduled second-order SCI. This first-order SCI can be SCI format 1-A.

[0257] For example, the first-order SCI includes a second information field and / or a second-order SCI format field, which indicates the format of the scheduled second-order SCI. The second information field can be an additional indication field, or an additional format indication field.

[0258] In one example, a first terminal transmits a first-order SCI. The COT additional indication field and the "Second-order SCI format" field in the first-order SCI may determine the format of the scheduled second-order SCI. For example, the second-order SCI may include at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, SCI format 2-D, SCI format 2-E, SCI format 2-F, and SCI format 2-G.

[0259] According to this method, for SCI format 1-A sent within a resource pool, if the current operation is accompanied by shared spectrum channel access (Shared spectrum channel access), or the current SL BWP is configured with parameters indicating the PSCCH and PSSCH structure (sl-Transmission Structure For PSCCH and PSSCH), then the SCI format 1-A contains a specific bit field, hereinafter referred to as the "additional format indication" field, the "additional format indication" field and the "second-order SCI format" field jointly indicate the format of the scheduled second-order SCI, including SCI format 2-E, SCI format 2-F and SCI format 2-G (if defined). An example of the correspondence between the values ​​of an "additional format indication" field and the "second-order SCI format" field and the second-order SCI format is shown in Table 8 below:

[0260] An example of the second-order SCI format scheduled by jointly indicating the "Additional Format Indication" field and the "Second-order SCI Format" field is shown in Table 8:

[0261] Table 8: Correspondence between the values ​​of the "Additional Format Indication" field and the "Second-level SCI Format" field and the second-level SCI format

[0262] The correspondence relationship shown in Table 8 above is only an example. The embodiment of the present application does not limit the correspondence relationship between different values ​​and the second-order SCI format.

[0263] The additional indication field (or additional format indication field) may be a newly added information field in the first-order SCI; or part or all of the bits in the reserved information field in the first-order SCI.

[0264] For example, the additional indication field can be one of the following:

[0265] (1) A bit field is added to the existing bit field of SCI format 1-A, and the bit field contains 1 bit.

[0266] (2) A specific bit in the reserved bit field of SCI format 1-A, for example:

[0267] The second to last bit of the reserved bit field (2 nd LSB); or,

[0268] When the UE is allowed to send SCI to indicate whether resource conflict is supported in the resource pool, that is, when the higher-layer parameter sl-IndicationUE-B is configured as "enabled", the second-to-last bit of the reserved bit field is used; otherwise, the first-to-last bit (LSB) of the reserved bit field is used.

[0269] In this embodiment, since the second-order SCIs are defined differently and include information of SCI format 2-A and information of SCI format 2-B respectively, when the COT shared information and SCI format 2-A are sent together, no padding bits are required.

[0270] Example 4:

[0271] In this embodiment, the COT shared information is sent via the SCI format 2-C, and the resource pool configuration ensures that the SCI format 2-C can carry the COT shared information and the SCI format 2-B.

[0272] In one example, SCI format 2-C includes COT shared information and information in SCI format 2-A; or, SCI format 2-C includes COT shared information and information in SCI format 2-B.

[0273] In this embodiment, COT shared information is sent together with information in SCI format 2-A or SCI format 2-B. For example, when a UE sends COT shared information, it indicates the second-order SCI format to be sent as SCI format 2-C, sets the value of the trigger signaling or reference resource set indication (Providing / Requesting indicator) field in SCI format 2-C to 1 to indicate that SCI format 2-C is trigger signaling, and sets the value of at least one of the last two bits to "1" to distinguish it from SCI format 2-C used to carry inter-UE coordination requests and to indicate whether the information sent together with the COT shared information is in SCI format 2-A or SCI format 2-B. For example, when the last bit is 1, it indicates that the information transmitted along with the COT shared information is in SCI format 2-A, meaning that SCI format 2-C contains both COT shared information and information in SCI format 2-A. When the second-to-last bit is 1, it indicates that the information transmitted along with the COT shared information is in SCI format 2-B, meaning that SCI format 2-C contains both COT shared information and information in SCI format 2-B. The bit field in SCI format 2-C, originally used to indicate inter-UE coordination requests, can now be used to carry COT shared information and other information indicating data transmission.

[0274] In one example, the SCI format 2-C includes at least one of the following information fields:

[0275] The third information field is used to carry COT shared information.

[0276] The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

[0277] In one example, when COT shared information is sent together with information in SCI format 2-A, the position, number of bits, and bit field values ​​of certain specific fields in SCI format 2-C may be determined as follows:

[0278] (1) The first bit field is the HARQ process number, which is 4 bits long and is used to indicate the HARQ process number of the transmitted TB.

[0279] (2) The second bit field is the new data indicator (NDI), which is 1 bit long and is used to indicate whether the TB being sent is a new transmission or a retransmission of a previous TB.

[0280] (3) The third bit field is the redundancy version (RV), which is 2 bits long and is used to indicate the redundancy version number of the transmitted TB.

[0281] (4) The fourth bit field is the source ID (Source ID), which is 8 bits long and is used to indicate the source ID of the sending UE.

[0282] (5) The fifth bit field is the target ID (Destination ID), which is 16 bits long and is used to indicate the ID of the target UE.

[0283] (6) The sixth bit field is the HARQ feedback enabled / disabled indicator, which has a length of 1 bit and is used to indicate whether the currently transmitted TB requires HARQ feedback.

[0284] (7) The seventh bit field is a CSI feedback request (CSI request), which has a length of 1 bit and is used to trigger the receiving UE to feedback CSI.

[0285] (8) The eighth bit field is a trigger signaling or reference resource set indication (Providing / Requesting indicator), which has a length of 1 bit and a value of "1".

[0286] (9) The ninth bit field is a unicast / multicast / broadcast indication field, which is 2 bits long and is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast, or broadcast.

[0287] (10) The tenth bit field is COT sharing information, including at least one of: channel access priority, unicast / multicast / broadcast indication, COT sharing ID information, and remaining COT time length. The specific content of the COT sharing information has been introduced above and will not be repeated here.

[0288] (11) The last bit (LSB) is set to "1".

[0289] In the above content, the positions of the 9th and 10th bit fields can be interchanged. In addition, the 9th bit field may not exist.

[0290] In one example, when COT shared information is sent together with information in SCI format 2-B, the position, number of bits, and bit field values ​​of certain specific fields in SCI format 2-C may be determined as follows:

[0291] (1) The 1st to 6th bit fields are the same as when the COT shared information and the information in SCI format 2-A are transmitted together.

[0292] (2) The 7th bit field is 1 bit in length. The value of this bit field is set to 1 bit in the "Zone ID" or "Communication distance requirement" field to be sent, for example, it is set to the LSB of the "Zone ID" to be sent, or it is set to the LSB of the "Communication distance requirement" to be sent, or it is set to other bits in the "Zone ID" or "Communication distance requirement" field.

[0293] (3) The 8th bit field is a trigger signaling or reference resource set indication (Providing / Requesting indicator), which has a length of 1 bit and a value of "1".

[0294] (4) The 9th bit field is 15 bits long. The value of this bit field is set to the remaining bits of the "Zone ID" or "Communication Distance Requirement" field. For example, if the sum of the lengths of the "Zone ID" and "Communication Distance Requirement" fields in SCI format 2-B is 16 bits, one bit of the 16 bits can be carried in the 7th bit field and the remaining 15 bits can be carried in the 9th bit field to compress the length of the entire SCI format 2-C.

[0295] (5) The 10th bit field is COT sharing information, including at least one of: channel access priority, unicast / multicast / broadcast indication, COT sharing ID information, and remaining COT time length. The specific content of the COT sharing information has been introduced above and will not be repeated here.

[0296] (6) The second to last bit (2 nd LSB), set to "1".

[0297] In this embodiment, the UE does not expect the number of bits in SCI format 2-C to be less than the number of bits required to transmit the COT shared information and the information in SCI format 2-B together. Alternatively, if the number of bits in SCI format 2-C is less than the number of bits required to transmit the COT shared information and the information in SCI format 2-B together, the UE does not transmit the COT shared information and the information in SCI format 2-B simultaneously, that is, it only transmits the COT shared information and the information in SCI format 2-A together.

[0298] This embodiment does not need to add a bit field in the SCI format 1-A or change the configuration of the existing bit field, which helps to simplify the complexity of the UE sending or receiving the first-order SCI.

[0299] The communication method of the embodiment of the present application is a COT information sharing method. Through the method of the embodiment of the present application, the terminal device can send and / or receive side control information.

[0300] The present application also provides a communication method. FIG10 is a schematic flow chart of a communication method 1000 according to an embodiment of the present application. The method includes at least part of the following contents.

[0301] S1010. A second terminal receives first control information, where the first control information includes COT sharing information.

[0302] In some embodiments, the first control information includes a second order SCI.

[0303] In some implementations, the second terminal further receives a first-order SCI, where the first-order SCI is used to indicate whether the second-order SCI includes COT sharing information.

[0304] In some implementations, the first-order SCI includes a first information field, where the first information field is used to indicate whether the second-order SCI includes COT sharing information and / or the format of the scheduled second-order SCI.

[0305] In some implementations, the first information field is a COT shared information indication field.

[0306] In some embodiments, the COT shared information indication field includes:

[0307] The newly added information field in the first-level SCI; or

[0308] Some or all bits in the reserved information field in the first-order SCI.

[0309] In some embodiments, the format of the second-stage SCI includes at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and SCI format 2-D.

[0310] In some implementations, the first-order SCI includes a second information field and / or a second-order SCI format field, where the second information field and / or the second-order SCI format field indicates the format of the scheduled second-order SCI.

[0311] In some implementations, the second information field is an additional indication field.

[0312] In some embodiments, the additional indication field includes:

[0313] The newly added information field in the first-level SCI; or

[0314] Some or all bits in the reserved information field in the first-order SCI.

[0315] In some embodiments, the format of the second-order SCI containing the COT shared information includes SCI format 2-E.

[0316] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0317] A third information field, where the third information field is used to carry the COT shared information;

[0318] Embed SCI format field;

[0319] Embedded SCI load domain;

[0320] Reserved bit field.

[0321] In some implementations, the embedded SCI format field is used to indicate that the second-order SCI containing the COT shared information is embedded in SCI format 2-A or SCI format 2-B.

[0322] In some embodiments, the format of the second-stage SCI containing the COT shared information includes SCI format 2-E, SCI format 2-F, or SCI format 2-G.

[0323] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0324] A third information field, where the third information field is used to carry the COT shared information;

[0325] The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B, or information in SCI format 2-C.

[0326] In some embodiments, the first stage SCI includes SCI format 1-A.

[0327] In some implementations, the format of the second-stage SCI includes SCI format 2-C.

[0328] In some embodiments, the SCI format 2-C includes the COT shared information and the information in the SCI format 2-A; or,

[0329] The SCI format 2-C includes the COT shared information and the information in the SCI format 2-B.

[0330] In some embodiments, the SCI format 2-C includes at least one of the following information fields:

[0331] The third information field is used to carry the COT shared information.

[0332] The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

[0333] In some embodiments, the COT shared information includes at least one of the following:

[0334] Channel access priority;

[0335] Unicast / multicast / broadcast indication;

[0336] COT shared identification ID information;

[0337] The remaining COT time length.

[0338] For a specific example of the execution method 1000 of the second terminal in this embodiment, reference may be made to the relevant description about the second terminal in the above method 900 , which will not be repeated here for the sake of brevity.

[0339] FIG11 is a schematic block diagram of a first terminal 1100 according to an embodiment of the present application. The first terminal 1100 may include:

[0340] The sending unit 1101 is configured to send first control information, where the first control information includes COT sharing information.

[0341] In some embodiments, the first control information includes a second order SCI.

[0342] In some implementations, the sending unit 1101 is further configured to send a first-order SCI, where the first-order SCI is used to indicate whether the second-order SCI includes COT sharing information and / or a format of the scheduled second-order SCI.

[0343] In some implementations, the first-order SCI includes a first information field, where the first information field is used to indicate whether the second-order SCI includes COT shared information.

[0344] In some implementations, the first information field is a COT shared information indication field.

[0345] In some embodiments, the COT shared information indication field includes:

[0346] The newly added information field in the first-level SCI; or

[0347] Some or all bits in the reserved information field in the first-order SCI.

[0348] In some embodiments, the format of the second-stage SCI includes at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and SCI format 2-D.

[0349] In some implementations, the first-order SCI includes a second information field and / or a second-order SCI format field, where the second information field and / or the second-order SCI format field indicates the format of the scheduled second-order SCI.

[0350] In some implementations, the second information field is an additional indication field.

[0351] In some embodiments, the additional indication field includes:

[0352] The newly added information field in the first-level SCI; or

[0353] Some or all bits in the reserved information field in the first-order SCI.

[0354] In some embodiments, the format of the second-order SCI containing the COT shared information includes SCI format 2-E.

[0355] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0356] A third information field, where the third information field is used to carry the COT shared information;

[0357] Embed SCI format field;

[0358] Embedded SCI load domain;

[0359] Reserved bit field.

[0360] In some implementations, the embedded SCI format field is used to indicate that the second-order SCI containing the COT shared information is embedded in SCI format 2-A or SCI format 2-B.

[0361] In some embodiments, the format of the second-stage SCI containing the COT shared information includes at least one of SCI format 2-E, SCI format 2-F, and SCI format 2-G.

[0362] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0363] A third information field, where the third information field is used to carry the COT shared information;

[0364] The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B, or information in SCI format 2-C.

[0365] In some embodiments, the first stage SCI includes SCI format 1-A.

[0366] In some implementations, the format of the second-stage SCI includes SCI format 2-C.

[0367] In some embodiments, the SCI format 2-C includes the COT shared information and the information in the SCI format 2-A; or,

[0368] The SCI format 2-C includes the COT shared information and the information in the SCI format 2-B.

[0369] In some embodiments, the SCI format 2-C includes at least one of the following information fields:

[0370] The third information field is used to carry the COT shared information.

[0371] The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

[0372] In some embodiments, the COT shared information includes at least one of the following:

[0373] Channel access priority;

[0374] Unicast / multicast / broadcast indication;

[0375] COT shared identification ID information;

[0376] The remaining COT time length.

[0377] The first terminal 1100 of the embodiment of the present application can implement the corresponding functions of the first terminal in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first terminal 1100 can be found in the corresponding descriptions in the above-mentioned method embodiments and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first terminal 1100 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0378] FIG12 is a schematic block diagram of a second terminal 1200 according to an embodiment of the present application. The second terminal 1200 may include:

[0379] The receiving unit 1201 is configured to receive first control information, where the first control information includes COT sharing information.

[0380] In some embodiments, the first control information includes a second order SCI.

[0381] In some implementations, the receiving unit 1201 is further configured to receive a first-order SCI, where the first-order SCI is used to indicate whether the second-order SCI includes COT sharing information and / or a format of the scheduled second-order SCI.

[0382] In some implementations, the first-order SCI includes a first information field, where the first information field is used to indicate whether the second-order SCI includes COT shared information.

[0383] In some implementations, the first information field is a COT shared information indication field.

[0384] In some embodiments, the COT shared information indication field includes:

[0385] The newly added information field in the first-level SCI; or

[0386] Some or all bits in the reserved information field in the first-order SCI.

[0387] In some embodiments, the format of the second-stage SCI includes at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and SCI format 2-D.

[0388] In some implementations, the first-order SCI includes a second information field and / or a second-order SCI format field, where the second information field and / or the second-order SCI format field indicates the format of the scheduled second-order SCI.

[0389] In some implementations, the second information field is an additional indication field.

[0390] In some embodiments, the additional indication field includes:

[0391] The newly added information field in the first-level SCI; or

[0392] Some or all bits in the reserved information field in the first-order SCI.

[0393] In some embodiments, the format of the second-order SCI containing the COT shared information includes SCI format 2-E.

[0394] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0395] A third information field, where the third information field is used to carry the COT shared information;

[0396] Embed SCI format field;

[0397] Embedded SCI load domain;

[0398] Reserved bit field.

[0399] In some implementations, the embedded SCI format field is used to indicate that the second-order SCI containing the COT shared information is embedded in SCI format 2-A or SCI format 2-B.

[0400] In some embodiments, the format of the second-stage SCI containing the COT shared information includes at least one of SCI format 2-E, SCI format 2-F, and SCI format 2-G.

[0401] In some embodiments, the second-order SCI containing the COT shared information includes at least one of the following information fields:

[0402] A third information field, where the third information field is used to carry the COT shared information;

[0403] The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B, or information in SCI format 2-C.

[0404] In some embodiments, the first stage SCI includes SCI format 1-A.

[0405] In some implementations, the format of the second-stage SCI includes SCI format 2-C.

[0406] In some embodiments, the SCI format 2-C includes the COT shared information and the information in the SCI format 2-A; or,

[0407] The SCI format 2-C includes the COT shared information and the information in the SCI format 2-B.

[0408] In some embodiments, the SCI format 2-C includes at least one of the following information fields:

[0409] The third information field is used to carry the COT shared information.

[0410] The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

[0411] In some embodiments, the COT shared information includes at least one of the following:

[0412] Channel access priority;

[0413] Unicast / multicast / broadcast indication;

[0414] COT shared identification ID information;

[0415] The remaining COT time length.

[0416] The second terminal 1200 of the embodiment of the present application can implement the corresponding functions of the second terminal in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the second terminal 1200 can be found in the corresponding description in the above method embodiment, and will not be repeated here. It should be noted that the functions described in each module (sub-module, unit or component, etc.) in the second terminal 1200 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0417] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 includes a processor 1310, which can call and run a computer program from a memory to enable the communication device 1300 to implement the method according to the embodiment of the present application.

[0418] In one embodiment, the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0419] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0420] In one embodiment, the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, the transceiver 1330 may send information or data to other devices, or receive information or data sent by other devices.

[0421] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0422] In one embodiment, the communication device 1300 may be the first terminal of the embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the first terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0423] In one embodiment, the communication device 1300 may be the second terminal of the embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the second terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0424] 14 is a schematic structural diagram of a chip 1400 according to an embodiment of the present application. The chip 1400 includes a processor 1410, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0425] In one embodiment, the chip 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to implement the method executed by the first terminal or the second terminal in the embodiment of the present application.

[0426] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0427] In one embodiment, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0428] In one embodiment, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0429] In one embodiment, the chip can be applied to the first terminal in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first terminal in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0430] In one embodiment, the chip can be applied to the second terminal in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the second terminal in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0431] The chip used in the first terminal and the second terminal may be the same chip or different chips.

[0432] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0433] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0434] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0435] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0436] FIG15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. The communication system 1500 includes a first terminal 1510 and a second terminal 1520 .

[0437] The first terminal 1510 is configured to send first control information, where the first control information includes COT sharing information;

[0438] The second terminal 1520 is configured to receive first control information, where the first control information includes COT sharing information.

[0439] The first terminal 1510 can be used to implement the corresponding functions implemented by the first terminal in the above method, and the second terminal 1520 can be used to implement the corresponding functions implemented by the second terminal in the above method. For the sake of brevity, they are not described here in detail.

[0440] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0441] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0442] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0443] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: The first terminal sends first control information, where the first control information includes channel occupancy time COT sharing information.

2. The method according to claim 1, wherein: The first control information includes second order sidelink control information SCI.

3. The method according to claim 2, further comprising: The first terminal sends a first-order SCI, where the first-order SCI is used to indicate whether the second-order SCI includes COT sharing information and / or a format of the scheduled second-order SCI.

4. The method according to claim 3, wherein: The first-order SCI includes a first information field, and the first information field is used to indicate whether the second-order SCI includes COT sharing information.

5. The method according to claim 4, wherein: The first information field is a COT shared information indication field.

6. The method according to claim 5, wherein: The COT shared information indication field includes: The newly added information field in the first-level SCI; or Some or all bits in the reserved information field in the first-order SCI.

7. The method according to any one of claims 4 to 6, wherein: The format of the second-stage SCI includes at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and SCI format 2-D.

8. The method according to claim 3, wherein: The first-order SCI includes a second information field and / or a second-order SCI format field, and the second information field and / or the second-order SCI format field indicates the format of the scheduled second-order SCI.

9. The method according to claim 8, wherein: The second information field is an additional indication field.

10. The method according to claim 9, wherein: The additional indication field includes: The newly added information field in the first-level SCI; or Some or all bits in the reserved information field in the first-order SCI.

11. The method according to any one of claims 8 to 10, wherein: The format of the second-order SCI including COT shared information includes SCI format 2-E.

12. The method according to any one of claims 8 to 11, wherein: The second-order SCI containing COT shared information includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; Embed SCI format field; Embedded in SCI load domain; Reserved bit field.

13. The method according to claim 12, wherein: The embedded SCI format field is used to indicate whether the second-order SCI containing the COT shared information is embedded in SCI format 2-A or SCI format 2-B.

14. The method according to any one of claims 8 to 10, wherein: The format of the second-order SCI including the COT shared information includes at least one of SCI format 2-E, SCI format 2-F, and SCI format 2-G.

15. The method according to any one of claims 8 to 10 and 14, wherein: The second-order SCI containing COT shared information includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B or information in SCI format 2-C.

16. The method according to any one of claims 2 to 15, wherein: The first-stage SCI includes SCI format 1-A.

17. The method according to claim 2, wherein: The format of the second-stage SCI includes SCI format 2-C.

18. The method according to claim 17, wherein: The SCI format 2-C includes the COT shared information and the information in the SCI format 2-A; or, The SCI format 2-C includes the COT shared information and the information in the SCI format 2-B.

19. The method according to claim 18, wherein: The SCI format 2-C includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

20. The method according to any one of claims 1 to 19, wherein: The COT shared information includes at least one of the following: Channel access priority; Unicast / multicast / broadcast indication; COT shared identification ID information; The remaining COT time length.

21. A communication method, comprising: The second terminal receives first control information, where the first control information includes COT sharing information.

22. The method according to claim 21, wherein: The first control information includes second order sidelink control information SCI.

23. The method according to claim 22, further comprising, The second terminal receives a first-order SCI, where the first-order SCI is used to indicate whether the second-order SCI includes COT sharing information and / or a format of the scheduled second-order SCI.

24. The method according to claim 23, wherein: The first-order SCI includes a first information field, and the first information field is used to indicate whether the second-order SCI includes COT sharing information.

25. The method according to claim 24, wherein: The first information field is a COT shared information indication field.

26. The method according to claim 25, wherein: The COT shared information indication field includes: The newly added information field in the first-level SCI; or Some or all bits in the reserved information field in the first-order SCI.

27. The method according to any one of claims 24 to 26, wherein: The format of the second-stage SCI includes at least one of SCI format 2-A, SCI format 2-B, SCI format 2-C, and SCI format 2-D.

28. The method of claim 23, wherein: The first-order SCI includes a second information field and / or a second-order SCI format field, and the second information field and / or the second-order SCI format field indicates the format of the scheduled second-order SCI.

29. The method according to claim 28, wherein: The second information field is an additional indication field.

30. The method of claim 29, wherein: The additional indication field includes: The newly added information field in the first-level SCI; or Some or all bits in the reserved information field in the first-order SCI.

31. The method according to any one of claims 28 to 30, wherein: The format of the second-order SCI including COT shared information includes SCI format 2-E.

32. The method according to any one of claims 28 to 31, wherein: The second-order SCI containing COT shared information includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; Embed SCI format field; Embedded in SCI load domain; Reserved bit field.

33. The method of claim 32, wherein: The embedded SCI format field is used to indicate whether the second-order SCI containing the COT shared information is embedded in SCI format 2-A or SCI format 2-B.

34. The method according to any one of claims 28 to 30, wherein: The format of the second-order SCI including the COT shared information includes SCI format 2-E, SCI format 2-F or SCI format 2-G.

35. The method according to any one of claims 28 to 30 and 24, wherein: The second-order SCI containing COT shared information includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; The fourth information field is used to carry information in SCI format 2-A, information in SCI format 2-B or information in SCI format 2-C.

36. The method according to any one of claims 22 to 35, wherein: The first-stage SCI includes SCI format 1-A.

37. The method of claim 22, wherein: The format of the second-stage SCI includes SCI format 2-C.

38. The method of claim 37, wherein: The SCI format 2-C includes the COT shared information and the information in the SCI format 2-A; or, The SCI format 2-C includes the COT shared information and the information in the SCI format 2-B.

39. The method of claim 38, wherein: The SCI format 2-C includes at least one of the following information fields: A third information domain, the third information domain is used to carry the COT shared information; The fifth information field is used to indicate whether the data scheduled by the second-order SCI is unicast, multicast or broadcast.

40. The method according to any one of claims 21 to 39, wherein: The COT shared information includes at least one of the following: Channel access priority; Unicast / multicast / broadcast indication; COT shared identification ID information; The remaining COT time length.

41. A first terminal, comprising: The sending unit is used to send first control information, where the first control information includes COT sharing information.

42. A second terminal, comprising: The receiving unit is used to receive first control information, where the first control information includes COT sharing information.

43. A terminal device, comprising: A transceiver, a processor and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory so that the terminal device executes the method as described in any one of claims 1 to 40.

44. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 40.

45. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 40.

46. ​​A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 40.

47. A computer program causing a computer to execute the method of any one of claims 1 to 40.

48. A communication system comprising: A first terminal, configured to execute the method according to any one of claims 1 to 20; The second terminal is used to execute the method according to any one of claims 21 to 40.

Images