Method for sidewalk communication and terminal device

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

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and terminal device for side-to-side communication. Background Technology

[0002] During communication on a sidelink, sidelink resource selection and / or sidelink data packet generation are required. How to account for the impact of unlicensed spectrum in sidelink communication while implementing sidelink resource selection and / or sidelink data packet generation is a pressing issue that needs to be addressed. Summary of the Invention

[0003] This application provides a method and terminal device for side-to-side communication. The various aspects covered in this application are described below.

[0004] In a first aspect, a method for sideline communication is provided, comprising: if the first condition is satisfied, a first terminal device performs a first operation on an unlicensed spectrum; based on the first operation, the first terminal device transmits first sideline 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 sideline resources and / or the generation of the first sideline data.

[0005] In a second aspect, a method for side-link communication is provided, comprising: a second terminal device receiving first side-link data sent by a first terminal device; wherein the first side-link data is sent based on a first operation performed by the first terminal device, the first operation being performed by the first terminal device on an unlicensed spectrum under the condition that the first condition is satisfied, the first condition being related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation being related to the selection of side-link resources and / or the generation of the first side-link data.

[0006] Thirdly, 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 transmission unit for transmitting first sideline 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 sideline resources and / or the generation of the first sideline data.

[0007] Fourthly, a terminal device is provided, the terminal device being a second terminal device, the terminal device comprising: a receiving unit, configured to receive first sideline data transmitted by a first terminal device; wherein the first sideline data is transmitted based on a first operation performed by the first terminal device, the first operation being performed by the first terminal device on an unlicensed spectrum under the condition that the first condition is satisfied, the first condition being related to one or more of channel access, resource occupancy, and channel occupancy, and the first operation being related to the selection of sideline resources and / or the generation of the first sideline data.

[0008] Fifthly, a terminal device is provided, including 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 invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first or second aspect.

[0009] Sixthly, embodiments of this application provide a communication system including the aforementioned terminal device. In another possible design, the system may further include other devices that interact with the terminal device as described in the embodiments of this application.

[0010] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a terminal to perform some or all of the steps in the methods described above.

[0011] Eighthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a terminal to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0012] Ninthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0013] The first condition relates to unlicensed spectrum, and the first operation can be performed if the first condition is met. In other words, based on the first condition, the execution of the first operation can take into account the impact of unlicensed spectrum. Therefore, this application optimizes the selection of sideline resources and / or the generation process of sideline data on unlicensed spectrum by setting the first condition. Attached Figure Description

[0014] Figure 1This is an example diagram of a wireless communication system used in an embodiment of this application.

[0015] Figure 2 This is an example diagram of the application scenario for the first mode of side-by-side communication.

[0016] Figure 3 This is an example diagram illustrating the application scenario of the second mode of side-by-side communication.

[0017] Figure 4 This is a schematic flowchart of a method for side-to-side communication provided in an embodiment of this application.

[0018] Figure 5 This is a schematic structural diagram of a terminal device provided in an embodiment of this application.

[0019] Figure 6 This is a schematic structural diagram of another terminal device provided in the embodiments of this application.

[0020] Figure 7 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0021] The technical solution of this application will now be described with reference to the accompanying drawings. For ease of understanding, the following description will first refer to the accompanying drawings. Figures 1 to 3 This application introduces the terminology and communication process involved.

[0022] Communication system

[0023] Figure 1 This is an example diagram of a wireless communication system 100 to which embodiments of this application apply. The wireless communication system 100 may include one or more communication devices. These devices may include, for example, a network device 110 and terminals 121-129. The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area.

[0024] In some implementations, terminal devices can communicate with each other via sidelinks (SL). Sidelink communication is also known as proximity services (ProSe) communication, one-way communication, side-link communication, device-to-device (D2D) communication, and direct-access communication. Vehicle-to-everything (V2X) systems can also be implemented using direct terminal-to-terminal communication (i.e., sidelink communication).

[0025] In some implementations, terminal devices can transmit sidelink data via a sidelink. This sidelink data can include data and / or control signaling. In some implementations, the sidelink data can be, for example, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a PSCCH demodulation reference signal (DMRS), PSSCH DMRS, PSFCH, a sidelink synchronization signal block (S-SSB), etc. 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).

[0026] Unlike traditional cellular systems where communication data is received or transmitted through network devices, side-pass communication systems (such as vehicle-to-everything (V2X) systems use direct communication between terminal devices. Therefore, side-pass communication offers higher spectral efficiency and lower transmission latency.

[0027] The following text combines Figure 1 This section introduces several common sidelink communication scenarios. Sidelink communication can be categorized into three scenarios based on whether the terminals in the sidelink are within the network device's coverage area: Scenario 1: Terminals conduct sidelink communication within the network device's coverage area. Scenario 2: Some terminals conduct sidelink communication within the network device's coverage area. Scenario 3: Terminals conduct sidelink communication outside the network device's coverage area.

[0028] like Figure 1 As shown, in scenario 1, terminals 121 and 122 can communicate via a side link, and all terminals 121 and 122 are within the coverage area of ​​network device 110, or in other words, all terminals 121 and 122 are within the coverage area of ​​the same network device 110. In this scenario, network device 110 can send configuration signaling to terminals 121 and 122, and correspondingly, terminals 121 and 122 communicate via the side link based on the configuration signaling.

[0029] like Figure 1As shown, in scenario 2, terminals 123 and 124 can communicate via the sidelink, with terminal 123 within the coverage area of ​​network device 110 and terminal 124 outside the coverage area of ​​network device 110. In this scenario, terminal 123 receives configuration information from network device 110 and communicates via the sidelink based on the configuration signaling. However, for terminal 124, since it is outside the coverage area of ​​network device 110, it cannot receive the configuration information from network device 110. In this case, terminal 124 can obtain the sidelink communication configuration based on the pre-configuration configuration information 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.

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

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

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

[0033] Terminal 127, acting as a CH, may have one or more of the following functions: establishing communication groups; allowing members to join or leave the group; coordinating resources, allocating side-transmission resources to group members, and receiving side-transmission feedback information from group members; and coordinating resources with other communication groups.

[0034] It should be noted that, Figure 1 An exemplary embodiment shows a network device and multiple terminal devices. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0035] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

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

[0037] The terminal in this application embodiment can 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 equipment, wireless communication equipment, user agent, or user device. The terminal equipment in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as handheld devices with wireless connectivity, vehicle-mounted devices, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a scheduling entity, providing sideline data between terminal devices in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sideline data. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0038] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode 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, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), device-to-device (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0039] 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 depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0040] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

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

[0042] Side-line communication mode

[0043] Some standards or protocols (such as the 3rd generation partnership project (3GPP)) define two modes of side-to-side communication (or transmission modes): mode-1 and mode-2.

[0044] In the first mode, the resources of the terminal device (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 can transmit data on the side link according to the resources allocated by the network device. The network device can allocate resources for a single transmission or resources for semi-static transmission to the terminal device. This first mode can be applied to scenarios with network device coverage, such as... Figure 2 The scene shown. In Figure 2 In the scenario shown, terminal devices 221 and 222 are located within the network coverage area of ​​network device 210. Network device 210 can allocate resources used during side-by-side transmission for terminal devices 221 and 222. Figure 2 As shown, the network device can grant resources used in the sidelink transmission process to terminal device 221 and terminal device 222 through the downlink (DL), so that terminal device 221 and terminal device 222 can communicate on the sidelink (SL). In some embodiments, the first mode can also be referred to as mode A.

[0045] 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 sideline transmission based on the selected resources. For example, in... Figure 3In the scenario shown, terminal device 321 is located within network coverage. Terminal device 321 can autonomously select resources from a pre-configured resource pool for side-pass transmission. Alternatively, terminal device 321 can autonomously select one or more resources from the resource pool configured by network device 310 for side-pass transmission. It should be noted that if terminal device 321 is located outside network coverage, terminal device 321 can also use the second mode for resource selection. In some embodiments, the second mode can also be referred to as mode B.

[0046] 3GPP Research Progress on Side-by-Side Communication

[0047] In 3GPP, research on side-by-side communication has been conducted at different stages.

[0048] In 3GPP release (Rel) 12 or 13, device-to-device communication is designed for proximity-based services (ProSe) scenarios, primarily targeting public safety services. In ProSe, the temporal location of resource pools can be configured, for example, making resource pools discontinuous in the temporal domain. Based on this approach, terminal devices can achieve discontinuous data transmission / reception on the sidelink, thereby saving power.

[0049] In Rel-14 or Rel-15, V2X systems were studied for vehicle-to-vehicle communication scenarios. V2X is mainly aimed at vehicle-to-vehicle and vehicle-to-person communication services that are moving at relatively high speeds. In V2X, since the onboard system has a continuous power supply, power efficiency is not the main problem to be solved, but data transmission latency is the main problem. Therefore, the system design can require the terminal equipment to continuously send and receive data.

[0050] In Rel-14, the further enhancements to LTE device-to-device (FeD2D) technology for LTE DTD was studied for scenarios where wearable devices access the network through terminal devices, primarily targeting low-mobility and low-power access scenarios. In FeD2D, during the pre-research phase, 3GPP concluded that network devices could configure the discontinuous reception (DRX) parameters of remote terminals through a relay terminal. However, this topic did not advance to the standardization stage, so the specific details of how to configure DRX remain unresolved.

[0051] In NR V2X research, NR V2X extends beyond LTE V2X broadcast scenarios to include unicast and multicast scenarios. Similar to LTE V2X, NR V2X also defines two resource granting modes: Mode 1 and Mode 2. Furthermore, in NR V2X, terminal devices can operate in a hybrid mode. In this hybrid mode, the terminal device can acquire resources using both Mode 1 and Mode 2 simultaneously. This resource acquisition can be indicated through sidelink granting, specifically by specifying the time-frequency location of the corresponding PSCCH and PSSCH resources.

[0052] In LTE V2X, Hybrid Automatic Repeat Request (HARQ) retransmissions can be initiated by the terminal device, and HARQ is based on feedbackless retransmission. Unlike LTE V2X, NR V2X introduces feedback-based HARQ retransmissions. This feedback-based HARQ retransmission can be applied to both unicast and multicast communications.

[0053] Unlicensed spectrum communication

[0054] Unlicensed spectrum refers to spectrum allocated by a country or region for use in wireless communication. This spectrum is generally considered a shared spectrum, meaning that communication equipment can use it as long as it meets the regulatory requirements set by the country or region for that spectrum, without needing to apply for a proprietary spectrum license from the country or region's dedicated spectrum management agency. Unlicensed spectrum can also be called shared spectrum, unlicensed spectrum, unlicensed frequency band, or unlicensed frequency band, etc.

[0055] For communication processes based on the Uu interface, network devices (such as gNBs) can operate in dynamic or semi-static channel access modes. In both of these modes, network and terminal devices can apply listen-before-talk (LBT) before transmission on cells configured with unlicensed spectrum channel access. When LBT is applied, the data transmitter listens to 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.

[0056] After a successful LBT (Learning Bypass) on an unlicensed spectrum channel, the duration for which the communication device uses that unlicensed spectrum channel for signal transmission can be represented by the channel occupancy time (COT). To ensure fairness, the duration for which the communication device uses an unlicensed spectrum channel for signal transmission in a single transmission cannot exceed the maximum channel occupancy time (MCOT).

[0057] The channel access procedure can include two types: Channel Access Procedure Type 1 (type 1) and Channel Access Procedure Type 2 (type 2). Channel Access Procedure Type 1 is a multi-slot channel detection method with random backoff based on contention window size adjustment, where the corresponding channel access priority class (CAPC) can be selected according to the priority of the service to be transmitted. Channel Access Procedure Type 2 is a channel access method based on fixed-length listening slots. In this embodiment, the channel access method is also referred to as the LBT method, and the channel access procedure is also referred to as the LBT procedure.

[0058] Channel access procedure type 1 is mainly used for communication devices to initiate channel occupancy. Channel access procedure type 2 is mainly used for communication devices to share channel occupancy.

[0059] Channel access procedure type 2 includes: channel access procedure type 2A, channel access procedure type 2B, and channel access procedure type 2C. Types 2A, 2B, and 2C are described below.

[0060] When a communication device accesses a channel using Type 2A, the channel detection method is a 25-microsecond (μs) channel detection. Specifically, when performing Type 2A channel access, the communication device can perform a 25-μs channel listening before transmission begins, and transmit after successful channel listening (i.e., when the channel is idle).

[0061] When a communication device accesses a channel using Type 2B, the channel detection method is a 16μs channel detection. Specifically, when performing Type 2B channel access, the communication device can perform a 16μs channel listening before transmission begins, and transmit after successful channel listening (i.e., when the channel is idle). The gap between the start position of this transmission and the end position of the previous transmission is 16μs, or the gap between the start position of this transmission and the end position of the previous transmission is greater than or equal to 16μs and less than 25μs.

[0062] When a communication device accesses a channel using Type 2C, it can transmit without performing channel detection after the gap ends. Specifically, in the case of Type 2C channel access, the communication device can directly transmit, wherein 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.

[0063] When a terminal device detects a consistent uplink LBT failure, it can take the measures specified in standard TS 38.321[6]. This detection is based on each bandwidth part (BWP) and on all uplink transmissions within that BWP. When a consistent uplink LBT failure is detected on a secondary cell (SCell), the terminal device can report this to the corresponding network device (e.g., gNB) via the medium access control element (MAC-CE) on a different serving cell than the SCell where the failure was detected (the master node (MN) is used for the master cell group (MCG), and the secondary node (SN) is used for the secondary cell group (SCG)). If no resources are available to transmit the MAC-CE, the terminal device can 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 configured with random access channel (RACH) resources on that cell, initiate RACH, and report the failure via MAC-CE. When multiple UL BWPs are available for switching, the terminal device can select which one to use. For a primary secondary cell (PSCell), if a consistent uplink LBT failure is detected on all UL BWPs configured with RACH resources, the terminal device can declare a radio link failure (RLF) and report the failure to the mobile network (MN) via SCGFailureInformation. For a primary cell (PCell), if an uplink LBT failure is detected on all ULBWPs with configured RACH resources, the terminal device can declare an RLF.

[0064] COT sharing mechanism

[0065] When a communication device initiates a COT (Communication-Operated-Operated-Operated) connection, it can not only use the resources within the COT for transmission, but also share those resources with other communication devices for transmission. For example, a first communication device can initiate a shared COT, sharing the acquired COT with a second communication device. The second communication device can 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., it may include a shared COT terminal device).

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

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

[0068] Some communication systems (such as sidelink over unlicensed spectrum (SL-U) systems) support direct COT sharing between terminal devices. This means that when a terminal device successfully accesses the network via a Type 1 channel and uses the channel for sidelink transmission, it can share the channel with other terminal devices for sidelink transmission. In other words, COT sharing is possible between terminal devices establishing a PC5 RRC connection. For example, terminal device 1 successfully accesses the network via a Type 1 channel and sends PSCCH / PSSCH to terminal device 2. Terminal device 1 can then share its COT with terminal device 2 so that terminal device 2 can send PSFCH to terminal device 1. In this case, terminal device 2 only needs to perform the Type 2 channel access process within this shared COT.

[0069] The COT sharing mechanism will be explained below using the SL-U system as an example. It is understood that the COT sharing mechanism described below can also be applied to other communication systems.

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

[0071] Terminal devices can perform COT sharing by instructing COT sharing information. Terminal devices sharing COT can achieve COT sharing by inheriting or forwarding COT sharing information. COT information can be carried in the sidelink control information (SCI) of the physical layer control signaling. If the COT sharing information is carried in the SCI, the processing time can be considered in the implementation of COT sharing. Processing time can be the time it takes for the 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 stipulated by regulations can be considered.

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

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

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

[0075] The inheritance and forwarding of COT shared information can satisfy 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 (e.g., it can be achieved through T). proc,SL-U (represented by T), where T proc,SL-U The processing time that needs to be considered for the inheritance and forwarding of COT shared information can be taken into account.

[0076] When a terminal device receives multiple COT shared messages that meet the processing time conditions, it can consider Option 1 and / or Option 2 to select the appropriate COT shared message to inherit and forward.

[0077] Option 1: The terminal device can select and inherit the COT shared information with the longest remaining COT length from among multiple COT shared information. The COT shared information with the longest remaining COT length forwarded by the terminal device can be determined relative to the sending time of that terminal device.

[0078] Option 2: When the remaining COT length determined by multiple COT shared information is the same, the terminal device can select to inherit and forward the COT shared information with the largest CAPC value based on the CAPC value among the multiple COT shared information.

[0079] It should be noted that the aforementioned multiple COT shared information can be multiple COT shared information that can be used by the terminal device. In addition to the above scheme, COT information can also be inherited and forwarded based on other information, such as the resource block set (RB set) information in the COT shared information.

[0080] Under the condition of COT sharing, terminal devices can be allowed to perform COT sharing.

[0081] As one implementation method, COT sharing conditions can be determined based on COT sharing ID information. For example, a terminal group can be determined based on COT sharing ID information, and terminal devices within the terminal group can share COT.

[0082] As one implementation, the COT sharing mechanism can also be based on an implicit public group approach, determining the validity of COT sharing by other terminals based on the evaluation results of the responding device terminal. The evaluation criteria for COT sharing by the responding device terminal can include the following criteria: the expected COT sharing range / area and the channel quality measurement of the responding device terminal. The expected COT sharing range / area can be determined through methods such as SL Zone ID or RSRP measurement. Channel quality measurements of the responding device terminal can include, for example, reference signal received power (RSRP) threshold or constant bit rate (CBR) related measurements.

[0083] During communication on a sidelink, sidelink resource selection and / or sidelink data packet generation are required. How to account for the impact of unlicensed spectrum in sidelink communication while implementing sidelink resource selection and / or sidelink data packet generation is a pressing issue that needs to be addressed.

[0084] Figure 4 This is a schematic flowchart of a method for side-to-side communication provided in an embodiment of this application. Figure 4 The method shown can be executed by a first terminal device and a second terminal device. Figure 4 The method shown may include steps S410 and S420.

[0085] In step S410, if the first condition is met, the first terminal device performs the first operation on the unlicensed spectrum.

[0086] In step S420, based on the first operation, the first terminal device sends first sideline data. Correspondingly, the second terminal device can receive the first sideline data.

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

[0088] Channel access can include a channel access procedure for unlicensed spectrum. That is, the first condition can be related to the channel access procedure of the first terminal device on unlicensed spectrum.

[0089] This application does not limit the type of channel access procedure. For example, the type of channel access procedure may include type 1 or type 2.

[0090] Channel occupancy may include information related to the Channel Occupancy Test (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 its own COT and use the COT for communication.

[0091] Resource occupancy can include the occupancy of time-domain resources and / or frequency-domain resources. For example, resource occupancy can be associated with a first resource for the first side row data. Alternatively, resource occupancy can be associated with the occupant of the resource.

[0092] The first operation may be related to the selection of sideline resources and / or the first sideline data transmitted by the first terminal device. For example, the first operation includes one or more of the following operations: selection of sideline resources, selection of a target address before the first terminal generates the first sideline data, selection of a logical channel before generating the first sideline data, and selection of a HARQ process when transmitting the first sideline data.

[0093] Channel access, resource occupancy, and channel usage are all related to unlicensed spectrum; therefore, the first condition is related to unlicensed spectrum. In this application, the first operation can be performed if 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 unlicensed spectrum. Therefore, this application optimizes the selection of sideline resources and / or the generation process of sideline data on unlicensed spectrum by setting the first condition.

[0094] In some implementations, the condition for the first terminal device to perform the first operation on unlicensed spectrum may also include a second condition. The second condition may, for example, include conditions unrelated to the unlicensed spectrum. As one implementation, the first terminal device can perform the first operation if both the first and second conditions are met. As another implementation, if the first condition is not met, the first terminal device can perform the first operation if the second condition is met. Taking resource selection as an example, if the first resource does not meet the first condition, resource selection can be based on the second condition; that is, if the first resource meets the second condition, the first terminal device can select the first resource to send the first sideline data. As another implementation, if the first operation is not for unlicensed spectrum or does not require meeting COT sharing conditions, the first condition can be ignored, and the first operation can be performed if the second condition is met.

[0095] In some embodiments, the first condition can be determined based on instructions from the physical layer of the first terminal device. That is, whether performing the first operation requires satisfying some or all of the conditions in the first condition can be determined by instructions from the physical layer. For example, the physical layer instructions can be used to indicate that the first condition is enabled, i.e., indicating that satisfying the first condition is a prerequisite for performing the first operation. Alternatively, the physical layer instructions can be used to indicate which one or more of the first conditions are enabled, i.e., indicating which one or more of the first conditions need to be satisfied as a prerequisite for performing the first operation.

[0096] In some implementations, the media access control (MAC) layer of the first terminal device can provide the physical layer of the first terminal device with first information about the first sideline data. This first information may include information related to the first sideline data. For example, the first information may include one or more of the following: source identifier, destination identifier, and CAPC value. Based on this first information, the physical layer can transmit the first sideline data.

[0097] The following details the settings for the first condition based on different scenarios of the first operation.

[0098] In some embodiments, the first operation may include sideline resource selection. The process of selecting sideline resources may include: the physical layer of the first terminal device reporting a set of resources to the MAC layer, and the MAC layer performing random resource selection under 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 sideline transmission.

[0099] In some embodiments, the sideline resource for the first sideline data can be a first resource. The first sideline data can be sideline data to be selected by the first terminal device. The first resource can be a sideline resource to be selected. That is, whether to select the first resource for sideline transmission can be determined according to a first condition. The first condition can be related to the resource occupancy of the second resource corresponding to the first resource. The time domain position of the second resource can be earlier than the time domain position of the first resource. The sideline data corresponding to the second resource can be second sideline data.

[0100] It should be noted that the second resource is a resource used for side-channel transmission. Furthermore, 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 also be occupied by other terminal devices besides the first terminal device.

[0101] Taking the first resource as a resource in time unit N as an example, the second resource can be a resource in time unit N-1 and / or a resource prior to time unit N-1. Here, N can be an integer greater than or equal to 0. Time units can include one or more of the following: time slot, second, microsecond, symbol, etc.

[0102] When the first condition relates to the resource occupancy of the second resource, the first condition can be determined based on one or more of the following information: CAPC of the second sideline data; COT containing the second resource; occupant of the second resource; source identifier of the second sideline data; destination identifier of the second sideline data; and time interval between the first resource and the second resource. Examples of the above information are given below.

[0103] When the first condition is determined based on the CAPC of the second sideline data, the first condition may include: the CAPC value of the second sideline data is greater than or equal to the CAPC value of the first sideline data. The CAPC value may be related to the duration of the Call on Transmission (COT); the larger the CAPC value, the longer the COT duration can be. Therefore, the larger the CAPC value of the second sideline data, the longer the COT duration of the second sideline resource can be. If the COT duration of the second sideline resource can cover the first sideline resource, the first terminal device can use the COT to communicate on the first sideline resource. That is, if the first sideline resource satisfies the condition that the CAPC value of the second sideline data is greater than or equal to the CAPC value of the first sideline data, the first terminal device can select the first sideline resource as the resource for sideline communication.

[0104] When 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. When the COT that includes the second resource includes the first resource, the first terminal device can utilize the COT to communicate on the first side-link resource. Taking a shared COT as an example, when the COT includes the first resource, the COT can be shared with the first terminal device for side-link communication on the first resource. That is, when the COT that includes the second resource includes the first resource, the first terminal device can select the first resource as the resource for side-link communication.

[0105] 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 other communication devices. 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.

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

[0107] In some embodiments, the specific communication device may be a first terminal device, and the first condition may include: the first terminal device is the occupant of the second resource. When the first terminal device is the occupant of the second resource, the COT containing the second resource can be used by the first terminal device. That is, the COT initiated by the first terminal device can continue to be used by the first terminal device for side-by-side communication in resources following the second resource.

[0108] When 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. That is, if the second resource is used for sideline communication by the second terminal device, but the first resource is used to send sideline data to the second terminal device, then the COT containing the second resource can be used to send the first sideline data to the second terminal device. Alternatively, when 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.

[0109] When 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. That is, 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, then the COT containing the second resource can be used by the first terminal device to send the first sideline data.

[0110] When 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 type 1 or type 2 channel access procedure. It is understood that if the second resource does not belong to a certain COT (Content Access Controller), the first terminal device can actively initiate a COT (e.g., perform LBT) and perform side-channel communication. Only when the time interval between the first resource and the second resource is sufficient for the channel access procedure can the first terminal device successfully perform the channel access procedure, thereby occupying the channel and transmitting the first side-channel data. Therefore, when the time interval between the second resource and the first resource is sufficient for the first terminal device to perform a channel access procedure (e.g., a type 1 channel access procedure), the first terminal device can choose the first resource to transmit the first side-channel data.

[0111] It should be noted that the time interval between the first resource and the second resource can 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 can be the interval between the start time unit of the first resource and the end time unit of the second resource. Taking OFDM symbols as an example, the time interval can be the number of symbols between the first OFDM symbol of the first resource and the last OFDM symbol of the second resource.

[0112] As explained above, the conditions under which the first terminal device performs the first operation on unlicensed spectrum may also include a second condition. In the case where the first operation includes resource selection, the second condition may 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; it is consistent with 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; it ensures 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] .

[0113] In some embodiments, the first operation may include one or more of the following: selecting a target address before the first terminal device generates the first sideline data, selecting a logical channel before the first terminal device generates the first sideline data, and selecting a HARQ process when transmitting the first sideline data. In this case, the first condition may be related to the COT sharing condition. That is, if it is determined during the resource selection phase that a first resource is selected for sideline communication, and the first resource is related to a shared COT with other communication devices (e.g., the first resource belongs to a shared COT), then the first condition may be related to the COT sharing condition, i.e., in this COT, the first sideline data transmitted by the first terminal device needs to meet the COT sharing condition.

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

[0115] As one implementation method, COT sharing conditions may include one or more of the following conditions: the source identifier of the first side data is 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 data is less than or equal to the CAPC value of the second side data.

[0116] The following sections explain the possible settings for the first condition for different first operations.

[0117] In some embodiments, when selecting a destination address before generating the first sideline data, the first terminal device can select sideline data that satisfies the COT sharing conditions. For example, if the first sideline data satisfies the COT sharing conditions, the first terminal device can select to transmit the first sideline data. The COT sharing conditions may include one or more of the following conditions: the source identifier of the first sideline data is the destination identifier of the second sideline data, or the destination identifier of the first sideline data is the source identifier of the second sideline data. That is, when selecting a destination address, if the source identifier of the first sideline data is the destination identifier of the second sideline data and / or the destination identifier of the first sideline data is the source identifier of the second sideline data, then the first terminal device can select to transmit the first sideline data.

[0118] When selecting the 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. That is, if the second resource is used for the second terminal device to send the second sideline data, but the first resource is used to send data to the second terminal device, then the COT containing the second resource can be used to send the first sideline data to the second terminal device.

[0119] 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. That is, if the second resource is used for the second terminal device to send the second sideline data, but the second resource is used to send data to the first terminal device, then the COT containing the second resource can be used by the first terminal device to send the first sideline data.

[0120] The following explanation uses the example of a resource with time unit N as the first resource and a resource with time unit N-1 as the second resource. The second resource sends second-sideline data from source identifier A to destination identifier B. When the first resource is a resource that needs to meet COT sharing conditions, the first-sideline data sent on the first resource must meet at least one of the following conditions when selecting the destination address: destination identifier is A, and source identifier is B.

[0121] It should be noted that, when 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, if there is any logical channel having parameter SBj > 0; if parameter sl-configuredGrantType1Allowed is configured, and the SL grant is a Configured Grant Type 1, parameter sl-configuredGrantType1Allowed is set to true; if parameter sl-AllowedCG-List is configured, and sl-AllowedCG-List includes the configured grant index associated with the first resource. SLgrant); if PSFCH is not configured, sl-HARQ-FeedbackEnabled is set to disabled.

[0122] In some embodiments, the first operation includes logical channel selection before generating the first sideline data. In this case, the first terminal device can select data that meets the COT sharing conditions for transmission. For example, if the first sideline data meets the COT sharing conditions, the first terminal device can select the first sideline data transmission. The COT sharing conditions 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.

[0123] Let's take the example of the first resource being the resource on time unit N, and the second resource being the resource on time unit N-1. The CAPC value of the second sideline data corresponding to the second resource is X. When the first resource is a resource that needs to meet the COT sharing conditions, the CAPC value of the first sideline data transmitted on the first resource must be equal to or less than X when selecting the logical channel.

[0124] In the case of selecting a logical channel before the first operation includes generating the first sideline data, the second condition may include one or more of the following conditions: sideline data is available for transmission; sl-configuredGrantType1Allowed is set to true if the sideline grant is a Configured Grant Type 1; sl-AllowedCG-List is configured if the parameter is configured and includes the configured grant index associated with the first resource. And / or, the second condition may include: if PSFCH is configured for the sideline authorization associated with SCI: if the highest priority logical channel sl-HARQ-FeedbackEnabled is set to enabled, sl-HARQ-FeedbackEnabled is set to enabled; or sl-HARQ-FeedbackEnabled is set to disabled, if the highest priority logical channel sl-HARQ-FeedbackEnabled 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 toenabled for the highest priority logical channel satisfying the aboveconditions; or sl-HARQ-FeedbackEnabled is set to disabled,if sl-HARQ-FeedbackEnabled is set to disabled for the highest priority logical channelsatisfying the above conditions.Else, sl-HARQ-FeedbackEnabled is set todisabled.).

[0125] In some embodiments, the first operation may include selecting a HARQ process. When selecting a HARQ process, the first terminal device may select a HARQ process that satisfies the COT sharing conditions. For example, if the HARQ process corresponding to the first resource (i.e., the HARQ process during the transmission of the first sideline data) satisfies the COT sharing conditions, the first terminal device may select that HARQ process. The COT sharing conditions may include, for example, one or more of the following conditions: the source identifier of the first sideline data is the destination identifier of the second sideline data; the destination identifier of the first sideline data is the source identifier of the second sideline data; or the CAPC value of the first sideline data is less than or equal to the CAPC value of the second sideline data.

[0126] 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 transmits second-sideline data from source identifier A to target identifier B. The CAPC value of the second-sideline data corresponding to the second resource is X. When the first resource belongs to a shared COT resource, the first-sideline data transmitted on the first resource must 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-sideline data transmitted on the first resource must 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 conditions, the first terminal device can select the HARQ process corresponding to the first resource.

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

[0128] The above text combined Figures 1 to 4 The method embodiments of this application are described in detail below, in conjunction with... Figures 5 to 7 The present application provides a detailed description of the apparatus embodiments. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0129] Figure 5 This is a schematic structural diagram of a terminal device 500 provided in an embodiment of this application. The terminal device 500 may include an execution unit 510 and a sending unit 520.

[0130] The execution unit 510 is configured to perform a first operation on an unlicensed spectrum if a first condition is met; the transmission unit 520 is configured to transmit first sideline 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 sideline resources and / or the generation of the first sideline data.

[0131] Optionally, the first operation includes one or more of the following operations: selection of sideline resources; selection of the target address before the first terminal device generates the first sideline data; selection of the logical channel before the first terminal device generates the first sideline data; and selection of the Hybrid Automatic Repeat Request (HARQ) process when the first sideline data is transmitted.

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

[0133] Optionally, the sideline data corresponding to the second resource is the second sideline data, and the first condition is determined based on one or more of the following information: the channel access priority (CAPC) of the second sideline data; the channel occupancy time (COT) of 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.

[0134] 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 user 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; and 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 procedure.

[0135] Optionally, if the first operation includes one or more of the following: 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 transmitted, then the first condition is related to the COT sharing condition.

[0136] Optionally, the COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

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

[0138] Optionally, the first condition is determined according to the instructions of the physical layer of the first terminal device.

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

[0140] Figure 6 This is a schematic structural diagram of a terminal device 600 provided in this application. The terminal device 600 can be a second terminal device. The terminal device 600 may include a receiving unit 610.

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

[0142] Optionally, the first operation includes one or more of the following operations: selection of sideline resources; selection of the target address before the first terminal device generates the first sideline data; selection of the logical channel before the first terminal device generates the first sideline data; and selection of the Hybrid Automatic Repeat Request (HARQ) process when the first sideline data is transmitted.

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

[0144] Optionally, the sideline data corresponding to the second resource is the second sideline data, and the first condition is determined based on one or more of the following information: the channel access priority (CAPC) of the second sideline data; the channel occupancy time (COT) of 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.

[0145] 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 user 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; and 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 procedure.

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

[0147] Optionally, the COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

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

[0149] Optionally, the first condition is determined according to the instructions of the physical layer of the first terminal device.

[0150] Figure 7 This is a schematic structural diagram of a communication device according to an embodiment of this application. Figure 7 The dashed lines indicate that the unit or module is optional. The device 700 can be used to implement the methods described in the above method embodiments. The device 700 can be a chip, a terminal device, or a network device.

[0151] The apparatus 700 may include one or more processors 710. The processor 710 may support the apparatus 700 in implementing the methods described in the preceding method embodiments. 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 other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0152] The apparatus 700 may also include one or more memories 720. The memories 720 store a program that can be executed by the processor 710, causing the processor 710 to perform the methods described in the preceding method embodiments. The memories 720 may be independent of the processor 710 or integrated within the processor 710.

[0153] The device 700 may also include a transceiver 730. The processor 710 can communicate with other devices or chips via the transceiver 730. For example, the processor 710 can send and receive data with other devices or chips via the transceiver 730.

[0154] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0155] This 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 this application embodiment, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0156] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0157] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0158] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

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

[0160] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0161] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0162] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0163] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0164] In the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0165] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0166] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0167] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0168] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0169] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for side-to-side communication, characterized in that, include: If the first condition is met, the first terminal device performs the first operation on the unlicensed spectrum; Based on the first operation, the first terminal device sends the first side data; The first condition is related to channel occupancy, and the first operation is related to the generation of the first side data.

2. The method according to claim 1, characterized in that, The first operation includes the following operations: The selection of the target address before the first terminal device generates the first side data; The selection of logical channels before the first terminal device generates the first side data.

3. The method according to claim 2, characterized in that, The first condition is related to the COT sharing condition.

4. The method according to claim 3, characterized in that, The COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

5. The method according to claim 4, characterized in that, The sideline resource for the first sideline data is a first resource. The COT sharing conditions are related to a second resource corresponding to the first resource. The second resource is a sideline resource whose time domain location is earlier than the first resource. The sideline data corresponding to the second resource is second sideline data. The COT sharing conditions 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 data is less than or equal to the CAPC value of the second side data.

6. The method according to any one of claims 1-5, characterized in that, The first condition is determined according to the instructions of the physical layer of the first terminal device.

7. A method for side-to-side communication, characterized in that, include: The second terminal device receives the first side data sent by the first terminal device; The first side data is transmitted based on a first operation performed by the first terminal device. 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 channel occupancy, and the first operation is related to the generation of the first side data.

8. The method according to claim 7, characterized in that, The first operation includes the following operations: The selection of the target address before the first terminal device generates the first side data; The selection of logical channels before the first terminal device generates the first side data.

9. The method according to claim 8, characterized in that, The first condition is related to the COT sharing condition.

10. The method according to claim 9, characterized in that, The COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

11. The method according to claim 10, characterized in that, The sideline resource for the first sideline data is a first resource. The COT sharing conditions are related to a second resource corresponding to the first resource. The second resource is a sideline resource whose time domain location is earlier than the first resource. The sideline data corresponding to the second resource is second sideline data. The COT sharing conditions 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 data is less than or equal to the CAPC value of the second side data.

12. The method according to any one of claims 7-11, characterized in that, The first condition is determined according to the instructions of the physical layer of the first terminal device.

13. A terminal device, characterized in that, include: An execution unit is configured to perform a first operation on an unlicensed spectrum if a first condition is met. The sending unit is configured to send first sideline data based on the first operation; The first condition is related to channel occupancy, and the first operation is related to the generation of the first side data.

14. The terminal device according to claim 13, characterized in that, The first operation includes the following operations: The selection of the target address before the first terminal device generates the first side data; The selection of logical channels before the first terminal device generates the first side data.

15. The terminal device according to claim 14, characterized in that, The first condition is related to the COT sharing condition.

16. The terminal device according to claim 15, characterized in that, The COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

17. The terminal device according to claim 16, characterized in that, The sideline resource for the first sideline data is a first resource. The COT sharing conditions are related to a second resource corresponding to the first resource. The second resource is a sideline resource whose time domain location is earlier than the first resource. The sideline data corresponding to the second resource is second sideline data. The COT sharing conditions 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 data is less than or equal to the CAPC value of the second side data.

18. The terminal device according to any one of claims 13-17, characterized in that, The first condition is determined according to the instructions of the physical layer of the first terminal device.

19. A terminal device, characterized in that, The terminal device is a second terminal device, and the terminal device includes: The receiving unit is used to receive the first sideline data sent by the first terminal device; The first side data is transmitted based on a first operation performed by the first terminal device. 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 channel occupancy, and the first operation is related to the generation of the first side data.

20. The terminal device according to claim 19, characterized in that, The first operation includes the following operations: The selection of the target address before the first terminal device generates the first side data; The selection of logical channels before the first terminal device generates the first side data.

21. The terminal device according to claim 20, characterized in that, The first condition is related to the COT sharing condition.

22. The terminal device according to claim 21, characterized in that, The COT sharing conditions are determined based on one or more of the following information from the first side data: source identifier, destination identifier, and CAPC value.

23. The terminal device according to claim 22, characterized in that, The sideline resource for the first sideline data is a first resource. The COT sharing conditions are related to a second resource corresponding to the first resource. The second resource is a sideline resource whose time domain location is earlier than the first resource. The sideline data corresponding to the second resource is second sideline data. The COT sharing conditions 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 data is less than or equal to the CAPC value of the second side data.

24. The terminal device according to any one of claims 20-23, characterized in that, The first condition is determined according to the instructions of the physical layer of the first terminal device.

Images