WO2022082800A1 - 处理侧行链路进程的方法及装置 - Google Patents

处理侧行链路进程的方法及装置 Download PDF

Info

Publication number
WO2022082800A1
WO2022082800A1 PCT/CN2020/123450 CN2020123450W WO2022082800A1 WO 2022082800 A1 WO2022082800 A1 WO 2022082800A1 CN 2020123450 W CN2020123450 W CN 2020123450W WO 2022082800 A1 WO2022082800 A1 WO 2022082800A1
Authority
WO
WIPO (PCT)
Prior art keywords
sidelink
terminal
sidelink process
configuration mode
data
Prior art date
Application number
PCT/CN2020/123450
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/CN2020/123450 priority Critical patent/WO2022082800A1/zh
Priority to CN202080102952.8A priority patent/CN115868200A/zh
Priority to EP20958382.2A priority patent/EP4224917A4/en
Priority to JP2023524641A priority patent/JP2023546482A/ja
Publication of WO2022082800A1 publication Critical patent/WO2022082800A1/zh
Priority to US18/304,842 priority patent/US20230262838A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for processing a sidelink (SL) process.
  • SL sidelink
  • V2X Vehicle to everything
  • the Internet of Vehicles generally refers to providing vehicle information through sensors mounted on the vehicle, vehicle terminals, etc. to achieve vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (vehicle to network). network, V2N) and vehicle-to-pedestrian (V2P) communication network.
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2N vehicle-to-network
  • V2P vehicle-to-pedestrian
  • V2X has the characteristics of wide application space, great industrial potential and strong social benefits. It is very important to promote the innovation and development of the automobile and information communication industries, build new models and new formats of automobile and transportation services, and promote unmanned driving, assisted driving, intelligent driving, and connected driving.
  • the innovation and application of technologies such as intelligent networked driving, autonomous driving, and car sharing, as well as the improvement of traffic efficiency and safety levels, are of great significance.
  • a communication link for direct communication between a terminal and other terminals may be called a sidelink (sidelink, SL) or a side link.
  • a hybrid automatic repeat request (HARQ) process on the SL may be referred to as an SL process.
  • HARQ hybrid automatic repeat request
  • Embodiments of the present application provide a method and apparatus for processing SL processes, so as to avoid the reduction in the number of available SL processes.
  • a method for processing a sidelink process including: the terminal determines to perform a MAC reset on an RRC connection of the sidelink; the terminal determines that the first sidelink process is not occupied; and /or, the terminal releases the association relationship associated with the first sidelink process; wherein, the first sidelink process is a sidelink process associated with the RRC connection.
  • the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL the first SL process can be determined to be unoccupied, so that these The SL process is used for receiving other data, avoiding the reduction of the number of available SL processes and increasing the rate of data reception.
  • the terminal determines to perform MAC reset on the RRC connection of the sidelink, including: the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection; the terminal resets the first sidelink process Determining that it is not occupied includes: the MAC entity of the terminal determines that the first sidelink process is not occupied; the terminal releases the association relationship associated with the first sidelink process, including: the MAC entity release of the terminal and the The association relationship of a sidelink process association.
  • the method before the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection, the method further includes: the upper layer of the RRC layer of the terminal requests to release the RRC connection.
  • the association relationship associated with the first sidelink process includes: an association relationship between the first sidelink process and the SCI, and/or, the first sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a method for processing a sidelink process including: the terminal determines to perform a MAC reset on an RRC connection of the sidelink; the terminal determines that the first sidelink process is not occupied; and /or, the terminal clears the cache of the first sidelink process; wherein, the first sidelink process is a sidelink process associated with the RRC connection.
  • the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL the first SL process can be determined to be unoccupied, so that these The SL process is used for sending other data, avoiding the reduction of the number of available SL processes and increasing the rate of data reception. By clearing the cache of the first SL process, the storage space can be released.
  • the terminal determines to perform MAC reset on the RRC connection of the sidelink, including: the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection; the terminal resets the first sidelink process Determining that it is not occupied includes: the MAC entity of the terminal determines that the first sidelink process is not occupied; the terminal clears the cache of the first sidelink process, including: the MAC entity of the terminal clears the first sidelink process The cache of the road process.
  • the method before the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection, the method further includes: the upper layer of the RRC layer of the terminal requests to release the RRC connection.
  • the method further includes: the terminal sends an SL RRC reconfiguration message, or the terminal sends an SL RRC reconfiguration message, and The terminal receives the SL RRC reconfiguration complete message; wherein, the SL RRC reconfiguration message includes an indication of the full configuration.
  • a method for processing a sidelink process including: the terminal releases the RRC connection of the sidelink; the terminal performs one or more of the following actions: the terminal determines the first sidelink process In order not to be occupied, the terminal releases the association relationship associated with the first sidelink process, and the terminal clears the cache of the first sidelink process; wherein, the first sidelink process is the sidelink associated with the RRC connection. road process.
  • the terminal releases the RRC connection of the SL when the terminal releases the RRC connection of the SL, the first SL process can be determined to be unoccupied, so that these SL processes can be used for sending other data, and the number of available SL processes can be prevented from being reduced. , which can improve the data reception rate.
  • the storage space By clearing the cache of the first SL process, the storage space can be released.
  • the association relationship associated with the first SL process the receiving terminal is prevented from erroneously clearing other data, and the reliability of data reception can be improved.
  • the terminal releases the RRC connection of the sidelink, including: the RRC layer of the terminal releases the RRC connection, or the upper layer of the RRC layer of the terminal requests to release the RRC connection;
  • the process is determined to be unoccupied, including: the MAC entity of the terminal determines that the first sidelink process is not occupied;
  • the terminal releases the association relationship associated with the first sidelink process, including: the MAC entity of the terminal releases and
  • the terminal clearing the cache of the first side link process includes: the MAC entity of the terminal clears the cache of the first side link process.
  • the method before the RRC layer of the terminal releases the RRC connection, the method further includes: an upper layer of the RRC layer of the terminal requests to release the RRC connection.
  • the association relationship associated with the first sidelink process includes: an association relationship between the first sidelink process and the SCI, and/or, the first sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a method for processing a sidelink process including: for a destination address, the terminal no longer sends or receives sidelink data; the terminal performs one or more of the following actions: the terminal sends the first The second side link process is determined to be unoccupied; the terminal releases the association relationship associated with the second side link process; the terminal clears the cache of the second side link process; wherein, the second side link process is associated with the second side link process.
  • the sidelink process associated with the destination address including: for a destination address, the terminal no longer sends or receives sidelink data; the terminal performs one or more of the following actions: the terminal sends the first The second side link process is determined to be unoccupied; the terminal releases the association relationship associated with the second side link process; the terminal clears the cache of the second side link process; wherein, the second side link process is associated with the second side link process.
  • the sidelink process associated with the destination address including: for a destination address, the terminal no longer sends or receives sidelink data; the terminal performs one or more of the following actions
  • the second SL process can be determined to be unoccupied when the terminal no longer sends or receives SL data for a destination address, so that these SL processes can be used for sending other data, Avoiding a reduction in the number of available SL processes can increase the rate at which data is received.
  • the storage space can be released.
  • the receiving terminal is prevented from erroneously clearing other data.
  • the terminal no longer sends or receives sidelink data, including: the transmission corresponding to the destination address is terminated, or the terminal does not need to send or receive sidelink data corresponding to the destination address.
  • the association relationship associated with the second sidelink process includes: an association relationship between the second sidelink process and the SCI, and/or, the second sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a method for processing a sidelink process including: for a destination address, the terminal determines to perform MAC reset; the terminal performs one or more of the following actions: the terminal resets the second sidelink The process is determined to be unoccupied; the terminal releases the association relationship associated with the second side link process; the terminal clears the cache of the second side link process; wherein, the second side link process is the side associated with the destination address. Link process.
  • the terminal performs MAC reset for a destination address it can be determined that the second SL process is not occupied, so that these SL processes can be used for sending other data and avoid the available data.
  • the number of SL processes is reduced, which can improve the rate of data reception.
  • By clearing the cache of the second SL process the storage space can be released.
  • the association relationship associated with the second SL process the receiving terminal is prevented from erroneously clearing other data, and the reliability of data reception can be improved.
  • the method before the terminal determines to perform MAC reset, the method further includes: for the destination address, the terminal no longer sends or receives sidelink data.
  • the association relationship associated with the second sidelink process includes: an association relationship between the second sidelink process and the SCI, and/or, the second sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a method for processing a sidelink process including: the terminal determines that the resource configuration mode is the first resource configuration mode; the terminal determines that the third sidelink process is not occupied, and/or, Clear the cache of the third side link process; wherein, the third side link process is a side link process associated with the second resource configuration mode.
  • the terminal determines that the resource configuration mode is the first resource configuration mode, since the second resource configuration mode and the first resource configuration mode cannot exist at the same time, the terminal will not use the resources of the second resource configuration mode.
  • these SL processes can be used for sending other data, the reduction of the number of available SL processes can be avoided, and the rate of data reception can be increased.
  • the storage space can be released.
  • the resources corresponding to the first resource configuration mode include configured sidelink authorization resources and/or dynamic sidelink authorization resources
  • the terminal determines the third sidelink process as is not occupied, and/or, before clearing the cache of the third sidelink process
  • the method further includes: the terminal acquires the configured sidelink authorization resource or the dynamic sidelink authorization resource, and/or, determining The number of unoccupied sidelink processes is less than or equal to the first threshold.
  • the resources corresponding to the first resource configuration mode include the selected sidelink resources
  • the terminal determines that the third sidelink process is not occupied, and/or clears the third sidelink process
  • the method further includes: the terminal determines the selected sidelink resource, and/or determines that the number of unoccupied sidelink processes is less than or equal to the first threshold.
  • the method before the terminal determines that the third sidelink process is not occupied, and/or before clearing the cache of the third sidelink process, the method further includes: for the second resource In configuration mode, the terminal determines to perform MAC reset.
  • the terminal determines that the third sidelink process is not occupied, and/or clears the cache of the third sidelink process, including: the terminal according to the third sidelink process One or more of the priority of the data associated with the process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, the third side One or more of the uplink processes are determined to be unoccupied, and/or the cache of one or more of the third sidelink processes is flushed.
  • frequent mode switching may occur. If the process is released immediately after the mode switching, it may cause serious packet loss, which may not meet the requirements for services with high priority, low latency requirements, and high reliability requirements. , this possible implementation can avoid this situation.
  • the method further includes: the terminal releases the sidelink resources corresponding to the second resource configuration mode and/or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode, so that Since these resources can be used by other terminals later, the resource utilization rate is improved.
  • a method for processing a sidelink process comprising: for the second resource configuration mode, the terminal determines to perform a MAC reset; the terminal determines that the third sidelink process is not occupied, and/ Or, clear the cache of the third sidelink process; wherein, the third sidelink process is a sidelink process associated with the second resource configuration mode.
  • the terminal performs MAC reset for the second resource configuration mode the third SL process can be determined to be unoccupied, so that these SL processes can be used for sending other data, avoiding available data. The number of SL processes is reduced, which can improve the rate of data reception. By clearing the cache of the third SL process, the storage space can be released.
  • the method before the terminal determines to perform MAC reset for the second resource configuration mode, the method further includes: the terminal determines that the resource configuration mode is the first resource configuration mode.
  • the terminal determines that the third sidelink process is not occupied, and/or clears the cache of the third sidelink process, including: the terminal according to the third sidelink process One or more of the priority of the data associated with the process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, the third side One or more of the uplink processes are determined to be unoccupied, and/or the cache of one or more of the third sidelink processes is flushed.
  • the method further includes: the terminal releasing the sidelink resources corresponding to the second resource configuration mode and/or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.
  • a method for releasing sidelink resources including: the terminal determines that the resource configuration mode is the first resource configuration mode; the terminal releases the sidelink resources corresponding to the second resource configuration mode and/or the The configuration corresponding to the sidelink resource corresponding to the second resource configuration mode.
  • the eighth aspect by releasing the SL resources associated with the second resource configuration mode and/or the configuration corresponding to the SL resources associated with the second resource configuration mode, these resources can be subsequently used by other terminals, thereby improving resource utilization.
  • an apparatus for processing a sidelink process comprising: a processing unit configured to: determine to perform a MAC reset on an RRC connection of the sidelink; determine that the first sidelink process is not occupied; and/or release the association relationship associated with the first sidelink process; wherein the first sidelink process is a sidelink process associated with the RRC connection.
  • the processing unit is specifically configured to: request at the upper layer of the MAC layer to perform MAC reset on the RRC connection; determine at the MAC entity that the first sidelink process is not occupied; at the MAC entity Release the association relationship associated with the first sidelink process.
  • the processing unit is further configured to: request release of the RRC connection at the upper layer of the RRC layer.
  • the association relationship associated with the first sidelink process includes: an association relationship between the first sidelink process and the SCI, and/or, the first sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • an apparatus for processing a sidelink process including: a processing unit configured to: determine to perform a MAC reset on an RRC connection of the sidelink; determine that the first sidelink process is not and/or, clear the cache of the first sidelink process; wherein, the first sidelink process is a sidelink process associated with the RRC connection.
  • the processing unit is specifically configured to: request at the upper layer of the MAC layer to perform MAC reset on the RRC connection; determine at the MAC entity that the first sidelink process is not occupied; at the MAC entity Clear the cache of the first sidelink process.
  • the processing unit is further configured to: request release of the RRC connection at the upper layer of the RRC layer.
  • the apparatus further includes a communication unit; the communication unit is configured to send the SL RRC reconfiguration message, or, send the SL RRC reconfiguration message, and the apparatus receives the SL RRC reconfiguration complete message; wherein , the SL RRC reconfiguration message includes an indication of the full configuration.
  • an apparatus for processing a sidelink process comprising: a processing unit configured to: release an RRC connection of the sidelink; perform one or more of the following actions: send the first sidelink The link process is determined to be unoccupied, the association relationship associated with the first side link process is released, and the cache of the first side link process is cleared; wherein, the first side link process is the side associated with the RRC connection Link process.
  • the processing unit is specifically configured to: release the RRC connection at the RRC layer, or request release of the RRC connection at the upper layer of the RRC layer; determine, at the MAC entity, that the first sidelink process has not been Occupy; release the association relationship associated with the first side link process at the MAC entity; clear the cache of the first side link process at the MAC entity.
  • the processing unit is further configured to: request release of the RRC connection at the upper layer of the RRC layer.
  • the association relationship associated with the first sidelink process includes: an association relationship between the first sidelink process and the SCI, and/or, the first sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a twelfth aspect provides an apparatus for processing a sidelink process, comprising: a processing unit configured to; for a destination address, no longer send or receive sidelink data; perform one or more of the following actions A: determine that the second side link process is not occupied; release the association relationship associated with the second side link process; clear the cache of the second side link process; wherein, the second side link process is the sidelink process associated with the destination address.
  • the sidelink data is no longer sent or received, including: the transmission corresponding to the destination address is terminated, or the sidelink data corresponding to the destination address does not need to be sent or received.
  • the association relationship associated with the second sidelink process includes: an association relationship between the second sidelink process and the SCI, and/or, the second sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a thirteenth aspect provides an apparatus for processing a sidelink process, comprising: a processing unit configured to: determine to perform MAC reset for a destination address; perform one or more of the following actions: The side link process is determined to be unoccupied; the association relationship associated with the second side link process is released; the cache of the second side link process is cleared; wherein, the second side link process is associated with the destination address sidelink process.
  • the processing unit is further configured to: for the destination address, no longer send or receive sidelink data.
  • the association relationship associated with the second sidelink process includes: an association relationship between the second sidelink process and the SCI, and/or, the second sidelink process An association relationship with one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.
  • a fourteenth aspect provides an apparatus for processing a sidelink process, comprising: a processing unit configured to: determine that a resource configuration mode is a first resource configuration mode; determine that a third sidelink process is not occupied , and/or, clearing the cache of the third sidelink process; wherein, the third sidelink process is a sidelink process associated with the second resource configuration mode.
  • the resources corresponding to the first resource configuration mode include configured sidelink authorization resources and/or dynamic sidelink authorization resources
  • the processing unit is further configured to: acquire the configured sidelink authorization resources. link grant resources or dynamic side link grant resources, and/or determine that the number of unoccupied side link processes is less than or equal to the first threshold.
  • the resources corresponding to the first resource configuration mode include selected sidelink resources
  • the processing unit is further configured to: determine the selected sidelink resources, and/or determine that they are not occupied The number of sidelink processes is less than or equal to the first threshold.
  • the processing unit is further configured to: determine to perform MAC reset for the second resource configuration mode.
  • the processing unit is specifically configured to: according to the priority of the data associated with the third side link process, the delay requirement of the data associated with the third side link process, and the third side link process one or more of the reliability requirements of the data associated with the three sidelink processes, determining one or more of the third sidelink processes as unoccupied, and/or, clearing the third sidelink process One or more caches in the process.
  • the processing unit is further configured to: release the sidelink resources corresponding to the second resource configuration mode and/or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.
  • a fifteenth aspect provides an apparatus for processing a sidelink process, including: a processing unit configured to: determine to perform a MAC reset for the second resource configuration mode; determine that the third sidelink process is not is occupied, and/or, the cache of the third sidelink process is cleared; wherein, the third sidelink process is a sidelink process associated with the second resource configuration mode.
  • the processing unit is further configured to: determine that the resource configuration mode is the first resource configuration mode.
  • the processing unit is specifically configured to: according to the priority of the data associated with the third side link process, the delay requirement of the data associated with the third side link process, and the third side link process one or more of the reliability requirements of the data associated with the three sidelink processes, determining one or more of the third sidelink processes as unoccupied, and/or, clearing the third sidelink process One or more caches in the process.
  • the processing unit is further configured to: release the sidelink resources corresponding to the second resource configuration mode and/or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.
  • a sixteenth aspect provides an apparatus for releasing sidelink resources, comprising: a processing unit configured to: determine that a resource configuration mode is a first resource configuration mode; release a sidelink corresponding to the second resource configuration mode resources and/or configurations corresponding to sidelink resources corresponding to the second resource configuration mode.
  • a seventeenth aspect provides an apparatus for processing a sidelink process, comprising: a processor.
  • the processor is connected to the memory, the memory is used for storing computer-executed instructions, and the processor executes the computer-executed instructions stored in the memory, thereby implementing any one of the methods provided in any one of the first to seventh aspects.
  • the memory and the processor may be integrated together, or may be independent devices. In the latter case, the memory may be located within the device that handles the sidelink process, or may be located outside the device that handles the sidelink process.
  • the processor includes a logic circuit, and also includes an input interface and/or an output interface.
  • the output interface is used for performing the sending action in the corresponding method
  • the input interface is used for performing the receiving action in the corresponding method.
  • the apparatus for processing the sidelink process further includes a communication interface and a communication bus, and the processor, the memory and the communication interface are connected through the communication bus.
  • the communication interface is used to perform the actions of transceiving in the corresponding method.
  • the communication interface may also be referred to as a transceiver.
  • the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is configured to perform the sending action in the corresponding method, and the receiver is configured to perform the receiving action in the corresponding method.
  • the device for processing the sidelink process exists in the form of a chip product.
  • An eighteenth aspect provides an apparatus for releasing sidelink resources, including: a processor.
  • the processor is connected to the memory, the memory is used for storing computer-executed instructions, and the processor executes the computer-executed instructions stored in the memory, thereby implementing the method provided in the eighth aspect.
  • the memory and the processor may be integrated together, or may be independent devices. In the latter case, the memory may be located in the apparatus for releasing sidelink resources, or may be located outside the apparatus for releasing sidelink resources.
  • the processor includes a logic circuit, and also includes an input interface and/or an output interface.
  • the output interface is used for performing the sending action in the corresponding method
  • the input interface is used for performing the receiving action in the corresponding method.
  • the apparatus for releasing sidelink resources further includes a communication interface and a communication bus, and the processor, the memory and the communication interface are connected through the communication bus.
  • the communication interface is used to perform the actions of transceiving in the corresponding method.
  • the communication interface may also be referred to as a transceiver.
  • the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is configured to perform the sending action in the corresponding method, and the receiver is configured to perform the receiving action in the corresponding method.
  • the device for releasing sidelink resources exists in the form of a chip product.
  • a nineteenth aspect provides an apparatus for processing a sidelink process, comprising: a processor and an interface, the processor is coupled to a memory through the interface, and when the processor executes a computer program or instructions in the memory, the first aspect is Any one of the methods provided by any one of the to seventh aspects is performed.
  • a twentieth aspect provides an apparatus for releasing sidelink resources, comprising: a processor and an interface, the processor is coupled to the memory through the interface, and when the processor executes the computer program or instructions in the memory, the eighth aspect The provided method is executed.
  • a twenty-first aspect provides a computer-readable storage medium, comprising computer-executable instructions, which, when the computer-executable instructions are run on a computer, cause the computer to execute any one of the first to eighth aspects. a way.
  • a twenty-second aspect provides a computer program product, comprising computer-executable instructions, which, when the computer-executable instructions are run on a computer, cause the computer to execute any one of the first to eighth aspects. method.
  • FIG. 1 is a schematic diagram of a communication scenario provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a sideline authorization provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a parallel HARQ process provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the association between an SCI and an SL process provided by an embodiment of the present application
  • FIG. 5 is a schematic diagram of a method for processing an SL process provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of releasing an association relationship associated with an SL process according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 10 is another schematic diagram of releasing an association relationship associated with an SL process provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram of another method for processing an SL process provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a method for releasing SL resources provided by an embodiment of the present application.
  • FIG. 15 is a schematic diagram of the composition of a terminal according to an embodiment of the present application.
  • FIG. 16 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of a hardware structure of another terminal according to an embodiment of the present application.
  • D2D device to device
  • V2X unmanned driving
  • ADS automatic driving
  • driver assistance driver assistance
  • ADAS intelligent driving
  • the network elements involved in this application include network equipment and terminals in a communication system.
  • the method provided by the embodiment of the present application mainly involves communication between terminals.
  • the communication systems in the embodiments of the present application include but are not limited to long term evolution (long term evolution, LTE) systems, fifth generation (5th-generation, 5G) systems, new radio (new radio, NR) systems, wireless local area networks (wireless local area networks) area networks, WLAN) systems and future evolution systems or various communication fusion systems.
  • the 5G system may be a non-standalone (NSA) 5G system or an independent (standalone, SA) 5G system.
  • the network device in this embodiment of the present application is an entity on the network side that is used for sending a signal, or receiving a signal, or sending a signal and receiving a signal.
  • the network equipment can be deployed in a wireless access network (radio access network,
  • a device in the RAN that provides a wireless communication function for a terminal, such as a transmission reception point (TRP), a base station, various forms of control nodes (for example, a network controller, a wireless controller (for example, a cloud wireless connection). wireless controller in the cloud radio access network (CRAN) scenario)) and so on.
  • the network device may be various forms of macro base station, micro base station (also referred to as small cell), relay station, access point (access point, AP), etc., and may also be the antenna panel of the base station.
  • the control node can be connected to multiple base stations, and configure resources for multiple terminals covered by the multiple base stations. In systems using different radio access technologies, the names of devices with base station functions may vary.
  • an LTE system may be called an evolved NodeB (eNB or eNodeB), and a 5G system or an NR system may be called a next generation node base station (gNB), the specific name of the base station in this application Not limited.
  • the network device may also be a network device in a future evolved public land mobile network (public land mobile network, PLMN).
  • PLMN public land mobile network
  • the terminal in this embodiment of the present application is an entity on the user side that is used to receive a signal, or send a signal, or receive a signal and send a signal.
  • the terminal is used to provide one or more of voice service and data connectivity service to the user.
  • a terminal may also be referred to as user equipment (UE), terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device.
  • UE user equipment
  • the terminal can be a V2X device, for example, smart car (smart car or intelligent car), digital car (digital car), unmanned car (unmanned car or driverless car or pilotless car or automobile), self-driving car (self-driving car or autonomous car) car), pure EV (pure EV or Battery EV), hybrid electric vehicle (HEV), range extended EV (REEV), plug-in HEV (PHEV) ), new energy vehicles (new energy vehicles), roadside units (road site units, RSU).
  • the terminal can also be a D2D device, such as an electricity meter, a water meter, and the like.
  • the terminal may also be a mobile station (mobile station, MS), a subscriber unit (subscriber unit), an unmanned aerial vehicle, an internet of things (IoT) device, a station (station, ST) in a WLAN, a cellular phone (cellular phone) ), smart phones (smart phones), cordless phones, wireless data cards, tablet computers, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital processing (personal digital processing) digital assistant (PDA) device, laptop computer (laptop computer), machine type communication (MTC) terminal, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device , wearable devices (also known as wearable smart devices).
  • the terminal may also be a terminal in a next-generation communication system, for example, a terminal in a 5G system or a terminal in a future evolved PLMN, a terminal in an NR system, and the like.
  • Uplink uplink (uplink, UL), downlink (downlink, DL), SL
  • the wireless communication link in which the terminal transmits data (ie, uplink data) to the network device may be referred to as UL.
  • the wireless communication link in which the network device transmits data (ie, downlink data) to the terminal may be referred to as DL.
  • the UL interface and the DL interface can be collectively referred to as a Uu interface, and therefore, the UL and DL can be collectively referred to as a Uu interface link.
  • the communication link for direct communication between terminals may be referred to as SL.
  • SLs can also be called side links.
  • Data transmitted between terminals may be referred to as SL data.
  • the data in the embodiments of the present application may be understood as a transport block (transport block, TB) or a medium access control (medium access control, MAC) protocol data unit (protocol data unit, PDU).
  • Transport block transport block
  • MAC medium access control
  • PDU protocol data unit
  • the SL transmission resource used by the sending terminal in the two terminals may be determined by any one of the following methods A and B.
  • the mode in which the network device schedules the SL transmission resources may include a mode 1 (mode1) resource configuration mode (name in NR) or a mode 3 (mode3) resource configuration mode (name in LTE).
  • mode1 mode 1
  • mode3 mode 3 resource configuration mode
  • the SL transmission resources scheduled by the network device are of the following two types:
  • each data transmission of the sending terminal does not always require the network device to allocate resources separately.
  • the sending terminal can use the above allocated resources for a certain period of time. It is "assign once, use many times".
  • the network device may configure a period of periodically occurring time domain resources for the sending terminal.
  • the time domain resources that appear periodically in this segment are symbols 4 to 9 of time slot 1, and the period is one time slot.
  • the time domain resource that appears each time is the authorization of one SL (SL grant, hereinafter referred to as the sideline authorization), then it can be understood that four sideline authorizations are shown in FIG. 2, and 1 sideline authorization is shown.
  • the sideline authorization IDs corresponding to the four sideline authorizations are sideline authorization 0, sideline authorization 1, sideline authorization 2, and sideline authorization 3 respectively.
  • SL CG resources may include SL type 1 (type1) CG (SL configured grant type 1) resources, and SL type 2 (type2) CG (SL configured grant type 2) resources.
  • the SL type1CG resource may be an SL transmission resource that is directly configured by the network device to the sending terminal through radio resource control (RRC) signaling, and the sending terminal can directly use the CG resource to transmit data without additional activation.
  • SL type1CG resources can also be called SL grant free resources.
  • the SL type2CG resource can be the period in which the network device defines the SL transmission resource through RRC signaling, and then activates the SL transmission resource through the physical downlink control channel (physical downlink control channel, PDCCH) or downlink control information (downlink control information, DCI). The terminal cannot directly use the SL transmission resource to transmit data, and can only be used after activation.
  • SL type2CG resources may also be called SL semi-persistent scheduling (SL Semi-Persistent Scheduling, SL SPS) resources.
  • one or more CG resources may be supported on one carrier.
  • different SL CG resources may correspond to different indexes.
  • the CG resources with indexes 1, 2, and 3 may be denoted as SL CG1, SL CG2, and SL CG3, respectively.
  • the second type SL dynamic grant (DG) resource
  • DCI may be carried in PDCCH.
  • Method B The sending terminal determines by itself
  • the mode in which the sending terminal determines the SL transmission resource by itself may include a mode 2 (mode2) resource configuration mode (name in NR) or a mode 4 (mode4) resource configuration mode (name in LTE).
  • mode2 mode 2
  • mode4 mode 4
  • the network device can configure the SL resource pool for the sending terminal through a system broadcast (system information block, SIB) message or dedicated RRC signaling, and the sending terminal can autonomously use the SL resource SL transmission resources are acquired in the pool to send control signals and/or data signals to the receiving terminal.
  • SIB system information block
  • the sending terminal can autonomously acquire SL transmission resources from a preconfigured SL resource pool to send control signals and/or data signals to the receiving terminal.
  • the sending terminal may perceive or compete for the SL transmission resource. Specifically, the sending terminal transmits the control signal and/or the data signal by competing with other terminals to obtain suitable SL transmission resources in the SL resource pool. For example, the higher the priority of the V2X service or data to be transmitted in the sending terminal, the greater the chance of competing for suitable SL transmission resources in the SL resource pool.
  • mode1 resource configuration mode For convenience of description, this application abbreviated mode1 resource configuration mode, mode2 resource configuration mode, mode3 resource configuration mode, and mode4 resource configuration mode as mode1, mode2, mode3, and mode4, respectively.
  • LTE V2X mode3 and mode4 cannot exist at the same time.
  • NR V2X mode1 and mode2 cannot exist at the same time.
  • SCI is used for scheduling SL data.
  • the control information of the SL data can be carried in the first-level SCI.
  • the SCI may be transmitted on the physical sidelink control channel (PSCCH).
  • PSCCH physical sidelink control channel
  • HARQ is a technology that combines forward error correction (or forward error correction code) (forward error correction, FEC) and automatic repeat request (automatic repeat request, ARQ) methods.
  • FEC forward error correction code
  • ARQ automatic repeat request
  • FEC means that the data sent by the sender includes forward error correction codes or redundant information.
  • the receiver receives the data, it passes a check (for example, cyclic redundancy check (CRC)) ) After an error is found, it can be corrected by forward error correction code or redundant information, so that the sender can reduce the number of retransmissions (ie, retransmit data).
  • CRC cyclic redundancy check
  • ARQ means that the receiving end judges the correctness of the received data by checking (for example, CRC check). If the data is received correctly, the receiving end sends an acknowledgement (ACK) to inform the sending end, otherwise the receiving end sends a negative acknowledgment (negative acknowledgement, NACK) informs the sender that when the sender receives a NACK, it can retransmit the data to the receiver.
  • ACK and NACK are HARQ feedback.
  • the content related to HARQ will be specifically introduced through the following three parts (a) to (c).
  • HARQ uses the stop-and-wait protocol to send data.
  • the stop-and-wait protocol after the sender sends a transport block (TB), it stops and waits for an acknowledgment.
  • the receiver can feed back ACK or NACK for the TB.
  • the sender stops and waits for an acknowledgment after each transmission, resulting in very low throughput. Therefore, the sender can use multiple parallel HARQ processes: while one HARQ process is waiting for an acknowledgment, the sender can use another HARQ process to continue sending data. Exemplarily, referring to FIG.
  • the terminal uses the first HARQ process to send TB1, finishes sending TB1 at time T1, receives HARQ feedback of TB1 at time T2, and waits for the confirmation of TB1 during the time period from T1 to T2, and then
  • the second HARQ process can be used to send TB2, send TB2 at time T2, receive the HARQ feedback of TB2 at time T3, and wait for the confirmation of TB2 during the time period from T2 to T3.
  • the third HARQ process can be used to send TB3.
  • a HARQ process is identified by a HARQ process ID.
  • the sideline authorization is associated with the HARQ process, and the terminal uses the process to transmit HARQ data in the sideline authorization associated with the HARQ process.
  • Each HARQ process has a corresponding buffer (for example, HARQ buffer or soft buffer) at the receiving end, so as to perform soft combining and decoding on the received data.
  • a corresponding buffer for example, HARQ buffer or soft buffer
  • the receiving end may put the received newly transmitted data into a buffer corresponding to the HARQ process for decoding. If the decoding fails, when the retransmitted data of the newly transmitted data is received again, the received retransmitted data can be combined with the newly transmitted data previously stored in the cache, put into the cache, and decoded again. This is called soft combining decoding, which improves the probability of successful decoding compared to separate decoding (that is, the data transmitted each time is decoded separately, and is not combined with the previous data for decoding). Likewise, if the decoding still fails, the above process can be repeated continuously, the newly received retransmission data is combined with the data in the buffer, and the decoding is performed again.
  • the retransmitted data and the newly transmitted data of the sender may be the same redundancy version (redundancy version, RV) of the same TB or different RVs.
  • RV redundancy version
  • the HARQ process on the Uu interface is called the HARQ process
  • the HARQ process on the SL can be called the SL process (SL process).
  • One sending terminal can communicate with multiple receiving terminals, that is, one sending terminal can send SCI and SL data to multiple receiving terminals.
  • One receiving terminal can also communicate with multiple sending terminals, that is, one receiving terminal can receive SCI and SL data from multiple sending terminals.
  • the SCI may contain the SL process ID, the first destination ID (destination ID), the first source ID (source ID), and the communication type.
  • the SL process ID is used to identify the SL process, which is similar to the HARQ process ID of the Uu interface.
  • the first target ID may be used to identify the target of the SL data scheduled by the SCI.
  • the first destination ID may be used for packet filtering performed by the PHY layer of the receiving terminal.
  • the first destination ID may be a part of the bits of the second destination ID.
  • the second destination ID is 24 bits, and the first destination ID is the lower 16 bits of the second destination ID.
  • the second destination ID is used to identify the destination (eg, target)/receiving end/receiving terminal of the data.
  • the second destination ID is used to identify a multicast or broadcast service.
  • the second destination ID may be an identifier of a destination/receiving end/receiving terminal.
  • the second destination ID may be a destination layer-2 ID (Destination Layer-2 ID).
  • the second destination ID may be used for packet filtering performed by the MAC layer of the receiving terminal.
  • the first source ID is used to identify the source (source) of the SL data scheduled by the SCI.
  • the first source ID may be used for packet filtering performed by the PHY layer of the receiving terminal.
  • the first source ID may be a part of the bits of the second source ID.
  • the second source ID is 24 bits, and the first source ID is the lower 8 bits of the second source ID.
  • the second source ID is used to identify the source (eg, sender)/sending end/sending terminal of the data.
  • the second source ID may be an identifier of a source/sending end/sending terminal.
  • the second source ID may be a source layer-2 ID (source Layer-2 ID).
  • the second source ID may be used for packet filtering performed by the MAC layer of the receiving terminal.
  • Communication types may include any one or more of unicast, multicast, and broadcast.
  • the communication type in the SCI is used to indicate whether the current communication is unicast, multicast or broadcast, or used to indicate whether the SL data scheduled by the SCI is unicast data, multicast data or broadcast data.
  • the receiving terminal can detect the surrounding SCI, and then determine whether the SCI or the SL data scheduled by the SCI is of interest to it according to the first destination ID, the first source ID and the communication type in the SCI. If interested, continue to receive SL data scheduled by SCI.
  • one SL HARQ entity On the sending side, one SL HARQ entity is included, and all SL processes (eg, 16) maintained by this SL HARQ entity are shared by all connection/communication types (casttypes). On the receiving side, one SL HARQ entity is included, and all SL processes (eg, 64) maintained by this SL HARQ entity are shared by all connection/communication types.
  • Different sending terminals may use the same SL process ID to communicate with the same receiving terminal.
  • the receiving terminal receives an SCI. And/or data, after judging that the data is newly transmitted data, an unoccupied SL process (denoted as SL process 1) will be selected for the data, and the "SL process ID+first destination ID+first source" in the SCI will be selected.
  • ID + Communication Type" is associated with SL Process 1.
  • first destination ID+first source ID+communication type may be referred to as SL identification information (sidelink identification information).
  • the terminal determines to perform a MAC reset (for example, the upper layer of the MAC layer of the terminal requests a MAC reset), and the MAC entity of the terminal will perform any one or more of the following: stop the running timer, cancel the triggered beam failure Recovery (beam failure recovery, BFR), cancel triggered scheduling request (SR), reset MAC-related counters (eg, LBT_COUNTER, BFI_COUNTER, etc.), stop ongoing random access procedures, etc.
  • a MAC reset for example, the upper layer of the MAC layer of the terminal requests a MAC reset
  • stop the running timer cancel the triggered beam failure Recovery (beam failure recovery, BFR), cancel triggered scheduling request (SR), reset MAC-related counters (eg, LBT_COUNTER, BFI_COUNTER, etc.), stop ongoing random access procedures, etc.
  • BFR beam failure recovery
  • SR cancel triggered scheduling request
  • reset MAC-related counters eg, LBT_COUNTER, BFI_COUNTER,
  • the MAC entity of the terminal will perform any one or more of the following: cancel the trigger The SR that is only associated with the RRC connection of the SL, cancels the triggered SL BSR that is only associated with the RRC connection of the SL, and clears the soft buffer of the SL process associated with the RRC connection of the SL.
  • cancel the trigger The SR that is only associated with the RRC connection of the SL
  • cancels the triggered SL BSR that is only associated with the RRC connection of the SL
  • clears the soft buffer of the SL process associated with the RRC connection of the SL please refer to Section 5.12 of TS 38.321, which will not be repeated here.
  • an SL radio link failure occurs, or, if the MAC layer of the receiving terminal receives a full-configured SL RRC reconfiguration (RRCReconfigurationSidelink) message, the receiving terminal A MAC reset is performed for the RRC connection of this SL.
  • the fully configured SL RRC reconfiguration message can be understood as: the SL RRC reconfiguration message includes an indication of the full configuration.
  • the indication of the full configuration is used to indicate that the SL RRC reconfiguration message should adopt the full configuration.
  • the indication of full configuration is "sl-ResetConfig".
  • the SL RRC reconfiguration message of the full configuration indicates that: for the RRC connection of one SL, all reconfigurations are performed on the receiving terminal, that is, for the RRC connection of the SL, all configurations are updated.
  • the sending terminal sends the SL configuration to the receiving terminal through the SL RRC reconfiguration message.
  • the parameter "sl-ResetConfig" is included in the SL RRC reconfiguration message, it means that all SLs are configured for the SL.
  • the receiving terminal regards the SL process as not being occupied in the following two situations:
  • the receiving terminal decodes the data successfully, and the SL process corresponding to the data is regarded as unoccupied.
  • the receiving terminal receives the same "SL process ID+first destination ID+first source ID+communication type" correspondingly to schedule the SCI or newly transmitted SL data, and the "SL process ID+first destination ID+first source”
  • the SL process corresponding to ID+communication type" is regarded as unoccupied.
  • the receiving terminal determines whether "SL process ID+first destination ID+first source ID+communication type" in an SCI that schedules newly transmitted SL data is associated with an SL process (referred to as SL process 2).
  • SL process 2 is regarded as unoccupied, and the cache of SL process 2 is cleared, and an unoccupied SL process (referred to as SL process 3) is selected for the SCI that schedules the newly transmitted SL data or the newly transmitted data.
  • SL process 3 associate the SL process 3 with "SL process ID+first destination ID+first source ID+communication type" in the SCI.
  • the receiving terminal performs an SL MAC reset, and the receiving terminal clears the caches of all SL processes associated with the RRC connection of the SL.
  • the receiving terminal occurs when event 1 (the receiving terminal determines to perform MAC reset for the RRC connection of the SL or the receiving terminal performs the MAC reset for the RRC connection of the SL), event 2 (the RRC connection of the SL is released) and event 3 ( When the receiving terminal no longer receives multicast and/or broadcast data), the association between the SCI (or "SL process ID+first destination ID+first source ID+communication type") and the SL process is not released, nor is the SL process released. Processes are considered unoccupied.
  • event 1 the receiving terminal determines to perform MAC reset for the RRC connection of the SL or the receiving terminal performs the MAC reset for the RRC connection of the SL
  • event 2 the RRC connection of the SL is released
  • event 3 When the receiving terminal no longer receives multicast and/or broadcast data), the association between the SCI (or "SL process ID+first destination ID+first source ID+communication type") and the SL process is not released, nor is the SL process released. Processes are considered unoccupied
  • the receiving terminal receives the SCI again (including the "SL process ID + the first destination ID + the first source For newly transmitted SL data scheduled by the same SCI with the same ID+communication type as the previous SCI), due to the existence of the association between the SCI and the SL process, the receiving terminal may mistakenly clear other data in the cache of the SL process.
  • the SCI again (including the "SL process ID + the first destination ID + the first source For newly transmitted SL data scheduled by the same SCI with the same ID+communication type as the previous SCI)
  • the receiving terminal may mistakenly clear other data in the cache of the SL process.
  • the receiving terminal receives SCI1 (including “SL process ID1 + first destination ID1 + first source ID1 + unicast”), SCI1 is used to schedule newly transmitted data 1, and after receiving SCI1, the receiving terminal will "SL process ID1 + first destination ID1 + first source ID1 + unicast" is associated with SL process 1 .
  • the receiving terminal performs MAC reset for the RRC connection of the SL, it determines that the SL process 1 associated with the RRC connection of the SL is not occupied, but does not release "SL process ID1 + first destination ID1 + first source ID1 + The association between "unicast” and SL process 1.
  • SCI2 (including “SL process ID2 + first destination ID2 + first source ID2 + unicast")
  • SCI2 is used to schedule the newly transmitted data 2.
  • the receiving terminal needs to be "SL process ID2 + first destination ID2 + first "One source ID2+unicast” selects an unoccupied SL process. If the selected unoccupied SL process is SL process 1, if data 2 is not successfully received, the cache of SL process 1 contains data 2.
  • the receiving terminal receives SCI3 (including "SL process ID1+first destination ID1+first source ID1+unicast")
  • SCI3 is used to schedule the newly transmitted data 3 that is, the receiving terminal receives "SL process ID1+
  • the SCI or newly transmitted SL data corresponding to the first destination ID1 + first source ID1 + unicast scheduling the newly transmitted SL data due to the association between "SL process ID1 + first destination ID1 + first source ID1 + unicast" and SL process 1 relationship still exists, therefore, the receiving terminal will clear the cache of SL process 1 associated with "SL process ID1 + first destination ID1 + first source ID1 + unicast” and regard SL process 1 as unoccupied, and at this time, There is still data 2 in the cache of the SL process 1 to be processed.
  • the terminal will erroneously clear the data 2, which affects the reception of the data 2.
  • the SL process 1 may be used for other data reception, which affects the reception of the data 2.
  • the sending terminal when the above-mentioned event 1, event 2, and event 3 occur, the sending terminal does not regard the SL process as unoccupied, and does not clear the cache of the SL process.
  • SL processes are not regarded as unoccupied, so that these SL processes cannot be used for sending other data, resulting in a reduction in the number of available SL processes; the cache of SL processes is not cleared, which may make these SL processes unusable.
  • the sending of other data results in a reduction in the number of available SL processes, or a larger cache, or a false trigger retransmission.
  • Embodiment 1 to Embodiment 5, which are described below respectively.
  • Embodiment 1 can solve the problem caused by not releasing the association relationship between the SCI and the SL process when event 1 occurs on the receiving terminal, and/or not treating the SL process as not being occupied.
  • the method includes:
  • the terminal determines to perform MAC reset on the RRC connection of the SL.
  • Step 501 can also be described as: the terminal performs MAC reset on the RRC connection of the SL.
  • the terminal may be a receiving terminal.
  • the RRC connection of the SL may be: a logical connection between a pair of second source IDs and second destination IDs; or, at the access-stratum (AS) layer, A pair of logical connections between a second source ID and a second destination ID.
  • the RRC connection of the SL may also be referred to as a PC5-RRC connection.
  • the RRC connection of the SL may include/replace with/correspond to any one or more of the following: unicast, unicast connection, destination address, second source ID and second destination ID pair (pair), Secondary destination ID.
  • the RRC connection of an SL may be understood/replaced as: an RRC connection of an SL, or, a unicast, or, a unicast connection, or, a destination address, or, a For a second source ID and a second destination ID, or, a second source ID and a second destination ID pair, or, a second destination ID.
  • the RRC connection of the first SL can be understood/replaced as: the first unicast, or, the first unicast connection, or, the first destination address, or, the pair of the second source ID1 and the second destination ID1, or, Second destination ID1.
  • a destination address (destination) is used to identify a unicast, or a multicast, or a broadcast.
  • the second source ID and the second destination ID pair are used to identify a unicast.
  • performing MAC reset for the RRC connection of the SL may include/replace/understand as: performing a SL-specific MAC reset (Sidelink specific reset of the MAC entity) for the RRC connection of the SL.
  • SL-specific MAC reset Sidelink specific reset of the MAC entity
  • the RRC connection, unicast connection, destination address, second source ID and second destination ID pair, second destination ID, second source ID, and second source ID of the SL correspond to Any two or more of the first destination ID pair corresponding to the first source ID and the second destination ID, the first destination ID corresponding to the second destination ID, and the first source ID corresponding to the second source ID can be correlated Associated/corresponding.
  • step 501 does not limit whether the terminal has performed MAC reset for the RRC connection of the SL.
  • step 501 can be understood as: the terminal will/prepare to perform MAC reset for the RRC connection of the SL.
  • the terminal determines that the first SL process is not occupied; and/or, the terminal releases the association relationship associated with the first SL process.
  • the first SL process is/includes the SL process associated with the RRC connection of the SL.
  • the first SL process may be/include one or more or all SL processes associated with the SL's RRC connection.
  • the SL process associated with the RRC connection of the SL can be understood as: the SL process associated with the second source ID and the second destination ID corresponding to the RRC connection of the SL, or the first source ID and the first source ID corresponding to the RRC connection of the SL.
  • the SL process associated with the destination ID For example, the second source ID and the second destination ID corresponding to the RRC connection of an SL are the second source ID1 and the second destination ID2, and the SL process associated with the RRC connection of the SL is the second source ID1 and the second destination ID2 Associated SL process.
  • the second source ID and the second destination ID corresponding to the RRC connection of one SL are the second source ID1 and the second destination ID2
  • the first source ID and the first destination ID corresponding to the second source ID1 and the second destination ID2 are The first source ID1 and the first destination ID2
  • the SL process associated with the RRC connection of the SL is the SL process associated with the first source ID1 and the first destination ID2.
  • the first SL process or the SL process associated with the RRC connection of the SL may include/replace with any one or more of the following: an SL process associated with a unicast connection, an SL process associated with a destination address , the SL process associated with the second destination ID, the SL process associated with the second source ID and the second destination ID pair, the SL process associated with the first destination ID, the SL process associated with the first source ID and the first destination ID pair SL process.
  • the association relationship associated with the first SL process includes: the association relationship between the first SL process and the SCI, and/or, the first SL process and the SL process ID, the first destination ID, and the first source ID and an association between one or more of the communication types.
  • determining the SL process as unoccupied may include/replace with any one or more of the following: consider the SL process as unoccupied, release the SL process, and deactivate the SL process. For example, determining that the first SL process is not occupied may be understood as releasing the first SL process.
  • releasing the association relationship associated with the SL process may include/replace as: deleting the association relationship associated with the SL process.
  • releasing the association relationship associated with the first SL process may include/replace: deleting the association relationship associated with the first SL process.
  • the association relationship that exists in the terminal or the SL process associated with the terminal may refer to the left side in FIG. 6 .
  • the terminal determines to perform a MAC reset for an RRC connection of an SL
  • the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively.
  • the SL process associated with the RRC connection of the SL is the SL process 1 and the SL process 2.
  • the terminal releases the SL process. 1 and SL process 2, and/or, release the associations associated with SL process 1 and SL process 2.
  • the association relationship with the SL process existing in the terminal can be referred to the right side in FIG. 6 .
  • the association relationship associated with the SL process shown in FIG. 6 is only an example, and in actual implementation, the association relationship associated with the SL process may be other, which is not limited in this application.
  • step 501 includes one or more of the following actions: (1) the upper layer of the MAC layer of the terminal requests a MAC reset for the RRC connection of the SL; (2) the MAC layer of the terminal/terminal is requested to perform a MAC reset for the SL. (3) The upper layer of the MAC layer of the terminal requests the MAC layer of the terminal to perform MAC reset for the RRC connection of the SL; (4) The MAC layer of the terminal determines to perform the MAC reset for the RRC connection of the SL; ( 5) The MAC layer of the terminal performs MAC reset for the RRC connection of the SL.
  • the terminal determining that the first SL process is not occupied includes: the MAC layer of the terminal determines that the first SL process is not occupied.
  • releasing the association relationship associated with the first SL process by the terminal includes: releasing the association relationship associated with the first SL process by the MAC layer of the terminal.
  • the MAC layer of the terminal may specifically be the MAC entity of the terminal.
  • the upper layer of the MAC layer may be an RRC layer, a radio link control (radio link control, RLC) layer, a packet data convergence protocol (packet data convergence protocol, PDCP) layer, and the like.
  • RRC radio link control
  • PDCP packet data convergence protocol
  • condition 3 includes any one or more of the following: the upper layer of the RRC layer of the terminal requests the RRC layer of the terminal to release the RRC connection of the SL; the upper layer of the RRC layer of the terminal requests to release the RRC connection of the SL; the upper layer of the RRC layer of the terminal requests the release of the RRC connection of the SL; Indicate the release of the SL unicast connection (PC5 unicast link) of the upper layer of the RRC layer of the terminal; the upper layer of the RRC layer of the terminal instructs the RRC layer of the terminal to release the SL unicast connection of the upper layer of the RRC layer of the terminal; SL unicast connection release; the terminal's RRC layer/terminal is requested to release the SL's RRC connection; the terminal's RRC layer/terminal is instructed to release the SL unicast connection of the upper layer of the terminal's R
  • condition 1 SL RLF occurs
  • condition 2 the terminal receives a fully configured SL RRC reset
  • the upper layer of the RRC layer of the terminal may be a V2X layer, a non-access stratum (non-access stratum, NAS) layer, an application (application, APP) layer, and the like.
  • a request may include/replace/understand any one or more of the following: configuration, indication.
  • the method provided in the first embodiment can determine that the first SL process is not occupied when the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL, so that these The SL process is used for receiving other data, avoiding the reduction of the number of available SL processes and increasing the rate of data reception.
  • the method provided in Embodiment 1 can release the association relationship associated with the first SL process when the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL, thereby avoiding
  • the terminal erroneously clears other data, or ensures the reception of data associated with the first SL process, which can improve the reliability of data reception.
  • the second embodiment can solve the problem caused by the fact that the SL process is not regarded as unoccupied and/or the cache of the SL process is not cleared when the event 1 occurs on the sending terminal.
  • the method includes:
  • the terminal determines to perform MAC reset on the RRC connection of the SL.
  • Step 701 can also be described as: the terminal performs MAC reset on the RRC connection of the SL.
  • the terminal may be a sending terminal.
  • step 501 For the related description of step 701, reference may be made to step 501, which will not be repeated.
  • the terminal determines that the first SL process is not occupied; and/or, the terminal clears the cache of the first SL process.
  • first SL process in the second embodiment can be found in the first embodiment, and will not be repeated here.
  • clearing the cache of the SL process may include/replace: deleting the cache of the SL process.
  • clearing the cache of the first SL process may include/replace with: deleting the cache of the first SL process.
  • the terminal determines to perform MAC reset for the RRC connection of one SL
  • the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1, respectively, which are the same as the first source ID1 and the first destination ID1.
  • the SL process associated with the RRC connection of the SL is the SL process associated with the first source ID1 and the first destination ID1 (for example, SL process 1 and SL process 2), and the terminal releases SL process 1 and SL process 2, and/or clears Cache for SL Process 1 and SL Process 2.
  • step 701 includes one or more of the following actions: (1) the upper layer of the MAC layer of the terminal requests a MAC reset for the RRC connection of the SL; (2) the MAC layer of the terminal/terminal is requested to perform a MAC reset for the SL. (3) The upper layer of the MAC layer of the terminal requests the MAC layer of the terminal to perform MAC reset for the RRC connection of the SL; (4) The MAC layer of the terminal determines to perform the MAC reset for the RRC connection of the SL; ( 5) The MAC layer of the terminal performs MAC reset for the RRC connection of the SL.
  • the terminal determining that the first SL process is not occupied includes: the MAC layer of the terminal determines that the first SL process is not occupied.
  • clearing the cache of the first SL process by the terminal includes: clearing the cache of the first SL process by the MAC layer of the terminal.
  • the MAC layer of the terminal may specifically be the MAC entity of the terminal.
  • the terminal performs step 701 or any one or more actions in (1)-(5) above when condition 3 is satisfied.
  • condition 3 reference may be made to Embodiment 1, and details are not repeated here.
  • condition 4 may be: the terminal sends the SL RRC reconfiguration message, or the terminal sends the SL RRC reconfiguration message, and the terminal receives the SL RRC reconfiguration complete message.
  • the SL RRC reconfiguration message includes an indication of the full configuration.
  • the SL RRC reconfiguration message is associated with the RRC connection of the SL.
  • the SL RRC Reconfiguration Complete message is associated with the SL's RRC connection.
  • the SL RRC reconfiguration complete message corresponds to the SL RRC reconfiguration message.
  • the terminal sends a SL RRC reconfiguration message for an RRC connection of one SL, or, if the terminal sends an SL RRC reconfiguration message for an RRC connection of one SL and receives a SL RRC reconfiguration complete message, wherein the SL The RRC reconfiguration message includes an indication of the full configuration.
  • the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively, and the SL process associated with the RRC connection of the SL is the first source ID1 and the first destination ID1
  • the terminal determines that SL process 1 and SL process 2 are not occupied, and/or clears the caches of SL process 1 and SL process 2.
  • the terminal can determine when setting the SL RRC reconfiguration message, or when/before/after sending the SL RRC reconfiguration message
  • the MAC reset is performed on the RRC connection of the SL, which is not limited in this application.
  • setting can be understood as generating or determining.
  • the sending of the SL RRC reconfiguration message may be specifically performed by the RRC layer of the terminal.
  • condition 1 SL RLF occurs
  • condition 2 the terminal receives a fully configured SL RRC reset
  • Condition 3 and/or Condition 4 may also be present in addition to the matching message).
  • the terminal may also directly execute step 702 when sending the SL RRC reconfiguration message, or sending the SL RRC reconfiguration message, and the terminal receives the SL RRC reconfiguration complete message.
  • the method provided in the second embodiment can determine that the first SL process is not occupied when the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL, so that these The SL process is used for sending other data, avoiding the reduction of the number of available SL processes and increasing the rate of data reception.
  • the method provided in the second embodiment can release the storage space by clearing the cache of the first SL process when the terminal determines to perform MAC reset for the RRC connection of the SL or the terminal performs MAC reset for the RRC connection of the SL.
  • These SL processes can be used for sending other data, avoiding the reduction of the number of available SL processes, and increasing the rate of data reception.
  • the third embodiment can solve the problem caused by the failure to perform one or more actions of releasing the association relationship between the SCI and the SL process, treating the SL process as unoccupied, and clearing the cache of the SL process when event 2 occurs at the receiving terminal.
  • the problem can also be solved when event 2 occurs on the sending terminal, the SL process is not regarded as unoccupied, and/or the problem caused by the cache of the SL process is not cleared.
  • the method includes:
  • the terminal releases the RRC connection of the SL. That is, the terminal no longer receives or sends unicast data.
  • the terminal may be a sending terminal or a receiving terminal.
  • the terminal may be a sending terminal or a receiving terminal.
  • the terminal performs one or more of the following actions: the terminal determines that the first SL process is not occupied, the terminal releases the association relationship associated with the first SL process, and the terminal clears the cache of the first SL process.
  • the first SL process is/includes the SL process associated with the RRC connection of the SL.
  • the first SL process may be/include one or more or all SL processes associated with the SL's RRC connection.
  • the association relationship associated with the first SL process includes: the association relationship between the first SL process and the SCI, and/or the first SL process and the SL process ID, the first purpose An association relationship between one or more of the ID, the first source ID, and the communication type.
  • the related description of "determining the SL process as unoccupied” and “releasing the association relationship associated with the SL process” can refer to the first embodiment, and the related description of "clearing the cache of the SL process” can refer to the second embodiment. ,No longer.
  • the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively, which are associated with the RRC connection of the SL.
  • the SL process is an SL process associated with the first source ID1 and the first destination ID1 (for example, SL process 1 and SL process 2), and the terminal performs one or more of the following actions: determining SL process 1 and SL process 2 as If it is not occupied, the caches of SL process 1 and SL process 2 are cleared, and the association relationship associated with SL process 1 and SL process 2 is released.
  • the release of the RRC connection of the SL by the terminal includes: the RRC layer of the terminal releases the RRC connection of the SL, or the upper layer of the RRC layer of the terminal requests to release the RRC connection.
  • the terminal determines that the first SL process is not occupied, including: the MAC entity of the terminal determines that the first SL process is not occupied.
  • releasing the association relationship associated with the first SL process by the terminal includes: releasing the association relationship associated with the first SL process by the MAC entity of the terminal.
  • clearing the cache of the first SL process by the terminal includes: clearing the cache of the first SL process by the MAC entity of the terminal.
  • condition 3 when condition 3 is satisfied, the RRC layer of the terminal releases the RRC connection of the SL.
  • the method provided by the third embodiment can determine that the first SL process is not occupied when the terminal releases the RRC connection of the SL, so that these SL processes can be used for sending or receiving other data, and the available SL processes can be avoided. By reducing the number, the rate at which data is sent or received can be increased.
  • the method provided by the third embodiment can release the storage space by clearing the cache of the first SL process when the terminal releases the RRC connection of the SL, and can also make these SL processes used for sending or receiving other data, avoiding the availability of the SL process. The number of SL processes is reduced, which can increase the rate at which data is sent or received.
  • the method provided by the third embodiment can release the association relationship associated with the first SL process when the terminal releases the RRC connection of the SL, so as to avoid the receiving terminal from erroneously clearing other data, and the reliability of data reception can be improved. , or, ensuring the reception of data associated with the first SL process can improve the reliability of data reception.
  • the fourth embodiment can solve the problem caused by one or more of the failure to execute the release of the association relationship between the SCI and the SL process when the event 3 occurs in the receiving terminal, the SL process is regarded as unoccupied, and the cache of the SL process is cleared. , it can also solve the problem caused by not treating the SL process as unoccupied and/or not clearing the cache of the SL process when event 3 occurs on the sending terminal.
  • the method includes:
  • the terminal no longer sends or receives SL data.
  • the destination address (destination) is used to identify a multicast, or a broadcast, or a unicast.
  • the destination address may include/replace with/correspond to any one or more of the following: multicast, multicast service, broadcast, broadcast service, unicast, unicast connection, SL RRC connection, second Source ID and second destination ID pair (pair), second destination ID, first source ID and first destination ID pair (pair), first destination ID.
  • the destination address may also include/replace with/correspond to any one or more of the following: a destination address, a multicast, a multicast service, a broadcast, a broadcast service, and an SL RRC connection , or, a unicast, or, a unicast connection, or, a destination address, or, a pair of a second source ID and a second destination ID, or, a pair of a second source ID and a second destination ID, or , a second destination ID, or, a pair of a first source ID and a first destination ID, or, a pair of a first source ID and a first destination ID, or, a first destination ID.
  • the first destination address can be understood/replaced as: the first multicast, the first multicast service, the first broadcast, the first broadcast service, the RRC connection of the first SL, or the first unicast, or the first A unicast connection, or, first destination address, or, second source ID1 and second destination ID1 pair, or, second destination ID1, or, first source ID1 and first destination ID1 pair, or, first destination ID1.
  • no longer sending or receiving can be understood as: there has been sending or receiving before, but not (re) sending or receiving at present, and there is no limit to not sending or not receiving in the future.
  • the terminal performs one or more of the following actions: the terminal determines that the second SL process is not occupied; the terminal releases the association relationship associated with the second SL process; and the terminal clears the cache of the second SL process.
  • the action of step 902 may be performed by the MAC layer of the terminal.
  • the second SL process is/includes the SL process associated with the destination address.
  • the second SL process may be/include one or more or all SL processes associated with the destination address.
  • the SL process associated with the destination address may be understood as: the SL process associated with the second destination ID corresponding to the destination address, or the SL process associated with the first destination ID corresponding to the destination address.
  • the second destination ID corresponding to one destination address is the second destination ID2
  • the SL process associated with the destination address is the SL process associated with the second destination ID2.
  • the second destination ID corresponding to a destination address is the second destination ID2
  • the first destination ID corresponding to the second destination ID2 is the first destination ID2
  • the SL process associated with the destination address is the SL associated with the first destination ID2 process.
  • the first SL process or the SL process associated with the destination address may include/replace with any one or more of the following: an SL process associated with a multicast/multicast service, an SL process associated with a broadcast/broadcast service SL process, the SL process associated with the second destination ID, and the SL process associated with the first destination ID.
  • the association relationship associated with the second SL process includes: the association relationship between the second SL process and the SCI, and/or the second SL process and the SL process ID, the first purpose An association relationship between one or more of the ID, the first source ID, and the communication type.
  • the related description of "determining the SL process as unoccupied” and “releasing the association relationship associated with the SL process” can refer to the first embodiment, and the related description of "clearing the cache of the SL process” can refer to the second embodiment. ,No longer.
  • the association relationship existing in the terminal or existing in the terminal associated with the SL process can be referred to the left side of FIG. 10 .
  • the terminal no longer receives SL data, wherein the first source ID and the first destination ID corresponding to the destination address are the first source ID2 and the first destination ID2 respectively, then the SL processes associated with the destination address are SL process 3 and SL process 4, and the terminal releases SL process 3 and SL process 4, and/or, release the association relationship associated with SL process 3 and SL process 4.
  • the association relationship with the SL process existing in the terminal can be referred to the right side in FIG. 10 .
  • the association relationship associated with the SL process shown in FIG. 10 is only an example, and in actual implementation, the association relationship associated with the SL process may be other, which is not limited in this application.
  • the terminal no longer sends or receives SL data, including: the transmission corresponding to the destination address is terminated, or the terminal does not need to send or receive SL data corresponding to the destination address (that is, the terminal is no longer interested in the transmission corresponding to the destination address. ).
  • the transmission corresponding to the destination address may include multicast transmission or broadcast transmission corresponding to the destination address.
  • the termination of transmission corresponding to the destination address can be understood as the termination of multicast transmission or broadcast transmission corresponding to the destination address. That is, the multicast or broadcast for this destination address is terminated/not sent again.
  • the fact that the terminal does not need to send or receive the SL data corresponding to the destination address may include: determining that the terminal does not need to send or receive the SL data corresponding to the destination address; the terminal is no longer interested in the transmission corresponding to the destination address.
  • the upper layer of the RRC layer of the terminal may request (or instruct or configure) that the transmission corresponding to a destination address is no longer of interest.
  • the upper layer of the RRC layer of the terminal may request (or instruct or configure) the termination of transmission for a destination address.
  • the second SL process can be determined to be unoccupied when the terminal no longer sends or receives SL data for a destination address, so that these SL processes can be used for sending or receiving other data.
  • Receive avoiding a reduction in the number of available SL processes, can increase the rate at which data is sent or received.
  • the method provided by the fourth embodiment can release the storage space by clearing the cache of the second SL process when the terminal no longer sends or receives SL data for a destination address, and can also make these SL processes used for other data.
  • the rate at which data is sent or received can be increased by avoiding a reduction in the number of available SL processes.
  • the method provided by the fourth embodiment can release the association relationship associated with the second SL process when the terminal no longer sends or receives SL data for a destination address, thereby preventing the receiving terminal from erroneously clearing other data, Alternatively, ensuring the reception of data associated with the first SL process can improve the reliability of data reception.
  • the fifth embodiment can solve the problem caused by one or more of not executing the release of the association relationship between the SCI and the SL process, treating the SL process as unoccupied, and clearing the cache of the SL process when event 3 occurs in the receiving terminal. , it can also solve the problem caused by not treating the SL process as unoccupied and/or not clearing the cache of the SL process when event 3 occurs on the sending terminal.
  • the method includes:
  • the terminal determines to perform MAC reset.
  • performing a MAC reset for a destination address may include/replace/understand: performing an SL-specific MAC reset (Sidelink specific reset of the MAC entity) for a destination address.
  • SL-specific MAC reset Sidelink specific reset of the MAC entity
  • Step 1101 can also be described as: for a destination address, the terminal performs MAC reset.
  • the destination address (destination) is used to identify a multicast, or a broadcast.
  • the method further includes: for the destination address, the terminal no longer sends or receives SL data.
  • the terminal does not send or receive SL data any more", refer to Embodiment 4, and details are not repeated here.
  • the terminal performs one or more of the following actions: the terminal determines that the second SL process is not occupied; the terminal releases the association relationship associated with the second SL process; the terminal clears the cache of the second SL process; The SL process is the SL process associated with the destination address.
  • the association relationship associated with the second SL process includes: the association relationship between the second SL process and the SCI, and/or, the second SL process and the SL process ID, the first destination ID, and the first source ID and an association between one or more of the communication types.
  • step 1102 For the related description of step 1102, reference may be made to the above-mentioned step 902, which will not be repeated.
  • the method provided in the fifth embodiment can determine that the second SL process is not occupied when the terminal performs MAC reset for a destination address, so that these SL processes can be used for sending or receiving other data, avoiding The number of available SL processes is reduced, which can increase the rate at which data is sent or received.
  • the method provided by the fifth embodiment can release the storage space by clearing the cache of the second SL process when the terminal performs MAC reset for a destination address, and can also make these SL processes used for sending other data or Receive, avoiding a reduction in the number of available SL processes, can increase the rate at which data is sent or received.
  • the method provided by the fifth embodiment can release the association relationship associated with the second SL process when the terminal performs MAC reset for a destination address, thereby avoiding the receiving terminal from erroneously clearing other data, and can improve the data.
  • the reliability of reception, or, ensuring the reception of data associated with the first SL process, can improve the reliability of data reception.
  • PC5-S transmission for a destination address is terminated at the upper layer of the RRC layer; or, the upper layer of the RRC layer requests (or instructs or configures) the termination of PC5-S transmission for a destination address, and the terminal performs the following actions: One or more of: the terminal determines that the fourth SL process is not occupied, the terminal releases the association relationship associated with the fourth SL process, and the terminal clears the cache of the fourth SL process.
  • the fourth SL process refers to the SL process associated with the PC5-S of the destination address or the destination address.
  • PC5-S transmission for a destination address is terminated at the upper layer of the RRC layer; or, the upper layer of the RRC layer requests (or instructs or configures) PC5-S transmission for a destination address to terminate, and the terminal for the destination address.
  • the PC5-S or the destination address resets the MAC address, and the terminal performs one or more of the following actions: the terminal determines that the fourth SL process is not occupied, the terminal releases the association relationship associated with the fourth SL process, and the terminal clears the fourth SL process. Cache for the SL process.
  • mode1 and mode2 cannot exist at the same time, and mutual retransmission cannot be performed between different resource configuration modes.
  • the present application also provides the methods for processing the SL process shown in Embodiment 6 and Embodiment 7, which will be described separately below. Both the terminals in Embodiment 6 and Embodiment 7 may be sending terminals.
  • the method for processing the SL process provided by the sixth embodiment includes:
  • the terminal determines that the resource configuration mode is the first resource configuration mode.
  • Step 1201 can also be described as: the terminal determines that the resource configuration mode is switched from the second resource configuration mode to the first resource configuration mode (that is, the resource configuration mode of the terminal is the second resource configuration mode before the switch), or the terminal determines the resource configuration The mode is switched from the first resource configuration mode and the second resource configuration mode to the first resource configuration mode (that is, the resource configuration mode of the terminal before the switching is the first resource configuration mode and the second resource configuration mode).
  • switching may be replaced by changing.
  • the first resource configuration mode may be mode1 or mode2.
  • the terminal determining that the resource configuration mode is the first resource configuration mode may include any one or more of the following: the MAC layer of the terminal determines that the resource configuration mode is the first resource configuration mode; the MAC layer of the terminal/terminal is configured with the resource configuration mode as the first resource configuration mode In the resource configuration mode, the RRC layer of the terminal configures the resource configuration mode as the first resource configuration mode, and the RRC layer of the terminal configures the resource configuration mode for the MAC layer of the terminal as the first resource configuration mode. For example, specifically, when the MAC entity of the terminal is configured with the SL resource associated with mode1, the terminal determines that the resource configuration mode is mode1. When the RRC layer of the terminal configures the SL resource to be associated with mode2, the terminal determines that the resource configuration mode is mode2.
  • the terminal determines that the third SL process is not occupied, and/or clears the cache of the third SL process.
  • the third SL process is the SL process associated with the second resource configuration mode, that is, the third SL process or the SL process associated with the second resource configuration mode can be understood as: using the resources corresponding to the second resource configuration mode
  • the second resource configuration mode is mode2. If the first resource configuration mode is mode2, the second resource configuration mode is mode1.
  • the third SL process is determined as not being occupied, so that these SL processes can be used for sending other data, and the available SL processes can be avoided.
  • the rate at which data is received can be increased.
  • the storage space can be released, and these SL processes can also be used for sending other data, so as to avoid reducing the number of available SL processes, and improve the rate of data sending or receiving.
  • the resources corresponding to the first resource configuration mode include configured SL authorization resources (that is, SL CG resources) or dynamic SL authorization resources (that is, SL DG resources) (that is, the first resource configuration mode is mode1), in step Before 1202, the method further includes: the terminal (for example, the HARQ entity of the terminal) obtains a configured SL authorization resource or a dynamic SL authorization resource (that is, the resource of mode1 is obtained, optionally, the resource may be a newly transmitted resource) ), and/or, it is determined that the number of unoccupied SL processes is less than or equal to the first threshold.
  • the terminal for example, the HARQ entity of the terminal
  • obtains a configured SL authorization resource or a dynamic SL authorization resource that is, the resource of mode1 is obtained, optionally, the resource may be a newly transmitted resource
  • the terminal acquiring the configured SL authorization resource or the dynamic SL authorization resource may include: the terminal acquires the configured SL authorization resource or the dynamic SL authorization resource, and acquires the configured SL authorization resource or the dynamic SL authorization resource. The data transferred on the resource.
  • the first threshold may be configured/instructed/sent to the terminal by the network device, may be pre-configured, may be specified by a protocol, may be stored in the terminal by the device manufacturer before the terminal leaves the factory, or may be When the terminal is connected to the network, the network device/other device is pre-configured in the terminal.
  • the first threshold may be 0, 2, 3, and so on.
  • the number of unoccupied SL processes is less than or equal to the first threshold, it can be understood that all SL processes are occupied, or the number of unoccupied SL processes is less than or equal to the requirement of the terminal for SL processes. number.
  • the terminal may directly execute step 1202, or may obtain configuration SL authorization resources or dynamic SL authorization resources, and/or the number of unoccupied SL processes is less than or equal to the first threshold. Step 1202 is performed.
  • Step 1202 may be performed when/after the configuration SL authorization resource or the dynamic SL authorization resource is acquired.
  • the resource corresponding to the first resource configuration mode includes a selected SL resource (selection sidelink resource) (that is, the first resource configuration mode is mode2).
  • the method further includes: the terminal determines the selected SL resource. (that is, the terminal needs to perform resource selection or needs to determine resources), and/or, the number of unoccupied SL processes is less than or equal to the first threshold.
  • the terminal may directly execute step 1202, or may execute step 1202 when the terminal determines the selected SL resource and/or the number of unoccupied SL processes is less than or equal to the first threshold.
  • the terminal can execute the resource selection when/after it is required/determined Step 1202.
  • the method further includes: for the second resource configuration mode, the terminal determines to perform MAC reset. That is, the mode switching triggers the MAC reset for the second resource configuration mode, and the MAC reset triggers the execution of step 1202 .
  • performing MAC reset for the second resource configuration mode may include/replace/understand as: performing SL-specific MAC reset (Sidelink specific reset of the MAC entity) for the second resource configuration mode.
  • SL-specific MAC reset Sidelink specific reset of the MAC entity
  • one or more of the third SL processes may be determined to be unoccupied according to one or more of the following information, and/or one of the third SL processes may be cleared. or multiple caches.
  • the terminal may determine one or more data-associated SL processes with the lowest priority or lower than a priority threshold as unoccupied and/or clear the corresponding cache.
  • the terminal may determine that one or more data-related SL processes whose latency requirements are the highest or lower than a latency threshold are not occupied and/or clear the corresponding cache.
  • the terminal may determine one or more data-related SL processes whose reliability requirements are the lowest or lower than a reliability threshold as unoccupied and/or clear the corresponding cache.
  • the terminal may also determine that one or more data-related SL processes are not occupied and/or clear the corresponding cache after a period of time after the mode is switched.
  • the terminal can process SL processes one by one.
  • one SL process can be used to process one SL process, or multiple SL processes can be processed, and all SL processes can be processed at one time, which is not limited in this application.
  • the processing here includes determining the SL process as unoccupied and/or flushing the corresponding cache.
  • the method further includes: the terminal releases the SL resources corresponding to the second resource configuration mode and/or the configuration corresponding to the SL resources corresponding to the second resource configuration mode, so that these resources can be subsequently used by other terminals, improving the resource utilization.
  • the method for processing the SL process provided by the seventh embodiment includes:
  • the terminal determines to perform MAC reset.
  • the terminal may perform step 1301 in the case of switching from the second resource configuration mode to another resource configuration mode, for example, the terminal may switch from the second resource configuration mode to the first resource in the resource configuration mode.
  • step 1301 is performed, and the terminal may also perform step 1301 when the resource configuration mode is switched from the first resource configuration mode and the second resource configuration mode to the first resource configuration mode.
  • the terminal may also perform step 1301 under the trigger of other trigger conditions.
  • the second resource configuration mode may be mode1 or mode2.
  • the method further includes: the terminal determines that the resource configuration mode is the first resource configuration mode.
  • the terminal determines that the resource configuration mode is the first resource configuration mode.
  • the terminal determines that the third SL process is not occupied, and/or clears the cache of the third SL process.
  • one or more of the third SL processes may be determined to be unoccupied according to one or more of the following information, and/or one of the third SL processes may be cleared. or multiple caches.
  • the method further includes: the terminal releases the SL resources corresponding to the second resource configuration mode and/or the configuration corresponding to the SL resources corresponding to the second resource configuration mode, so that these resources can be subsequently used by other terminals, improving the resource utilization.
  • the terminal determines to perform MAC reset for the second resource configuration mode, by determining that the third SL process is not occupied, these SL processes can be used for sending other data, avoiding available data.
  • the number of SL processes is reduced, which can improve the rate of data reception.
  • the storage space can be released, and these SL processes can also be used for sending other data, so as to avoid reducing the number of available SL processes, and improve the rate of data sending or receiving.
  • Embodiment 8 which is used to improve resource utilization.
  • the method for releasing SL resources provided by the eighth embodiment includes:
  • the terminal determines that the resource configuration mode is the first resource configuration mode.
  • the terminal releases the SL resource corresponding to the second resource configuration mode and/or the configuration corresponding to the SL resource corresponding to the second resource configuration mode.
  • Embodiment 8 By releasing the SL resources associated with the second resource configuration mode and/or the configuration corresponding to the SL resources associated with the second resource configuration mode, these resources can be subsequently used by other terminals, thereby improving resource utilization.
  • the methods shown in the sixth embodiment to the eighth embodiment are also applicable to the LTE system, and it is only necessary to replace the mode1 with mode3 and the mode2 with mode4 for understanding.
  • parameter eg, destination address, second resource configuration mode, RRC connection of SL
  • parameter eg, destination address, second resource configuration mode, RRC connection of SL
  • MAC reset it is not limited whether or not MAC reset has been performed for this parameter.
  • the terminal will/prepare to reset the MAC for this parameter.
  • the buffer of the SL process of the sending terminal may be referred to as a HARQ buffer
  • the buffer of the SL process of the receiving terminal may be referred to as a soft buffer.
  • the SL process that is considered to be unoccupied can also be described as releasing the SL process or deactivating the SL process, and the SL process that is not occupied can also be described as a deactivated SL process.
  • an SL process that is considered occupied can also be described as an activated SL process, and an occupied SL process can also be described as an activated SL process.
  • the terminal includes at least one of corresponding hardware structures and software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the terminal may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division methods may be used in actual implementation.
  • FIG. 15 shows a possible schematic structural diagram of the apparatus (referred to as apparatus 150 ) involved in the foregoing embodiment, where the apparatus 150 includes a processing unit 1501 and a communication unit 1502 .
  • a storage unit 1503 is also included.
  • the apparatus 150 may be used to illustrate the structure of the terminal in the foregoing embodiment.
  • the processing unit 1501 is used to control and manage the actions of the terminal.
  • the processing unit 1501 is used to execute the operations in FIG. 5 , FIG. 7 , FIG. 8 , FIG. 9 , FIG. 11 , FIG. 12 , FIG. 13 and FIG. Each step, and/or actions performed by the terminal in other processes described in the embodiments of this application.
  • the processing unit 1501 can communicate with other network entities through the communication unit 1502, for example, to transmit SL data or SCI with another terminal.
  • the storage unit 1503 is used to store program codes and data of the terminal.
  • the apparatus 150 may be a device or a chip or a chip system.
  • the processing unit 1501 may be a processor; the communication unit 1502 may be a communication interface, a transceiver, or an input interface and/or an output interface.
  • the transceiver may be a transceiver circuit.
  • the input interface may be an input circuit, and the output interface may be an output circuit.
  • the communication unit 1502 may be a communication interface, input interface and/or output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or chip system.
  • the processing unit 1501 may be a processor, a processing circuit, a logic circuit, or the like.
  • the medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • Storage media for storing computer software products include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or CD, etc. that can store program codes medium.
  • An embodiment of the present application also provides a schematic diagram of a hardware structure of an apparatus.
  • the apparatus includes a processor 1601 and, optionally, a memory 1602 connected to the processor 1601 .
  • the processor 1601 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
  • the processor 1601 may also include multiple CPUs, and the processor 1601 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, or processing cores for processing data (eg, computer program instructions).
  • the memory 1602 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory.
  • read-only memory EEPROM
  • CD-ROM compact disc read-only memory
  • optical disc storage including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.
  • magnetic disk A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, is not limited in this embodiment of the present application.
  • the memory 1602 may exist independently (in this case, the memory 1602 may be located outside the device, or may be located in the device), or may be integrated with the processor 1601 . Among them, the memory 1602 may contain computer program code.
  • the processor 1601 is configured to execute the computer program codes stored in the memory 1602, so as to implement the methods provided by the embodiments of the present application.
  • the apparatus further includes a transceiver 1603 .
  • the processor 1601, the memory 1602 and the transceiver 1603 are connected by a bus.
  • the transceiver 1603 is used to communicate with other devices or communication networks.
  • the transceiver 1603 may include a transmitter and a receiver.
  • a device in the transceiver 1603 for implementing the receiving function may be regarded as a receiver, and the receiver is configured to perform the receiving steps in the embodiments of the present application.
  • the device in the transceiver 1603 for implementing the sending function may be regarded as a transmitter, and the transmitter is used to perform the sending step in the embodiment of the present application.
  • the schematic structural diagram shown in FIG. 16 may be used to illustrate the structure of the terminal involved in the foregoing embodiment.
  • the processor 1601 is used to control and manage the actions of the terminal, for example, the processor 1601 is used to execute the operations in FIG. 5 , FIG. 7 , FIG. 8 , FIG. 9 , FIG. 11 , FIG. 12 , FIG. 13 and FIG. 14 Each step, and/or actions performed by the terminal in other processes described in the embodiments of this application.
  • the processor 1601 can communicate with other network entities through the transceiver 1603, for example, to transmit SL data or SCI with another terminal.
  • the memory 1602 is used to store program codes and data of the terminal.
  • the processor 1601 includes a logic circuit and an input interface and/or an output interface.
  • the output interface is used for performing the sending action in the corresponding method
  • the input interface is used for performing the receiving action in the corresponding method.
  • FIG. 17 The schematic structural diagram shown in FIG. 17 may be used to illustrate the terminals involved in the foregoing embodiments.
  • the processor 1601 is used to control and manage the actions of the terminal, for example, the processor 1601 is used to execute the operations in FIG. 5 , FIG. 7 , FIG. 8 , FIG. 9 , FIG. 11 , FIG. 12 , FIG. 13 and FIG.
  • the processor 1601 may communicate with other network entities through the input interface and/or the output interface, for example, to transmit SL data or SCI, etc. with another terminal.
  • the memory 1602 is used to store program codes and data of the terminal.
  • each step in the method provided in this embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • Embodiments of the present application further provide a computer-readable storage medium, including computer-executable instructions, which, when executed on a computer, cause the computer to execute any of the above methods.
  • Embodiments of the present application also provide a computer program product, including computer-executable instructions, which, when run on a computer, cause the computer to execute any of the above methods.
  • An embodiment of the present application further provides a communication system, including: the above-mentioned terminal.
  • An embodiment of the present application further provides an apparatus, including: a processor and an interface, the processor is coupled to a memory through the interface, and when the processor executes a computer program or computer-executable instruction in the memory, any one of the above-mentioned embodiments method is executed.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g.
  • coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or data storage devices including one or more servers, data centers, etc., that can be integrated with the media.
  • Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

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

Abstract

本申请提供了一种处理侧行链路进程的方法及装置，涉及通信技术领域。该方法中，终端确定对侧行链路的RRC连接进行MAC重置。之后，终端可以将与RRC连接关联的侧行链路进程(记为第一侧行链路进程)确定为未被占用，从而可以使得这些SL进程用于其他数据的接收，避免可用的SL进程数量减少，提高数据接收的速率。终端还可以释放与第一侧行链路进程关联的关联关系，从而避免终端错误的清空掉其他数据，或者，确保与第一侧行链路进程关联的数据的接收，可以提高数据接收的可靠性。

Description

处理侧行链路进程的方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种处理侧行链路(sidelink，SL)进程的方法及装置。
背景技术
车联网(vehicle to everything，V2X)是智能交通运输***的关键技术，被认为是物联网体系中最有产业潜力、市场需求最明确的领域之一。车联网一般是指通过装载在车上的传感器、车载终端等提供车辆信息，实现车辆到车辆(vehicle to vehicle，V2V)，车辆到基础设施(vehicle to infrastructure，V2I)，车辆到网络(vehicle to network，V2N)以及车辆到行人(vehicle to pedestrian，V2P)之间的相互通信的通信网络。
V2X具有应用空间广、产业潜力大、社会效益强的特点，对促进汽车和信息通信产业创新发展，构建汽车和交通服务新模式新业态，推动无人驾驶、辅助驾驶、智能驾驶、网联驾驶、智能网联驾驶、自动驾驶、汽车共享等技术的创新和应用，以及提高交通效率和安全水平等都具有重要意义。
一般的，在V2X场景下，终端与其他终端之间进行直连通信的通信链路可以称之为侧行链路(sidelink，SL)或者边链路。SL上的混合自动重传请求(hybrid automatic repeat request，HARQ)进程可以称为SL进程。目前针对SL进程的处理，没有有效的方法。
发明内容
本申请实施例提供了一种处理SL进程的方法及装置，用于避免可用的SL进程的数量减少。
第一方面，提供了一种处理侧行链路进程的方法，包括：终端确定对侧行链路的RRC连接进行MAC重置；终端将第一侧行链路进程确定为未被占用；和/或，终端释放与第一侧行链路进程关联的关联关系；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。第一方面提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的接收，避免可用的SL进程数量减少，可以提高数据接收的速率。通过将与第一SL进程关联的关联关系释放，从而避免终端错误的清空掉其他数据，或者，确保与第一SL进程关联的数据的接收，可以提高数据接收的可靠性。
在一种可能的实现方式中，终端确定对侧行链路的RRC连接进行MAC重置，包括：终端的MAC层的上层请求对RRC连接进行MAC重置；终端将第一侧行链路进程确定为未被占用，包括：终端的MAC实体将第一侧行链路进程确定为未被占用；终端释放与第一侧行链路进程关联的关联关系，包括：终端的MAC实体释放与第一侧行链路进程关联的关联关系。
在一种可能的实现方式中，在终端的MAC层的上层请求对RRC连接进行MAC重置之前，该方法还包括：终端的RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，与第一侧行链路进程关联的关联关系，包括：第一侧行链路进程与SCI之间的关联关系，和/或，第一侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第二方面，提供了一种处理侧行链路进程的方法，包括：终端确定对侧行链路的RRC连接进行MAC重置；终端将第一侧行链路进程确定为未被占用；和/或，终端清空第一侧行链路进程的缓存；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。第二方面提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第一SL进程的缓存，可以释放存储空间。
在一种可能的实现方式中，终端确定对侧行链路的RRC连接进行MAC重置，包括：终端的MAC层的上层请求对RRC连接进行MAC重置；终端将第一侧行链路进程确定为未被占用，包括：终端的MAC实体将第一侧行链路进程确定为未被占用；终端清空第一侧行链路进程的缓存，包括：终端的MAC实体清空第一侧行链路进程的缓存。
在一种可能的实现方式中，在终端的MAC层的上层请求对RRC连接进行MAC重置之前，该方法还包括：终端的RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，在终端确定对侧行链路的RRC连接进行MAC重置之前，该方法还包括：终端发送SL RRC重配消息，或者，终端发送SL RRC重配消息、且终端接收到SL RRC重配完成消息；其中，SL RRC重配消息包括全配置的指示。
第三方面，提供了一种处理侧行链路进程的方法，包括：终端释放侧行链路的RRC连接；终端执行以下动作中的一个或多个：终端将第一侧行链路进程确定为未被占用，终端释放与第一侧行链路进程关联的关联关系，终端清空第一侧行链路进程的缓存；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。第三方面提供的方法，可以在终端释放SL的RRC连接的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第一SL进程的缓存，可以释放存储空间。通过将与第一SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据，可以提高数据接收的可靠性。
在一种可能的实现方式中，终端释放侧行链路的RRC连接，包括：终端的RRC层释放RRC连接，或，终端的RRC层的上层请求释放RRC连接；终端将第一侧行链路进程确定为未被占用，包括：终端的MAC实体将第一侧行链路进程确定为未被占用；终端释放与第一侧行链路进程关联的关联关系，包括：终端的MAC实体释放与第一侧行链路进程关联的关联关系；终端清空第一侧行链路进程的缓存，包括：终端的MAC实体清空第一侧行链路进程的缓存。
在一种可能的实现方式中，在终端的RRC层释放RRC连接之前，该方法还包括：终端的RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，与第一侧行链路进程关联的关联关系，包括：第一侧行链路进程与SCI之间的关联关系，和/或，第一侧行链路进程与第一源标识、第一目 的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第四方面，提供了一种处理侧行链路进程的方法，包括：针对一个目的地址，终端不再发送或接收侧行链路数据；终端执行以下动作中的一个或多个：终端将第二侧行链路进程确定为未被占用；终端释放与第二侧行链路进程关联的关联关系；终端清空第二侧行链路进程的缓存；其中，第二侧行链路进程为与目的地址关联的侧行链路进程。第四方面提供的方法，可以在针对一个目的地址，终端不再发送或接收SL数据的情况下，将第二SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第二SL进程的缓存，可以释放存储空间。通过将与第二SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据。
在一种可能的实现方式中，终端不再发送或接收侧行链路数据，包括：目的地址对应的传输终止，或，终端不需要发送或接收目的地址对应的侧行链路数据。
在一种可能的实现方式中，与第二侧行链路进程关联的关联关系，包括：第二侧行链路进程与SCI之间的关联关系，和/或，第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第五方面，提供了一种处理侧行链路进程的方法，包括：针对一个目的地址，终端确定进行MAC重置；终端执行以下动作中的一个或多个：终端将第二侧行链路进程确定为未被占用；终端释放与第二侧行链路进程关联的关联关系；终端清空第二侧行链路进程的缓存；其中，第二侧行链路进程为与目的地址关联的侧行链路进程。第五方面提供的方法，可以在针对一个目的地址，终端进行MAC重置的情况下，将第二SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第二SL进程的缓存，可以释放存储空间。通过将与第二SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据，可以提高数据接收的可靠性。
在一种可能的实现方式中，在终端确定进行MAC重置之前，该方法还包括：针对目的地址，终端不再发送或接收侧行链路数据。
在一种可能的实现方式中，与第二侧行链路进程关联的关联关系，包括：第二侧行链路进程与SCI之间的关联关系，和/或，第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第六方面，提供了一种处理侧行链路进程的方法，包括：终端确定资源配置模式为第一资源配置模式；终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存；其中，第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。第六方面提供的方法，若终端确定资源配置模式为第一资源配置模式，由于第二资源配置模式与第一资源配置模式不可以同时存在，终端不会采用第二资源配置模式的资源，此时，通过将第三SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第三SL进程的缓存，可以释放存储空间。
在一种可能的实现方式中，第一资源配置模式对应的资源包括配置的侧行链路授权资源和/或动态的侧行链路授权资源，在终端将第三侧行链路进程确定为未被占用， 和/或，清空第三侧行链路进程的缓存之前，该方法还包括：终端获取配置的侧行链路授权资源或动态的侧行链路授权资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
在一种可能的实现方式中，第一资源配置模式对应的资源包括选择的侧行链路资源，在终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存之前，该方法还包括：终端确定选择的侧行链路资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
在一种可能的实现方式中，在终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存之前，该方法还包括：针对第二资源配置模式，终端确定进行MAC重置。
在一种可能的实现方式中，终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存，包括：终端根据与第三侧行链路进程关联的数据的优先级、与第三侧行链路进程关联的数据的时延要求、与第三侧行链路进程关联的数据的可靠性要求中的一个或多个，将第三侧行链路进程中的一个或多个确定为未被占用，和/或，清空第三侧行链路进程中的一个或多个的缓存。在终端中，可能发生mode切换频繁的情况，若mode切换之后立即释放进程，可能会造成丢包严重，对于优先级高、时延要求低、可靠性要求较高的业务来说可能不能满足要求，该种可能的实现方式，可以避免该情况。
在一种可能的实现方式中，该方法还包括：终端释放与第二资源配置模式对应的侧行链路资源和/或与第二资源配置模式对应的侧行链路资源对应的配置，以便于这些资源后续可以被其他终端使用，提高资源利用率。
第七方面，提供了一种处理侧行链路进程的方法，包括：针对第二资源配置模式，终端确定进行MAC重置；终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存；其中，第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。第七方面提供的方法，若针对第二资源配置模式，终端进行了MAC重置，通过将第三SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第三SL进程的缓存，可以释放存储空间。
在一种可能的实现方式中，在针对第二资源配置模式，终端确定进行MAC重置之前，该方法还包括：终端确定资源配置模式为第一资源配置模式。
在一种可能的实现方式中，终端将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存，包括：终端根据与第三侧行链路进程关联的数据的优先级、与第三侧行链路进程关联的数据的时延要求、与第三侧行链路进程关联的数据的可靠性要求中的一个或多个，将第三侧行链路进程中的一个或多个确定为未被占用，和/或，清空第三侧行链路进程中的一个或多个的缓存。
在一种可能的实现方式中，该方法还包括：终端释放与第二资源配置模式对应的侧行链路资源和/或与第二资源配置模式对应的侧行链路资源对应的配置。
第八方面，提供了一种释放侧行链路资源的方法，包括：终端确定资源配置模式为第一资源配置模式；终端释放与第二资源配置模式对应的侧行链路资源和/或与第二 资源配置模式对应的侧行链路资源对应的配置。第八方面通过释放第二资源配置模式关联的SL资源和/或与第二资源配置模式关联的SL资源对应的配置，可以使得这些资源后续被其他终端使用，提高资源利用率。
第九方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：确定对侧行链路的RRC连接进行MAC重置；将第一侧行链路进程确定为未被占用；和/或，释放与第一侧行链路进程关联的关联关系；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。
在一种可能的实现方式中，处理单元，具体用于：在MAC层的上层请求对RRC连接进行MAC重置；在MAC实体将第一侧行链路进程确定为未被占用；在MAC实体释放与第一侧行链路进程关联的关联关系。
在一种可能的实现方式中，处理单元，还用于：在RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，与第一侧行链路进程关联的关联关系，包括：第一侧行链路进程与SCI之间的关联关系，和/或，第一侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第十方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：确定对侧行链路的RRC连接进行MAC重置；将第一侧行链路进程确定为未被占用；和/或，清空第一侧行链路进程的缓存；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。
在一种可能的实现方式中，处理单元，具体用于：在MAC层的上层请求对RRC连接进行MAC重置；在MAC实体将第一侧行链路进程确定为未被占用；在MAC实体清空第一侧行链路进程的缓存。
在一种可能的实现方式中，处理单元，还用于：在RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，该装置还包括通信单元；通信单元，用于发送SL RRC重配消息，或者，发送SL RRC重配消息、且该装置接收到SL RRC重配完成消息；其中，SL RRC重配消息包括全配置的指示。
第十一方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：释放侧行链路的RRC连接；执行以下动作中的一个或多个：将第一侧行链路进程确定为未被占用，释放与第一侧行链路进程关联的关联关系，清空第一侧行链路进程的缓存；其中，第一侧行链路进程为与RRC连接关联的侧行链路进程。
在一种可能的实现方式中，处理单元，具体用于：在RRC层释放RRC连接，或，在RRC层的上层请求释放RRC连接；在MAC实体将第一侧行链路进程确定为未被占用；在MAC实体释放与第一侧行链路进程关联的关联关系；在MAC实体清空第一侧行链路进程的缓存。
在一种可能的实现方式中，处理单元，还用于：在RRC层的上层请求释放RRC连接。
在一种可能的实现方式中，与第一侧行链路进程关联的关联关系，包括：第一侧行链路进程与SCI之间的关联关系，和/或，第一侧行链路进程与第一源标识、第一目 的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第十二方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于；针对一个目的地址，不再发送或接收侧行链路数据；执行以下动作中的一个或多个：将第二侧行链路进程确定为未被占用；释放与第二侧行链路进程关联的关联关系；清空第二侧行链路进程的缓存；其中，第二侧行链路进程为与目的地址关联的侧行链路进程。
在一种可能的实现方式中，不再发送或接收侧行链路数据，包括：目的地址对应的传输终止，或，不需要发送或接收目的地址对应的侧行链路数据。
在一种可能的实现方式中，与第二侧行链路进程关联的关联关系，包括：第二侧行链路进程与SCI之间的关联关系，和/或，第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第十三方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：针对一个目的地址，确定进行MAC重置；执行以下动作中的一个或多个：将第二侧行链路进程确定为未被占用；释放与第二侧行链路进程关联的关联关系；清空第二侧行链路进程的缓存；其中，第二侧行链路进程为与目的地址关联的侧行链路进程。
在一种可能的实现方式中，处理单元，还用于：针对目的地址，不再发送或接收侧行链路数据。
在一种可能的实现方式中，与第二侧行链路进程关联的关联关系，包括：第二侧行链路进程与SCI之间的关联关系，和/或，第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
第十四方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：确定资源配置模式为第一资源配置模式；将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存；其中，第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。
在一种可能的实现方式中，第一资源配置模式对应的资源包括配置的侧行链路授权资源和/或动态的侧行链路授权资源，处理单元，还用于：获取配置的侧行链路授权资源或动态的侧行链路授权资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
在一种可能的实现方式中，第一资源配置模式对应的资源包括选择的侧行链路资源，处理单元，还用于：确定选择的侧行链路资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
在一种可能的实现方式中，处理单元，还用于：针对第二资源配置模式，确定进行MAC重置。
在一种可能的实现方式中，处理单元，具体用于：根据与第三侧行链路进程关联的数据的优先级、与第三侧行链路进程关联的数据的时延要求、与第三侧行链路进程关联的数据的可靠性要求中的一个或多个，将第三侧行链路进程中的一个或多个确定为未被占用，和/或，清空第三侧行链路进程中的一个或多个的缓存。
在一种可能的实现方式中，处理单元，还用于：释放与第二资源配置模式对应的侧行链路资源和/或与第二资源配置模式对应的侧行链路资源对应的配置。
第十五方面，提供了一种处理侧行链路进程的装置，包括：处理单元，用于：针对第二资源配置模式，确定进行MAC重置；将第三侧行链路进程确定为未被占用，和/或，清空第三侧行链路进程的缓存；其中，第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。
在一种可能的实现方式中，处理单元，还用于：确定资源配置模式为第一资源配置模式。
在一种可能的实现方式中，处理单元，具体用于：根据与第三侧行链路进程关联的数据的优先级、与第三侧行链路进程关联的数据的时延要求、与第三侧行链路进程关联的数据的可靠性要求中的一个或多个，将第三侧行链路进程中的一个或多个确定为未被占用，和/或，清空第三侧行链路进程中的一个或多个的缓存。
在一种可能的实现方式中，处理单元，还用于：释放与第二资源配置模式对应的侧行链路资源和/或与第二资源配置模式对应的侧行链路资源对应的配置。
第十六方面，提供了一种释放侧行链路资源的装置，包括：处理单元，用于：确定资源配置模式为第一资源配置模式；释放与第二资源配置模式对应的侧行链路资源和/或与第二资源配置模式对应的侧行链路资源对应的配置。
第十七方面，提供了一种处理侧行链路进程的装置，包括：处理器。处理器与存储器连接，存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，从而实现第一方面至第七方面中的任意一个方面提供的任意一种方法。示例性的，存储器和处理器可以集成在一起，也可以为独立的器件。若为后者，存储器可以位于处理侧行链路进程的装置内，也可以位于处理侧行链路进程的装置外。
在一种可能的实现方式中，处理器包括逻辑电路，还包括输入接口和/或输出接口。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
在一种可能的实现方式中，处理侧行链路进程的装置还包括通信接口和通信总线，处理器、存储器和通信接口通过通信总线连接。通信接口用于执行相应方法中的收发的动作。通信接口也可以称为收发器。可选的，通信接口包括发送器和接收器中的至少一种，该情况下，发送器用于执行相应方法中的发送的动作，接收器用于执行相应方法中的接收的动作。
在一种可能的实现方式中，处理侧行链路进程的装置以芯片的产品形态存在。
第十八方面，提供了一种释放侧行链路资源的装置，包括：处理器。处理器与存储器连接，存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，从而实现第八方面提供的方法。示例性的，存储器和处理器可以集成在一起，也可以为独立的器件。若为后者，存储器可以位于释放侧行链路资源的装置内，也可以位于释放侧行链路资源的装置外。
在一种可能的实现方式中，处理器包括逻辑电路，还包括输入接口和/或输出接口。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
在一种可能的实现方式中，释放侧行链路资源的装置还包括通信接口和通信总线，处理器、存储器和通信接口通过通信总线连接。通信接口用于执行相应方法中的收发 的动作。通信接口也可以称为收发器。可选的，通信接口包括发送器和接收器中的至少一种，该情况下，发送器用于执行相应方法中的发送的动作，接收器用于执行相应方法中的接收的动作。
在一种可能的实现方式中，释放侧行链路资源的装置以芯片的产品形态存在。
第十九方面，提供了一种处理侧行链路进程的装置，包括：处理器和接口，处理器通过接口与存储器耦合，当处理器执行存储器中的计算机程序或指令时，使得第一方面至第七方面中的任意一个方面提供的任意一种方法被执行。
第二十方面，提供了一种释放侧行链路资源的装置，包括：处理器和接口，处理器通过接口与存储器耦合，当处理器执行存储器中的计算机程序或指令时，使得第八方面提供的方法被执行。
第二十一方面，提供了一种计算机可读存储介质，包括计算机可执行指令，当计算机可执行指令在计算机上运行时，使得计算机执行第一方面至第八方面中任一方面提供的任意一种方法。
第二十二方面，提供了一种计算机程序产品，包括计算机可执行指令，当计算机可执行指令在计算机上运行时，使得计算机执行第一方面至第八方面中任一方面提供的任意一种方法。
第九方面至第二十二方面中的任一种实现方式所带来的技术效果可参见第一方面至第八方面中对应实现方式所带来的技术效果，此处不再赘述。
需要说明的是，在方案不矛盾的前提下，上述各个方面中的方案均可以结合。
附图说明
图1为本申请实施例提供的一种通信场景示意图；
图2为本申请实施例提供的一种侧行授权的示意图；
图3为本申请实施例提供的一种并行HARQ进程的示意图；
图4为本申请实施例提供的一种SCI与SL进程的关联示意图；
图5为本申请实施例提供的一种处理SL进程的方法的示意图；
图6为本申请实施例提供的一种释放与SL进程关联的关联关系的示意图；
图7为本申请实施例提供的又一种处理SL进程的方法的示意图；
图8为本申请实施例提供的又一种处理SL进程的方法的示意图；
图9为本申请实施例提供的又一种处理SL进程的方法的示意图；
图10为本申请实施例提供的又一种释放与SL进程关联的关联关系的示意图；
图11为本申请实施例提供的又一种处理SL进程的方法的示意图；
图12为本申请实施例提供的又一种处理SL进程的方法的示意图；
图13为本申请实施例提供的又一种处理SL进程的方法的示意图；
图14为本申请实施例提供的一种释放SL资源的方法的示意图；
图15为本申请实施例提供的一种终端的组成示意图；
图16为本申请实施例提供的一种终端的硬件结构示意图；
图17为本申请实施例提供的又一种终端的硬件结构示意图。
具体实施方式
在本申请的描述中，除非另有说明，“/”表示“或”的意思，例如，A/B可以表示A或B。 本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。此外，“至少一个”是指一个或多个，“多个”是指两个或两个以上。“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例提供的方法可适用但不限于如下领域：设备到设备(device to device，D2D)、V2X、无人驾驶(unmanned driving)、自动驾驶(automated driving，ADS)、辅助驾驶(driver assistance，ADAS)、智能驾驶(intelligent driving)、网联驾驶(connected driving)、智能网联驾驶(intelligent network driving)、汽车共享(car sharing)等。
本申请涉及到的网元包括通信***中的网络设备和终端。参见图1，本申请实施例提供的方法主要涉及终端和终端之间的通信。
本申请实施例中的通信***包括但不限于长期演进(long term evolution，LTE)***、第五代(5th-generation，5G)***、新无线(new radio，NR)***，无线局域网(wireless local area networks，WLAN)***以及未来演进***或者多种通信融合***。其中，5G***可以为非独立组网(non-standalone，NSA)的5G***或独立组网(standalone，SA)的5G***。
本申请实施例中的网络设备为网络侧的一种用于发送信号，或者，接收信号，或者，发送信号和接收信号的实体。网络设备可以为部署在无线接入网(radio access network，
RAN)中为终端提供无线通信功能的装置，例如可以为传输接收点(transmission reception point，TRP)、基站、各种形式的控制节点(例如，网络控制器、无线控制器(例如，云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器))等。具体的，网络设备可以为各种形式的宏基站，微基站(也称为小站)，中继站，接入点(access point，AP)等，也可以为基站的天线面板。所述控制节点可以连接多个基站，并为所述多个基站覆盖下的多个终端配置资源。在采用不同的无线接入技术的***中，具备基站功能的设备的名称可能会有所不同。例如，LTE***中可以称为演进型基站(evolved NodeB，eNB或eNodeB)，5G***或NR***中可以称为下一代基站节点(next generation node base station，gNB)，本申请对基站的具体名称不作限定。网络设备还可以是未来演进的公共陆地移动网络(public land mobile network，PLMN)中的网络设备等。
本申请实施例中的终端是用户侧的一种用于接收信号，或者，发送信号，或者，接收信号和发送信号的实体。终端用于向用户提供语音服务和数据连通***中的一种或多种。终端还可以称为用户设备(user equipment，UE)、终端设备、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端可以是V2X设备，例如，智能汽车(smart car或intelligent car)、数字汽车(digital car)、无人汽车(unmanned car或driverless car或pilotless car或automobile)、自动汽车(self-driving car或autonomous car)、纯电动汽车(pure EV或Battery EV)、混合动力汽车(hybrid electric vehicle，HEV)、增程式电动汽车(range extended EV，REEV)、插电 式混合动力汽车(plug-in HEV，PHEV)、新能源汽车(new energy vehicle)、路边装置(road site unit，RSU)。终端也可以是D2D设备，例如，电表、水表等。终端还可以是移动站(mobile station，MS)、用户单元(subscriber unit)、无人机、物联网(internet of things，IoT)设备、WLAN中的站点(station，ST)、蜂窝电话(cellular phone)、智能电话(smart phone)、无绳电话、无线数据卡、平板型电脑、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备(也可以称为穿戴式智能设备)。终端还可以为下一代通信***中的终端，例如，5G***中的终端或者未来演进的PLMN中的终端，NR***中的终端等。
为了使得本申请实施例更加的清楚，以下对与本申请实施例相关的概念和部分内容作简单介绍。
1、上行链路(uplink，UL)、下行链路(downlink，DL)、SL
终端向网络设备发送数据(即上行数据)的无线通信链路可以称为UL。网络设备向终端发送数据(即下行数据)的无线通信链路可以称为DL。UL接口和DL接口可以统称为Uu口，因此，UL和DL可以统称为Uu口链路。
终端和终端之间的直连通信的通信链路可以称为SL。SL也可以称为边链路。终端和终端之间传输的数据可以称为SL数据。
示例性的，本申请实施例中的数据可以理解为传输块(transport block，TB)或媒介接入控制(medium access control，MAC)协议数据单元(protocol data unit，PDU)。数据也可以称为数据包或报文。
2、SL的资源配置模式
两个终端中的发送终端所采用的SL传输资源可以通过以下方式A和方式B中的任意一种确定。
方式A、网络设备调度
网络设备调度SL传输资源的模式可以包括模式1(mode1)资源配置模式(NR中的名称)或者模式3(mode3)资源配置模式(LTE中的名称)。
其中，网络设备调度的SL传输资源有以下两种类型：
第一种：SL配置授权(configured grant，CG)资源
该情况下，发送终端的每次数据传输并不总是需要网络设备单独分配资源，网络设备在某次为发送终端分配资源之后，未来一段时间内，发送终端都可以使用上述分配的资源，特点是“一次分配，多次使用”。示例性的，网络设备可以为发送终端配置一段周期性出现的时域资源。示例性的，参见图2，该段周期性出现的时域资源中第一次出现的时域资源为时隙1的符号4至符号9，周期为1个时隙。其中，每次出现的时域资源为一个SL的授权(SL grant，下文中简称为侧行授权)，则可以理解的是，图2中示出了4个侧行授权，1个侧行授权对应1个侧行授权ID，则4个侧行授权对应的侧行授权ID分别为侧行授权0、侧行授权1、侧行授权2和侧行授权3。
SL CG资源可以包括SL类型1(type1)CG(SL configured grant type 1)资源、SL类型2(type2)CG(SL configured grant type 2)资源。SL type1CG资源可以是网络设备通过无线资源控制(radio resource control，RRC)信令直接配置给发送终端的SL传输资源，发送终端可以直接使用该CG资源传输数据，不需要额外的激活。SL type1CG资源也可以称为SL免授权(SL grant free)资源。SL type2CG资源可以是网络设备通过RRC信令定义SL传输资源的周期，再通过物理下行控制信道(physical downlink control channel，PDCCH)或下行控制信息(downlink control information，DCI)激活该SL传输资源，发送终端不能直接使用该SL传输资源传输数据，激活之后才能使用。SL type2CG资源也可以称为SL半静态调度(SL Semi-Persistent Scheduling，SL SPS)资源。
针对SL，一个载波上可以支持一个或多个CG资源。可选的，不同的SL CG资源可以对应不同的索引。示例性的，索引为1、2、3的CG资源可以分别记为SL CG1、SL CG2、SL CG3。
第二种：SL动态授权(dynamic grant，DG)资源
比如，可以是网络设备通过DCI动态分配给发送终端的SL传输资源。DCI可以承载在PDCCH中。
方式B、发送终端自行确定
示例性的，发送终端自行确定SL传输资源的模式可以包括模式2(mode2)资源配置模式(NR中的名称)或者模式4(mode4)资源配置模式(LTE中的名称)。
在方式B中，发送终端在网络设备通信覆盖范围内时，网络设备可以通过***广播(system information block，SIB)消息或专用RRC信令为发送终端配置SL资源池，发送终端可以自主从SL资源池中获取SL传输资源来发送控制信号和/或数据信号给接收终端。发送终端在网络设备通信覆盖范围外时，发送终端可以自主从预配置的SL资源池中获取SL传输资源来发送控制信号和/或数据信号给接收终端。
在从SL资源池中获取SL传输资源时，发送终端可以感知或竞争SL传输资源。具体的，发送终端通过和其他终端竞争获得SL资源池中的合适的SL传输资源来发送控制信号和/或数据信号。例如，发送终端中待传输的V2X业务或数据的优先级越高，其竞争到SL资源池中的合适的SL传输资源的机会就越大。
为了方便描述，本申请将mode1资源配置模式、mode2资源配置模式、mode3资源配置模式、mode4资源配置模式分别简称为mode1、mode2、mode3和mode4。一种可能的情况，在LTE V2X中，mode3和mode4不可以同时存在。一种可能的情况，在NR V2X中，mode1和mode2也不可以同时存在。
3、侧行链路控制信息(sidelink control information，SCI)
类似于调度Uu口数据的DCI，SCI用于调度SL数据。例如，第一级SCI中可以承载SL数据的控制信息。SCI可以在物理侧行链路控制信道(physical sidelink control channel，PSCCH)上传输。
4、HARQ
HARQ是一种结合前向纠错(或者说前向纠错码)(forward error correction，FEC)与自动重传请求(automatic repeat request，ARQ)方法的技术。
其中，FEC是指发送端发送的数据中包括前向纠错码或冗余信息，当接收端接收到数据后，通过校验(例如，循环冗余校验(cyclic redundancy check，CRC)校验)发现错误之后，能够通过前向纠错码或冗余信息进行纠正，这样发送端可以减少重传(即重新传输数据)的次数。
ARQ是指接收端通过校验(例如，CRC校验)判断接收到的数据的正确性，如果数据接收正确，接收端发送肯定确认(acknowledgement，ACK)告知发送端，否则接收端发送否定确认(negative acknowledgement，NACK)告知发送端，发送端接收到NACK时，可以重传数据给接收端。ACK和NACK即HARQ反馈。
LTE V2X中由于仅支持广播业务，因此，不支持SL HARQ反馈。NR V2X中支持单播、组播和广播业务，支持SL HARQ反馈。
以下通过(a)至(c)三部分内容对与HARQ相关的内容具体进行介绍。
(a)HARQ进程
HARQ使用停等协议(stop-and-wait protocol)来发送数据。在停等协议中，发送端发送一个传输块(transport block，TB)后，就停下来等待确认信息。接收端可以针对该TB反馈ACK或NACK。但是每次传输后发送端就停下来等待确认，会导致吞吐量很低。因此，发送端可以使用多个并行的HARQ进程：当一个HARQ进程在等待确认时，发送端可以使用另一个HARQ进程来继续发送数据。示例性的，参见图3，终端采用第1个HARQ进程发送TB1，在T1时刻发送完TB1，在T2时刻接收TB1的HARQ反馈，在T1到T2这一时间段内，等待TB1的确认，在等待确认的这段时间内，可以采用第2个HARQ进程发送TB2，在T2时刻发送完TB2，在T3时刻接收TB2的HARQ反馈，在T2到T3这一时间段内，等待TB2的确认，在等待确认的这段时间内，可以采用第3个HARQ进程发送TB3。
一个HARQ进程通过一个HARQ进程ID来标识。侧行授权与HARQ进程关联，终端在与该HARQ进程关联的侧行授权采用该进程传输HARQ数据。
(b)接收端对新传数据和重传数据的处理机制
每个HARQ进程在接收端有对应的缓存(例如，HARQ buffer或soft buffer)，以便对接收到的数据进行软合并解码。
接收端接收到发送端采用一个HARQ进程发送的新传数据后，可以将接收到的新传数据放入该HARQ进程对应的缓存中，进行解码。若解码失败，再次接收到该新传数据的重传数据时，可以将接收到的重传数据和之前存储在缓存中的新传数据进行合并，放入缓存中，再次解码，这种方式可以称为软合并解码，相比于单独解码(即每次传输的数据都单独解码，不和之前的数据合并进行解码)，提高了解码成功的几率。同样，若解码仍然失败，可以继续重复上述过程，将新接收到的重传数据与缓存中的数据进行合并，并再次解码。
其中，发送端的重传数据和新传数据可以为同一个TB的同一个冗余版本(redundancy version，RV)或不同的RV。
Uu口上的HARQ进程称为HARQ进程，SL上的HARQ进程可以称为SL进程(SL process)。
(c)基于SL进程的SL数据传输
一个发送终端可以和多个接收终端进行通信，即，一个发送终端可以向多个接收终端发送SCI和SL数据。一个接收终端也可以和多个发送终端进行通信，即，一个接收终端可以接收来自多个发送终端的SCI和SL数据。SCI中可以包含SL进程ID、第一目的ID(destination ID)、第一源ID(source ID)和通信类型。
其中，SL进程ID用于标识SL进程，与Uu口的HARQ进程ID类似。
第一目的ID可以用于标识SCI调度的SL数据的目的(target)。可选的，第一目的ID可以用于接收终端的PHY层进行数据包过滤。可选的，第一目的ID可以为第二目的ID的一部分比特位。例如，第二目的ID为24比特(bit)，第一目的ID为第二目的ID的低16位。
第二目的ID用于标识数据的目的(例如，target)/接收端/接收终端。示例性的，第二目的ID用于标识一个组播或广播业务。示例性的，第二目的ID可以为目的/接收端/接收终端的标识。示例性的，第二目的ID可以为目的层2 ID(Destination Layer-2 ID)。可选的，第二目的ID可以用于接收终端的MAC层进行数据包过滤。
第一源ID用于标识SCI调度的SL数据的源(source)。可选的，第一源ID可以用于接收终端的PHY层进行数据包过滤。可选的，第一源ID可以为第二源ID的一部分比特位。例如，第二源ID为24bit，第一源ID为第二源ID的低8位。
第二源ID(source ID)用于标识数据的源(例如，sender)/发送端/发送终端。示例性的，第二源ID可以为源/发送端/发送终端的标识。示例性的，第二源ID可以为源层2 ID(source Layer-2 ID)。可选的，第二源ID可以用于接收终端的MAC层进行数据包过滤。
通信类型可以包括单播、组播、广播中的任一个或多个。SCI中的通信类型用于指示当前的通信为单播、组播还是广播，或，用于指示该SCI调度的SL数据为单播数据、组播数据还是广播数据。
例如，接收终端可以检测周围的SCI，然后再根据SCI中的第一目的ID、第一源ID和通信类型确定该SCI或SCI调度的SL数据是否是其感兴趣的。若感兴趣，再继续接收SCI调度的SL数据。
在发送侧，包含一个SL HARQ实体，该SL HARQ实体维护的所有的SL进程(例如，16个)由所有的连接/通信类型(casttype)共享。在接收侧，包含一个SL HARQ实体，该SL HARQ实体维护的所有的SL进程(例如，64个)由所有的连接/通信类型共享。
不同的发送终端可能会使用相同的SL进程ID与同一个接收终端进行通信，对于接收终端来说，为了能够区分来自不同发送终端的、与相同SL进程ID关联的数据，接收终端接收到一个SCI和/或数据，判断该数据是新传数据之后，会为该数据选择一个未被占用的SL进程(记为SL进程1)，并将SCI中的“SL进程ID+第一目的ID+第一源ID+通信类型”与SL进程1相关联。等到接收终端再次接收到与相同“SL进程ID+第一目的ID+第一源ID+通信类型”对应的重传数据，就可以将重传数据放入SL进程1的缓存中，以便对接收到的数据进行软合并解码。其中，“第一目的ID+第一源ID+通信类型”可以称为SL识别信息(sidelink identification information)。
5、MAC重置(MAC reset)
在Uu口，终端确定进行MAC重置(例如，终端的MAC层的上层请求MAC重置)， 终端的MAC实体会执行以下任一项或多项：停止运行的定时器、取消触发的波束失败恢复(beam failure recovery，BFR)、取消触发的调度请求(scheduling request，SR)、重置MAC相关的计数器(例如，LBT_COUNTER、BFI_COUNTER等)、停止正在进行的随机接入过程等。具体的内容可以参考TS 38.321的5.12节，此处不再赘述。
目前，在SL上，终端确定进行MAC重置(例如，终端的MAC层的上层请求针对一个SL的RRC连接进行MAC重置)，终端的MAC实体会执行以下任一项或多项：取消触发的、仅与该SL的RRC连接关联的SR，取消触发的、仅与该SL的RRC连接关联的SL BSR，清空与该SL的RRC连接关联的SL进程的soft buffer。具体的内容可以参考TS 38.321的5.12节，此处不再赘述。
目前，针对一个SL的RRC连接，发生SL无线链路失败(radio link failure，RLF)，或者，接收终端的MAC层接收到全配置(fullconfig)的SL RRC重配(RRCReconfigurationSidelink)消息，则接收终端针对该SL的RRC连接进行MAC重置。
全配置的SL RRC重配消息可以理解为：SL RRC重配消息中包括全配置的指示。其中，全配置的指示用于指示SL RRC重配消息应采用全配置。例如，全配置的指示为“sl-ResetConfig”。
例如，全配置(fullconfig)的SL RRC重配消息表示：针对一个SL的RRC连接，对接收终端进行全部的重配置，也就是针对该SL的RRC连接，对全部的配置进行更新。对于单播传输，发送终端通过SL RRC重配消息给接收终端发送SL的配置。当SL RRC重配消息中包含参数“sl-ResetConfig”时，表示对SL进行全部的SL的配置。
以上是对与本申请实施例相关的概念和部分内容作的简单介绍。
目前，一方面，针对SL进程，接收终端在下述两种情况下将SL进程视为未被占用：
1)接收终端解码数据成功，将该数据对应的SL进程视为未被占用的。
2)接收终端再次接收相同“SL进程ID+第一目的ID+第一源ID+通信类型”对应的调度新传SL数据的SCI或新传SL数据，将该“SL进程ID+第一目的ID+第一源ID+通信类型”对应的SL进程视为未被占用的。具体的，接收终端判断一个调度新传SL数据的SCI中的“SL进程ID+第一目的ID+第一源ID+通信类型”是否与一个SL进程(记为SL进程2)关联，若关联，会将SL进程2视为未被占用的、并清空SL进程2的缓存，并且为该调度新传SL数据的SCI或者说该新传数据选择一个未被占用的SL进程(记为SL进程3)，且将SL进程3与该SCI中的“SL进程ID+第一目的ID+第一源ID+通信类型”关联。
另一方面，针对一个SL的RRC连接，接收终端执行SL MAC重置，接收终端会清空与该SL的RRC连接关联的所有SL进程的缓存。
目前的SL进程的处理会存在如下问题：
针对接收侧，接收终端在发生事件1(接收终端确定针对SL的RRC连接进行MAC重置或接收终端针对SL的RRC连接进行MAC重置)、事件2(SL的RRC连接释放)和事件3(接收终端不再接收组播和/或广播数据)时，未释放SCI(或者说“SL进程ID+第一目的ID+第一源ID+通信类型”)和SL进程之间的关联关系，也未将SL进程视为未被占用。会存在如下问题:
一方面，未将SL进程视为未被占用，使得这些SL进程无法用于其他数据的接收，导致可用的SL进程数量减少。
另一方面，若仅仅是将SL进程视为未被占用，未释放SCI和SL进程之间的关联关系，接收终端再次接收到该SCI(既包含的“SL进程ID+第一目的ID+第一源ID+通信类型”与之前的SCI相同的SCI)调度的新传SL数据，由于SCI和SL进程之间的关联关系的存在，接收终端可能会错误的清空掉该SL进程的缓存中的其他数据。示例性的，参见图4，若接收终端接收SCI1(包含“SL进程ID1+第一目的ID1+第一源ID1+单播”)，SCI1用于调度新传的数据1，接收终端接收到SCI1之后，将“SL进程ID1+第一目的ID1+第一源ID1+单播”与SL进程1关联。后续过程中，接收终端针对SL的RRC连接进行MAC重置时，将与该SL的RRC连接关联的SL进程1确定为未被占用，但未释放“SL进程ID1+第一目的ID1+第一源ID1+单播”与SL进程1之间的关联关系。若接收终端接收SCI2(包含“SL进程ID2+第一目的ID2+第一源ID2+单播”)，SCI2用于调度新传的数据2，此时，接收终端需要为“SL进程ID2+第一目的ID2+第一源ID2+单播”选择一个未被占用的SL进程，若选择的未被占用的SL进程为SL进程1，若数据2未被成功接收，则SL进程1的缓存中包含数据2。此时，若接收终端接收SCI3(包含“SL进程ID1+第一目的ID1+第一源ID1+单播”)，SCI3用于调度新传的数据3，也就是说，接收终端再次接收到“SL进程ID1+第一目的ID1+第一源ID1+单播”对应的调度新传SL数据的SCI或新传SL数据，由于“SL进程ID1+第一目的ID1+第一源ID1+单播”与SL进程1之间的关联关系还存在，因此，接收终端会将与“SL进程ID1+第一目的ID1+第一源ID1+单播”关联的SL进程1的缓存清空并将SL进程1视为未被占用的，而此时，SL进程1的缓存中还有数据2待处理，因此，终端会错误的将数据2清空，影响数据2的接收。或者，因为错误的将SL进程1视为未被占用，在数据2的传输还未成功的情况下，可能将SL进程1用于其他的数据接收，影响数据2的接收。
针对发送终端,发送终端在发生上述事件1、事件2和事件3时，未将SL进程视为未被占用，未清空SL进程的缓存。会存在如下问题:未将SL进程视为未被占用，使得这些SL进程无法用于其他数据的发送，导致可用的SL进程数量减少；未清空SL进程的缓存，可能使得这些SL进程无法用于其他数据的发送，导致可用的SL进程数量减少，或，缓存较大，或，错误的触发重传。
为了解决这些问题，本申请提供了一种处理SL进程的方法，包括实施例一至实施例五，以下分别进行描述。
实施例一
实施例一可以解决由于接收终端发生事件1时，未释放SCI和SL进程之间的关联关系，和/或，未将SL进程视为未被占用所导致的问题。参见图5，该方法包括：
501、终端确定对SL的RRC连接进行MAC重置。
步骤501也可以描述为：终端对SL的RRC连接进行MAC重置。其中，终端可以为接收终端。
本申请各个实施例中，示例性的，SL的RRC连接可以为：一对第二源ID和第二目的ID之间的逻辑连接；或，在接入层(access-stratum，AS)层，一对第二源ID和第二目的ID之间的逻辑连接。SL的RRC连接也可以称为PC5-RRC连接。本申请各个实施例中，SL的RRC连接可以包括/替换为/对应以下任一项或多项：单播、单播连接、目的地址、第二源ID和第二目的ID对(pair)、第二目的ID。本申请各个实施例中，示例 性的，SL的RRC连接可以理解为/替换为：一个SL的RRC连接，或，一个单播，或，一个单播连接，或，一个目的地址，或，一对第二源ID和第二目的ID，或，一个第二源ID和一个第二目的ID对，或，一个第二目的ID。例如，第一SL的RRC连接可以理解为/替换为：第一单播，或，第一单播连接，或，第一目的地址，或，第二源ID1和第二目的ID1对，或，第二目的ID1。
本申请各个实施例中，示例性的，目的地址(destination)用于标识一个单播，或，一个组播，或，一个广播。
本申请各个实施例中，示例性的，第二源ID和第二目的ID对用于标识一个单播。
本申请各个实施例中，针对SL的RRC连接进行MAC重置可以包括/替换/理解为：针对SL的RRC连接进行SL特定的MAC重置(Sidelink specific reset of the MAC entity)。
本申请各个实施例中，示例性的，SL的RRC连接、单播连接、目的地址、第二源ID和第二目的ID对、第二目的ID、第二源ID、第二源ID对应的第一源ID和第二目的ID对应的第一目的ID对、第二目的ID对应的第一目的ID、第二源ID对应的第一源ID中的任2项或多项之间可以相关联/相对应。
需要说明的是，步骤501并未限定终端是否已经针对SL的RRC连接进行了MAC重置。例如，步骤501可以理解为：终端将/准备针对SL的RRC连接进行MAC重置。
502、终端将第一SL进程确定为未被占用；和/或，终端释放与第一SL进程关联的关联关系。
其中，第一SL进程为/包括与SL的RRC连接关联的SL进程。示例性的，第一SL进程可以为/包括与SL的RRC连接关联的一个或多个或所有SL进程。
与SL的RRC连接关联的SL进程可以理解为：与SL的RRC连接对应的第二源ID和第二目的ID关联的SL进程，或，与SL的RRC连接对应的第一源ID和第一目的ID关联的SL进程。例如，一个SL的RRC连接对应的第二源ID和第二目的ID为第二源ID1和第二目的ID2，与该SL的RRC连接关联的SL进程为与第二源ID1和第二目的ID2关联的SL进程。例如，一个SL的RRC连接对应的第二源ID和第二目的ID为第二源ID1和第二目的ID2，第二源ID1和第二目的ID2对应的第一源ID和第一目的ID为第一源ID1和第一目的ID2，与该SL的RRC连接关联的SL进程为与第一源ID1和第一目的ID2关联的SL进程。
本申请各个实施例中，第一SL进程或与SL的RRC连接关联的SL进程可以包括/替换为以下任一项或多项：与单播连接关联的SL进程，与目的地址关联的SL进程，与第二目的ID关联的SL进程，与第二源ID和第二目的ID对关联的SL进程，与第一目的ID关联的SL进程，与第一源ID和第一目的ID对关联的SL进程。示例性的，与第一SL进程关联的关联关系，包括：第一SL进程与SCI之间的关联关系，和/或，第一SL进程与SL进程ID、第一目的ID、第一源ID和通信类型中的一个或多个之间的关联关系。
本申请各个实施例中，将SL进程确定为未被占用可以包括/替换为以下任一项或多项：将SL进程视为未被占用，释放SL进程，去激活SL进程。例如，将第一SL进程确定为未被占用可以理解为释放第一SL进程。
本申请各个实施例中，释放与SL进程关联的关联关系可以包括/替换为：删除与 SL进程关联的关联关系。例如，释放与第一SL进程关联的关联关系可以包括/替换为：删除与第一SL进程关联的关联关系。
示例性的，参见图6，终端中存在的或终端中之前存在的与SL进程关联的关联关系可参见图6中的左侧，若终端确定针对一个SL的RRC连接进行MAC重置，其中该SL的RRC连接对应的第一源ID和第一目的ID分别为第一源ID1和第一目的ID1，与该SL的RRC连接关联的SL进程为SL进程1和SL进程2，终端释放SL进程1和SL进程2，和/或，释放与SL进程1和SL进程2关联的关联关系。在这种情况下，终端中存在的与SL进程关联的关联关系可参见图6中的右侧。需要说明的是，图6所示的与SL进程关联的关联关系仅仅为一个示例，在实际实现时，与SL进程关联的关联关系可以为其他，本申请不作限制。
可选的，步骤501包括以下动作中的一个或多个：(1)终端的MAC层的上层请求针对SL的RRC连接进行MAC重置；(2)终端的MAC层/终端被请求针对SL的RRC连接进行MAC重置；(3)终端的MAC层的上层请求终端的MAC层针对SL的RRC连接进行MAC重置；(4)终端的MAC层确定针对SL的RRC连接进行MAC重置；(5)终端的MAC层针对SL的RRC连接进行MAC重置。
可选的，终端将第一SL进程确定为未被占用，包括：终端的MAC层将第一SL进程确定为未被占用。
可选的，终端释放与第一SL进程关联的关联关系，包括：终端的MAC层释放与第一SL进程关联的关联关系。
示例性的，终端的MAC层具体可以为终端的MAC实体。
示例性的，MAC层的上层可以为RRC层、无线链路控制(radio link control，RLC)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层等。
可选的，终端在满足条件3的情况下，执行步骤501或上述(1)-(5)中的任一个或多个动作。其中，条件3包括以下中的任意一个或多个：终端的RRC层的上层请求终端的RRC层释放SL的RRC连接；终端的RRC层的上层请求释放SL的RRC连接；终端的RRC层的上层指示终端的RRC层的上层的SL单播连接(PC5unicast link)释放；终端的RRC层的上层向终端的RRC层指示终端的RRC层的上层的SL单播连接释放；终端的RRC层的上层的SL单播连接释放；终端的RRC层/终端被请求释放SL的RRC连接；终端的RRC层/终端被指示终端的RRC层的上层的SL单播连接释放；终端的RRC层/终端释放SL的RRC连接。
也就是说，触发终端确定对SL的RRC连接进行MAC重置或终端对SL的RRC连接进行MAC重置的条件除了条件1(发生SL RLF)和条件2(终端接收到全配置的SL RRC重配消息)之外，还可以有条件3。
本申请各个实施例中，示例性的，终端的RRC层的上层可以为V2X层、非接入层(non-access stratum，NAS)层、应用(application，APP)层等。
本申请各个实施例中，请求可以包括/替换/理解为以下任一项或多项：配置，指示。
实施例一提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的接收，避免可用的SL进程数量减少，可以提高数据接收 的速率。实施例一提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，通过将与第一SL进程关联的关联关系释放，从而避免终端错误的清空掉其他数据，或者，确保与第一SL进程关联的数据的接收，可以提高数据接收的可靠性。
实施例二
实施例二可以解决由于发送终端发生事件1时，未将SL进程视为未被占用，和/或，未清空SL进程的缓存所导致的问题。参见图7，该方法包括：
701、终端确定对SL的RRC连接进行MAC重置。
步骤701也可以描述为：终端对SL的RRC连接进行MAC重置。其中，终端可以为发送终端。关于步骤701的相关描述可参见步骤501，不再赘述。
702、终端将第一SL进程确定为未被占用；和/或，终端清空第一SL进程的缓存。
实施例二中“第一SL进程”的相关描述可参加实施例一，不再赘述。
实施例二中“将SL进程确定为未被占用”的相关描述可参加实施例一，不再赘述。
本申请各个实施例中，清空SL进程的缓存可以包括/替换为：删除SL进程的缓存。例如，清空第一SL进程的缓存可以包括/替换为：删除第一SL进程的缓存。示例性的，若终端确定针对一个SL的RRC连接进行MAC重置，其中，该SL的RRC连接对应的第一源ID和第一目的ID分别为第一源ID1和第一目的ID1，与该SL的RRC连接关联的SL进程为与第一源ID1和第一目的ID1关联的SL进程(例如，SL进程1和SL进程2)，终端释放SL进程1和SL进程2，和/或，清空SL进程1和SL进程2的缓存。
可选的，步骤701包括以下动作中的一个或多个：(1)终端的MAC层的上层请求针对SL的RRC连接进行MAC重置；(2)终端的MAC层/终端被请求针对SL的RRC连接进行MAC重置；(3)终端的MAC层的上层请求终端的MAC层针对SL的RRC连接进行MAC重置；(4)终端的MAC层确定针对SL的RRC连接进行MAC重置；(5)终端的MAC层针对SL的RRC连接进行MAC重置。
可选的，终端将第一SL进程确定为未被占用，包括：终端的MAC层将第一SL进程确定为未被占用。
可选的，终端清空第一SL进程的缓存，包括：终端的MAC层清空第一SL进程的缓存。关于该可选的方法的相关描述可参见实施例一，不再赘述。示例性的，终端的MAC层具体可以为终端的MAC实体。
可选的，终端在满足条件3的情况下，执行步骤701或上述(1)-(5)中的任一个或多个动作。其中，关于条件3的描述可参见实施例一，不再赘述。
可选的，终端在满足条件4的情况下，执行步骤701或上述(1)-(5)中的任一个或多个动作。其中，条件4可以为：终端发送SL RRC重配消息，或者，终端发送SL RRC重配消息、且终端接收到SL RRC重配完成消息。其中，SL RRC重配消息包括全配置的指示。其中，SL RRC重配消息与SL的RRC连接相关联。SL RRC重配完成消息与SL的RRC连接相关联。SL RRC重配完成消息与SL RRC重配消息相对应。
示例性的，若终端发送针对一个SL的RRC连接的SL RRC重配消息，或，若终端发送针对一个SL的RRC连接的SL RRC重配消息且收到SL RRC重配完成消息，其中， SL RRC重配消息包括全配置的指示。其中，该SL的RRC连接对应的第一源ID和第一目的ID分别为第一源ID1和第一目的ID1，与该SL的RRC连接关联的SL进程为与第一源ID1和第一目的ID1关联的SL进程(例如，SL进程1和SL进程2)，终端将SL进程1和SL进程2确定为未被占用，和/或，清空SL进程1和SL进程2的缓存。
具体的，针对终端发送SL RRC重配消息，终端确定对SL的RRC连接进行MAC重置的情况，终端可以在设置SL RRC重配消息，或，发送SL RRC重配消息时/前/后确定对SL的RRC连接进行MAC重置，本申请不作限制。其中，设置可以理解为生成或确定。
其中，发送SL RRC重配消息具体可以由终端的RRC层执行。
也就是说，触发终端确定对SL的RRC连接进行MAC重置或终端对SL的RRC连接进行MAC重置的条件除了条件1(发生SL RLF)和条件2(终端接收到全配置的SL RRC重配消息)之外，还可以有条件3和/或条件4。
需要说明的是，终端也可以在发送SL RRC重配消息，或者，发送SL RRC重配消息、且终端接收到SL RRC重配完成消息的情况下，直接执行步骤702。
实施例二提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。实施例二提供的方法，可以在终端确定针对SL的RRC连接进行MAC重置或终端针对SL的RRC连接进行MAC重置的情况下，通过清空第一SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。
实施例三
实施例三可以解决由于接收终端发生事件2时，未执行释放SCI和SL进程之间的关联关系、将SL进程视为未被占用以及清空SL进程的缓存中的一个或多个动作所导致的问题，还可以解决发送终端发生事件2时，未将SL进程视为未被占用，和/或，未清空SL进程的缓存所导致的问题。参见图8，该方法包括：
801、终端释放SL的RRC连接。也就是说，终端不再接收或发送单播数据。
其中，终端可以为发送终端或接收终端。关于SL的RRC连接的相关描述可参见实施例一，不再赘述。
802、终端执行以下动作中的一个或多个：终端将第一SL进程确定为未被占用，终端释放与第一SL进程关联的关联关系，终端清空第一SL进程的缓存。
其中，第一SL进程为/包括与SL的RRC连接关联的SL进程。示例性的，第一SL进程可以为/包括与SL的RRC连接关联的一个或多个或所有SL进程。关于“第一SL进程”或“与SL的RRC连接关联的SL进程”的相关描述可参见实施例一，不再赘述。可选的，终端为接收终端时，与第一SL进程关联的关联关系，包括：第一SL进程与SCI之间的关联关系，和/或，第一SL进程与SL进程ID、第一目的ID、第一源ID和通信类型中的一个或多个之间的关联关系。
实施例三中，“将SL进程确定为未被占用”和“释放与SL进程关联的关联关系”的 相关描述可参见实施例一，“清空SL进程的缓存”的相关描述可参见实施例二，不再赘述。
示例性的，若终端释放SL的RRC连接，其中，该SL的RRC连接对应的第一源ID和第一目的ID分别为第一源ID1和第一目的ID1，与该SL的RRC连接关联的SL进程为与第一源ID1和第一目的ID1关联的SL进程(例如，SL进程1和SL进程2)，终端执行以下动作中的一个或多个：将SL进程1和SL进程2确定为未被占用，清空SL进程1和SL进程2的缓存，释放与SL进程1和SL进程2关联的关联关系。
可选的，终端释放SL的RRC连接，包括：终端的RRC层释放SL的RRC连接，或，终端的RRC层的上层请求释放RRC连接。
可选的，终端将第一SL进程确定为未被占用，包括：终端的MAC实体将第一SL进程确定为未被占用。
可选的，终端释放与第一SL进程关联的关联关系，包括：终端的MAC实体释放与第一SL进程关联的关联关系。
可选的，终端清空第一SL进程的缓存，包括：终端的MAC实体清空第一SL进程的缓存。
可选的，在满足条件3的情况下，终端的RRC层释放SL的RRC连接。
实施例三提供的方法，可以在终端释放SL的RRC连接的情况下，将第一SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例三提供的方法，可以在终端释放SL的RRC连接的情况下，通过清空第一SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例三提供的方法，可以在终端释放SL的RRC连接的情况下，通过将与第一SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据，可以提高数据接收的可靠性，或者，确保与第一SL进程关联的数据的接收，可以提高数据接收的可靠性。
实施例四
实施例四可以解决由于接收终端发生事件3时，未执行释放SCI和SL进程之间的关联关系、将SL进程视为未被占用以及清空SL进程的缓存中的一个或多个所导致的问题，还可以解决发送终端发生事件3时，未将SL进程视为未被占用，和/或，未清空SL进程的缓存所导致的问题。参见图9，该方法包括：
901、针对一个目的地址，终端不再发送或接收SL数据。
其中，目的地址(destination)用于标识一个组播，或，一个广播，或一个单播。
本申请各个实施例中，目的地址可以包括/替换为/对应以下任一项或多项：组播、组播业务、广播、广播业务、单播、单播连接、SL的RRC连接、第二源ID和第二目的ID对(pair)、第二目的ID、第一源ID和第一目的ID对(pair)、第一目的ID。
本申请各个实施例中，目的地址也可以包括/替换为/对应以下任一项或多项：一个目的地址、一个组播、一个组播业务、一个广播、一个广播业务、一个SL的RRC连接，或，一个单播，或，一个单播连接，或，一个目的地址，或，一对第二源ID和第二目的ID，或，一个第二源ID和一个第二目的ID对，或，一个第二目的ID，或， 一对第一源ID和第一目的ID，或，一个第一源ID和一个第一目的ID对，或，一个第一目的ID。例如，第一目的地址可以理解为/替换为：第一组播、第一组播业务、第一广播、第一广播业务、第一SL的RRC连接，或，第一单播，或，第一单播连接，或，第一目的地址，或，第二源ID1和第二目的ID1对，或，第二目的ID1，或，第一源ID1和第一目的ID1对，或，第一目的ID1。
需要说明的是，不再发送或接收可以理解为：之前有发送或接收，目前不(再)发送或接收，并没有限定将来一直不发送或不接收。902、终端执行以下动作中的一个或多个：终端将第二SL进程确定为未被占用；终端释放与第二SL进程关联的关联关系；终端清空第二SL进程的缓存。示例性的，步骤902的动作可以由终端的MAC层执行。
其中，第二SL进程为/包括与目的地址关联的SL进程。示例性的，第二SL进程可以为/包括与目的地址关联的一个或多个或所有SL进程。
与目的地址关联的SL进程可以理解为：与目的地址对应的第二目的ID关联的SL进程，或，与目的地址对应的第一目的ID关联的SL进程。例如，一个目的地址对应的第二目的ID为第二目的ID2，与该目的地址关联的SL进程为与第二目的ID2关联的SL进程。例如，一个目的地址对应的第二目的ID为第二目的ID2，第二目的ID2对应的第一目的ID为第一目的ID2，与该目的地址关联的SL进程为与第一目的ID2关联的SL进程。本申请各个实施例中，第一SL进程或与目的地址关联的SL进程可以包括/替换为以下任一项或多项：与组播/组播业务关联的SL进程，与广播/广播业务关联的SL进程，与第二目的ID关联的SL进程，与第一目的ID关联的SL进程。
示例性的，终端为接收终端时，与第二SL进程关联的关联关系，包括：第二SL进程与SCI之间的关联关系，和/或，第二SL进程与SL进程ID、第一目的ID、第一源ID和通信类型中的一个或多个之间的关联关系。
实施例四中，“将SL进程确定为未被占用”和“释放与SL进程关联的关联关系”的相关描述可参见实施例一，“清空SL进程的缓存”的相关描述可参见实施例二，不再赘述。
示例性的，参见图10，以组播为例，终端中存在的或终端中之前存在的与SL进程关联的关联关系可参见图10中的左侧，若针对一个目的地址，终端不再接收SL数据，其中该目的地址对应的第一源ID和第一目的ID分别为第一源ID2和第一目的ID2，则与该目的地址关联的SL进程为SL进程3和SL进程4，终端释放SL进程3和SL进程4，和/或，释放与SL进程3和SL进程4关联的关联关系。在这种情况下，终端中存在的与SL进程关联的关联关系可参见图10中的右侧。需要说明的是，图10所示的与SL进程关联的关联关系仅仅为一个示例，在实际实现时，与SL进程关联的关联关系可以为其他，本申请不作限制。
可选的，终端不再发送或接收SL数据，包括：目的地址对应的传输终止，或，终端不需要发送或接收目的地址对应的SL数据(也就是终端对目的地址对应的传输不再感兴趣)。
目的地址对应的传输可以包括：目的地址对应的组播传输或广播传输。
目的地址对应的传输终止可以理解为：目的地址对应的组播传输或广播传输终止。 也就是说，针对该目的地址的组播或广播终止/不再发送。
终端不需要发送或接收目的地址对应的SL数据可以包括：终端确定不需要发送或接收目的地址对应的SL数据；终端对目的地址对应的传输不再感兴趣。
需要说明的是，不再感兴趣可以理解的是，之前感兴趣，目前不(再)感兴趣，并没有限定将来一直不感兴趣。
具体的，终端的RRC层的上层可以请求(或者说指示或者说配置)针对一个目的地址对应的传输不再感兴趣。终端的RRC层的上层可以请求(或者说指示或者说配置)针对一个目的地址的传输终止。
实施例四提供的方法，可以在针对一个目的地址，终端不再发送或接收SL数据的情况下，将第二SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例四提供的方法，可以在针对一个目的地址，终端不再发送或接收SL数据的情况下，通过清空第二SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例四提供的方法，可以在针对一个目的地址，终端不再发送或接收SL数据的情况下，通过将与第二SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据，或者，确保与第一SL进程关联的数据的接收，可以提高数据接收的可靠性。
实施例五
实施例五可以解决由于接收终端发生事件3时，未执行释放SCI和SL进程之间的关联关系、将SL进程视为未被占用以及清空SL进程的缓存中的一个或多个所导致的问题，还可以解决发送终端发生事件3时，未将SL进程视为未被占用，和/或，未清空SL进程的缓存所导致的问题。参见图11，该方法包括：
1101、针对一个目的地址，终端确定进行MAC重置。
本申请各个实施例中，针对一个目的地址进行MAC重置可以包括/替换/理解为：针对一个目的地址进行SL特定的MAC重置(Sidelink specific reset of the MAC entity)。关于目的地址的相关描述可参见实施例四，不再赘述。
步骤1101也可以描述为：针对一个目的地址，终端进行MAC重置。
其中，目的地址(destination)用于标识一个组播，或，一个广播。
可选的，在步骤1101之前，该方法还包括：针对目的地址，终端不再发送或接收SL数据。“针对目的地址，终端不再发送或接收SL数据”相关描述可参见实施例四，不再赘述。
1102、终端执行以下动作中的一个或多个：终端将第二SL进程确定为未被占用；终端释放与第二SL进程关联的关联关系；终端清空第二SL进程的缓存；其中，第二SL进程为与目的地址关联的SL进程。
可选的，与第二SL进程关联的关联关系，包括：第二SL进程与SCI之间的关联关系，和/或，第二SL进程与SL进程ID、第一目的ID、第一源ID和通信类型中的一个或多个之间的关联关系。
关于步骤1102的相关描述可参见上述步骤902，不再赘述。
实施例五提供的方法，可以在针对一个目的地址，终端进行MAC重置的情况下， 将第二SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例五提供的方法，可以在针对一个目的地址，终端进行MAC重置的情况下，通过清空第二SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送或接收，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。实施例五提供的方法，可以在针对一个目的地址，终端进行MAC重置的情况下，通过将与第二SL进程关联的关联关系释放，从而避免接收终端错误的清空掉其他数据，可以提高数据接收的可靠性，或者，确保与第一SL进程关联的数据的接收，可以提高数据接收的可靠性。
另外，除了上述实施例一至实施例五之外，还可以有以下方案1和方案2。
方案1、针对一个目的地址的PC5-S传输在RRC层的上层终止；或，RRC层的上层请求(或者说指示或者说配置)针对一个目的地址的PC5-S传输终止，终端执行以下动作中的一个或多个：终端将第四SL进程确定为未被占用，终端释放与第四SL进程关联的关联关系，终端清空第四SL进程的缓存。第四SL进程是指与目的地址的PC5-S或目的地址关联的SL进程。
方案2、针对一个目的地址的PC5-S传输在RRC层的上层终止；或，RRC层的上层请求(或者说指示或者说配置)针对一个目的地址的PC5-S传输终止，终端针对目的地址的PC5-S或目的地址进行MAC重置，终端执行以下动作中的一个或多个：终端将第四SL进程确定为未被占用，终端释放与第四SL进程关联的关联关系，终端清空第四SL进程的缓存。目前，NR V2X的现有协议中，mode1和mode2不可以同时存在，不同资源配置模式之间也不能进行相互的重传。即，使用mode1的资源进行新传的数据不能采用mode2的资源进行重传，使用mode2的资源进行新传的数据也不能采用mode1的资源进行重传。在资源配置模式发生切换/改变(简称为mode切换)的情况下，在发送终端侧，未规定SL进程处理的机制。mode切换后，若原本的资源配置模式下被占用的进程仍被占用，可能导致发送终端可用的进程数减少。为了解决该问题，本申请还提供了实施例六和实施例七所示的处理SL进程的方法，以下分别进行描述。实施例六和实施例七中的终端均可以为发送终端。
实施例六
参见图12，实施例六提供的处理SL进程的方法包括：
1201、终端确定资源配置模式为第一资源配置模式。
步骤1201也可以描述为：终端确定资源配置模式从第二资源配置模式切换为第一资源配置模式(也就是在切换之前终端的资源配置模式为第二资源配置模式)，或者，终端确定资源配置模式从第一资源配置模式和第二资源配置模式切换为第一资源配置模式(也就是在切换之前终端的资源配置模式为第一资源配置模式和第二资源配置模式)。
本申请中，切换可以替换为改变。
其中，第一资源配置模式可以为mode1，也可以为mode2。终端确定资源配置模式为第一资源配置模式可以包括以下任一项或多项：终端的MAC层确定资源配置模式为第一资源配置模式；终端的MAC层/终端被配置资源配置模式为第一资源配置模式，终端的RRC层配置资源配置模式为第一资源配置模式，终端的RRC层向终端的MAC层配 置资源配置模式为第一资源配置模式。例如，具体的，当终端的MAC实体被配置SL资源与mode1关联时，终端确定资源配置模式为mode1。当终端的RRC层配置SL资源与mode2关联时，终端确定资源配置模式为mode2。
1202、终端将第三SL进程确定为未被占用，和/或，清空第三SL进程的缓存。
其中，第三SL进程为与第二资源配置模式关联的SL进程，也就是说，第三SL进程或与第二资源配置模式关联的SL进程可以理解为：使用第二资源配置模式对应的资源发送数据的SL进程，和/或，与第二资源配置模式对应的资源相关联的SL进程。
其中，若第一资源配置模式为mode1，则第二资源配置模式mode2。若第一资源配置模式为mode2，则第二资源配置模式mode1。
实施例六提供的方法，若终端确定资源配置模式为第一资源配置模式，通过将第三SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第三SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。
可选的，第一资源配置模式对应的资源包括配置的SL授权资源(即SL CG资源)或动态的SL授权资源(即SL DG资源)(也就是第一资源配置模式为mode1)，在步骤1202之前，该方法还包括：终端(例如可以为终端的HARQ实体)获取配置的SL授权资源或动态的SL授权资源(也就是获取了mode1的资源，可选的，该资源可以为新传资源)，和/或，确定未被占用的SL进程的个数小于或等于第一阈值。
可选的，终端获取配置的SL授权资源或动态的SL授权资源可以包括：终端获取了配置的SL授权资源或动态的SL授权资源，且获取了在该配置的SL授权资源或动态的SL授权资源上传输的数据。
其中，第一阈值可以是网络设备配置/指示/发送给终端的，也可以是预配置的，也可以是协议规定的，也可以是设备厂商在终端出厂前存储在终端中的，还可以是终端连网时网络设备/其他设备预先配置在终端中的。例如，第一阈值可以为0、2、3等。
示例性的，未被占用的SL进程的个数小于或等于第一阈值，可以理解为，SL进程均被占用，或者，未被占用的SL进程的个数小于或等于终端对SL进程需求的个数。
在步骤1201之后，终端可以直接执行步骤1202，也可以在获取了配置SL授权资源或动态SL授权资源，和/或，未被占用的SL进程的个数小于或等于第一阈值的情况下，执行步骤1202。
需要说明的是，在第一资源配置模式为mode1的情况下，终端的SL资源是网络设备调度的，终端在获取了配置SL授权资源或动态SL授权资源后，才选择SL进程，因此，终端可以在获取了配置SL授权资源或动态SL授权资源时/后再执行步骤1202。
可选的，第一资源配置模式对应的资源包括选择的SL资源(selection sidelink resource)(也就是第一资源配置模式为mode2)，在步骤1202之前，该方法还包括：终端确定选择的SL资源(即终端需要进行资源选择或需要确定资源)，和/或，未被占用的SL进程的个数小于或等于第一阈值。
在步骤1201之后，终端可以直接执行步骤1202，也可以在终端确定选择的SL资源，和/或，未被占用的SL进程的个数小于或等于第一阈值的情况下，执行步骤1202。
需要说明的是，在第一资源配置模式为mode2的情况下，终端的SL资源是自行选择的，终端确定SL进程，进行资源选择，因此，终端可以在需要/确定进行资源选择时/后执行步骤1202。
可选的，在步骤1202之前，该方法还包括：针对第二资源配置模式，终端确定进行MAC重置。也就是说，mode切换触发针对第二资源配置模式的MAC重置，该MAC重置触发步骤1202的执行。
本申请各个实施例中，针对第二资源配置模式进行MAC重置可以包括/替换/理解为：针对第二资源配置模式进行SL特定的MAC重置(Sidelink specific reset of the MAC entity)。
可选的，步骤1202在具体实现时，可以根据以下信息中的一个或多个将第三SL进程中的一个或多个确定为未被占用，和/或，清空第三SL进程中的一个或多个的缓存。
信息1、与第三SL进程关联的数据的优先级。
信息2、与第三SL进程关联的数据的时延要求。
信息3、与第三SL进程关联的数据的可靠性要求。
例如，针对信息1，终端可以将优先级最低或低于一个优先级阈值的一个或多个数据关联的SL进程确定为未被占用和/或清空对应的缓存。
例如，针对信息2，终端可以将时延要求最高或低于一个时延阈值的一个或多个数据关联的SL进程确定为未被占用和/或清空对应的缓存。
例如，针对信息3，终端可以将可靠性要求最低或低于一个可靠性阈值的一个或多个数据关联的SL进程确定为未被占用和/或清空对应的缓存。
在终端中，可能发生mode切换频繁的情况，若mode切换之后立即释放进程，可能会造成丢包严重，对于优先级高、时延要求低、可靠性要求较高的业务来说可能不能满足要求，该可选的方法，可以避免该情况。另外，终端也可以在mode切换后的一个时间段之后，将一个或多个数据关联的SL进程确定为未被占用和/或清空对应的缓存。
实施例六中，终端可以一个一个处理SL进程，例如，用到一个SL进程处理一个SL进程，也可以多个多个处理SL进程，还可以一次性处理全部的SL的进程，本申请不作限制。此处的处理包括将SL进程确定为未被占用和/或清空对应的缓存。
可选的，该方法还包括：终端释放与第二资源配置模式对应的SL资源和/或与第二资源配置模式对应的SL资源对应的配置，以便于这些资源后续可以被其他终端使用，提高资源利用率。
实施例七
参见图13，实施例七提供的处理SL进程的方法包括：
1301、针对第二资源配置模式，终端确定进行MAC重置。
步骤1301在具体实现时，终端可以在从第二资源配置模式切换至其他的资源配置模式的情况下，执行步骤1301，例如，终端可以在资源配置模式从第二资源配置模式切换为第一资源配置模式的情况下，执行步骤1301，终端也可以在资源配置模式从第一资源配置模式和第二资源配置模式切换为第一资源配置模式的情况下，执行步骤 1301。终端也可以在其他触发条件的触发下，执行步骤1301。
其中，第二资源配置模式可以为mode1，也可以为mode2。
可选的，在步骤1301之前，该方法还包括：终端确定资源配置模式为第一资源配置模式。该步骤的相关描述可参见上述步骤1201，不再赘述。
1302、终端将第三SL进程确定为未被占用，和/或，清空第三SL进程的缓存。
可选的，步骤1302在具体实现时，可以根据以下信息中的一个或多个将第三SL进程中的一个或多个确定为未被占用，和/或，清空第三SL进程中的一个或多个的缓存。
信息1、与第三SL进程关联的数据的优先级。
信息2、与第三SL进程关联的数据的时延要求。
信息3、与第三SL进程关联的数据的可靠性要求。
该可选的方法的相关描述可参见上述实施例六，不再赘述。
可选的，该方法还包括：终端释放与第二资源配置模式对应的SL资源和/或与第二资源配置模式对应的SL资源对应的配置，以便于这些资源后续可以被其他终端使用，提高资源利用率。
实施例七提供的方法，若针对第二资源配置模式，终端确定进行MAC重置，通过将第三SL进程确定为未被占用，从而可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据接收的速率。通过清空第三SL进程的缓存，可以释放存储空间，也可以使得这些SL进程用于其他数据的发送，避免可用的SL进程数量减少，可以提高数据发送或接收的速率。
另外，在mode切换场景下，本申请还提供了实施例八，用于提高资源利用率。
实施例八
参见图14，实施例八提供的释放SL资源的方法，包括：
1401、终端确定资源配置模式为第一资源配置模式。
1402、终端释放与第二资源配置模式对应的SL资源和/或与第二资源配置模式对应的SL资源对应的配置。
实施例八的相关描述，可参见上述实施例六中的相关描述，在此不再赘述。实施例八通过释放第二资源配置模式关联的SL资源和/或与第二资源配置模式关联的SL资源对应的配置，可以使得这些资源后续被其他终端使用，提高资源利用率。
实施例六至实施例八所示的方法也适用于LTE***，只需要将其中的mode1替换为mode3，mode2替换为mode4进行理解即可。
本申请上述实施例中，不论是针对哪个参数(例如，目的地址、第二资源配置模式、SL的RRC连接)进行MAC重置，均不限定是否已经针对该参数进行了MAC重置。例如，均可以理解为终端将/准备针对该参数进行MAC重置。
本申请上述实施例中，发送终端的SL进程的缓存可以称为HARQ buffer，接收终端的SL进程的缓存可以称为soft buffer。本申请中，SL进程视为未被占用也可以描述为释放SL进程或去激活SL进程，未被占用的SL进程也可以描述为去激活的SL进程。类似的，SL进程视为被占用也可以描述为激活SL进程，被占用的SL进程也可以描述为激活的SL进程。
上述实施例提供的方法，在方案不矛盾的情况下，均可以进行结合。上述实施例提供的方法除了可以由终端执行之外，还可以由其他设备执行。
上述主要从方法的角度对本申请实施例的方案进行了介绍。可以理解的是，终端为了实现上述功能，其包含了执行各个功能相应的硬件结构和软件模块中的至少一个。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
示例性的，图15示出了上述实施例中所涉及的装置(记为装置150)的一种可能的结构示意图，该装置150包括处理单元1501和通信单元1502。可选的，还包括存储单元1503。装置150可以用于示意上述实施例中的终端的结构。该情况下，处理单元1501用于对终端的动作进行控制管理，例如，处理单元1501用于执行图5、图7、图8、图9、图11、图12、图13和图14中的各个步骤，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理单元1501可以通过通信单元1502与其他网络实体通信，例如，与另一个终端之间传输SL数据或SCI等。存储单元1503用于存储终端的程序代码和数据。
示例性的，装置150可以为一个设备也可以为芯片或芯片***。
当装置150为一个设备时，处理单元1501可以是处理器；通信单元1502可以是通信接口、收发器，或，输入接口和/或输出接口。可选地，收发器可以为收发电路。可选地，输入接口可以为输入电路，输出接口可以为输出电路。
当装置150为芯片或芯片***时，通信单元1502可以是该芯片或芯片***上的通信接口、输入接口和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。处理单元1501可以是处理器、处理电路或逻辑电路等。
图15中的集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。存储计算机软件产品的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例还提供了一种装置的硬件结构示意图，参见图16或图17，该装置包括处理器1601，可选的，还包括与处理器1601连接的存储器1602。
处理器1601可以是一个通用中央处理器(central processing unit，CPU)、微处理器、 特定应用集成电路(application-specific integrated circuit，ASIC)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器1601也可以包括多个CPU，并且处理器1601可以是一个单核(single-CPU)处理器，也可以是多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路或用于处理数据(例如计算机程序指令)的处理核。
存储器1602可以是ROM或可存储静态信息和指令的其他类型的静态存储设备、RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，本申请实施例对此不作任何限制。存储器1602可以是独立存在(此时，存储器1602可以位于装置外，也可以位于装置内)，也可以和处理器1601集成在一起。其中，存储器1602中可以包含计算机程序代码。处理器1601用于执行存储器1602中存储的计算机程序代码，从而实现本申请实施例提供的方法。
在第一种可能的实现方式中，参见图16，装置还包括收发器1603。处理器1601、存储器1602和收发器1603通过总线相连接。收发器1603用于与其他设备或通信网络通信。可选的，收发器1603可以包括发射机和接收机。收发器1603中用于实现接收功能的器件可以视为接收机，接收机用于执行本申请实施例中的接收的步骤。收发器1603中用于实现发送功能的器件可以视为发射机，发射机用于执行本申请实施例中的发送的步骤。
基于第一种可能的实现方式，图16所示的结构示意图可以用于示意上述实施例中所涉及的终端的结构。该情况下，处理器1601用于对终端的动作进行控制管理，例如，处理器1601用于执行图5、图7、图8、图9、图11、图12、图13和图14中的各个步骤，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理器1601可以通过收发器1603与其他网络实体通信，例如，与另一个终端之间传输SL数据或SCI等。存储器1602用于存储终端的程序代码和数据。
在第二种可能的实现方式中，处理器1601包括逻辑电路以及输入接口和/或输出接口。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。基于第二种可能的实现方式，参见图17，图17所示的结构示意图可以用于示意上述实施例中所涉及的终端。该情况下，处理器1601用于对终端的动作进行控制管理，例如，处理器1601用于执行图5、图7、图8、图9、图11、图12、图13和图14中的各个步骤，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理器1601可以通过输入接口和/或输出接口与其他网络实体通信，例如，与另一个终端之间传输SL数据或SCI等。存储器1602用于存储终端的程序代码和数据。
在实现过程中，本实施例提供的方法中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供了一种计算机可读存储介质，包括计算机可执行指令，当其在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种计算机程序产品，包含计算机可执行指令，当其在计算机 上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种通信***，包括：上述终端。
本申请实施例还提供了一种装置，包括：处理器和接口，处理器通过接口与存储器耦合，当处理器执行存储器中的计算机程序或计算机可执行指令时，使得上述实施例提供的任意一种方法被执行。
在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。在本申请的描述中，除非另有说明，“至少一个”是指一个或多个，“多个”是指两个或多于两个。
另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的保护范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的保护范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种处理侧行链路进程的方法，其特征在于，包括：
    终端确定对侧行链路的无线资源控制RRC连接进行媒体接入控制MAC重置；
    所述终端将第一侧行链路进程确定为未被占用；和/或，所述终端释放与所述第一侧行链路进程关联的关联关系；
    其中，所述第一侧行链路进程为与所述RRC连接关联的侧行链路进程。
  2. 根据权利要求1所述的方法，其特征在于，
    所述终端确定对侧行链路的RRC连接进行MAC重置，包括：所述终端的MAC层的上层请求对所述RRC连接进行MAC重置；
    所述终端将第一侧行链路进程确定为未被占用，包括：所述终端的MAC实体将所述第一侧行链路进程确定为未被占用；
    所述终端释放与所述第一侧行链路进程关联的关联关系，包括：所述终端的MAC实体释放与所述第一侧行链路进程关联的关联关系。
  3. 根据权利要求2所述的方法，其特征在于，在所述终端的MAC层的上层请求对所述RRC连接进行MAC重置之前，所述方法还包括：
    所述终端的RRC层的上层请求释放所述RRC连接。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，与所述第一侧行链路进程关联的关联关系，包括：所述第一侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第一侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  5. 一种处理侧行链路进程的方法，其特征在于，包括：
    针对一个目的地址，终端不再发送或接收侧行链路数据；
    所述终端执行以下动作中的一个或多个：所述终端将第二侧行链路进程确定为未被占用；所述终端释放与所述第二侧行链路进程关联的关联关系；所述终端清空所述第二侧行链路进程的缓存；
    其中，所述第二侧行链路进程为与所述目的地址关联的侧行链路进程。
  6. 根据权利要求5所述的方法，其特征在于，所述终端不再发送或接收侧行链路数据，包括：
    所述目的地址对应的传输终止，或，所述终端不需要发送或接收所述目的地址对应的侧行链路数据。
  7. 根据权利要求5或6所述的方法，其特征在于，与所述第二侧行链路进程关联的关联关系，包括：所述第二侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  8. 一种处理侧行链路进程的方法，其特征在于，包括：
    针对一个目的地址，终端确定进行媒体接入控制MAC重置；
    所述终端执行以下动作中的一个或多个：所述终端将第二侧行链路进程确定为未被占用；所述终端释放与所述第二侧行链路进程关联的关联关系；所述终端清空所述第二侧行链路进程的缓存；
    其中，所述第二侧行链路进程为与所述目的地址关联的侧行链路进程。
  9. 根据权利要求8所述的方法，其特征在于，在所述终端确定进行MAC重置之前，所述方法还包括：
    针对所述目的地址，所述终端不再发送或接收侧行链路数据。
  10. 根据权利要求8或9所述的方法，其特征在于，与所述第二侧行链路进程关联的关联关系，包括：所述第二侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  11. 一种处理侧行链路进程的方法，其特征在于，包括：
    终端确定资源配置模式为第一资源配置模式；
    所述终端将第三侧行链路进程确定为未被占用，和/或，清空所述第三侧行链路进程的缓存；
    其中，所述第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。
  12. 根据权利要求11所述的方法，其特征在于，所述第一资源配置模式对应的资源包括配置的侧行链路授权资源和/或动态的侧行链路授权资源，在所述终端将第三侧行链路进程确定为未被占用，和/或，清空所述第三侧行链路进程的缓存之前，所述方法还包括：
    所述终端获取所述配置的侧行链路授权资源或所述动态的侧行链路授权资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
  13. 根据权利要求11所述的方法，其特征在于，所述第一资源配置模式对应的资源包括选择的侧行链路资源，在所述终端将第三侧行链路进程确定为未被占用，和/或，清空所述第三侧行链路进程的缓存之前，所述方法还包括：
    所述终端确定选择的侧行链路资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，在所述终端将第三侧行链路进程确定为未被占用，和/或，清空所述第三侧行链路进程的缓存之前，所述方法还包括：
    针对所述第二资源配置模式，所述终端确定进行媒体接入控制MAC重置。
  15. 一种释放侧行链路资源的方法，其特征在于，包括：
    终端确定资源配置模式为第一资源配置模式；
    所述终端释放与第二资源配置模式对应的侧行链路资源和/或与所述第二资源配置模式对应的侧行链路资源对应的配置。
  16. 一种处理侧行链路进程的装置，其特征在于，包括：处理单元，用于：
    确定对侧行链路的无线资源控制RRC连接进行媒体接入控制MAC重置；
    将第一侧行链路进程确定为未被占用；和/或，释放与所述第一侧行链路进程关联的关联关系；
    其中，所述第一侧行链路进程为与所述RRC连接关联的侧行链路进程。
  17. 根据权利要求16所述的装置，其特征在于，所述处理单元，具体用于：
    在MAC层的上层请求对所述RRC连接进行MAC重置；
    在MAC实体将所述第一侧行链路进程确定为未被占用；
    在MAC实体释放与所述第一侧行链路进程关联的关联关系。
  18. 根据权利要求17所述的装置，其特征在于，所述处理单元，还用于：
    在RRC层的上层请求释放所述RRC连接。
  19. 根据权利要求16-18任一项所述的装置，其特征在于，与所述第一侧行链路进程关联的关联关系，包括：所述第一侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第一侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  20. 一种处理侧行链路进程的装置，其特征在于，包括：所述处理单元，用于；
    针对一个目的地址，不再发送或接收侧行链路数据；
    执行以下动作中的一个或多个：将第二侧行链路进程确定为未被占用；释放与所述第二侧行链路进程关联的关联关系；清空所述第二侧行链路进程的缓存；
    其中，所述第二侧行链路进程为与所述目的地址关联的侧行链路进程。
  21. 根据权利要求20所述的装置，其特征在于，不再发送或接收侧行链路数据，包括：所述目的地址对应的传输终止，或，不需要发送或接收所述目的地址对应的侧行链路数据。
  22. 根据权利要求20或21所述的装置，其特征在于，与所述第二侧行链路进程关联的关联关系，包括：所述第二侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  23. 一种处理侧行链路进程的装置，其特征在于，包括：所述处理单元，用于：
    针对一个目的地址，确定进行媒体接入控制MAC重置；
    执行以下动作中的一个或多个：将第二侧行链路进程确定为未被占用；释放与所述第二侧行链路进程关联的关联关系；清空所述第二侧行链路进程的缓存；
    其中，所述第二侧行链路进程为与所述目的地址关联的侧行链路进程。
  24. 根据权利要求23所述的装置，其特征在于，所述处理单元，还用于：
    针对所述目的地址，不再发送或接收侧行链路数据。
  25. 根据权利要求23或24所述的装置，其特征在于，与所述第二侧行链路进程关联的关联关系，包括：所述第二侧行链路进程与侧行链路控制信息SCI之间的关联关系，和/或，所述第二侧行链路进程与第一源标识、第一目的标识、侧行链路进程标识和通信类型中的一个或多个之间的关联关系。
  26. 一种处理侧行链路进程的装置，其特征在于，包括：所述处理单元，用于：
    确定资源配置模式为第一资源配置模式；
    将第三侧行链路进程确定为未被占用，和/或，清空所述第三侧行链路进程的缓存；
    其中，所述第三侧行链路进程为与第二资源配置模式关联的侧行链路进程。
  27. 根据权利要求26所述的装置，其特征在于，所述第一资源配置模式对应的资源包括配置的侧行链路授权资源和/或动态的侧行链路授权资源，所述处理单元，还用于：
    获取所述配置的侧行链路授权资源或所述动态的侧行链路授权资源，和/或，确定 未被占用的侧行链路进程的个数小于或等于第一阈值。
  28. 根据权利要求26所述的装置，其特征在于，所述第一资源配置模式对应的资源包括选择的侧行链路资源，所述处理单元，还用于：
    确定选择的侧行链路资源，和/或，确定未被占用的侧行链路进程的个数小于或等于第一阈值。
  29. 根据权利要求26-28任一项所述的装置，其特征在于，所述处理单元，还用于：
    针对所述第二资源配置模式，确定进行媒体接入控制MAC重置。
  30. 一种释放侧行链路资源的装置，其特征在于，包括：处理单元，用于：
    确定资源配置模式为第一资源配置模式；
    释放与第二资源配置模式对应的侧行链路资源和/或与所述第二资源配置模式对应的侧行链路资源对应的配置。
  31. 一种处理侧行链路进程的装置，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求1-4中任一项，或者，权利要求5-7中任一项，或者，权利要求8-10中任一项所述的方法，或者，权利要求11-14中任一项所述的方法。
  32. 一种释放侧行链路资源的装置，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求15所述的方法。
  33. 一种计算机可读存储介质，其特征在于，包括计算机执行指令，当所述计算机执行指令在计算机上运行时，使得所述计算机执行如权利要求1-15中任一项所述的方法。
  34. 一种计算机程序产品，其特征在于，包括计算机执行指令，当所述计算机执行指令在计算机上运行时，使得所述计算机执行如权利要求1-15中任一项所述的方法。
PCT/CN2020/123450 2020-10-23 2020-10-23 处理侧行链路进程的方法及装置 WO2022082800A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2020/123450 WO2022082800A1 (zh) 2020-10-23 2020-10-23 处理侧行链路进程的方法及装置
CN202080102952.8A CN115868200A (zh) 2020-10-23 2020-10-23 处理侧行链路进程的方法及装置
EP20958382.2A EP4224917A4 (en) 2020-10-23 2020-10-23 METHOD AND DEVICE FOR PROCESSING A SIDELINK PROCESS
JP2023524641A JP2023546482A (ja) 2020-10-23 2020-10-23 サイドリンク・プロセスを処理するための方法及び装置
US18/304,842 US20230262838A1 (en) 2020-10-23 2023-04-21 Method and apparatus for processing sidelink process

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123450 WO2022082800A1 (zh) 2020-10-23 2020-10-23 处理侧行链路进程的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/304,842 Continuation US20230262838A1 (en) 2020-10-23 2023-04-21 Method and apparatus for processing sidelink process

Publications (1)

Publication Number Publication Date
WO2022082800A1 true WO2022082800A1 (zh) 2022-04-28

Family

ID=81291181

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123450 WO2022082800A1 (zh) 2020-10-23 2020-10-23 处理侧行链路进程的方法及装置

Country Status (5)

Country Link
US (1) US20230262838A1 (zh)
EP (1) EP4224917A4 (zh)
JP (1) JP2023546482A (zh)
CN (1) CN115868200A (zh)
WO (1) WO2022082800A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110121192A (zh) * 2019-03-22 2019-08-13 西安电子科技大学 Mac ce、harq进程模式切换方法、切换mac ce的发送和接收方法
CN110662202A (zh) * 2018-06-29 2020-01-07 华硕电脑股份有限公司 在无线通信***中处理装置到装置资源释放的方法和设备
CN110831192A (zh) * 2018-08-10 2020-02-21 华为技术有限公司 侧行通信方法、终端设备和网络设备
US10652919B1 (en) * 2018-12-20 2020-05-12 National Chung-Shan Institute Of Science And Technology Method of side-link transmission for ultra-reliable and low latency communication
CN111436079A (zh) * 2019-01-11 2020-07-21 华硕电脑股份有限公司 用于无线通信中的侧链路资源分配模式配置的方法及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110662202A (zh) * 2018-06-29 2020-01-07 华硕电脑股份有限公司 在无线通信***中处理装置到装置资源释放的方法和设备
CN110831192A (zh) * 2018-08-10 2020-02-21 华为技术有限公司 侧行通信方法、终端设备和网络设备
US10652919B1 (en) * 2018-12-20 2020-05-12 National Chung-Shan Institute Of Science And Technology Method of side-link transmission for ultra-reliable and low latency communication
CN111436079A (zh) * 2019-01-11 2020-07-21 华硕电脑股份有限公司 用于无线通信中的侧链路资源分配模式配置的方法及设备
CN110121192A (zh) * 2019-03-22 2019-08-13 西安电子科技大学 Mac ce、harq进程模式切换方法、切换mac ce的发送和接收方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4224917A4 *

Also Published As

Publication number Publication date
JP2023546482A (ja) 2023-11-02
EP4224917A1 (en) 2023-08-09
CN115868200A (zh) 2023-03-28
US20230262838A1 (en) 2023-08-17
EP4224917A4 (en) 2023-12-06

Similar Documents

Publication Publication Date Title
US11804940B2 (en) Resources selection for feedback based NR-V2X communication
WO2019192596A1 (zh) 传输数据的方法及其装置和***
WO2021032067A1 (zh) 用于传输混合自动重传请求harq反馈信息的方法和装置
WO2019153935A1 (zh) 传输方式确定方法及装置，存储介质和电子装置
WO2018059173A1 (zh) 免授权的传输上行信息的方法、网络设备和终端设备
WO2020143731A1 (zh) 用于传输数据的方法、通信设备和网络设备
WO2021068708A1 (zh) 通信方法及装置
WO2018028320A1 (zh) 一种数据传输方法及终端、网络设备
US20220217768A1 (en) Communication Method and Apparatus
WO2021031912A1 (zh) 一种处理侧行链路资源的方法、装置及***
WO2021204091A1 (zh) 一种清空缓存的方法及装置
WO2020063410A1 (zh) 一种通信方法及通信装置
WO2021062846A1 (zh) 一种通信方法及装置
WO2021032064A1 (zh) 一种确定侧行链路资源的方法、装置以及***
CN111294166A (zh) 业务传输与业务配置的发送方法及装置、存储介质、终端、基站
JP7352647B2 (ja) リソース割り当て方法ならびにデバイス、記憶媒体および端末
WO2024103798A1 (zh) 无线通信的方法及装置
WO2022082800A1 (zh) 处理侧行链路进程的方法及装置
JP7339439B2 (ja) 通信方法及び装置
CN113517960B (zh) 通信方法及装置
WO2020063029A1 (zh) 数据传输方法、设备和***
TW202131740A (zh) 用於處理實體上鏈路控制通道碰撞的裝置及方法
WO2021035541A1 (zh) 一种数据传输方法及相关设备
WO2021087799A1 (zh) 信道质量反馈的方法及装置
TW202345539A (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: 20958382

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023524641

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2020958382

Country of ref document: EP

Effective date: 20230505

NENP Non-entry into the national phase

Ref country code: DE