Method and apparatus for communication

Abstract

The application provides a method and device for communication, which manages the resources in COT shared by other terminal devices based on the service type, so as to improve the resource utilization and reduce the resource collision when multiple services request the COT shared resources. The method comprises the following steps: a first terminal device determines to allocate a first resource in the COT shared resources to a second terminal device according to the service type of the second terminal device requesting the COT shared resources; wherein the first resource belongs to a first resource block, the first resource block is one of K resource blocks in the COT shared resources, and the K resource blocks correspond to K service types one by one.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly to a method and apparatus for communication. BACKGROUND

[0002] In unlicensed spectrum, a terminal device of sidelink obtains channel resources through mechanisms such as listen before talk (LBT). The terminal device can use the channel resources for sidelink communication within a channel occupancy time (COT), and can also share the COT with other terminal devices.

[0003] The resources for sharing within the COT are limited. When multiple different types of services request the COT sharing resources, how the terminal device allocates resources to improve resource utilization is a problem to be solved. SUMMARY

[0004] The present application provides a method and apparatus for communication. The following introduces each aspect of the embodiments of the present application.

[0005] In a first aspect, a method for communication is provided, the method comprising: determining, by a first terminal device, to allocate a first resource within COT sharing resources to a second terminal device according to a service type for which the second terminal device requests the COT sharing resources; wherein the first resource belongs to a first resource block, the first resource block being one of K resource blocks within the COT sharing resources, the K resource blocks corresponding to K service types one by one.

[0006] In a second aspect, an apparatus for communication is provided, the apparatus being a first terminal device, the first terminal device comprising: a determining unit configured to determine to allocate a first resource within COT sharing resources to a second terminal device according to a service type for which the second terminal device requests the COT sharing resources; wherein the first resource belongs to a first resource block, the first resource block being one of K resource blocks within the COT sharing resources, the K resource blocks corresponding to K service types one by one.

[0007] In a third aspect, a communication apparatus is provided, comprising a memory and a processor, the memory being configured to store a program, and the processor being configured to invoke the program in the memory to execute the method of the first aspect.

[0008] In a fourth aspect, an apparatus is provided, comprising a processor configured to invoke a program from a memory to execute the method of the first aspect.

[0009] In a fifth aspect, a chip is provided, comprising a processor configured to invoke a program from a memory, so that a device in which the chip is installed performs the method according to the first aspect.

[0010] In a sixth aspect, a computer-readable storage medium is provided, having stored thereon a program, which causes a computer to perform the method according to the first aspect.

[0011] In a seventh aspect, a computer program product is provided, comprising a program, which causes a computer to perform the method according to the first aspect.

[0012] In an eighth aspect, a computer program is provided, which causes a computer to perform the method according to the first aspect.

[0013] Embodiments of the present application manage the COT shared resources in blocks based on service types, and the first terminal device allocates the first resources according to the service types of the requested COT shared resources. As can be seen, the COT shared resources include K resource blocks corresponding to K service types, and when other terminal devices request resources based on different service types, the COT can meet the resource requirements of different service types, thereby improving the resource utilization and reducing resource collisions. BRIEF DESCRIPTION OF DRAWINGS

[0014] FIG. 1 An example diagram of a wireless communication system to which embodiments of the present application can be applied.

[0015] FIG. 2 An example diagram of communication for NR-V2X.

[0016] FIG. 3 A structural diagram of a single time slot of a sidelink resource pool.

[0017] FIG. 4 A structural diagram of COT resources obtained by a terminal device through LBT.

[0018] FIG. 5 A flow diagram of a method for communication provided by embodiments of the present application.

[0019] FIG. 6 A flow diagram of another method for communication provided by embodiments of the present application.

[0020] FIG. 7 An example diagram of a system of unicast communication to which embodiments of the present application can be applied.

[0021] FIG. 8 An example diagram of a system of multicast communication to which embodiments of the present application can be applied.

[0022] FIG. 9A system example diagram of another group communication applicable to the embodiments of the present application.

[0023] FIG. 10 A structural schematic diagram of an apparatus for communication provided by the embodiments of the present application.

[0024] FIG. 11 A structural schematic diagram of a communication apparatus provided by the embodiments of the present application. DETAILED DESCRIPTION

[0025] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. In order to facilitate understanding, the following will first be described with reference to the drawings. FIGS. 1-5 The terms and communication processes involved in the present application are introduced.

[0026] FIG. 1 A system architecture example diagram of a wireless communication system 100 applicable to the embodiments of the present application. The wireless communication system 100 can include a network device 110 and terminal devices 121-129. The network device 110 can provide communication coverage for a specific geographic area, and can communicate with terminals located in the coverage area.

[0027] In some implementations, terminal devices can communicate with each other through a sidelink (SL). Sidelink communication can also be referred to as proximity service (ProSe) communication, unilateral communication, side chain communication, device to device (D2D) communication, etc.

[0028] In other words, terminal devices and terminal devices transmit sidelink data through a sidelink. The sidelink data can include data and / or control signaling. In some implementations, the sidelink data can be a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a PSCCH demodulation reference signal (DMRS), a PSSCH DMRS, a physical sidelink feedback channel (PSFCH), etc.

[0029] The following will be described with reference to the drawings. FIG. 1Several common sidelink communication scenarios are introduced. In sidelink communication, according to whether the terminal devices in the sidelink are within the coverage of the network device, three scenarios can be divided. Scenario 1, the terminal devices are within the coverage of the network device for sidelink communication. Scenario 2, part of the terminal devices are within the coverage of the network device for sidelink communication. Scenario 3, the terminal devices are outside the coverage of the network device for sidelink communication.

[0030] As shown in FIG. 1, in scenario 1, the terminal devices 121-122 can communicate through sidelink, and the terminal devices 121-122 are both within the coverage of the network device 110, or in other words, the terminal devices 121-122 are both within the coverage of the same network device 110. In this scenario, the network device 110 can send configuration signaling to the terminal devices 121-122, and accordingly, the terminal devices 121-122 communicate through sidelink based on the configuration signaling. FIG. 1 As shown in FIG. 1, in scenario 2, the terminal devices 123-124 can communicate through sidelink, and the terminal device 123 is within the coverage of the network device 110, and the terminal device 124 is outside the coverage of the network device 110. In this scenario, the terminal device 123 receives the configuration information of the network device 110, and communicates through sidelink based on the configuration of the configuration signaling. However, for the terminal device 124, since the terminal device 124 is outside the coverage of the network device 110, it cannot receive the configuration information of the network device 110, at this time, the terminal device 124 can obtain the configuration of the sidelink communication according to the pre-configuration configuration information and / or the configuration information sent by the terminal device 123 within the coverage, so as to communicate with the terminal device 123 through sidelink based on the obtained configuration.

[0031] FIG. 1 In some cases, the terminal device 123 can send the above-mentioned configuration information to the terminal device 124 through the physical sidelink broadcast channel (PSBCH) to configure the terminal device 124 to communicate through sidelink.

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

[0033] As shown in FIG. 1, in scenario 3, the terminal devices 125-129 are all outside the coverage of the network device 110 and cannot communicate with the network device 110. In this case, the terminal devices can all communicate through sidelink based on pre-configuration information. FIG. 1

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

[0035] The terminal device 127 serving as the CH can have one or more of the following functions: responsible for establishment of the communication group; joining and leaving of the cluster members; performing resource coordination, allocating sidelink transmission resources for the cluster members, receiving sidelink feedback information from the cluster members; performing resource coordination with other communication groups, and the like.

[0036] It should be noted that, FIG. 1 Exemplarily, one network device and multiple terminal devices are shown, and optionally, the wireless communication system 100 can include multiple network devices, and each network device can include other numbers of terminal devices within its coverage, which are not limited in the embodiments of the present application.

[0037] Optionally, the wireless communication system 100 can further include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

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

[0039] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, and can be used to connect people, things and machines, for example, handheld devices with wireless connection function, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a vehicle, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in 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, which provides a sidelink signal between terminal devices in vehicle-to-everything (V2X) or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink data. The cellular phone and the smart home device communicate with each other without relaying the communication signal through the base station.

[0040] The network device in the embodiments of the present application can be a device for communicating with a terminal device, and the network device can also be referred to as an access network device or a radio access network device, for example, the network device can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) for accessing a terminal device to a wireless network. The base station can broadly cover various names in the following or be replaced by the following names, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), access point (AP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, 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. The 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. The base station can also refer to a communication module, modem or chip for being arranged in the foregoing device or apparatus. The base station can also be a mobile switching center and a device assuming a base station function in D2D, V2X, machine-to-machine (M2M) communication, a network side device in 6G network, a device assuming a base station function in future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form of the network device.

[0041] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, the helicopter or the drone can be configured to act as a device communicating with another base station.

[0042] In some deployments, the network device in the embodiments of the present application can refer to a CU or a DU, or the network device includes a CU and a DU. The gNB can also include an AAU.

[0043] The network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed on airplanes, balloons and satellites in the air. The scene where the network device and the terminal device are located is not limited in the embodiments of the present application.

[0044] It should be understood that all or part of the functions of the communication device in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform, such as a cloud platform.

[0045] Communication modes for sidelink

[0046] With the development of sidelink communication technology, sidelink communication technology involves information interaction of multiple terminal devices. For example, as shown in a V2X communication system 200, vehicle-to-vehicle (V2V) communication between a terminal device 201 and a terminal device 202 involves information interaction between vehicles themselves. Vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication and vehicle-to-pedestrian (V2P) communication between the terminal device 201 and terminal devices 203-205 respectively involve information interaction between vehicles and external systems. FIG. 2

[0047] The gradual expansion of the information interaction range puts forward higher requirements for the communication system. For example, the communication system is required to support higher throughput, lower latency, higher reliability, larger coverage range, more flexible resource allocation, etc. For example, in the development of V2X, in LTE-V2X, only broadcast mode is supported for sidelink communication between terminal devices and terminal devices. In NR-V2X, three communication modes of broadcast, groupcast and unicast can be supported.

[0048] Broadcast is the most basic communication mode in sidelink communication. For the broadcast transmission mode, the terminal device receiving sidelink data can be any terminal device around the terminal device as the sending end. For example, referring to FIG. 1 , assuming that the terminal device 125 is the sending end and sends sidelink data in the form of broadcast, the terminal devices 121-124 and the terminal devices 126-129 around the terminal device 125 can all be the receiving end of the sidelink data.

[0049] ​Multicast (or groupcast) communication is used to support information exchange between terminal devices in a specific group (or communication group) to assist in completing negotiation and decision-making of terminal devices in the group. The sidelink groupcast is divided into two transmission types. Type one is for a managed group with a stable connection relationship, and there is clear ID information and information of members in the group. Type two is for a connectionless group, for example, a distance-based dynamic groupcast, which needs to explicitly indicate the communication distance of the current service.

[0050] For the transmission mode of groupcast, the terminal device receiving the sidelink data can be all terminal devices in a communication group. Alternatively, the terminal device receiving the sidelink data can be all terminal devices within a certain transmission distance. For example, see FIG. 1 For the communication group including terminal devices 127-129, when the terminal device 127 transmits sidelink data in a groupcast manner, other terminal devices 128-129 in the communication group are all receiving terminals receiving the sidelink data. For another example, see FIG. 1 Suppose that the terminal devices within a predetermined range include terminal devices 127-129, when the terminal device 127 transmits sidelink data in a groupcast manner, other terminal devices 128-129 within the predetermined range are all receiving terminals receiving the sidelink data.

[0051] Unicast communication can realize sidelink communication between two terminal devices. Taking NR-V2X as an example, radio resource control (RRC) signaling based on PC5 interface can realize terminal device to terminal device reliable communication.

[0052] For the transmission mode of unicast, the terminal device receiving the sidelink data is usually only one. See FIG. 1 The terminal device 121 and the terminal device 122 can communicate through the transmission mode of unicast. For example, when the terminal device 121 performs sidelink communication with the terminal device 122, the terminal device 122 receives sidelink data as the only receiving device. The sidelink data can include PSSCH and PSCCH. The terminal device 122 can obtain sidelink control information (SCI) related to sidelink transmission and scheduling by demodulation, and the SCI can help the terminal device 122 to receive and decode the sidelink information.

[0053] In a communication system, a higher layer decides whether unicast, groupcast or broadcast transmission is used for a specific data transmission and informs the physical layer accordingly. For example, when considering unicast or groupcast transmission, the terminal device is able to establish which unicast or groupcast session the transmission belongs to and the physical layer is aware of the identities (IDs) information. The IDs of the destination transmitted in the SCI are conveyed over the PSCCH and can be used for the receiver to identify the process ID of the transmission HARQ when using hybrid automatic repeat request (HARQ) feedback. The access layer can provide whether it is unicast, groupcast or broadcast transmission for this specific data transmission. For unicast and groupcast transmission in SL, the layer 2 is aware of the IDs information: destination ID and source ID for unicast; destination group ID and source ID for groupcast. If a terminal device is configured with a destination group ID, it is allowed to perform broadcast transmission regardless of whether it is within or outside the “minimum communication range” provided by the upper layer.

[0054] In certain communication systems (e.g., NR-V2X), it is necessary to address the HARQ transmission in a resource pool. For example, the groupcast and unicast sidelink transmission supported by NRV2X supports HARQ operation. The unicast and groupcast traffic of SL supports the HARQ mechanism through acknowledgement (ACK) / negative acknowledgement (NACK). For groupcast traffic, NACK-only HARQ can also be used. In addition, a blind retransmission mechanism is also supported. The sidelink HARQ feedback is sent by the terminal device of the receiver to the terminal device of the transmitter on the PSFCH. In the resource pool of the sidelink, the HARQ feedback resource can be configured and / or pre-configured, for example, once every n time slots (n = 1, 2, 4). That is, NRV2X can support resource reservation for HARQ-based retransmission.

[0055] Resource pools for sidelink

[0056] In certain communication systems (e.g., NR), two resource configuration modes of sidelink resources are defined, mode 1 and mode 2. Mode 1 is that the network device schedules sidelink resources for the terminal device. For example, FIG. 1 The terminal devices 121-123 are located within the coverage of the network device 110, and the network device 110 can allocate sidelink resources for the terminal devices 121-123.

[0057] Mode 2 involves the terminal device autonomously selecting sidelink resources from the resource pool. In this mode, the process performed by the terminal device includes a resource probing process and / or a resource selection process. During resource probing, the terminal device can detect the occupancy of sidelink resources by demodulating the SCI. The terminal device can also detect the occupancy of sidelink resources by measuring the received power of the sidelink. For example, FIG. 1 The terminal devices 124 to 129 are located outside the coverage area of ​​the network device 110. The terminal devices 124 to 129 can autonomously select sidelink resources through mode 2.

[0058] The following text combines FIG. 3 This paper uses the NR-V2X resource pool as an example to introduce the sidelink resource pool applicable to the embodiments of this application. A sub-channel can be understood as the smallest granularity specifying PSSCH resource allocation in NR-V2X. For example... FIG. 3 As shown, the resource pool of the side link includes m sub-channels, namely sub-channel 0, sub-channel 1 to sub-channel m-1. Each sub-channel can be composed of n... SubCHsize It consists of n physical resource blocks (PRBs). SubCHsize The value can be 10, 12, 15, 20, 25, 50, 75, or 100. In the time domain, the terminal device can be configured with m×n values ​​in a given time slot. SubCHsize PRB, this m×n SubCHsize One PRB can be transmitted in one transmission. If the resource pool includes T time slots, the resource pool that the terminal device can choose autonomously is m×n. SubCHsize ×T PRBs.

[0059] Taking unicast communication between terminal device A and terminal device B as an example, in the resource pool, terminal device A, as the sender, can sequentially select resources to conduct side-channel communication with terminal device B, the receiver. For example, terminal device A can conduct side-channel communication with terminal device B in the same time slot, a portion of frequency resources, or directly in the next time slot. Terminal device A can also select a portion of resources in each sub-channel of each time slot to conduct side-channel communication with terminal device B.

[0060] In the resource pool, there are mainly reserved resource pool and dynamically allocated resource pool. The reserved resource pool can be used for various communication systems. Taking the resource pool of NR as an example, the reserved resource pool is also suitable for access of other communication modes, such as LTE, wireless fidelity (WIFI), etc. The reserved resource pool can also be used for periodic traffic with obvious characteristics. For example, for V2X traffic with obvious periodic characteristics such as road safety, a resource allocation mechanism combining sensing channel and semi-persistent scheduling (SPS) is adopted. By taking full advantage of the periodic characteristics of V2X traffic, the sending node reserves periodic transmission resources to carry the periodic V2X traffic to be sent, which helps the receiving node to perform resource state sensing and collision avoidance, improves the resource utilization, and improves the transmission reliability.

[0061] The dynamically allocated resource pool can be used for non-periodic traffic. For non-periodic traffic, a resource allocation mechanism combining sensing and single transmission is adopted, but due to the inability to predict and reserve future resource occupation, the probability of resource collision is large.

[0062] Communication spectrum for sidelink

[0063] The spectrum used by the communication system includes licensed spectrum and unlicensed spectrum. An important direction for the communication system to expand into different fields is the use of unlicensed spectrum. For example, NR deployed on unlicensed spectrum is called NR-U.

[0064] At present, the main spectrum used by sidelink is licensed spectrum. Sidelink can also use unlicensed spectrum. Deploying sidelink on unlicensed spectrum can be called SL-U.

[0065] Compared with licensed spectrum, unlicensed spectrum has the shared characteristic of not requiring permission. For operators, spectrum sharing helps to aggregate spectrum in time to dynamically support high-bandwidth services. Spectrum sharing can also extend the advantages of communication technologies (such as NR) to operators who may not be able to obtain licensed spectrum.

[0066] Unlicensed spectrum needs to consider the coexistence between different radio access technology (RAT) systems, such as wireless fidelity (WIFI) system, license assisted access (LAA) system based on LTE, etc. Different systems use the frequency band in the unlicensed spectrum in a competitive manner according to the principle of channel access fairness and multi-RAT coexistence.

[0067] In unlicensed spectrum, any RAT system must communicate under the constraints of unlicensed spectrum regulatory rules. These rules include power and power spectral density levels, maximum COT (Cost-Occupied Area), channel occupancy bandwidth, and channel monitoring mechanisms. Within the same frequency band, each system must meet the regulatory requirements, appropriately occupying and releasing channels to avoid interfering with other RAT systems in the same band. For example, to support different RATs in unlicensed spectrum, communication between sidelink terminal devices is subject to the aforementioned regulatory rules.

[0068] For the use of unlicensed spectrum, RAT systems can employ forced channel detection techniques (e.g., LBT) to access the network. That is, data transmission can only proceed if it is detected that the channel is currently unoccupied. For example, a sidelink terminal device can initiate an LBT, which can be either a type 2 (Cat 2) LBT or a type 4 (Cat 4) LBT.

[0069] Under the LBT channel access mechanism in SL-U, unlicensed spectrum can support different types and levels of LBTs depending on the circumstances. For example, LBTs have different priorities to reflect the importance of the channel / signal to be transmitted. Generally, terminal devices use type 4 LBT when requesting COT resources, and the LBT priority is determined based on the data being transmitted during data transmission, with other signal / channel transmissions using the highest priority.

[0070] After obtaining channel resources through LBT, the terminal device can perform corresponding detections and transmit data based on the aforementioned regulatory rules. For example, when the terminal device transmits data through channel resources, it needs to meet the COT (Condition of Time) restriction. That is, a single continuous data transmission must be limited to the COT time. If this time is exceeded, the terminal device needs to release the channel and re-enter LBT.

[0071] The terminal device initiates LBT and obtains channel resources within the COT; therefore, this terminal device is also called the initiator of COT resources. The following section provides a detailed description of the resource situation within the COT in four pairs.

[0072] like FIG. 4 As shown, the resources within a COT refer to the time-frequency resources within a COT following the LBT. In the frequency domain, this channel resource includes multiple... FIG. 3 The subchannel is shown. In the time domain, this channel resource contains T time slots within the COT. There are m subchannels, and each subchannel contains n... SubCHsize When there are 1 PRBs, the total size of the COT shared resources initiated by the terminal device is m×n. SubCHsize ×T PRBs. Within a single time slot, the resources shared by the COT are m×n. SubCHsize One PRB.

[0073] The terminal device obtains FIG. 4 The terminal device can sequentially select resources to perform sidelink transmission with other terminal devices after the COT resources are indicated. For example, the terminal device can transmit PSSCH and PSCCH through partial frequency resources of the same time slot. The terminal device can also perform data transmission in different time slots. The terminal device can also transmit PSSCH and PSCCH to other terminal devices by selecting partial resources in each time slot and each subchannel.

[0074] In FIG. 4 The direction of data transmission within one COT can be changed. The terminal device obtaining the COT information can transmit data to the terminal device receiving sidelink within the COT resources, and the terminal device receiving sidelink can also transmit data to the terminal device transmitting sidelink using the resources. For example, after terminal device A accesses the network through LBT, it can initiate COT sharing. If terminal device A and terminal device B perform sidelink communication, PSSCH and PSCCH are transmitted. Terminal device B can obtain sidelink-related transmission and scheduling information SCI by demodulating PSCCH. Terminal device B can receive and decode sidelink information through the SCI.

[0075] The resources within the COT can also be divided into a reserved resource pool and a dynamically allocated resource pool as a shared resource pool. The reserved resource pool can be used for periodic services, and the dynamically allocated resource pool can be used for resource requests of non-periodic services.

[0076] If the resources within the COT are not fully used, the remaining COT resources can also be shared with other terminal devices for sidelink to avoid resource waste. For example, terminal device C and terminal device D can also perform sidelink communication through the COT shared information (COT-SI) sent by terminal device A. Specifically, to provide sidelink sharing, terminal device A can include COT sharing information for sidelink in PSCCH. The COT sharing information can indicate the COT duration, where to start, where to end, and indicate the remaining unused resources. The COT sharing information can display the remaining resources to avoid conflicts. Terminal device C and terminal device D detecting sidelink sharing can join the COT according to the information and use the remaining unused resources for sidelink transmission. Further, the COT sharing information can also indicate how long the terminal device C or terminal device D wishing to join the COT is allowed to access.

[0077] However, the resources for sharing within the COT are limited. If multiple sidelinks want to join, the remaining resources within the COT can not meet the needs of all sidelinks. Or, if multiple terminal devices request to use the resources within the same time period based on multiple service types, resource collision can occur. Further, if the COT allocates resources based on the request time, the service type with higher priority can not have enough resources due to the later request time, and thus cannot complete data transmission in time. Therefore, how to manage and allocate the resources for sharing within the COT to improve resource utilization and reduce resource collision is a technical problem to be solved.

[0078] To solve the above-mentioned partial problems, an embodiment of the present application provides a method for communication. The method manages the resources for sharing within the COT based on service types, and dynamically allocates resources through the service types requesting resources, which helps to improve resource utilization and further reduces the problem that some service types with higher priority cannot be transmitted in time due to insufficient resources. The method will be described below in combination with FIG. 5 The method for communication provided by the embodiment of the present application is introduced.

[0079] Referring to FIG. 5 At step S510, the first terminal device determines to allocate a first resource within the COT shared resources to the second terminal device according to the service type of the second terminal device requesting the COT shared resources.

[0080] The first terminal device can be a terminal device initiating the COT sharing. In some embodiments, the first terminal device can perform LBT on the unlicensed frequency spectrum based on the transmission service, and obtain the COT resources after the LBT succeeds. The first terminal device can initiate the COT sharing based on the COT resources. For example, the first terminal device can indicate other terminal devices to use the resources for sharing within the COT for sidelink communication by sending COT-SI.

[0081] The second terminal device can be two terminals performing sidelink communication with the first terminal device, or can be another terminal device requesting resources within the COT. In some embodiments, the first terminal device and the second terminal device are two terminal devices interacting with each other, for example, a car and a pedestrian communicating in V2X, or two cars. The first terminal device can be a transmitting terminal of the sidelink, and the second terminal device can be a receiving terminal, or the first terminal device can be a receiving terminal of the sidelink, and the second terminal device can be a transmitting terminal. In some embodiments, the second terminal device can be a terminal device within a communication group to which the first terminal device belongs. For example, the first terminal device and the second terminal device can both be group members within the communication group, or can be a group head terminal and a group member of the communication group, respectively. In some embodiments, the second terminal device can be a terminal device outside the communication group to which the first terminal device belongs.

[0082] The first terminal device and the second terminal device can perform unicast communication, groupcast communication, or broadcast communication. When the first terminal device performs unicast communication, the second terminal device can be a receiving terminal. When the first terminal device performs groupcast communication, the second terminal device can be a receiving terminal within the communication group.

[0083] The COT sharing resource can be an available resource within a COT resource pool initiated by the first terminal device, that is, the resource within the COT for sharing described above. In some embodiments, the COT sharing resource can refer to all resources within the COT, and the size of the COT sharing resource is fixed. In some embodiments, the COT sharing resource can refer to the remaining available resources within the COT, and the size of the COT sharing resource is dynamically changing. In some embodiments, the COT sharing resource can refer to a dynamically allocated resource pool within the COT.

[0084] The COT sharing resource can be obtained by the first terminal device performing channel listening in the unlicensed frequency spectrum. For example, the first terminal device can initiate LBT, and obtain the COT sharing resource after LBT succeeds. Generally, the first terminal device can determine whether the channel is idle through energy detection. The energy detection can detect, for example, the reference signal received power (RSRP), and can also detect the received signal strength indicator (RSSI).

[0085] COT shared resources can have a certain priority. In some embodiments, the priority of COT shared resources can be determined according to the priority corresponding to the service type that initiated the COT. The service type that initiated the COT refers to the service type for which the first terminal device requests COT resource transmission. For example, when the first terminal device requests COT resources for real-time data transmission, the obtained COT shared resources can have a higher priority. In some embodiments, the priority of COT shared resources can be determined according to the priority of the first terminal device initiating LBT.

[0086] The service type requesting COT shared resources can be one of several service types supported by the system. In some embodiments, the multiple service types can be based on different application scenarios of the system. In some embodiments, the multiple service types can be different service types determined based on service priorities, and service type can also refer to service priority. For example, the multiple service types can be multiple types determined based on relevant priorities in Quality of Service (QoS).

[0087] As one possible implementation, the various service types supported by the system can be the three major application scenarios in NR communication systems. For example, the various service types can be enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (uRLLC), or massive machine-type communication (mMTC).

[0088] As another possible implementation, various service types can be determined based on QoS class identifiers (QCI). For example, the service types supported by the system can be divided into L classes based on the QCI. The service type requested by the second terminal device for COT shared resources can belong to one of the L class service types. It should be noted that not all L class service types can be allocated to COT shared resources. That is to say, COT shared resources may only support some services in the L class, which will be explained in detail later.

[0089] Information requesting COT shared resources from a second terminal device can be indicated through various means. For example, the service type or priority of the requested COT shared resources can be indicated through higher-level RRC signaling. Furthermore, the size of the resources required when requesting COT shared resources can be indicated through SCI or other request information. In other words, the request information in the SCI can include the size of the requested resources.

[0090] The first resource can be a time-frequency resource allocated by the first terminal device to the second terminal device. As the initiator of the COT, the first terminal device can allocate the first resource to the second terminal device according to a certain scheduling strategy. In some embodiments, the first terminal device can sort the COT sharing resource in time slot order and schedule in time slot order. In some embodiments, the first terminal device can allocate frequency resources corresponding to different sub-channels in the same time slot.

[0091] The first resource can be indicated by COT-related indication information. In some embodiments, the first terminal device can directly indicate the time domain range and frequency domain range of the first resource through the COT sharing information. In some embodiments, the second terminal device can derive the start and end time and frequency range of the first resource from the indication information.

[0092] The first resource belongs to a first resource block within the COT sharing resource. The first resource block can be one of a plurality of resource blocks within the COT sharing resource. The plurality of resource blocks can be implemented by block management of the resources within the COT for sharing. Each of the plurality of resource blocks can be considered as a resource allocation pool. Through block management, the first terminal device can more finely manage the resources within the COT, reduce resource request collisions, and improve resource utilization.

[0093] In some embodiments, the plurality of resource blocks within the COT sharing resource can correspond to the plurality of service types described above. That is, each type of service can be allocated a resource block. When multiple types of services request resources in the same time period at different times, the first terminal device can reduce the situation of insufficient resources for service types requesting later. For example, when the COT sharing resource supports K types of services, the COT sharing resource can include K resource blocks, and the K resource blocks correspond one-to-one to the K types of services. That is, within the COT sharing resource, there are multiple resource allocation pools for multiple services.

[0094] As a possible implementation, when the service type corresponds to the service priority, the resources within the COT for sharing can also be block-managed according to the service priority. For example, the COT sharing resource can support S different service priorities, and the COT sharing resource can include S resource blocks corresponding one-to-one to the service priorities.

[0095] The size of each resource block in the plurality of resource blocks can be determined according to the resource allocation unit within the COT. In some embodiments, the COT sharing resource includes the m x n resource blocks described above. SubCHsizeWhen the number of PRBs is X T, K resource blocks can be divided into blocks in units of PRBs. In some embodiments, the K resource blocks can also be divided into blocks in units of resource elements (REs) or physical resource block groups (PRBGs).

[0096] In some embodiments, after the COT shared resource is managed in blocks based on the service type, the first terminal device needs to consider the service type to which it belongs when determining the first resource allocated to the second terminal device. For example, when the service type of the COT shared resource requested by the second terminal device is real-time voice transmission, the first terminal device can allocate the corresponding resource in the resource block corresponding to the service as the first resource.

[0097] By FIG. 5 As can be seen, the COT shared resource is managed in blocks based on the service type, which can facilitate the first terminal device to more efficiently allocate resources. However, as described above, the COT shared resource does not necessarily support all service types. In the case of COT sharing, the priority of the data transmitted by the sharing device cannot be lower than the priority of the shared COT. The priority of the shared COT is the priority of the COT shared resource. Therefore, the determination of the plurality of (e.g., K) resource blocks in the COT shared resource needs to consider multiple information.

[0098] In some embodiments, the plurality of resource blocks can be determined according to the priority corresponding to the service type initiating the COT. As can be seen from the foregoing, the priority of the service type that can share the COT resource cannot be lower than the priority of the COT. Therefore, for the COT shared resource, the first terminal device can determine the number of service types that can allocate the first resource according to the priority corresponding to the service type initiating the COT. For example, when the number of service types higher than or equal to the priority of the COT shared resource is K (K is less than or equal to L) among the L service types determined according to the QCI, the COT shared resource can be divided into K resource blocks. That is, the priority corresponding to the K service types is all not lower than the priority corresponding to the service type initiating the COT.

[0099] As a possible implementation, when the priority of the COT shared resource requested by the second terminal device is higher than the priority corresponding to the service type initiating the COT, other conditions also need to be met to obtain the first resource, in order to improve the transmission effect of the resource. As a possible implementation, when the sidelink corresponding to the second terminal device also meets the first condition, the first terminal device can allocate the first resource to the second terminal device. The first condition can be that the channel quality corresponding to the sidelink is greater than a first threshold. The channel quality is, for example, the RSRP of the sidelink communication service that hopes to share the ith resource block, and the first threshold can be RSRP target(i). Specifically, if RSRP > RSRP target (i) Only then can the service be accessed and resources allocated. As another possible implementation, different service types correspond to different RSRPs. target They can be the same or different. Different service types correspond to different RSRPs. target At the same time, the first threshold is related to the service type of the second terminal device requesting COT shared resources.

[0100] In some embodiments, multiple resource blocks can be determined based on the priority of the service type initiating the COT and the priority of the service type requesting the COT to share resources. For example, if K service types requesting COT to share resources have a higher priority than the service type initiating the COT, the COT shared resources can be divided into K resource blocks.

[0101] In some embodiments, multiple resource blocks can be determined based on the priority of the service type requesting the COT shared resource and the number of service types requesting the COT shared resource. For example, if K service types out of L service types requesting the COT shared resource have the highest priority, the COT shared resource can be divided into K resource blocks.

[0102] In some embodiments, multiple resource blocks can be determined based on the size of the COT shared resource and the resource size required by the services requesting the COT shared resource. For example, if the resources available for allocation within the COT shared resource can only satisfy the resource size required by K services, the COT shared resource can be divided into K resource blocks.

[0103] In some embodiments, multiple resource blocks can be determined based on whether the resources in each resource block are contiguous. Contiguous resources facilitate management and scheduling, while discontinuous resources improve the flexibility of resource usage. As a possible implementation, some resource blocks among K resource blocks may have contiguous resources, which can be determined based on the distribution of contiguous resources within the COT shared resources. Discontinuous resources in some resource blocks can improve resource utilization.

[0104] As mentioned earlier, COT shared resources can be divided into K resource blocks, and the number of K resource blocks can be determined based on the size of the COT shared resources. Once the size of the COT shared resources is determined, how to divide them into K resource blocks is a question that needs to be considered.

[0105] In some embodiments, the size of each of the K resource blocks can be determined by equally allocating the COT shared resource. That is, the maximum resource allocated for all service types is the same. By equally allocating the resource occupied by the COT, the problem of insufficient resources for some service types can be reduced, and the use of the resource can be monitored in real time. As a possible implementation, when the size of the COT shared resource is N PRBs per unit time, the maximum resource allocated for each of the K service types is N / K PRBs. For example, all sub-channels in each time slot are equally allocated. If N in each time slot is m x n SubCHsize , the size of each resource block is (m x n SubCHsize ) / K.

[0106] In some embodiments, the size of each of the K resource blocks can be determined based on the fairness factors corresponding to the K service types. After the sizes of the multiple resource blocks are determined based on the fairness factors, the sum of the multiple resource blocks should be less than or equal to the size of the COT shared resource. When the sum of the multiple resource blocks is equal to the size of the COT shared resource, the utilization of the resource can be improved. For example, when the COT shared resource is directly managed by the fairness factors, the sum of the K fairness factors can be 1.

[0107] As a possible implementation, the fairness factors can be determined according to the service types and the service priorities. That is, the system allocates fairness factors according to the service types corresponding to the resource blocks and the service priorities. For example, the fairness factor of each of the K service types is represented by Q j , where j is an integer from 0 to K-1. That is, the fairness factor of the jth resource block corresponding to the K resource blocks corresponding to the K service types is Q j .

[0108] As some embodiments, the size of each resource block can be determined based on the fairness factors on the basis of equal allocation. That is, the system can equally divide the COT shared resource into K resource blocks according to the K supported service types, and then determine the final resource size of each resource block according to the allocated fairness factors. Therefore, the sum of the multiple fairness factors is K, so as to ensure that the sum of the sizes of the multiple resource blocks is equal to the COT shared resource. As a possible example, the size of the COT shared resource is N PRBs per unit time, and the size of the jth resource block of the K resource blocks is Q j x N / K PRBs per unit time. Where the fairness factor Q j satisfies ∑Q j = K, and j is an integer from 0 to K-1. When N in each time slot is m x n SubCHsize , the size of each resource block can be represented as Q j x (m x nSubCHsize ) PRBs.

[0109] For the K resource blocks determined in different ways, the resources of each resource block can be continuous or discontinuous. In some embodiments, according to the actual needs of different service types, part of the K resource blocks allocated on average can be continuous, and part of the K resource blocks allocated on average can be discontinuous.

[0110] The above describes how to divide the COT shared resources into multiple resource blocks. In order to use the resources in each resource block more efficiently, the first terminal device can monitor the use of resources in real time to determine whether there is any remaining available resource for allocation. For example, the first terminal device can determine whether to allocate the first resource to the second terminal device according to the available resources of the first resource block.

[0111] In some embodiments, the available resources of the first resource block can be determined according to the size of the first resource block and the size of the allocated resources. The size of the first resource block can be determined according to the size of each resource block described above. The size of the allocated resources needs to consider the size of the resources allocated each time, or the size of the resources requested each time.

[0112] As a possible implementation, each time the resources are allocated, the allocation unit can be determined according to the size of the requested resources or the setting mode of the RBs in the COT shared resources. That is, each time the resources are allocated, one allocation unit can be subtracted from each resource block. The allocation unit each time the allocation is performed can be a RE, a PRB, or a PRBG. For example, when the resource blocks in the COT shared resources are interleaved by rows, the PRBG can be used as the allocation unit.

[0113] If the frequency domain resources allocated each time on each resource block are represented as [index(i), index(i)+size(i)], where size(i) is the size of the resources requested by the i-th terminal device or the i-th service through SCI. Each time the resources are allocated, the remaining available resources of the different service type resource blocks are the size of the resource block minus the sum of the sizes of the allocated resources. For example, the first resource block is the j-th resource block in the K resource blocks, and S(j) represents the size of the available resources of the j-th resource block. S(j) satisfies the following conditions:

[0114] S(j) = Q j N / K - ∑ i size(i);

[0115] Where N represents the number of PRBs of the COT shared resources in a unit of time; Qj represents the fairness factor corresponding to the j-th resource block, Q j satisfies ∑Q j= K, and j is an integer from 0 to K-1; size(i) represents the size of the resource shared by the ith service request, i is an integer greater than or equal to 0.

[0116] Based on the condition satisfied by S(j) above, when the unit time is one time slot, that is, N on a single time slot is m x n SubCHsize , S(j) satisfies the following condition:

[0117] S(j) = Q j x (m x n SubChsize ) / K -∑ i size(i);

[0118] wherein m represents the number of sub-channels on a single time slot, and n SubCHsize represents the number of PRBs of each sub-channel.

[0119] In some embodiments, the first terminal device can achieve real-time monitoring of the resource usage by determining S(j). For example, if S(j) > 0, it indicates that there is resource available for allocation for this type of service; if S(j) ≤ 0, it indicates that there is no resource available for allocation for this type of service. After each allocation of resource, the size of S(j) can be compared to determine whether S(j) is greater than zero or less than or equal to zero.

[0120] In some embodiments, if the resource allocation of the resource block corresponding to a certain type of service is completed, and a new service request allocates the resource, the first terminal device can determine whether to mobilize other resource blocks for the service. For example, when the first resource block has no available resource, the first terminal device can determine whether to allocate resources in other resource blocks to the second terminal device according to the available resources of the other resource blocks in the K resource blocks except the first resource block.

[0121] As a possible implementation, the first terminal device can determine not to call other resources according to the service situation, and the service can wait for the allocation of resources in the next time slot through LBT backoff mechanism.

[0122] As another possible implementation, the first terminal device can detect whether there is a remaining resource in the resource block corresponding to other service types. For example, when different resource blocks are allocated to the K service types, as long as S(j) > 0 in the other service resource block, the terminal device performing the service can apply for the remaining available resources in the other resource block. The first terminal device determines whether to allocate resources in the other resource blocks to the second terminal device according to the available resources of the other resource blocks in the K resource blocks except the first resource block

[0123] The foregoing introduces real-time monitoring and dynamic adjustment of resources in different resource blocks, which helps to improve the occupancy rate of resources. Through real-time monitoring, the index of the next allocated resource can be determined, and the available resource can be indicated to the second terminal device through the resource index. The resource index can indicate the time-frequency location of the resource in the COT shared resource, or only indicate the time domain location or frequency domain location of the resource. For example, the first resource allocated by the first terminal device to the second terminal device can be indicated by the resource index corresponding to the first resource. The first resource is based on

[0124] In some embodiments, the resource index corresponding to the next allocated resource can be related to the starting index of the COT shared resource. The starting index can be determined based on the starting time-frequency location of the resource available for sharing within the COT, which can be represented by index0.

[0125] In some embodiments, the resource index corresponding to the next allocated resource can be related to the size of the K resource blocks. For example, when the next allocated resource includes the jth resource block of the K resource blocks, the starting position of the time-frequency resource corresponding to the jth resource block can be determined according to the size of the 0th to (j-1)th resource blocks.

[0126] In some embodiments, the resource index corresponding to the next allocated resource can be related to the size of the allocated resource. For example, in the jth resource block, the time-frequency location of the next allocated resource can be determined according to the starting position of the resource block and the size of the allocated resource.

[0127] In some embodiments, the resource index corresponding to the next allocated resource can be related to the starting index of the COT shared resource, the size of the K resource blocks, and the size of the allocated resource. For example, the resource index index(j, i) corresponding to the next allocated resource in the jth resource block of the K resource blocks satisfies the following conditions:

[0128]

[0129] where N represents the number of PRBs of the COT shared resource in a unit of time; Qj represents the fairness factor corresponding to the jth resource block, Q j satisfies ∑Q j = K, and j is an integer from 0 to K-1; size(j, i) represents the size of the resource shared by the ith service request in the jth resource block, i is an integer greater than or equal to 0; K j represents the jth resource pool, K j takes a value of an integer from 0 to K-1, and index0 represents the starting index of the COT shared resource.

[0130] Based on the conditions that the index(j, i) satisfies, when the unit time is one slot, that is, N is mxn on a single slot SubCHsize When, the index(j, i) satisfies the following conditions:

[0131]

[0132] Wherein, m represents the number of sub-channels on a single slot, n SubCHsize represents the number of PRBs of each sub-channel.

[0133] The above introduces the resource index corresponding to the resource used for the next allocation in the COT shared resource. This resource can be used to send PSSCH and PSCCH, or can be used to send PSFCH. Each terminal device that gets the resource of the sidelink can feed back PSFCH to the initiator of the COT, which can indicate the influence of the current resource on the communication result. The terminal device will also send PSFCH feedback to the communicator of the sidelink, indicating the result of the current communication.

[0134] In some embodiments, the PSFCH resource can be a part of the reserved resource in the COT resource pool. For example, the PSFCH resource can be reserved every N slots (N = 1, 2, 4). In some embodiments, the PSFCH resource can be in several common resource blocks according to the service division. For example, the COT shared resource can schedule one or more resource blocks for sending PSFCH.

[0135] As mentioned earlier, in some communication systems, groupcast and unicast of sidelink can support HARQ mechanism. In the case of enabling HARQ setting, the terminal device receiving PSFCH will determine whether to initiate retransmission according to the feedback. Generally speaking, when the feedback information carried by PSFCH is NACK, the terminal device receiving PSFCH will retransmit the data corresponding to the NACK feedback to ensure the reliability of data transmission.

[0136] However, the resources for sharing within the COT are limited. If the NACK for a certain service is constantly retransmitted, it may cause waste of resources. For example, in the case of poor link environment, the receiving terminal will always feedback NACK, and the sending terminal will therefore constantly request COT shared resources for data retransmission, resulting in no available resources for the resource block corresponding to the service, and no available resources for other resource blocks, affecting the transmission of other services.

[0137] For unicast communication, the sending terminal can determine whether to request the first resource mentioned above for retransmission through the number of NACK feedbacks and the available resources of the corresponding service in the COT shared resource block. The terminal device initiating the COT sharing can also determine whether to allocate the first resource according to this situation.

[0138] For the multicast communication, the terminal device initiating the multicast service can set the HARQ enable and disable according to the service mode. The multicast service can include two service modes: the first mode is the multicast service initiated by the terminal device initiating the COT shared resource; the second mode is the multicast service initiated by the terminal device occupying the COT shared resource. Since the terminal device initiating the multicast service is different, different retransmission strategies can be set according to different service modes to meet the communication needs of the terminal device initiating the COT shared resource. That is, the multicast service in the first mode can have higher priority than the multicast service in the second mode. How to ensure the main communication needs during the multicast communication based on the above analysis is a problem to be considered.

[0139] Embodiments of the present application also provide a method for communication. In the method, the COT sharing information is used to indicate whether the terminal device can use the first resource for retransmission, and the utilization rate of the resource is improved by limiting the specific application of the COT shared resource. The method will be described in detail below in combination with FIG. 6

[0140] Referring to FIG. 6 In step S610, the first terminal device sends first COT sharing information, and the first COT sharing information indicates that the first terminal device allocates the first resource within the COT to the second terminal device.

[0141] The first terminal device is FIG. 5 The second terminal device can be a terminal device initiating a multicast service. It should be noted that FIG. 6 The second terminal device in the above

[0142] The first COT sharing information can be carried in the PSSCH or the PSCCH, which is not limited here.

[0143] The first terminal device allocating the first resource within the COT to the second terminal device can mean that the first terminal device allocates the resource to the terminal device within the group, or can mean that the first terminal device allocates the remaining resource available within the COT to the terminal device outside the group.

[0144] The first resource can be a reserved resource within the COT, or FIG. 5 The resource in the resource block corresponding to the different service types shown in

[0145] ​The first information is used to indicate whether the first resource is used for retransmission by the second terminal device, which means that the first information can indicate that the second terminal device initiates in-group retransmission through the first resource, or can indicate that the second terminal device does not perform retransmission through the first resource.

[0146] The first information can be determined according to one or more information. For example, whether the second terminal device is a terminal device initiating COT, or whether a terminal device feeding back NACK to the second terminal device, or whether a sidelink channel sent by the second terminal device disables HARQ feedback.

[0147] In some embodiments, the first information can be determined according to whether the second terminal device is a terminal device initiating COT. For example, when the second terminal device is a terminal device initiating COT, the first information can indicate that it initiates in-group retransmission as long as NACK feedback is received. For another example, when the second terminal device is not a terminal device initiating COT, the first information can indicate that it does not initiate in-group retransmission in the case of receiving NACK feedback.

[0148] In some embodiments, the first information can be determined according to a terminal device feeding back NACK to the second terminal device. That is, the first information can be determined according to the case of the second terminal device receiving NACK feedback. The terminal device feeding back NACK can refer to the number of terminal devices, or can refer to the case of the terminal device feeding back NACK being in a communication group. For example, in a groupcast communication initiated by the second terminal device, when the number of terminal devices feeding back NACK is large, the first information can indicate that the second terminal device initiates in-group retransmission using the first resource. For another example, when the terminal devices feeding back NACK and the terminal device initiating COT are in one communication group, the first information can indicate that the second terminal device initiates retransmission.

[0149] In some embodiments, the first information can be determined according to whether a sidelink channel sent by the second terminal device disables HARQ feedback. Disabling HARQ feedback can reduce the resource of transmitting PSFCH, or can reduce the resource related to retransmission. The sidelink channel sent by the second terminal device can be various channels sent to members in a group, which is not limited here. For example, when the PSSCH sent by the second terminal device disables HARQ feedback, the second terminal device will not perform retransmission, and the first information can directly indicate that the first resource is not used for retransmission. For another example, when the PSSCH sent by the second terminal device disables HARQ feedback, the first information can directly indicate that the second terminal device retransmits only twice.

[0150] In some embodiments, the first information can be determined according to the above-mentioned multiple information. For example, the second terminal device is the terminal device initiating the COT, and when the number of terminal devices feeding back NACK to the second terminal device is at least one, the first information indicates that the second terminal device retransmits through the first resource. For another example, if the second terminal device is not the terminal device initiating the COT, when the number of terminal devices feeding back NACK to the second terminal device satisfies the second condition, the first information indicates that the second terminal device retransmits through the first resource, otherwise, the second terminal device does not retransmit.

[0151] As a possible implementation, the second condition can be related to the number of terminal devices feeding back NACK, or related to the number of terminal devices receiving data in the communication group. The number of terminal devices receiving data corresponding to the NACK feedback can be represented by a first parameter. For example, when the ratio of the number of terminal devices feeding back NACK to the second terminal device to the first parameter is greater than a second threshold, the first information indicates that the second terminal device retransmits. The second threshold is, for example, 30%, or for example, 50%.

[0152] As a possible implementation, when the second terminal device is not the terminal device initiating the COT, whether the sidelink channel sent by the second terminal device disables HARQ feedback can be determined according to the type of service carried by the sidelink channel. The type of service carried by the sidelink channel can be one of the K types of services that can share the COT resource as described above. For example, whether to disable HARQ feedback can be determined according to the priority of the type of service carried by the sidelink channel. When the priority of the type of service carried by the sidelink channel is high, HARQ feedback is not disabled, and the reliability of transmission can be guaranteed.

[0153] For ease of understanding, the following describes in detail the unicast communication system and the groupcast communication system to which the embodiments of the present application can be applied. FIGS. 7-9 FIG. 7 Fig. 1 shows an example diagram of a unicast communication system to which the embodiments of the present application can be applied. FIG. 8 Fig. 2 shows an example diagram of a groupcast communication system to which the embodiments of the present application can be applied. FIG. 9 Fig. 3 shows another example diagram of a groupcast communication system to which the embodiments of the present application can be applied.

[0154] Referring to Fig. 1, the unicast communication system 700 includes terminal devices 701-704. After the terminal device 701 accesses the network through LBT, it can initiate COT sharing. The terminal device 701 transmits PSCCH and PSSCH to the terminal device 702 through unicast communication. FIG. 7

[0155] ​​The terminal device 702 is a group terminal device in the sidelink communication with the terminal device 701. The terminal device 702 obtains sidelink-related transmission and scheduling information SCI by demodulating the PSCCH. The SCI can help the terminal device 702 receive and decode the sidelink information. The terminal device 702 can send the PSFCH to the terminal device 701 through the COT shared resource. Generally, as long as the terminal device 702 feeds back the NACK, the terminal device 701 will initiate retransmission through the COT shared resource.

[0156] The terminal device 703 and the terminal device 704 are out-of-group terminal devices that want to perform sidelink communication through the COT sharing of the terminal device 701. The terminal device 703 and the terminal device 704 can join the COT sharing of the first terminal device by detecting the COT sharing information. The terminal device 703 and the terminal device 704 can both send the PSFCH to the terminal device 701 through the COT shared resource. If the number of NACKs fed back by the terminal device 703 or the terminal device 704 to the terminal device 701 reaches a certain value (such as 3 times, 5 times, etc.), and there is no available resource in the resource block to which the NACK corresponds, the terminal device 703 or the terminal device 704 cannot request other service resource block allocation retransmission resources.

[0157] Referring to FIG. 8 , the multicast communication system 800 includes terminal devices 801-805. The terminal device 801 communicates with the group member terminal devices 802-805 in a multicast mode.

[0158] The terminal device 801 is the initiating terminal of the COT sharing, and the group member terminal devices 802-805 can receive the information of the terminal device 801. The terminal devices 802-805 obtain the starting point, the termination point, and the time length of the COT shared resource by demodulating the PSCCH / PSSCH. That is, the terminal device 801 initiating the COT resource sharing is also the initiator of the multicast service.

[0159] If the HARQ of the communication group to which the terminal device 801 belongs is set to an enabled state, the terminal devices 802-805 will send a NACK indication when decoding the PSSCH / PSCCH fails. The terminal device 801 can have the following two processing modes.

[0160] Mode one, the terminal device 801 will initiate group retransmission as long as it receives a NACK fed back by a group terminal.

[0161] Mode two, the terminal device 801 will initiate group retransmission only when the ratio of the NACKs fed back by the group terminals to the number of multicast terminals reaches a certain proportion, for example, 30%, 50%, etc., otherwise, it will not initiate retransmission.

[0162] Referring to FIG. 9 , the terminal device 901~907 are included in the multicast communication system 900. The terminal device 901 communicates with the terminal device 902 and the terminal device 903 in the mode of multicast, and the terminal device 903 also communicates with the in-group member terminal device 904~907 in the mode of multicast.

[0163] The terminal device 901 is the initiator of COT sharing, and the in-group member terminal device 902 and the terminal device 903 can receive the information of the terminal device 901. The terminal device 902 and the terminal device 903 obtain the starting point, the ending point, the time length, etc. of COT sharing by demodulating the PSCCH / PSSCH.

[0164] The terminal device 903 can initiate the multicast communication with the in-group member terminal device 904~907 through the COT sharing resource initiated by the terminal device 901. If the multicast service initiated by the terminal device 903 enables HARQ, the terminal device 904~907 will feed back to the terminal device 903 according to the decoding situation. Since the terminal device 903 that initiates the multicast service is not the initiator of COT sharing, the terminal device 903 will only initiate the in-group retransmission when the ratio of the NACKs received from the in-group terminals to the number of multicast terminals reaches a certain proportion. This proportion can also be 30%, 50%, etc., otherwise, the terminal device 903 will not initiate the retransmission.

[0165] In order to save resources, the multicast service initiated by the terminal device 903 can also disable the HARQ feedback. That is, the terminal device 904~907 can not consider the decoding situation and do not feed back to the terminal device 903. The terminal device 903 can not retransmit or can retransmit a fixed number of times.

[0166] The above describes the method embodiments of the present application in detail. FIGS. 1-9 The device embodiments of the present application are described in detail below in combination with FIG. 10 and FIG. 11 . It should be understood that the description of the device embodiments corresponds to the description of the method embodiments, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.

[0167] FIG. 10 A structure schematic diagram of a device for communication provided by the embodiments of the present application. The device for communication 1000 is configured as any one of the first terminal devices described above, and can execute the method for communication described above. As shown in FIG. 5 , the device 1000 includes a determination unit 1010. FIG. 10

[0168] ​The determining unit 1010 can be configured to determine, according to a service type of the second terminal device requesting the COT shared resource, to allocate a first resource in the COT shared resource to the second terminal device; wherein the first resource belongs to a first resource block, and the first resource block is one of K resource blocks in the COT shared resource, and the K resource blocks correspond to the K service types one by one.

[0169] Optionally, the K resource blocks are determined according to one or more of the following information: a priority corresponding to the service type initiating the COT; a priority corresponding to the service type requesting the COT shared resource; a number of service types requesting the COT shared resource; a size of the COT shared resource; a size of a resource required by the service requesting the COT shared resource; and whether the resource of each of the K resource blocks is continuous.

[0170] Optionally, the priority corresponding to each of the K service types is not lower than the priority corresponding to the service type initiating the COT.

[0171] Optionally, the size of each of the K resource blocks is determined by equally allocating the COT shared resource.

[0172] Optionally, the size of each of the K resource blocks is determined based on a fairness factor corresponding to the K service types.

[0173] Optionally, the size of the COT shared resource is N PRBs in a unit of time, and the fairness factor corresponding to the jth resource block of the K resource blocks is Q j , Q j satisfies ∑Q j = K, where j is an integer from 0 to K-1, and the size of the jth resource block is Q j ×N / K PRBs in a unit of time.

[0174] Optionally, the apparatus 1000 further includes an allocating unit configured to allocate the first resource to the second terminal device when a first condition of a sidelink corresponding to the second terminal device is satisfied.

[0175] Optionally, the first condition is that a channel quality corresponding to the sidelink is greater than a first threshold, and the first threshold is related to the service type of the second terminal device requesting the COT shared resource.

[0176] Optionally, the determining unit 1010 is further configured to determine whether to allocate the first resource to the second terminal device according to available resources of the first resource block.

[0177] Optionally, the available resources of the first resource block are determined according to a size of the first resource block and a size of an already allocated resource.

[0178] Optionally, the size of the COT sharing resource is N PRBs in a unit of time, the first resource block is a jth resource block in K resource blocks, and a fairness factor corresponding to the jth resource block is Q j , Q j satisfies ∑Q j = K, where j is an integer from 0 to K-1, and the size S(j) of the available resource of the jth resource block satisfies the following condition:

[0179] S(j) = Q j × N / K - ∑ i size(i);

[0180] where size(i) represents the size of the resource shared by the ith service request, and i is an integer greater than or equal to 0.

[0181] Optionally, the first resource block has no available resource, and the determining unit 1010 is further configured to determine whether to allocate resources in other resource blocks to the second terminal device according to the available resources of the other resource blocks except the first resource block in the K resource blocks.

[0182] Optionally, the first resource is indicated by a resource index corresponding to the first resource.

[0183] Optionally, the resource index corresponding to the first resource is related to one or more of the following information: a starting index of the COT sharing resource, a size of the K resource blocks, and a size of the allocated resource.

[0184] Optionally, the size of the COT sharing resource is N PRBs in a unit of time, and a fairness factor corresponding to a jth resource block in K resource blocks is Q j , Q j satisfies ∑Q j = K, where j is an integer from 0 to K-1, the first resource belongs to the jth resource block, and a resource index index(j, i) corresponding to the first resource satisfies the following condition:

[0185]

[0186] where size(j, i) represents the size of the resource shared by the ith service request in the jth resource block, i is an integer greater than or equal to 0, K j represents a jth resource pool, K j takes an integer value of 0 to K-1, and index0 represents a starting index of the COT sharing resource.

[0187] Optionally, the apparatus 1000 further includes a sending unit, configured to send first COT sharing information, the first COT sharing information indicating that the first terminal device allocates a first resource in a COT to a second terminal device; wherein the first COT sharing information includes first information, the first information being used to indicate whether the first resource is used for the second terminal device to perform retransmission.

[0188] Optionally, the first information is determined according to the following information: whether the second terminal device is a terminal device initiating the COT; a terminal device feeding back a NACK to the second terminal device; and whether a sidelink channel sent by the second terminal device disables HARQ feedback.

[0189] Optionally, the first information is determined according to the following information: if the second terminal device is a terminal device initiating the COT, when the number of terminal devices feeding back a NACK to the second terminal device is at least one, the first information indicates that the second terminal device performs retransmission through the first resource; and if the second terminal device is not a terminal device initiating the COT, when the number of terminal devices feeding back a NACK to the second terminal device satisfies a second condition, the first information indicates that the second terminal device performs retransmission through the first resource.

[0190] Optionally, the second condition is that the ratio of the number of terminal devices feeding back a NACK to the second terminal device to a first parameter is greater than a second threshold value, and the first parameter is the number of terminal devices receiving data corresponding to the NACK feedback.

[0191] Optionally, the second terminal device is not a terminal device initiating the COT, and whether a sidelink channel sent by the second terminal device disables HARQ feedback is determined according to a service type carried by the sidelink channel.

[0192] FIG. 11 FIG. 1 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application. FIG. 11 The dashed line in FIG. 1 indicates that the unit or module is optional. FIG. 11 The apparatus 1100 in FIG. 1 can be used to implement the method described in the above method embodiment. The apparatus 1100 can be a chip, a terminal device or a network device.

[0193] The apparatus 1100 can include one or more processors 1110. The processor 1110 can support the apparatus 1100 to implement the methods described in the foregoing method embodiments. The processor 1110 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0194] The apparatus 1100 can also include one or more memories 1120. The memory 1120 stores programs, which can be executed by the processor 1110, so that the processor 1110 performs the methods described in the foregoing method embodiments. The memory 1120 can be independent of the processor 1110 or integrated in the processor 1110.

[0195] The apparatus 1100 can also include a transceiver 1130. The processor 1110 can communicate with other devices or chips through the transceiver 1130. For example, the processor 1110 can perform data transceiving with other devices or chips through the transceiver 1130.

[0196] The embodiments of the present application also provide a computer readable storage medium for storing programs. The computer readable storage medium can be applied to the terminal device or the network device provided by the embodiments of the present application, and the programs make the computer execute the methods performed by the terminal or the network device in the embodiments of the present application.

[0197] The computer readable storage medium can be any available medium or a data storage device such as a server, data center, etc. integrated with one or more available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)) or a semiconductor medium (for example, a solid state disk (SSD)) and the like.

[0198] The embodiment of the present application further provides a computer program product. The computer program product comprises a program. The computer program product can be applied to the terminal device or the network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the embodiments of the present application.

[0199] In the above embodiments, the implementation can be achieved by software, hardware, firmware or any combination thereof. When implemented by software, the implementation can be achieved by a computer program product in whole or in part. The computer program product comprises one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the whole or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL) or wireless (such as infrared, wireless, microwave, etc.).

[0200] The terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0201] In the embodiments of the present application, the "indication" mentioned can be direct indication, indirect indication, or can be an indication with an associated relationship. For example, A indicates B, which can mean that B can be obtained by A, or A indirectly indicates B, for example, A indicates C, and B can be obtained by C, or A and B have an associated relationship.

[0202] In the embodiments of the present application, the term "corresponding" can mean that there is a direct or indirect corresponding relationship between the two, or can mean that there is an associated relationship between the two, or can mean an indication and being indicated, configuration and being configured, etc.

[0203] In the embodiments of the present application, the "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables or other manners available for indicating relevant information in devices (for example, including terminal devices and network devices), and the specific implementation manners are not limited in the present application. For example, the predefined can refer to the definition in a protocol.

[0204] In the embodiments of the present application, the "determining B according to A" does not mean that B is determined only according to A, but also can be determined according to A and / or other information.

[0205] The term "and / or" in the embodiments of the present application merely describes an association relationship of associated objects, and can represent three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " in the present application generally represents an "or" relationship between the front and rear associated objects.

[0206] In various embodiments of the present application, the size of the serial number of the above processes does not mean the execution order, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0207] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other ways. For example, the device embodiments described above are only schematic, and for example, the division of the units is only a logical function division, and there can be another division way in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0208] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

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

[0210] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for communication, characterized in that, include: The first terminal device determines to allocate the first resource within the COT shared resource to the second terminal device based on the service type of the channel occupancy time (COT) shared resource requested by the second terminal device. The first terminal device sends first COT sharing information, which indicates that the first terminal device has allocated the first resource within the COT to the second terminal device; wherein, the first resource belongs to a first resource block, and the first resource block is one of K resource blocks within the COT shared resource, and the K resource blocks correspond one-to-one with K service types, and the first COT sharing information includes first information, which is used to indicate whether the first resource is used for retransmission by the second terminal device.

2. The method according to claim 1, characterized in that, The K resource blocks are determined based on one or more of the following information: Priority of the business type that initiates COT; The priority corresponding to the service type of the requested COT shared resources; The number of service types requested for the COT shared resources; The size of the COT shared resources; The size of the resources required for the service requesting the COT shared resources; and Whether the resources of each of the K resource blocks are contiguous.

3. The method according to claim 2, characterized in that, The priority of each of the K service types is no lower than the priority of the service type that initiates the COT.

4. The method according to claim 2, characterized in that, The size of each of the K resource blocks is determined by evenly distributing the COT shared resources.

5. The method according to claim 2 or 4, characterized in that, The size of each of the K resource blocks is also determined based on the fairness factor corresponding to the K business types.

6. The method according to claim 5, characterized in that, The size of the COT shared resource is N physical resource blocks (PRBs) per unit time, and the fairness factor corresponding to the j-th resource block among the K resource blocks is Q. j The Q j Satisfying ∑Q j = K, where j is an integer from 0 to K-1, and the size of the j-th resource block is Q per unit time. j ×N / K PRBs.

7. The method according to any one of claims 1-4, characterized in that, The method further includes: When the side link corresponding to the second terminal device meets the first condition, the first terminal device allocates the first resource to the second terminal device.

8. The method according to claim 7, characterized in that, The first condition is that the channel quality corresponding to the side link is greater than a first threshold, and the first threshold is related to the service type of the second terminal device requesting the COT shared resources.

9. The method according to any one of claims 1-4, characterized in that, The method further includes: The first terminal device determines whether to allocate the first resource to the second terminal device based on the available resources of the first resource block.

10. The method according to claim 9, characterized in that, The available resources of the first resource block are determined based on the size of the first resource block and the size of the allocated resources.

11. The method according to claim 10, characterized in that, The size of the COT shared resource is N PRBs per unit time, the first resource block is the j-th resource block among the K resource blocks, and the fairness factor corresponding to the j-th resource block is Q. j The Q j Satisfying ∑Q j = K, where j is an integer from 0 to K-1, and the available resource size S(j) of the j-th resource block satisfies the following condition: S(j)=Q j ×N / K―∑ i size(i); Where size(i) represents the size of the resource shared by the i-th business request, and i is an integer greater than or equal to 0.

12. The method according to claim 9, characterized in that, The method further includes: If the first resource block has no available resources, the method also includes: The first terminal device determines whether to allocate resources from the other resource blocks to the second terminal device based on the available resources of the other resource blocks among the K resource blocks excluding the first resource block.

13. The method according to any one of claims 1-4, characterized in that, The first resource is indicated by the resource index corresponding to the first resource.

14. The method according to claim 13, characterized in that, The resource index is determined based on one or more of the following information: the starting index of the COT shared resource, the size of the K resource blocks, and the size of the allocated resources.

15. The method according to claim 14, characterized in that, The size of the COT shared resource is N PRBs per unit time, and the fairness factor corresponding to the j-th resource block among the K resource blocks is Q. j The Q j Satisfying ∑Q j = K, where j is an integer from 0 to K-1, the first resource belongs to the j-th resource block, and the resource index index(j,i) corresponding to the first resource satisfies the following condition: Where size(j,i) represents the size of the resource shared by the i-th service request in the j-th resource block, i is an integer greater than or equal to 0, and index0 represents the starting index of the COT shared resource.

16. The method according to claim 1, characterized in that, The first information is determined based on one or more of the following: Whether the second terminal device is the terminal device that initiated the COT; The terminal device that sends a negative acknowledgment (NACK) to the second terminal device; and The second terminal device sends feedback on whether the side-channel is disabled via Hybrid Automatic Repeat Request (HARQ).

17. The method according to claim 1, characterized in that, The first information is determined based on the following information: If the second terminal device is the terminal device that initiated the COT, when the number of terminal devices that send NACK feedback to the second terminal device is at least one, the first information instructs the second terminal device to retransmit through the first resource; If the second terminal device is not the terminal device that initiated the COT, when the number of terminal devices that send NACK feedback to the second terminal device meets the second condition, the first information instructs the second terminal device to retransmit through the first resource.

18. The method according to claim 17, characterized in that, The second condition is that the ratio of the number of terminal devices that send NACK feedback to the second terminal device to the first parameter is greater than a second threshold, where the first parameter is the number of terminal devices that receive the corresponding data of the NACK feedback.

19. The method according to claim 16, characterized in that, The second terminal device is not the terminal device that initiated the COT. Whether the side channel sent by the second terminal device disables HARQ feedback is determined according to the service type carried by the side channel.

20. A device for communication, characterized in that, The device is a first terminal device, which includes: The determining unit is configured to determine, based on the service type of the second terminal device requesting the channel occupancy time (COT) shared resource, to allocate a first resource within the COT shared resource to the second terminal device; A sending unit is configured to send first COT sharing information, wherein the first COT sharing information indicates that the first terminal device allocates the first resource within the COT to the second terminal device; Wherein, the first resource belongs to the first resource block, the first resource block is one of the K resource blocks in the COT shared resource, the K resource blocks correspond one-to-one with K service types, the first COT shared information includes first information, the first information is used to indicate whether the first resource is used for retransmission by the second terminal device.

21. The apparatus according to claim 20, characterized in that, The K resource blocks are determined based on one or more of the following information: Priority of the business type that initiates COT; The priority corresponding to the service type of the requested COT shared resources; The number of service types requested for the COT shared resources; The size of the COT shared resources; The size of the resources required for the service requesting the COT shared resources; and Whether the resources of each of the K resource blocks are contiguous.

22. The apparatus according to claim 20, characterized in that, The first terminal device also includes: The allocation unit is used to allocate the first resource to the second terminal device when the side link corresponding to the second terminal device meets the first condition.

23. The apparatus according to claim 20, characterized in that, The determining unit is further configured to determine whether to allocate the first resource to the second terminal device based on the available resources of the first resource block.

24. The apparatus according to claim 23, characterized in that, If the first resource block has no available resources, the determining unit is further configured to determine whether to allocate resources from the other resource blocks to the second terminal device based on the available resources of the other resource blocks among the K resource blocks excluding the first resource block.

25. A communication device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to perform the method as described in any one of claims 1-19.

26. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-19.

Images