WO2024168756A1 - 通信处理方法及装置 - Google Patents

通信处理方法及装置 Download PDF

Info

Publication number
WO2024168756A1
WO2024168756A1 PCT/CN2023/076614 CN2023076614W WO2024168756A1 WO 2024168756 A1 WO2024168756 A1 WO 2024168756A1 CN 2023076614 W CN2023076614 W CN 2023076614W WO 2024168756 A1 WO2024168756 A1 WO 2024168756A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
terminal device
shared cot
data packet
shared
Prior art date
Application number
PCT/CN2023/076614
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2023/076614 priority Critical patent/WO2024168756A1/zh
Publication of WO2024168756A1 publication Critical patent/WO2024168756A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a communication processing method and device.
  • SL sidelink
  • the present disclosure proposes a communication processing method and device.
  • side link communication when a data packet obtained through LCP processing does not meet the use conditions of a shared COT, a specific processing solution for a terminal device is provided, and the specific processing behavior of the terminal device is clarified to meet business needs.
  • a first aspect of the present disclosure provides a communication processing method that can be applied to a terminal device for execution.
  • the method includes: when a first data packet does not meet the use conditions of a shared COT, the terminal device executes a first type of Listen Before Talk (LBT), wherein the first data packet is a data packet obtained by LCP processing.
  • LBT Listen Before Talk
  • the terminal device is a response terminal of a shared COT.
  • the first data packet does not meet the use condition of the shared COT, including at least one of the following:
  • the channel access priority class (CAPC) of the first data packet is greater than the CAPC indicated in the shared COT indication information;
  • the target terminal receiving the first data packet is not an initiating terminal of the shared COT.
  • the method further includes: determining whether the terminal device is a responding terminal of the shared COT based on a target address and a service type indicated by sidelink control information (Sidelink Control Information, SCI) carrying the shared COT indication information.
  • SCI Sidelink Control Information
  • the determining whether the terminal device is a responding terminal of the shared COT based on the target address indicated by the SCI carrying the shared COT indication information and the service type includes: when the service type is a unicast service and the target address indicated by the SCI carrying the shared COT indication information is the address of the terminal device, determining that the terminal device is a responding terminal of the shared COT; or, when the service type is a multicast service and the target address indicated by the SCI carrying the shared COT indication information is an address associated with the multicast service, and the response terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determining that the terminal device is a responding terminal of the shared COT; or, when the service type is a broadcast service and the target address indicated by the SCI carrying the shared COT indication information is an address associated with the broadcast service, and the response terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determining that the terminal device
  • the method further includes: the terminal device sending the first data packet using the shared COT, or sending the first data packet without using the shared COT.
  • the terminal device performs a first type of LBT, including: the terminal device performs the first type of LBT before sending the first data packet.
  • a second aspect of the present disclosure provides a communication processing device, applied to a terminal device, the device comprising: a processing module, configured to perform a first type of LBT when a first data packet does not meet the usage conditions of a shared COT, wherein the first data packet is a data packet obtained by LCP processing.
  • the third aspect embodiment of the present disclosure provides a communication device, which includes: a transceiver; a memory; a processor, which is connected to the transceiver and the memory respectively, 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 of the present disclosure.
  • the fourth aspect embodiment of the present disclosure provides a computer storage medium, wherein the computer storage medium stores computer executable instructions; after the computer executable instructions are executed by a processor, the method of the first aspect embodiment of the present disclosure can be implemented.
  • the disclosed embodiments provide a communication processing method and apparatus, wherein when a first data packet does not meet the use conditions of a shared COT, a terminal device executes a first type of LBT, wherein the first data packet is a data packet obtained through LCP processing.
  • a terminal device executes a first type of LBT, wherein the first data packet is a data packet obtained through LCP processing.
  • this embodiment provides a specific processing solution for the terminal device and clarifies the specific processing behavior of the terminal device to meet business needs.
  • FIG1 is a schematic diagram of an exemplary architecture according to an embodiment of the present disclosure.
  • FIG2 is a flow chart of a communication processing method according to an embodiment of the present disclosure.
  • FIG3 is a flow chart of a communication processing method according to an embodiment of the present disclosure.
  • FIG4 is a flow chart of a communication processing method according to an embodiment of the present disclosure.
  • FIG5 is a block diagram of a communication processing device according to an embodiment of the present disclosure.
  • FIG6 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the disclosed embodiments, 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 determining”.
  • the communication interface between terminal devices is called the PC-5 interface.
  • the link for transmitting data between terminal devices is called the sidelink.
  • the transmitting terminal device 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
  • PSSCH Physical Sidelink shared channel
  • PSSCH Physical Sidelink shared channel
  • the receiving terminal device performs HARQ-ACK feedback on PSSCH on the physical sidelink feedback channel (PSFCH).
  • PSFCH physical sidelink feedback channel
  • Dynamic scheduling means that the network dynamically allocates transmission resources on the sidelink to the terminal device based on the cached data reported by the terminal device, while autonomous selection means that the terminal device randomly selects transmission resources from the resource pool configured by the network.
  • the network can configure multiple resource pools for the terminal device on a bandwidth part (BWP).
  • BWP bandwidth part
  • RRC radio resource control
  • LBT is a technology to avoid channel access conflicts. Different terminal devices compete for shared unlicensed (or license-free) spectrum resources through LBT operations.
  • NR-U is a project of 3GPP in communication protocol version 16 (release16, R16), which provides the necessary technology for operators to fully integrate unlicensed spectrum into 5G networks.
  • NR-U supports uplink and downlink operations in unlicensed frequency bands.
  • channel access for both downlink and uplink depends on the LBT feature. The wireless device or base station must first "sense" the communication channel and find that there is no communication before any transmission.
  • LBT type includes type 1 and type 2.
  • Type 1 is based on the contention window, and the duration of channel monitoring is determined by a random number until the random number is equal to 0 and the channel is idle to access the channel; type 2 is based on a fixed period of time to monitor the channel, such as 25us, 16us, etc.
  • Shared COT is a feature discussed in R18, which allows type 1 LBT terminal devices to seize COT and share it with other terminal devices, but there are certain requirements for terminal devices that can share COT.
  • the terminal device that initiates the shared COT is called the initiating terminal (COT initiating UE) 11 of the shared COT, and the terminal device that uses the shared COT is called the responding terminal (responding UE) 12.
  • the multiplexing function of the media access control (MAC) layer at the sending end loads the data of multiple logical channels into one transport channel, that is, multiplexing multiple MAC service data units (SDUs) into one MAC packet data unit. (packet data unit, PDU), and sent through the physical layer channel.
  • SDUs MAC service data units
  • PDU packet data unit
  • the target terminal/address has at least one highest priority MAC CE or logical channel among all logical channels and MAC CEs that meet the following conditions.
  • SBj scheduled frequency band
  • the sidelink grant is configured grant type 1
  • the sl-configuredGrantType1Allowed configuration associated with the logical channel allows the MAC SDUs of the logical channel to be transmitted on configured grant type 1;
  • the list contains the configuration authorization identifiers associated with the sidelink authorizations
  • the HARQ attribute of the logical channel is HARQ-disabled.
  • CAPC is a parameter related to LBT. Different CAPCs will affect the priority when competing for channels. The smaller the CAPC value, the higher the priority.
  • the terminal device determines the CAPC of a MAC PDU according to the following guidelines:
  • the CAPC of the SL MAC PDU has the highest priority (the lowest CAPC value);
  • the CAPC of the SL MAC PDU has the highest priority (the lowest CAPC value);
  • the CAPC of the SL MAC PDU is the lowest priority CAPC associated with the logical channel multiplexed into this transport block (Transport Block, TB) (CAPC is configured according to logical channels) regardless of whether the SL MAC PDU contains a SL MAC CE.
  • the sidelink works in the unlicensed spectrum (Sidelink-U) scenario. If the terminal device has completed the LCP processing process and the corresponding assembled data packet does not meet the use conditions of the shared COT, the specific processing behavior of the terminal device needs to be determined. However, there is currently no such communication processing solution. Therefore, this embodiment proposes a communication processing method and device.
  • Sidelink-U scenario when the data packet obtained by LCP processing does not meet the use conditions of the shared COT, a specific processing solution for the terminal device is provided, and the specific processing behavior of the terminal device is clarified to meet business needs.
  • FIG2 shows a flow chart of a communication processing method according to an embodiment of the present disclosure.
  • the method can be applied to the terminal device side for execution, and the terminal device can be called a terminal (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc.
  • terminal terminal
  • UE user equipment
  • MS mobile station
  • MT mobile terminal device
  • the terminal device can also be a car with communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving (self-driving), a wireless terminal device in remote medical surgery (remote medical surgery), a smart grid (smart grid), etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal devices.
  • the method of this embodiment may include the following steps.
  • Step 201 When the first data packet does not meet the usage conditions of the shared COT, the terminal device performs the first type of LBT.
  • the first data packet is a data packet obtained through LCP processing.
  • the first type of LBT may be the type 1 LBT mentioned above, that is, based on the contention window, the duration of channel monitoring is determined by a random number, and the channel is accessed only when the random number is equal to 0 and the channel is idle.
  • the terminal device has completed the LCP process and has assembled a data packet (the first data packet), but the data packet does not meet the conditions for using the shared COT. At this time, the terminal device executes type 1 LBT.
  • this embodiment provides a specific processing solution for the terminal device when the data packet obtained through LCP processing does not meet the use conditions of the shared COT, and clarifies the specific processing behavior of the terminal device to meet business needs.
  • Fig. 3 shows a flow chart of a communication processing method according to an embodiment of the present disclosure, which can be applied to a terminal device for execution, and as shown in Fig. 3, can include the following steps.
  • Step 301 Before obtaining shared COT indication information, a first data packet is obtained through LCP processing, and when the first data packet does not meet the use conditions of the shared COT, the terminal device performs a first type of LBT.
  • the terminal device has assembled a data packet before obtaining the shared COT indication information, but the data packet does not meet the conditions for using the shared COT.
  • the terminal device executes type 1 LBT.
  • the terminal device may be a responding terminal of the shared COT. For example, the terminal device determines that it is a responding terminal of the shared COT, such as the terminal 12 shown in FIG1 .
  • the terminal device has completed the LCP process before obtaining the shared COT indication information, that is, a SL MAC PDU has been generated, but the SL MAC PDU does not meet the use conditions of the shared COT. In this case, the terminal device performs type 1 LBT.
  • the first data packet does not meet the use condition of the shared COT, including at least one of the following:
  • the CAPC of the first data packet is greater than the CAPC indicated in the shared COT indication information; b.
  • the target terminal receiving the first data packet is not the initiating terminal of the shared COT.
  • the responding terminal is restricted to use only this COT to send sidelink data to the initiating terminal of the shared COT, which may include but not be limited to physical sidelink control channel (PSSCH) data or physical sidelink control channel (PSCCH) data
  • sidelink data may include but not be limited to physical sidelink control channel (PSSCH) data or physical sidelink control channel (PSCCH) data
  • PSSCH physical sidelink control channel
  • PSCCH physical sidelink control channel
  • Case A the CACP of the data packet is greater than the CAPC indicated by the shared COT indication information; and/or, Case B: the target terminal receiving the data packet is not the initiating terminal of the shared COT.
  • the supporting responding terminal can use this COT to send sidelink data to other terminal devices other than the initiating terminal of the shared COT, which may include but not be limited to PSSCH data or PSCCH data
  • the data packets grouped by the LCP do not meet the use conditions of the shared COT, which may include the following situations:
  • Case C the CACP of the data packet is greater than the CAPC indicated in the shared COT indication information.
  • the terminal device needs to determine whether it is a responding terminal of the shared COT. Accordingly, the method of this embodiment may also include: determining whether the terminal device is a responding terminal of the shared COT based on the target address and service type indicated by the SCI carrying the shared COT indication information. If the terminal device is a responding terminal of the shared COT, that is, it determines that it is a responding terminal of the shared COT, and the terminal device has completed the LCP process before obtaining the shared COT indication information, but the assembled data packet does not meet the use conditions of the shared COT, in this case, the terminal device performs type 1 LBT.
  • the above determination of whether the terminal device is a responding terminal of the shared COT based on the target address indicated by the SCI carrying the shared COT indication information and the service type may specifically include: when the service type is a unicast service and the target address indicated by the SCI carrying the shared COT indication information is the address of the terminal device (such as the layer 2 address of the terminal device, etc.), determining that the terminal device is a responding terminal of the shared COT.
  • the terminal device can determine that it is the responding terminal of the shared COT. For example, in response to the unicast service between terminal A and the initiating terminal of the shared COT, and the destination address indicated by the SCI carrying the shared COT indication information is the layer 2 address of terminal A, terminal A is determined to be the responding terminal of the shared COT.
  • terminal A in response to terminal A determining that the source layer 1 address (Source Layer-1ID) carried in the SCI carrying the shared COT indication information is equal to the 8 least significant bits (Least Significant Bit, LSB) of the layer 2 address of the initiating terminal of the shared COT, and the destination layer 1 address (Destination Layer-1ID) carried in the SCI carrying the shared COT indication information is equal to the 16LSB of the layer 2 address of terminal A, and the casttype indicated by the SCI carrying the shared COT indication information is unicast, terminal A is determined to be the responding terminal of the shared COT.
  • Source Layer-1ID the source layer 1 address carried in the SCI carrying the shared COT indication information is equal to the 8 least significant bits (Least Significant Bit, LSB) of the layer 2 address of the initiating terminal of the shared COT
  • LSB least significant bits
  • the above-mentioned determination of whether the terminal device is a responding terminal of the shared COT based on the target address indicated by the SCI carrying the shared COT indication information and the service type may also specifically include: when the service type is a multicast service, and the target address indicated by the SCI carrying the shared COT indication information is an address associated with the multicast service (such as the layer 2 address associated with the multicast service, etc.), and the responding terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determining that the terminal device is a responding terminal of the shared COT.
  • terminal B is determined to be the responding terminal of the shared COT.
  • terminal B determines that the target layer 1 address carried in the SCI carrying the shared COT indication information is equal to 16LSB of the intended receiving target layer 2 address/target layer 1 address, and the casttype indicated by the SCI carrying the shared COT indication information is multicast, and the responding terminal identifier indicated by the shared COT indication information is the same as the terminal identifier of terminal B, then terminal B can be determined to be the target terminal of the shared COT.
  • the response terminal identifier indicated by the shared COT indication information can be a response terminal layer 2 address or a response terminal application layer address, or a response terminal member identifier (member ID).
  • the same as the terminal identifier of terminal B can mean that when the response terminal identifier indicated by the shared COT indication information is a response terminal layer 2 address, the response terminal layer 2 address can be the same as the layer 2 address of terminal B; or when the response terminal identifier indicated by the shared COT indication information is a response terminal application layer address, the response terminal application layer address is the same as the application layer address of terminal B; or when the response terminal identifier indicated by the shared COT indication information is a response terminal member identifier, the response terminal member identifier is the same as the member identifier of terminal B.
  • the response terminal identifier indicated by the shared COT indication information can also be implemented in other ways, which are not specifically limited in this embodiment.
  • the above-mentioned determination of whether the terminal device is a responding terminal of the shared COT based on the target address and service type indicated by the SCI carrying the shared COT indication information may further include: when the service type is a broadcast service and the SCI carrying the shared COT indication information is a broadcast service, the SCI carrying the shared COT indication information is a broadcast service.
  • the target address indicated by the SCI of the information is the address associated with the broadcast service (such as the layer 2 address associated with the broadcast service, etc.), and the response terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determining that the terminal device is the response terminal of the shared COT.
  • terminal C is determined to be the responding terminal of the shared COT.
  • terminal C determines that terminal C is the responding terminal of the shared COT by determining that the target layer 1 address carried in the SCI carrying the shared COT indication information is equal to the expected receiving target layer 2 address or 16LSB of the target layer 1 address, and the cast type indicated by the SCI is broadcast, and the responding terminal identifier indicated by the shared COT indication information is the same as the terminal identifier of terminal C.
  • the response terminal identifier indicated by the shared COT indication information can be the response terminal layer 2 address, or it can also be the response terminal application layer address.
  • the same as the terminal identifier of terminal C can mean that when the response terminal identifier indicated by the shared COT indication information is the response terminal layer 2 address, the response terminal layer 2 address is the same as the layer 2 address of terminal C; or when the response terminal identifier indicated by the shared COT indication information is the response terminal application layer address, the response terminal application layer address is the same as the application layer address of terminal C.
  • the response terminal identifier indicated by the shared COT indication information can also be implemented in other ways, which are not specifically limited in this embodiment.
  • the method of this embodiment may further include: the terminal device sends the first data packet using the shared COT, or sends the first data packet without using the shared COT.
  • the first data packet may be sent using the shared COT, or may not be sent using the shared COT, but may be sent using other resources.
  • the terminal device may choose to discard (drop) the sideline authorization (SL grant), or discard the first data packet, etc.
  • the process of the terminal device performing the first type of LBT in step 301 may specifically include: the terminal device performs the first type of LBT before sending the first data packet.
  • the terminal device performing type 1 LBT may mean that the terminal device performs type 1 LBT before sending the first data packet.
  • the terminal device has completed the LCP process before obtaining the shared COT indication information, when the data packet obtained through the LCP processing does not meet the usage conditions of the shared COT, a specific processing solution for the terminal device is provided, and the specific processing behavior of the terminal device is clarified to meet business needs.
  • Fig. 4 shows a flow chart of a communication processing method according to an embodiment of the present disclosure, which can be applied to a terminal device for execution, and as shown in Fig. 4, can include the following steps.
  • Step 401 After obtaining shared COT indication information, a first data packet is obtained through LCP processing, and when the first data packet does not meet the use conditions of the shared COT, the terminal device performs a first type of LBT.
  • the terminal device After obtaining the shared COT indication information, the terminal device assembles the data packet through the LCP process. If the assembled data packet does not meet the shared COT usage conditions, the terminal device executes type 1 LBT.
  • the terminal device may be a responding terminal of the shared COT. For example, the terminal device determines that it is a responding terminal of the shared COT, such as the terminal 12 shown in FIG1 .
  • the terminal device starts the LCP packet assembly process after obtaining the shared COT indication information, but the data packet (SL MAC PDU) assembled by the LCP process does not meet the use conditions of the shared COT.
  • the terminal device may choose not to use the shared COT according to actual needs, and the terminal device performs the first type of LBT.
  • the first data packet does not meet the use condition of the shared COT, including at least one of the following:
  • the CAPC of the first data packet is greater than the CAPC indicated in the shared COT indication information; d.
  • the target terminal receiving the first data packet is not the initiating terminal of the shared COT.
  • the responding terminal is restricted to use only this COT to send sidelink data to the initiating terminal of the shared COT, which may include but not be limited to PSSCH data or PSCCH data
  • the data packets grouped by LCP do not meet the shared COT usage conditions, which may include the following situations:
  • Case D the CACP of the data packet is greater than the CAPC indicated by the shared COT indication information; and/or, Case E: the target terminal receiving the data packet is not the initiating terminal of the shared COT.
  • the supporting responding terminal can use this COT to send sidelink data to other terminal devices other than the initiating terminal of the shared COT, which may include but not be limited to PSSCH data or PSCCH data
  • the data packets grouped by the LCP do not meet the use conditions of the shared COT, which may include the following situations:
  • Case F the CACP of the data packet is greater than the CAPC indicated by the shared COT indication information.
  • the method of this embodiment may further include: the terminal device sends the first data packet using the shared COT, or sends the first data packet without using the shared COT.
  • the first data packet may be sent using the shared COT, or may not be sent using the shared COT, but may be sent using other resources.
  • the terminal device may choose to discard the SL grant, or discard the first data packet, etc.
  • the process of the terminal device performing the first type of LBT in step 401 may specifically include: the terminal device performs the first type of LBT before sending the first data packet.
  • the terminal device performing type 1 LBT may mean that the terminal device performs type 1 LBT before sending the first data packet.
  • the terminal device executes type 1LBT.
  • This embodiment provides a specific processing solution for the terminal device and clarifies the specific processing behavior of the terminal device to meet business needs.
  • the method provided by the embodiment of the present disclosure is introduced from the perspective of the user equipment.
  • the user equipment 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.
  • One of the above functions may be executed in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • the present disclosure also provides a communication processing device. Since the communication processing device provided in the embodiment of the present disclosure corresponds to the communication processing methods provided in the above-mentioned embodiments, the implementation method of the communication processing method is also applicable to the communication processing device provided in this embodiment and will not be described in detail in this embodiment.
  • FIG5 is a schematic diagram of the structure of a communication processing device provided in an embodiment of the present disclosure, and the communication processing device can be used in a terminal device.
  • the apparatus may include: a processing module 51 configured to perform a first type of LBT when a first data packet does not meet the use conditions of a shared COT, wherein the first data packet is a data packet obtained by LCP processing.
  • the terminal device is a responding terminal of a shared COT.
  • the first data packet does not meet the use conditions of the shared COT, including at least one of the following:
  • the CAPC of the first data packet is greater than the CAPC indicated in the shared COT indication information; and the target terminal receiving the first data packet is not an initiating terminal of the shared COT.
  • the processing module 51 is further configured to determine whether the terminal device is a responding terminal of the shared COT based on a target address and a service type indicated by the SCI carrying the shared COT indication information.
  • the processing module 51 is specifically configured to, when the service type is a unicast service and the target address indicated by the SCI carrying the shared COT indication information is the address of the terminal device, determine that the terminal device is a responding terminal of the shared COT; or, when the service type is a multicast service and the target address indicated by the SCI carrying the shared COT indication information is an address associated with the multicast service, and the response terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determine that the terminal device is a responding terminal of the shared COT; or, when the service type is a broadcast service and the target address indicated by the SCI carrying the shared COT indication information is an address associated with the broadcast service, and the response terminal identifier indicated by the shared COT indication information is the same as the identifier of the terminal device, determine that the terminal device is a responding terminal of the shared COT.
  • the processing module 51 is further configured to enable the terminal device to send the first data packet using the shared COT, or to send the first data packet without using the shared COT.
  • the processing module 51 is further configured to cause the terminal device to perform the first type of LBT before sending the first data packet.
  • this embodiment provides a specific processing solution for the terminal device when the data packet obtained through LCP processing does not meet the use conditions of the shared COT, and clarifies the specific processing behavior of the terminal device to meet business needs.
  • FIG. 6 is a schematic diagram of the structure of a communication device 1300 provided in this embodiment.
  • 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 1207 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.
  • a transceiver circuit, an interface, or an interface circuit for implementing the receiving and sending functions They can be separated or integrated.
  • the above transceiver circuit, interface or interface circuit can be used for reading and writing code/data, or the above transceiver circuit, interface or interface circuit can be used for transmitting or transferring 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 1301, 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 embodiments.
  • the processor and transceiver described in the present disclosure may 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 may 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 disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 6.
  • 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 chip shown in Figure 7 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 disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.
  • This embodiment also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • 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 can be accessed by a computer 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.
  • magnetic media e.g., floppy disks, hard disks, tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks (SSD)
  • At least one in the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present disclosure.
  • 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

本公开提出了一种通信处理方法及装置，涉及通信技术领域。其中方法包括：当第一数据包不符合共享COT的使用条件时，终端设备执行第一类型的LBT，其中，所述第一数据包为通过LCP处理得到的数据包。通过应用本公开的技术方案，针对侧行链路通信，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。

Description

通信处理方法及装置 技术领域
本公开涉及通信技术领域，特别涉及一种通信处理方法及装置。
背景技术
为了支持终端设备与终端设备之间的直接通信，引入了侧行链路(sidelink，SL)通信方式。
目前，针对侧行链路通信，如果终端设备已经完成逻辑信道优先级(Logical Channel Prioritization，LCP)的处理过程，并且相应已经组好的数据包不符合共享信道占用时间(Channel occupancy time，COT)的使用条件，此时终端设备具体的处理行为需要确定，然而，目前尚缺乏这种通信处理方案。
发明内容
本公开提出了一种通信处理方法及装置，针对侧行链路通信，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
本公开的第一方面实施例提供了一种通信处理方法，可应用于终端设备执行，所述方法包括：当第一数据包不符合共享COT的使用条件时，所述终端设备执行第一类型的先听后说(Listen Before Talk，LBT)，其中，所述第一数据包为通过LCP处理得到的数据包。
在本公开的一些实施例中，所述终端设备为共享COT的响应终端。
在本公开的一些实施例中，所述第一数据包不符合共享COT的使用条件至少包括以下其中一项：
所述第一数据包的信道接入优先级(channelaccesspriorityclass，CAPC)大于共享COT指示信息中指示的CAPC；
接收所述第一数据包的目标终端不是共享COT的发起终端。
在本公开的一些实施例中，所述方法还包括：基于承载共享COT指示信息的侧行链路控制信息(Sidelink Control Information，SCI)指示的目标地址以及业务类型，确定所述终端设备是否为所述共享COT的响应终端。
在本公开的一些实施例中，所述基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定所述终端设备是否为所述共享COT的响应终端，包括：当所述业务类型为单播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述终端设备的地址，确定所述终端设备为所述共享COT的响应终端；或者，当所述业务类型为组播业务、且承载所述共享COT指示信息的SCI指示的目标地址为与所述组播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端；或者，当所述业务类型为广播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述广播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端。
在本公开的一些实施例中，所述方法还包括：所述终端设备使用所述共享COT发送所述第一数据包、或者不使用所述共享COT发送所述第一数据包。
在本公开的一些实施例中，所述终端设备执行第一类型的LBT，包括：所述终端设备在发送所述第一数据包之前执行所述第一类型的LBT。
本公开的第二方面提供了一种通信处理装置，应用于终端设备，所述装置包括：处理模块，被配置为当第一数据包不符合共享COT的使用条件时，执行第一类型的LBT，其中，所述第一数据包为通过LCP处理得到的数据包。
本公开的第三方面实施例提供了一种通信设备，该通信设备包括：收发器；存储器；处理器，分别与收发器及存储器连接，配置为通过执行存储器上的计算机可执行指令，控制收发器的无线信号收发，并能够实现如本公开第一方面实施例的方法。
本公开的第四方面实施例提供了一种计算机存储介质，其中，计算机存储介质存储有计算机可执行指令；计算机可执行指令被处理器执行后，能够实现如本公开第一方面实施例的方法。
本公开实施例提供了一种通信处理方法及装置，其中，当第一数据包不符合共享COT的使用条件时，终端设备执行第一类型的LBT，其中，该第一数据包为通过LCP处理得到的数据包，本实施例针对侧行链路通信，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
本公开附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为根据本公开实施例的一种示例的架构示意图；
图2为根据本公开实施例的一种通信处理方法的流程示意图；
图3为根据本公开实施例的一种通信处理方法的流程示意图；
图4为根据本公开实施例的一种通信处理方法的流程示意图；
图5为根据本公开实施例的一种通信处理装置的框图；
图6为根据本公开实施例的一种通信装置的结构示意图；
图7为本公开实施例提供的一种芯片的结构示意图。
具体实施方式
下面详细描述本公开的实施例，实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。需要说明的是，在不冲突的情况下，本公开的实施例及实施例中的特征可以相互组合。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下 文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
为了便于理解，首先介绍本实施例涉及的术语。
1、侧行链路(sidelink，SL)
终端设备与终端设备之间的通信接口称为PC-5接口。在PC-5接口上，终端设备与终端设备之间传输数据的链路称为侧行链路。根据发送端终端设备和接收端终端设备的对应关系，在侧行链路上可支持三种传输方式，包括：单播、组播和广播。发送端终端设备在物理侧行链路控制信道(Physical Sidelink Control Channel，PSCCH)上发送侧行链路控制信息(Sidelink Control Information，SCI)以及在物理侧行链路共享信道(Physical Sidelink Shared Channel，PSSCH)信道上发送第二阶段SCI，其中携带传输数据的资源位置以及源和目标标识等。对于混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)反馈使能的数据包，接收端终端设备在物理侧行链路反馈信道(Physical Sidelink Feedback Channel，PSFCH)上对PSSCH做HARQ-ACK反馈。
侧行链路通信有两种发送资源分配方式，一种是网络动态调度的方式(mode 1)，另一种是终端设备在网络广播的资源池中自主选择的方式(mode 2)。其中动态调度是网络根据终端设备的缓存数据上报，动态给终端设备分配侧行链路上的发送资源，而自主选择是终端设备自行在网络配置的资源池中随机选择发送资源。网络可以在一个带宽(Bandwidth Part，BWP)上给终端设备配置多个资源池。具体使用哪种分配方式是网络侧通过无线资源控制(Radio Resource Control，RRC)配置的。
2、先听后说(ListenBefore Talk，LBT)
LBT是一种避免信道接入冲突的技术。不同的终端设备通过LBT操作竞争获得共享的非授权(Unlicensed，或称免授权)的频谱资源。NR-U是3GPP在通信协议版本16(release16，R16)的一个立项，为运营商将非授权频谱完全融入5G网络提供了必要的技术。NR-U支持在未授权的频段进行上行和下行操作。在NR-U中，下行链路和上行链路的通道接入都依赖于LBT特性。无线设备或基站必须首先“感知”通信信道，在任何传输之前发现没有通信。LBT type包含type 1和type 2，type1是基于竞争窗口，由随机数决定信道监听的时长，直到随机数等于0，且信道空闲才算接入信道；type2是基于一段固定时间的监听信道，如25us，16us等。
3、共享COT(COT sharing)
共享COT是R18讨论的一个特性，允许做type 1LBT的终端设备抢占了COT共享给其他终端设备使用，但是对可以共享COT的终端设备有一定要求。其中，如图1所示，发起共享COT的终端设备称为共享COT的发起终端(COT initiating UE)11，使用共享COT的终端设备称为响应终端(responding UE)12。
4、逻辑信道优先级(Logical Channel Prioritization，LCP)
发送端媒体接入控制(media access control，MAC)层的复用功能将多个逻辑信道的数据装入一个传输信道，即将多个MAC服务数据单元(service data unit，SDU)复用到一个MAC包数据单元 (packetDataunit，PDU)内，通过物理层信道发送出去。当多个逻辑信道都有数据发送，且数据总量超过当前授权的传输能力时，就出现了应该让哪个逻辑信道优先发送的问题，称为LCP。目前LCP过程在选择目标(destination)的时候需要遵循如下规则：
条件1：如果SL非连续接收(discontinous reception，DRX)适用于目标终端/地址，那么侧行链路授权处于目标终端/地址的激活时间。
条件2：目标终端/地址在所有满足下列条件的逻辑信道和MAC CE中具有至少一个最高优先级的MAC CE或者逻辑信道。
具有待传的SL数据；
如果有任何逻辑信道有信道占用的调度频带(SBj)，SBj>0；
如果侧行链路授权是配置授权类型1，逻辑信道关联的sl-configuredGrantType1Allowed配置允许逻辑信道的MAC SDU在配置授权类型1上传输；
如果配置了允许使用的配置授权的列表，该列表包含了侧行链路授权关联的配置授权标识；
如果侧行链路授权没有关联的PSFCH资源，逻辑信道的HARQ属性是HARQ-disabled。
5、信道接入优先级(channelaccesspriorityclass，CAPC)
CAPC是LBT相关的一个参数。不同的CAPC会影响在竞争信道时候的优先级。CAPC取值越小表明优先级越高。终端设备确定一个MAC PDU的CAPC遵循如下准则：
如果该SL MAC PDU只包含SL MAC CE，该SL MAC PDU的CAPC是最高优先级(CAPC值最低)；
如果该SL MAC PDU包含侧行链路控制信道(sidelinkcontrolchannel SDU，SCCH SDU)，该SL MAC PDU的CAPC是最高优先级(CAPC值最低)；
如果该SL MAC PDU包含SL MAC SDU，该SL MAC PDU的CAPC是复用到这个传输块(Transport Block，TB)的逻辑信道关联的最低优先级的CAPC(CAPC是按逻辑信道配置的)不管该SL MAC PDU是否包含SL MAC CE。
目前侧行链路工作在非授权频谱(Sidelink-U)场景下，如果终端设备已经完成LCP的处理过程，并且相应已经组好的数据包不符合共享COT的使用条件，此时终端设备具体的处理行为需要确定，然而，目前尚缺乏这种通信处理方案。因此，本实施例提出了一种通信处理方法及装置，在Sidelink-U场景下，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
下面结合附图对本实施例所提供的通信处理方法及装置进行详细地介绍。
图2示出了根据本公开实施例的一种通信处理方法的流程示意图。该方法可应用于终端设备侧执行，终端设备可以称为终端(terminal)、用户设备(userequipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备也可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart  grid)中的无线终端设备、运输安全(transportationsafety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smarthome)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
如图2所示，本实施例方法可以包括以下步骤。
步骤201、当第一数据包不符合共享COT的使用条件时，终端设备执行第一类型的LBT。
其中，第一数据包为通过LCP处理得到的数据包。
第一类型的LBT可为上述type 1LBT(类型1的LBT)，即基于竞争窗口，由随机数决定信道监听的时长，直到随机数等于0，且信道空闲才算接入信道。
例如，终端设备已完成LCP过程，已经组好了数据包(第一数据包)，但是该数据包不符合共享COT的使用条件，此时终端设备执行type 1LBT。
本实施例在Sidelink-U场景下，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
图3示出了根据本公开实施例的一种通信处理方法的流程示意图。可应用于终端设备侧执行，如图3所示，可以包括以下步骤。
步骤301、在获取共享COT指示信息之前通过LCP处理得到第一数据包，并且该第一数据包不符合共享COT的使用条件时，终端设备执行第一类型的LBT。
例如，终端设备获取共享COT指示信息之前已经组好了数据包，但该数据包不符合共享COT的使用条件，在这种情况下，终端设备执行type 1LBT。
在一些示例中，终端设备可为共享COT的响应终端。例如，终端设备确定自己是共享COT的响应终端，如图1所示的终端12，该终端设备在获取共享COT指示信息之前已经完成了LCP过程，即已经有生成的SL MAC PDU，但是该SL MAC PDU不符合共享COT的使用条件，在这种情况下，终端设备执行type 1LBT。
在一些示例中，第一数据包不符合共享COT的使用条件至少包括以下其中一项：
a、第一数据包的CAPC大于共享COT指示信息中指示的CAPC；b、接收第一数据包的目标终端不是共享COT的发起终端。
例如，如果限制响应终端只能使用这个COT给共享COT的发起终端发送侧行链路数据，可包括但不限定为物理直连共享信道(Physical Sidelink Control Channel，PSSCH)数据或者物理直连控制信道(Physical Sidelink Control Channel，PSCCH)数据，通过LCP所组的数据包不满足共享COT的使用条件可包含如下几个情况：
情况A、该数据包的CACP大于该共享COT指示信息指示的CAPC；和/或，情况B、接收该数据包的目标终端不是该共享COT的发起终端。
再例如，如果支持响应终端可以用这个COT给除了共享COT的发起终端以外的其他终端设备发送侧行链路数据，可包括但不限定为PSSCH数据或者PSCCH数据，通过LCP所组的数据包不满足共享COT的使用条件可包含如下情况：
情况C、该数据包的CACP大于该共享COT指示信息中指示的CAPC。
在一些示例中，终端设备需要确定自己是否是共享COT的响应终端，相应的，本实施例方法还可包括：基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定终端设备是否为共享COT的响应终端。如果终端设备为共享COT的响应终端，即确定自己是共享COT的响应终端，并且终端设备在获取共享COT指示信息之前已经完成了LCP过程，但是组好的数据包不符合共享COT的使用条件，在这种情况下，终端设备执行type 1LBT。
为了说明上述确定过程，在一些示例中，上述基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定终端设备是否为共享COT的响应终端，具体可包括：当业务类型为单播业务、且承载共享COT指示信息的SCI指示的目标地址为终端设备的地址(如终端设备的层2地址等)，确定终端设备为共享COT的响应终端。
例如，终端设备和共享COT的发起终端存在单播连接，承载该共享COT指示信息的数据包(SL MAC PDU)的目标地址是该终端设备的层2地址，在这种情况下，终端设备可确定自己是共享COT的响应终端。如响应于终端A与共享COT的发起终端之间进行单播业务，且承载共享COT指示信息的SCI指示的目标地址为终端A的层2地址，确定终端A为共享COT的响应终端。具体的，响应于终端A通过确定承载共享COT指示信息的SCI里携带的源层1地址(Source Layer-1ID)等于共享COT的发起终端的层2地址的8最低有效位(Least Significant Bit，LSB)，并且承载该共享COT指示信息的SCI里携带的目标层1地址(Destination Layer-1ID)等于终端A的层2地址的16LSB，且承载共享COT指示信息的SCI指示的casttype是单播，则确定终端A为共享COT的响应终端。
在一些示例中，上述基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定终端设备是否为共享COT的响应终端，具体还可包括：当业务类型为组播业务、且承载共享COT指示信息的SCI指示的目标地址为与该组播业务关联的地址(如该组播业务关联的层2地址等)、且共享COT指示信息指示的响应终端标识与终端设备的标识相同，确定终端设备为共享COT的响应终端。
例如，响应于终端B与共享COT的发起终端之间进行组播业务，且承载共享COT指示信息的SCI指示的目标地址为组播业务关联的层2地址，且共享COT指示信息指示的响应终端标识与该终端B的终端标识相同，确定终端B为共享COT的响应终端。具体的，终端B通过确定承载共享COT指示信息的SCI里携带的目标层1地址等于预期接收(intended)目标层2地址/目标层1地址的16LSB，且承载该共享COT指示信息的SCI指示的casttype是组播，且该共享COT指示信息指示的响应终端标识与终端B的终端标识相同，则可确定终端B为共享COT的目标终端。
需要说明的是，上述预期接收目标层2地址可与组播业务关联。共享COT指示信息指示的响应终端标识可以是响应终端层2地址也可以是响应终端应用层地址，还可以是响应终端成员标识(member ID)，与终端B的终端标识相同可以指当共享COT指示信息指示的响应终端标识是响应终端层2地址时，该响应终端层2地址可与终端B的层2地址相同；或者当共享COT指示信息指示的响应终端标识是响应终端应用层地址时，该响应终端应用层地址与终端B的应用层地址相同；或者当共享COT指示信息指示的响应终端标识是响应终端成员标识，该响应终端成员标识与终端B的成员标识相同。在一些示例中，共享COT指示信息指示的响应终端标识还可以有其他的实现方式，本实施例不做具体限定。
在一些示例中，上述基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定终端设备是否为共享COT的响应终端，具体还可包括：当该业务类型为广播业务、且承载该共享COT指示 信息的SCI指示的目标地址为该广播业务关联的地址(如该广播业务关联的层2地址等)、且该共享COT指示信息指示的响应终端标识与终端设备的标识相同，确定该终端设备为共享COT的响应终端。
例如，响应于终端C与共享COT的发起终端之间进行广播业务，且承载共享COT指示信息的SCI指示的目标地址为广播业务关联的层2地址，并且共享COT指示信息指示的响应终端标识与终端C的终端标识相同，确定终端C为共享COT的响应终端。具体地，终端C通过确定承载共享COT指示信息的SCI里携带的目标层1地址等于预期接收目标层2地址或者目标层1地址的16LSB，且SCI指示的cast type是广播，且该共享COT指示信息指示的响应终端标识与终端C的终端标识相同，确定终端C为共享COT的响应终端。
需要说明的是，上述预期接收目标层2地址可与该广播业务关联，该广播业务可以是终端C感兴趣接收的广播业务。共享COT指示信息指示的响应终端标识可以是响应终端层2地址，或者也可以是响应终端应用层地址。与终端C的终端标识相同可以指当共享COT指示信息指示的响应终端标识是响应终端层2地址时，该响应终端层2地址与终端C的层2地址相同；或者当共享COT指示信息指示的响应终端标识是响应终端应用层地址时，该响应终端应用层地址与终端C的应用层地址相同。在一些示例中，共享COT指示信息指示的响应终端标识还可以有其他的实现方式，本实施例不做具体限定。
在一些示例中，本实施例方法还可包括：终端设备使用共享COT发送第一数据包、或者不使用共享COT发送第一数据包。例如，第一数据包可使用共享COT发送，或者也可以不使用该共享COT发送，而使用其他资源发送该第一数据包。可选的，终端设备在确定通过LCP所组的第一数据包不符合共享COT的使用条件时，可以选择丢弃(drop)该侧行授权(SL grant)，或者丢弃该第一数据包等。
在一些示例中，步骤301的终端设备执行第一类型的LBT的过程具体可包括：终端设备在发送第一数据包之前执行第一类型的LBT。例如，终端设备执行type 1LBT可以是指终端设备发送该第一数据包之前执行type 1LBT。
本实施例在Sidelink-U场景下，如果终端设备获取共享COT指示信息之前已完成LCP过程，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
图4示出了根据本公开实施例的一种通信处理方法的流程示意图。可应用于终端设备侧执行，如图4所示，可以包括以下步骤。
步骤401、在获取共享COT指示信息之后通过LCP处理得到第一数据包，并且该第一数据包不符合共享COT的使用条件时，终端设备执行第一类型的LBT。
例如，终端设备在获取共享COT指示信息后通过LCP过程进行组包，如果所组的该数据包不符合共享COT使用条件，则终端设备执行type 1LBT。
在一些示例中，终端设备可为共享COT的响应终端。例如，终端设备确定自己是共享COT的响应终端，如图1所示的终端12，该终端设备在获取共享COT指示信息之后才开始LCP组包过程，但是LCP过程所组的数据包(SL MAC PDU)不满足共享COT的使用条件。
在一些示例中，终端设备在获取共享COT指示信息之后，终端设备可以根据实际需求选择不使用该共享COT，终端设备执行第一类型的LBT。
在一些示例中，第一数据包不符合共享COT的使用条件至少包括以下其中一项：
c、第一数据包的CAPC大于共享COT指示信息中指示的CAPC；d、接收第一数据包的目标终端不是共享COT的发起终端。
例如，如果限制响应终端只能使用这个COT给共享COT的发起终端发送侧行链路数据，可包括但不限定为PSSCH数据或者PSCCH数据，通过LCP所组的数据包不满足共享COT使用条件可包含如下几个情况：
情况D、该数据包的CACP大于该共享COT指示信息指示的CAPC；和/或，情况E、接收该数据包的目标终端不是该共享COT的发起终端。
再例如，如果支持响应终端可以用这个COT给除了共享COT的发起终端以外的其他终端设备发送侧行链路数据，可包括但不限定为PSSCH数据或者PSCCH数据，通过LCP所组的数据包不满足共享COT的使用条件可包含如下情况：
情况F、该数据包的CACP大于该共享COT指示信息指示的CAPC。
在一些示例中，本实施例方法还可包括：终端设备使用共享COT发送第一数据包、或者不使用共享COT发送第一数据包。例如，第一数据包可使用共享COT发送，或者也可以不使用该共享COT发送，而使用其他资源发送该第一数据包。可选的，终端设备在确定通过LCP所组的第一数据包不符合共享COT的使用条件时，可以选择丢弃该SL grant，或者丢弃该第一数据包等。
在一些示例中，步骤401的终端设备执行第一类型的LBT的过程具体可包括：终端设备在发送第一数据包之前执行第一类型的LBT。例如，终端设备执行type 1LBT可以是指终端设备发送该第一数据包之前执行type 1LBT。
需要说明的是，对于图4中具体实施例的内容可参见图3中实施例的对应描述，在此不再赘述。
本实施例在Sidelink-U场景下，如果终端设备获取共享COT指示信息之后完成LCP过程，当通过LCP处理得到的数据包不符合共享COT的使用条件时或者终端设备根据实际需求选择不适用这个共享COT进行数据包发送时，终端设备执行type 1LBT，本实施例提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
上述本公开提供的实施例中，从用户设备的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，用户设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
与上述几种实施例提供的通信处理方法相对应，本公开还提供一种通信处理装置，由于本公开实施例提供的通信处理装置与上述几种实施例提供的通信处理方法相对应，因此通信处理方法的实施方式也适用于本实施例提供的通信处理装置，在本实施例中不再详细描述。
图5为本公开实施例提供的一种通信处理装置的结构示意图，该通信处理装置可用于终端设备。
如图5所示，该装置可以包括：处理模块51，被配置为当第一数据包不符合共享COT的使用条件时，执行第一类型的LBT，其中，所述第一数据包为通过LCP处理得到的数据包。
在一些实施例中，所述终端设备为共享COT的响应终端。
在一些实施例中，所述第一数据包不符合共享COT的使用条件至少包括以下其中一项：
所述第一数据包的CAPC大于共享COT指示信息中指示的CAPC；接收所述第一数据包的目标终端不是共享COT的发起终端。
在一些实施例中，处理模块51，还被配置为基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定所述终端设备是否为所述共享COT的响应终端。
在一些实施例中，处理模块51，具体被配置为当所述业务类型为单播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述终端设备的地址，确定所述终端设备为所述共享COT的响应终端；或者，当所述业务类型为组播业务、且承载所述共享COT指示信息的SCI指示的目标地址为与所述组播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端；或者，当所述业务类型为广播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述广播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端。
在一些实施例中，处理模块51，还被配置为所述终端设备使用所述共享COT发送所述第一数据包、或者不使用所述共享COT发送所述第一数据包。
在一些实施例中，处理模块51，具体还被配置为所述终端设备在发送所述第一数据包之前执行所述第一类型的LBT。
本实施例在Sidelink-U场景下，当通过LCP处理得到的数据包不符合共享COT的使用条件时，提供了终端设备具体的处理方案，明确了终端设备具体的处理行为，以满足业务需求。
请参见图6，图6是本实施例提供的一种通信装置1300的结构示意图。通信装置1300可以是网络设备，也可以是用户设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持用户设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1300可以包括一个或多个处理器1301。处理器1301可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1300中还可以包括一个或多个存储器1302，其上可以存有计算机程序1304，处理器1301执行计算机程序1304，以使得通信装置1300执行上述方法实施例中描述的方法。可选的，存储器1302中还可以存储有数据。通信装置1300和存储器1302可以单独设置，也可以集成在一起。
可选的，通信装置1300还可以包括收发器1305、天线1306。收发器1305可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1305可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1300中还可以包括一个或多个接口电路1307。接口电路1207用于接收代码指令并传输至处理器1301。处理器1301运行代码指令以使通信装置1300执行上述方法实施例中描述的方法。
在一种实现方式中，处理器1301中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路 可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1301可以存有计算机程序1303，计算机程序1303在处理器1301上运行，可使得通信装置1300执行上述方法实施例中描述的方法。计算机程序1303可能固化在处理器1301中，该种情况下，处理器1301可能由硬件实现。
在一种实现方式中，通信装置1300可以包括电路，该电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者用户设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图6的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如该通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图7所示的芯片的结构示意图。图7所示的芯片包括处理器1401和接口1402。其中，处理器1401的数量可以是一个或多个，接口1402的数量可以是多个。
可选的，芯片还包括存储器1403，存储器1403用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本实施例还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行计算机程序时，全部或部分地产生按照本公开实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
如本文使用的，术语“机器可读介质”和“计算机可读介质”指的是用于将机器指令和/或数据提供给可编程处理器的任何计算机程序产品、设备、和/或装置(例如，磁盘、光盘、存储器、可编程逻辑装置(PLD))，包括，接收作为机器可读信号的机器指令的机器可读介质。术语“机器可读信号”指的是用于将机器指令和/或数据提供给可编程处理器的任何信号。
可以将此处描述的系统和技术实施在包括后台部件的计算系统(例如，作为数据服务器)、或者包括中间件部件的计算系统(例如，应用服务器)、或者包括前端部件的计算系统(例如，具有图形用户界面或者网络浏览器的用户计算机，用户可以通过该图形用户界面或者该网络浏览器来与此处描述的系统和技术的实施方式交互)、或者包括这种后台部件、中间件部件、或者前端部件的任何组合的计算系统中。可以通过任何形式或者介质的数字数据通信(例如，通信网络)来将系统的部件相互连接。通信网络的示例包括：局域网(LAN)、广域网(WAN)和互联网。
计算机系统可以包括客户端和服务器。客户端和服务器一般远离彼此并且通常通过通信网络进行交互。通过在相应的计算机上运行并且彼此具有客户端-服务器关系的计算机程序来产生客户端和服务器的关系。
应该理解，可以使用上面所示的各种形式的流程，重新排序、增加或删除步骤。例如，本公开中记载的各步骤可以并行地执行也可以顺序地执行也可以不同的次序执行，只要能够实现本公开申请的技术方案所期望的结果，本文在此不进行限制。
此外，应该理解，本公开所述的各种实施例可以单独实施，也可以在方案允许的情况下与其他实施例组合实施。
本领域普通技术人员可以意识到，结合本文中所申请的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行， 取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (10)

  1. 一种通信处理方法，其特征在于，所述方法包括：
    当第一数据包不符合共享信道占用时间COT的使用条件时，终端设备执行第一类型的先听后说LBT，其中，所述第一数据包为通过逻辑信道优先级LCP处理得到的数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备为共享COT的响应终端。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一数据包不符合共享COT的使用条件至少包括以下其中一项：
    所述第一数据包的信道接入优先级CAPC大于共享COT指示信息中指示的CAPC；
    接收所述第一数据包的目标终端不是共享COT的发起终端。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述方法还包括：
    基于承载共享COT指示信息的侧行链路控制信息SCI指示的目标地址以及业务类型，确定所述终端设备是否为所述共享COT的响应终端。
  5. 根据权利要求4所述的方法，其特征在于，所述基于承载共享COT指示信息的SCI指示的目标地址以及业务类型，确定所述终端设备是否为所述共享COT的响应终端，包括：
    当所述业务类型为单播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述终端设备的地址，确定所述终端设备为所述共享COT的响应终端；
    或者，
    当所述业务类型为组播业务、且承载所述共享COT指示信息的SCI指示的目标地址为与所述组播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端；
    或者，
    当所述业务类型为广播业务、且承载所述共享COT指示信息的SCI指示的目标地址为所述广播业务关联的地址、且所述共享COT指示信息指示的响应终端标识与所述终端设备的标识相同，确定所述终端设备为所述共享COT的响应终端。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备使用所述共享COT发送所述第一数据包、或者不使用所述共享COT发送所述第一数据包。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述终端设备执行第一类型的LBT，包括：
    所述终端设备在发送所述第一数据包之前执行所述第一类型的LBT。
  8. 一种通信处理装置，其特征在于，所述装置包括：
    处理模块，被配置为当第一数据包不符合共享信道占用时间COT的使用条件时，执行第一类型的先听后说LBT，其中，所述第一数据包为通过逻辑信道优先级LCP处理得到的数据包。
  9. 一种通信设备，其中，包括：收发器；存储器；处理器，分别与所述收发器及所述存储器连接，配置为通过执行所述存储器上的计算机可执行指令，控制所述收发器的无线信号收发，并能够实现权利要求1-7中任一项所述的方法。
  10. 一种计算机存储介质，其中，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被处理器执行后，能够实现权利要求1-7中任一项所述的方法。
PCT/CN2023/076614 2023-02-16 2023-02-16 通信处理方法及装置 WO2024168756A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076614 WO2024168756A1 (zh) 2023-02-16 2023-02-16 通信处理方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076614 WO2024168756A1 (zh) 2023-02-16 2023-02-16 通信处理方法及装置

Publications (1)

Publication Number Publication Date
WO2024168756A1 true WO2024168756A1 (zh) 2024-08-22

Family

ID=92421646

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076614 WO2024168756A1 (zh) 2023-02-16 2023-02-16 通信处理方法及装置

Country Status (1)

Country Link
WO (1) WO2024168756A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021257255A1 (en) * 2020-06-18 2021-12-23 Qualcomm Incorporated In-coverage network controlled off-loading over an unlicensed sidelink
CN114731528A (zh) * 2021-06-22 2022-07-08 上海诺基亚贝尔股份有限公司 共享信道占用时间的机制
CN115553024A (zh) * 2022-08-02 2022-12-30 北京小米移动软件有限公司 一种信道占用时间cot的共享方法及其装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021257255A1 (en) * 2020-06-18 2021-12-23 Qualcomm Incorporated In-coverage network controlled off-loading over an unlicensed sidelink
CN114731528A (zh) * 2021-06-22 2022-07-08 上海诺基亚贝尔股份有限公司 共享信道占用时间的机制
CN115553024A (zh) * 2022-08-02 2022-12-30 北京小米移动软件有限公司 一种信道占用时间cot的共享方法及其装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL, LENOVO: "CAPC for configured grant and dynamic grant", 3GPP DRAFT; R2-1913290 CAPC FOR CONFIGURED GRANT AND DYNAMIC GRANT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, China; 20191014 - 20191018, 3 October 2019 (2019-10-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051791300 *
NOKIA, NOKIA SHANGHAI BELL: "CAPC for dynamic grant with COT sharing", 3GPP DRAFT; R2-1910094 CAPC FOR DYNAMIC GRANT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051767879 *

Similar Documents

Publication Publication Date Title
JP7169499B2 (ja) キャリア集合の決定方法およびデバイス、記憶媒体、および電子デバイス
WO2024026701A1 (zh) 一种信道占用时间cot的共享方法及其装置
WO2024092772A1 (zh) 侧行链路sl通信方法及装置
JP7083854B2 (ja) データ複製をサポートする方法、送信側デバイスおよび受信側デバイス
WO2024168756A1 (zh) 通信处理方法及装置
WO2024000180A1 (zh) 一种指示方法、装置、设备及存储介质
WO2024197934A1 (zh) 一种非授权频谱的侧行链路sl的通信方法及其装置
WO2024187390A1 (zh) 一种侧行链路传输方法及其装置
WO2024138397A1 (zh) 一种侧行链路优先级的确定方法及其装置
CN118830321A (zh) 通信处理方法及装置
WO2024087123A1 (zh) 一种侧行链路连续先听后说失败的上报方法及装置
WO2024197950A1 (zh) 一种通信控制方法及其装置
WO2024168752A1 (zh) 一种组播通信方法及其装置
WO2024092711A1 (zh) 一种信道接入优先级capc的确定方法、配置方法及其装置
WO2024197931A1 (zh) 侧行链路数据无线承载drb配置方法及装置
WO2024197949A1 (zh) 一种通信控制方法及其装置
WO2024087026A1 (zh) 一种侧行链路连续先听后说失败的处理方法及装置
WO2024207527A1 (zh) 多路径通信方法及装置
WO2024138564A1 (zh) 一种服务质量分配方法及其装置
WO2024130562A1 (zh) 一种侧行链路通信方法、装置、设备及存储介质
WO2024197932A1 (zh) 一种辅助信息交互方法及其装置
WO2024148626A1 (zh) 一种终端标识确定方法/装置/设备及存储介质
WO2024138396A1 (zh) 非授权频谱中侧行链路的无线链路失败检测方法及其装置
WO2024016244A1 (zh) 支持非激活态组播业务接收的配置方法及装置
WO2024065452A1 (zh) 多路径通信方法、装置及系统

Legal Events

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

Ref document number: 23921910

Country of ref document: EP

Kind code of ref document: A1