WO2024087123A1 - Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale - Google Patents

Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale Download PDF

Info

Publication number
WO2024087123A1
WO2024087123A1 PCT/CN2022/128083 CN2022128083W WO2024087123A1 WO 2024087123 A1 WO2024087123 A1 WO 2024087123A1 CN 2022128083 W CN2022128083 W CN 2022128083W WO 2024087123 A1 WO2024087123 A1 WO 2024087123A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
resource pool
sidelink
continuous
lbt failure
Prior art date
Application number
PCT/CN2022/128083
Other languages
English (en)
Chinese (zh)
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 CN202280003923.5A priority Critical patent/CN118266198A/zh
Priority to PCT/CN2022/128083 priority patent/WO2024087123A1/fr
Publication of WO2024087123A1 publication Critical patent/WO2024087123A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems

Definitions

  • the present application relates to the field of communication technology, and in particular to a method and device for reporting continuous listen-before-speak failure of a side link.
  • the sidelink (SL) communication mode is introduced.
  • the network dynamic scheduling mode is that the network device dynamically allocates transmission resources on the sidelink to the terminal device based on the cached data reported by the terminal device.
  • the resource autonomous selection mode is that the terminal device randomly selects transmission resources from the network broadcast or pre-configured resource pool.
  • a terminal device when a terminal device operates in a network dynamic scheduling mode, or operates in a resource autonomous selection mode and is in a Radio Resource Control (RRC) connection state, if a continuous Listen Before Talk (LBT) failure is triggered, a technical problem may arise in which the terminal device is unsure how to report the continuous LBT failure status of the sidelink.
  • RRC Radio Resource Control
  • the present application proposes a method and device for reporting the failure of continuous listen-before-talk in the side link, which solves the technical problem that for side link communication, when the terminal device works in the network dynamic scheduling mode, or the terminal device works in the resource autonomous selection mode and is in the RRC connected state, if the continuous LBT failure of the side link is triggered, the terminal device is not sure how to report the continuous LBT failure status of the side link.
  • the first aspect embodiment of the present application provides a method for reporting a side link continuous listen-before-talk failure, which is applied to a terminal device, including: reporting a resource pool identifier of a resource pool that triggers a side link continuous LBT failure through a first signaling.
  • the first signaling includes: sidelink terminal information (sidelink UE information, SUI), or terminal assistance information (UE assistance information, UAI), or media access layer control element (MAC CE).
  • sidelink UE information sidelink UE information, SUI
  • terminal assistance information UE assistance information, UAI
  • MAC CE media access layer control element
  • the resource pool identifier of the resource pool that triggers the side link continuous LBT failure reported through the first signaling includes: when the terminal device detects that at least one resource pool has triggered the side link continuous LBT failure and the side link continuous LBT failure state is not canceled, the resource pool identifier of the at least one resource pool is reported through SUI or UAI or side link continuous LBT failure MAC CE.
  • the resource pool identifier of the at least one resource pool is reported through the SUI or UAI, including: in a non-carrier aggregation scenario, reporting a list containing the resource pool identifier through the SUI or UAI; or, reporting a list containing the resource pool identifier and a resource block set (Resource block set, RB set) identifier through the SUI or UAI, the RB set identifier being the identifier of the RB set associated with the resource pool corresponding to the resource pool identifier.
  • the resource pool identifier of the at least one resource pool is reported through the sidelink continuous LBT failure MAC CE, including: in a non-carrier aggregation scenario, the terminal device reports a first MAC CE information, and the first MAC CE information includes a first value corresponding to the first resource pool identifier; or, the first MAC CE information includes a first RB set identifier and a first value corresponding to the first resource pool identifier, and the first RB set identifier is an identifier of the RB set associated with the resource pool corresponding to the first resource pool identifier; wherein the first value is used to indicate whether the resource pool corresponding to the first resource pool identifier has triggered a sidelink continuous LBT failure.
  • the resource pool identifier of the at least one resource pool is reported through the SUI or UAI, including: in a carrier aggregation scenario, reporting a list including the resource pool identifier and a first cell identifier through the SUI or UAI, the first cell identifier being the identifier of the service cell associated with the resource pool corresponding to the resource pool identifier; or, reporting a list including the resource pool identifier, a second RB set identifier and a second cell identifier through the SUI or UAI, the second RB set identifier being the identifier of the RB set associated with the resource pool corresponding to the resource pool identifier, and the second cell identifier being the cell identifier of the service cell associated with the RB set corresponding to the second RB set identifier.
  • the resource pool identifier of the at least one resource pool is reported through the sidelink continuous LBT failure MAC CE, including: in a carrier aggregation scenario, the terminal device reports a second MAC CE information, the second MAC CE information includes a third cell identifier and a second value corresponding to the second resource pool identifier, the third cell identifier is an identifier of a service cell associated with the resource pool corresponding to the second resource pool identifier; or, the second MAC CE information includes a fourth cell identifier, a third RB set identifier and a second value corresponding to the second resource pool identifier, the third RB set identifier is an identifier of an RB set associated with the resource pool corresponding to the second resource pool identifier, and the fourth cell identifier is a cell identifier of a service cell associated
  • a second aspect of the present application provides a method for reporting a continuous listen-before-talk failure in a side link, which is applied to a terminal device, including: reporting the RB set identifier of the RB set that triggers the continuous LBT failure in the side link through a second signaling.
  • the second signaling includes: SUI, UAI, or MAC CE.
  • the RB set identifier of the RB set that triggers the continuous LBT failure of the side link reported through the second signaling includes: when the terminal device detects that at least one RB set has triggered the continuous LBT failure of the side link and the continuous LBT failure state of the side link is not canceled, the RB set identifier of the at least one RB set is reported through SUI or UAI or side link continuous LBT failure MAC CE.
  • the RB set identifier of the at least one RB set is reported through the SUI or UAI, including: in a non-carrier aggregation scenario, a list containing the RB set identifier is reported through the SUI or UAI; or, a list containing the RB set identifier and a resource pool identifier is reported through the SUI or UAI, and the resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to the RB set identifier.
  • the terminal device when the terminal device detects that at least one RB set has triggered a sidelink continuous LBT failure and the sidelink continuous LBT failure state is not canceled, the RB set identifier of the at least one RB set is reported through the sidelink continuous LBT failure MAC CE, including: in a non-carrier aggregation scenario, the terminal device reports a third MAC CE information, and the third MAC CE information includes a third value corresponding to a fourth RB set identifier; or, the third MAC CE information includes a third resource pool identifier and a third value corresponding to a fourth RB set identifier, and the resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the RB set identifier; wherein the third value is used to indicate whether the RB set corresponding to the fourth RB set identifier has triggered a sidelink continuous LBT failure.
  • the RB set identifier of the at least one RB set is reported through the SUI or UAI, including: in a carrier aggregation scenario, reporting a list including the RB set identifier and the fifth cell identifier through the SUI or UAI, the fifth cell identifier is the identifier of the service cell associated with the RB set corresponding to the RB set identifier; or, reporting a list including the RB set identifier, the fourth resource pool identifier and the sixth cell identifier through the SUI or UAI, the fourth resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to the RB set identifier, and the sixth cell identifier is the identifier on the service cell associated with the resource pool corresponding to the fourth resource pool identifier.
  • the RB set identifier of the at least one RB set is reported through the side link continuous LBT failure MAC CE, including: in a carrier aggregation scenario, the terminal device reports a fourth MAC CE information, the fourth MAC CE information includes a seventh cell identifier and a fourth value corresponding to a fifth RB set identifier, the seventh cell identifier is an identifier of a service cell associated with the RB set corresponding to the fifth RB set identifier; or, the fourth MAC CE information includes an eighth cell identifier, a fifth resource pool identifier and a fourth value corresponding to the fifth RB set identifier, the fifth resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the fifth RB set identifier, and the eighth cell identifier is an
  • the third aspect of the present application provides a method for reporting a sidelink continuous listen-before-talk failure, which is applied to a terminal device, including: reporting the cell identifier of a service cell that triggers the sidelink continuous LBT failure through a third signaling.
  • the third signaling includes: SUI, or UAI, or MAC CE.
  • the cell identifier of the service cell that triggers the sidelink continuous LBT failure by reporting the third signaling includes: when the terminal device detects that at least one service cell has triggered the sidelink continuous LBT failure and the sidelink continuous LBT failure state is not canceled, the cell identifier of the at least one service cell is reported through SUI or UAI or sidelink continuous LBT failure MAC CE.
  • the cell identifier of the at least one service cell is reported through SUI or UAI, including: in a non-carrier aggregation scenario, parameter information is reported through SUI or UAI, and the parameter information is used to indicate whether the current service cell has triggered a sidelink continuous LBT failure.
  • the cell identifier of the at least one service cell is reported through the sidelink continuous LBT failure MAC CE, including: in a non-carrier aggregation scenario, the terminal device reports the fifth MAC CE information, and the fifth MAC CE information is used to indicate whether the current service cell has triggered a sidelink continuous LBT failure.
  • the cell identifier of the at least one service cell is reported through SUI or UAI, including: in a carrier aggregation scenario, a list containing the cell identifiers is reported through SUI or UAI.
  • the cell identifier of the at least one service cell is reported through the sidelink continuous LBT failure MAC CE, including: in a carrier aggregation scenario, the terminal device reports a sixth MAC CE information, the sixth MAC CE information includes a fifth numerical value corresponding to the cell identifier, wherein the fifth numerical value is used to indicate whether the service cell corresponding to the cell identifier has triggered a sidelink continuous LBT failure.
  • the fourth aspect of the present application provides a method for reporting a side link continuous listen-before-talk failure, which is applied to a terminal device.
  • the method includes: reporting the terminal identifier of the target terminal that triggers the side link continuous LBT failure through a fourth signaling.
  • the fourth signaling includes: SUI, or UAI, or MAC CE.
  • the terminal identification of the target terminal that triggers the side link continuous LBT failure by reporting the fourth signaling includes: when the terminal device detects that at least one target terminal has triggered the side link continuous LBT failure and has not canceled the side link continuous LBT failure state, the terminal identification of the at least one target terminal is reported through SUI or UAI or side link continuous LBT failure MAC CE.
  • the terminal identifier of the at least one target terminal is reported through SUI or UAI, including: reporting a list containing the terminal identifier through SUI or UAI.
  • the terminal identifier of the at least one target terminal is reported through the side link continuous LBT failure MAC CE, including: the terminal device reports the seventh MAC CE information, and the seventh MAC CE information includes the terminal identifier.
  • the fifth aspect embodiment of the present application provides a reporting device for continuous listen-before-talk failure of a side link, which is applied to a terminal device, and the device includes: a first sending module, configured to report the resource pool identifier of the resource pool that triggers the continuous LBT failure of the side link through a first signaling report.
  • the sixth aspect embodiment of the present application provides a reporting device for continuous listen-before-talk failure of a side link, characterized in that, applied to a terminal device, the device includes: a second sending module, configured to report the RB set identifier of the resource block set RB set that triggers the continuous LBT failure of the side link through a second signaling.
  • the seventh aspect embodiment of the present application provides a reporting device for continuous listen-before-talk failure of a side link, which is applied to a terminal device, including: a third sending module, configured to report the cell identifier of a service cell that triggers the continuous LBT failure of the side link through a third signaling.
  • the eighth aspect embodiment of the present application provides a reporting device for the failure of continuous listen-before-talk in a side link, which is applied to a terminal device, including: a fourth sending module, configured to report the terminal identifier of the target terminal that triggers the failure of continuous LBT in the side link through a fourth signaling.
  • the ninth aspect embodiment of the present application provides a communication device, which is applied to a terminal device, and the communication device includes: a transceiver; a memory; a processor, which is respectively connected to the transceiver and the memory, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method of the first aspect embodiment, the second aspect embodiment, the third aspect embodiment, or the fourth aspect embodiment of the present application.
  • the tenth aspect embodiment of the present application provides a computer storage medium, which is applied to a terminal device, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the method of the first aspect embodiment, the second aspect embodiment, the third aspect embodiment, or the fourth aspect embodiment of the present application can be implemented.
  • the embodiments of the present application provide a method and apparatus for reporting continuous listen-before-talk failure of a sidelink.
  • a terminal device operates in a network dynamic scheduling mode, or the terminal device operates in a resource autonomous selection mode and is in an RRC connected state
  • the resource pool identifier of the resource pool that triggers the continuous LBT failure of the sidelink, or the RB set identifier of the RB set that triggers the continuous LBT failure of the sidelink, or the cell identifier of the service cell that triggers the continuous LBT failure of the sidelink, or the terminal identifier of the target terminal that triggers the continuous LBT failure of the sidelink can be reported through signaling based on different detection granularities, so that the network device can determine the resource pool, RB set, service cell, target terminal, etc. where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or in other ways.
  • FIG1 is a schematic flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG2 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG3 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG4 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG5 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG6 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG7 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG8 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG9 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG10 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG11 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG12 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG13 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG14 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG15 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG16 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application
  • FIG17 is an example of a MAC CE reporting format according to an embodiment of the present application.
  • FIG18 is a block diagram of a reporting device for a sidelink continuous listen-before-speak failure according to an embodiment of the present application
  • FIG19 is a block diagram of a reporting device for a sidelink continuous listen-before-speak failure according to an embodiment of the present application
  • FIG20 is a block diagram of a reporting device for a sidelink continuous listen-before-speak failure according to an embodiment of the present application
  • FIG21 is a block diagram of a reporting device for a sidelink continuous listen-before-speak failure according to an embodiment of the present application
  • FIG22 is a schematic diagram of the structure of a communication device according to an embodiment of the present application.
  • FIG23 is a schematic diagram of the structure of a chip provided in an embodiment of the present application.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "at the time of” or "when” or "in response to determination".
  • the communication interface between the terminal equipment (User Equipment, UE) and the terminal equipment is called the PC-5 interface.
  • the link for transmitting data between the terminal equipment and the terminal equipment is called the sidelink.
  • the transmitting UE sends the sidelink control information (Sidelink Control Information, SCI) on the physical sidelink control channel (Physical Sidelink Control Channel, PSCCH) and sends the second stage SCI on the physical sidelink shared channel (Physical Sidelink Shared Channel, PSSCH), which carries the resource location of the transmitted data and the source and destination identifiers, etc.
  • SCI Sidelink Control Information
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink shared channel
  • the receiving UE performs HARQ-ACK feedback on PSSCH on the physical sidelink feedback channel (PSFCH).
  • LBT is a technology to avoid channel access conflicts. Different terminal devices compete for shared unlicensed (or license-free) spectrum resources through LBT operations. Communication protocol version 18 (release18, R18) supports sidelink communication using unlicensed spectrum. Terminal devices also need to perform LBT when sending sidelink data on unlicensed spectrum. The continuous LBT mechanism is also applicable to sidelink communication on unlicensed spectrum.
  • CA Carrier Aggregation
  • Carrier aggregation is a key technology in LTE-A.
  • CA Carrier Aggregation
  • CA technology can aggregate multiple carriers (Component Carrier, CC) together, effectively improving the uplink and downlink transmission rates.
  • LTE V2X already supports sidelink carrier aggregation technology, and R18 NR sidelink may also support sidelink carrier aggregation technology, that is, UE and UE communicate on multiple carriers, so that they can use the resources on multiple carriers to send and receive data at the same time, effectively improving the transmission rate of the sidelink.
  • the network dynamic scheduling mode (Mode 1, Mode 1); the other is the mode in which the terminal device autonomously selects resources from the network broadcast resource pool (Mode 2, Mode 2).
  • the specific mode to be used can be configured by the network device through RRC signaling.
  • the network dynamic scheduling mode is that the network device dynamically allocates transmission resources on the side link to the terminal device based on the cached data reported by the terminal device.
  • the resource autonomous selection mode is that the terminal device randomly selects transmission resources from the network broadcast or pre-configured resource pool.
  • the terminal device works in the network dynamic scheduling mode, or the terminal device works in the resource autonomous selection mode and is in the RRC connection state, if the continuous LBT failure is triggered, it will cause a technical problem that the terminal device is not sure how to report the continuous LBT failure status of the side link.
  • this embodiment proposes a method and device for reporting sidelink continuous listen-before-talk failure.
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state, if the sidelink continuous LBT failure is triggered, the terminal device is not sure how to report the sidelink continuous LBT failure status.
  • Fig. 1 shows a schematic flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. As shown in Fig. 1, it can be applied to a terminal device and can include the following steps.
  • Step 101 The terminal device reports the resource pool identifier of the resource pool that triggers the continuous LBT failure of the side link through the first signaling.
  • the first signaling may specifically include: SUI, or UAI, or MAC CE, etc.
  • SUI and UAI can be considered as RRC signaling
  • MAC CE can be considered as MAC signaling.
  • the detection granularity of the continuous LBT failure of the side link is the resource pool granularity.
  • the number of side link LBT failures is counted for the resource pool currently used by the terminal device, and the network device configures the corresponding maximum number of continuous LBT failures of the side link and the detection timer of the continuous LBT failure of the side link to the terminal device through the radio resource control (RRC) signaling, which is used to count the continuous LBT failure of the side link.
  • RRC radio resource control
  • the LBT failure on any resource in a resource pool is counted as the LBT failure of the resource pool. If the number of side link LBT failures of the resource pool is greater than or equal to the maximum number within the specified time, it can be considered that the resource pool has triggered the continuous LBT failure of the side link, and then the resource pool identifier of the resource pool that triggered the continuous LBT failure of the side link is reported to the network device through SUI or UAI or MAC CE of continuous LBT failure of the side link.
  • the reporting method for continuous listen-before-talk failure of the side link provided in this embodiment, when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connection state, the resource pool identifier of the resource pool that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the resource pool where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or other methods.
  • Fig. 2 is a flow chart showing a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. Based on the embodiment shown in Fig. 1, as shown in Fig. 2, it can be applied to a terminal device for execution, and the method may include the following steps.
  • Step 201 When the terminal device detects that at least one resource pool has triggered a side link continuous LBT failure and the side link continuous LBT failure state is not canceled, the terminal device reports the resource pool identifier of the at least one resource pool through SUI or UAI or side link continuous LBT failure MAC CE.
  • the side link continuous LBT failure state of the resource pool will be canceled.
  • the resource pool identifier of resource pool A (triggering a side link continuous LBT failure) has been reported through SUI or UAI or side link continuous LBT failure MAC CE, then when the resource pool identifier of resource pool A is reported successfully, the side link continuous LBT failure state of resource pool A will be canceled.
  • the terminal device when the terminal device detects that at least one resource pool has triggered a side link continuous LBT failure and has not canceled the side link continuous LBT failure state (such as not reported before), the terminal device reports the resource pool identifier of the at least one resource pool through SUI or UAI or side link continuous LBT failure MAC CE.
  • the specific reporting method needs to consider whether it is a carrier aggregation scenario.
  • the network device can configure one or more resource pools for the terminal device on each carrier-activated BWP; in the non-carrier aggregation scenario, there is no other carrier except the current carrier, and the network device can configure one or more resource pools for the terminal device on the current carrier-activated BWP.
  • step 201 may specifically include: in a non-carrier aggregation scenario, a list including resource pool identifiers (the resource pools corresponding to these resource pool identifiers triggered the sidelink continuous LBT failure and the sidelink continuous LBT failure status was not canceled) may be reported through SUI or UAI; or, a list including the resource pool identifier and the RB set identifier may be reported through SUI or UAI, wherein the RB set identifier is the identifier of the RB set associated with the resource pool corresponding to the resource pool identifier.
  • the detection granularity of the continuous LBT failure of the side link is the granularity of the resource pool
  • the granularity of the RB set is larger than the granularity of the resource pool, that is, one RB set can contain multiple resource pools
  • a list including the resource pool identifier (the resource pools corresponding to these resource pool identifiers triggered the continuous LBT failure of the side link and the continuous LBT failure status of the side link was not canceled) and the RB set identifier (the identifier of the RB set associated with the resource pool corresponding to the resource pool identifier) is reported through the SUI or UAI.
  • a resource pool can contain multiple RB sets
  • a list containing the resource pool identifier (the resource pools corresponding to these resource pool identifiers triggered the sidelink continuous LBT failure and did not cancel the sidelink continuous LBT failure state) is reported through the SUI or UAI.
  • the SUI or UAI may include a list containing the resource pool identifiers of the resource pools that triggered the sidelink continuous LBT failure, such as the resource pool identifier SL-ResourcePoolID-r16, and the resource pool corresponding to the identifier triggered the sidelink continuous LBT failure.
  • step 201 may specifically include: in a non-carrier aggregation scenario, the terminal device reports a first MAC CE information, and the first MAC CE information may specifically include a first value corresponding to a first resource pool identifier; or, the first MAC CE information may specifically include a first RB set identifier and a first value corresponding to a first resource pool identifier, and the first RB set identifier may be an identifier of an RB set associated with the resource pool corresponding to the first resource pool identifier; wherein the first value is used to indicate whether the resource pool corresponding to the first resource pool identifier has triggered the sidelink continuous LBT failure.
  • the MAC CE information reported by the terminal device includes the value corresponding to the resource pool identifier.
  • the MAC CE of the continuous LBT failure of the side link indicates through an octet whether the resource pool associated with SL-ResourcePoolID i has triggered the continuous LBT failure of the side link, where 1 may indicate that the resource pool associated with SL-ResourcePoolID i has triggered the continuous LBT failure of the side link, and 0 may indicate that the resource pool associated with SL-ResourcePoolID i has not triggered the continuous LBT failure of the side link; or 0 may indicate that the resource pool associated with SL-ResourcePoolID i has triggered the continuous LBT failure of the side link, and 1 may indicate that the resource pool associated with SL-ResourcePoolID i has not triggered the continuous LBT failure of the side link.
  • This embodiment is not limited.
  • the MAC CE information reported by the terminal device includes the RB set identifier and the value corresponding to the resource pool identifier.
  • the RB set identifier is the identifier of the RB set associated with the resource pool corresponding to these resource pool identifiers.
  • the sidelink continuous LBT failure MAC CE indicates through an octet whether the resource pool associated with SL-ResourcePoolID m on the RB set corresponding to the RB set identifier triggers the sidelink continuous LBT failure, wherein 1 may indicate that the resource pool associated with SL-ResourcePoolID m on the RB set corresponding to the RB set identifier triggers the sidelink continuous LBT failure, and 0 may indicate that the resource pool associated with SL-ResourcePoolID m on the RB set corresponding to the RB set identifier does not trigger the sidelink continuous LBT failure; or 0 may indicate that the resource pool associated with SL-ResourcePoolID m on the RB set corresponding to the RB set identifier triggers the sidelink continuous LBT failure, and 1 may indicate that the resource pool associated with SL-ResourcePoolID m on the RB set corresponding to the RB set identifier triggers the sidelink continuous LBT failure,
  • the above is a reporting method in a non-carrier aggregation scenario.
  • the following describes in detail a reporting method in a carrier aggregation scenario.
  • step 201 may specifically include: in a carrier aggregation scenario, reporting through SUI or UAI a list including resource pool identifiers (the resource pools corresponding to these resource pool identifiers triggered the sidelink continuous LBT failure, and the sidelink continuous LBT failure state was not canceled) and a first cell identifier, the first cell identifier being an identifier of a service cell associated with the resource pool corresponding to the resource pool identifier; or, reporting through SUI or UAI a list including resource pool identifiers (the resource pools corresponding to these resource pool identifiers triggered the sidelink continuous LBT failure, and the sidelink continuous LBT failure state was not canceled), a second RB set identifier and a second cell identifier, the second RB set identifier being an identifier of an RB set associated with the resource pool corresponding to the resource pool identifier, and the second cell identifier being a cell identifier of a service cell associated with the RB set corresponding to the second RB
  • the detection granularity of the continuous LBT failure of the side link is the granularity of the resource pool
  • the granularity of the RB set is larger than the granularity of the resource pool, that is, one RB set can contain multiple resource pools
  • a list including the resource pool identifier (the resource pools corresponding to these resource pool identifiers triggered the continuous LBT failure of the side link and the continuous LBT failure state of the side link was not canceled)
  • the RB set identifier the identifier of the RB set associated with the resource pool corresponding to the resource pool identifier
  • the cell identifier the cell identifier of the service cell associated with the RB set corresponding to the RB set identifier
  • the SUI or UAI may include a list including the resource pool identifier and the cell identifier of the resource pool that triggered the sidelink continuous LBT failure.
  • the resource pool identifier may be SL-ResourcePoolID-r16, the resource pool corresponding to the identifier triggered the sidelink continuous LBT failure, and the cell identifier is the identifier of the service cell associated with the resource pool corresponding to the resource pool identifier.
  • step 201 may specifically include: in a carrier aggregation scenario, the terminal device reports a second MAC CE information, the second MAC CE information includes a third cell identifier and a second value corresponding to the second resource pool identifier, the third cell identifier is an identifier of a service cell associated with the resource pool corresponding to the second resource pool identifier; or, the second MAC CE information includes a fourth cell identifier, a third RB set identifier and a second value corresponding to the second resource pool identifier, the third RB set identifier is an identifier of an RB set associated with the resource pool corresponding to the second resource pool identifier, and the fourth cell identifier is a cell identifier of a service cell associated with the RB set corresponding to the third RB set identifier; wherein the second value is used to indicate whether the resource pool corresponding to the second resource
  • the MAC CE information reported by the terminal device includes the values corresponding to the cell identifier and the resource pool identifier.
  • the sidelink continuous LBT failure MAC CE indicates through an octet whether the resource pool associated with SL-ResourcePoolID m1 on the serving cell corresponding to SL-ServCellIndex i (cell identifier) has triggered the sidelink continuous LBT failure, wherein 1 may indicate that the resource pool associated with SL-ResourcePoolID m1 on the serving cell corresponding to SL-ServCellIndex i has triggered the sidelink continuous LBT failure, and 0 may indicate that the resource pool associated with SL-ResourcePoolID m1 on the serving cell corresponding to SL-ServCellIndex i has not triggered the sidelink continuous LBT failure; or 0 may indicate that the resource pool associated with SL-ResourcePoolID m1 on the serving cell corresponding to SL-ServCellIndex i has triggered the sidelink continuous LBT failure, and 1 may indicate that the resource pool associated with SL-
  • the MAC CE information reported by the terminal device includes the cell identifier, the RB set identifier, and the value corresponding to the resource pool identifier.
  • the RB set identifier is the identifier of the RB set associated with the resource pool corresponding to these resource pool identifiers
  • the cell identifier is the cell identifier of the service cell associated with the RB set corresponding to the RB set identifier.
  • the sidelink continuous LBT failure MAC CE indicates the RB set identifier of the RB set on the service cell corresponding to the cell identifier through an eight-bit group, and whether the resource pool associated with the SL-ResourcePoolIDm2 on the RB set corresponding to the RB set identifier has triggered the sidelink continuous LBT failure, wherein 1 may indicate that the resource pool associated with the SL-ResourcePoolID m2 on the RB set corresponding to the RB set identifier has triggered the sidelink continuous LBT failure, and 0 may indicate that the resource pool associated with the SL-ResourcePoolID m2 on the RB set corresponding to the RB set identifier has not triggered the sidelink continuous LBT failure; or 0 may indicate that the resource pool associated with the SL-ResourcePoolID m2 on the RB set corresponding to the RB set identifier has triggered the sidelink continuous LBT failure,
  • the reporting method for continuous listen-before-talk failure of the side link provided in this embodiment, when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connection state, the identifier of the resource pool that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the resource pool where the continuous LBT failure has occurred, and then can perform recovery processing by reconfiguring resources or other methods.
  • Fig. 6 shows a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. As shown in Fig. 6, it can be applied to a terminal device side, and the method can include the following steps.
  • Step 301 The terminal device reports the RB set identifier of the RB set that triggers the continuous LBT failure of the side link through the second signaling.
  • the second signaling includes: SUI, or UAI, or MAC CE.
  • SUI and UAI can be considered as RRC signaling
  • MAC CE can be considered as MAC signaling.
  • the detection granularity of the continuous LBT failure of the sidelink is the RB set granularity.
  • the number of sidelink LBT failures is counted for the RB set currently used by the terminal device, and the network device configures the corresponding maximum number of continuous LBT failures of the sidelink and the continuous LBT failure detection timer of the sidelink to the terminal device through RRC signaling, which is used to count the continuous LBT failures of the sidelink.
  • RRC signaling which is used to count the continuous LBT failures of the sidelink.
  • the LBT failure on any resource in an RB set is counted as the LBT failure of the RB set. If the number of sidelink LBT failures of the RB set is greater than or equal to the maximum number within the specified time, it can be considered that the RB set has triggered the continuous LBT failure of the sidelink, and then the RB set identifier of the RB set that triggered the continuous LBT failure of the sidelink is reported to the network device through SUI or UAI or MAC CE of continuous LBT failure of the sidelink.
  • the RB set identifier of the RB set that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the RB set where the continuous LBT failure has occurred, and then can perform recovery processing by reconfiguring resources or other methods.
  • Fig. 7 shows a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. Based on the embodiment shown in Fig. 6, as shown in Fig. 7, it can be applied to the terminal device side, and the method may include the following steps.
  • Step 401 When the terminal device detects that at least one RB set has triggered a side link continuous LBT failure and the side link continuous LBT failure state is not canceled, the RB set identifier of at least one RB set is reported through the SUI or UAI or the side link continuous LBT failure MAC CE.
  • the sidelink continuous LBT failure state of the RB set will be canceled.
  • the RB set identifier of RB set 1 (triggering a sidelink continuous LBT failure) has been reported through SUI or UAI or sidelink continuous LBT failure MAC CE, then when the RB set identifier of this RB set 1 is reported successfully, the sidelink continuous LBT failure state of this RB set 1 will be canceled.
  • the terminal device when the terminal device detects that at least one RB set has triggered a sidelink continuous LBT failure and the sidelink continuous LBT failure state is not canceled (such as it has not been reported before), the terminal device reports the RB set identifier of the at least one RB set through SUI or UAI or sidelink continuous LBT failure MAC CE.
  • the specific reporting method needs to consider whether it is a carrier aggregation scenario.
  • the network device can configure one or more RB sets for the terminal device on each carrier-activated BWP; in the non-carrier aggregation scenario, there is no other carrier except the current carrier, and the network device can configure one or more RB sets for the terminal device on the current carrier-activated BWP.
  • step 401 may specifically include: in a non-carrier aggregation scenario, reporting a list including RB set identifiers through SUI or UAI; or, reporting a list including RB set identifiers and resource pool identifiers through SUI or UAI, where the resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the RB set identifier.
  • the detection granularity of the continuous LBT failure of the side link is RB set
  • the granularity of the RB set is smaller than the granularity of the resource pool, that is, one resource pool can contain multiple RB sets
  • a list including the RB set identifier (the RB sets corresponding to these RB set identifiers triggered the continuous LBT failure of the side link and the continuous LBT failure state of the side link was not canceled) and the resource pool identifier (the identifier of the resource pool associated with the RB set corresponding to the RB set identifier) is reported through SUI or UAI.
  • the granularity of the RB set is larger than that of the resource pool, that is, one RB set may include multiple resource pools, then in a non-carrier aggregation scenario, a list including the RB set identifier (the RB sets corresponding to these RB set identifiers triggered the sidelink continuous LBT failure and the sidelink continuous LBT failure state was not cancelled) is reported through the SUI or UAI.
  • the SUI or UAI may include a list including the RB set identifiers of the RB sets that triggered the sidelink continuous LBT failure, such as the RB set identifier may be SL–RBsetID–r17, and the RB set corresponding to the RB set identifier triggered the sidelink continuous LBT failure.
  • step 401 may specifically include: in a non-carrier aggregation scenario, the terminal device reports a third MAC CE information, the third MAC CE information includes a third value corresponding to the fourth RB set identifier; or, the third MAC CE information includes a third resource pool identifier and a third value corresponding to the fourth RB set identifier, the third resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the fourth RB set identifier; wherein the third value is used to indicate whether the RB set corresponding to the fourth RB set identifier triggers the continuous LBT failure of the side link.
  • the MAC CE information reported by the terminal device includes the value corresponding to the RB set identifier.
  • the MAC CE of the continuous LBT failure of the side link indicates through an octet whether the RB set associated with SL-RBsetID i has triggered the continuous LBT failure of the side link, wherein 1 may indicate that the RB set associated with SL-RBsetID i has triggered the continuous LBT failure of the side link, and 0 may indicate that the RB set associated with SL-RBsetID i has not triggered the continuous LBT failure of the side link; or 0 may indicate that the RB set associated with SL-RBsetID i has triggered the continuous LBT failure of the side link, and 1 may indicate that the RB set associated with SL-RBsetID i has not triggered the continuous LBT failure of the side link.
  • This embodiment is not limited.
  • FIG8 is an exemplary description assuming that there are 16 RB sets, and there may also be 24 RB sets or 32 RB sets or more or less RB sets, which are not limited in this embodiment.
  • the MAC CE information reported by the terminal device includes the resource pool identifier and the value corresponding to the RB set identifier.
  • the resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to these RB set identifiers.
  • the sidelink continuous LBT failure MAC CE indicates through an octet whether the RB set associated with SL-RBsetID m on the resource pool corresponding to the resource pool identifier has triggered the sidelink continuous LBT failure, wherein 1 may indicate that the RB set associated with SL-RBsetID m on the resource pool corresponding to the resource pool identifier has triggered the sidelink continuous LBT failure, and 0 may indicate that the RB set associated with SL-RBsetID m on the resource pool corresponding to the resource pool identifier has not triggered the sidelink continuous LBT failure; or 0 may indicate that the RB set associated with SL-RBsetID m on the resource pool corresponding to the resource pool identifier has triggered the sidelink continuous LBT failure, and 1 may indicate that the RB set associated with SL-RBsetID m on the resource pool corresponding to the resource pool identifier has not triggered the sidelink continuous LBT failure.
  • This embodiment is not
  • the above is a reporting method in a non-carrier aggregation scenario.
  • the following describes in detail a reporting method in a carrier aggregation scenario.
  • step 401 may specifically include: in a carrier aggregation scenario, reporting through SUI or UAI a list including RB set identifiers (the RB sets corresponding to these RB set identifiers triggered continuous LBT failure of the sidelink, and the sidelink continuous LBT failure state was not canceled) and a fifth cell identifier, the fifth cell identifier being the identifier of the service cell associated with the RB set corresponding to the RB set identifier; or, reporting through SUI or UAI a list including RB set identifiers (the RB sets corresponding to these RB set identifiers triggered continuous LBT failure of the sidelink, and the sidelink continuous LBT failure state was not canceled), a fourth resource pool identifier and a sixth cell identifier, the fourth resource pool identifier being the identifier of the resource pool associated with the RB set corresponding to the RB set identifier, and the sixth cell identifier being the identifier on the service cell associated with the resource pool corresponding to
  • the detection granularity of the continuous LBT failure of the sidelink is the granularity of the RB set
  • the granularity of the RB set is smaller than the granularity of the resource pool, that is, one resource pool can contain multiple RB sets
  • a list including the RB set identifier (the RB sets corresponding to these RB set identifiers triggered the continuous LBT failure of the sidelink, and the continuous LBT failure state of the sidelink was not canceled)
  • the resource pool identifier the identifier of the resource pool associated with the RB set corresponding to the RB set identifier
  • the cell identifier the cell identifier of the service cell associated with the resource pool corresponding to the resource pool identifier
  • the SUI or UAI may include a list including the RB set identifier and the cell identifier of the RB set that triggered the sidelink continuous LBT failure.
  • the RB set identifier may be SL–RBsetID–r17, the RB set corresponding to the identifier triggered the sidelink continuous LBT failure, and the cell identifier is the identifier of the service cell associated with the RB set corresponding to the RB set identifier.
  • step 401 may specifically include: in the carrier aggregation scenario, the terminal device reports a fourth MAC CE information, the fourth MAC CE information includes the seventh cell identifier and the fourth value corresponding to the fifth RB set identifier, the seventh cell identifier is the identifier of the service cell associated with the RB set corresponding to the fifth RB set identifier; or, the fourth MAC CE information includes the eighth cell identifier, the fifth resource pool identifier and the fourth value corresponding to the fifth RB set identifier, the fifth resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to the fifth RB set identifier, and the eighth cell identifier is the identifier of the service cell associated with the resource pool corresponding to the fifth resource pool identifier; wherein the fourth value is used to indicate whether the RB set corresponding to the fifth RB set identifier triggers the
  • the MAC CE information reported by the terminal device includes the cell identifier and the numerical value corresponding to the RB set identifier.
  • the MAC CE of the continuous LBT failure of the sidelink indicates through an octet whether the RB set associated with SL-RBsetID m1 on the serving cell corresponding to SL-ServCellIndex i (cell identifier) has triggered the continuous LBT failure of the sidelink, wherein 1 indicates that the RB set associated with SL-RBsetID m1 on the serving cell corresponding to SL-ServCellIndex i has triggered the continuous LBT failure of the sidelink, and 0 indicates that the RB set associated with SL-RBsetID m1 on the serving cell corresponding to SL-ServCellIndex i has not triggered the continuous LBT failure of the sidelink.
  • the MAC CE information reported by the terminal device includes the cell identifier, the resource pool identifier, and the value corresponding to the RB set identifier.
  • the resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to these RB set identifiers
  • the cell identifier is the cell identifier of the service cell associated with the resource pool corresponding to the resource pool identifier.
  • the sidelink continuous LBT failure MAC CE indicates the resource pool identifier of the resource pool on the service cell corresponding to the cell identifier through an octet, and whether the RB set associated with SL-RBsetIDm2 on the resource pool corresponding to the resource pool identifier has triggered the sidelink continuous LBT failure, where 1 indicates that the RB set associated with SL-RBsetIDm2 on the RB set corresponding to the RB set identifier has triggered the sidelink continuous LBT failure, and 0 indicates that the RB set associated with SL-RBsetIDm2 on the RB set corresponding to the RB set identifier has not triggered the sidelink continuous LBT failure.
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state
  • the identifier of the RB set that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device can determine the RB set where the continuous LBT failure has occurred, and then can perform recovery processing by reconfiguring resources or other methods.
  • Fig. 11 is a flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. As shown in Fig. 11, the method can be applied to a terminal device and can include the following steps.
  • Step 501 The terminal device reports the cell identifier of the service cell that triggers the failure of continuous LBT of the sidelink through the third signaling.
  • the third signaling includes: SUI, or UAI, or MAC CE.
  • SUI and UAI can be considered as RRC signaling
  • MAC CE can be considered as MAC signaling.
  • the detection granularity of the sidelink continuous LBT failure is the BWP granularity.
  • the number of sidelink LBT failures is counted for the BWP activated by the current carrier of the terminal device, and the network device configures the corresponding maximum number of sidelink continuous LBT failures and the sidelink continuous LBT failure detection timer to the terminal device through RRC signaling, which are used to count the sidelink continuous LBT failures.
  • the number of sidelink LBT failures of the BWP activated by the current carrier is greater than or equal to the maximum number, it can be considered that the BWP activated by the current carrier has triggered the sidelink continuous LBT failure, and then the cell identifier of the service cell that triggered the sidelink continuous LBT failure is reported to the network device through SUI or UAI or sidelink continuous LBT failure MAC CE.
  • the terminal device counts the number of uplink LBT failures on each BWP.
  • the network device configures the maximum number of consecutive LBT failures (lbt-FailureInstanceMaxCount) and the consecutive LBT failure detection timer (lbt-FailureDetectionTimer) for the terminal device according to each serving cell (servingcell) through RRC signaling (lbt-FailureRecoveryConfig) to count consecutive LBT failures.
  • the terminal device maintains an LBT_counter variable for each serving cell, and the initial value of the variable is 0.
  • the terminal device For each activated serving cell configured with lbt-FailureRecoveryConfig, when the terminal device receives an LBT failure indication submitted by the physical layer, it starts or restarts lbt-FailureDetectionTimer, and the LBT_counter is incremented by 1. When the LBT_counter is greater than or equal to lbt-FailureInstanceMaxCount, the activated BWP on the serving cell triggers a continuous LBT failure.
  • the terminal device When the lbt-FailureDetectionTimer times out, or the higher layer reconfigures the lbt-FailureInstanceMaxCount or lbt-FailureDetectionTimer, or all consecutive LBT failures on this service cell are canceled, the terminal device resets the LBT_counter to 0.
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state
  • the cell identifier of the service cell that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the service cell where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or other methods.
  • Fig. 12 is a flowchart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. Based on the embodiment shown in Fig. 11, as shown in Fig. 12, it can be applied to the terminal device side and can include the following steps.
  • Step 601 When the terminal device detects that at least one service cell has triggered a sidelink continuous LBT failure and has not canceled the sidelink continuous LBT failure state, the cell identifier of the at least one service cell is reported through the SUI or UAI or the sidelink continuous LBT failure MAC CE.
  • the sidelink continuous LBT failure state of the service cell will be canceled.
  • the service cell identity of service cell a (triggering a sidelink continuous LBT failure) has been reported through SUI or UAI or sidelink continuous LBT failure MAC CE, then when the service cell identity of this service cell a is reported successfully, the sidelink continuous LBT failure state of this service cell a will be canceled.
  • the terminal device when the terminal device detects that at least one service cell has triggered a sidelink continuous LBT failure and has not canceled the sidelink continuous LBT failure state (such as it has not been reported before), the terminal device reports the service cell identity of the at least one service cell through SUI or UAI or sidelink continuous LBT failure MAC CE.
  • step 601 may specifically include: in a non-carrier aggregation scenario, reporting parameter information through SUI or UAI, wherein the parameter information is used to indicate whether the current serving cell has triggered a sidelink continuous LBT failure.
  • SUI or UAI can define a new parameter, such as sl-ConsistentLBT, which can be used to indicate whether the current service cell has triggered a sidelink continuous LBT failure. If this parameter is set to 1, it can be used to indicate that the current service cell has triggered a sidelink continuous LBT failure, and if this parameter is set to 0, it can be used to indicate that the current service cell has not triggered a sidelink continuous LBT failure. Alternatively, if this parameter is true/enable, it can indicate that the current service cell has triggered a sidelink continuous LBT failure.
  • the terminal device reports through SUI or UAI, if this parameter is carried, it indicates that the current service cell has triggered a sidelink continuous LBT failure, and if this parameter is not carried, it indicates that the current service cell has not triggered a sidelink continuous LBT failure. It should be noted that in the specific implementation, there may be other optional methods, which are not limited in this embodiment.
  • step 601 may specifically include: in a non-carrier aggregation scenario, the terminal device reports the fifth MAC CE information, and the fifth MAC CE information can be used to indicate whether the current service cell has triggered the sidelink continuous LBT failure.
  • the sidelink continuous LBT failure MAC CE can be identified by the logical channel identifier (LCID) in the MAC subheader, such as a new LCID is defined to indicate the new MAC CE.
  • LCID logical channel identifier
  • the network device receives a MAC CE containing the newly defined LCID, it means that the current service cell has triggered the sidelink continuous LBT failure.
  • the detection granularity of the sidelink continuous LBT failure is the BWP granularity, so the MAC CE can have a fixed size of 0 bytes.
  • the above is a reporting method in a non-carrier aggregation scenario.
  • the following describes in detail a reporting method in a carrier aggregation scenario.
  • step 601 may specifically include: in a carrier aggregation scenario, reporting a list including cell identifiers (the serving cells corresponding to these cell identifiers triggered the sidelink continuous LBT failure and did not cancel the sidelink continuous LBT failure state) through SUI or UAI.
  • SUI or UAI may include a list, which may include cell identifiers of serving cells that triggered the sidelink continuous LBT failure and did not cancel the sidelink continuous LBT failure state.
  • step 601 may specifically include: in a carrier aggregation scenario, the terminal device reports a sixth MAC CE information, the sixth MAC CE information includes a fifth value corresponding to the cell identifier, wherein the fifth value can be used to indicate whether the service cell corresponding to the cell identifier has triggered a sidelink continuous LBT failure.
  • MAC CE format In actual applications, if the number of aggregated sidelink carriers is less than or equal to 8, a 1-byte MAC CE format can be used, as shown in Figure 13; and if the number of aggregated sidelink carriers is greater than 8, a 4-byte MAC CE format can be used, as shown in Figure 14.
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state
  • the cell identifier of the service cell that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the service cell where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or other methods.
  • Fig. 15 shows a schematic flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. As shown in Fig. 15, the method can be applied to a terminal device and can include the following steps.
  • Step 701 The terminal device reports the terminal identifier of the target terminal that triggers the failure of continuous LBT of the sidelink through the fourth signaling.
  • the target terminal may be a peer UE associated with unicast, broadcast, or multicast, and the terminal identifier of the target terminal may be the source layer 2 address, name, or ID number of the peer UE.
  • the fourth signaling may specifically include: SUI, or UAI, or MAC CE, etc. SUI and UAI can be considered as RRC signaling, while MAC CE can be considered as MAC signaling.
  • the detection granularity of the continuous LBT failure of the side link is the source address + target address pair granularity.
  • the terminal device can report the address of the peer UE that triggered the continuous LBT failure of the side link to the network device through SUI, UAI, or MAC CE.
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state
  • the terminal identifier of the target terminal that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device can determine the target terminal where the continuous LBT failure has occurred, and then make corresponding adjustments.
  • Figure 16 shows a schematic flow chart of a method for reporting failure of continuous listen-before-speak in a sidelink according to an embodiment of the present application. Based on the embodiment of Figure 15 , as shown in Figure 16 , it can be applied to a terminal device for execution, and the method may include the following steps.
  • Step 801 When the terminal device detects that at least one target terminal has triggered a side link continuous LBT failure and has not canceled the side link continuous LBT failure state, the terminal identifier of at least one target terminal is reported through the SUI or UAI or the side link continuous LBT failure MAC CE.
  • the sidelink continuous LBT failure state of the target terminal will be canceled.
  • the terminal identification of the target terminal b (triggering the sidelink continuous LBT failure) has been reported through the SUI or UAI or the sidelink continuous LBT failure MAC CE, then when the terminal identification of the target terminal b is reported successfully, the sidelink continuous LBT failure state of the target terminal b will be canceled.
  • the terminal device when the terminal device detects that at least one target terminal has triggered a sidelink continuous LBT failure and has not canceled the sidelink continuous LBT failure state (such as it has not been reported before), the terminal device reports the terminal identification of the at least one target terminal through the SUI or UAI or the sidelink continuous LBT failure MAC CE.
  • step 801 may specifically include: reporting a list including terminal identifiers (the target terminals corresponding to these terminal identifiers triggered the side link continuous LBT failure and did not cancel the side link continuous LBT failure status) through SUI or UAI.
  • the target terminal may be a peer UE associated with unicast, broadcast, or multicast.
  • the terminal device detects that at least one target terminal has triggered a sidelink continuous LBT failure, it reports to the network device through the SUI or UAI.
  • the SUI or UAI may include a list containing the address of the peer UE that has triggered the sidelink continuous LBT failure and has not canceled the sidelink continuous LBT failure status.
  • step 801 may specifically include: the terminal device reports the seventh MAC CE information, the seventh MAC CE information includes a terminal identifier, and the target terminal corresponding to the terminal identifier triggers the side link continuous LBT failure, and the side link continuous LBT failure state is not canceled.
  • the side link continuous LBT failure MAC CE contains the opposite UE address of the opposite UE that triggered the side link continuous LBT failure, as shown in Figure 17, where Destination Index 1 (DST1) represents that the target terminal 1 corresponding to the identifier triggers the side link continuous LBT failure, and Destination Index 2 (DST2) represents that the target terminal 2 corresponding to the identifier triggers the side link continuous LBT failure, etc.
  • DST1 Destination Index 1
  • DST2 Destination Index 2
  • the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state
  • the terminal identifier of the target terminal that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the target terminal where the continuous LBT failure has occurred, and can then make corresponding adjustments.
  • the method provided by the embodiment of the present application is introduced from the perspective of the terminal device.
  • the terminal device may include a hardware structure and a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function of the above functions can be executed in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • the present application also provides a reporting device for continuous listen-before-speak failure of the sidelink, which can be applied to the terminal device side. Since the reporting device for continuous listen-before-speak failure of the sidelink provided in the embodiments of the present application corresponds to the reporting methods for continuous listen-before-speak failure of the sidelink provided in the above-mentioned embodiments, the implementation methods of the reporting methods for continuous listen-before-speak failure of the sidelink are also applicable to the reporting device for continuous listen-before-speak failure of the sidelink provided in the present embodiment, and will not be described in detail in the present embodiment.
  • Figure 18 is a structural diagram of a reporting device for a side link continuous listen-before-talk failure provided in an embodiment of the present application.
  • the device may specifically include: a first sending module 91, configured to report the resource pool identifier of a resource pool that triggers the side link continuous listen-before-talk LBT failure through a first signaling report.
  • the first signaling includes: SUI, or UAI, or MAC CE.
  • the first sending module 91 is specifically configured to report the resource pool identifier of the at least one resource pool through SUI or UAI or side link continuous LBT failure MAC CE when the terminal device detects that at least one resource pool has triggered a side link continuous LBT failure and has not canceled the side link continuous LBT failure state.
  • the first sending module 91 is specifically configured to report a list including the resource pool identifier through SUI or UAI in a non-carrier aggregation scenario; or, to report a list including the resource pool identifier and the resource block set RB set identifier through SUI or UAI, wherein the RB set identifier is an identifier of the RB set associated with the resource pool corresponding to the resource pool identifier.
  • the first sending module 91 is specifically configured to, in a non-carrier aggregation scenario, report, by a terminal device, a first MAC CE information, wherein the first MAC CE information includes a first value corresponding to a first resource pool identifier; or, the first MAC CE information includes a first RB set identifier and a first value corresponding to a first resource pool identifier, wherein the first RB set identifier is an identifier of an RB set associated with a resource pool corresponding to the first resource pool identifier; wherein the first value is used to indicate whether the resource pool corresponding to the first resource pool identifier has triggered a side link continuous LBT failure.
  • the first sending module 91 is specifically configured to report, through SUI or UAI in a carrier aggregation scenario, a list including the resource pool identifier and the first cell identifier, wherein the first cell identifier is an identifier of a service cell associated with the resource pool corresponding to the resource pool identifier; or, to report, through SUI or UAI, a list including the resource pool identifier, a second RB set identifier and a second cell identifier, wherein the second RB set identifier is an identifier of an RB set associated with the resource pool corresponding to the resource pool identifier, and the second cell identifier is a cell identifier of a service cell associated with the RB set corresponding to the second RB set identifier.
  • the first sending module 91 is specifically configured to, in a carrier aggregation scenario, report, by the terminal device, a second MAC CE information, wherein the second MAC CE information includes a third cell identifier and a second numerical value corresponding to a second resource pool identifier, wherein the third cell identifier is an identifier of a service cell associated with the resource pool corresponding to the second resource pool identifier; or, the second MAC CE information includes a fourth cell identifier, a third RB set identifier and a second numerical value corresponding to the second resource pool identifier, wherein the third RB set identifier is an identifier of an RB set associated with the resource pool corresponding to the second resource pool identifier, and the fourth cell identifier is a cell identifier of a service cell associated with the RB set corresponding to the third RB set identifier; wherein the second numerical value is used to indicate whether the resource pool corresponding to the second resource pool identifier has triggered a continuous
  • the terminal device when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connection state, the resource pool identifier of the resource pool that triggers the side link continuous LBT failure is reported through signaling, so that the network device determines the resource pool where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or other methods.
  • Fig. 19 is a schematic diagram of the structure of a reporting device for a continuous listen-before-talk failure of a side link provided in an embodiment of the present application.
  • the device may specifically include: a second sending module 1001, configured to report an RB set identifier of an RB set that triggers a continuous LBT failure of the side link through a second signaling.
  • the second signaling includes: SUI, or UAI, or MAC CE.
  • the second sending module 1001 is specifically configured to report the RB set identifier of the at least one RB set through SUI or UAI or side link continuous LBT failure MAC CE when the terminal device detects that at least one RB set has triggered a side link continuous LBT failure and has not canceled the side link continuous LBT failure state.
  • the second sending module 1001 is specifically configured to report a list including the RB set identifier through SUI or UAI in a non-carrier aggregation scenario; or, to report a list including the RB set identifier and the resource pool identifier through SUI or UAI, wherein the resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the RB set identifier.
  • the second sending module 1001 is specifically configured to, in a non-carrier aggregation scenario, the terminal device reports a third MAC CE information, wherein the third MAC CE information includes a third numerical value corresponding to a fourth RB set identifier; or, the third MAC CE information includes a third resource pool identifier and a third numerical value corresponding to a fourth RB set identifier, wherein the resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the RB set identifier; wherein the third numerical value is used to indicate whether the RB set corresponding to the fourth RB set identifier triggers a side link continuous LBT failure.
  • the second sending module 1001 is specifically configured to report, through SUI or UAI, in a carrier aggregation scenario, a list including the RB set identifier and the fifth cell identifier, wherein the fifth cell identifier is the identifier of the service cell associated with the RB set corresponding to the RB set identifier; or, to report, through SUI or UAI, a list including the RB set identifier, the fourth resource pool identifier and the sixth cell identifier, wherein the fourth resource pool identifier is the identifier of the resource pool associated with the RB set corresponding to the RB set identifier, and the sixth cell identifier is the identifier on the service cell associated with the resource pool corresponding to the fourth resource pool identifier.
  • the second sending module 1001 is specifically configured to, in a carrier aggregation scenario, report, by the terminal device, a fourth MAC CE information, wherein the fourth MAC CE information includes a seventh cell identifier and a fourth numerical value corresponding to a fifth RB set identifier, wherein the seventh cell identifier is an identifier of a service cell associated with the RB set corresponding to the fifth RB set identifier; or, the fourth MAC CE information includes an eighth cell identifier, a fifth resource pool identifier and a fourth numerical value corresponding to a fifth RB set identifier, wherein the fifth resource pool identifier is an identifier of a resource pool associated with the RB set corresponding to the fifth RB set identifier, and the eighth cell identifier is an identifier of a service cell associated with the resource pool corresponding to the fifth resource pool identifier; wherein the fourth numerical value is used to indicate whether the RB set corresponding to the fifth RB set identifier triggers a
  • the terminal device when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connected state, the identifier of the RB set that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device can determine the RB set where the continuous LBT failure has occurred, and then can perform recovery processing by reconfiguring resources or other methods.
  • Figure 20 is a schematic diagram of a structure of a reporting device for a sidelink continuous listen-before-talk failure provided by an embodiment of the present application.
  • the device may include: a third determination module 1101, configured to report a cell identifier of a serving cell that triggers a sidelink continuous LBT failure through a third signaling.
  • the third signaling includes: SUI, or UAI, or MAC CE.
  • the third determination module 1101 is specifically configured to report the cell identifier of the at least one service cell through SUI or UAI or sidelink continuous LBT failure MAC CE when the terminal device detects that at least one service cell has triggered a sidelink continuous LBT failure and has not canceled the sidelink continuous LBT failure state.
  • the third determination module 1101 is specifically configured to report parameter information through SUI or UAI in a non-carrier aggregation scenario, where the parameter information is used to indicate whether the current serving cell has triggered a sidelink continuous LBT failure.
  • the third determination module 1101 is specifically configured to, in a non-carrier aggregation scenario, cause the terminal device to report fifth MAC CE information, wherein the fifth MAC CE information is used to indicate whether the current serving cell has triggered a sidelink continuous LBT failure.
  • the third determination module 1101 is specifically configured to report the list including the cell identifiers through SUI or UAI in a carrier aggregation scenario.
  • the third determination module 1101 is specifically configured to, in a carrier aggregation scenario, the terminal device reports a sixth MAC CE information, wherein the sixth MAC CE information includes a fifth value corresponding to the cell identifier, wherein the fifth value is used to indicate whether the service cell corresponding to the cell identifier has triggered a sidelink continuous LBT failure.
  • the terminal device when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connection state, the cell identifier of the service cell that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device determines the service cell where the continuous LBT failure has occurred, and can then perform recovery processing by reconfiguring resources or other methods.
  • Figure 21 is a schematic diagram of a structure of a reporting device for a sidelink continuous listen-before-talk failure provided by an embodiment of the present application.
  • the device may include: a fourth sending module 1201, configured to report a terminal identifier of a target terminal that triggers a sidelink continuous LBT failure through a fourth signaling.
  • the fourth signaling includes: SUI, or UAI, or MAC CE.
  • the fourth sending module 1201 is specifically configured to report the terminal identification of at least one target terminal through SUI or UAI or side link continuous LBT failure MAC CE when the terminal device detects that at least one target terminal has triggered a side link continuous LBT failure and has not canceled the side link continuous LBT failure state.
  • the fourth sending module 1201 is specifically configured to report the list including the terminal identification through SUI or UAI.
  • the fourth sending module 1201 is specifically configured for the terminal device to report the seventh MAC CE information, and the seventh MAC CE information includes the terminal identifier.
  • the terminal device when the terminal device works in the network dynamic scheduling mode (Mode 1), or the terminal device works in the resource autonomous selection mode (Mode 2) and is in the RRC connection state, the terminal identifier of the target terminal that triggers the continuous LBT failure of the side link is reported through signaling, so that the network device can determine the target terminal where continuous LBT failure has occurred, and then make corresponding adjustments.
  • FIG 22 is a schematic diagram of the structure of a communication device 1300 provided in this embodiment. It can be applied to the terminal device side.
  • the communication device 1300 can be a network device, or a user device, or a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the user device to implement the above method.
  • the device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.
  • the communication device 1300 may include one or more processors 1301.
  • the processor 1301 may be a general-purpose processor or a dedicated processor, etc.
  • it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and communication data
  • the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.
  • the communication device 1300 may further include one or more memories 1302, on which a computer program 1304 may be stored, and the processor 1301 executes the computer program 1304 so that the communication device 1300 performs the method described in the above method embodiment.
  • data may also be stored in the memory 1302.
  • the communication device 1300 and the memory 1302 may be provided separately or integrated together.
  • the communication device 1300 may further include a transceiver 1305 and an antenna 1306.
  • the transceiver 1305 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1305 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., and is used to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is used to implement a transmitting function.
  • the communication device 1300 may further include one or more interface circuits 1307.
  • the interface circuit 1307 is used to receive code instructions and transmit them to the processor 1301.
  • the processor 1301 executes the code instructions to enable the communication device 1300 to execute the method described in the above method embodiment.
  • the processor 1301 may include a transceiver for implementing the receiving and sending functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
  • the processor 1301 may store a computer program 1303, which runs on the processor 1301 and enables the communication device 1300 to perform the method described in the above method embodiment.
  • the computer program 1303 may be fixed in the processor 1101, in which case the processor 1301 may be implemented by hardware.
  • the communication device 1300 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment.
  • the processor and transceiver described in the present application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide semiconductor
  • PMOS P-type metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a user device, but the scope of the communication device described in the present application is not limited thereto, and the structure of the communication device may not be limited by FIG. 22.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be:
  • the IC set may also include a storage component for storing data and computer programs;
  • ASIC such as modem
  • the communication device can be a chip or a chip system
  • the communication device can be a chip or a chip system
  • the schematic diagram of the chip structure shown in Figure 23 includes a processor 1401 and an interface 1402.
  • the number of processors 1401 can be one or more, and the number of interfaces 1402 can be multiple.
  • the chip further includes a memory 1403, and the memory 1403 is used to store necessary computer programs and data.
  • the present application also provides a computer storage medium that can be applied to a terminal device side, on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above-mentioned method embodiments are realized.
  • the present application also provides a computer program product that can be applied to a terminal device side.
  • the computer program product When executed by a computer, it realizes the functions of any of the above method embodiments.
  • the computer program product includes one or more computer programs.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrated. Available media can be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks (SSD)), etc.
  • At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application.
  • the technical features in the technical feature are distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc., and there is no order of precedence or size between the technical features described by the "first”, “second”, “third”, “A”, “B”, “C” and “D”.
  • machine-readable medium and “computer-readable medium” refer to any computer program product, apparatus, and/or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal.
  • machine-readable signal refers to any signal for providing machine instructions and/or data to a programmable processor.
  • the systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components.
  • the components of the system may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include: a local area network (LAN), a wide area network (WAN), and the Internet.
  • a computer system may include clients and servers.
  • Clients and servers are generally remote from each other and usually interact through a communication network.
  • the relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

Landscapes

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

Abstract

La présente demande se rapporte au domaine technique des communications, et concerne un procédé et un appareil pour rapporter une défaillance d'écoute avant de parler (LBT) continue de liaison latérale. L'application du procédé de la présente demande résout le problème technique selon lequel, pour une communication de liaison latérale, lorsqu'un dispositif terminal fonctionne dans un mode de planification dynamique de réseau ou lorsque le dispositif terminal fonctionne dans un mode de sélection autonome de ressources et est dans un état connecté RRC, si une défaillance LBT continue de liaison latérale est déclenchée, le dispositif terminal n'est pas sûr de rapporter un état de défaillance LBT continue de liaison latérale.
PCT/CN2022/128083 2022-10-27 2022-10-27 Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale WO2024087123A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280003923.5A CN118266198A (zh) 2022-10-27 2022-10-27 一种侧行链路连续先听后说失败的上报方法及装置
PCT/CN2022/128083 WO2024087123A1 (fr) 2022-10-27 2022-10-27 Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/128083 WO2024087123A1 (fr) 2022-10-27 2022-10-27 Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale

Publications (1)

Publication Number Publication Date
WO2024087123A1 true WO2024087123A1 (fr) 2024-05-02

Family

ID=90829721

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/128083 WO2024087123A1 (fr) 2022-10-27 2022-10-27 Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale

Country Status (2)

Country Link
CN (1) CN118266198A (fr)
WO (1) WO2024087123A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071535A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 一种通信方法及装置
WO2022104545A1 (fr) * 2020-11-17 2022-05-27 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif terminal et dispositif de réseau
CN114938710A (zh) * 2022-03-28 2022-08-23 北京小米移动软件有限公司 侧行链路sidelink通信方法及装置
CN115734202A (zh) * 2021-08-31 2023-03-03 华为技术有限公司 旁链路通信方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071535A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 一种通信方法及装置
WO2022104545A1 (fr) * 2020-11-17 2022-05-27 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif terminal et dispositif de réseau
CN115734202A (zh) * 2021-08-31 2023-03-03 华为技术有限公司 旁链路通信方法及设备
CN114938710A (zh) * 2022-03-28 2022-08-23 北京小米移动软件有限公司 侧行链路sidelink通信方法及装置

Also Published As

Publication number Publication date
CN118266198A (zh) 2024-06-28

Similar Documents

Publication Publication Date Title
US11540318B2 (en) Carrier set determination method and device, storage medium and electronic device
EP3742766A1 (fr) Procédé et appareil de transmission de données
WO2024164149A1 (fr) Procédé et dispositif pour déterminer une ressource de transmission pour un signal de référence
WO2024087123A1 (fr) Procédé et appareil pour rapporter une défaillance d'écoute avant de parler continue de liaison latérale
KR102657514B1 (ko) 무선 통신 시스템에서 복제된 데이터를 송수신하기 위한 방법 및 장치
JP7083854B2 (ja) データ複製をサポートする方法、送信側デバイスおよび受信側デバイス
WO2024087026A1 (fr) Procédé et appareil de traitement pour un échec de procédure de type écouter avant de parler continue de liaison latérale
WO2024092626A1 (fr) Procédé et appareil de traitement de défaillances d'écoute avant de parler continues de liaison latérale
WO2024168756A1 (fr) Procédé et appareil de traitement de communication
WO2024168752A1 (fr) Procédé de communication en multidiffusion et appareil associé
WO2024197934A1 (fr) Procédé et appareil de communication pour liaison latérale (sl) dans un spectre sans licence
WO2024197944A1 (fr) Procédé et appareil de récupération de liaison
WO2024016244A1 (fr) Procédé et appareil de configuration pour prendre en charge la réception d'un service de multidiffusion inactif
WO2024138397A1 (fr) Procédé et appareil de détermination de priorité de liaison latérale
WO2024197931A1 (fr) Procédé et appareil de configuration de porteuse radio de données (drb) de liaison latérale
WO2024207527A1 (fr) Procédé et appareil de communication à trajets multiples
WO2024065452A1 (fr) Procédé, appareil et système de communication à trajets multiples
WO2024197758A1 (fr) Procédé de comptage de défaillances lbt cohérentes sl, et appareil de communication
WO2024092824A1 (fr) Procédé et appareil de rapport pour rapport de défaillance
WO2024168479A1 (fr) Procédé et appareil pour une configuration d'activation de processus de demande automatique de répétition hybride (harq)
WO2024138396A1 (fr) Procédé et appareil de détection de défaillance de liaison radio pour liaison latérale dans un spectre sans licence
WO2024197949A1 (fr) Procédé et appareil de commande de communication
WO2024197950A1 (fr) Procédé et appareil de commande de communication
WO2024187390A1 (fr) Procédé de transmission de liaison latérale et appareil associé
WO2024168553A1 (fr) Procédé et appareil de communication de liaison latérale

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280003923.5

Country of ref document: CN

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

Ref document number: 22963107

Country of ref document: EP

Kind code of ref document: A1