WO2023184116A1 - 侧行链路sidelink通信方法及装置 - Google Patents

侧行链路sidelink通信方法及装置 Download PDF

Info

Publication number
WO2023184116A1
WO2023184116A1 PCT/CN2022/083493 CN2022083493W WO2023184116A1 WO 2023184116 A1 WO2023184116 A1 WO 2023184116A1 CN 2022083493 W CN2022083493 W CN 2022083493W WO 2023184116 A1 WO2023184116 A1 WO 2023184116A1
Authority
WO
WIPO (PCT)
Prior art keywords
sidelink
shared frequency
transmission resource
lbt
destination address
Prior art date
Application number
PCT/CN2022/083493
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 PCT/CN2022/083493 priority Critical patent/WO2023184116A1/zh
Priority to CN202280000767.7A priority patent/CN114938710A/zh
Publication of WO2023184116A1 publication Critical patent/WO2023184116A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a sidelink communication method and device.
  • the sidelink communication method is introduced, and the interface between user terminals is PC-5.
  • LBT listen before talk
  • An embodiment of the first aspect of the present disclosure provides a sidelink sidelink communication method.
  • the method is executed by a terminal device.
  • the method includes determining whether a persistent LBT failure is triggered on a sidelink transmission resource of a shared frequency; When the persistent LBT fails to be triggered, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages.
  • the terminal device determines whether the persistent LBT fails to be triggered on the sidelink transmission resource of the shared frequency; when the persistent LBT fails to be triggered, it reports a failure indication to the network device or determines the backup sidelink transmission resource, using For sending sidelink messages, the terminal device can send data in time when LBT fails, avoiding data loss and increasing communication reliability.
  • the embodiment of the second aspect of the present disclosure proposes another sidelink communication method, which is applied to network equipment.
  • the method includes sending a first message to the terminal device; wherein the first message carries a designated timer and a designated timer.
  • the number of times threshold is used to determine whether continuous LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the third aspect of the present disclosure provides a sidelink communication method, which is applied to a destination terminal device.
  • the method includes: receiving a failure indication sent by the terminal device, wherein the failure indication includes: a first Destination address identifier, wherein sidelink communication with the first destination address identifier triggers persistent LBT failure.
  • the fourth embodiment of the present disclosure proposes a sidelink communication device, which is applied to terminal equipment.
  • the device includes: a first processing unit configured to determine whether to trigger a sidelink transmission resource on a shared frequency.
  • the persistent LBT fails;
  • the second processing unit is configured to report a failure indication to the network device or determine the backup sidelink transmission resource for sending the sidelink message when the persistent LBT failure is triggered.
  • the embodiment of the fifth aspect of the present disclosure proposes another sidelink communication device, which is applied to network equipment.
  • the device includes: a transceiver unit for sending a first message to the terminal device; wherein the first message Carrying a specified timer and a specified number of times threshold, used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the embodiment of the sixth aspect of the present disclosure proposes another sidelink communication device, which is applied to a destination terminal device.
  • the device includes: a transceiver unit configured to receive a failure indication sent by the terminal device, wherein the The failure indication includes: a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers a persistent LBT failure.
  • the seventh embodiment of the present disclosure provides a sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory. , so that the device executes the method described in the embodiment of the first aspect of the present disclosure.
  • the eighth embodiment of the present disclosure proposes another sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory. Program, so that the device executes the method described in the embodiment of the second aspect of the present disclosure.
  • the ninth aspect of the present disclosure provides another sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory. Program, so that the device executes the method described in the third embodiment of the present disclosure.
  • the tenth aspect of the present disclosure provides a sidelink communication device, which is characterized in that it 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 configured to run the code instructions to perform the method described in the embodiment of the first aspect of the present disclosure.
  • An eleventh aspect embodiment of the present disclosure proposes another sidelink communication device, which is characterized in that it 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 configured to run the code instructions to perform the method described in the embodiment of the second aspect of the present disclosure.
  • the twelfth aspect of the present disclosure provides another sidelink communication device, which is characterized in that it 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 configured to run the code instructions to perform the method described in the third aspect of the present disclosure.
  • the thirteenth embodiment of the present disclosure provides a computer-readable storage medium for storing instructions. When the instructions are executed, the method described in the first embodiment of the present disclosure is implemented.
  • the fourteenth embodiment of the present disclosure provides another computer-readable storage medium for storing instructions. When the instructions are executed, the method described in the second embodiment of the present disclosure is implemented.
  • the fifteenth aspect embodiment of the present disclosure provides another computer-readable storage medium for storing instructions. When the instructions are executed, the method described in the third aspect embodiment of the present disclosure is implemented.
  • a sixteenth aspect embodiment of the present disclosure provides a computer program product that, when run on a computer, causes the computer to execute the method described in the first aspect embodiment.
  • the seventeenth aspect embodiment of the present disclosure provides another computer program product, which, when run on a computer, causes the computer to execute the method described in the above-mentioned second aspect embodiment.
  • the eighteenth aspect embodiment of the present disclosure provides another computer program product, which, when run on a computer, causes the computer to execute the method described in the above-mentioned third aspect embodiment.
  • Figure 1 is a schematic structural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flow chart of a sidelink communication method provided by an embodiment of the present disclosure
  • Figure 3 is a schematic flow chart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 4 is a schematic flowchart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 5 is a schematic flowchart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 6 is a schematic flow chart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 7 is a schematic flow chart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 8 is a schematic flow chart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 9 is a schematic flowchart of another sidelink communication method provided by an embodiment of the present disclosure.
  • Figure 10 is a schematic structural diagram of a sidelink communication device provided by an embodiment of the present disclosure.
  • Figure 11 is a schematic structural diagram of another sidelink communication device provided by an embodiment of the present disclosure.
  • Figure 12 is a schematic structural diagram of another sidelink communication device provided by an embodiment of the present disclosure.
  • Figure 13 is a schematic structural diagram of a network device provided by an embodiment of the present disclosure.
  • Figure 14 is a block diagram of a terminal device provided by an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • the words "if” and “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • 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 one network device and one 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. In actual applications, two or more devices may be included. Network equipment, two or more terminal devices.
  • the communication system shown in Figure 1 only includes one network device 101 and one terminal device 102 as an example.
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the network 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 device 101 can be an evolved base station (evolved NodeB, eNB), a transmission reception point (transmission reception point or transmit receive point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other future mobile Base stations in communication systems or access nodes in wireless fidelity (WiFi) systems, etc.
  • the embodiments of the present disclosure do not limit the specific technologies and specific equipment forms used by network equipment.
  • the network equipment provided by the embodiments of the present disclosure may be composed of a centralized unit (CU) and a distributed unit (DU).
  • the CU may also be called a control unit (control unit).
  • the structure can separate the protocol layers of network equipment, such as base stations, and place some protocol layer functions under centralized control on the CU. The remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 102 in the embodiment of the present disclosure is an entity on the user side that is used to receive or transmit signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user terminal (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.
  • the sidelink (sidelink) communication method is introduced.
  • the interface between user terminals and user terminals is PC-5 .
  • three transmission methods are supported on sidelink, unicast, multicast and broadcast.
  • each UE corresponds to a destination address identifier; in multicast, each UE can belong to one or more groups, and each group corresponds to a destination address identifier.
  • all UEs Corresponds to at least one destination address identifier.
  • the application layer sends the source layer 2 address and destination layer 2 address to the access layer, with a length of 24 bits.
  • the lower 8 bits of the source layer 2 address are carried in the SCI and become the source layer 1 address, and the remaining 16 bits are carried in the MAC subheader.
  • the lower 16 bits of the destination layer 2 address are carried in the SCI and become the destination layer 1 address, and the remaining 8 bits are carried in the MAC subheader.
  • the UE reports the destination address identifier of the destination UE of the failed unicast connection and the failure reason to the network device.
  • the failure reason includes the sidelink wireless link failure. Or the sidelink configuration fails.
  • the UE When the UE performs uplink transmission on the shared frequency (unlicensed spectrum), the UE needs to perform LBT (Listen Before Talk, listen before transmitting). When LBT fails, the physical layer will notify the Media Access Control layer (Media Access Control, MAC). )layer.
  • LBT Listen Before Talk, listen before transmitting
  • the physical layer will notify the Media Access Control layer (Media Access Control, MAC). )layer.
  • the MAC When receiving an LBT failure indication, the MAC starts or restarts the specified timer (lbt-FailureDetectionTimer), and the number of LBT failures increases by one. If the specified timer times out, the number of failed attempts to reset LBT is 0. If the number of LBT failures reaches the specified threshold (lbt-FailureInstanceMaxCount), continuous LBT failures are triggered.
  • the specified timer and specified times threshold are configured by the network device through Radio Resource Control (RRC) messages.
  • RRC Radio Resource Control
  • BWP bandwidth part
  • RLF Radio Link Failure
  • LBT listen before talk
  • the present disclosure proposes a sidelink communication method and device.
  • Figure 2 is a schematic flow chart of a sidelink communication method provided by an embodiment of the present disclosure.
  • the sidelink communication method can be performed by the terminal device in the communication system shown in Figure 1.
  • the sidelink communication method may include the following steps:
  • Step 201 Determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the number of LBT failures on the sidelink transmission resources of the shared frequency is greater than or equal to the specified number threshold, it is determined that a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency.
  • the number of LBT failures within the specified timer is less than the specified number threshold, it is determined that no continuous LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • Step 202 When the persistent LBT fails to be triggered, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages.
  • the backup sidelink transmission resource may be a sidelink transmission resource on a shared frequency, or may be a sidelink transmission resource on a non-shared frequency.
  • the terminal device when a persistent LBT failure is triggered, the terminal device reports a first failure indication to the network device, and sends a sidelink message according to the backup sidelink transmission resources scheduled by the network device.
  • a backup sidelink transmission resource is selected from at least one configured candidate sidelink transmission resource for sending the sidelink message.
  • a candidate sidelink transmission resource of a shared frequency that does not trigger a persistent LBT failure or a candidate sidelink transmission resource of a non-shared frequency may be selected from at least one candidate sidelink transmission resource as a backup sidelink. Send resources.
  • the terminal device receives a fourth RRC message from the network device, wherein the fourth RRC message carries candidate sidelink transmission resources; wherein the candidate sidelink transmission resources include a shared frequency Candidate sidelink transmission resources or candidate sidelink transmission resources of non-shared frequencies.
  • the terminal device receives a second sidelink RRC message from the destination terminal device corresponding to at least one destination address identifier, where the second sidelink RRC message carries the candidate sidelink transmission resource message.
  • the candidate sidelink transmission resources include candidate sidelink transmission resources of shared frequencies or candidate sidelink transmission resources of non-shared frequencies.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • determining whether a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency when triggering a persistent LBT failure, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink Link messages enable terminal devices to send data in a timely manner when LBT fails, avoiding data loss and increasing communication reliability.
  • FIG. 3 is a schematic flowchart of another sidelink communication method provided by the embodiment of the present disclosure.
  • the sidelink communication method can be applied
  • the sidelink communication method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any method in related technologies. A technical solution is implemented together.
  • the sidelink communication method may include the following steps:
  • Step 301 When the number of LBT failures on the sidelink transmission resources of the shared frequency is greater than or equal to a specified number threshold, it is determined that a persistent LBT failure is triggered on the sidelink transmission resources of the shared frequency.
  • the process of the terminal device determining the number of LBT failures on the sidelink transmission resource of the shared frequency may be, for example, resetting the current number of LBT failures to zero when the specified timer times out, and stopping. Specify the timer; when an LBT failure occurs on the sidelink transmission resource of the shared frequency, start or restart the specified timer, and add 1 to the current number of LBT failures.
  • the specified timer when an LBT failure occurs on the sidelink transmission resource of the shared frequency, if the specified timer has not been started, the specified timer is started, and the number of LBT failures is increased by 1; if the specified timer has not been started, the specified timer is started. After stopping or starting, the specified timer will be restarted, and the number of LBT failures will be incremented by 1.
  • the number of LBT failures on the sidelink transmission resources of a shared frequency includes the number of LBT failures on all sidelink transmission resources of all shared frequencies.
  • the number of LBT failures within the specified timer is less than the specified number threshold, it is determined that a continuous LBT failure is not triggered on the sidelink transmission resource of the shared frequency.
  • the terminal device receives a first RRC message from the network device before determining whether to trigger a persistent LBT failure on the sidelink transmission resource of the shared frequency, where the first RRC message carries a specified timer and a specified number of times. Threshold; specifies a timer to reset the number of LBT failures upon timeout.
  • the first RRC message carries the same number of designated timers and designated times thresholds, and may carry one designated timer and one designated times threshold.
  • Step 302 When the persistent LBT fails to be triggered, a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages.
  • the terminal device when a persistent LBT failure is triggered, the terminal device reports a first failure indication to the network device, and sends a sidelink message according to the backup sidelink transmission resources scheduled by the network device.
  • the terminal device when triggering the persistent LBT fails, may select a backup sidelink transmission resource from at least one configured candidate sidelink transmission resource for sending the sidelink link message.
  • a candidate sidelink transmission resource of a shared frequency that does not trigger a persistent LBT failure or a candidate sidelink transmission resource of a non-shared frequency may be selected from at least one candidate sidelink transmission resource as a backup sidelink. Send resources.
  • the terminal device receives a fourth RRC message from the network device, wherein the fourth RRC message carries candidate sidelink transmission resources; wherein the candidate sidelink transmission resources include a shared frequency Candidate sidelink transmission resources or candidate sidelink transmission resources of non-shared frequencies.
  • the terminal device receives a second sidelink RRC message from the destination terminal device corresponding to at least one destination address identifier, where the second sidelink RRC message carries the candidate sidelink transmission resource message.
  • the candidate sidelink transmission resources include candidate sidelink transmission resources of shared frequencies or candidate sidelink transmission resources of non-shared frequencies.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • the continuous LBT failure when the number of LBT failures on the sidelink transmission resources of the shared frequency is greater than or equal to the specified number threshold, it is determined that the continuous LBT failure is triggered on the sidelink transmission resources of the shared frequency; when the continuous LBT failure is triggered , report a failure indication to the network device or determine the backup sidelink transmission resource for sending sidelink messages, so that the terminal device can send data in a timely manner when LBT fails, avoiding data loss and increasing communication reliability.
  • FIG. 4 is a schematic flowchart of another sidelink communication method provided by the embodiment of the present disclosure.
  • the sidelink communication method can be applied
  • the path switching method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any technical solution in related technologies. are executed together.
  • the sidelink communication method may include the following steps:
  • Step 401 When there is a first shared frequency in at least one shared frequency, it is determined that triggering the persistent LBT on the sidelink transmission resource of the first shared frequency fails.
  • the number of LBT failures corresponding to the first shared frequency is greater than or equal to a specified number of times threshold corresponding to the first shared frequency.
  • the terminal device before the terminal device determines whether a first shared frequency exists in at least one shared frequency, it receives a second RRC message from the network device, where the second RRC message carries: a designated timer corresponding to at least one shared frequency, and a specified number of thresholds corresponding to at least one shared frequency; wherein a specified timer is used to reset the number of LBT failures corresponding to the shared frequency when timeout occurs.
  • the designated timers corresponding to at least one shared frequency are the same or different; the designated number thresholds corresponding to at least one shared frequency are the same or different.
  • each sharing frequency can correspond to a specified timer, and each sharing frequency can correspond to a specified times threshold.
  • multiple shared frequencies may correspond to a specified timer, and multiple shared frequencies may correspond to a specified threshold of times.
  • Step 402 When the persistent LBT fails to be triggered on the sidelink transmission resource of the first shared frequency, report the failure indication to the network device or determine the backup sidelink transmission resource for sending the sidelink message.
  • a second failure indication carrying the first shared frequency is reported to the network device, according to the network device schedule
  • the backup sidelink transmission resource is used to send sidelink messages.
  • the terminal device may select a backup sidelink transmission resource from at least one configured candidate sidelink transmission resource. , used to send sidelink messages.
  • a candidate sidelink transmission resource of a shared frequency that does not trigger a persistent LBT failure or a candidate sidelink transmission resource of a non-shared frequency may be selected from at least one candidate sidelink transmission resource as a backup sidelink. Send resources.
  • the terminal device receives a fourth RRC message from the network device, wherein the fourth RRC message carries candidate sidelink transmission resources; wherein the candidate sidelink transmission resources include a shared frequency Candidate sidelink transmission resources or candidate sidelink transmission resources of non-shared frequencies.
  • the terminal device receives a second sidelink RRC message from the destination terminal device corresponding to at least one destination address identifier, where the second sidelink RRC message carries the candidate sidelink transmission resource message.
  • the candidate sidelink transmission resources include candidate sidelink transmission resources of shared frequencies or candidate sidelink transmission resources of non-shared frequencies.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • the number of LBT failures corresponding to the first shared frequency is greater than or equal to the designated number threshold corresponding to the first shared frequency; when a continuous LBT failure is triggered on the sidelink transmission resource of the first shared frequency, a failure indication or determination is reported to the network device
  • the backup sidelink transmission resource is used to send sidelink messages, so that when the LBT fails, the terminal device can send data in time to avoid data loss and increase communication reliability.
  • FIG. 5 is a schematic flowchart of another sidelink communication method provided by the embodiment of the present disclosure.
  • the sidelink communication method can be applied
  • the sidelink communication method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any method in related technologies. A technical solution is implemented together.
  • Step 501 When there is a first destination address identifier in at least one destination address identifier for sidelink communication on at least one shared frequency sidelink transmission resource, determine to perform sidelink communication with the first destination address identifier. Failed to trigger continuous LBT.
  • the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the specified number of times corresponding to the first destination address identifier. threshold.
  • the terminal device before determining whether to trigger a persistent LBT failure on the sidelink transmission resource of the shared frequency, receives a third RRC message from the network device, where the third RRC message carries : The specified timer corresponding to at least one destination address identifier, and the specified number of times threshold corresponding to at least one destination address identifier; the specified timer is used to reset the number of LBT failures corresponding to the destination address identifier when timeout.
  • a first sidelink RRC message is received from a destination terminal device corresponding to at least one destination address identifier, wherein the first sidelink RRC message carries: a specified timer corresponding to the destination address identifier, and a specified timer corresponding to the destination address identifier. times threshold.
  • the specified timers corresponding to at least one destination address identifier are the same or different; the specified number of times thresholds corresponding to at least one destination address identifier are the same or different.
  • Step 502 When it is determined that the sidelink communication with the first destination address identifier fails to trigger the continuous LBT, report the failure indication to the network device or determine the backup sidelink transmission resource for sending the sidelink message.
  • a third failure indication carrying the first destination address identifier is reported to the network device; according to the network device
  • the scheduled backup sidelink transmission resource is used to transmit sidelink messages.
  • the terminal device may select a shared resource from at least one configured candidate sidelink transmission resource.
  • the candidate sidelink transmission resources of the frequency or the candidate sidelink transmission resources of the non-shared frequency are used as the backup sidelink transmission resources.
  • the terminal selects a candidate sidelink transmission resource of a shared frequency that does not trigger a persistent LBT failure from at least one configured candidate sidelink transmission resource as a backup sidelink transmission resource for transmitting the sidelink information.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • the embodiment of the present disclosure provides another sidelink communication method.
  • Figure 6 is a schematic flowchart of another sidelink communication method provided by the embodiment of the present disclosure.
  • the sidelink communication method can be applied For terminal equipment, the sidelink communication method can be performed by the terminal equipment in Figure 1.
  • the sidelink communication method may include the following steps:
  • Step 601 When there is a first destination address identifier in at least one destination address identifier for sidelink communication on at least one shared frequency sidelink transmission resource, determine to perform sidelink communication with the first destination address identifier. Failed to trigger continuous LBT.
  • the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the specified number of times corresponding to the first destination address identifier. threshold.
  • Step 602 When the sidelink communication with the first destination address identifier triggers a persistent LBT failure, send a fourth failure indication to the destination terminal device corresponding to the first destination address identifier.
  • the fourth failure indication is used to instruct the destination terminal device to stop receiving sidelink messages of the terminal device on the sidelink transmission resource of the shared frequency where persistent LBT failure occurs.
  • the fourth failure indication is used to indicate that when the backup sidelink transmission resource exists, the sidelink message is received on the backup sidelink transmission resource.
  • the fourth failure indication also carries: a second shared frequency.
  • the sidelink transmission resource of the second shared frequency triggers a continuous LBT failure.
  • the terminal device sends a fourth failure indication carrying the second shared frequency to the destination terminal device, and the sidelink transmission resource of the second shared frequency triggers a continuous LBT failure. That is to say, the sidelink of the second shared frequency fails.
  • the sidelink transmission resource cannot send sidelink messages.
  • a third sidelink RRC message is sent to the destination terminal device corresponding to the first destination address identification, where the third sidelink RRC message carries a fourth failure indication.
  • a sidelink MAC CE message is sent to the destination terminal device corresponding to the first destination address identification, where the sidelink MAC CE message carries a fourth failure indication.
  • Step 603 When it is determined that the sidelink communication with the first destination address identifier fails to trigger the continuous LBT, report the failure indication to the network device or determine the backup sidelink transmission resource for sending the sidelink message.
  • the terminal device may select a shared frequency from at least one configured candidate sidelink transmission resource.
  • Candidate sidelink transmission resources or candidate sidelink transmission resources of non-shared frequencies are used as backup sidelink transmission resources.
  • the terminal selects a candidate sidelink transmission resource of a shared frequency that does not trigger a persistent LBT failure from at least one configured candidate sidelink transmission resource as a backup sidelink transmission resource for transmitting the sidelink information.
  • a fourth RRC message is received from a network device, wherein the fourth RRC message carries candidate sidelink transmission resources; wherein the candidate sidelink transmission resources include candidates for shared frequencies. Sidelink transmission resources or candidate sidelink transmission resources of non-shared frequencies.
  • a second sidelink RRC message is received from a destination terminal device corresponding to at least one destination address identifier, where the second sidelink RRC message carries a candidate sidelink transmission resource message.
  • the candidate sidelink transmission resources include candidate sidelink transmission resources of shared frequencies or candidate sidelink transmission resources of non-shared frequencies.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • the side link communication with the first destination address identification triggers the continuous LBT failure
  • a failure indication is reported to the network device or a backup sidelink transmission resource is determined for sending sidelink messages, so that the terminal device can send data in a timely manner when LBT fails to avoid data loss and increase Communication reliability.
  • FIG. 7 is a schematic flowchart of another sidelink communication method provided by the embodiment of the present disclosure.
  • the sidelink communication method can be applied For network equipment, the sidelink communication method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any method in related technologies. A technical solution is implemented together.
  • the sidelink communication method may include the following steps:
  • Step 701 Send the first message to the terminal device.
  • the first message may be an RRC message, for example.
  • the first message carries a specified timer and a specified times threshold, which are used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the first RRC message carries the same number of designated timers and designated times thresholds, and may carry one designated timer and one designated times threshold. Among them, a timer is specified to reset the number of LBT failures when timeout occurs.
  • the first message carries a specified timer corresponding to at least one shared frequency, and a specified times threshold corresponding to at least one shared frequency, and is used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the specified timer is used to reset the number of LBT failures corresponding to the shared frequency when it times out; the specified timers corresponding to at least one shared frequency are the same or different; the specified number thresholds corresponding to at least one shared frequency are the same or different.
  • the number of designated timers is at least one, corresponding to at least one shared frequency; the number of designated times thresholds is at least one, corresponding to at least one shared frequency.
  • the first message carries a specified timer corresponding to at least one destination address identifier, and a specified times threshold corresponding to at least one destination address identifier, and is used to determine whether to trigger a continuous trigger on the sidelink transmission resource of the shared frequency.
  • LBT failed. Specify a timer to reset the number of LBT failures corresponding to the destination address identifier when timeout occurs.
  • the number of designated timers is at least one, corresponding to at least one destination address identifier; the number of designated times thresholds is at least one, corresponding to at least one destination address identifier.
  • the network device sends a fourth RRC message to the terminal device, where the fourth RRC message carries a candidate sidelink transmission resource; wherein the candidate sidelink transmission resource includes a candidate sidelink with a shared frequency. Transmit resources or candidate sidelink transmit resources on non-shared frequencies.
  • the implementation of the sidelink communication method on the shared frequency is also applicable to the sidelink communication method on the unlicensed frequency.
  • the network device sends a first message to the terminal device.
  • the first message carries a specified timer and a specified number of times threshold, and is used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency, so that the terminal device fails in LBT.
  • data can be sent in time to avoid data loss and increase communication reliability.
  • FIG. 8 is a schematic flowchart of another sidelink communication method provided by an embodiment of the present disclosure.
  • the sidelink communication method can be applied to network equipment.
  • the sidelink communication method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any technical solution in related technologies. are executed together.
  • the sidelink communication method may include the following steps:
  • Step 801 Send the first message to the terminal device.
  • the first message may be an RRC message, for example.
  • the first message carries a specified timer and a specified times threshold, which are used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the first RRC message carries the same number of designated timers and designated times thresholds, and may carry one designated timer and one designated times threshold. Among them, a timer is specified to reset the number of LBT failures when timeout occurs.
  • the first message carries a specified timer corresponding to at least one shared frequency, and a specified times threshold corresponding to at least one shared frequency, and is used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency.
  • the specified timer is used to reset the number of LBT failures corresponding to the shared frequency when it times out; the specified timers corresponding to at least one shared frequency are the same or different; the specified number thresholds corresponding to at least one shared frequency are the same or different.
  • the number of designated timers is at least one, corresponding to at least one shared frequency; the number of designated times thresholds is at least one, corresponding to at least one shared frequency.
  • the first message carries a specified timer corresponding to at least one destination address identifier, and a specified times threshold corresponding to at least one destination address identifier, and is used to determine whether to trigger a continuous trigger on the sidelink transmission resource of the shared frequency.
  • LBT failed. Specify a timer to reset the number of LBT failures corresponding to the destination address identifier when timeout occurs.
  • the number of specified timers is at least one, corresponding to at least one destination address identifier; the number of specified times thresholds is at least one, corresponding to at least one destination address identifier.
  • Step 802 Receive a failure indication reported by the terminal device.
  • the failure indication is used to indicate a failure to trigger continuous LBT.
  • the network device schedules backup sidelink transmission resources to the terminal device according to the failure indication.
  • the backup sidelink transmission resources are resources transmitted through a sidelink with a shared frequency, or resources transmitted through a sidelink with a non-shared frequency.
  • the failure indication includes: the first shared frequency of the sidelink transmission resource of the shared frequency that triggers the persistent LBT failure.
  • the network device schedules sidelink transmission resources of other shared frequencies except the first shared frequency to the terminal device, or schedules sidelink transmission resources of non-shared frequencies to the terminal device.
  • the failure indication includes: a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers a persistent LBT failure.
  • the network device schedules, according to the failure indication, other shared frequency sidelink transmission resources to the terminal device other than the shared frequency sidelink transmission resources used for sidelink communication with the first destination address identification, or , scheduling sidelink transmission resources of non-shared frequencies to the terminal equipment.
  • the network device sends the first message to the terminal device and receives the failure indication reported by the terminal device.
  • the failure indication is used to indicate the triggering of the continuous LBT failure, so that the terminal device can send data in time when the LBT fails. Avoid data loss and increase communication reliability.
  • FIG. 9 is a schematic flowchart of another sidelink communication method provided by this embodiment of the disclosure.
  • the sidelink communication method can be applied to the destination terminal device.
  • the sidelink communication method can be executed alone, or can be executed in combination with any embodiment or possible implementation method in the embodiment, or in combination with any technical solution in related technologies. are executed together.
  • the sidelink communication method may include the following steps:
  • Step 901 Receive a failure indication sent by the terminal device, where the failure indication includes: a first destination address identifier, where sidelink communication with the first destination address identifier triggers a persistent LBT failure.
  • the failure indication stopping receiving sidelink messages of the terminal device on the sidelink transmission resource of the shared frequency where the persistent LBT failure occurs.
  • the failure indication when the backup sidelink transmission resource exists, the sidelink message of the terminal device is received on the backup sidelink transmission resource.
  • a sidelink RRC message of the terminal device is received, where the sidelink RRC message carries a failure indication.
  • a sidelink MAC CE message sent by the terminal device is received, where the sidelink MAC CE message carries a failure indication.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of terminal equipment, network equipment, and destination terminal equipment.
  • the terminal device, the network device and the destination terminal device may include a hardware structure and a software module to implement the above 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.
  • the present disclosure also provides a sidelink sidelink communication device. Since the embodiment of the present disclosure provides a sidelink sidelink communication device and the above-mentioned The sidelink communication methods provided by the embodiments of Figures 2 to 6 correspond to each other. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided by the embodiments of the present disclosure. In this disclosure Detailed description will not be given in the disclosed embodiments.
  • Figure 10 is a schematic structural diagram of a sidelink communication device provided by an embodiment of the present disclosure.
  • the sidelink communication device is applied to terminal equipment.
  • the sidelink communication device 1000 includes: a first processing unit 1010 and a second processing unit 1020 .
  • the first processing unit 1010 is used to determine whether the persistent LBT fails to be triggered on the sidelink transmission resource of the shared frequency; the second processing unit 1020 is used to report the failure to the network device when the persistent LBT fails to be triggered. Indicate or determine backup sidelink transmission resources for sending sidelink messages.
  • the first processing unit 1010 is specifically configured to determine that when the number of LBT failures on the sidelink transmission resource of the shared frequency is greater than or equal to a specified number threshold, Frequency sidelink transmit resource triggers persistent LBT failure.
  • the first processing unit 1010 is specifically configured to reset the current number of LBT failures to zero when the specified timer times out, and stop the specified timer. Timer; when an LBT failure occurs on the sidelink transmission resource of the shared frequency, start or restart the specified timer, and add 1 to the current number of LBT failures.
  • the sidelink communication device 1000 further includes: a transceiver unit configured to receive a first RRC message from a network device, where the first RRC message carries the specified The timer and the specified number of times threshold; the specified timer is used to reset the number of LBT failures when it times out.
  • the first processing unit 1010 is specifically configured to, when a first shared frequency exists in at least one shared frequency, determine the side link at the first shared frequency. Triggering continuous LBT failure on the transmission resource; wherein, on the sidelink transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to the specified number of times corresponding to the first shared frequency threshold.
  • the transceiver unit is further configured to receive a second RRC message from the network device, wherein the second RRC message carries: at least one designated timer corresponding to the shared frequency, and at least A threshold of specified times corresponding to a shared frequency; the specified timer is used to reset the number of LBT failures corresponding to the shared frequency when timeout occurs; the specified timers corresponding to the at least one shared frequency are the same or different; the at least The designated number thresholds corresponding to a shared frequency are the same or different.
  • the first processing unit 1010 is specifically configured to perform at least one destination address identification for sidelink communication on at least one sidelink transmission resource sharing a frequency.
  • a first destination address identifier it is determined that sidelink communication with the first destination address identifier triggers continuous LBT failure; wherein, the shared frequency used for sidelink communication with the first destination address identifier
  • the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the designated number threshold corresponding to the first destination address identifier.
  • the transceiver unit is further configured to receive a third RRC message from the network device, wherein the third RRC message carries: a designated timer corresponding to at least one destination address identifier, and The specified number of times threshold corresponding to at least one destination address identifier; the specified timer is used to reset the number of LBT failures corresponding to the destination address identifier when timeout; or, receive the third number of LBT failures corresponding to the at least one destination address identifier from the destination terminal device corresponding to the destination address identifier.
  • a sidelink RRC message wherein the first sidelink RRC message carries: a designated timer corresponding to the destination address identifier, and a designated times threshold corresponding to the destination address identifier; wherein, the at least one destination address identifier corresponds to The designated timers are the same or different; the designated number thresholds corresponding to the at least one destination address identifier are the same or different.
  • the second processing unit 1020 is specifically configured to report a first failure indication to the network device when the persistent LBT failure is triggered.
  • the second processing unit 1020 is specifically configured to, when triggering the persistent LBT failure, select the backup sidelink from at least one configured candidate sidelink transmission resource. Link sends resources.
  • the second processing unit 1020 is specifically configured to report the first shared frequency to the network device when the persistent LBT fails to be triggered on the sidelink transmission resource of the first shared frequency.
  • the second failure indication of the shared frequency wherein, on the sidelink transmission resource of the first shared frequency, the number of LBT failures corresponding to the first shared frequency is greater than or equal to the specified number of times corresponding to the first shared frequency threshold.
  • the second processing unit 1020 is specifically configured to: when the persistent LBT fails to be triggered on the sidelink transmission resource of the first shared frequency, from at least one configured candidate sidelink Select a candidate sidelink transmission resource of a shared frequency or a candidate sidelink transmission resource of a non-shared frequency among the transmission resources of the first shared frequency as the backup sidelink transmission resource; wherein, on the side of the first shared frequency On the downlink transmission resource, the number of LBT failures corresponding to the first shared frequency is greater than or equal to the designated number threshold corresponding to the first shared frequency.
  • the second processing unit 1020 is specifically configured to, when the sidelink communication with the first destination address identifier triggers the continuous LBT failure, report the first destination address identifier carrying the first message to the network device.
  • the third failure indication of the destination address identifier wherein, on the sidelink transmission resource of the shared frequency used for sidelink communication with the first destination address identifier, the LBT corresponding to the first destination address identifier fails The number of times is greater than or equal to the specified number of times threshold corresponding to the first destination address identifier.
  • the second processing unit 1020 is specifically configured to, when sidelink communication with the first destination address identifier triggers a persistent LBT failure, from at least one configured candidate sidelink Select a candidate sidelink transmission resource with a shared frequency or a candidate sidelink transmission resource with a non-shared frequency among the transmission resources as the backup sidelink transmission resource; wherein, the sidelink transmission resource used to communicate with the first destination address On the sidelink transmission resource that identifies the shared frequency for sidelink communication, the number of LBT failures corresponding to the first destination address identifier is greater than or equal to the specified number of times threshold corresponding to the first destination address identifier.
  • the transceiver unit is further configured to receive a fourth RRC message from the network device, wherein the fourth RRC message carries the candidate sidelink transmission resource; or, from The destination terminal device corresponding to at least one destination address identifier receives a second sidelink RRC message, wherein the second sidelink RRC message carries the candidate sidelink transmission resource message.
  • the transceiver unit is also configured to send a message to the destination terminal corresponding to the first destination address identifier when the sidelink communication with the first destination address identifier triggers the continuous LBT failure.
  • the device sends a fourth failure indication; wherein, on the sidelink transmission resource of the shared frequency used for sidelink communication with the first destination address identifier, the number of LBT failures corresponding to the first destination address identifier is greater than Or equal to the specified number of times threshold corresponding to the first destination address identifier.
  • the fourth failure indication is used to instruct the destination terminal device to stop receiving the sidelink transmission resource of the shared frequency where the persistent LBT failure occurs.
  • a sidelink message of the terminal device; or, the fourth failure indication is used to indicate that when a backup sidelink transmission resource exists, the sidelink is received on the backup sidelink transmission resource. information;
  • the fourth failure indication also carries: a second shared frequency; wherein, at least one shared frequency used for sidelink communication with the first destination address identification Among the sidelink transmission resources, the sidelink transmission resource of the second shared frequency triggers the persistent LBT failure.
  • the transceiver unit is further configured to send a third sidelink RRC message to the destination terminal device corresponding to the first destination address identification, wherein the third sidelink RRC message carries the the fourth failure indication; or, send a sidelink MAC CE message to the destination terminal device corresponding to the first destination address identifier, wherein the sidelink MAC CE message carries the fourth failure indication.
  • the sidelink communication device of the embodiment of the present disclosure is applied to terminal equipment and determines whether the sustained LBT fails to be triggered on the sidelink transmission resource of the shared frequency; when the sustained LBT fails to be triggered, a failure indication is reported to the network device. Or determine the backup sidelink transmission resources for sending sidelink messages, so that when the LBT fails, the terminal device can send data in time, avoid data loss, and increase communication reliability.
  • the present disclosure also provides a sidelink sidelink communication device. Since the embodiment of the present disclosure provides a sidelink sidelink communication device and the above-mentioned The sidelink communication method provided by the embodiments of FIG. 7 to FIG. 8 corresponds to the sidelink communication method. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided by the embodiment of the present disclosure. In this disclosure Detailed description will not be given in the disclosed embodiments.
  • Figure 11 is a schematic structural diagram of another sidelink communication device provided by an embodiment of the present disclosure.
  • the sidelink communication device is applied to network equipment.
  • the sidelink communication device 1100 includes a transceiver unit 1110.
  • the transceiver unit 1110 is used to send a first message to the terminal device; wherein the first message carries a specified timer and a specified number of times threshold, and is used to determine whether a persistent LBT failure is triggered on the sidelink transmission resource of the shared frequency. .
  • the number of designated timers is at least one, corresponding to at least one shared frequency; the number of designated times thresholds is at least one, corresponding to at least one shared frequency; or, The number of the designated timers is at least one, corresponding to at least one destination address identifier; the number of the designated times threshold is at least one, corresponding to at least one destination address identifier.
  • the transceiver unit 1110 is further configured to receive a failure indication reported by the terminal device, where the failure indication is used to indicate a failure to trigger the continuous LBT.
  • the method further includes: scheduling a backup sidelink transmission resource to the terminal device according to the failure indication; wherein the backup sidelink transmission resource is , sending resources through a sidelink with a shared frequency, or sending resources through a sidelink with a non-shared frequency.
  • the failure indication includes: the first shared frequency of the sidelink transmission resource of the shared frequency that triggers the persistent LBT failure; or, the failure indication includes: the first destination address Identification, wherein sidelink communication with the first destination address identification triggers persistent LBT failure.
  • the sidelink communication device of the embodiment of the present disclosure is applied to network equipment and sends a first message to the terminal device.
  • the first message carries a specified timer and a specified number of times threshold, and is used to determine the sidelink transmission of the shared frequency. Whether continuous LBT failure is triggered on the resource allows the terminal device to send data in time when LBT fails, avoiding data loss and increasing communication reliability.
  • the present disclosure also provides a sidelink sidelink communication device, because the sidelink communication device provided by the embodiment of the present disclosure is consistent with the above-mentioned implementation of Figure 9
  • the sidelink communication method provided in the example corresponds to the sidelink communication method. Therefore, the implementation of the sidelink communication method is also applicable to the sidelink communication device provided in the embodiment of the present disclosure, and is no longer used in the embodiment of the present disclosure. A detailed description.
  • Figure 12 is a schematic structural diagram of another sidelink communication device provided by an embodiment of the present disclosure.
  • the sidelink communication device is applied to the destination terminal equipment.
  • the sidelink communication device 1200 includes a transceiver unit 1210.
  • the transceiver unit 1210 is configured to receive a failure indication sent by the terminal device, wherein the failure indication includes: a first destination address identifier, wherein sidelink communication with the first destination address identifier triggers continuous LBT failed.
  • the failure indication stop receiving sidelink messages of the terminal device on the sidelink transmission resource of the shared frequency where the persistent LBT failure occurs; or , according to the failure indication, when a backup sidelink transmission resource exists, receive a sidelink message of the terminal device on the backup sidelink transmission resource.
  • the transceiver unit 1210 is also configured to receive a sidelink RRC message from the terminal device, where the sidelink RRC message carries the failure indication; or, receive a sidelink RRC message sent by the terminal device.
  • sidelink MAC CE message wherein the sidelink MAC CE message carries the failure indication.
  • the present disclosure also proposes a sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory, so that the device The sidelink communication method described in the embodiments of Figures 2 to 6 is executed.
  • the present disclosure also proposes another sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory so that the The device executes the sidelink communication method described in the embodiments of Figures 7 to 8.
  • the present disclosure also proposes another sidelink communication device.
  • the device includes a processor and a memory.
  • a computer program is stored in the memory.
  • the processor executes the computer program stored in the memory so that the The device executes the sidelink communication method described in the embodiment of FIG. 9 .
  • the present disclosure also proposes a sidelink communication method, including: 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 are used to execute the sidelink communication method described in the embodiments of FIGS. 2 to 6 .
  • the present disclosure also proposes another sidelink communication method, including: 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 execute the sidelink communication method described in the embodiments of Figures 7 to 8.
  • the present disclosure also proposes another sidelink communication method, including: 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 code instructions to execute the sidelink communication method described in the embodiment of FIG. 9 .
  • the present disclosure proposes a computer-readable storage medium for storing instructions.
  • the sidelink communication method of the embodiments described in Figures 2 to 6 is used. accomplish.
  • the present disclosure proposes another computer-readable storage medium for storing instructions.
  • the sidelink communication method of the embodiments described in Figures 7 to 8 is used. be realized.
  • the present disclosure proposes another computer-readable storage medium for storing instructions.
  • the instructions When the instructions are executed, the sidelink communication method of the embodiment described in Figure 9 is implemented.
  • FIG. 13 is a schematic structural diagram of a network device provided by an embodiment of the present disclosure.
  • network device 1300 includes a processing component 1322, which further includes at least one processor, and memory resources represented by memory 1332 for storing instructions, such as application programs, executable by processing component 1322.
  • the application program stored in memory 1332 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 1322 is configured to execute instructions to perform any of the foregoing methods applied to the network device, for example, the methods in the embodiments of FIGS. 7 to 8 .
  • Network device 1300 may also include a power supply component 1326 configured to perform power management of network device 1300, a wired or wireless network interface 1350 configured to connect network device 1300 to a network, and an input-output (I/O) interface 1358 .
  • Network device 1300 may operate based on an operating system stored in memory 1332, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • Figure 14 is a block diagram of a terminal device provided by an embodiment of the present disclosure.
  • the terminal device 1400 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • the terminal device 1400 may include at least one of the following components: a processing component 1402, a memory 1404, a power supply component 1406, a multimedia component 1408, an audio component 1410, an input/output (I/O) interface 1412, a sensor component 1414, and Communication component 1416.
  • a processing component 1402 a memory 1404, a power supply component 1406, a multimedia component 1408, an audio component 1410, an input/output (I/O) interface 1412, a sensor component 1414, and Communication component 1416.
  • the processing component 1402 generally controls the overall operations of the terminal device 1400, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 1402 may include at least one processor 1420 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 1402 may include at least one module that facilitates interaction between processing component 1402 and other components. For example, processing component 1402 may include a multimedia module to facilitate interaction between multimedia component 1408 and processing component 1402.
  • the memory 1404 is configured to store various types of data to support operations at the terminal device 1400 . Examples of such data include instructions for any application or method operating on the terminal device 1400, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 1404 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic or optical disk.
  • Power supply component 1406 provides power to various components of terminal device 1400.
  • Power supply component 1406 may include a power management system, at least one power supply, and other components associated with generating, managing, and distributing power to end device 1400.
  • Multimedia component 1408 includes a screen providing an output interface between the terminal device 1400 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes at least one touch sensor to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense the boundary of the touch or sliding operation, but also detect the wake-up time and pressure related to the touch or sliding operation.
  • multimedia component 1408 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 1410 is configured to output and/or input audio signals.
  • the audio component 1410 includes a microphone (MIC) configured to receive external audio signals when the terminal device 1400 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signals may be further stored in memory 1804 or sent via communications component 1416 .
  • audio component 1410 also includes a speaker for outputting audio signals.
  • the I/O interface 1412 provides an interface between the processing component 1402 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • the sensor component 1414 includes at least one sensor for providing various aspects of status assessment for the terminal device 1400 .
  • the sensor component 1414 can detect the open/closed state of the terminal device 1400 and the relative positioning of components, such as the display and keypad of the terminal device 1400.
  • the sensor component 1414 can also detect the terminal device 1400 or one of the terminal devices 1400. Changes in the position of components, presence or absence of user contact with the terminal device 1400 , orientation or acceleration/deceleration of the terminal device 1400 and temperature changes of the terminal device 1400 .
  • Sensor assembly 1414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1414 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 1414 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 1416 is configured to facilitate wired or wireless communication between the terminal device 1400 and other devices.
  • the terminal device 1400 can access a wireless network based on communication standards, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 1416 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communications component 1416 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the terminal device 1400 may be configured by at least one application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate Array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above methods shown in Figures 2 to 5.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • DSPD digital signal processing device
  • PLD programmable logic device
  • FPGA field programmable gate Array
  • controller microcontroller, microprocessor or other electronic components are implemented for executing the above methods shown in Figures 2 to 5.
  • a non-transitory computer-readable storage medium including instructions such as a memory 1404 including instructions, which can be executed by the processor 1420 of the terminal device 1400 to complete the above-described FIGS. 2 to 6 is also provided.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • inventions of the present disclosure also provide a communication device.
  • the communication device may be a network device, a user device, or a chip, chip system, or processor that supports the network device to implement the above method. , it can also be a chip, chip system, or processor that supports the user equipment to implement the above method.
  • the device can be used to implement the method described in any of the above method embodiments. For details, please refer to the description in the above method embodiments.
  • the communication device may include one or more processors.
  • the processor may be a general-purpose processor or a special-purpose processor, etc.
  • 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, user equipment, user equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device may also include one or more memories, on which a computer program may be stored, and the processor executes the computer program, so that the communication device executes the method described in the above method embodiment.
  • data may also be stored in the memory.
  • the communication device and the memory can be provided separately or integrated together.
  • the communication device may also include a transceiver and an antenna.
  • the transceiver can be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver can include a receiver and a transmitter.
  • the receiver can be called a receiver or a receiving circuit, etc., and is used to implement the receiving function;
  • the transmitter can be called a transmitter or a transmitting circuit, etc., and is used to implement the transmitting function.
  • the communication device may also include one or more interface circuits.
  • Interface circuitry is used to receive code instructions and transmit them to the processor.
  • the processor executes the code instructions to cause the communication device to perform the method described in any of the above method embodiments.
  • a transceiver for implementing receiving and transmitting functions may be included in the processor.
  • 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 may store a computer program, and the computer program runs on the processor, causing the communication device to perform the method described in any of the above method embodiments.
  • the computer program may be embedded in the processor, in which case the processor may be implemented in hardware.
  • the communication device may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processor and transceiver described in this disclosure can be implemented in IC (Integrated Circuit, integrated circuit), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, ASIC (Application Specific Integrated Circuit, application specific integrated circuit), PCB (Printed Circuit) Board, printed circuit board), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as CMOS (Complementary Metal Oxide Semiconductor, complementary metal oxide semiconductor), NMOS (nMetal-Oxide-Semiconductor, N-type metal oxide semiconductor), PMOS ( Positive Channel Metal Oxide Semiconductor, P-type metal oxide semiconductor), BJT (Bipolar Junction Transistor, bipolar junction transistor), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS Complementary Metal Oxide Semiconductor, complementary metal oxide semiconductor
  • NMOS nMetal-Oxide-Semiconductor, N-type metal oxide semiconductor
  • PMOS Positive Channel Metal Oxide Semiconductor, P-type metal oxide semiconductor
  • BJT Bipolar Junction Transistor, bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a user equipment, but the scope of the communication device described in the present disclosure is not limited thereto.
  • 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 system on a chip
  • the chip may include a processor and an interface.
  • the number of processors may be one or more, and the number of interfaces may be multiple.
  • the chip also includes a memory, which is used to store necessary computer programs and data.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of the embodiments of Figures 2 to 6 described above.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of the embodiments of FIGS. 7 to 8 described above.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of the embodiment of FIG. 9 described above.
  • 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, DSL (Digital Subscriber Line)) 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 available media may be magnetic media (for example, floppy disks, hard disks, magnetic tapes), optical media (for example, high-density DVD (Digital Video Disc, Digital Video Disc)), or semiconductor media (for example, SSD (Solid State Disk, Solid State Disk) Hard drive)) etc.
  • magnetic media for example, floppy disks, hard disks, magnetic tapes
  • optical media for example, high-density DVD (Digital Video Disc, Digital Video Disc)
  • semiconductor media for example, SSD (Solid State Disk, Solid State Disk) Hard drive
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种侧行链路sidelink通信方法及装置，属于通信技术领域，其中，侧行链路sidelink通信方法应用于终端设备，该方法包括：确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；在触发持续LBT失败时，向网络设备上报失败指示或确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。

Description

侧行链路sidelink通信方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种侧行链路sidelink通信方法及装置。
背景技术
目前，为了支持用户终端(user equipment，UE)与用户终端之间的直接通信，引入了sidelink(侧行链路)通信方式，用户终端与用户终端之间的接口为PC-5。
用户终端(user equipment，UE)在共享频率的侧行链路发送资源上进行sidelink发送时，需要进行先听后发(LBT，listen before talk)，可能会出现LBT失败，在LBT失败时，用户终端持续等待，可能导致数据发送延迟，甚至数据丢失。
发明内容
本公开第一方面实施例提供了一种侧行链路sidelink通信方法，所述方法由终端设备执行，所述方法包括确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；在触发所述持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
在该技术方案中，终端设备确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开第二方面实施例提出了另一种侧行链路sidelink通信方法，应用于网络设备，所述方法包括向终端设备发送第一消息；其中，所述第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。
本公开第三方面实施例提出了一种侧行链路sidelink通信方法，应用于目的终端设备，所述方法包括：接收所述终端设备发送的失败指示，其中，所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
本公开第四方面实施例提出了一种侧行链路sidelink通信装置，应用于终端设备，所述装置包括：第一处理单元，用于确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；第二处理单元，用于在触发所述持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
本公开第五方面实施例提出了另一种侧行链路sidelink通信装置，应用于网络设备，所述装置包括：收发单元，用于向终端设备发送第一消息；其中，所述第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。
本公开第六方面实施例提出了另一种侧行链路sidelink通信装置，应用于目的终端设备，所述装置包括：收发单元，用于接收所述终端设备发送的失败指示，其中，所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
本公开第七方面实施例提出了一种侧行链路sidelink通信装置，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行本公开第一方面实施例所述的方法。
本公开第八方面实施例提出了另一种侧行链路sidelink通信装置，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行本公开第二方面实施例所述的方法。
本公开第九方面实施例提出了另一种侧行链路sidelink通信装置，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行本公开第三方面实施例所述的方法。
本公开第十方面实施例提出了一种侧行链路sidelink通信装置，其特征在于，包括：处理器和接口电路；所述接口电路，用于接收代码指令并传输至所述处理器；所述处理器，用于运行所述代码指令以执行本公开第一方面实施例所述的方法。
本公开第十一方面实施例提出了另一种侧行链路sidelink通信装置，其特征在于，包括：处理器和接口电路；所述接口电路，用于接收代码指令并传输至所述处理器；所述处理器，用于运行所述代码指令以执行本公开第二方面实施例所述的方法。
本公开第十二方面实施例提出了另一种侧行链路sidelink通信装置，其特征在于，包括：处理器和 接口电路；所述接口电路，用于接收代码指令并传输至所述处理器；所述处理器，用于运行所述代码指令以执行本公开第三方面实施例所述的方法。
本公开第十三方面实施例提出了一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使本公开第一方面实施例所述的方法被实现。
本公开第十四方面实施例提出了另一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使本公开第二方面实施例所述的方法被实现。
本公开第十五方面实施例提出了另一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使本公开第三方面实施例所述的方法被实现。
本公开第十六方面实施例提出了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面实施例所述的方法。
本公开第十七方面实施例提出了另一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面实施例所述的方法。
本公开第十八方面实施例提出了另一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第三方面实施例所述的方法。
本公开附加的方面和优点将在下面的描述中部分给出，将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1为本公开实施例提供的一种通信系统结构示意图；
图2为本公开实施例提供的一种侧行链路sidelink通信方法的流程示意图；
图3为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图4为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图5为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图6为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图7为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图8为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图9为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图；
图10为本公开实施例所提供的一种侧行链路sidelink通信装置的结构示意图；
图11为本公开实施例所提供的另一种侧行链路sidelink通信装置的结构示意图；
图12为本公开实施例所提供的另一种侧行链路sidelink通信装置的结构示意图；
图13为本公开实施例所提供的一种网络设备的结构示意图；
图14为本公开实施例所提供的一种终端设备的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在……时”或“当……时”或“响应于确定”。
请参见图1，图1为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统仅以包括一个网络设备101、一个终端设备102为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的网络设备101是网络侧的一种用于发射或接收信号的实体。例如，网络设备101可以为演进型基站(evolved NodeB，eNB)、传输接收点(transmission reception point或transmit receive 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是用户侧的一种用于接收或者发射信号的实体，如手机。终端设备也可以称为终端设备(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)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
为了支持用户终端(user equipment，UE)与用户终端(user equipment，UE)之间的直接通信，引入了sidelink(侧行链路)通信方式，用户终端与用户终端之间的接口为PC-5。根据发送用户终端和接收用户终端的对应关系，在sidelink上支持三种传输方式，单播，组播和广播。在单播连接中，每个UE都对应一个目的地址标识；在组播中，每个UE可以属于一个或者多个组，每个组与一个目的地址标识相对应，在广播中，所有UE都至少与一个目的地址标识相对应。
当UE发送sidelink数据时，需要根据目的地址和源地址来进行寻址，应用层将源层2地址和目的层2地址发送给接入层，长度为24比特。其中，源层2地址的低位8在SCI中携带，成为源层1地址，剩余的16比特在MAC子头中携带。目的层2地址的低16位在SCI中携带，成为目的层1地址，剩余的8比特在MAC子头中携带。
如果某个单播连接发生了sidelink无线链路失败或者sidelink配置失败，UE向网络设备上报发生失败的单播连接的目的UE的目的地址标识以及失败原因，其中，失败原因包括sidelink无线链路失败或者sidelink配置失败。
当UE在共享频率(非授权频谱)上进行上行发送时，UE需要进行LBT(Listen Before Talk，先听后发)，当LBT失败时，物理层会通知介质访问控制层(Media Access Control，MAC)层。收到LBT失败指示时，MAC启动或者重启指定定时器(lbt-FailureDetectionTimer)，同时LBT失败次数加一。如果指定定时器超时，则重置LBT失败次数为0。如果LBT失败次数达到指定次数阈值(lbt-FailureInstanceMaxCount)，则触发持续LBT失败。其中指定定时器和指定次数阈值为网络设备通过无线资源控制(Radio Resource Control，RRC)消息配置。
如果服务小区的所有上行部分带宽(band width part，BWP)都触发了持续LBT失败，则这个服务小区发生无线链路失败(Radio Link Failure，RLF)；否则，UE将激活上行BWP切换到没有发生持续LBT失败的上行BWP。
用户终端在共享频率的侧行链路发送资源上进行sidelink发送时，需要进行先听后发(LBT，listen before talk)，可能会出现LBT失败，在LBT失败时，用户终端持续等待，可能导致数据发送延迟，甚至数据丢失。
针对上述问题，本公开提出了侧行链路sidelink通信方法及装置。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本公开所提供的侧行链路sidelink通信方法及装置进行详细地介绍。
请参见图2，图2为本公开实施例提供的一种侧行链路sidelink通信方法的流程示意图。该侧行链 路sidelink通信方法可以由图1所示的通信系统中的终端设备执行。
如图2所示，该侧行链路sidelink通信方法可包括如下步骤：
步骤201，确定在共享频率的侧行链路发送资源上是否触发持续LBT失败。
本公开实施例中，在共享频率的侧行链路发送资源上的LBT失败次数大于或者等于指定次数阈值时，确定在共享频率的侧行链路发送资源上触发持续LBT失败。在指定定时器内的LBT失败次数小于指定次数阈值时，确定在共享频率的侧行链路发送资源上未触发持续LBT失败。
步骤202，在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
其中，备用侧行链路发送资源可以是共享频率的侧行链路发送资源，也可以是非共享频率上的侧行链路发送资源。
本公开实施例中，在一种示例中，在触发持续LBT失败时，终端设备向网络设备上报第一失败指示，根据网络设备调度的备用侧行链路发送资源，发送侧行链路消息。
本公开实施例中，在另一种示例中，在触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择备用侧行链路发送资源，用于发送侧行链路消息。其中，可以从至少一个候选侧行链路发送资源中选择没有触发持续LBT失败的共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
本公开实施例中，在一种示例中，终端设备从网络设备接收第四RRC消息，其中，第四RRC消息携带候选侧行链路发送资源；其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
在另一种示例中，终端设备从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，第二sidelink RRC消息携带候选侧行链路发送资源消息。其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，通过确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图3为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图，该侧行链路sidelink通信方法可应用于终端设备，该侧行链路sidelink通信方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图3所示，该侧行链路sidelink通信方法可包括如下步骤：
步骤301，在共享频率的侧行链路发送资源上的LBT失败次数大于或者等于指定次数阈值时，确定在共享频率的侧行链路发送资源上触发持续LBT失败。
本公开实施例中，终端设备确定共享频率的侧行链路发送资源上的LBT失败次数的过程例如可以为，在指定定时器超时时，将当前的LBT失败次数重置为零值，并停止指定定时器；在共享频率的侧行链路发送资源上发生LBT失败时，启动或者重启指定定时器，对当前的LBT失败次数进行加1处理。
本公开实施例中，在共享频率的侧行链路发送资源上发生LBT失败时，若指定定时器未启动过，则启动指定定时器，LBT失败次数，进行加1处理；若指定定时器未停止或者启动过了，则重启指定定时器，LBT失败次数，进行加1处理。
其中，共享频率的侧行链路发送资源上的LBT失败次数包括所有共享频率的所有侧行链路发送资源上的LBT失败次数。
本公开实施例中，在指定定时器内的LBT失败次数小于指定次数阈值时，确定在共享频率的侧行链路发送资源上未触发持续LBT失败。
本公开实施例中，终端设备在确定在共享频率的侧行链路发送资源上是否触发持续LBT失败之前，从网络设备接收第一RRC消息，其中，第一RRC消息携带指定定时器和指定次数阈值；指定定时器，用于在超时时重置LBT失败次数。
其中，第一RRC消息携带的指定定时器和指定次数阈值的数量相同，可以携带一个指定定时器和一个指定次数阈值。
步骤302，在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
本公开实施例中，在一种示例中，在触发持续LBT失败时，终端设备向网络设备上报第一失败指示，根据网络设备调度的备用侧行链路发送资源，发送侧行链路消息。
本公开实施例中，在另一种示例中，在触发持续LBT失败时，终端设备可以从配置的至少一个候选侧行链路发送资源中选择备用侧行链路发送资源，用于发送侧行链路消息。其中，可以从至少一个候选侧行链路发送资源中选择没有触发持续LBT失败的共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
本公开实施例中，在一种示例中，终端设备从网络设备接收第四RRC消息，其中，第四RRC消息携带候选侧行链路发送资源；其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
在另一种示例中，终端设备从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，第二sidelink RRC消息携带候选侧行链路发送资源消息。其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，通过在共享频率的侧行链路发送资源上的LBT失败次数大于或者等于指定次数阈值时，确定在共享频率的侧行链路发送资源上触发持续LBT失败；在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图4为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图，该侧行链路sidelink通信方法可应用于终端设备，该路径切换方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图4所示，该侧行链路sidelink通信方法可包括如下步骤：
步骤401，在至少一个共享频率中存在第一共享频率时，确定在第一共享频率的侧行链路发送资源上触发持续LBT失败。
其中，在第一共享频率的侧行链路发送资源上，第一共享频率对应的LBT失败次数大于或者等于第一共享频率对应的指定次数阈值。
其中，在第一共享频率对应的LBT失败次数小于第一共享的频率对应指定次数阈值时，确定在第一共享频率的侧行链路发送资源上未触发持续LBT失败。
本公开实施例中，终端设备确定在至少一个共享频率中是否存在第一共享频率之前，从网络设备接收第二RRC消息，其中，第二RRC消息携带：至少一个共享频率对应的指定定时器，以及至少一个共享频率对应的指定次数阈值；其中，指定定时器，用于在超时时重置共享频率对应的LBT失败次数。
在本公开实施例中，至少一个共享频率对应的指定定时器相同或者不同；至少一个共享频率对应的指定次数阈值相同或者不同。
其中，共享频率有多个，指定定时器为多个，指定次数阈值为多个。在一种示例中，每个共享频率可以对应一个指定定时器，每个共享频率可以对应一个指定次数阈值。在另一种示例中，多个共享频率可以对应一个指定定时器，多个共享频率可以对应的一个指定次数阈值。
步骤402，在第一共享频率的侧行链路发送资源上触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
本公开实施例中，在一种示例中，在第一共享频率的侧行链路发送资源上触发持续LBT失败时，向网络设备上报携带第一共享频率的第二失败指示，根据网络设备调度的备用侧行链路发送资源，发送侧行链路消息。
在另一种示例中，在第一共享频率的侧行链路发送资源上触发持续LBT失败时，终端设备可以从配置的至少一个候选侧行链路发送资源中选择备用侧行链路发送资源，用于发送侧行链路消息。
其中，可以从至少一个候选侧行链路发送资源中选择没有触发持续LBT失败的共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
本公开实施例中，在一种示例中，终端设备从网络设备接收第四RRC消息，其中，第四RRC消息 携带候选侧行链路发送资源；其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
在另一种示例中，终端设备从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，第二sidelink RRC消息携带候选侧行链路发送资源消息。其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，在至少一个共享频率中存在第一共享频率时，确定在第一共享频率的侧行链路发送资源上触发持续LBT失败；其中，在第一共享频率的侧行链路发送资源上，第一共享频率对应的LBT失败次数大于或者等于第一共享频率对应的指定次数阈值；在第一共享频率的侧行链路发送资源上触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图5为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图，该侧行链路sidelink通信方法可应用于终端设备，该侧行链路sidelink通信方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
步骤501，在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与第一目的地址标识进行侧行链路通信触发持续LBT失败。
其中，用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，第一目的地址标识对应的LBT失败次数大于或者等于第一目的地址标识对应的指定次数阈值。
其中，用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，第一目的地址标识对应的LBT失败次数小于第一目的地址标识对应的指定次数阈值时，确定与第一目的地址标识进行侧行链路通信未触发持续LBT失败。
本公开实施例中，在一种示例中，在确定在共享频率的侧行链路发送资源上是否触发持续LBT失败之前，终端设备从网络设备接收第三RRC消息，其中，第三RRC消息携带：至少一个目的地址标识对应的指定定时器，以及至少一个目的地址标识对应的指定次数阈值；指定定时器，用于在超时时重置目的地址标识对应的LBT失败次数。
在另一种示例中，从至少一个目的地址标识对应的目的终端设备接收第一sidelink RRC消息，其中，第一sidelink RRC消息携带：目的地址标识对应的指定定时器，以及目的地址标识对应的指定次数阈值。
其中，至少一个目的地址标识对应的指定定时器相同或者不同；至少一个目的地址标识对应的指定次数阈值相同或者不同。
步骤502，在确定与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
本公开实施例中，在一种示例中，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报携带第一目的地址标识的第三失败指示；根据网络设备调度的备用侧行链路发送资源，发送侧行链路消息。
本公开实施例中，在另一种示例中，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，终端设备可以从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
其中，终端从配置的至少一个候选侧行链路发送资源中选择没有触发持续LBT失败的共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源，用于发送侧行链路消息。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与第一目的地址标识进行侧行链路通信触发持续LBT失败；其中，用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，第一目的地址标识对应的LBT失败次数大于或者等于第一目的地址标识对应的指定次数阈值；在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图6为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图，该侧行链路sidelink通信方法可应用于终端设备，该侧行链路sidelink通信方法可以由图1中的终端设备执行。
如图6所示，该侧行链路sidelink通信方法可包括如下步骤：
步骤601，在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与第一目的地址标识进行侧行链路通信触发持续LBT失败。
其中，用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，第一目的地址标识对应的LBT失败次数大于或者等于第一目的地址标识对应的指定次数阈值。
步骤602，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向第一目的地址标识对应的目的终端设备发送第四失败指示。
本公开实施例中，在一种示例中，第四失败指示，用于指示目的终端设备停止在发生持续LBT失败的共享频率的侧行链路发送资源上接收终端设备的侧行链路消息。
在另一种示例中，第四失败指示，用于指示在备用侧行链路发送资源存在时，在备用侧行链路发送资源上接收侧行链路消息。
本公开实施例中，第四失败指示还携带：第二共享频率。其中，与第一目的地址标识进行侧行链路通信使用的至少一个共享频率的侧行链路发送资源中，第二共享频率的侧行链路发送资源触发持续LBT失败。
本公开实施例中，终端设备向目的终端设备发送携带第二共享频率的第四失败指示，第二共享频率的侧行链路发送资源触发持续LBT失败，也就是说，第二共享频率的侧行链路发送资源无法发送侧行链路消息。
本公开实施例中，在一种示例中，向第一目的地址标识对应的目的终端设备发送第三sidelink RRC消息，其中，第三sidelink RRC消息携带第四失败指示。在另一种示例中，向第一目的地址标识对应的目的终端设备发送sidelink MAC CE消息，其中，sidelink MAC CE消息携带第四失败指示。
步骤603，在确定与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
本公开实施例中，在一种示例中，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，终端设备可以从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
其中，终端从配置的至少一个候选侧行链路发送资源中选择没有触发持续LBT失败的共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源，用于发送侧行链路消息。
在另一种示例中，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择非共享频率的候选侧行链路发送资源，作为备用侧行链路发送资源。
本公开实施例中，在一种示例中，从网络设备接收第四RRC消息，其中，第四RRC消息携带候选侧行链路发送资源；其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
在另一种示例中，从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，第二sidelink RRC消息携带候选侧行链路发送资源消息。其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与第一目的地址标识进行侧行链路通信触发持续LBT失败；其中，用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，第一目的地址标识对应的LBT失败次数大于或者等于第一目的地址标识对应的指定次数阈值。在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向第一目的地址标识对应的目的终端设备发送第四失败指示；在确定与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图7为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图，该侧行链路sidelink通信方法可应用于网络设备，该侧行链路sidelink通信方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图7所示，该侧行链路sidelink通信方法可包括如下步骤：
步骤701，向终端设备发送第一消息。
本公开实施例中，第一消息例如可以为RRC消息。在一种示例中，第一消息携带一个指定定时器和一个指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。其中，第一RRC消息携带的指定定时器和指定次数阈值的数量相同，可以携带一个指定定时器和一个指定次数阈值。其中，指定定时器，用于在超时时重置LBT失败次数。
在另一种示例中，第一消息携带至少一个共享频率对应的指定定时器，以及至少一个共享频率对应的指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。指定定时器，用于在超时时重置共享频率对应的LBT失败次数；至少一个共享频率对应的指定定时器相同或者不同；至少一个共享频率对应的指定次数阈值相同或者不同。
其中，指定定时器的数量为至少一个，与至少一个共享频率对应；指定次数阈值的数量为至少一个，与至少一个共享频率对应。
在另一种示例中，第一消息携带至少一个目的地址标识对应的指定定时器，以及至少一个目的地址标识对应的指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。指定定时器，用于在超时时重置目的地址标识对应的LBT失败次数。
其中，指定定时器的数量为至少一个，与至少一个目的地址标识对应；指定次数阈值的数量为至少一个，与至少一个目的地址标识对应。
本公开实施例中，网络设备向终端设备发送第四RRC消息，其中，第四RRC消息携带候选侧行链路发送资源；其中，候选侧行链路发送资源包括共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源。
上述本公开提供的实施例中，共享频率上的侧行链路sidelink通信方法的实施方式也适用非授权频率的侧行链路sidelink通信方法。
综上，网络设备通过向终端设备发送第一消息，第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图8为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图。该侧行链路sidelink通信方法可应用于网络设备。该侧行链路sidelink通信方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图8所示，该侧行链路sidelink通信方法可以包括如下步骤：
步骤801，向终端设备发送第一消息。
本公开实施例中，第一消息例如可以为RRC消息。在一种示例中，第一消息携带一个指定定时器和一个指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。其中，第一RRC消息携带的指定定时器和指定次数阈值的数量相同，可以携带一个指定定时器和一个指定次数阈值。其中，指定定时器，用于在超时时重置LBT失败次数。
在另一种示例中，第一消息携带至少一个共享频率对应的指定定时器，以及至少一个共享频率对应的指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。指定定时器，用于在超时时重置共享频率对应的LBT失败次数；至少一个共享频率对应的指定定时器相同或者不同；至少一个共享频率对应的指定次数阈值相同或者不同。
其中，指定定时器的数量为至少一个，与至少一个共享频率对应；指定次数阈值的数量为至少一个，与至少一个共享频率对应。
在另一种示例中，第一消息携带至少一个目的地址标识对应的指定定时器，以及至少一个目的地址标识对应的指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。指定定时器，用于在超时时重置目的地址标识对应的LBT失败次数。
其中，指定定时器的数量为至少一个，与至少一个目的地址标识对应；指定次数阈值的数量为至少 一个，与至少一个目的地址标识对应。
步骤802，接收终端设备上报的失败指示，失败指示用于指示触发持续LBT失败。
本公开实施例中，网络设备根据失败指示，向终端设备调度备用侧行链路发送资源。其中，备用侧行链路发送资源为，通过共享频率的侧行链路发送资源，或者，通过非共享频率的侧行链路发送资源。
本公开实施例中，在一种示例中，失败指示包括：触发持续LBT失败的共享频率的侧行链路发送资源的第一共享频率。网络设备根据失败指示，向终端设备调度除第一共享频率以外的其他共享频率的侧行链路发送资源，或者，向终端设备调度非共享频率的侧行链路发送资源。
在另一种示例中，失败指示包括：第一目的地址标识，其中，与第一目的地址标识进行侧行链路通信触发持续LBT失败。网络设备根据失败指示，向终端设备调度除与第一目的地址标识进行侧行链路通信所使用的共享频率的侧行链路发送资源以外的的其他共享频率的侧行链路发送资源，或者，向终端设备调度非共享频率的侧行链路发送资源。
需要说明的是，前述任一实施例对终端设备执行的侧行链路sidelink通信方法的解释说明，也适用于该网络设备执行的侧行链路sidelink通信方法，其实现原理类似，在此不做赘述。
综上，网络设备通过向终端设备发送向终端设备发送第一消息；接收终端设备上报的失败指示，失败指示用于指示触发持续LBT失败，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
本公开实施例提供了另一种侧行链路sidelink通信方法，图9为本公开实施例提供的另一种侧行链路sidelink通信方法的流程示意图。该侧行链路sidelink通信方法可应用于目的终端设备。该侧行链路sidelink通信方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图9所示，该侧行链路sidelink通信方法可以包括如下步骤：
步骤901，接收终端设备发送的失败指示，其中，失败指示包括：第一目的地址标识，其中，与第一目的地址标识进行侧行链路通信触发持续LBT失败。
本公开实施例中，在一种示例中，根据失败指示，停止在发生持续LBT失败的共享频率的侧行链路发送资源上接收终端设备的侧行链路消息。在另一种示例中，根据失败指示，在备用侧行链路发送资源存在时，在备用侧行链路发送资源上接收终端设备的侧行链路消息。
本公开实施例中，在一种示例中，接收终端设备的sidelink RRC消息，其中，sidelink RRC消息携带失败指示。在另一种示例中，接收终端设备发送的sidelink MAC CE消息，其中，sidelink MAC CE消息携带失败指示。
需要说明的是，前述任一实施例对终端设备执行的侧行链路sidelink通信方法的解释说明，也适用于该目的终端设备执行的侧行链路sidelink通信方法，其实现原理类似，在此不做赘述。
需要说明的是，上述的这些可能的实现方式可以单独被执行，也可以结合在一起被执行，本公开实施例并不对此作出限定。
上述本公开提供的实施例中，从终端设备、网络设备和目的终端设备的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，终端设备、网络设备和目的终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
与上述图2至图6实施例提供的侧行链路sidelink通信方法相对应，本公开还提供一种侧行链路sidelink通信装置，由于本公开实施例提供侧行链路sidelink通信装置与上述图2至图6实施例提供的侧行链路sidelink通信方法相对应，因此在侧行链路sidelink通信方法的实施方式也适用于本公开实施例提供的侧行链路sidelink通信装置，在本公开实施例中不再详细描述。
图10为本公开实施例所提供的一种侧行链路sidelink通信装置的结构示意图。该侧行链路sidelink通信装置应用于终端设备。
如图10所示，侧行链路sidelink通信装置1000包括：第一处理单元1010和第二处理单元1020。
其中，第一处理单元1010，用于确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；第二处理单元1020，用于在触发所述持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
作为本公开实施例的一种可能的实现方式，所述第一处理单元1010具体用于，在共享频率的侧行链路发送资源上的LBT失败次数大于或者等于指定次数阈值时，确定在共享频率的侧行链路发送资源 上触发持续LBT失败。
作为本公开实施例的一种可能的实现方式，所述第一处理单元1010具体用于，在指定定时器超时时，将当前的所述LBT失败次数重置为零值，并停止所述指定定时器；在共享频率的侧行链路发送资源上发生LBT失败时，启动或者重启指定定时器，对当前的所述LBT失败次数进行加1处理。
作为本公开实施例的一种可能的实现方式，侧行链路sidelink通信装置1000还包括：收发单元，用于从网络设备接收第一RRC消息，其中，所述第一RRC消息携带所述指定定时器和所述指定次数阈值；所述指定定时器，用于在超时时重置所述LBT失败次数。
作为本公开实施例的一种可能的实现方式，所述第一处理单元1010具体用于，在至少一个共享频率中存在第一共享频率时，确定在所述第一共享频率的侧行链路发送资源上触发持续LBT失败；其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，收发单元还用于，从网络设备接收第二RRC消息，其中，所述第二RRC消息携带：至少一个共享频率对应的指定定时器，以及至少一个共享频率对应的指定次数阈值；所述指定定时器，用于在超时时重置所述共享频率对应的LBT失败次数；所述至少一个共享频率对应的指定定时器相同或者不同；所述至少一个共享频率对应的指定次数阈值相同或者不同。
作为本公开实施例的一种可能的实现方式，所述第一处理单元1010具体用于，在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与所述第一目的地址标识进行侧行链路通信触发持续LBT失败；其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，收发单元还用于，从网络设备接收第三RRC消息，其中，所述第三RRC消息携带：至少一个目的地址标识对应的指定定时器，以及至少一个目的地址标识对应的指定次数阈值；所述指定定时器，用于在超时时重置所述目的地址标识对应的LBT失败次数；或者，从至少一个目的地址标识对应的目的终端设备接收第一sidelink RRC消息，其中，所述第一sidelink RRC消息携带：所述目的地址标识对应的指定定时器，以及所述目的地址标识对应的指定次数阈值；其中，所述至少一个目的地址标识对应的指定定时器相同或者不同；所述至少一个目的地址标识对应的指定次数阈值相同或者不同。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在触发所述持续LBT失败时，向网络设备上报第一失败指示。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在触发所述持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择所述备用侧行链路发送资源。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在第一共享频率的侧行链路发送资源上触发持续LBT失败时，向网络设备上报携带所述第一共享频率的第二失败指示；其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在第一共享频率的侧行链路发送资源上触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为所述备用侧行链路发送资源；其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报携带所述第一目的地址标识的第三失败指示；其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，第二处理单元1020具体用于，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为所述备用侧行链路发送资源；其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，收发单元还用于，从网络设备接收第四RRC消息，其 中，所述第四RRC消息携带所述候选侧行链路发送资源；或者，从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，所述第二sidelink RRC消息携带所述候选侧行链路发送资源消息。
作为本公开实施例的一种可能的实现方式，收发单元还用于，在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向所述第一目的地址标识对应的目的终端设备发送第四失败指示；其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
作为本公开实施例的一种可能的实现方式，所述第四失败指示，用于指示所述目的终端设备停止在发生所述持续LBT失败的共享频率的侧行链路发送资源上接收所述终端设备的侧行链路消息；或者，所述第四失败指示，用于指示在备用侧行链路发送资源存在时，在所述备用侧行链路发送资源上接收所述侧行链路消息；
作为本公开实施例的一种可能的实现方式，所述第四失败指示还携带：第二共享频率；其中，与所述第一目的地址标识进行侧行链路通信使用的至少一个共享频率的侧行链路发送资源中，所述第二共享频率的侧行链路发送资源触发所述持续LBT失败。
作为本公开实施例的一种可能的实现方式，收发单元还用于，向所述第一目的地址标识对应的目的终端设备发送第三sidelink RRC消息，其中，所述第三sidelink RRC消息携带所述第四失败指示；或者，向所述第一目的地址标识对应的目的终端设备发送sidelink MAC CE消息，其中，所述sidelink MAC CE消息携带所述第四失败指示。
本公开实施例的侧行链路sidelink通信装置，应用于终端设备，通过确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；在触发持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
与上述图7至图8实施例提供的侧行链路sidelink通信方法相对应，本公开还提供一种侧行链路sidelink通信装置，由于本公开实施例提供侧行链路sidelink通信装置与上述图7至图8实施例提供的侧行链路sidelink通信方法相对应，因此在侧行链路sidelink通信方法的实施方式也适用于本公开实施例提供的侧行链路sidelink通信装置，在本公开实施例中不再详细描述。
图11为本公开实施例所提供的另一种侧行链路sidelink通信装置的结构示意图。该侧行链路sidelink通信装置应用于网络设备。
如图11所示，该侧行链路sidelink通信装置1100包括：收发单元1110。
其中，收发单元1110，用于向终端设备发送第一消息；其中，所述第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。
作为本公开实施例的一种可能实现方式，所述指定定时器的数量为至少一个，与至少一个共享频率对应；所述指定次数阈值的数量为至少一个，与至少一个共享频率对应；或者，所述指定定时器的数量为至少一个，与至少一个目的地址标识对应；所述指定次数阈值的数量为至少一个，与至少一个目的地址标识对应。
作为本公开实施例的一种可能实现方式，收发单元1110还用于，接收所述终端设备上报的失败指示，所述失败指示用于指示触发持续LBT失败。
作为本公开实施例的一种可能实现方式，所述方法还包括：根据所述失败指示，向所述终端设备调度备用侧行链路发送资源；其中，所述备用侧行链路发送资源为，通过共享频率的侧行链路发送资源，或者，通过非共享频率的侧行链路发送资源。
作为本公开实施例的一种可能实现方式，所述失败指示包括：触发持续LBT失败的共享频率的侧行链路发送资源的第一共享频率；或者，所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
本公开实施例的侧行链路sidelink通信装置，应用于网络设备，通过向终端设备发送第一消息，第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败，使得终端设备在LBT失败时，能够及时进行数据发送，避免数据丢失，增加通信可靠性。
与上述图9实施例提供的侧行链路sidelink通信方法相对应，本公开还提供一种侧行链路sidelink通信装置，由于本公开实施例提供侧行链路sidelink通信装置与上述图9实施例提供的侧行链路sidelink通信方法相对应，因此在侧行链路sidelink通信方法的实施方式也适用于本公开实施例提供的侧行链路sidelink通信装置，在本公开实施例中不再详细描述。
图12为本公开实施例所提供的另一种侧行链路sidelink通信装置的结构示意图。该侧行链路sidelink通信装置应用于目的终端设备。
如图12所示，该侧行链路sidelink通信装置1200包括：收发单元1210。
其中，收发单元1210，用于接收所述终端设备发送的失败指示，其中，所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
作为本公开实施例的一种可能实现方式，根据所述失败指示，停止在发生所述持续LBT失败的共享频率的侧行链路发送资源上接收所述终端设备的侧行链路消息；或者，根据所述失败指示，在备用侧行链路发送资源存在时，在所述备用侧行链路发送资源上接收所述终端设备的侧行链路消息。
作为本公开实施例的一种可能实现方式，收发单元1210还用于，接收所述终端设备的sidelink RRC消息，其中，所述sidelink RRC消息携带所述失败指示；或者，接收所述终端设备发送的sidelink MAC CE消息，其中，所述sidelink MAC CE消息携带所述失败指示。
为了实现上述实施例，本公开还提出一种侧行链路sidelink通信装置，该装置包括处理器和存储器，存储器中存储有计算机程序，处理器执行存储器中存储的计算机程序，以使所述装置执行图2至图6实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开还提出另一种侧行链路sidelink通信装置，该装置包括处理器和存储器，存储器中存储有计算机程序，处理器执行存储器中存储的计算机程序，以使所述装置执行图7至图8实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开还提出另一种侧行链路sidelink通信装置，该装置包括处理器和存储器，存储器中存储有计算机程序，处理器执行存储器中存储的计算机程序，以使所述装置执行图9实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开还提出一种侧行链路sidelink通信方法，包括：处理器和接口电路；接口电路，用于接收代码指令并传输至所述处理器；处理器，用于运行代码指令以执行图2至图6实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开还提出另一种侧行链路sidelink通信方法，包括：处理器和接口电路；接口电路，用于接收代码指令并传输至所述处理器；处理器，用于运行代码指令以执行图7至图8实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开还提出另一种侧行链路sidelink通信方法，包括：处理器和接口电路；接口电路，用于接收代码指令并传输至所述处理器；处理器，用于运行代码指令以执行图9实施例所述的侧行链路sidelink通信方法。
为了实现上述实施例，本公开提出一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使图2至图6所述实施例的侧行链路sidelink通信方法被实现。
为了实现上述实施例，本公开提出另一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使图7至图8所述实施例的侧行链路sidelink通信方法被实现。
为了实现上述实施例，本公开提出另一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使图9所述实施例的侧行链路sidelink通信方法被实现。
如图13所示，图13为本公开实施例所提供的一种网络设备的结构示意图。参照图13，网络设备1300包括处理组件1322，其进一步包括至少一个处理器，以及由存储器1332所代表的存储器资源，用于存储可由处理组件1322的执行的指令，例如应用程序。存储器1332中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1322被配置为执行指令，以执行上述方法前述应用在所述网络设备的任意方法，例如，如图7至图8实施例的方法。
网络设备1300还可以包括一个电源组件1326被配置为执行网络设备1300的电源管理，一个有线或无线网络接口1350被配置为将网络设备1300连接到网络，和一个输入输出(I/O)接口1358。网络设备1300可以操作基于存储在存储器1332的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
图14为本公开实施例所提供的一种终端设备的框图。例如，终端设备1400可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图14，终端设备1400可以包括以下至少一个组件：处理组件1402，存储器1404，电源组件1406，多媒体组件1408，音频组件1410，输入/输出(I/O)的接口1412，传感器组件1414，以及通信组件1416。
处理组件1402通常控制终端设备1400的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1402可以包括至少一个处理器1420来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1402可以包括至少一个模块，便于处理组件1402和其他组件之间的交互。例如，处理组件1402可以包括多媒体模块，以方便多媒体组件1408和处理组件1402之间的交互。
存储器1404被配置为存储各种类型的数据以支持在终端设备1400的操作。这些数据的示例包括用于在终端设备1400上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1404可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1406为终端设备1400的各种组件提供电力。电源组件1406可以包括电源管理系统，至少一个电源，及其他与为终端设备1400生成、管理和分配电力相关联的组件。
多媒体组件1408包括在所述终端设备1400和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括至少一个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的唤醒时间和压力。在一些实施例中，多媒体组件1408包括一个前置摄像头和/或后置摄像头。当终端设备1400处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1410被配置为输出和/或输入音频信号。例如，音频组件1410包括一个麦克风(MIC)，当终端设备1400处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1804或经由通信组件1416发送。在一些实施例中，音频组件1410还包括一个扬声器，用于输出音频信号。
I/O接口1412为处理组件1402和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1414包括至少一个传感器，用于为终端设备1400提供各个方面的状态评估。例如，传感器组件1414可以检测到终端设备1400的打开/关闭状态，组件的相对定位，例如所述组件为终端设备1400的显示器和小键盘，传感器组件1414还可以检测终端设备1400或终端设备1400一个组件的位置改变，用户与终端设备1400接触的存在或不存在，终端设备1400方位或加速/减速和终端设备1400的温度变化。传感器组件1414可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1414还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1414还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1416被配置为便于终端设备1400和其他设备之间有线或无线方式的通信。终端设备1400可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1416经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1416还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端设备1400可以被至少一个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述图2至图5所示的方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1404，上述指令可由终端设备1400的处理器1420执行以完成上述图2至图6所示的方法，和/或，完成上述图9所示的方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其 范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
为了实现上述实施例，本公开实施例还提供了一种通信装置，通信装置可以是网络设备，也可以是用户设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持用户设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述任一方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
其中，通信装置可以包括一个或多个处理器。处理器可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，用户设备、用户设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置中还可以包括一个或多个存储器，其上可以存有计算机程序，处理器执行所述计算机程序，以使得通信装置执行上述方法实施例中描述的方法。可选的，所述存储器中还可以存储有数据。通信装置和存储器可以单独设置，也可以集成在一起。
可选的，通信装置还可以包括收发器、天线。收发器可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置中还可以包括一个或多个接口电路。接口电路用于接收代码指令并传输至处理器。处理器运行所述代码指令以使通信装置执行上述任一方法实施例中描述的方法。
在一种实现方式中，处理器中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器可以存有计算机程序，计算机程序在处理器上运行，可使得通信装置执行上述任一方法实施例中描述的方法。计算机程序可能固化在处理器中，该种情况下，处理器可能由硬件实现。
在一种实现方式中，通信装置可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在IC(Integrated Circuit，集成电路)、模拟IC、射频集成电路RFIC、混合信号IC、ASIC(Application Specific Integrated Circuit，专用集成电路)、PCB(Printed Circuit Board，印刷电路板)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如CMOS(Complementary Metal Oxide Semiconductor，互补金属氧化物半导体)、NMOS(nMetal-Oxide-Semiconductor，N型金属氧化物半导体)、PMOS(Positive Channel Metal Oxide Semiconductor，P型金属氧化物半导体)、BJT(Bipolar Junction Transistor，双极结型晶体管)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者用户设备，但本公开中描述的通信装置的范围并不限于此。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、用户设备、智能用户设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，芯片可以包括处理器和接口。其中，处理器的数量可以是一个或多个，接口的数量可以是多个。
可选的，芯片还包括存储器，存储器用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述图2至图6实施例 的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述图7至图8实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述图9实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、DSL(Digital Subscriber Line，数字用户线))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度DVD(Digital Video Disc，数字视频光盘))、或者半导体介质(例如，SSD(Solid State Disk，固态硬盘))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种侧行链路sidelink通信方法，其特征在于，应用于终端设备，所述方法包括：
    确定在共享频率的侧行链路发送资源上是否触发持续LBT失败；
    在触发所述持续LBT失败时，向网络设备上报失败指示或者确定备用侧行链路发送资源，用于发送侧行链路消息。
  2. 根据权利要求1所述的方法，其特征在于，所述确定在共享频率的侧行链路发送资源上是否触发持续LBT失败，包括：
    在共享频率的侧行链路发送资源上的LBT失败次数大于或者等于指定次数阈值时，确定在共享频率的侧行链路发送资源上触发持续LBT失败。
  3. 根据权利要求2所述的方法，其特征在于，确定共享频率的侧行链路发送资源上的LBT失败次数，包括：
    在指定定时器超时时，将当前的所述LBT失败次数重置为零值，并停止所述指定定时器；
    在共享频率的侧行链路发送资源上发生LBT失败时，启动或者重启指定定时器，对当前的所述LBT失败次数进行加1处理。
  4. 根据权利要求2所述的方法，其特征在于，在确定在共享频率的侧行链路发送资源上是否触发持续LBT失败之前，还包括：
    从网络设备接收第一RRC消息，其中，所述第一RRC消息携带所述指定定时器和所述指定次数阈值；所述指定定时器，用于在超时时重置所述LBT失败次数。
  5. 根据权利要求1所述的方法，其特征在于，所述确定在共享频率的侧行链路发送资源上是否触发持续LBT失败，包括：
    在至少一个共享频率中存在第一共享频率时，确定在所述第一共享频率的侧行链路发送资源上触发持续LBT失败；
    其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
  6. 根据权利要求5所述的方法，其特征在于，在确定在共享频率的侧行链路发送资源上是否触发持续LBT失败之前，还包括：
    从网络设备接收第二RRC消息，其中，所述第二RRC消息携带：至少一个共享频率对应的指定定时器，以及至少一个共享频率对应的指定次数阈值；所述指定定时器，用于在超时时重置所述共享频率对应的LBT失败次数；
    所述至少一个共享频率对应的指定定时器相同或者不同；所述至少一个共享频率对应的指定次数阈值相同或者不同。
  7. 根据权利要求1所述的方法，其特征在于，所述确定在共享频率的侧行链路发送资源上是否触发持续LBT失败，包括：
    在至少一个共享频率的侧行链路发送资源上进行侧行链路通信的至少一个目的地址标识中存在第一目的地址标识时，确定与所述第一目的地址标识进行侧行链路通信触发持续LBT失败；
    其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
  8. 根据权利要求7所述的方法，其特征在于，在确定在共享频率的侧行链路发送资源上是否触发持续LBT失败之前，还包括：
    从网络设备接收第三RRC消息，其中，所述第三RRC消息携带：至少一个目的地址标识对应的指定定时器，以及至少一个目的地址标识对应的指定次数阈值；所述指定定时器，用于在超时时重置所述目的地址标识对应的LBT失败次数；
    或者，
    从至少一个目的地址标识对应的目的终端设备接收第一sidelink RRC消息，其中，所述第一sidelinkRRC消息携带：所述目的地址标识对应的指定定时器，以及所述目的地址标识对应的指定次数阈值；
    其中，所述至少一个目的地址标识对应的指定定时器相同或者不同；所述至少一个目的地址标识对应的指定次数阈值相同或者不同。
  9. 根据权利要求1或2所述的方法，其特征在于，所述在触发所述持续LBT失败时，向网络设备上报失败指示，包括：
    在触发所述持续LBT失败时，向网络设备上报第一失败指示。
  10. 根据权利要求1或2所述的方法，其特征在于，所述在触发所述持续LBT失败时，确定备用侧行链路发送资源，用于发送侧行链路消息，包括：
    在触发所述持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择所述备用侧行链路发送资源。
  11. 根据权利要求1或5所述的方法，其特征在于，所述在触发所述持续LBT失败时，向网络设备上报失败指示，包括：
    在第一共享频率的侧行链路发送资源上触发持续LBT失败时，向网络设备上报携带所述第一共享频率的第二失败指示；
    其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
  12. 根据权利要求1或5所述的方法，其特征在于，所述在触发所述持续LBT失败时，确定备用侧行链路发送资源，用于发送侧行链路消息，包括：
    在第一共享频率的侧行链路发送资源上触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为所述备用侧行链路发送资源；
    其中，在所述第一共享频率的侧行链路发送资源上，所述第一共享频率对应的LBT失败次数大于或者等于所述第一共享频率对应的指定次数阈值。
  13. 根据权利要求1或7所述的方法，其特征在于，所述在触发所述持续LBT失败时，向网络设备上报失败指示，包括：
    在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向网络设备上报携带所述第一目的地址标识的第三失败指示；
    其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
  14. 根据权利要求1或7所述的方法，其特征在于，所述在触发所述持续LBT失败时，确定备用侧行链路发送资源，用于发送侧行链路消息，包括：
    在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，从配置的至少一个候选侧行链路发送资源中选择共享频率的候选侧行链路发送资源或者非共享频率的候选侧行链路发送资源，作为所述备用侧行链路发送资源；
    其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
  15. 根据权利要求10或12或14所述的方法，其特征在于，所述方法还包括：
    从网络设备接收第四RRC消息，其中，所述第四RRC消息携带所述候选侧行链路发送资源；
    或者，
    从至少一个目的地址标识对应的目的终端设备接收第二sidelink RRC消息，其中，所述第二sidelink RRC消息携带所述候选侧行链路发送资源消息。
  16. 根据权利要求1或7所述的方法，其特征在于，所述方法还包括：
    在与第一目的地址标识进行侧行链路通信触发持续LBT失败时，向所述第一目的地址标识对应的目的终端设备发送第四失败指示；
    其中，所述用于与第一目的地址标识进行侧行链路通信的共享频率的侧行链路发送资源上，所述第一目的地址标识对应的LBT失败次数大于或者等于所述第一目的地址标识对应的指定次数阈值。
  17. 根据权利要求16所述的方法，其特征在于，
    所述第四失败指示，用于指示所述目的终端设备停止在发生所述持续LBT失败的共享频率的侧行链路发送资源上接收所述终端设备的侧行链路消息；
    或者，
    所述第四失败指示，用于指示在备用侧行链路发送资源存在时，在所述备用侧行链路发送资源上接收所述侧行链路消息。
  18. 根据权利要求16所述的方法，其特征在于，所述第四失败指示还携带：第二共享频率；
    其中，与所述第一目的地址标识进行侧行链路通信使用的至少一个共享频率的侧行链路发送资源中，所述第二共享频率的侧行链路发送资源触发所述持续LBT失败。
  19. 根据权利要求16所述的方法，其特征在于，所述向所述第一目的地址标识对应的目的终端设 备发送第四失败指示，包括：
    向所述第一目的地址标识对应的目的终端设备发送第三sidelink RRC消息，其中，所述第三sidelink RRC消息携带所述第四失败指示；
    或者，
    向所述第一目的地址标识对应的目的终端设备发送sidelink MAC CE消息，其中，所述sidelink MAC CE消息携带所述第四失败指示。
  20. 一种侧行链路通信方法，其特征在于，应用于网络设备，所述方法包括：
    向终端设备发送第一消息；
    其中，所述第一消息携带指定定时器和指定次数阈值，用于确定共享频率的侧行链路发送资源上是否触发持续LBT失败。
  21. 根据权利要求20所述的方法，其特征在于，所述指定定时器的数量为至少一个，与至少一个共享频率对应；所述指定次数阈值的数量为至少一个，与至少一个共享频率对应；
    或者，
    所述指定定时器的数量为至少一个，与至少一个目的地址标识对应；所述指定次数阈值的数量为至少一个，与至少一个目的地址标识对应。
  22. 根据权利要求20或21所述的方法，其特征在于，所述方法还包括：
    接收所述终端设备上报的失败指示，所述失败指示用于指示触发持续LBT失败。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    根据所述失败指示，向所述终端设备调度备用侧行链路发送资源；
    其中，所述备用侧行链路发送资源为，通过共享频率的侧行链路发送资源，或者，通过非共享频率的侧行链路发送资源。
  24. 根据权利要求22所述的方法，其特征在于，
    所述失败指示包括：触发持续LBT失败的共享频率的侧行链路发送资源的第一共享频率；
    或者，
    所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
  25. 一种侧行链路sidelink通信方法，其特征在于，应用于目的终端设备，所述方法包括：
    接收终端设备发送的失败指示，其中，所述失败指示包括：第一目的地址标识，其中，与所述第一目的地址标识进行侧行链路通信触发持续LBT失败。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    根据所述失败指示，停止在发生所述持续LBT失败的共享频率的侧行链路发送资源上接收所述终端设备的侧行链路消息；
    或者，
    根据所述失败指示，在备用侧行链路发送资源存在时，在所述备用侧行链路发送资源上接收所述终端设备的侧行链路消息。
  27. 根据权利要求25所述的方法，其特征在于，所述接收所述终端设备发送的失败指示，包括：
    接收所述终端设备的sidelink RRC消息，其中，所述sidelink RRC消息携带所述失败指示；
    或者，
    接收所述终端设备发送的sidelink MAC CE消息，其中，所述sidelink MAC CE消息携带所述失败指示。
  28. 一种侧行链路sidelink通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至19中任一项所述的方法。
  29. 一种侧行链路sidelink通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求20至24中任一项所述的方法。
  30. 一种侧行链路sidelink通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求25至27中任一项所述的方法。
PCT/CN2022/083493 2022-03-28 2022-03-28 侧行链路sidelink通信方法及装置 WO2023184116A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/083493 WO2023184116A1 (zh) 2022-03-28 2022-03-28 侧行链路sidelink通信方法及装置
CN202280000767.7A CN114938710A (zh) 2022-03-28 2022-03-28 侧行链路sidelink通信方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/083493 WO2023184116A1 (zh) 2022-03-28 2022-03-28 侧行链路sidelink通信方法及装置

Publications (1)

Publication Number Publication Date
WO2023184116A1 true WO2023184116A1 (zh) 2023-10-05

Family

ID=82869297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083493 WO2023184116A1 (zh) 2022-03-28 2022-03-28 侧行链路sidelink通信方法及装置

Country Status (2)

Country Link
CN (1) CN114938710A (zh)
WO (1) WO2023184116A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023202316A1 (zh) * 2022-04-22 2023-10-26 大唐移动通信设备有限公司 一种一致性lbt失败的处理方法、终端及网络设备
CN117835424A (zh) * 2022-09-29 2024-04-05 华为技术有限公司 一种通信方法及装置
WO2024087026A1 (zh) * 2022-10-25 2024-05-02 北京小米移动软件有限公司 一种侧行链路连续先听后说失败的处理方法及装置
WO2024087123A1 (zh) * 2022-10-27 2024-05-02 北京小米移动软件有限公司 一种侧行链路连续先听后说失败的上报方法及装置
WO2024092824A1 (zh) * 2022-11-04 2024-05-10 北京小米移动软件有限公司 一种失败报告的上报方法及其装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112753275A (zh) * 2018-09-26 2021-05-04 康维达无线有限责任公司 Nr-u lbt mac过程
CN113727368A (zh) * 2020-05-25 2021-11-30 华为技术有限公司 一种通信方法及装置
US20220022252A1 (en) * 2019-03-27 2022-01-20 Apple Inc. Uplink listen before talk failure handling
WO2022104542A1 (zh) * 2020-11-17 2022-05-27 Oppo广东移动通信有限公司 无线通信方法和通信装置
WO2022165851A1 (en) * 2021-02-08 2022-08-11 Lenovo (Beijing) Limited Method for sidelink communication and terminal device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112753275A (zh) * 2018-09-26 2021-05-04 康维达无线有限责任公司 Nr-u lbt mac过程
US20220022252A1 (en) * 2019-03-27 2022-01-20 Apple Inc. Uplink listen before talk failure handling
CN113727368A (zh) * 2020-05-25 2021-11-30 华为技术有限公司 一种通信方法及装置
WO2022104542A1 (zh) * 2020-11-17 2022-05-27 Oppo广东移动通信有限公司 无线通信方法和通信装置
WO2022165851A1 (en) * 2021-02-08 2022-08-11 Lenovo (Beijing) Limited Method for sidelink communication and terminal device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO, LG ELECTRONICS: "New WID on NR sidelink evolution", 3GPP TSG RAN MEETING #94E, RP-213678, 16 December 2021 (2021-12-16), XP052088710 *

Also Published As

Publication number Publication date
CN114938710A (zh) 2022-08-23

Similar Documents

Publication Publication Date Title
WO2023184116A1 (zh) 侧行链路sidelink通信方法及装置
WO2023201760A1 (zh) PScell添加或改变的成功报告的记录方法、装置
WO2023206182A1 (zh) 成功PScell添加或更换报告的位置信息记录方法、装置
WO2023004652A1 (zh) 节能配置方法及其装置
WO2023206031A1 (zh) 发送通知消息的方法及装置
WO2023151044A1 (zh) 路径切换方法及装置
WO2023173381A1 (zh) 侧行链路通信方法及装置
WO2024065127A1 (zh) 控制中继设备信息发送的方法及其装置
WO2023000230A1 (zh) 辅助配置方法及其装置
WO2023201759A1 (zh) 成功PScell添加或更换报告的上报方法、装置
WO2023206032A2 (zh) 直连sidelink非连续接收DRX的控制方法及装置
WO2023004554A1 (zh) 一种业务控制方法、装置、用户设备、基站及存储介质
WO2023220900A1 (zh) Mcg失败相关信息上报方法、装置
WO2023206181A1 (zh) 一种小区管理方法/装置/设备及存储介质
WO2023206570A1 (zh) 一种配置管理方法、装置、设备及存储介质
WO2023035116A1 (zh) 一种无线资源控制rrc状态切换方法、装置、用户设备、基站及存储介质
WO2023197331A1 (zh) 数据传输方法/装置/设备及存储介质
WO2022266862A1 (zh) 联合信道估计方法及其装置
WO2023206297A1 (zh) 一种小区激活方法/装置/设备及存储介质
CN114586401B (zh) 一种测量放松方法、设备、存储介质及装置
WO2023178568A1 (zh) 一种测量方法及设备/存储介质/装置
WO2023225828A1 (zh) 支持跨ssb的多prach传输配置方法、装置
WO2023178567A1 (zh) 一种上报方法/装置/设备及存储介质
WO2023184260A1 (zh) 一种信号传输方法/装置/设备及存储介质
WO2023010432A1 (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: 22933973

Country of ref document: EP

Kind code of ref document: A1