Lateral communication method and terminal equipment

Abstract

The invention provides a sidewalk communication method and terminal equipment. The method comprises the following steps: if a first condition is met, a first terminal device executes a first operation on an unlicensed spectrum; based on the first operation, the first terminal device sends first side row data; wherein the first condition is related to one or more of channel access, resource occupancy and channel occupancy, and the first operation is related to selection of sidewalk resources and / or generation of the first sidewalk data. The first condition is related to the unlicensed spectrum, and the first operation may be performed if the first condition is satisfied. That is, based on the first condition, performance of the first operation may take into account the effects of the unlicensed spectrum. Therefore, by setting the first condition, the selection of the sidewalk resources and / or the generation process of the sidewalk data are optimized on the unlicensed spectrum.

Description

Sideline communication method and terminal device Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a method and terminal device for sideline communication. Background Art

[0002] During sidelink communications, sidelink resource selection and / or sidelink data packet generation are required. For sidelink communications on unlicensed spectrum, how to implement sidelink resource selection and / or sidelink data packet generation while taking into account the impact of unlicensed spectrum is a pressing issue.

[0003] Summary of the Invention

[0004] The present application provides a method and terminal device for sideline communication. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for sidelink communication is provided, comprising: if a first condition is met, a first terminal device performs a first operation on an unlicensed spectrum; based on the first operation, the first terminal device sends first sidelink data; wherein, the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0006] According to a second aspect, a method for sidelink communication is provided, comprising: a second terminal device receiving first sidelink data sent by a first terminal device; wherein, the first sidelink data is sent based on a first operation performed by the first terminal device, and the first operation is performed by the first terminal device on an unlicensed spectrum when a first condition is met, the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0007] According to a third aspect, a terminal device is provided, comprising: an execution unit for performing a first operation on an unlicensed spectrum if a first condition is met; and a sending unit for sending first sidelink data based on the first operation; wherein the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0008] In a fourth aspect, a terminal device is provided, which is a second terminal device, and the terminal device includes: a receiving unit, used to receive first sidelink data sent by a first terminal device; wherein, the first sidelink data is sent based on a first operation performed by the first terminal device, and the first operation is performed by the first terminal device on an unlicensed spectrum when a first condition is met, and the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0009] In a fifth aspect, a terminal device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect or the second aspect.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device. In another possible design, the system may also include other devices that interact with the terminal device in the solution provided in the embodiment of the present application.

[0011] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a terminal to execute part or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a terminal to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a ninth aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] The first condition is related to unlicensed spectrum, and the first operation can be performed when the first condition is met. That is, based on the first condition, the execution of the first operation can take into account the impact of the unlicensed spectrum. Therefore, by setting the first condition, the present application optimizes the selection of sidelink resources and / or the generation of sidelink data on the unlicensed spectrum. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.

[0016] FIG2 is a diagram illustrating an application scenario of the sideline communication in the first mode.

[0017] FIG3 is a diagram illustrating an application scenario of the sideline communication in the second mode.

[0018] FIG4 is a schematic flowchart of a method for sideline communication provided in an embodiment of the present application.

[0019] FIG5 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

[0020] FIG6 is a schematic structural diagram of another terminal device provided in an embodiment of the present application.

[0021] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solutions in this application will be described below with reference to the accompanying drawings. For ease of understanding, the following first introduces the terms and communication processes involved in this application with reference to Figures 1 to 3.

[0023] Communication System

[0024] Figure 1 is an example diagram of a wireless communication system 100 to which an embodiment of the present application is applicable. The wireless communication system 100 may include one or more communication devices. The one or more communication devices may include, for example, a network device 110 and terminals 121 to 129. The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminals within the coverage area.

[0025] In some implementations, terminal devices can communicate with each other via sidelinks (SLs). Sidelink communication may also be referred to as proximity services (ProSe) communication, unilateral communication, sidelink communication, device-to-device (D2D) communication, or direct link communication. Vehicle-to-everything (V2X) systems can also be implemented using direct terminal-to-terminal communication (i.e., sidelink communication).

[0026] In some implementations, sidelink data may be transmitted between terminal devices via a sidelink. The sidelink data may include data and / or control signaling. In some implementations, the sidelink data may be, for example, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a PSCCH demodulation reference signal (DMRS), a PSSCH DMRS, a PSFCH, a sidelink synchronization signal block (S-SSB), etc., wherein the S-SSB includes a sidelink primary synchronization signal (S-PSS), a sidelink secondary synchronization signal (S-SSS), and a physical sidelink broadcast channel (PSBCH).

[0027] Unlike traditional cellular systems, where data is sent and received via network devices, sideline communication systems (such as the Internet of Vehicles) use direct device-to-device communication. As a result, sideline communication offers higher spectral efficiency and lower transmission latency.

[0028] The following describes several common sidelink communication scenarios using Figure 1. Sidelink communication can be categorized into three scenarios, depending on whether the terminal in the sidelink is within the coverage of the network device. Scenario 1: The terminal conducts sidelink communication within the coverage of the network device. Scenario 2: Some terminals conduct sidelink communication within the coverage of the network device. Scenario 3: The terminal conducts sidelink communication outside the coverage of the network device.

[0029] As shown in Figure 1, in scenario 1, terminals 121-122 can communicate via a sidelink, and terminals 121-122 are all within the coverage of network device 110, or in other words, terminals 121-122 are all within the coverage of the same network device 110. In this scenario, network device 110 can send configuration signaling to terminals 121-122, and accordingly, terminals 121-122 communicate via the sidelink based on the configuration signaling.

[0030] As shown in Figure 1, in scenario 2, terminals 123 and 124 can communicate via a sidelink, and terminal 123 is within the coverage of network device 110, while terminal 124 is outside the coverage of network device 110. In this scenario, terminal 123 receives configuration information from network device 110 and communicates via a sidelink based on the configuration of the configuration signaling. However, for terminal 124, since terminal 124 is outside the coverage of network device 110, it cannot receive the configuration information of network device 110. In this case, terminal 124 can obtain the configuration of the sidelink communication based on the configuration information according to pre-configuration and / or the configuration information sent by terminal 123 within the coverage area, so as to communicate with terminal 123 via the sidelink based on the obtained configuration.

[0031] In some cases, terminal 123 may send the above configuration information to terminal 124 via a physical sidelink broadcast channel (PSBCH) to configure terminal 124 to communicate via the sidelink.

[0032] As shown in Figure 1, in scenario 3, terminals 125-129 are all outside the coverage of network device 110 and cannot communicate with network device 110. In this case, the terminals can configure sidelink communication based on pre-configuration information.

[0033] In some cases, terminals 127-129 located outside the coverage area of ​​the network device can form a communication group, and the terminals 127-129 in the communication group can communicate with each other. In addition, terminal 127 in the communication group can serve as a central control node, also known as a cluster header (CH), and correspondingly, the terminals in other communication groups can be called "group members."

[0034] Terminal 127 as a CH may have one or more of the following functions: responsible for establishing a communication group; joining and leaving group members; coordinating resources, allocating side transmission resources to group members, receiving side transmission feedback information from group members; coordinating resources with other communication groups, etc.

[0035] It should be noted that Figure 1 exemplarily shows a network device and multiple terminal devices. Optionally, the wireless communication system 100 may include multiple network devices and the coverage range of each network device may include other numbers of terminal devices. This embodiment of the present application does not limit this.

[0036] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0037] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0038] The terminal in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal device, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity that provides side data between terminal devices in V2X or D2D. For example, a cellular phone and a car communicate with each other using side data. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0039] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device (D2D), V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network device.

[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0041] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0042] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0043] Sideline communication mode

[0044] Certain standards or protocols (such as the 3rd Generation Partnership Project (3GPP)) define two sideline communication modes (or transmission modes): a first mode (mode-1) and a second mode (mode-2).

[0045] In the first mode, the resources of the terminal device (the resources mentioned in this application may also be referred to as transmission resources, such as time-frequency resources) are allocated by the network device. The terminal device may send data on the sidelink according to the resources allocated by the network device. The network device may allocate resources for a single transmission to the terminal device, or may allocate resources for a semi-static transmission to the terminal device. This first mode may be applied to a scenario covered by a network device, such as the scenario shown in FIG2 . In the scenario shown in FIG2 , the terminal device 221 and the terminal device 222 are located within the network coverage of the network device 210. The network device 210 may allocate resources used in the sidelink transmission process to the terminal device 221 and the terminal device 222. As shown in FIG2 , the network device may grant (grant) via a downlink (DL) to allocate resources used in the sidelink transmission process to the terminal device 221 and the terminal device 222, so that the terminal device 221 and the terminal device 222 can communicate on the sidelink (SL). In some embodiments, the first mode may also be referred to as mode A.

[0046] In the second mode, the terminal device can autonomously select one or more resources from the resource pool (RP). Then, the terminal device can perform side transmission based on the selected resources. For example, in the scenario shown in Figure 3, the terminal device 321 is located within the network coverage area. The terminal device 321 can autonomously select resources from the pre-configured resource pool for side transmission. Alternatively, the terminal device 321 can autonomously select one or more resources from the resource pool configured by the network device 310 for side transmission. It should be noted that if the terminal device 321 is outside the network coverage area, the terminal device 321 can also use the second mode for resource selection. In some embodiments, the second mode may also be referred to as mode B.

[0047] 3GPP Research Progress on Sideline Communications

[0048] In 3GPP, studies on sideline communications have been conducted at different stages.

[0049] In 3GPP Releases (Rel) 12 and 13, device-to-device communication targets Proximity-Based Services (ProSe) scenarios, primarily for public safety services. In ProSe, resource pools can be configured for time domain location, for example, discontinuously. This allows devices to transmit and receive data discontinuously on the sidelink, thereby saving power.

[0050] In Rel-14 or Rel-15, V2X systems were studied for vehicle-to-vehicle communication scenarios. V2X primarily targets relatively high-speed vehicle-to-vehicle and vehicle-to-pedestrian communications. In V2X, since the onboard system has a continuous power supply, power efficiency is less of a concern. Data transmission latency is the primary concern, so system design can require continuous transmission and reception on terminal devices.

[0051] In Rel-14, further enhancements to LTE device-to-device (FeD2D) technologies were studied for scenarios where wearable devices access the network through terminal devices, primarily targeting low-speed and low-power access scenarios. In FeD2D, during the preliminary research phase, 3GPP concluded that network equipment could configure the discontinuous reception (DRX) parameters of remote terminals through a relay terminal. However, this topic did not progress to the standardization stage, and the specific details of how DRX is configured have not yet been determined.

[0052] In NR V2X-related research, NR V2X has further expanded to unicast and multicast scenarios based on the LTE V2X broadcast scenario. Similar to LTE V2X, NR V2X will also define the two resource authorization modes mentioned above, the first mode and the second mode. In addition, in NR V2X, the terminal device can be in a mixed mode. In this mixed mode, the terminal device can use the first mode to acquire resources and the second mode to acquire resources at the same time. The above-mentioned resource acquisition can be indicated by sidelink authorization, that is, the sidelink authorization can indicate the time-frequency position of the corresponding PSCCH and PSSCH resources.

[0053] In LTE V2X, hybrid automatic repeat request (HARQ) retransmissions can be initiated by the terminal device. HARQ is based on no feedback. Unlike LTE V2X, NR V2X introduces feedback-based HARQ retransmissions. This feedback-based HARQ retransmission can be applied to both unicast and multicast communications.

[0054] Unlicensed spectrum communications

[0055] Unlicensed spectrum is the spectrum designated by countries and regions for use by radio equipment. This spectrum is generally considered shared spectrum, meaning that as long as communications equipment meets the regulatory requirements set by the country or region for that spectrum, it can use it without having to apply for exclusive spectrum authorization from the country or region's dedicated spectrum management agency. Unlicensed spectrum can also be referred to as shared spectrum, unlicensed spectrum, unlicensed frequency band, or unlicensed frequency band.

[0056] For Uu-based communication, network equipment (e.g., gNB) can operate in dynamic or semi-static channel access modes. In both of these modes, network equipment and terminal devices can apply listen before talk (LBT) before performing transmissions on cells configured with unlicensed spectrum channel access. When LBT is applied, the data transmitter (transmitter) listens or senses the channel to determine whether it is idle or busy. When the channel is sensed to be idle, the data transmitter can perform data transmission.

[0057] After a successful LBT on an unlicensed spectrum channel, the length of time a communication device uses the unlicensed spectrum channel for signal transmission can be represented by the channel occupancy time (COT). To ensure fairness, the duration of a communication device's signal transmission using the unlicensed spectrum channel cannot exceed the maximum channel occupancy time (MCOT) during a transmission.

[0058] The types of channel access processes may include: channel access process type 1 (type 1) and channel access process type 2 (type 2). Channel access process type 1 is a multi-slot channel detection with random backoff based on contention window size adjustment, wherein the corresponding channel access priority class (CAPC) can be selected according to the priority of the service to be transmitted. Channel access process type 2 is a channel access method based on a fixed-length listening time slot. In an embodiment of the present application, the channel access method is also called the LBT method, and the channel access process is also called the LBT process.

[0059] Channel access procedure type 1 is mainly used by communication devices to initiate channel occupation. Channel access procedure type 2 is mainly used by communication devices to share channel occupation.

[0060] Channel access procedure type 2 includes channel access procedure type 2A (type 2A), channel access procedure type 2B (type 2B), and channel access procedure type 2C (type 2C). Type 2A, type 2B, and type 2C are introduced below.

[0061] When a communication device performs channel access in type 2A, the channel detection mode of the communication device is 25 microseconds (μs) channel detection. Specifically, when performing channel access in type 2A, the communication device may perform 25 μs of channel monitoring before starting transmission, and transmit after the channel monitoring is successful (i.e., the channel is idle).

[0062] When the communication device performs channel access in type 2B, the channel detection method of the communication device is 16μs channel detection. Specifically, when performing channel access in type 2B channel access process, the communication device can perform 16μs channel monitoring before the start of transmission, and transmit after the channel monitoring is successful (that is, the channel is idle). The gap size between the starting position of the transmission and the end position of the previous transmission is 16μs, or the gap size between the starting position of the transmission and the end position of the previous transmission is greater than or equal to 16μs and less than 25μs.

[0063] When a communication device accesses a channel using Type 2C, it can transmit after the gap ends without performing channel detection. Specifically, when accessing a channel using Type 2C, the communication device can directly transmit, where the gap between the start position of the transmission and the end position of the previous transmission is less than or equal to 16 μs. The transmission length does not exceed 584 μs.

[0064] When a consistent uplink LBT failure is detected by a terminal device, the terminal device may take the measures specified in the standard TS 38.321 [6] to handle it. This detection is based on each bandwidth part (BWP) and on all uplink transmissions within the BWP. When a consistent uplink LBT failure is detected on a secondary cell (SCell), the terminal device may report this to the corresponding network equipment (e.g., gNB) (master node (MN) for master cell group (MCG) and secondary node (SN) for secondary cell group (SCG)) via a medium access control element (MAC-CE) on a serving cell different from the SCell where the failure was detected. If no resources are available to transmit the MAC-CE, the terminal device may transmit a scheduling request (SR). When a consistent uplink LBT failure is detected on a special cell (SpCell), the terminal device can switch to another uplink (UL) BWP that has random access channel (RACH) resources configured on the cell, initiate RACH, and report the failure through MAC-CE. When multiple UL BWPs are available for exchange, the terminal device can select which one. For the primary secondary cell (PSCell), if a consistent uplink LBT failure is detected on all UL BWPs that have RACH resources configured, the terminal device can declare an SCG radio link failure (RLF) and report the failure to the mobile network (MN) through SCGFailureInformation. For the primary cell (PCell), if an uplink LBT failure is detected on all UL BWPs with configured RACH resources, the terminal device can declare an RLF.

[0065] COT Sharing Mechanism

[0066] After a communication device initiates a COT, it can use the resources within the COT for transmission and can also share the resources with other communication devices for transmission. For example, a first communication device can initiate a shared COT and share the acquired COT with a second communication device. The second communication device can then inherit the COT and use it for data transmission. The second communication device can be referred to as a shared COT communication device (e.g., a shared COT terminal device).

[0067] The principle of COT sharing may include: the CAPC level corresponding to the service transmitted by the second communication device should be no lower than the CAPC level used by the first communication device when acquiring the COT.

[0068] When the first communication device shares resources within the COT with the second communication device, the second communication device may use channel access procedure type 2 for channel access.

[0069] Some communication systems (such as the sidelink over unlicensed spectrum (SL-U) system) support a direct COT sharing mechanism for terminal devices, that is, when a terminal device successfully accesses a type 1 channel and uses the channel for side transmission, the terminal device can share the channel with other terminal devices for side transmission. In other words, shared COT can be supported between terminal devices that establish a PC5RRC connection. For example, terminal device 1 successfully accesses a type 1 channel and sends PSCCH / PSSCH to terminal device 2. Terminal device 1 can share COT with terminal device 2 so that terminal device 2 sends PSFCH to terminal device 1. In this case, terminal device 2 only needs to perform a type 2 channel access process within the shared COT.

[0070] The following uses the SL-U system as an example to illustrate the COT sharing mechanism. It is understandable that the COT sharing mechanism described below can also be applied to other communication systems.

[0071] To ensure that communication devices in the SL-U system can continuously use the channel within the acquired COT, the SL-U frame structure can support a 16us guard period (GP) symbol. In some implementations, the GP length can be reduced by reusing the cyclic prefix extension (CP extension).

[0072] Terminal devices can implement COT sharing by indicating COT sharing information. Shared COT terminal devices can implement COT sharing by inheriting or forwarding COT sharing information. COT information can be carried in physical layer control signaling sidelink control information (SCI). If COT sharing information is carried in SCI, the implementation of COT sharing can take processing time into consideration. Processing time can be the time it takes for a terminal device to receive and decode the COT sharing information carried in the SCI. Furthermore, the relationship between processing time and the minimum listening time specified by regulations can be considered.

[0073] The COT sharing information indicated by the terminal device initiating COT may include one or more of the following information: remaining COT duration information, available subband information (this information can be obtained through the resource indication information carried by SCI), CAPC information and COT sharing identity (ID) information, etc.

[0074] The COT sharing information inherited by the shared COT terminal device may include: remaining COT duration information, available subband information (this information can be obtained through the resource indication information carried by the SCI), CAPC information and COT sharing ID information, etc.

[0075] The COT shared ID information may include at least one or more of the following: target terminal ID, terminal group ID, service identification information, and sidewalk zone identification (SL zone ID).

[0076] The inheritance and forwarding of COT shared information can meet the following processing time conditions: the time length between the end position of the received SCI symbol and the start position of the sent SCI symbol is greater than or equal to the first time length (for example, it can be obtained by T proc,SL-U Indicates), where T proc,SL-U The processing time that needs to be considered for the inheritance and forwarding of COT shared information can be considered.

[0077] When the terminal device receives multiple COT shared information that meets the processing time conditions, solution 1 and / or solution 2 may be considered to select appropriate COT shared information for inheritance and forwarding.

[0078] Solution 1: A terminal device may select and forward the COT shared information with the longest remaining COT length based on the remaining COT lengths among multiple COT shared information. The COT shared information with the longest remaining COT length forwarded by the terminal device may be determined relative to the time at which the terminal device sends the information.

[0079] Solution 2: When the remaining COT lengths determined based on multiple COT sharing information are the same, the terminal device can select to inherit and forward the COT sharing information with the largest CAPC value based on the CAPC values ​​in the multiple COT sharing information.

[0080] It should be noted that the above-mentioned multiple COT shared information can be multiple COT shared information available to the terminal device. In addition to the above scheme, COT information can also be inherited and forwarded based on other information. For example, COT information can be inherited and forwarded based on resource block set (RB set) information in the COT shared information.

[0081] If the COT sharing conditions are met, the terminal device can be allowed to perform COT sharing.

[0082] As an implementation manner, the COT sharing condition may be determined based on the COT sharing ID information. For example, a terminal group may be determined based on the COT sharing ID information, and the COT may be shared between terminal devices in the terminal group.

[0083] As an implementation method, the COT sharing mechanism can also be based on an implicit public group method to determine whether the COT shared by other terminals is valid according to the evaluation results of the responding device terminal. The evaluation criteria for COT sharing of the responding device terminal may include the following criteria: expected COT sharing range / area, channel quality measurement of the responding device terminal. The expected COT sharing range / area can be determined by SL Zone ID or RSRP measurement. The channel quality measurement of the responding device terminal may include, for example, a reference signal received power (RSRP) threshold or a constant bit rate (CBR) related measurement.

[0084] During sidelink communications, sidelink resource selection and / or sidelink data packet generation are required. For sidelink communications on unlicensed spectrum, how to implement sidelink resource selection and / or sidelink data packet generation while taking into account the impact of unlicensed spectrum is a pressing issue.

[0085] Figure 4 is a schematic flow chart of a method for sideline communication provided by an embodiment of the present application. The method shown in Figure 4 can be performed by a first terminal device and a second terminal device. The method shown in Figure 4 can include steps S410 and S420.

[0086] Step S410: If the first condition is met, the first terminal device performs a first operation on the unlicensed spectrum.

[0087] Step S420: Based on the first operation, the first terminal device sends first sidelink data. Correspondingly, the second terminal device can receive the first sidelink data.

[0088] The first condition may be related to one or more of channel access, resource occupancy, and channel occupancy.

[0089] Channel access may include a channel access process for an unlicensed spectrum. That is, the first condition may be related to a channel access process of the first terminal device on the unlicensed spectrum.

[0090] The present application does not limit the type of the channel access process. For example, the type of the channel access process may include type 1 or type 2.

[0091] Channel occupancy may include information related to the Channel Occupancy Trace (COT). In some embodiments, the COT may be a COT initiated and shared by a terminal device other than the first terminal device. For example, a communication device (e.g., a second terminal device) may share its occupied COT with the first terminal device, and the first terminal device may communicate based on the shared COT. Alternatively, the first terminal device may initiate a COT on its own and utilize the COT for communication.

[0092] Resource occupancy may include occupancy of time domain resources and / or frequency domain resources. For example, resource occupancy may be related to the first resource for the first sidelink data. Alternatively, resource occupancy may be related to the occupant of the resource.

[0093] The first operation may be related to the selection of a sidelink resource and / or the first sidelink data sent by the first terminal device. For example, the first operation includes one or more of the following operations: selecting a sidelink resource, selecting a target address before the first terminal device generates the first sidelink data, selecting a logical channel before generating the first sidelink data, and selecting a HARQ process when sending the first sidelink data.

[0094] Channel access, resource occupancy, and channel occupancy are all related to unlicensed spectrum, so the first condition is related to unlicensed spectrum. In this application, the first operation can be performed when the first condition is met. That is, based on the first condition, the execution of the first operation can take into account the impact of the unlicensed spectrum. Therefore, by setting the first condition, this application optimizes the selection of sidelink resources and / or the generation of sidelink data on the unlicensed spectrum.

[0095] In some implementations, the condition for the first terminal device to perform the first operation on the unlicensed spectrum may further include a second condition. The second condition may, for example, include a condition that is unrelated to the unlicensed spectrum. As an implementation, if both the first condition and the second condition are met, the first terminal device may perform the first operation. As another implementation, if the first condition is not met, the first terminal device may perform the first operation if the second condition is met. Taking the example where the first operation includes resource selection, if the first resource does not meet the first condition, resource selection may be performed based on the second condition, that is, if the first resource meets the second condition, the first terminal device may select the first resource to send the first sidelink data. As an implementation, if the first operation is not for the unlicensed spectrum or does not need to meet the COT sharing condition, the first condition may be ignored, and the first operation may be performed if the second condition is met.

[0096] In some embodiments, the first condition can be determined based on an indication from the physical layer of the first terminal device. That is, whether the execution of the first operation requires the satisfaction of some or all of the conditions in the first condition can be determined based on the indication from the physical layer. For example, the indication from the physical layer can be used to indicate the activation of the first condition, i.e., indicating that the prerequisite for performing the first operation includes the satisfaction of the first condition. Alternatively, the indication from the physical layer can be used to indicate which one or more of the first conditions are activated, i.e., indicating which one or more of the first conditions need to be satisfied before the first operation can be performed.

[0097] In some implementations, a media access control (MAC) layer of the first terminal device may provide first information regarding the first sidelink data to the physical layer of the first terminal device. The first information may include information related to the first sidelink data. For example, the first information may include one or more of the following: a source identifier, a destination identifier, and a CAPC value. Based on the first information, the physical layer may implement transmission of the first sidelink data.

[0098] The following describes in detail the setting of the first condition based on different situations of the first operation.

[0099] In some embodiments, the first operation may include sidelink resource selection. The sidelink resource selection process may include: the physical layer of the first terminal device reporting a resource set to the MAC layer, and the MAC layer performing random resource selection based on the premise that a first condition is met. For example, if the first resource meets the first condition, the first terminal device may select the first resource for sidelink transmission.

[0100] In some embodiments, the sidelink resource for the first sidelink data may be a first resource. The first sidelink data may be sidelink data to be selected by the first terminal device. The first resource may be a sidelink resource to be selected. In other words, whether the first resource is selected for sidelink transmission may be determined based on a first condition. The first condition may be related to resource occupancy of a second resource corresponding to the first resource. The time domain location of the second resource may be earlier than the time domain location of the first resource. The sidelink data corresponding to the second resource may be second sidelink data.

[0101] It should be noted that the second resource is a resource used for sideline transmission. In addition, this application does not limit the communication device that occupies the second resource. For example, the second resource may be occupied by the first terminal device. Alternatively, the second resource may be occupied by a terminal device other than the first terminal device.

[0102] Taking the first resource as a resource in time unit N as an example, the second resource may be a resource in time unit N-1 and / or a resource before time unit N-1. N may be an integer greater than or equal to 0. A time unit may include one or more of: a time slot, a second, a microsecond, a symbol, etc.

[0103] When the first condition is related to the resource occupancy of the second resource, the first condition can be determined based on one or more of the following information: the CAPC of the second sideline data; the COT containing the second resource; the occupant of the second resource; the source identifier of the second sideline data; the destination identifier of the second sideline data; and the time interval between the first resource and the second resource. The following provides examples of each of the above information.

[0104] In the case where the first condition is determined based on the CAPC of the second side-line data, the first condition may include: the value of the CAPC of the second side-line data is greater than or equal to the value of the CAPC of the first side-line data. The value of CAPC may be related to the duration of COT, and the larger the value of CAPC, the longer the duration of COT may be. Therefore, the larger the value of the CAPC of the second side-line data, the longer the duration of the COT containing the second side-line resource may be. In the case where the duration of the COT of the second side-line resource can cover the first side-line resource, the first terminal device may utilize the COT to communicate on the first side-line resource. That is, in the case where the first side-line resource satisfies that the value of the CAPC of the second side-line data is greater than or equal to the value of the CAPC of the first side-line data, the first terminal device may select the first side-line resource as the resource for side-line communication.

[0105] If the first condition is determined based on a COT that includes the second resource, the first condition may include: the COT that includes the second resource includes the first resource. If the COT that includes the second resource includes the first resource, the first terminal device may utilize the COT to communicate on the first sideline resource. For example, if the COT is a shared COT and includes the first resource, the COT may be shared with the first terminal device for sideline communication on the first resource. That is, if the COT that includes the second resource includes the first resource, the first terminal device may select the first resource as the resource for sideline communication.

[0106] It should be noted that the COT containing the second resource can be a COT initiated by the first terminal device or a shared COT initiated by another communication device. For example, the second resource can be a resource included in a shared COT initiated by the second terminal device. Alternatively, the second resource can be a resource included in a COT initiated by the first terminal device.

[0107] When the first condition is determined based on the occupant of the second resource, the first condition may include: the occupant of the second resource is a specific communication device. That is, only when the occupant of the second resource is a specific communication device can the first terminal device select the first resource for sidelink communication. It is understood that only when the initiator of the COT containing the second resource is a specific communication device can the first terminal device use the first resource in the COT for communication.

[0108] In some embodiments, the specific communication device may be a first terminal device. The first condition may include: the occupant of the second resource is the first terminal device. If the occupant of the second resource is the first terminal device, the COT containing the second resource may be used by the first terminal device. In other words, the COT initiated by the first terminal device may continue to be used by the first terminal device for sideline communication in resources subsequent to the second resource.

[0109] In the case where the first condition is determined based on the source identifier of the second sideline data, the first condition may include: the source identifier of the second sideline data can match the destination identifier of the first sideline data. In other words, if the second resource is used for sideline communication with the second terminal device, but the first resource is used to send sideline data to the second terminal device, the COT containing the second resource can be used to send the first sideline data to the second terminal device. Alternatively, in the case where the first condition is determined based on the source identifier of the second sideline data, the first condition may include: the source identifier of the second sideline data can match the source identifier of the first sideline data.

[0110] In the case where the first condition is determined based on the destination identifier of the second sideline data, the first condition may include: the destination identifier of the second sideline data can match the source identifier of the first sideline data. In other words, if the second resource is occupied by the second terminal device, but the second resource is used to send data to the first terminal device, the COT containing the second resource can be used by the first terminal device to send the first sideline data.

[0111] In the case where the first condition is determined based on the time interval between the first resource and the second resource, the first condition may include: the time interval between the second resource and the first resource is sufficient for the first terminal device to perform a channel access process of type 1 or type 2. It is understandable that if the second resource does not belong to a certain COT, the first terminal device can actively initiate a COT (for example, perform LBT) and perform side communication. In the case where the time interval between the first resource and the second resource is sufficient to perform the channel access process, the first terminal device can successfully perform the channel access process, realize channel occupancy, and thus transmit the first side data. Therefore, in the case where the time interval between the second resource and the first resource is sufficient for the first terminal device to perform a channel access process (for example, a channel access process of type 1), the first terminal device can select the first resource to transmit the first side data.

[0112] It should be noted that the time interval between the first resource and the second resource may be the interval between the end time of the first resource and the start time of the second resource. Alternatively, the time interval between the first resource and the second resource may be the interval between the start time unit of the first resource and the end time unit of the second resource. Taking the time unit as an OFDM symbol as an example, the time interval may be the number of symbols between the first OFDM symbol of the first resource and the last OFDM symbol of the second resource.

[0113] As described above, the condition for the first terminal device to perform the first operation on the unlicensed spectrum may further include a second condition. In the case where the first operation includes resource selection, the second condition may, for example, be determined based on one or more of the following conditions: the first resource occurs within the SL DRX Active time as specified in clause 5.28.2 of the destination UE selected for indicating to the physical layer the SL DRX Active time above; according to the amount of selected frequency resources; the first resource satisfies the remaining PDB of SL data available in the logical channel(s) allowed on the carrier; ensuring the minimum time gap between any two selected resources in case that PSFCH is configured for this pool of resources; a retransmission resource can be indicated by the time resource assignment of a prior SCI according to clause 8.3.1.1 of TS 38.212[9]).

[0114] In some embodiments, the first operation may include one or more of the selection of a target address before the first terminal device generates the first sideline data, the selection of a logical channel before the first terminal device generates the first sideline data, and the selection of a HARQ process when the first sideline data is sent. In this case, the first condition may be related to the COT sharing condition. That is, if it is determined in the resource selection stage to select the first resource for sideline communication, and the first resource is related to sharing the COT with other communication devices (for example, the first resource belongs to a shared COT), then the first condition may be related to the COT sharing condition, that is, in the COT, the first sideline data transmitted by the first terminal device needs to meet the COT sharing condition.

[0115] In some implementations, the COT sharing condition may be related to the second sideline data corresponding to the second resource. For example, the COT sharing condition may be determined based on one or more of the following information of the second sideline data: destination identifier, source identifier, CAPC value, etc.

[0116] As an implementation method, the COT sharing conditions may include one or more of the following conditions: the source identifier of the first side row data is the destination identifier of the second side row data; the destination identifier of the first side row data is the source identifier of the second side row data; the CAPC value of the first side row data is less than or equal to the CAPC value of the second side row data.

[0117] The following describes possible settings of the first condition for different first operations.

[0118] In some embodiments, when the first operation includes selecting a target address before generating the first side-row data, the first terminal device may select the side-row data that satisfies the COT sharing condition. For example, in the case where the first side-row data satisfies the COT sharing condition, the first terminal device may select the first side-row data transmission. The COT sharing condition may, for example, include one or more of the following conditions: the source identifier of the first side-row data is the destination identifier of the second side-row data, the destination identifier of the first side-row data is the source identifier of the second side-row data. That is, when selecting the target address, if the source identifier of the first side-row data is the destination identifier of the second side-row data and / or the destination identifier of the first side-row data is the source identifier of the second side-row data, the first terminal device may select the first side-row data transmission.

[0119] When selecting a target address before generating the first sideline data, if the first condition is determined based on the source identifier of the second sideline data, the first condition may include: the source identifier of the second sideline data can match the destination identifier of the first sideline data. In other words, if the second resource is used to transmit the second sideline data to the second terminal device, but the first resource is used to transmit data to the second terminal device, the COT containing the second resource can be used to transmit the first sideline data to the second terminal device.

[0120] When selecting a target address before generating the first sideline data, if the first condition is determined based on the destination identifier of the second sideline data, the first condition may include: the destination identifier of the second sideline data can match the source identifier of the first sideline data. In other words, if the second resource is used by the second terminal device to transmit the second sideline data, but the second resource is used to transmit data to the first terminal device, the COT containing the second resource can be used by the first terminal device to transmit the first sideline data.

[0121] The following example uses a first resource as a resource for time unit N, and a second resource as a resource for time unit N-1. The second resource transmits second sidelink data from source identifier A to destination identifier B. When the first resource is a resource that requires COT sharing, the first sidelink data transmitted by the first resource must meet at least one of the following conditions when selecting a destination address: the destination identifier is A and the source identifier is B.

[0122] It should be noted that, in the case where the second operation includes destination address selection, the second condition may be determined based on one or more of the following conditions: SL data is available for transmission; parameter SBj>0, in case there is any logical channel having SBj>0; if parameter sl-configuredGrantType1Allowed is configured and the sideline grant is a Configured Grant Type 1, parameter sl-configuredGrantType1Allowed is set to true; if parameter sl-AllowedCG-List is configured and the sl-AllowedCG-List includes the configured grant index associated to the SL grant); if PSFCH is not configured, sl-HARQ-FeedbackEnabled is set to disabled, (sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI).

[0123] In some embodiments, the first operation includes selecting a logical channel before generating the first sideline data. In this case, the first terminal device may select data that meets a COT sharing condition for transmission. For example, if the first sideline data meets the COT sharing condition, the first terminal device may select the first sideline data for transmission. The COT sharing condition may include, for example, that the CAPC value of the first sideline data is less than or equal to the CAPC value of the second sideline data.

[0124] Again, for example, a first resource is a resource for time unit N, and a second resource is a resource for time unit N-1. The CAPC value of the second sidelink data corresponding to the second resource is X. When the first resource is a resource that needs to meet the COT sharing condition, the CAPC value of the first sidelink data sent on the first resource must be equal to or less than X when selecting a logical channel.

[0125] In the case where the first operation includes selecting a logical channel before generating first sidelink data, the second condition may include one or more of the following conditions: there is sidelink data available for transmission (SL data is available for transmission); if the parameter sl-configuredGrantType1Allowed is configured and the sidelink grant is a configured grant type 1, the parameter sl-configuredGrantType1Allowed is set to true (sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1); if the parameter sl-AllowedCG-List is configured and the sl-AllowedCG-List includes the configured grant index associated to the first resource (sl-AllowedCG-List, if configured, includes the configured grant index associated to the SL grant). And / or, the second condition may include: if PSFCH is configured for the sidelink grant associated with the SCI: if the highest priority logical channel sl-HARQ-FeedbackEnabled is set to satisfied, sl-HARQ-FeedbackEnabled is set to enabled; or sl-HARQ-FeedbackEnabled is set to disabled, if the sl-HARQ-FeedbackEnabled of the highest priority logical channel is set to disabled, sl-HARQ-FeedbackEnabled is set to disabled.(if PSFCH is configured for the sidelink grant associated to the SCI: sl-HARQ-FeedbackEnabled is set to enabled,if sl-HARQ-FeedbackEnabled is set to enabled for the highest priority logical channel satisfying the above conditions; or sl-HARQ-FeedbackEnabled is set to disabled,if sl-HARQ-FeedbackEnabled is set to disabled for the highest priority logical channel satisfying the above conditions.Else, sl-HARQ-FeedbackEnabled is set to disabled.).

[0126] In some embodiments, the first operation may include selecting a HARQ process. When selecting the HARQ process, the first terminal device may select a HARQ process that satisfies the COT sharing condition. For example, when the HARQ process corresponding to the first resource (i.e., the HARQ process when the first side-link data is sent) satisfies the COT sharing condition, the first terminal device may select the HARQ process. The COT sharing condition may, for example, include one or more of the following conditions: the source identifier of the first side-link data is the destination identifier of the second side-link data, the destination identifier of the first side-link data is the source identifier of the second side-link data, and the value of the CAPC of the first side-link data is less than or equal to the value of the CAPC of the second side-link data.

[0127] Again, let's take the example of the first resource being a resource on time unit N and the second resource being a resource on time unit N-1. The second resource sends the second side-line data sent from source identifier A to target identifier B. The CAPC value of the second side-line data corresponding to the second resource is X. When the first resource belongs to a resource that shares a COT, the first side-line data sent on the first resource needs to meet at least one of the following conditions: the target identifier is A, the source identifier is B, and the CAPC value of the first side-line data sent on the first resource needs to be equal to or less than X, then the first terminal device can select the HARQ process corresponding to the first resource. When the first resource meets the COT sharing condition, the first terminal device can select the HARQ process corresponding to the first resource.

[0128] It should be noted that the source identifier and destination identifier mentioned above can be source layer 2ID and destination layer 2ID respectively. For example, the source identifier of the first side data can be source layer 2ID of the first side data, and the destination identifier of the first side data can be destination layer 2ID of the first side data.

[0129] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 4 . The device embodiment of the present application is described in detail below in conjunction with Figures 5 to 7 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0130] 5 is a schematic structural diagram of a terminal device 500 provided in an embodiment of the present application. The terminal device 500 may include an execution unit 510 and a sending unit 520.

[0131] The execution unit 510 is used to perform a first operation on the unlicensed spectrum if a first condition is met; the sending unit 520 is used to send first sidelink data based on the first operation; wherein the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0132] Optionally, the first operation includes one or more of the following operations: selection of sidelink resources; selection of a target address before the first terminal device generates the first sidelink data; selection of a logical channel before the first terminal device generates the first sidelink data; and selection of a hybrid automatic repeat request HARQ process when sending the first sidelink data.

[0133] Optionally, the sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

[0134] Optionally, the side data corresponding to the second resource is the second side data, and the first condition is determined based on one or more of the following information: the channel access priority CAPC of the second side data; the channel occupancy time COT containing the second resource; the occupant of the second resource; the source identifier of the second side data; the destination identifier of the second side data; and the time interval between the first resource and the second resource.

[0135] Optionally, the first condition includes one or more of the following conditions: the CAPC value of the second sideline data is greater than or equal to the CAPC value of the first sideline data; the COT containing the second resource includes the first resource; the occupant of the second resource is the first terminal device; the destination identifier of the second sideline data matches the source ID of the first sideline data; the source identifier of the second sideline data matches the destination identifier of the first sideline data; the time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

[0136] Optionally, if the first operation includes one or more of selection of a target address before the first terminal device generates the first sideline data, selection of a logical channel before the first terminal device generates the first sideline data, and selection of a HARQ process when the first sideline data is sent, then the first condition is related to the COT sharing condition.

[0137] Optionally, the COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

[0138] Optionally, the sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, and the sidelink data corresponding to the second resource is second sidelink data. The COT sharing condition includes one or more of the following conditions: the source identifier of the first sidelink data is the destination identifier of the second sidelink data; the destination identifier of the first sidelink data is the source identifier of the second sidelink data; the CAPC value of the first sidelink data is less than or equal to the CAPC value of the second sidelink data.

[0139] Optionally, the first condition is determined based on an indication of a physical layer of the first terminal device.

[0140] Optionally, the terminal device 500 further includes: a providing unit for the media access control layer of the terminal device to provide first information of the first sidelink data to the physical layer of the terminal device; wherein the first information includes one or more of the following information: source identifier, destination identifier, and CAPC value.

[0141] FIG6 is a schematic structural diagram of a terminal device 600 provided in this application. The terminal device 600 may be a second terminal device and may include a receiving unit 610.

[0142] The receiving unit 610 is used to receive first sidelink data sent by a first terminal device; wherein the first sidelink data is sent based on a first operation performed by the first terminal device, and the first operation is performed by the first terminal device on an unlicensed spectrum when a first condition is met, and the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

[0143] Optionally, the first operation includes one or more of the following operations: selection of sidelink resources; selection of a target address before the first terminal device generates first sidelink data; selection of a logical channel before the first terminal device generates first sidelink data; selection of a hybrid automatic repeat request HARQ process when sending the first sidelink data.

[0144] Optionally, the sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

[0145] Optionally, the side data corresponding to the second resource is the second side data, and the first condition is determined based on one or more of the following information: the channel access priority CAPC of the second side data; the channel occupancy time COT containing the second resource; the occupant of the second resource; the source identifier of the second side data; the destination identifier of the second side data; and the time interval between the first resource and the second resource.

[0146] Optionally, the first condition includes one or more of the following conditions: the CAPC value of the second sideline data is greater than or equal to the CAPC value of the first sideline data; the COT containing the second resource includes the first resource; the occupant of the second resource is the first terminal device; the destination identifier of the second sideline data matches the source ID of the first sideline data; the source identifier of the second sideline data matches the destination identifier of the first sideline data; the time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

[0147] Optionally, if the first operation includes one or more of selection of a target address before the first terminal device generates the first sideline data, selection of a logical channel before the first terminal device generates the first sideline data, and selection of a HARQ process when the first sideline data is sent, then the first condition is related to the COT sharing condition.

[0148] Optionally, the COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

[0149] Optionally, the sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, and the sidelink data corresponding to the second resource is second sidelink data. The COT sharing condition includes one or more of the following conditions: the source identifier of the first sidelink data is the destination identifier of the second sidelink data; the destination identifier of the first sidelink data is the source identifier of the second sidelink data; the CAPC value of the first sidelink data is less than or equal to the CAPC value of the second sidelink data.

[0150] Optionally, the first condition is determined based on an indication of a physical layer of the first terminal device.

[0151] Figure 7 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 7 indicate that the unit or module is optional. The device 700 may be used to implement the method described in the above method embodiment. The device 700 may be a chip, a terminal device, or a network device.

[0152] The device 700 may include one or more processors 710. The processor 710 may support the device 700 to implement the method described in the method embodiment above. The processor 710 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0153] The apparatus 700 may further include one or more memories 720. The memories 720 store programs that can be executed by the processor 710, causing the processor 710 to perform the methods described in the above method embodiments. The memories 720 may be independent of the processor 710 or integrated into the processor 710.

[0154] The apparatus 700 may further include a transceiver 730. The processor 710 may communicate with other devices or chips via the transceiver 730. For example, the processor 710 may transmit and receive data with other devices or chips via the transceiver 730.

[0155] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0156] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0157] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0158] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0159] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0160] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0161] In 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 indication, configuration and configuration, etc.

[0162] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0163] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0164] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0165] In 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.

[0166] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0167] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0168] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0169] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, 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 described in 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 device. 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 one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0170] 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 changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for sideline communication, characterized in that include: If the first condition is met, the first terminal device performs a first operation on the unlicensed spectrum; Based on the first operation, the first terminal device sends first sidelink data; The first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

2. The method according to claim 1, characterized in that The first operation includes one or more of the following operations: Selection of sidetracking resources; selection of a target address before the first terminal device generates first sideline data; Selection of a logical channel before the first terminal device generates first sidelink data; Selection of a hybrid automatic repeat request HARQ process when sending data on the first side.

3. The method according to claim 2, characterized in that The sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

4. The method according to claim 3, characterized in that The sideline data corresponding to the second resource is second sideline data, and the first condition is determined based on one or more of the following information: a channel access priority level CAPC for the second sideline data; A channel occupancy time COT including the second resource; an occupier of the second resource; a source identifier of the second side row data; a destination identifier of the second side row data; The time interval between the first resource and the second resource.

5. The method according to claim 4, characterized in that The first condition includes one or more of the following conditions: The CAPC value of the second side row data is greater than or equal to the CAPC value of the first side row data; The COT including the second resource includes the first resource; The occupant of the second resource is the first terminal device; The destination identifier of the second side data matches the source ID of the first side data; The source identifier of the second side data matches the destination identifier of the first side data; The time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

6. The method according to any one of claims 2 to 5, characterized in that If the first operation includes the The first condition is related to the COT sharing condition if the first condition includes one or more of the selection of the target address before the first terminal device generates the first side line data, the selection of the logical channel before the first terminal device generates the first side line data, and the selection of the HARQ process when the first side line data is sent.

7. The method according to claim 6, characterized in that The COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

8. The method according to claim 7, characterized in that The sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, the sidelink data corresponding to the second resource is second sidelink data, and the COT sharing condition includes one or more of the following conditions: The source identifier of the first side data is used as the destination identifier of the second side data; The destination identifier of the first side data is the source identifier of the second side data; The CAPC value of the first side row data is less than or equal to the CAPC value of the second side row data.

9. The method according to any one of claims 1 to 8, characterized in that The first condition is determined according to an indication of the physical layer of the first terminal device.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: The media access control layer of the first terminal device provides first information of the first sidelink data to the physical layer of the first terminal device; The first information includes one or more of the following information: a source identifier, a destination identifier, and a CAPC value.

11. A method for sideline communication, characterized in that include: The second terminal device receives the first sidelink data sent by the first terminal device; In which, the first sidelink data is sent based on a first operation performed by the first terminal device, and the first operation is performed by the first terminal device on an unlicensed spectrum when a first condition is met, and the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

12. The method according to claim 11, characterized in that The first operation includes one or more of the following operations: Selection of sidetracking resources; selection of a target address before the first terminal device generates first sideline data; Selection of a logical channel before the first terminal device generates first sidelink data; Selection of a hybrid automatic repeat request HARQ process when sending data on the first side.

13. The method according to claim 12, characterized in that The sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

14. The method according to claim 13, characterized in that The sideline data corresponding to the second resource is second sideline data, and the first condition is determined based on one or more of the following information: a channel access priority level CAPC for the second sideline data; A channel occupancy time COT including the second resource; an occupier of the second resource; a source identifier of the second side row data; a destination identifier of the second side row data; The time interval between the first resource and the second resource.

15. The method according to claim 14, characterized in that The first condition includes one or more of the following conditions: The CAPC value of the second side row data is greater than or equal to the CAPC value of the first side row data; The COT including the second resource includes the first resource; The occupant of the second resource is the first terminal device; The destination identifier of the second side data matches the source ID of the first side data; The source identifier of the second side data matches the destination identifier of the first side data; The time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

16. The method according to any one of claims 12 to 15, characterized in that If the first operation includes The first condition is related to the COT sharing condition if the first condition includes one or more of the selection of the target address before the first terminal device generates the first side line data, the selection of the logical channel before the first terminal device generates the first side line data, and the selection of the HARQ process when the first side line data is sent.

17. The method according to claim 16, characterized in that The COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

18. The method according to claim 17, characterized in that The sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, the sidelink data corresponding to the second resource is second sidelink data, and the COT sharing condition includes one or more of the following conditions: The source identifier of the first side data is used as the destination identifier of the second side data; The destination identifier of the first side data is the source identifier of the second side data; The CAPC value of the first side row data is less than or equal to the CAPC value of the second side row data.

19. The method according to any one of claims 11 to 18, characterized in that The first condition is determined according to an indication of the physical layer of the first terminal device.

20. A terminal device, characterized in that: include: an executing unit, configured to perform a first operation on the unlicensed spectrum if a first condition is met; a sending unit, configured to send first sideline data based on the first operation; The first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

21. The terminal device according to claim 20, characterized in that The first operation includes one or more of the following operations: Selection of sidetracking resources; selection of a target address before the first terminal device generates first sideline data; Selection of a logical channel before the first terminal device generates first sidelink data; Selection of a hybrid automatic repeat request HARQ process when sending data on the first side.

22. The terminal device according to claim 21, characterized in that The sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

23. The terminal device according to claim 22, characterized in that The sideline data corresponding to the second resource is second sideline data, and the first condition is determined based on one or more of the following information: a channel access priority level CAPC for the second sideline data; A channel occupancy time COT including the second resource; an occupier of the second resource; a source identifier of the second side row data; a destination identifier of the second side row data; The time interval between the first resource and the second resource.

24. The terminal device according to claim 23, characterized in that The first condition includes one or more of the following conditions: The CAPC value of the second side row data is greater than or equal to the CAPC value of the first side row data; The COT including the second resource includes the first resource; The occupant of the second resource is the first terminal device; The destination identifier of the second side data matches the source ID of the first side data; The source identifier of the second side data matches the destination identifier of the first side data; The time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

25. The terminal device according to any one of claims 21 to 24, characterized in that: If the first operation includes one or more of selection of a target address before the first terminal device generates the first sideline data, selection of a logical channel before the first terminal device generates the first sideline data, and selection of a HARQ process when the first sideline data is sent, then the first condition is related to the COT sharing condition.

26. The terminal device according to claim 25, characterized in that The COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

27. The terminal device according to claim 26, characterized in that The sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, the sidelink data corresponding to the second resource is second sidelink data, and the COT sharing condition includes one or more of the following conditions: The source identifier of the first side data is used as the destination identifier of the second side data; The destination identifier of the first side data is the source identifier of the second side data; The CAPC value of the first side row data is less than or equal to the CAPC value of the second side row data.

28. The terminal device according to any one of claims 20 to 27, characterized in that: The first condition is determined according to an indication of the physical layer of the first terminal device.

29. The terminal device according to any one of claims 20 to 28, characterized in that: The terminal device further includes: A providing unit, configured for a media access control layer of the terminal device to provide first information of the first sidelink data to a physical layer of the terminal device; The first information includes one or more of the following information: a source identifier, a destination identifier, and a CAPC value.

30. A terminal device, characterized in that: The terminal device is a second terminal device, and the terminal device includes: A receiving unit, configured to receive first sidelink data sent by a first terminal device; In which, the first sidelink data is sent based on a first operation performed by the first terminal device, and the first operation is performed by the first terminal device on an unlicensed spectrum when a first condition is met, and the first condition is related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation is related to the selection of sidelink resources and / or the generation of the first sidelink data.

31. The terminal device according to claim 30, characterized in that The first operation includes one or more of the following operations: Selection of sidetracking resources; selection of a target address before the first terminal device generates first sideline data; Selection of a logical channel before the first terminal device generates first sidelink data; Selection of a hybrid automatic repeat request HARQ process when sending data on the first side.

32. The terminal device according to claim 31, characterized in that The sidelink resource for the first sidelink data is a first resource. If the first operation includes the selection of the first resource, the first condition is related to the resource occupancy of a second resource corresponding to the first resource, wherein the second resource is a sidelink resource whose time domain position is earlier than that of the first resource.

33. The terminal device according to claim 32, characterized in that The sideline data corresponding to the second resource is second sideline data, and the first condition is determined based on one or more of the following information: a channel access priority level CAPC for the second sideline data; A channel occupancy time COT including the second resource; an occupier of the second resource; a source identifier of the second side row data; a destination identifier of the second side row data; The time interval between the first resource and the second resource.

34. The terminal device according to claim 33, characterized in that The first condition includes one or more of the following conditions: The CAPC value of the second side row data is greater than or equal to the CAPC value of the first side row data; The COT including the second resource includes the first resource; The occupant of the second resource is the first terminal device; The destination identifier of the second side data matches the source ID of the first side data; The source identifier of the second side data matches the destination identifier of the first side data; The time interval between the second resource and the first resource is sufficient for the first terminal device to perform a type 1 channel access process.

35. The terminal device according to any one of claims 31 to 34, characterized in that: If the first operation includes one or more of selection of a target address before the first terminal device generates the first sideline data, selection of a logical channel before the first terminal device generates the first sideline data, and selection of a HARQ process when the first sideline data is sent, then the first condition is related to the COT sharing condition.

36. The terminal device according to claim 35, characterized in that The COT sharing condition is determined based on one or more of the following information of the first sidelink data: a source identifier, a destination identifier, and a value of CAPC.

37. The terminal device according to claim 36, characterized in that The sidelink resource for the first sidelink data is a first resource, the COT sharing condition is related to a second resource corresponding to the first resource, the second resource is a sidelink resource whose time domain position is earlier than the first resource, the sidelink data corresponding to the second resource is second sidelink data, and the COT sharing condition includes one or more of the following conditions: The source identifier of the first side data is used as the destination identifier of the second side data; The destination identifier of the first side data is the source identifier of the second side data; The CAPC value of the first side row data is less than or equal to the CAPC value of the second side row data.

38. The terminal device according to any one of claims 30 to 37, characterized in that: The first condition is determined according to an indication of the physical layer of the first terminal device.

39. A terminal device, characterized in that: The terminal comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal executes the method according to any one of claims 1 to 19.

40. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 19.

41. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 19.

42. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 19.

43. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 19.

44. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 19.

Images