WO2024026887A1 - 直连sidelink终端设备间内部协调信息请求的发送方法及其装置 - Google Patents

直连sidelink终端设备间内部协调信息请求的发送方法及其装置 Download PDF

Info

Publication number
WO2024026887A1
WO2024026887A1 PCT/CN2022/110706 CN2022110706W WO2024026887A1 WO 2024026887 A1 WO2024026887 A1 WO 2024026887A1 CN 2022110706 W CN2022110706 W CN 2022110706W WO 2024026887 A1 WO2024026887 A1 WO 2024026887A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
inter
coordination information
counter
timer
Prior art date
Application number
PCT/CN2022/110706
Other languages
English (en)
French (fr)
Inventor
杨星
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280003015.6A priority Critical patent/CN115606313A/zh
Priority to PCT/CN2022/110706 priority patent/WO2024026887A1/zh
Publication of WO2024026887A1 publication Critical patent/WO2024026887A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method and device for sending internal coordination information requests between directly connected sidelink terminal devices.
  • the UE currently using SL for communication does not know whether the opposite UE is in mode 1 or mode 2, and does not know whether the opposite UE supports the IUC feature.
  • 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, causing a waste of signaling and affecting the performance of other UEs. Communication causes interference.
  • Embodiments of the present disclosure provide a method and device 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 and workshop communication long-term evolution technology (V2X). long term evolution-vehicle (LTE-V), vehicle to vehicle (V2V) communication, etc., or can be used in fields such as intelligent driving and intelligent connected vehicles, by setting the timer and counting according to the counter value, determine whether to stop sending or generating inter-terminal device coordination information requests, which can prevent the first terminal device from continuing to send or generate inter-terminal device coordination information without knowing the resource allocation mode and/or capabilities of the second terminal device. request, thereby avoiding signaling waste and reducing interference to other terminal devices.
  • V2X vehicle to everything
  • V2X workshop communication long-term evolution technology
  • LTE-V long term evolution-vehicle
  • V2V vehicle to vehicle
  • embodiments of the present disclosure provide a method for sending internal coordination information requests between directly connected sidelink terminal devices.
  • the method is executed by the first terminal device.
  • the method includes: according to the set duration of the timer and the counter. Count value to determine whether to stop sending or generating the inter-terminal device coordination information request IUC-request.
  • determining whether to stop continuing to send or generate the inter-terminal device coordination information request based on the set duration of the timer and the count value of the counter includes: responding to the completion of sending or generating the coordination information request between the terminal devices. After the inter-terminal coordination information is requested, start the timer; during the operation of the timer, monitor the inter-terminal coordination information sent by the second terminal device and maintain the counter; determine whether to stop and continue based on the count value of the counter Send or generate the inter-terminal device coordination information request.
  • the step of monitoring the inter-terminal device coordination information sent by the second terminal device and maintaining the counter during the running of the timer includes: in response to the timer exceeding the device The timing is long and 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; 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.
  • determining whether to stop continuing to send or generate the inter-terminal device coordination information request based on the count value of the counter includes: responding that the count value of the counter is greater than or equal to a predetermined value.
  • the first terminal device stops sending or generating the inter-terminal device coordination information request; 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. Coordinate information requests between end devices.
  • the preset value is configured by the network side device through radio resource control RRC signaling, or the UE determines it by itself.
  • the method further includes: receiving 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 inter-terminal device coordination features; the counter If the count value 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.
  • the method further 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 is equal to the 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.
  • the first terminal device has a unicast link with one or more second terminal devices, and the first terminal device controls the corresponding timer and counter on each of the unicast links. Perform maintenance.
  • 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 preferred resource set.
  • the indicated resources are sent 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 resource indicated in the non-preferred resource set sends data to the second terminal device.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a transceiver module and a processing module, wherein the processing module is configured to: determine whether to stop continuing to send according to the set duration of the timer and the count value of the counter. Or generate the inter-terminal device coordination information request IUC-request.
  • the processing module is specifically configured to: start the timer in response to sending or generating the inter-terminal device coordination information request; and monitor the second terminal device during the running of the timer. Send inter-terminal device coordination information and maintain the counter; determine whether to stop continuing to send or generate the inter-terminal device coordination information request according to the count value of the counter.
  • the processing module is specifically configured to: respond to the timer exceeding the set duration and the first terminal device not receiving the terminal device sent by the second terminal device. Inter-terminal coordination information, the first terminal device adds 1 to the count value of the counter; during the running of the timer, the first terminal device receives the inter-terminal device coordination information sent by the second terminal device , stop the timer, and reset the counter to its initial value.
  • the processing module is specifically configured to: in response to the count value of the counter being greater than or equal to a preset value, the first terminal device stops continuing to send or generate the inter-terminal device coordination.
  • Information request in response to the count value of the counter being less than the preset value, the first terminal device continues to send or generates the inter-terminal device coordination information request.
  • the preset value is configured by the network side device through radio resource control RRC signaling, or the UE determines it by itself.
  • the transceiver module is configured to: 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 inter-terminal device coordination features; the processing The module is also configured to: when 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.
  • the transceiver module is also configured to: 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; the processing module is also configured 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 the inter-terminal device coordination information request; wherein the first preset value is less than or equal to the second preset value value.
  • the first terminal device has a unicast link with one or more second terminal devices, and the first terminal device controls the corresponding timer and counter on each of the unicast links. Perform maintenance.
  • 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 preferred resource set.
  • the indicated resources are sent 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 resource indicated in the non-preferred resource set sends data to the second terminal device.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the first aspect.
  • embodiments of the present disclosure provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal device. When the instructions are executed, the terminal device is caused to perform the method described in the first aspect. .
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a chip system that includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing the data involved in the above method and at least one of the information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flowchart of a method for sending internal coordination information requests between directly connected sidelink terminal devices provided by an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of another method for sending internal coordination information requests between directly connected sidelink terminal devices provided by an embodiment of the present disclosure
  • Figure 4 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 5 is a schematic structural diagram of another communication device provided by an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • FIG. 1 is a schematic architectural diagram 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.
  • the number and form of devices shown in Figure 1 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. Practical applications may include two or more network side devices, two or more first terminal devices, and two or more second terminal devices.
  • the communication system shown in Figure 1 takes as an example a network side device 101, a first terminal device 102 and a second terminal device 103.
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the network side device 101 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the network side device 101 can be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other future mobile communication systems.
  • eNB evolved base station
  • TRP transmission reception point
  • gNB next generation base station
  • WiFi wireless fidelity
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the network side equipment.
  • the network-side device may be composed of a centralized unit (central unit, CU) and a distributed unit (DU), where the CU may also be called a control unit (control unit), using CU-
  • the structure of DU can separate the protocol layers of network-side equipment, such as base stations, with some protocol layer functions placed under centralized control by the CU, while the remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the first terminal device 102 and the second terminal device 103 in the embodiment of the present disclosure are an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can 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 (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • Figure 2 is a schematic flowchart of a method for sending internal coordination information requests between directly connected sidelink terminal devices according to an embodiment of the present disclosure. The method is executed by the first terminal device. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step S201 Determine whether to stop continuing to send or generate an inter-terminal device coordination information request IUC-request based on the set duration of the timer and the count value of the counter.
  • the first terminal device starts a timer in response to meeting the preset conditions. If the first terminal device does not receive the inter-terminal device coordination information sent by the opposite terminal device within the set time of the timer, the count value of the counter is increased by 1. . And when the count value of the counter reaches a preset value, it stops sending or generating inter-terminal device coordination information requests.
  • the first terminal device generating an inter-terminal device coordination information request means that the first terminal device uses SL (sidelink, sidelink) resources for new transmission, and uses LCP (Logical channel prioritization , logical channel priority) process includes the IUC (inter-UE coordination, collaboration between terminal equipment) request MAC (Medium Access Control, medium access control) CE (Control Element, control unit) and its sub-headers, thereby through the complex Use and assembly processes to generate inter-end device coordination information requests.
  • SL sidelink, sidelink
  • LCP Logical channel prioritization , logical channel priority
  • IUC inter-UE coordination, collaboration between terminal equipment
  • MAC Medium Access Control, medium access control
  • CE Control Element, control unit
  • the set duration of the timer can be determined by sl-IUC-ReportTimer (sidelink inter-UE coordination Report Time, side link inter-UE coordination report timer), or, It can also be determined independently by the first terminal device.
  • the first terminal device By implementing the embodiments of the present disclosure, it is possible to avoid the first terminal device from continuously sending 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 reduce interference to other terminal equipment.
  • Figure 3 is a schematic flowchart of a method for sending internal coordination information requests between directly connected sidelink terminal devices according to an embodiment of the present disclosure. The method is executed by the first terminal device. As shown in Figure 3, the method may include but is not limited to the following steps:
  • Step S301 In response to sending or generating an inter-terminal device coordination information request, start a timer.
  • the first terminal device starts a timer in response to sending the inter-terminal device coordination information request.
  • the first terminal device starts a timer in response to generating an inter-terminal device coordination information request.
  • Step S302 Monitor the inter-terminal device coordination information sent by the second terminal device and maintain the counter during the running of the timer.
  • the first terminal device monitors the inter-terminal device coordination information sent by the second terminal device during the running of the timer, and maintains a counter based on whether the inter-terminal device coordination information is received.
  • 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.
  • the above-mentioned monitoring of inter-terminal device coordination information sent by the second terminal device and maintaining the counter during the running of the timer may include: in response to the timer exceeding the set duration and the first The terminal device does not receive the inter-terminal device coordination information sent by the second terminal device, and the first terminal device increases the count value of the counter by 1.
  • the first terminal device After starting the timer, the first terminal device responds that the working time of the timer reaches or exceeds the preset time length, and within the working time of the timer, the first terminal device does not receive any information from the second terminal device. If the first terminal device sends coordination information between terminal devices, the first terminal device increases the count value of the counter by 1.
  • 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.
  • the second terminal sends corresponding inter-device coordination information through IUC (inter-ue coordination) MAC CE.
  • the first terminal device receives the inter-terminal device coordination information sent by the second terminal device during the running of the timer, stops the running of the timer, and resets the count value of the counter to the initial value. value.
  • the above initial value may be 0.
  • Step S303 Determine whether to stop sending or generating inter-terminal device coordination information requests according to the count value of the counter.
  • the first terminal device determines whether to stop sending or generating an inter-terminal device coordination information request based on the relationship between the count value of the counter and the preset value.
  • the above-mentioned determination of whether to stop sending or generating inter-terminal device coordination information requests 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 inter-terminal device coordination information requests.
  • the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.
  • the first terminal device stops generating the inter-terminal device coordination information request to the second terminal device in response to the count value of the counter being greater than or equal to the preset value.
  • the above-mentioned preset value is a value used by the first terminal device to determine whether to stop sending or generating an inter-terminal device coordination information request.
  • the above-mentioned determination of whether to stop sending or generating inter-terminal device coordination information requests based on the count value of the counter may also include: in response to the count value of the counter being less than the preset value, first The terminal device continues to send or generate inter-terminal device coordination information requests.
  • the first terminal device in response to the count value of the counter being less than the preset value, continues to send the inter-terminal device coordination information request to the second terminal device.
  • the first terminal device in response to the count value of the counter being less than the preset value, continues to generate an inter-terminal device coordination information request to the second terminal device.
  • the first terminal device may stop sending or generating inter-terminal device coordination information requests, or the first terminal device may also continue to send or generate inter-terminal device coordination information requests. Send or generate inter-end device coordination information requests.
  • the above preset value can be configured by the network side device through RRC (Radio Resource Control, Radio Resource Control) signaling.
  • the RRC signaling may be dedicated RRC signaling or SIB (Signaling In Band).
  • SIB Signaling In Band
  • the above-mentioned first preset value may also be preconfigured.
  • the above preset value may also be predetermined by the first terminal device through implementation.
  • the above-mentioned network side device is a network side device supporting the SL feature.
  • the first terminal device can use different preset values. For example, if there has been UE capability interaction 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 make statistics. For another example, if the UE capability interaction between terminal devices does not include IUC capabilities, 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 for statistics.
  • 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 device coordination feature. .
  • 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, and the terminal device capability information is used to indicate to the second terminal
  • the device supports the Inter-End Device Coordination (IUC) feature. Since the terminal device capability information can indicate that the second terminal device supports the inter-terminal device coordination (IUC) feature, the first terminal device knows that the second terminal device supports the IUC feature. In this scenario, the first terminal device can use the first The default value is used for statistics to determine whether to stop sending or generate coordination information requests between terminal devices.
  • IUC Inter-End Device Coordination
  • the first terminal device stops sending or generating inter-terminal device coordination information requests.
  • the first 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 above-mentioned first preset value may be configured by the network side device through RRC signaling.
  • the RRC signaling may be dedicated RRC signaling or SIB.
  • the above-mentioned first preset value may also be preconfigured.
  • the above-mentioned first preset value may be predetermined by the first terminal device.
  • the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.
  • the first terminal device stops generating an inter-terminal device coordination information request to the second terminal device.
  • the first terminal device may continue to send or generate an inter-terminal device coordination information request in response to the count value of the counter being less than the first preset value.
  • 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.
  • a first terminal device and a second terminal device perform UE capability interaction.
  • the first terminal device may receive terminal device capability information sent by the second terminal device.
  • the terminal device capability information does not include coordination between terminal devices. Capability information. Since the terminal device capability information does not include inter-terminal device coordination capability information, the first terminal device is not sure whether the second terminal device supports the IUC feature. In this scenario, the first terminal device can use the second preset value to Make statistics to determine whether to stop sending or generate coordination information requests between terminal devices.
  • the first terminal device stops sending or generating inter-terminal device coordination information requests.
  • 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 above-mentioned first preset value.
  • 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 independently determine that the first preset value is less than or equal to the second preset value. default value.
  • the above-mentioned second preset value may be configured by the network side device through RRC signaling.
  • the RRC signaling may be dedicated RRC signaling or SIB.
  • the above-mentioned second preset value may also be preconfigured.
  • the above-mentioned second preset value may be predetermined by the first terminal device.
  • the first terminal device stops sending the inter-terminal device coordination information request to the second terminal device.
  • the first terminal device stops generating an inter-terminal device coordination information request to the second terminal device.
  • 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 an inter-terminal device coordination information request.
  • a first terminal device has a unicast link with one or more second terminal devices, and the first terminal device controls the corresponding timer and counter on each unicast link. Perform maintenance.
  • each communication link has a corresponding timer and counter.
  • the first terminal device can provide according to various embodiments of the present disclosure. Method to maintain the timers and counters corresponding to each communication link.
  • the above-mentioned 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 resources indicated in the preferred resource set.
  • the second terminal device sends data.
  • the method provided by the embodiments of the present disclosure is introduced from the perspective of the first terminal device.
  • the first terminal device may include a hardware structure and a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 4 is a schematic structural diagram of a communication device 40 provided by an embodiment of the present disclosure.
  • the communication device 40 shown in FIG. 4 may include a transceiver module 401 and a processing module 402.
  • the transceiving module 401 may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module 401 may implement the sending function and/or the receiving function.
  • the communication device 40 may be a first terminal device, a device in the first terminal device, or a device that can be used in conjunction with the first terminal device.
  • the processing module 402 is used to determine whether to stop continuing to send or generate an inter-terminal device coordination information request IUC-request according to the set duration of the timer and the count value of the counter.
  • the processing module 402 is specifically configured to: start a timer in response to sending or generating an inter-terminal device coordination information request; and monitor the inter-terminal device coordination information sent by the second terminal device during the running of the timer. And maintain the counter; based on the count value of the counter, determine whether to stop sending or generate a coordination information request between terminal devices.
  • the processing module 402 is specifically configured 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 will The count value of the counter is increased by 1; during the running 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.
  • the processing module 402 is specifically configured to: in response to the count value of the counter being greater than or equal to the preset value, the first terminal device stops sending or generating an inter-terminal device coordination information request; in response to the count value of the counter If the count value is less than the preset value, the first terminal device continues to send or generates an inter-terminal device coordination information request.
  • the preset value is configured by the network side device through radio resource control RRC signaling, or the UE determines it by itself.
  • the transceiver module 401 is used to: 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; the processing module 402 is also used to: count the counter If the value is greater than or equal to the first preset value, the first terminal device stops sending or generating inter-terminal device coordination information requests.
  • the transceiver module 401 is also used to: receive the 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 processing module 402 is also used to: count the value of the counter is greater than or equal to the second preset value, the first terminal device stops sending or generating inter-terminal device coordination information requests; wherein the first preset value is less than or equal to the second preset value.
  • a first terminal device has a unicast link with one or more second terminal devices, and the first terminal device maintains corresponding timers and counters on each unicast link.
  • 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 the second terminal device.
  • Send data 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.
  • the device of the embodiment of the present disclosure it can be determined whether to stop sending or generating an inter-terminal device coordination information request according to the set duration of the timer and the count value of the counter, thereby avoiding not knowing the resource allocation mode of the second terminal device and / or capabilities, continue to send or generate coordination information requests between terminal devices, thereby avoiding signaling waste and reducing interference to other terminal devices.
  • FIG. 5 is a schematic structural diagram of another communication device 50 provided by an embodiment of the present disclosure.
  • the communication device 50 may be a network-side device, a terminal device, a chip, a chip system, a processor, etc. that supports the network-side device to implement the above method, or a chip or a chip system that supports the terminal device to implement the above method. , or processor, etc.
  • the device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 50 may include one or more processors 501 .
  • the processor 501 may be a general-purpose processor or a special-purpose processor, or the like. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device 50 may also include one or more memories 502, on which a computer program 503 may be stored.
  • the processor 501 executes the computer program 503, so that the communication device 50 performs the steps described in the above method embodiments. method.
  • the memory 502 may also store data.
  • the communication device 50 and the memory 502 can be provided separately or integrated together.
  • the communication device 50 may also include a transceiver 504 and an antenna 505.
  • the transceiver 504 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 504 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 50 may also include one or more interface circuits 506.
  • the interface circuit 506 is used to receive code instructions and transmit them to the processor 501 .
  • the processor 501 executes the code instructions to cause the communication device 50 to perform the method described in the above method embodiment.
  • the communication device 50 is a first terminal device: the processor 501 is configured to execute step S201 in Figure 2; and execute step S301, step S302 and step S303 in Figure 3.
  • the processor 501 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 501 may store a computer program, and the computer program runs on the processor 501 to cause the communication device 50 to perform the method described in the above method embodiment.
  • the computer program may be solidified in the processor 501, in which case the processor 501 may be implemented by hardware.
  • the communication device 50 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, 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 (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited to FIG. 5 .
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • the communication device may be a chip or a chip system
  • the communication device may be a chip or a chip system
  • the chip shown in Figure 6 includes a processor 601 and an interface 602.
  • the number of processors 601 may be one or more, and the number of interfaces 602 may be multiple.
  • the processor 601 is configured to determine whether to stop sending or generate an inter-terminal device coordination information request IUC-request based on the set duration of the timer and the count value of the counter.
  • the processor 601 is specifically configured to: start a timer in response to sending or generating an inter-terminal device coordination information request; and monitor the inter-terminal device coordination information sent by the second terminal device during the running of the timer. And maintain the counter; based on the count value of the counter, determine whether to stop sending or generate a coordination information request between terminal devices.
  • the processor 601 is specifically configured 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 will The count value of the counter is increased by 1; during the running 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.
  • the processor 601 is specifically configured 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 an inter-terminal device coordination information request; in response to the count value of the counter If the count value is less than the preset value, the first terminal device continues to send or generates an inter-terminal device coordination information request.
  • the preset value is configured by the network side device through radio resource control RRC signaling, or the UE determines it by itself.
  • the interface 602 is used to: 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; the processor 601 is also used to: count the value of the counter is greater than or equal to the first preset value, the first terminal device stops sending or generating inter-terminal device coordination information requests.
  • the interface 602 is also configured to: 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; the processor 601 is also configured to: the count value of the counter is greater than or equal to the second preset value, the first terminal device stops sending or generating inter-terminal device coordination information requests; wherein the first preset value is less than or equal to the second preset value.
  • a first terminal device has a unicast link with one or more second terminal devices, and the first terminal device maintains corresponding timers and counters on each unicast link.
  • 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 the second terminal device.
  • Send data 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.
  • the chip also includes a memory 603, which is used to store necessary computer programs and data.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present disclosure are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种直连sidelink终端设备间内部协调信息请求的发送方法及其装置，可以应用于车联网、V2X、V2V等***中，其中，该方法由第一终端设备执行，该方法包括：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求。通过实施本公开实施例，可以避免第一终端设备在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。

Description

直连sidelink终端设备间内部协调信息请求的发送方法及其装置 技术领域
本公开涉及通信技术领域，尤其涉及一种直连sidelink终端设备间内部协调信息请求的发送方法及其装置。
背景技术
相关技术中，在不同UE(user equipment，用户设备)之间通过侧链路(sidelink，SL)通信时，有两种发送资源分配方式，一种是网络动态调度的方式(mode 1)，另一种是UE在网络广播的资源池中自主选择的方式(mode 2)。为了辅助对端UE更好地进行资源选择，避免和其他UE发生冲突，R17(Release-17)标准引入了IUC(inter-UE coordination，用户设备间协作)，使得处于mode2的UE-A可以给处于mode 2的对端UE-B发送用户间协作介质访问控制单元IUCMAC(Medium Access Control，介质访问控制)CE(Control Element，控制单元)。但目前使用SL进行通信的UE并不知道对端UE处于mode1还是mode2，并且不知道对端UE是否支持IUC特性。针对基于请求的IUC机制，如果UE-B向UE-A发送IUC请求，但是UE-A没有反馈IUC信息，那么UE-B会一直持续发送IUC请求，从而造成信令浪费，并对其他UE的通信造成干扰。
发明内容
本公开实施例提供一种直连sidelink终端设备间内部协调信息请求的发送方法及其装置，可以应用于车联网，例如车与任何事物(vehicle to everything，V2X)通信、车间通信长期演进技术(long term evolution-vehicle，LTE-V)、车辆与车辆(vehicle to vehicle，V2V)通信等，或可以用于智能驾驶，智能网联车等领域，通过根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，可以避免第一终端设备在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。
第一方面，本公开实施例提供一种直连sidelink终端设备间内部协调信息请求的发送方法，所述方法由第一终端设备执行，所述方法包括：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求IUC-request。
在一种实现方式中，所述根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求，包括：响应于发送完或生成所述终端设备间协调信息请求后，启动所述定时器；在所述定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护所述计数器；根据所述计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求。
在一种可选地实现方式中，所述在所述定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护所述计数器，包括：响应于所述定时器超过所述设定时长且所述第一终端设备未接收到所述第二终端设备发送的终端设备间协调信息，所述第一终端设备将所述计数器的计数值加1；在所述定时器的运行期间，所述第一终端设备接收到所述第二终端设备发送的终端设备间协调信息，停止所述定时器，并将所述计数器重置为初始值。
在一种可选地实现方式中，所述根据所述计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求，包括：响应于所述计数器的计数值大于或等于预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；响应于所述计数器的计数值小于所述预设值，所述第一终端设备继续发送或生成所述终端设备间协调信息请求。
可选地，所述预设值为网络侧设备通过无线资源控制RRC信令配置的，或者，UE通过实现自己确定。
可选地，所述方法还包括：接收所述第二终端设备发送的终端设备能力信息，所述终端设备能力信息用于指示所述第二终端设备支持终端设备间协调特性；所述计数器的计数值大于或等于第一预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求。
可选地，所述方法还包括：接收所述第二终端设备发送的终端设备能力信息；其中，所述终端设备能力信息中未包含终端设备间协调能力信息；所述计数器的计数值大于或等于第二预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；其中第一预设值小于或等于第二预设值。
在一种实现方式中，所述第一终端设备与一个或多个第二终端设备存在单播链路，所述第一终端 设备对每个所述单播链路上对应的定时器和计数器进行维护。
在一种可选地实现方式中，所述终端设备间协调信息中携带首选资源集合指示信息，所述首选资源集合指示信息用于指示所述第一终端设备只能使用所述首选资源集合中指示的资源给所述第二终端设备发送数据；或者，所述终端设备间协调信息中携带非首选资源集合指示信息，所述非首选资源集合指示信息用于指示所述第一终端设备不能使用所述非首选资源集合中指示的资源给所述第二终端设备发送数据。
在该技术方案中，通过根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，可以避免第一终端设备在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。
第二方面，本公开实施例提供一种通信装置，该装置包括收发模块和处理模块，其中，所述处理模块用于：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求IUC-request。
在一种实现方式中，所述处理模块具体用于：响应于发送完或生成所述终端设备间协调信息请求后，启动所述定时器；在所述定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护所述计数器；根据所述计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求。
在一种可选地实现方式中，所述处理模块具体用于：响应于所述定时器超过所述设定时长且所述第一终端设备未接收到所述第二终端设备发送的终端设备间协调信息，所述第一终端设备将所述计数器的计数值加1；在所述定时器的运行期间，所述第一终端设备接收到所述第二终端设备发送的终端设备间协调信息，停止所述定时器，并将所述计数器重置为初始值。
在一种可选地实现方式中，所述处理模块具体用于：响应于所述计数器的计数值大于或等于预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；响应于所述计数器的计数值小于所述预设值，所述第一终端设备继续发送或生成所述终端设备间协调信息请求。
可选地，所述预设值为网络侧设备通过无线资源控制RRC信令配置的，或者，UE通过实现自己确定。
可选地，所述收发模块用于：接收所述第二终端设备发送的终端设备能力信息，所述终端设备能力信息用于指示所述第二终端设备支持终端设备间协调特性；所述处理模块还用于：所述计数器的计数值大于或等于第一预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求。
可选地，所述收发模块还用于：接收所述第二终端设备发送的终端设备能力信息；其中，所述终端设备能力信息中未包含终端设备间协调能力信息；所述处理模块还用于：所述计数器的计数值大于或等于第二预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；其中第一预设值小于或等于第二预设值。
在一种实现方式中，所述第一终端设备与一个或多个第二终端设备存在单播链路，所述第一终端设备对每个所述单播链路上对应的定时器和计数器进行维护。
在一种可选地实现方式中，所述终端设备间协调信息中携带首选资源集合指示信息，所述首选资源集合指示信息用于指示所述第一终端设备只能使用所述首选资源集合中指示的资源给所述第二终端设备发送数据；或者，所述终端设备间协调信息中携带非首选资源集合指示信息，所述非首选资源集合指示信息用于指示所述第一终端设备不能使用所述非首选资源集合中指示的资源给所述第二终端设备发送数据。
第三方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第四方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第五方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第七方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第八方面，本公开提供一种芯片***，该芯片***包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片***还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
第九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种通信***的架构示意图；
图2是本公开实施例提供的一种直连sidelink终端设备间内部协调信息请求的发送方法的流程示意图；
图3是本公开实施例提供的另一种直连sidelink终端设备间内部协调信息请求的发送方法的流程示意图；
图4是本公开实施例提供的一种通信装置的结构示意图；
图5是本公开实施例提供的另一种通信装置的结构示意图；
图6是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。其中，在本公开的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
为了更好的理解本公开实施例公开的一种直连sidelink终端设备间内部协调信息请求的发送方法，下面首先对本公开实施例适用的通信***进行描述。
请参见图1，图1为本公开实施例提供的一种通信***的架构示意图。该通信***可包括但不限于一个网络侧设备、一个第一终端设备和一个第二终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络侧设备，两个或两个以上的第一终端设备，两个或两个以上的第二终端设备。图1所示的通信***以包括网络侧设备101、第一终端设备102和第二终端设备103为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信***。例如：长期演进(long term evolution，LTE)***、第五代(5th generation，5G)移动通信***、5G新空口(new radio，NR)***，或者其他未来的新型移动通信***等。
本公开实施例中的网络侧设备101是网络侧的一种用于发射或接收信号的实体。例如，网络侧设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR***中的下一代基站(next generation NodeB，gNB)、其他未来移动通信***中的基站或无线保真(wireless fidelity，WiFi)***中的接入节点等。本公开的实施例对网络侧设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络侧设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络侧设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的第一终端设备102和第二终端设备103是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全 (transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信***是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着***架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本公开所提供的直连sidelink终端设备间内部协调信息请求的发送方法及其装置进行详细地介绍。
请参见图2，图2是本公开实施例提供的一种直连sidelink终端设备间内部协调信息请求的发送方法的流程示意图。该方法由第一终端设备执行。如图2所示，该方法可以包括但不限于如下步骤：
步骤S201：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求IUC-request。
举例而言，第一终端设备响应于满足预设条件则启动定时器，在定时器的设定时长内未收到对端终端设备发送的终端设备间协调信息，则将计数器的计数值加1。并在计数器的计数值达到预先设定的数值时，停止继续发送或生成终端设备间协调信息请求。
需要说明的是，在本公开的实施例中，第一终端设备生成终端设备间协调信息请求是指第一终端设备使用SL(sidelink，侧行链路)资源进行新传，并且通过LCP(Logicalchannelprioritization，逻辑信道优先级)过程将IUC(inter-UE coordination，终端设备间协作)request MAC(Medium Access Control，介质访问控制)CE(Control Element，控制单元)以及它的子头包含进去，从而通过复用和组装流程生成终端设备间协调信息请求。
需要说明的是，在本公开的实施例中，定时器的设定时长可以由sl-IUC-ReportTimer(sidelink inter-UE coordination Report Time，侧链路终端设备间协作报告定时器)确定，或者，也可以由第一终端设备自主确定。
通过实施本公开实施例，可以避免第一终端设备在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。
请参见图3，图3是本公开实施例提供的一种直连sidelink终端设备间内部协调信息请求的发送方法的流程示意图。该方法由第一终端设备执行。如图3所示，该方法可以包括但不限于如下步骤：
步骤S301：响应于发送完或生成终端设备间协调信息请求后，启动定时器。
作为一种示例，第一终端设备响应于发送完终端设备间协调信息请求，启动定时器。
作为另一种示例，第一终端设备响应于生成终端设备间协调信息请求，启动定时器。
步骤S302：在定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护计数器。
举例而言，第一终端设备在定时器运行期间监听第二终端设备发送的终端设备间协调信息，并基于是否收到该终端设备间协调信息维护计数器。
需要说明的是，在本公开的实施例中，第一终端设备和第二终端设备之间可以建立直连通信PC5连接，并且第一终端设备和第二终端设备都支持SL通信。
可选地，在本公开的一些实施例中，上述在定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护计数器，可以包括：响应于定时器超过设定时长且第一终端设备未接收到第二终端设备发送的终端设备间协调信息，第一终端设备将计数器的计数值加1。
举例而言，第一终端设备在启动定时器后，响应于定时器的工作时长达到或者超过预先设定的时长，并且在定时器的工作时间内，第一终端设备未接收到第二终端设备发送的终端设备间协调信息，则第一终端设备将计数器的计数值加1。
可选地，在定时器的运行期间，第一终端设备接收到第二终端设备发送的终端设备间协调信息，停止定时器，并将计数器重置为初始值。其中第二终端通过IUC(inter-ue coordination)MAC CE发送对应的设备间协调信息。
举例而言，第一终端设备在启动定时器后，在定时器的运行期间接收到第二终端设备发送的终端设备间协调信息，则停止定时器运行，并将计数器的计数值重置为初始值。
需要说明的是，在本公开的实施例中，上述初始值可以为0。
步骤S303：根据计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求。
举例而言，第一终端设备根据计数器的计数值与预设值之间的大小关系，确定是否停止继续发送或生成终端设备间协调信息请求。
可选地，在本公开的一些实施例中，上述根据计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，可以包括：响应于计数器的计数值大于或等于预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求。
作为一种示例，第一终端设备响应于计数器的计数值大于或等于预设值，停止向第二终端设备发送终端设备间协调信息请求。
作为另一种示例，第一终端设备响应于计数器的计数值大于或等于预设值，停止向第二终端设备生成终端设备间协调信息请求。
其中，在本公开的实施例中，上述预设值为第一终端设备用于判断是否停止继续发送或生成终端设备间协调信息请求的数值。
可选地，在本公开的实施例中，上述根据计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，还可以包括：响应于计数器的计数值小于预设值，第一终端设备继续发送或生成终端设备间协调信息请求。
作为一种示例，第一终端设备响应于计数器的计数值小于预设值，继续向第二终端设备发送终端设备间协调信息请求。
作为另一种示例，第一终端设备响应于计数器的计数值小于预设值，继续向第二终端设备生成终端设备间协调信息请求。
需要说明的是，在本公开的实施例中，当计数器的计数值等于预设值时，第一终端设备可以停止继续发送或生成终端设备间协调信息请求，或者，第一终端设备也可以继续发送或生成终端设备间协调信息请求。
其中，在本公开的实施例中，上述预设值可以由网络侧设备通过RRC(Radio Resource Control，无线资源控制)信令配置。该RRC信令可以是专用RRC信令或者SIB(Signaling In Band，带内信令)。或者，上述第一预设值也可以是预配置的。或者，上述预设值也可以由第一终端设备通过实现预先确定。
需要说明的是，在本公开的实施例中，上述网络侧设备为支持SL特性的网络侧设备。
还需要说明的是，针对不同的场景，第一终端设备可以使用不同的预设值。例如，如果终端设备之间已经进行过UE能力交互，知道对端UE(如第二终端设备)支持IUC特性，则第一终端设备可以使用第一预设值来做统计。又如，如果终端设备之间进行的UE能力交互不包含IUC能力，第一终端设备不确定对端UE(如第二终端设备)是否支持IUC特性，则第一终端设备可以使用第二预设值来做统计。可选地，在本公开实施例的一些实施例中，第一终端设备可以接收第二终端设备发送的终端设备能力信息，该终端设备能力信息用于指示第二终端设备支持终端设备间协调特性。
举例而言，第一终端设备与第二终端设备之间进行UE能力交互，第一终端设备可以接收到第二终端设备发送的终端设备能力信息，该终端设备能力信息用于指示该第二终端设备支持终端设备间协调(IUC)特性。由于该终端设备能力信息可以指示第二终端设备支持终端设备间协调(IUC)特性，所以第一终端设备知道第二终端设备支持IUC特性，在这种场景下，第一终端设备可以使用第一预设值来做统计，以确定是否停止继续发送或生成终端设备间协调信息请求。
可选地，计数器的计数值大于或等于第一预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求。
其中，在本公开的实施例中，第一预设值为第一终端设备用于判断是否停止继续发送或生成终端设备间协调信息请求的数值。
需要说明的是，在本公开的实施例中，上述第一预设值可以由网络侧设备通过RRC信令配置。该RRC信令可以是专用RRC信令或者SIB。或者，上述第一预设值也可以是预配置的。或者，上述第一预设值可以由第一终端设备预先确定。
作为一种示例，计数器的计数值大于或等于第一预设值，第一终端设备停止向第二终端设备发送终端设备间协调信息请求。
作为另一种示例，计数器的计数值大于或等于第一预设值，第一终端设备停止向第二终端设备生成终端设备间协调信息请求。
可选地，第一终端设备可以响应于计数器的计数值小于第一预设值，继续发送或生成终端设备间协调信息请求。
可选地，在本公开实施例的一些实施例中，第一终端设备可以接收第二终端设备发送的终端设备能力信息；其中，终端设备能力信息中未包含终端设备间协调能力信息。
举例而言，第一终端设备与第二终端设备之间进行UE能力交互，第一终端设备可以接收到第二 终端设备发送的终端设备能力信息，该终端设备能力信息中未包含终端设备间协调能力信息。由于该终端设备能力信息中未包含终端设备间协调能力信息，所以第一终端设备不确定第二终端设备是否支持IUC特性，在这种场景下，第一终端设备可以使用第二预设值来做统计，以确定是否停止继续发送或生成终端设备间协调信息请求。
可选地，计数器的计数值大于或等于第二预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求。
其中，在本公开的实施例中，第二预设值为第一终端设备用于判断是否停止继续发送或生成终端设备间协调信息请求的数值。第二预设值大于或等于上述第一预设值。在本公开的一些实施例中，网络侧设备可以通过RRC信令配置第一预设值小于或者等于第二预设值，或者第一终端设备可以自主确定第一预设值小于或者等于第二预设值。
需要说明的是，在本公开的实施例中，上述第二预设值可以由网络侧设备通过RRC信令配置。该RRC信令可以是专用RRC信令或者SIB。或者，上述第二预设值也可以是预配置的。或者，上述第二预设值可以由第一终端设备预先确定。
作为一种示例，计数器的计数值大于或等于第二预设值，第一终端设备停止向第二终端设备发送终端设备间协调信息请求。
作为另一种示例，第一终端设备响应于计数器的计数值大于或等于第二预设值，第一终端设备停止向第二终端设备生成终端设备间协调信息请求。
可选地，在本公开的实施例中，计数器的计数值小于或等于第二预设值，第一终端设备继续发送或生成终端设备间协调信息请求。
通过实施本公开实施例，可以根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，从而避免第一终端设备在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。
可选地，在本公开的一些实施例中，第一终端设备与一个或多个第二终端设备存在单播链路，第一终端设备对每个单播链路上对应的定时器和计数器进行维护。
举例而言，第一终端设备与每个第二终端设备间存在一个点对点的通信链路，并且每个通信链路具有对应的定时器和计数器，第一终端设备可以按照本公开各个实施例提供的方法，对每个通信链路对应的定时器和计数器进行维护。
可选地，在本公开的一些实施例中，上述终端设备间协调信息中携带首选资源集合指示信息，该首选资源集合指示信息用于指示第一终端设备只能使用首选资源集合中指示的资源给第二终端设备发送数据；或者，该终端设备间协调信息中携带非首选资源集合指示信息，该非首选资源集合指示信息用于指示第一终端设备不能使用非首选资源集合中指示的资源给第二终端设备发送数据。
上述本公开提供的实施例中，从第一终端设备的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，第一终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图4，为本公开实施例提供的一种通信装置40的结构示意图。图4所示的通信装置40可包括收发模块401和处理模块402。收发模块401可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块401可以实现发送功能和/或接收功能。
通信装置40可以是第一终端设备，也可以是第一终端设备中的装置，还可以是能够与第一终端设备匹配使用的装置。
其中，处理模块402用于：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求IUC-request。
在一种实现方式中，处理模块402具体用于：响应于发送完或生成终端设备间协调信息请求后，启动定时器；在定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护计数器；根据计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求。
在一种可选地实现方式中，处理模块402具体用于：响应于定时器超过设定时长且第一终端设备未接收到第二终端设备发送的终端设备间协调信息，第一终端设备将计数器的计数值加1；在定时器的运行期间，第一终端设备接收到第二终端设备发送的终端设备间协调信息，停止定时器，并将计数器重置为初始值。
在一种可选地实现方式中，处理模块402具体用于：响应于计数器的计数值大于或等于预设值， 第一终端设备停止继续发送或生成终端设备间协调信息请求；响应于计数器的计数值小于预设值，第一终端设备继续发送或生成终端设备间协调信息请求。
可选地，预设值为网络侧设备通过无线资源控制RRC信令配置的，或者，UE通过实现自己确定。
可选地，收发模块401用于：接收第二终端设备发送的终端设备能力信息，终端设备能力信息用于指示第二终端设备支持终端设备间协调特性；处理模块402还用于：计数器的计数值大于或等于第一预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求。
可选地，收发模块401还用于：接收第二终端设备发送的终端设备能力信息；其中，终端设备能力信息中未包含终端设备间协调能力信息；处理模块402还用于：计数器的计数值大于或等于第二预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求；其中第一预设值小于或等于第二预设值。
在一种实现方式中，第一终端设备与一个或多个第二终端设备存在单播链路，第一终端设备对每个单播链路上对应的定时器和计数器进行维护。
在一种可选地实现方式中，终端设备间协调信息中携带首选资源集合指示信息，首选资源集合指示信息用于指示第一终端设备只能使用首选资源集合中指示的资源给第二终端设备发送数据；或者，终端设备间协调信息中携带非首选资源集合指示信息，非首选资源集合指示信息用于指示第一终端设备不能使用非首选资源集合中指示的资源给第二终端设备发送数据。
通过本公开实施例的装置，可以根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求，从而避免在不知道第二终端设备的资源分配模式和/或能力的情况下，持续发送或生成终端设备间协调信息请求，从而避免造成信令浪费，并降低对其他终端设备造成的干扰。
请参见图5，图5是本公开实施例提供的另一种通信装置50的结构示意图。通信装置50可以是网络侧设备，也可以是终端设备，也可以是支持网络侧设备实现上述方法的芯片、芯片***、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片***、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置50可以包括一个或多个处理器501。处理器501可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置50中还可以包括一个或多个存储器502，其上可以存有计算机程序503，处理器501执行所述计算机程序503，以使得通信装置50执行上述方法实施例中描述的方法。可选的，所述存储器502中还可以存储有数据。通信装置50和存储器502可以单独设置，也可以集成在一起。
可选的，通信装置50还可以包括收发器504、天线505。收发器504可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器504可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置50中还可以包括一个或多个接口电路506。接口电路506用于接收代码指令并传输至处理器501。处理器501运行所述代码指令以使通信装置50执行上述方法实施例中描述的方法。
通信装置50为第一终端设备：处理器501用于执行图2中的步骤S201；执行图3中的步骤S301、步骤S302和步骤S303。
在一种实现方式中，处理器501中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器501可以存有计算机程序，该计算机程序在处理器501上运行，可使得通信装置50执行上述方法实施例中描述的方法。该计算机程序可能固化在处理器501中，该种情况下，处理器501可能由硬件实现。
在一种实现方式中，通信装置50可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel  metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图5的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片***或子***；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络侧设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片***的情况，可参见图6所示的芯片的结构示意图。图6所示的芯片包括处理器601和接口602。其中，处理器601的数量可以是一个或多个，接口602的数量可以是多个。
其中，处理器601用于：根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求IUC-request。
在一种实现方式中，处理器601具体用于：响应于发送完或生成终端设备间协调信息请求后，启动定时器；在定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护计数器；根据计数器的计数值，确定是否停止继续发送或生成终端设备间协调信息请求。
在一种可选地实现方式中，处理器601具体用于：响应于定时器超过设定时长且第一终端设备未接收到第二终端设备发送的终端设备间协调信息，第一终端设备将计数器的计数值加1；在定时器的运行期间，第一终端设备接收到第二终端设备发送的终端设备间协调信息，停止定时器，并将计数器重置为初始值。
在一种可选地实现方式中，处理器601具体用于：响应于计数器的计数值大于或等于预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求；响应于计数器的计数值小于预设值，第一终端设备继续发送或生成终端设备间协调信息请求。
可选地，预设值为网络侧设备通过无线资源控制RRC信令配置的，或者，UE通过实现自己确定。
可选地，接口602用于：接收第二终端设备发送的终端设备能力信息，终端设备能力信息用于指示第二终端设备支持终端设备间协调特性；处理器601还用于：计数器的计数值大于或等于第一预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求。
可选地，接口602还用于：接收第二终端设备发送的终端设备能力信息；其中，终端设备能力信息中未包含终端设备间协调能力信息；处理器601还用于：计数器的计数值大于或等于第二预设值，第一终端设备停止继续发送或生成终端设备间协调信息请求；其中第一预设值小于或等于第二预设值。
在一种实现方式中，第一终端设备与一个或多个第二终端设备存在单播链路，第一终端设备对每个单播链路上对应的定时器和计数器进行维护。
在一种可选地实现方式中，终端设备间协调信息中携带首选资源集合指示信息，首选资源集合指示信息用于指示第一终端设备只能使用首选资源集合中指示的资源给第二终端设备发送数据；或者，终端设备间协调信息中携带非首选资源集合指示信息，非首选资源集合指示信息用于指示第一终端设备不能使用非首选资源集合中指示的资源给第二终端设备发送数据。
可选的，芯片还包括存储器603，存储器603用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个***的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算 机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (11)

  1. 一种直连sidelink终端设备间内部协调信息请求的发送方法，其特征在于，所述方法由第一终端设备执行，所述方法包括：
    根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求IUC-request。
  2. 如权利要求1所述的方法，其特征在于，所述根据定时器的设定时长和计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求，包括：
    响应于发送完或生成所述终端设备间协调信息请求后，启动所述定时器；
    在所述定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护所述计数器；
    根据所述计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求。
  3. 如权利要求2所述的方法，其特征在于，所述在所述定时器的运行期间监听第二终端设备发送的终端设备间协调信息并维护所述计数器，包括：
    响应于所述定时器超过所述设定时长且所述第一终端设备未接收到所述第二终端设备发送的终端设备间协调信息，所述第一终端设备将所述计数器的计数值加1；
    在所述定时器的运行期间，所述第一终端设备接收到所述第二终端设备发送的终端设备间协调信息，停止所述定时器，并将所述计数器重置为初始值。
  4. 如权利要求2或3所述的方法，其特征在于，所述根据所述计数器的计数值，确定是否停止继续发送或生成所述终端设备间协调信息请求，包括：
    响应于所述计数器的计数值大于或等于预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；
    响应于所述计数器的计数值小于所述预设值，所述第一终端设备继续发送或生成所述终端设备间协调信息请求。
  5. 如权利要求4所述的方法，其特征在于，所述预设值为网络侧设备通过无线资源控制RRC信令配置的，或者，UE通过实现自己确定。
  6. 如权利要求4或5所述的方法，其特征在于，还包括：
    接收所述第二终端设备发送的终端设备能力信息，所述终端设备能力信息用于指示所述第二终端设备支持终端设备间协调特性；所述计数器的计数值大于或等于第一预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求。
  7. 如权利要求4或5所述的方法，其特征在于，还包括：
    接收所述第二终端设备发送的终端设备能力信息；其中，所述终端设备能力信息中未包含终端设备间协调能力信息；所述计数器的计数值大于或等于第二预设值，所述第一终端设备停止继续发送或生成所述终端设备间协调信息请求；其中第一预设值小于或等于第二预设值。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，所述第一终端设备与一个或多个第二终端设备存在单播链路，所述第一终端设备对每个所述单播链路上对应的定时器和计数器进行维护。
  9. 如权利要求2至7中任一项所述的方法，其特征在于，
    所述终端设备间协调信息中携带首选资源集合指示信息，所述首选资源集合指示信息用于指示所述第一终端设备只能使用所述首选资源集合中指示的资源给所述第二终端设备发送数据；或者，
    所述终端设备间协调信息中携带非首选资源集合指示信息，所述非首选资源集合指示信息用于指示所述第一终端设备不能使用所述非首选资源集合中指示的资源给所述第二终端设备发送数据。
  10. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至9中任一项所述的方法。
  11. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至9中任一项所述的方法被实现。
PCT/CN2022/110706 2022-08-05 2022-08-05 直连sidelink终端设备间内部协调信息请求的发送方法及其装置 WO2024026887A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280003015.6A CN115606313A (zh) 2022-08-05 2022-08-05 直连Sidelink终端设备间内部协调信息请求的发送方法及其装置
PCT/CN2022/110706 WO2024026887A1 (zh) 2022-08-05 2022-08-05 直连sidelink终端设备间内部协调信息请求的发送方法及其装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110706 WO2024026887A1 (zh) 2022-08-05 2022-08-05 直连sidelink终端设备间内部协调信息请求的发送方法及其装置

Publications (1)

Publication Number Publication Date
WO2024026887A1 true WO2024026887A1 (zh) 2024-02-08

Family

ID=84853846

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110706 WO2024026887A1 (zh) 2022-08-05 2022-08-05 直连sidelink终端设备间内部协调信息请求的发送方法及其装置

Country Status (2)

Country Link
CN (1) CN115606313A (zh)
WO (1) WO2024026887A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333661A (zh) * 2020-10-23 2021-02-05 大唐高鸿数据网络技术股份有限公司 资源选择方法、装置及终端设备
WO2022147228A1 (en) * 2020-12-31 2022-07-07 Ofinno, Llc Inter-ue coordination for resource selection

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333661A (zh) * 2020-10-23 2021-02-05 大唐高鸿数据网络技术股份有限公司 资源选择方法、装置及终端设备
WO2022147228A1 (en) * 2020-12-31 2022-07-07 Ofinno, Llc Inter-ue coordination for resource selection

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "Open issues on SL inter-UE coordination", 3GPP TSG RAN WG2 MEETING #117E, R2-2202582, 14 February 2022 (2022-02-14), XP052110515 *
LG: "Summary of [POST116bis-e][707][V2X/SL] Open issues on IUC, Phase 1", 3GPP TSG RAN WG2 MEETING #116BIS ELECTRONIC, R2-2201807, 31 January 2022 (2022-01-31), XP052104347 *

Also Published As

Publication number Publication date
CN115606313A (zh) 2023-01-13

Similar Documents

Publication Publication Date Title
WO2023028962A1 (zh) 一种信息传输方法和装置
WO2023206179A1 (zh) 一种确定传输配置指示状态的方法及装置
WO2023206034A1 (zh) 混合自动重传请求harq反馈的处理方法及其装置
WO2024000180A1 (zh) 一种指示方法、装置、设备及存储介质
WO2024031272A1 (zh) 一种上报方法、装置、设备及存储介质
WO2024000531A1 (zh) 一种循环前缀扩展cpe的发送方法及其装置
WO2023151103A1 (zh) 一种终端辅助信息上报方法、获取方法及其装置
US20240244527A1 (en) Method and apparatus for determining activation state of terminal
WO2024026887A1 (zh) 直连sidelink终端设备间内部协调信息请求的发送方法及其装置
WO2024040414A1 (zh) 基于条件触发的终端内部协作方法和装置
WO2024045042A1 (zh) 一种能力交互触发方法/装置/设备及存储介质
WO2024138396A1 (zh) 非授权频谱中侧行链路的无线链路失败检测方法及其装置
WO2024031374A1 (zh) 基于侧行链路的设备间协作方法、装置、设备及存储介质
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2023164851A1 (zh) 侧行链路监听方法及装置
WO2023173257A1 (zh) 一种请求***信息的方法及其装置
WO2024098430A1 (zh) 一种处理时延的确定方法、装置、设备及存储介质
WO2024065199A1 (zh) 用于终端设备ue到ue中继场景的中继ue选择方法及其装置
WO2024130566A1 (zh) 一种反馈方法、装置、设备及存储介质
WO2024040484A1 (zh) 基于harq属性的载波选择或重选方法、装置及设备
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
WO2024065198A1 (zh) 用于终端设备ue到ue中继场景的中继通信处理方法及装置
WO2024092427A1 (zh) 一种激活状态确定方法/装置/设备及存储介质
WO2023245453A1 (zh) 一种消息传输方法/装置/设备及存储介质
WO2024026799A1 (zh) 数据传输方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22953687

Country of ref document: EP

Kind code of ref document: A1