Method and device for sending internal coordination information request between directly connected sidelink terminal devices

Abstract

The disclosed embodiments disclose a method and apparatus for transmitting internal coordination information requests between directly connected sidelink terminal devices. The method can be applied to systems such as the Internet of Vehicles, Vehicle-to-Everything (V2X), and Vehicle-to-Vehicle (V2V). The method is executed by a first terminal device and includes determining whether to stop transmitting or generating inter-terminal device coordination information requests based on a set duration of a timer and a count value of a counter. By implementing the disclosed embodiments, the first terminal device can be prevented from continuously transmitting or generating inter-terminal device coordination information requests without knowing the resource allocation mode and / or capabilities of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and apparatus for sending an internal coordination information request between directly connected Sidelink terminal devices. Background Art

[0002] In the related art, when different UEs (user equipment) communicate via a sidelink (SL), there are two ways to allocate transmission resources: one is the network dynamic scheduling method (mode 1), and the other is the UE's autonomous selection from the resource pool broadcast by the network (mode 2). In order to assist the peer UE in better resource selection and avoid conflicts with other UEs, the R17 (Release-17) standard introduced IUC (inter-UE coordination), so that UE-A in mode 2 can send an inter-UE coordination medium access control unit IUC MAC (Medium Access Control) CE (Control Element) to the peer UE-B in mode 2. However, the UE currently using SL for communication does not know whether the peer UE is in mode 1 or mode 2, and does not know whether the peer UE supports the IUC feature. For the request-based IUC mechanism, if UE-B sends an IUC request to UE-A, but UE-A does not feedback IUC information, UE-B will continue to send IUC requests, resulting in signaling waste and interference with the communications of other UEs. Summary of the Invention

[0003] The embodiments of the present disclosure provide a method and apparatus for sending internal coordination information requests between directly connected Sidelink terminal devices, which can be applied to the Internet of Vehicles, such as vehicle-to-everything (V2X) communication, long-term evolution-vehicle (LTE-V) communication, vehicle-to-vehicle (V2V) communication, etc., or can be used in the fields of intelligent driving, intelligent connected vehicles, etc. By determining whether to stop sending or generating coordination information requests between terminal devices based on the set duration of a timer and the count value of a counter, it is possible to avoid the first terminal device from continuously sending or generating coordination information requests between terminal devices without knowing the resource allocation mode and / or capability of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

[0004] In a first aspect, an embodiment of the present disclosure provides a method for sending an internal coordination information request between directly connected Sidelink terminal devices, the method being executed by a first terminal device, and the method comprising: determining whether to stop sending or generate the inter-terminal device coordination information request IUC-request based on a set duration of a timer and a count value of a counter.

[0005] In one implementation, the determination of whether to stop sending or generating the coordination information request between terminal devices based on the set duration of the timer and the count value of the counter includes: starting the timer in response to sending or generating the coordination information request between terminal devices; listening to the coordination information between terminal devices sent by the second terminal device and maintaining the counter during the operation of the timer; and determining whether to stop sending or generating the coordination information request between terminal devices based on the count value of the counter.

[0006] In an optional implementation, the monitoring of the inter-terminal device coordination information sent by the second terminal device and the maintenance of the counter during the operation of the timer include: in response to the timer exceeding the set duration and the first terminal device not receiving the inter-terminal device coordination information sent by the second terminal device, the first terminal device adding 1 to the count value of the counter; during the operation of the timer, the first terminal device receives the inter-terminal device coordination information sent by the second terminal device, stops the timer, and resets the counter to the initial value.

[0007] In an optional implementation, the determination of whether to stop sending or generating the coordination information request between terminal devices is based on the count value of the counter, including: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating the coordination information request between terminal devices; in response to the count value of the counter being less than the preset value, the first terminal device continues sending or generating the coordination information request between terminal devices.

[0008] Optionally, the preset value is configured by the network side device through radio resource control RRC signaling, or is determined by the UE itself through implementation.

[0009] Optionally, the method also includes: receiving terminal device capability information sent by the second terminal device, the terminal device capability information is used to indicate that the second terminal device supports the inter-terminal device coordination feature; when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request.

[0010] Optionally, the method also includes: receiving terminal device capability information sent by the second terminal device; wherein, the terminal device capability information does not include inter-terminal device coordination capability information; the count value of the counter is greater than or equal to a second preset value, and the first terminal device stops sending or generating the inter-terminal device coordination information request; wherein the first preset value is less than or equal to the second preset value.

[0011] In one implementation, a unicast link exists between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each of the unicast links.

[0012] In an optional implementation, the coordination information between terminal devices carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, the coordination information between terminal devices carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

[0013] In this technical solution, by determining whether to stop sending or generating coordination information requests between terminal devices based on the set duration of the timer and the count value of the counter, the first terminal device can be prevented from continuously sending or generating coordination information requests between terminal devices without knowing the resource allocation mode and / or capabilities of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

[0014] In a second aspect, an embodiment of the present disclosure provides a communication device, which includes a transceiver module and a processing module, wherein the processing module is used to determine whether to stop sending or generate the inter-terminal device coordination information request IUC-request based on the set duration of the timer and the count value of the counter.

[0015] In one implementation, the processing module is specifically used to: start the timer in response to sending or generating the inter-terminal device coordination information request; listen to the inter-terminal device coordination information sent by the second terminal device and maintain the counter during the operation of the timer; and determine whether to stop sending or generating the inter-terminal device coordination information request based on the count value of the counter.

[0016] In an optional implementation, the processing module is specifically used to: in response to the timer exceeding the set duration and the first terminal device not receiving the inter-terminal device coordination information sent by the second terminal device, the first terminal device adds 1 to the count value of the counter; during the operation of the timer, the first terminal device receives the inter-terminal device coordination information sent by the second terminal device, stops the timer, and resets the counter to the initial value.

[0017] In an optional implementation, the processing module is specifically used to: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating the coordination information request between the terminal devices; in response to the count value of the counter being less than the preset value, the first terminal device continues sending or generating the coordination information request between the terminal devices.

[0018] Optionally, the preset value is configured by the network side device through radio resource control RRC signaling, or is determined by the UE itself through implementation.

[0019] Optionally, the transceiver module is used to: receive terminal device capability information sent by the second terminal device, and the terminal device capability information is used to indicate that the second terminal device supports the inter-terminal device coordination feature; the processing module is also used to: when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request.

[0020] Optionally, the transceiver module is also used to: receive terminal device capability information sent by the second terminal device; wherein the terminal device capability information does not include coordination capability information between terminal devices; the processing module is also used to: when the count value of the counter is greater than or equal to a second preset value, the first terminal device stops sending or generating the coordination information request between terminal devices; wherein the first preset value is less than or equal to the second preset value.

[0021] In one implementation, a unicast link exists between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each of the unicast links.

[0022] In an optional implementation, the coordination information between terminal devices carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, the coordination information between terminal devices carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

[0023] In a third aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0024] In a fourth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0025] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0026] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the terminal device executes the method described in the first aspect.

[0027] In a seventh aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0028] In an eighth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a terminal device in implementing the functions described in the first aspect, such as determining or processing at least one of the data and information described in the above method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the terminal device. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0029] In a ninth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0031] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0032] Figure 2 1 is a flow chart of a method for sending an internal coordination information request between directly connected Sidelink terminal devices provided by an embodiment of the present disclosure;

[0033] Figure 3 1 is a flow chart of another method for sending an internal coordination information request between directly connected Sidelink terminal devices provided by an embodiment of the present disclosure;

[0034] Figure 4 is a structural diagram of a communication device provided by an embodiment of the present disclosure;

[0035] Figure 5 is a structural diagram of another communication device provided by an embodiment of the present disclosure;

[0036] Figure 6 It is a schematic structural diagram of a chip provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0037] The embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and are not to be construed as limitations on the present disclosure. In the description of the present disclosure, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: the existence of A alone, the existence of A and B at the same time, and the existence of B alone.

[0038] In order to better understand the method for sending an internal coordination information request between directly connected Sidelink terminal devices disclosed in an embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.

[0039] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to a network side device, a first terminal device and a second terminal device. Figure 1The number and form of the devices shown are for example only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network-side devices, two or more first terminal devices, and two or more second terminal devices may be included. Figure 1 The communication system shown takes a network-side device 101 , a first terminal device 102 , and a second terminal device 103 as an example.

[0040] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0041] The network side device 101 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network side device 101 can be an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network side device. The network side device provided in the embodiment of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network side device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0042] In the embodiments of the present disclosure, the first terminal device 102 and the second terminal device 103 are user-side entities for receiving or transmitting signals, such as mobile phones. The terminal device may also be referred to as a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal device may be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving (self-driving), a wireless terminal device in remote medical surgery (remote medical surgery), a wireless terminal device in a smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.

[0043] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0044] The following describes in detail the method and apparatus for sending an internal coordination information request between directly connected Sidelink terminal devices provided by the present disclosure with reference to the accompanying drawings.

[0045] See Figure 2 , Figure 2 1 is a flow chart of a method for sending an internal coordination information request between directly connected Sidelink terminal devices provided by an embodiment of the present disclosure. The method is executed by a first terminal device. Figure 2 As shown, the method may include but is not limited to the following steps:

[0046] Step S201: Determine whether to stop sending or generating the inter-terminal device coordination information request IUC-request according to the set duration of the timer and the count value of the counter.

[0047] For example, in response to a preset condition being met, the first terminal device starts a timer. If the first terminal device does not receive inter-terminal device coordination information sent by the opposite terminal device within the set duration of the timer, the first terminal device increases the count value of the counter by 1. When the count value of the counter reaches a preset value, the first terminal device stops sending or generating inter-terminal device coordination information requests.

[0048] It should be noted that, in the embodiment of the present disclosure, the first terminal device generates a request for coordination information between terminal devices, which means that the first terminal device uses SL (Sidelink, direct link, also known as side link or side link) resources for new transmission, and includes IUC (inter-UE coordination, coordination between terminal devices) request MAC (Medium Access Control, medium access control) CE (Control Element, control unit) and its sub-header through the LCP (Logical channel prioritization) process, thereby generating a request for coordination information between terminal devices through a multiplexing and assembly process.

[0049] It should be noted that, in the embodiment of the present disclosure, the set duration of the timer can be determined by SL-IUC-ReportTimer (Sidelink inter-UE coordination Report Time, side link terminal device coordination report timer), or can also be determined autonomously by the first terminal device.

[0050] By implementing the embodiments of the present disclosure, it is possible to avoid the first terminal device from continuously sending or generating coordination information requests between terminal devices without knowing the resource allocation mode and / or capabilities of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

[0051] See Figure 3 , Figure 3 1 is a flow chart of a method for sending an internal coordination information request between directly connected Sidelink terminal devices provided by an embodiment of the present disclosure. The method is executed by a first terminal device. Figure 3 As shown, the method may include but is not limited to the following steps:

[0052] Step S301: In response to sending or generating a request for coordination information between terminal devices, start a timer.

[0053] As an example, the first terminal device starts a timer in response to sending the inter-terminal device coordination information request.

[0054] As another example, the first terminal device starts a timer in response to generating the inter-terminal device coordination information request.

[0055] Step S302: During the operation of the timer, the terminal device coordination information sent by the second terminal device is monitored and a counter is maintained.

[0056] For example, the first terminal device monitors the inter-terminal device coordination information sent by the second terminal device during the timer running period, and maintains a counter based on whether the inter-terminal device coordination information is received.

[0057] It should be noted that, in the embodiment of the present disclosure, a direct communication PC5 connection can be established between the first terminal device and the second terminal device, and both the first terminal device and the second terminal device support SL communication.

[0058] Optionally, in some embodiments of the present disclosure, the above-mentioned monitoring of the inter-terminal device coordination information sent by the second terminal device and maintaining the counter during the operation of the timer may include: in response to the timer exceeding the set time length and the first terminal device not receiving the inter-terminal device coordination information sent by the second terminal device, the first terminal device adds 1 to the count value of the counter.

[0059] For example, after the first terminal device starts the timer, in response to the timer's working duration reaching or exceeding a preset duration, and during the timer's working time, the first terminal device does not receive the inter-terminal device coordination information sent by the second terminal device, the first terminal device adds 1 to the count value of the counter.

[0060] Optionally, during the operation of the timer, the first terminal device receives the inter-terminal coordination information sent by the second terminal device, stops the timer, and resets the counter to an initial value. The second terminal sends the corresponding inter-terminal coordination information via IUC (inter-ue coordination) MAC CE.

[0061] For example, after starting the timer, the first terminal device receives the inter-terminal device coordination information sent by the second terminal device during the operation of the timer, then stops the timer and resets the count value of the counter to the initial value.

[0062] It should be noted that, in the embodiment of the present disclosure, the above initial value may be 0.

[0063] Step S303: Determine whether to stop sending or generating the inter-terminal device coordination information request according to the count value of the counter.

[0064] For example, the first terminal device determines whether to stop sending or generating the inter-terminal device coordination information request based on the size relationship between the count value of the counter and the preset value.

[0065] Optionally, in some embodiments of the present disclosure, the above-mentioned determination of whether to stop sending or generating coordination information requests between terminal devices based on the count value of the counter may include: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating coordination information requests between terminal devices.

[0066] As an example, in response to a count value of a counter being greater than or equal to a preset value, the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.

[0067] As another example, in response to a count value of a counter being greater than or equal to a preset value, the first terminal device stops generating the inter-terminal device coordination information request to the second terminal device.

[0068] In an embodiment of the present disclosure, the preset value is a value used by the first terminal device to determine whether to stop sending or generating a coordination information request between terminal devices.

[0069] Optionally, in an embodiment of the present disclosure, the above-mentioned determination of whether to stop sending or generating coordination information requests between terminal devices based on the count value of the counter may also include: in response to the count value of the counter being less than a preset value, the first terminal device continues to send or generate coordination information requests between terminal devices.

[0070] As an example, in response to a count value of a counter being less than a preset value, the first terminal device continues to send an inter-terminal device coordination information request to the second terminal device.

[0071] As another example, in response to a count value of the counter being less than a preset value, the first terminal device continues to generate an inter-terminal device coordination information request to the second terminal device.

[0072] It should be noted that in an embodiment of the present disclosure, when the count value of the counter is equal to a preset value, the first terminal device may stop sending or generating coordination information requests between terminal devices, or the first terminal device may continue to send or generate coordination information requests between terminal devices.

[0073] In an embodiment of the present disclosure, the preset value may be configured by a network-side device through RRC (Radio Resource Control) signaling. The RRC signaling may be dedicated RRC signaling or SIB (Signaling In Band). Alternatively, the first preset value may be preconfigured. Alternatively, the preset value may be predetermined by the first terminal device through implementation.

[0074] It should be noted that, in the embodiments of the present disclosure, the above-mentioned network side device is a network side device that supports SL features.

[0075] It should also be noted that for different scenarios, the first terminal device can use different preset values. For example, if UE capability interaction has been performed between terminal devices, and it is known that the opposite UE (such as the second terminal device) supports the IUC feature, the first terminal device can use the first preset value to do statistics. For another example, if the UE capability interaction performed between terminal devices does not include the IUC capability, and the first terminal device is not sure whether the opposite UE (such as the second terminal device) supports the IUC feature, the first terminal device can use the second preset value to do statistics. Optionally, in some embodiments of the present disclosure, the first terminal device can receive terminal device capability information sent by the second terminal device, and the terminal device capability information is used to indicate that the second terminal device supports the inter-terminal device coordination feature.

[0076] For example, during UE capability interaction between a first terminal device and a second terminal device, the first terminal device may receive terminal device capability information sent by the second terminal device, where the terminal device capability information is used to indicate that the second terminal device supports the inter-terminal coordination (IUC) feature. Since the terminal device capability information may indicate that the second terminal device supports the inter-terminal coordination (IUC) feature, the first terminal device knows that the second terminal device supports the IUC feature. In this scenario, the first terminal device may use a first preset value for statistics to determine whether to stop sending or generating inter-terminal coordination information requests.

[0077] Optionally, if the count value of the counter is greater than or equal to a first preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request.

[0078] In an embodiment of the present disclosure, the first preset value is a value used by the first terminal device to determine whether to stop sending or generating a coordination information request between terminal devices.

[0079] It should be noted that in the embodiments of the present disclosure, the first preset value may be configured by the network-side device via RRC signaling. The RRC signaling may be dedicated RRC signaling or SIB. Alternatively, the first preset value may be preconfigured. Alternatively, the first preset value may be predetermined by the first terminal device.

[0080] As an example, when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.

[0081] As another example, when the count value of the counter is greater than or equal to a first preset value, the first terminal device stops generating the inter-terminal device coordination information request to the second terminal device.

[0082] Optionally, the first terminal device may continue to send or generate the inter-terminal device coordination information request in response to the count value of the counter being less than the first preset value.

[0083] Optionally, in some embodiments of the present disclosure, the first terminal device may receive terminal device capability information sent by the second terminal device; wherein the terminal device capability information does not include inter-terminal device coordination capability information.

[0084] For example, a first terminal device and a second terminal device perform UE capability interaction, and the first terminal device may receive terminal device capability information sent by the second terminal device, wherein the terminal device capability information does not include inter-terminal device coordination capability information. Since the terminal device capability information does not include inter-terminal device coordination capability information, the first terminal device is unsure whether the second terminal device supports the IUC feature. In this scenario, the first terminal device may use a second preset value for statistics to determine whether to stop sending or generating inter-terminal device coordination information requests.

[0085] Optionally, if the count value of the counter is greater than or equal to a second preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request.

[0086] In an embodiment of the present disclosure, the second preset value is a value used by the first terminal device to determine whether to stop sending or generating inter-terminal device coordination information requests. The second preset value is greater than or equal to the first preset value. In some embodiments of the present disclosure, the network-side device may configure the first preset value to be less than or equal to the second preset value through RRC signaling, or the first terminal device may autonomously determine that the first preset value is less than or equal to the second preset value.

[0087] It should be noted that in the embodiments of the present disclosure, the second preset value may be configured by the network-side device via RRC signaling. The RRC signaling may be dedicated RRC signaling or SIB. Alternatively, the second preset value may be preconfigured. Alternatively, the second preset value may be predetermined by the first terminal device.

[0088] As an example, when the count value of the counter is greater than or equal to the second preset value, the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.

[0089] As another example, in response to a count value of a counter being greater than or equal to a second preset value, the first terminal device stops generating the inter-terminal device coordination information request to the second terminal device.

[0090] Optionally, in an embodiment of the present disclosure, the count value of the counter is less than or equal to the second preset value, and the first terminal device continues to send or generate the inter-terminal device coordination information request.

[0091] By implementing the embodiments of the present disclosure, it is possible to determine whether to stop sending or generating coordination information requests between terminal devices based on the set duration of the timer and the count value of the counter, thereby avoiding the first terminal device from continuously sending or generating coordination information requests between terminal devices without knowing the resource allocation mode and / or capabilities of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

[0092] Optionally, in some embodiments of the present disclosure, a unicast link exists between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each unicast link.

[0093] For example, there is a point-to-point communication link between the first terminal device and each second terminal device, and each communication link has a corresponding timer and counter. The first terminal device can maintain the timer and counter corresponding to each communication link according to the methods provided in various embodiments of the present disclosure.

[0094] Optionally, in some embodiments of the present disclosure, the above-mentioned coordination information between terminal devices carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, the coordination information between terminal devices carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

[0095] In the above embodiments of the present disclosure, the methods provided in these embodiments are described from the perspective of a first terminal device. To implement the various functions of the methods provided in these embodiments of the present disclosure, the first terminal device may include hardware structures and software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or hardware structures and software modules. Certain of the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures and software modules.

[0096] See Figure 4 , which is a structural diagram of a communication device 40 provided in an embodiment of the present disclosure. Figure 4 The communication device 40 shown may include a transceiver module 401 and a processing module 402. The transceiver module 401 may include a sending module and / or a receiving module, the sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 401 can implement the sending function and / or the receiving function.

[0097] The communication device 40 may be the first terminal device, or a device in the first terminal device, or a device that can be used in conjunction with the first terminal device.

[0098] The processing module 402 is configured to determine whether to stop sending or generating the inter-terminal device coordination information request IUC-request according to the set duration of the timer and the count value of the counter.

[0099] In one implementation, the processing module 402 is specifically used to: start a timer in response to sending or generating a request for coordination information between terminal devices; listen to the coordination information between terminal devices sent by the second terminal device and maintain a counter during the operation of the timer; and determine whether to stop sending or generating the request for coordination information between terminal devices based on the count value of the counter.

[0100] In an optional implementation, the processing module 402 is specifically used to: in response to the timer exceeding the set time length and the first terminal device not receiving the terminal device coordination information sent by the second terminal device, the first terminal device adds 1 to the count value of the counter; during the operation of the timer, the first terminal device receives the terminal device coordination information sent by the second terminal device, stops the timer, and resets the counter to the initial value.

[0101] In an optional implementation, the processing module 402 is specifically used to: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating coordination information requests between terminal devices; in response to the count value of the counter being less than a preset value, the first terminal device continues sending or generating coordination information requests between terminal devices.

[0102] Optionally, the preset value is configured by the network side device through radio resource control RRC signaling, or is determined by the UE itself through implementation.

[0103] Optionally, the transceiver module 401 is used to: receive terminal device capability information sent by the second terminal device, the terminal device capability information is used to indicate that the second terminal device supports the coordination feature between terminal devices; the processing module 402 is also used to: when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating a request for coordination information between terminal devices.

[0104] Optionally, the transceiver module 401 is also used to: receive terminal device capability information sent by the second terminal device; wherein the terminal device capability information does not include coordination capability information between terminal devices; the processing module 402 is also used to: when the count value of the counter is greater than or equal to the second preset value, the first terminal device stops sending or generating coordination information requests between terminal devices; wherein the first preset value is less than or equal to the second preset value.

[0105] In one implementation, a unicast link exists between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each unicast link.

[0106] In an optional implementation, the coordination information between terminal devices carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, the coordination information between terminal devices carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

[0107] Through the device of the embodiment of the present disclosure, it can be determined whether to stop sending or generating coordination information requests between terminal devices based on the set duration of the timer and the count value of the counter, thereby avoiding continuously sending or generating coordination information requests between terminal devices without knowing the resource allocation mode and / or capabilities of the second terminal device, thereby avoiding signaling waste and reducing interference to other terminal devices.

[0108] See Figure 5 , Figure 5 is a schematic diagram of the structure of another communication device 50 provided in an embodiment of the present disclosure. Communication device 50 can be a network-side device or a terminal device, or a chip, chip system, or processor that supports the network-side device in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports the terminal device in implementing the above-mentioned method. This device can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0109] The communication device 50 may include one or more processors 501. The processor 501 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0110] Optionally, the communication device 50 may further include one or more memories 502, on which a computer program 503 may be stored. The processor 501 executes the computer program 503 to cause the communication device 50 to perform the method described in the above method embodiment. Optionally, the memory 502 may also store data. The communication device 50 and the memory 502 may be provided separately or integrated together.

[0111] Optionally, the communication device 50 may further include a transceiver 504 and an antenna 505. The transceiver 504 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 504 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.

[0112] Optionally, the communication device 50 may further include one or more interface circuits 506. The interface circuit 506 is configured to receive code instructions and transmit the code instructions to the processor 501. The processor 501 executes the code instructions to enable the communication device 50 to perform the method described in the above method embodiment.

[0113] The communication device 50 is a first terminal device: the processor 501 is used to execute Figure 2 Step S201 in the process; Figure 3 Steps S301, S302 and S303 in .

[0114] In one implementation, the processor 501 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0115] In one implementation, the processor 501 may store a computer program that runs on the processor 501 and enables the communication device 50 to perform the method described in the above method embodiment. The computer program may be fixed in the processor 501, in which case the processor 501 may be implemented by hardware.

[0116] In one implementation, the communication device 50 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0117] The scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited thereto. Figure 5 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0118] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0119] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0120] (3) ASIC, such as modem;

[0121] (4) Modules that can be embedded in other devices;

[0122] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network-side devices, cloud devices, artificial intelligence devices, etc.;

[0123] (6)Others, etc.

[0124] For the case where the communication device may be a chip or a chip system, see Figure 6 Schematic diagram of the chip structure shown. Figure 6 The chip shown includes a processor 601 and an interface 602. There may be one or more processors 601 and there may be more than one interface 602.

[0125] The processor 601 is configured to determine whether to stop sending or generating the inter-terminal device coordination information request IUC-request according to a set duration of the timer and a count value of the counter.

[0126] In one implementation, the processor 601 is specifically used to: start a timer in response to sending or generating a request for coordination information between terminal devices; listen to the coordination information between terminal devices sent by the second terminal device and maintain a counter during the operation of the timer; and determine whether to stop sending or generating the request for coordination information between terminal devices based on the count value of the counter.

[0127] In an optional implementation, the processor 601 is specifically used to: in response to the timer exceeding the set duration and the first terminal device not receiving the terminal device coordination information sent by the second terminal device, the first terminal device adds 1 to the count value of the counter; during the operation of the timer, the first terminal device receives the terminal device coordination information sent by the second terminal device, stops the timer, and resets the counter to the initial value.

[0128] In an optional implementation, the processor 601 is specifically used to: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating coordination information requests between terminal devices; in response to the count value of the counter being less than the preset value, the first terminal device continues sending or generating coordination information requests between terminal devices.

[0129] Optionally, the preset value is configured by the network side device through radio resource control RRC signaling, or is determined by the UE itself through implementation.

[0130] Optionally, the interface 602 is used to: receive terminal device capability information sent by the second terminal device, the terminal device capability information is used to indicate that the second terminal device supports the coordination feature between terminal devices; the processor 601 is also used to: when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating a request for coordination information between terminal devices.

[0131] Optionally, the interface 602 is also used to: receive terminal device capability information sent by the second terminal device; wherein the terminal device capability information does not include coordination capability information between terminal devices; the processor 601 is also used to: when the count value of the counter is greater than or equal to a second preset value, the first terminal device stops sending or generating coordination information requests between terminal devices; wherein the first preset value is less than or equal to the second preset value.

[0132] In one implementation, a unicast link exists between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each unicast link.

[0133] In an optional implementation, the coordination information between terminal devices carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, the coordination information between terminal devices carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

[0134] Optionally, the chip further includes a memory 603, which is used to store necessary computer programs and data.

[0135] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0136] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0137] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0138] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program 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 program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0139] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0140] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0141] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0142] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0143] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

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

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

Claims

1. A method for sending an internal coordination information request between directly connected sidelink terminal devices, characterized in that: The method is performed by a first terminal device, and includes: In response to sending or generating the inter-terminal device coordination information request IUC-request, starting a timer; In response to the timer exceeding a set duration and the first terminal device not receiving the inter-terminal device coordination information sent by the second terminal device, the first terminal device increases the count value of the counter by 1; In response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request, wherein the preset value is determined based on the capability information of the second terminal device.

2. The method according to claim 1, wherein The method further comprises: During the operation of the timer, the first terminal device receives the inter-terminal device coordination information sent by the second terminal device, stops the timer, and resets the counter to an initial value.

3. The method according to claim 2, wherein The method further comprises: In response to the count value of the counter being less than the preset value, the first terminal device continues to send or generate the inter-terminal device coordination information request.

4. The method according to claim 3, wherein The preset value is configured by the network side device through radio resource control RRC signaling, or is determined by the UE itself through implementation.

5. The method according to claim 3 or 4, wherein: Also includes: Receive terminal device capability information sent by the second terminal device, where the terminal device capability information is used to indicate that the second terminal device supports the inter-terminal device coordination feature; when the count value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request.

6. The method according to claim 3 or 4, wherein: Also includes: Receive terminal device capability information sent by the second terminal device; wherein, the terminal device capability information does not include inter-terminal device coordination capability information; when the count value of the counter is greater than or equal to a second preset value, the first terminal device stops sending or generating the inter-terminal device coordination information request; wherein the first preset value is less than or equal to the second preset value.

7. The method according to any one of claims 1 to 4, characterized in that There is a unicast link between the first terminal device and one or more second terminal devices, and the first terminal device maintains a corresponding timer and counter on each of the unicast links.

8. The method according to any one of claims 1 to 4, characterized in that The inter-terminal device coordination information carries preferred resource set indication information, and the preferred resource set indication information is used to indicate that the first terminal device can only use the resources indicated in the preferred resource set to send data to the second terminal device; or, The inter-terminal device coordination information carries non-preferred resource set indication information, and the non-preferred resource set indication information is used to indicate that the first terminal device cannot use the resources indicated in the non-preferred resource set to send data to the second terminal device.

9. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory, so that the device performs the method according to any one of claims 1 to 8.

10. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 1 to 8 to be implemented.

Images