Method and apparatus for handling sidelink processes

Abstract

This application provides a method and apparatus for processing sidelink processes, and relates to the field of communication technologies. In this method, a terminal determines to perform a MAC reset for a sidelink RRC connection. The terminal may then determine that a sidelink process (denoted as a first sidelink process) associated with the RRC connection is unoccupied, so that these SL processes may be used to receive other data. This avoids a reduction in the number of available SL processes and improves data reception speed. The terminal may further release an association associated with the first sidelink process to prevent the terminal from erroneously clearing other data or ensure reception of data associated with the first sidelink process. This can improve data reception reliability.

Description

[Technical Field]

[0001] This application relates to the field of communication technologies, and in particular to a method and apparatus for handling sidelink (SL) processes. [Background technology]

[0002] Vehicle-to-everything (V2X) is a key technology for intelligent transportation systems and is considered one of the fields with the greatest industrial potential and clearest market demand in the Internet of Things system. Vehicle-to-everything typically uses sensors and on-board terminals installed in vehicles to provide vehicle information and is a communication network that implements vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, and vehicle-to-pedestrian (V2P) communication.

[0003] V2X has broad application space, great industrial potential, and powerful social benefits. V2X will promote innovation and development in the automotive and information and communications industries, create new models and forms of automotive and transportation services, promote the innovation and application of technologies such as self-driving, assisted driving, intelligent driving, connected driving, intelligent network driving, autonomous driving, and car sharing, and is of great significance in improving transportation efficiency and safety.

[0004] Generally, in a V2X scenario, a communication link for direct communication between a terminal and another terminal may be called a sidelink (SL). A hybrid automatic repeat request (HARQ) process on a SL may be called a SL process. Currently, there is no effective method for processing the SL process. Summary of the Invention

[0005] Embodiments of this application provide a method and apparatus for handling SL processes to avoid a reduction in the number of available SL processes.

[0006] According to a first aspect, a method for processing sidelink processes is provided, including a terminal determining to perform a MAC reset for a sidelink RRC connection, and the terminal determining that a first sidelink process is unoccupied and / or releasing an association relationship associated with the first sidelink process, where the first sidelink process is a sidelink process associated with the RRC connection. According to the method provided in the first aspect, when the terminal determines to perform a MAC reset for the sidelink RRC connection or when the terminal performs a MAC reset for the sidelink RRC connection, the terminal determines that the first sidelink process is unoccupied, so that these sidelink processes may be used to receive other data. This avoids a reduction in the number of available sidelink processes and improves data reception speed. The association relationship associated with the first sidelink process is released to prevent the terminal from erroneously clearing other data or ensuring the reception of data associated with the first sidelink process. This can improve data reception reliability.

[0007] In a possible implementation, the terminal determining to perform a MAC reset for the RRC connection on the sidelink includes a layer above the MAC layer of the terminal requesting a MAC reset for the RRC connection; the terminal determining that the first sidelink process is unoccupied includes a MAC entity of the terminal determining that the first sidelink process is unoccupied; and the terminal releasing an association relationship related to the first sidelink process includes a MAC entity of the terminal releasing an association relationship related to the first sidelink process.

[0008] In a possible implementation, before the upper layer of the MAC layer of the terminal requests a MAC reset for the RRC connection, the method further includes the upper layer of the RRC layer of the terminal requesting the release of the RRC connection.

[0009] In a possible implementation, the association relationship associated with the first sidelink process includes an association relationship between the first sidelink process and an SCI and / or an association relationship between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type.

[0010] According to a second aspect, a method for processing sidelink processes is provided, including a terminal determining to perform a MAC reset for a sidelink RRC connection, and determining that a first sidelink process is unoccupied and / or clearing a buffer for the first sidelink process, where the first sidelink process is a sidelink process associated with the RRC connection. According to the method provided in the second aspect, when the terminal determines to perform a MAC reset for the SL RRC connection or performs a MAC reset for the SL RRC connection, the terminal determines that the first SL processes are unoccupied, so that these SL processes may be used to transmit other data. This avoids a reduction in the number of available SL processes and improves data reception speed. The buffer for the first SL process may be cleared, thereby freeing up storage space.

[0011] In a possible implementation, the terminal determining to perform a MAC reset for the RRC connection on the sidelink includes a layer above the MAC layer of the terminal requesting a MAC reset for the RRC connection; the terminal determining that the first sidelink process is unoccupied includes a MAC entity of the terminal determining that the first sidelink process is unoccupied; and the terminal clearing a buffer for the first sidelink process includes a MAC entity of the terminal clearing a buffer for the first sidelink process.

[0012] In a possible implementation, before the upper layer of the MAC layer of the terminal requests a MAC reset for the RRC connection, the method further includes the upper layer of the RRC layer of the terminal requesting the release of the RRC connection.

[0013] In a possible implementation, before the terminal decides to perform a MAC reset for the sidelink RRC connection, the method further includes the terminal sending an SL RRC reconfiguration message, or the terminal sending an SL RRC reconfiguration message and the terminal receiving an SL RRC reconfiguration complete message, where the SL RRC reconfiguration message includes a complete configuration indication.

[0014] According to a third aspect, a method for processing sidelink processes is provided, the method including a terminal releasing a sidelink RRC connection and performing one or more of the following actions: determining that a first sidelink process is unoccupied; releasing an association relationship associated with the first sidelink process; and clearing a buffer for the first sidelink process, where the first sidelink process is a sidelink process associated with the RRC connection. According to the method provided in the third aspect, when the terminal releases the SL RRC connection, the terminal determines that the first SL process is unoccupied, so that these SL processes may be used to transmit other data. This avoids a reduction in the number of available SL processes and improves data reception speed. The buffer for the first SL process may be cleared, so that storage space is freed. The association relationship associated with the first SL process is released, preventing the terminal from erroneously clearing other data. This can improve reliability of data reception.

[0015] In a possible implementation, the terminal releasing the sidelink RRC connection includes an RRC layer of the terminal releasing the RRC connection or an upper layer of the RRC layer of the terminal requesting the release of the RRC connection; the terminal determining that a first sidelink process is unoccupied includes a MAC entity of the terminal determining that the first sidelink process is unoccupied; the terminal releasing an association relationship related to the first sidelink process includes a MAC entity of the terminal releasing an association relationship related to the first sidelink process; and the terminal clearing a buffer for the first sidelink process includes a MAC entity of the terminal clearing a buffer for the first sidelink process.

[0016] In a possible implementation, before the RRC layer of the terminal releases the RRC connection, the method further includes: requesting an upper layer of the RRC layer of the terminal to release the RRC connection.

[0017] In a possible implementation, the association relationship associated with the first sidelink process includes an association relationship between the first sidelink process and an SCI and / or an association relationship between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type.

[0018] According to a fourth aspect, a method for processing a sidelink process is provided, the method including: a terminal skipping transmission or reception of sidelink data for a destination address; and the terminal performing one or more of the following actions: determining that a second sidelink process is unoccupied; releasing an association related to the second sidelink process; and clearing a buffer of the second sidelink process, where the second sidelink process is the sidelink process associated with the destination address. According to the method provided in the fourth aspect, when the terminal skips transmission or reception of sidelink data for the destination address, the terminal determines that the second sidelink process is unoccupied, so that these sidelink processes can be used to transmit other data. This avoids a reduction in the number of available sidelink processes and improves data reception speed. The buffer of the second sidelink process may be cleared, thereby freeing storage space. The association related to the second sidelink process is released to prevent the terminal from erroneously clearing other data.

[0019] In a possible implementation, the terminal skipping the transmission or reception of sidelink data may involve either stopping transmission corresponding to the destination address or not needing the terminal to transmit or receive sidelink data corresponding to the destination address.

[0020] In a possible implementation, the association relationship associated with the second sidelink process includes an association relationship between the second sidelink process and an SCI and / or an association relationship between the second sidelink process and one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.

[0021] According to a fourth aspect, a method for processing a sidelink process is provided, the method including a terminal determining to perform a MAC reset for a destination address and performing one or more of the following actions: determining that a second sidelink process is unoccupied; releasing an association related to the second sidelink process; and clearing a buffer of the second sidelink process, where the second sidelink process is the sidelink process associated with the destination address. According to the method provided in a fifth aspect, when the terminal performs a MAC reset for the destination address, the terminal determines that the second SL processes are unoccupied, so that these SL processes can be used to transmit other data. This avoids a reduction in the number of available SL processes and improves data reception speed. The buffer of the second SL process may be cleared, thereby freeing storage space. The association related to the second SL process is released to prevent the receiving terminal from erroneously clearing other data. This can improve reliability of data reception.

[0022] In a possible implementation, before the terminal decides to perform a MAC reset, the method further includes the terminal skipping transmission or reception of sidelink data to the destination address.

[0023] In a possible implementation, the association relationship associated with the second sidelink process includes an association relationship between the second sidelink process and an SCI and / or an association relationship between the second sidelink process and one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.

[0024] According to a sixth aspect, a method for processing sidelink processes is provided. The method includes a terminal determining that a resource configuration mode is a first resource configuration mode, and the terminal determining that a third sidelink process is unoccupied and / or clearing a buffer for the third sidelink process, where the third sidelink process is a sidelink process associated with a second resource configuration mode. According to the method provided in the sixth aspect, if the terminal determines that the resource configuration mode is the first resource configuration mode because the second resource configuration mode and the first resource configuration mode cannot coexist, the terminal does not use resources in the second resource configuration mode. In this case, the third SL process is determined to be unoccupied, so that these SL processes can be used to transmit other data. This avoids the number of available SL processes and improves data reception speed. The buffer for the third SL process may be cleared, so that storage space is freed.

[0025] In a possible implementation, the resources corresponding to the first resource configuration mode include configured and / or dynamic sidelink grant resources, and when the terminal determines that a third sidelink process is unoccupied and / or before the terminal clears a buffer for the third sidelink process, the method further comprises the terminal obtaining the configured or dynamic sidelink grant resources and / or determining that the number of unoccupied sidelink processes is less than or equal to a first threshold.

[0026] In a possible implementation, the resources corresponding to the first resource configuration mode include selected sidelink resources, and before the terminal determines that the third sidelink process is unoccupied and / or before the terminal clears the buffer for the third sidelink process, the method further comprises the terminal determining the selected sidelink resources and / or determining that the number of unoccupied sidelink processes is less than or equal to a first threshold.

[0027] In a possible implementation, the method may further comprise the terminal determining to perform a MAC reset for the second resource configuration mode before determining that the third sidelink process is unoccupied and / or before clearing the buffer of the third sidelink process.

[0028] In a possible implementation, the terminal's determining that the third sidelink process is unoccupied and / or clearing the buffer of the third sidelink process includes the terminal determining that one or more of the third sidelink processes is unoccupied and / or clearing one or more buffers of the third sidelink process based on one or more of the priority of data associated with the third sidelink process, the delay requirement of data associated with the third sidelink process, and the reliability requirement of data associated with the third sidelink process. Mode switching may occur frequently in the terminal. If a process is released immediately after a mode switch, severe packet loss may occur, and services with high priority, small delay requirements, and high reliability requirements may not meet their requirements. In this possible implementation, this situation may be avoided.

[0029] In a possible implementation, the method further comprises 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, so that the resources can be subsequently used by another terminal, thus improving resource utilization.

[0030] According to a seventh aspect, a method for processing sidelink processes is provided, including: a terminal determining to perform a MAC reset for a second resource configuration mode; and the terminal determining that a third sidelink process is unoccupied and / or clearing a buffer for the third sidelink process, where the third sidelink process is a sidelink process associated with the second resource configuration mode. According to the method provided in the seventh aspect, when the terminal performs a MAC reset for the second resource configuration mode, the terminal determines that the third SL processes are unoccupied, so that these SL processes can be used to transmit other data. This avoids a reduction in the number of available SL processes and improves data reception speed. The buffer for the third SL process may be cleared, so that storage space is freed.

[0031] In a possible implementation, before the terminal determines to perform a MAC reset for the second resource configuration mode, the method further includes the terminal determining that the resource configuration mode is the first resource configuration mode.

[0032] In a possible implementation, the terminal's determining that the third sidelink process is unoccupied and / or clearing the buffers of the third sidelink process may include the terminal determining that one or more of the third sidelink processes is unoccupied and / or clearing the buffers of the third sidelink process based on one or more of a priority of data associated with the third sidelink process, a delay requirement of data associated with the third sidelink process, and a reliability requirement of data associated with the third sidelink process.

[0033] In a possible implementation, the method further comprises the terminal releasing sidelink resources corresponding to the second resource configuration mode and / or a configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0034] According to an eighth aspect, a method for releasing sidelink resources is provided, comprising: a terminal determining that a resource configuration mode is a first resource configuration mode; and the terminal releasing sidelink resources corresponding to a second resource configuration mode and / or configuration corresponding to the sidelink resources corresponding to the second resource configuration mode. According to the eighth aspect, the SL resources associated with the second resource configuration mode and / or configuration corresponding to the SL resources associated with the second resource configuration mode are released, so that these resources can be subsequently used by another terminal, thereby improving resource utilization.

[0035] According to a ninth aspect, there is provided an apparatus for processing sidelink processes, comprising: a processing unit configured to: determine to perform a MAC reset for a sidelink RRC connection; determine that a first sidelink process is unoccupied; and / or release an association relationship related to the first sidelink process, wherein the sidelink process is a sidelink process associated with the RRC connection.

[0036] In a possible implementation, the processing unit is particularly configured to: request a MAC reset for the RRC connection at a layer above the MAC layer; determine at the MAC entity that the first sidelink process is unoccupied; and release at the MAC entity an association related to the first sidelink process.

[0037] In a possible implementation, the processing unit is further configured to request, at a layer above the RRC layer, to release the RRC connection.

[0038] In a possible implementation, the association relationship associated with the first sidelink process includes an association relationship between the first sidelink process and an SCI and / or an association relationship between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type.

[0039] According to a tenth aspect, there is provided an apparatus for processing sidelink processes, comprising: a processing unit configured to: determine to perform a MAC reset for a sidelink RRC connection; determine that a first sidelink process is unoccupied; and / or clear a buffer of the first sidelink process, wherein the first sidelink process is a sidelink process associated with the RRC connection.

[0040] In a possible implementation, the processing unit is particularly configured to: request a MAC reset for the RRC connection at a layer above the MAC layer; determine at the MAC entity that the first sidelink process is unoccupied; and clear a buffer of the first sidelink process at the MAC entity.

[0041] In a possible implementation, the processing unit is further configured to request, at a layer above the RRC layer, to release the RRC connection.

[0042] In a possible implementation, the apparatus further includes a communication unit, wherein the communication unit is configured to send an SL RRC reconfiguration message, or wherein the communication unit is configured to send an SL RRC reconfiguration message, and the apparatus receives an SL RRC reconfiguration complete message, wherein the SL RRC reconfiguration message includes a complete configuration indication.

[0043] According to an eleventh aspect, there is provided an apparatus for processing sidelink processes, comprising: a processing unit configured to release a sidelink RRC connection and to perform one or more of the following actions: determine that a first sidelink process is unoccupied; release an association relationship related to the first sidelink process; and clear a buffer of the first sidelink process, wherein the first sidelink process is a sidelink process associated with the RRC connection.

[0044] In a possible implementation, the processing unit is specifically configured to: release the RRC connection at the RRC layer or request the release of the RRC connection at a layer above the RRC layer; determine, at the MAC entity, that the first sidelink process is unoccupied; release, at the MAC entity, an association relationship related to the first sidelink process; and release, at the MAC entity, a buffer of the first sidelink process.

[0045] In a possible implementation, the processing unit is further configured to request, at a layer above the RRC layer, to release the RRC connection.

[0046] In a possible implementation, the association relationship associated with the first sidelink process includes an association relationship between the first sidelink process and an SCI and / or an association relationship between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type.

[0047] According to a twelfth aspect, there is provided an apparatus for processing a sidelink process, comprising: a processing unit configured to skip transmission or reception of sidelink data for a destination address and to perform one or more of the following actions: determine that a second sidelink process is unoccupied; release an association relationship associated with the second sidelink process; and clear a buffer of the second sidelink process, wherein the second sidelink process is the sidelink process associated with the destination address.

[0048] In a possible implementation, skipping the transmission or reception of sidelink data may involve either the transmission corresponding to the destination address being stopped or the sidelink data corresponding to the destination address not needing to be transmitted or received.

[0049] In a possible implementation, the association relationship associated with the second sidelink process includes an association relationship between the second sidelink process and an SCI and / or an association relationship between the second sidelink process and one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.

[0050] According to a thirteenth aspect, there is provided an apparatus for processing a sidelink process, comprising: a processing unit configured to determine to perform a MAC reset for a destination address; and to perform one or more of the following actions: determine that a second sidelink process is unoccupied; release an association relationship associated with the second sidelink process; and clear a buffer of the second sidelink process, wherein the second sidelink process is the sidelink process associated with the destination address.

[0051] In a possible implementation, the processing unit is further configured to skip transmitting or receiving sidelink data for the destination address.

[0052] In a possible implementation, the association relationship associated with the second sidelink process includes an association relationship between the second sidelink process and an SCI and / or an association relationship between the second sidelink process and one or more of the first source identifier, the first destination identifier, the sidelink process identifier, and the communication type.

[0053] According to a fourteenth aspect, there is provided an apparatus for processing a sidelink process, comprising: a processing unit configured to: determine a resource configuration mode is a first resource configuration mode; determine a third sidelink process is unoccupied; and / or clear a buffer of the third sidelink process, the third sidelink being a sidelink process associated with the second resource configuration mode.

[0054] In a possible implementation, the resources corresponding to the first resource configuration mode include configured and / or dynamic sidelink grant resources, and the processing unit is further configured to obtain the configured or dynamic sidelink grant resources and / or to determine that the number of unoccupied sidelink processes is less than or equal to a first threshold.

[0055] In a possible implementation, the resources corresponding to the first resource configuration mode include selected sidelink resources, and the processing unit is further configured to determine the selected sidelink resources and / or to determine that the number of unoccupied sidelink processes is less than or equal to a first threshold.

[0056] In a possible implementation, the processing unit is further configured to determine to perform a MAC reset for the second resource configuration mode.

[0057] In a possible implementation, the processing unit is specifically configured to cause the terminal to determine that one or more of the third sidelink processes are unoccupied and / or clear one or more buffers of the third sidelink process based on one or more of a priority of data associated with the third sidelink process, a delay requirement of data associated with the third sidelink process, and a reliability requirement of data associated with the third sidelink process.

[0058] In a possible implementation, the processing unit is further configured to release sidelink resources corresponding to the second resource configuration mode and / or a configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0059] According to a fifteenth aspect, there is provided an apparatus for processing a sidelink process, comprising: a processing unit configured to: determine to perform a MAC reset for a second resource configuration mode; determine that a third sidelink process is unoccupied; and / or clear a buffer of the third sidelink process, the third sidelink process being a sidelink process associated with the second resource configuration mode.

[0060] In a possible implementation, the processing unit is further configured to determine that the resource configuration mode is the first resource configuration mode.

[0061] In a possible implementation, the processing unit is specifically configured to cause the terminal to determine that one or more of the third sidelink processes are unoccupied and / or clear one or more buffers of the third sidelink process based on one or more of a priority of data associated with the third sidelink process, a delay requirement of data associated with the third sidelink process, and a reliability requirement of data associated with the third sidelink process.

[0062] In a possible implementation, the processing unit is further configured to release sidelink resources corresponding to the second resource configuration mode and / or a configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0063] According to a sixteenth aspect, there is provided an apparatus for releasing sidelink resources, comprising: a processing unit configured to: determine a resource configuration mode is a first resource configuration mode; and release sidelink resources corresponding to a second resource configuration mode and / or a configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0064] According to a seventeenth aspect, there is provided an apparatus for processing a sidelink process, the apparatus including a processor. The processor is coupled to a memory, the memory being configured to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory to implement the method provided in any one of the first to seventh aspects. For example, the memory and the processor may be integrated together or may be separate components. When the memory and the processor are separate components, the memory may be located within the apparatus for processing the sidelink process, or may be located outside the apparatus for processing the sidelink process.

[0065] In a possible implementation, the processor includes logic circuitry and further includes an input interface and / or an output interface, for example, the output interface configured to perform a sending action in a corresponding manner, and the input interface configured to perform a receiving action in a corresponding manner.

[0066] In a possible implementation, the device for processing the sidelink process further includes a communication interface and a communication bus, where the processor, the memory, and the communication interface are connected via the communication bus. The communication interface is configured to perform transmitting and receiving actions in a corresponding manner. The communication interface may also be referred to as a transceiver. Optionally, the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is configured to perform transmitting actions in a corresponding manner, and the receiver is configured to perform receiving actions in a corresponding manner.

[0067] In a possible implementation, the device for handling the sidelink process exists in the product form of a chip.

[0068] According to an eighteenth aspect, there is provided an apparatus for releasing sidelink resources, the apparatus including a processor. The processor is coupled to a memory, the memory being configured to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory to implement the method provided in the eighth aspect. For example, the memory and the processor may be integrated together or may be separate components. When the memory and the processor are separate components, the memory may be located within the apparatus for releasing sidelink resources or may be located outside the apparatus for releasing sidelink resources.

[0069] In a possible implementation, the processor includes logic circuitry and further includes an input interface and / or an output interface, for example, the output interface configured to perform a sending action in a corresponding manner, and the input interface configured to perform a receiving action in a corresponding manner.

[0070] In a possible implementation, the device for releasing sidelink resources further includes a communication interface and a communication bus, where the processor, the memory, and the communication interface are connected via the communication bus. The communication interface is configured to perform transmitting and receiving actions in a corresponding manner. The communication interface may also be referred to as a transceiver. Optionally, the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is configured to perform transmitting actions in a corresponding manner, and the receiver is configured to perform receiving actions in a corresponding manner.

[0071] In a possible implementation, the device for freeing up sidelink resources exists in the product form of a chip.

[0072] According to a nineteenth aspect, there is provided an apparatus for processing a sidelink process, the apparatus including a processor and an interface, the processor being coupled to a memory using the interface, and the processor executing a computer program or instructions in the memory performs any of the methods provided in any one of the first to seventh aspects.

[0073] According to a twentieth aspect, there is provided an apparatus for releasing sidelink resources, comprising a processor and an interface, wherein the processor is coupled to a memory using the interface, and when the processor executes a computer program or instructions in the memory, the method provided in the eighth aspect is performed.

[0074] According to a twenty-first aspect, there is provided a computer-readable storage medium comprising computer-executable instructions which, when run on a computer, enable the computer to perform any of the methods provided in any one of the first to eighth aspects.

[0075] According to a twenty-second aspect, there is provided a computer program product comprising computer-executable instructions which, when run on a computer, enable the computer to perform any of the methods provided in any one of the first to eighth aspects.

[0076] For the technical effects achieved by implementing any of the ninth to twenty-second aspects, please refer to the technical effects achieved by the corresponding implementation of the first to eighth aspects, and the details will not be described again here.

[0077] It should be noted that the solutions of the above aspects may be combined, provided that the solutions are not contradictory. [Brief explanation of the drawings]

[0078] [Figure 1] 1 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0079] [Figure 2] FIG. 1 is a schematic diagram of a sidelink grant according to one embodiment of the present application.

[0080] [Figure 3] FIG. 2 is a schematic diagram of a parallel HARQ process according to an embodiment of this application;

[0081] [Figure 4] FIG. 1 is a schematic diagram of the association between SCI and SL processes according to an embodiment of the present application.

[0082] [Figure 5] 1 is a schematic diagram of a method for treating a SL process according to an embodiment of the present application.

[0083] [Figure 6] FIG. 1 is a schematic diagram of releasing an association relationship related to a SL process according to an embodiment of the present application;

[0084] [Figure 7] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0085] [Figure 8] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0086] [Figure 9] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0087] [Figure 10] FIG. 10 is yet another schematic diagram of releasing an association relationship related to a SL process according to an embodiment of the present application;

[0088] [Figure 11] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0089] [Figure 12] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0090] [Figure 13] FIG. 1 is a schematic diagram of yet another method for treating a SL process according to an embodiment of the present application.

[0091] [Figure 14] 2 is a schematic diagram of a method for releasing SL resources according to an embodiment of the present application;

[0092] [Figure 15] FIG. 1 is a schematic configuration diagram of a terminal according to an embodiment of the present application.

[0093] [Figure 16] 1 is a schematic diagram of a hardware structure of a terminal according to an embodiment of this application;

[0094] [Figure 17] FIG. 10 is a schematic diagram of the hardware structure of yet another terminal according to an embodiment of this application; DETAILED DESCRIPTION OF THE INVENTION

[0095] In the description of this application, unless otherwise specified, " / " means "or." For example, A / B may represent A or B. The term "and / or" in this specification describes only the association relationship between related objects and indicates that there are three possible relationships. For example, A and / or B may represent three cases: only A exists, both A and B exist, and only B exists. Additionally, "at least one" means one or more, and "multiple" means two or more. Terms such as "first," "second," etc. do not limit the number and execution sequence, and terms such as "first," "second," etc. do not indicate a clear distinction.

[0096] It should be noted that in this application, words such as "example," "for example," and the like are used to denote providing an example, illustration, or explanation. In this application, an embodiment or design described as an "example" or "for example" should not be described as preferred or having more advantages over other embodiments or designs. Rather, the use of words such as "example" or "for example" is intended to present a relative concept in a particular manner.

[0097] The methods provided in the embodiments of this application are applicable to, but not limited to, the following fields: device to device (D2D), V2X, unmanned driving, automated driving (ADS), driver assistance (ADAS), intelligent driving, connected driving, intelligent network driving, and car sharing.

[0098] The network elements in this application include network devices and terminals in a communication system, see Figure 1. The method provided in the embodiment of this application mainly relates to communication between terminals.

[0099] In embodiments of this application, communication systems include, but are not limited to, long-term evolution (LTE) systems, fifth-generation (5G) systems, new radio (NR) systems, wireless local area network (WLAN) systems, and future evolved systems or converged communication systems. 5G systems may be non-standalone (NSA) 5G systems or standalone (SA) 5G systems.

[0100] A network device in an embodiment of this application is a network-side entity configured to transmit signals, receive signals, or transmit signals and receive signals. The network device may be a device deployed on a radio access network (RAN) and providing wireless communication functions for terminals, such as a transmission reception point (TRP), a base station, or various forms of control nodes (e.g., a network controller and a radio controller (e.g., a radio controller in a cloud radio access network (CRAN) scenario)). Specifically, the network device may be various forms such as a macro base station, a micro base station (also called a small cell), a relay station, an access point (AP), or an antenna panel of a base station. A control node may be connected to multiple base stations and configure resources for multiple terminals within the coverage of multiple base stations. In systems using different radio access technologies, the name of a device having base station functionality may be different. For example, a device having the functionality of a base station may be called an evolved NodeB (eNB or eNodeB) in an LTE system, or a next generation node base station (gNB) in a 5G system or NR system. The specific name of the base station is not limited in this application. Alternatively, the network device may be a network device in a future public land mobile network (PLMNN), etc.

[0101] A terminal in an embodiment of this application is a user-side entity configured to receive signals, transmit signals, or receive signals and transmit signals. The terminal is configured to provide one or more of voice services and data connection services to a user. A terminal may also be called user equipment (UE), a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal may be a V2X device, such as a smart car (or an intelligent car), a digital car, an unmanned car (or a driverless car, or a pilotless car, or an automobile), a self-driving car (or an autonomous car), a pure electric vehicle (or a battery EV), a hybrid electric vehicle (HEV), a range extended electric vehicle (REEV), a plug-in hybrid electric vehicle (PHEV), a new energy vehicle (NEV), or a road site unit (RSU). Alternatively, the terminal may be a D2D device, such as an electricity meter or a water meter.Alternatively, the terminal may be a mobile station (MS), a subscriber unit, an unmanned aerial vehicle, an internet of things (IoT) device, a station (ST) in a WLAN, a cellular phone, a smartphone, a cordless phone, a wireless data card, a tablet computer, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a laptop computer, a machine type communication (MTC) terminal, a handheld device with wireless communication capabilities, a computing device, another processing device connected to a wireless modem, an in-vehicle device, or a wearable device (also referred to as a wearable intelligent device). Alternatively, the terminal may be a terminal in a next-generation communication system, such as a terminal in a 5G system, a terminal in a future PLMN, or a terminal in an NR system.

[0102] To make the embodiments of this application clearer, the following briefly describes the concepts and some contents related to the embodiments of this application.

[0103] 1. Uplink (UL), downlink (DL), and SL

[0104] The wireless communication link used by a terminal to transmit data (i.e., uplink data) to a network device may be referred to as the UL. The wireless communication link used by a network device to transmit data (i.e., downlink data) to a terminal may be referred to as the DL. The UL interface and the DL interface may be collectively referred to as the Uu interface. Thus, the UL interface and the DL interface may be collectively referred to as the Uu interface link.

[0105] A communication link for direct communication between terminals may be referred to as an SL. An SL may also be referred to as a side link. Data transmitted between terminals may be referred to as SL data.

[0106] For example, data in the embodiments of this application may be understood as a transport block (TB) or a medium access control (MAC) protocol data unit (PDU). Data may also be referred to as a data packet or packet.

[0107] 2. SL resource setting mode

[0108] The SL transmission resource used by the transmitting terminal of the two terminals may be determined by either method A or method B below.

[0109] Scheme A: SL transmission resources may be scheduled by the network device.

[0110] The mode in which a network device schedules SL transmission resources may include mode 1 resource configuration mode (named in NR) and mode 3 resource configuration mode (named in LTE).

[0111] There are two types of SL transmission resources scheduled by network devices:

[0112] Type 1: SL configured grant (CG) resource

[0113] In this case, the network device does not need to allocate resources to the transmitting terminal separately during each data transmission. After allocating resources to the transmitting terminal once, the transmitting terminal may use the allocated resources in future periods. The characteristic of the aforementioned allocation is that "resources are allocated once and can be used multiple times." For example, the network device may configure periodically occurring time-domain resources for the transmitting terminal. See Figure 2 for an example. The first time-domain resource in the periodically occurring time-domain resources is symbol 4 to symbol 9 in slot 1, and the period of the time-domain resources is one slot. Each time a time-domain resource appears, it is called a single SL grant (also called a sidelink grant). Figure 2 shows four sidelink grants, each corresponding to one sidelink grant ID. Therefore, the sidelink grant IDs corresponding to the four sidelink grants are sidelink grant 0, sidelink grant 1, sidelink grant 2, and sidelink grant 3.

[0114] SL CG resources may include SL type 1 (SL configured grant type 1) resources and SL type 2 (SL configured grant type 2) resources. SL type 1 CG resources may be SL transmission resources directly configured by a network device for a transmitting terminal using radio resource control (RRC) signaling. The transmitting terminal may directly use the CG resources to transmit data without activating additional resources. SL type 1 CG resources are also called SL grant-free resources. SL type 2 CG resources are a period during which a network device defines SL transmission resources using RRC signaling and then activates the SL transmission resources using a physical downlink control channel (PDCCH) or downlink control information (DCI). The transmitting terminal cannot directly use the SL transmission resources to transmit data, but can use the SL transmission resources only after they are activated. SL Type 2 CG resources may also be referred to as SL Semi-Persistent Scheduling (SL SPS) resources.

[0115] For a SL, one carrier may support one or more CG resources. Optionally, different SL CG resources may correspond to different indices. For example, CG resources with indices 1, 2, and 3 may be denoted as SL CG1, SL CG2, and SL CG3, respectively.

[0116] Type 2: SL dynamic grant (DG) resource

[0117] For example, SL transmission resources may be dynamically allocated to a transmitting terminal by a network device using DCI, which may be carried on a PDCCH.

[0118] Scheme B: The SL transmission resource may be determined autonomously by the transmitting terminal.

[0119] For example, the mode in which the transmitting terminal determines the SL transmission resource may include mode 2 resource configuration mode (named in NR) or mode 4 resource configuration mode (named in LTE).

[0120] In scheme B, when the transmitting terminal is located within the communication coverage of the network device, the network device configures an SL resource pool for the transmitting terminal using a system broadcast message (system information block, SIB) or dedicated RRC signaling, and the transmitting terminal may obtain SL transmission resources from the SL resource pool to transmit control signals and / or data signals to the receiving terminal. When the transmitting terminal is located outside the communication coverage of the network device, the transmitting terminal may obtain SL transmission resources from the SL resource pool pre-configured by the transmitting terminal to transmit control signals and / or data signals to the receiving terminal.

[0121] When obtaining SL transmission resources from the SL resource pool, the transmitting terminal may detect or contend for SL transmission resources. Specifically, the transmitting terminal transmits control and / or data signals by competing with other terminals for suitable SL transmission resources in the SL resource pool. For example, the higher the priority of the V2X service to be transmitted or the data of the transmitting terminal, the higher the probability of obtaining suitable SL transmission resources in the SL resource pool through competition.

[0122] For simplicity, in this application, Mode 1 resource configuration mode, Mode 2 resource configuration mode, Mode 3 resource configuration mode, and Mode 4 resource configuration mode are abbreviated as Mode 1, Mode 2, Mode 3, and Mode 4, respectively. Where possible, Mode 3 and Mode 4 cannot coexist in LTE V2X. Where possible, Mode 1 and Mode 2 cannot coexist in NR V2X.

[0123] 3. Sidelink control information (SCI)

[0124] Similar to the DCI for scheduling Uu interface data, the SCI is used to schedule SL data. For example, the first level SCI may carry control information for SL data. The SCI may be transmitted on the physical sidelink control channel (PSCCH).

[0125] 4. HARQ

[0126] HARQ is a technique that combines forward error correction (FEC) (or forward error correction code) and automatic repeat request (ARQ) methods.

[0127] FEC means that the data transmitted by the transmitting end includes a forward error correction code or redundancy information. After receiving the data, the receiving end can find errors through a check (such as a cyclic redundancy check (CRC)) and correct the errors using the forward error correction code or redundancy information. In this way, the number of retransmissions (i.e., retransmission of data) at the transmitting end is reduced.

[0128] ARQ means that the receiving end determines the accuracy of the received data through a check (e.g., CRC check). If the received data is correct, the receiving end sends a positive acknowledgement (ACK) to notify the transmitting end that the received data is correct. If the received data is incorrect, the receiving end sends a negative acknowledgement (ACK) to notify the transmitting end that the received data is incorrect. When the transmitting end receives a NACK, it may retransmit the data to the receiving end. ACK and NACK are HARQ feedback.

[0129] LTE V2X only supports broadcast services, so SL HARQ feedback is not supported. NR V2X supports unicast, multicast, and broadcast services and supports SL HARQ feedback.

[0130] Below, the HARQ-related content will be specifically explained using three parts (a) to (c).

[0131] (a) HARQ process

[0132] The HARQ process uses a stop-and-wait protocol to transmit data. In the stop-and-wait protocol, after transmitting a transport block (TB), the transmitting end stops and waits for acknowledgment information. The receiving end may feed back an ACK or NACK for the TB. However, the transmitting end stops and waits for an acknowledgment after each transmission. As a result, throughput is low. Therefore, the transmitting end may use multiple parallel HARQ processes. While one HARQ process is waiting for an acknowledgment, the transmitting end may continue transmitting data using another HARQ process. For example, see FIG. 3. The terminal transmits TB1 using a first HARQ process, finishes transmitting TB1 at time T1, receives HARQ feedback for TB1 at time T2, and waits for an acknowledgment for TB1 during the period from T1 to T2. While waiting for an acknowledgement for TB1, the terminal transmits TB2 using the second HARQ process, finishes transmitting TB2 at time T2, receives HARQ feedback for TB2 at time T3, and waits for an acknowledgement for TB2 within the period from T2 to T3. While waiting for an acknowledgement for TB2, the terminal may transmit TB3 using the third HARQ process.

[0133] One HARQ process is identified by one HARQ process ID. A sidelink grant is associated with the HARQ process, and the terminal transmits HARQ data using the process of the sidelink grant associated with the HARQ process.

[0134] (b) Processing mechanism at the receiving end for newly transmitted data and retransmitted data

[0135] Each HARQ process has a corresponding buffer (eg, HARQ buffer or soft buffer) at the receiving end to perform soft combining and decoding on the received data.

[0136] After receiving newly transmitted data sent by the transmitting end using one HARQ process, the receiving end may place the received newly transmitted data in a buffer corresponding to the HARQ process for decoding. If decoding fails, when receiving retransmitted data of the newly transmitted data, the receiving end may combine the received retransmitted data with the newly transmitted data previously stored in the buffer, place the combined data in the buffer, and perform decoding again. This method may be referred to as soft combining and decoding. Compared with separate decoding (i.e., data in each transmission is decoded separately and not combined with previous data for decoding), the success rate of decoding is improved by using the soft combining and decoding method. Similarly, if decoding still fails, the above procedure is repeated again. The newly received retransmitted data is combined with the data in the buffer and decoded again.

[0137] At the transmitting end, the retransmitted data and the newly transmitted data may have the same redundancy version (RV) or different RVs with the same TB.

[0138] A HARQ process on the Uu interface is called an HARQ process, and a HARQ process on the SL is called an SL process.

[0139] (c) SL data transmission by SL process

[0140] One transmitting terminal may communicate with multiple receiving terminals, i.e., one transmitting terminal may transmit SCI and SL data to multiple receiving terminals. One receiving terminal may also communicate with multiple transmitting terminals, i.e., one receiving terminal may receive SCI and SL data from multiple transmitting terminals. The SCI may include an SL process ID, a first destination ID, a first source ID, and a communication type.

[0141] The SL process ID identifies the SL process and is similar to the HARQ process ID of the Uu interface.

[0142] The first destination ID may identify a target of the SL data scheduled by the SCI. Optionally, the first destination ID may be used to perform data packet filtering at the PHY layer of the receiving terminal. Optionally, the first destination ID may be some bits of the second destination ID. For example, the second destination ID is 24 bits, and the first destination ID is the lower 16 bits of the second destination ID.

[0143] The second destination ID identifies a target (e.g., target) / receiving end / receiving terminal of the data. For example, the second destination ID identifies a multicast service or a broadcast service. For example, the second destination ID may be an identifier of the target / receiving end / receiving terminal. For example, the second destination ID may be a Destination Layer-2 ID. Optionally, the second destination ID may be used to perform data packet filtering at the MAC layer of the receiving terminal.

[0144] The first source ID identifies the source of the SL data scheduled by the SCI. Optionally, the first source ID may be used for data packet filtering at the PHY layer of the receiving terminal. Optionally, the first source ID may be some bits of the second source ID. For example, the second source ID is 24 bits, and the first source ID is the lower 8 bits of the second source ID.

[0145] The second source ID identifies a source (e.g., source) / sender / transmitting terminal of the data. For example, the second source ID may be an identifier of the source / sender / transmitting terminal. For example, the second source ID may be a source Layer-2 ID. Optionally, the second source ID may be used to perform data packet filtering at the MAC layer of the receiving terminal.

[0146] The communication type may include one or more of unicast, multicast, and broadcast. The communication type in the SCI indicates whether the current communication is unicast, multicast, or broadcast, or whether the SL data scheduled by the SCI is unicast data, multicast data, or broadcast data.

[0147] For example, the receiving terminal may detect a surrounding SCI, and then determine whether the receiving terminal is interested in the SCI or the SL data scheduled by the SCI based on the first destination ID, the first source ID, and the communication type in the SCI. If the receiving terminal is interested in the SCI or the SL data, the receiving terminal continues to receive the SL data scheduled by the SCI.

[0148] On the transmitting side, an SL HARQ entity is included, and all SL processes (e.g., 16 SL processes) maintained by the SL HARQ entity are shared by all connection / communication types. On the receiving side, an SL HARQ entity is included, and all SL processes (e.g., 64 SL processes) maintained by the SL HARQ entity are shared by all connection / communication types.

[0149] Different transmitting terminals may use the same SL process ID to communicate with the same receiving terminal. To distinguish data associated with the same SL process ID from different transmitting terminals, the receiving terminal receives one SCI and / or data. After the receiving terminal determines that data is to be newly transmitted, it selects an SL process (denoted as SL process 1) that is not occupied by the data and associates the "SL process ID + first destination ID + first source ID + communication type" in the SCI with SL process 1. When the receiving terminal again receives retransmitted data corresponding to the same "SL process ID + first destination ID + first source ID + communication type," it may place the retransmitted data in a buffer of SL process 1 and perform soft combining and decoding on the received data. The "first destination ID + first source ID + communication type" may be referred to as SL identification information.

[0150] 5. MAC reset

[0151] In the Uu interface, when the terminal decides to perform a MAC reset (e.g., a layer above the terminal's MAC layer requests a MAC reset), the terminal's MAC entity performs one or more of the following: stopping running timers, canceling triggered beam failure recoveries (BFRs), canceling triggered scheduling requests (SRs), resetting MAC-related counters (e.g., LBT_COUNTER, BFI_COUNTER, etc.), and stopping ongoing random access processes. For specific content, see clause 5.12 of TS 38.321. The details will not be repeated here.

[0152] Currently, in the SL, the terminal decides to perform a MAC reset (e.g., a higher layer of the terminal's MAC layer requests a MAC reset for one SL RRC connection), and the terminal's MAC entity performs one or more of the following: canceling triggered SRs related to only the SL RRC connection, canceling triggered SL BSRs related to only the SL RRC connection, and clearing soft buffers of SL processes related to the SL RRC connection. For specific content, see clause 5.12 of TS 38.321. The details will not be described again here.

[0153] Currently, in the SL RRC connection, an SL radio link failure (RLF) occurs or the MAC layer of the receiving terminal receives an SL RRC reconfiguration (RRCReconfigurationSidelink) message with full configuration, in which case the receiving terminal performs a MAC reset on the SL RRC connection.

[0154] An SL RRC reconfiguration message with full configuration may be understood as the SL RRC reconfiguration message including a full configuration indication. The full configuration indication indicates that the SL RRC reconfiguration message should use the full configuration. For example, the full configuration indication is "sl-ResetConfig".

[0155] For example, an SL RRC reconfiguration message with fullconfig indicates that all reconfiguration is performed in the receiving terminal for the SL RRC connection. In other words, all configurations are updated for the SL RRC connection. In unicast transmission, the transmitting terminal uses the SL RRC reconfiguration message to send the SL configuration to the receiving terminal. If the SL RRC reconfiguration message includes the "sl-ResetConfig" parameter, it indicates that all SLs are configured.

[0156] The above briefly describes concepts and some context related to embodiments of this application.

[0157] Currently, in one aspect, in an SL process, the receiving terminal considers the SL process to be unoccupied in the following two cases:

[0158] (1) If the receiving terminal successfully decodes the received data, the SL process corresponding to that data is considered unoccupied.

[0159] (2) When the receiving terminal again receives an SCI for scheduling newly transmitted SL data or newly transmitted SL data corresponding to the same "SL process ID + first destination ID + first source ID + communication type," the SL process corresponding to the "SL process ID + first destination ID + first source ID + communication type" is deemed to be unoccupied. Specifically, the receiving terminal determines whether the "SL process ID + first destination ID + first source ID + communication type" in the SCI for scheduling newly transmitted SL data is associated with an SL process (denoted as SL process 2). If the "SL process ID + first destination ID + first source ID + communication type" in the SCI for scheduling newly transmitted SL data is associated with SL process 2, SL process 2 is deemed to be unoccupied, the buffer of SL process 2 is cleared, and an unoccupied SL process (denoted as SL process 3) is selected for the SCI for scheduling newly transmitted SL data or newly transmitted data. Additionally, the SL process 3 is associated with "SL process ID+first destination ID+first source ID+communication type" in the SCI.

[0160] In another aspect, in a SL RRC connection, the receiving terminal performs a SL MAC reset, where the receiving terminal clears the buffers of all SL processes associated with the SL RRC connection.

[0161] Currently, there are the following problems with the SL process:

[0162] On the receiving side, when event 1 (the receiving terminal decides to perform a MAC reset on the SL RRC connection or the receiving terminal performs a MAC reset on the SL RRC connection), event 2 (the SL RRC connection is released), and event 3 (the receiving terminal skips receiving multicast and / or broadcast data) occur at the receiving terminal, the association between the SCI (or "SL process ID + first destination ID + first source ID + communication type") and the SL process is not released, and the SL process is not considered to be unoccupied. As a result, the following problems may occur:

[0163] On the other hand, SL processes are not considered to be unoccupied. As a result, these SL processes cannot be used to receive other data. This reduces the number of available SL processes.

[0164] On the other hand, if only the SL process is considered unoccupied and the association between the SCI and the SL process is not released, the receiving terminal may again receive newly transmitted SL data scheduled by the SCI (the SCI having the same “SL process ID + first destination ID + first source ID + communication type” as the previous SCI) because the association between the SCI and the SL process exists, and the receiving terminal may erroneously clear other data in the buffer of the SL process. See FIG. 4. For example, the receiving terminal receives SCI1 (including “SL process ID1 + first destination ID1 + first source ID1 + unicast”) used to schedule newly transmitted data 1. After receiving SCI1, the receiving terminal associates “SL process ID1 + first destination ID1 + first source ID1 + unicast” with SL process 1. In a subsequent procedure, when performing a MAC reset for the SL RRC connection, the receiving terminal determines that SL process 1 associated with the SL RRC connection is unoccupied. However, the receiving terminal does not release the association between "SL process ID1 + first destination ID1 + first source ID1 + unicast" and SL process 1. When the receiving terminal receives SCI2 (including "SL process ID2 + first destination ID2 + first source ID2 + unicast") used to schedule newly transmitted data 2, in this case the receiving terminal needs to select an unoccupied SL process for "SL process ID2 + first destination ID2 + first source ID2 + unicast". If the selected unoccupied SL process is SL process 1 and data 2 is not successfully received, the buffer of SL process 1 will contain data 2.In this case, when the receiving terminal receives SCI3 (including "SL process ID1+first destination ID1+first source ID1+unicast") used to schedule newly transmitted data 3, i.e., when the receiving terminal receives again an SCI for scheduling newly transmitted SL data corresponding to "SL process ID1+first destination ID1+first source ID1+unicast" or newly transmitted SL data, since the association relationship between "SL process ID1+first destination ID1+first source ID1+unicast" and SL process 1 still exists, the receiving terminal clears the buffer of SL process 1 associated with "SL process ID1+first destination ID1+first source ID1+unicast" and regards SL process 1 as unoccupied. In this case, the buffer of SL process 1 still contains data 2 to be processed. As a result, the terminal erroneously clears data 2, affecting the reception of data 2. Alternatively, when the transmission of data 2 fails because SL process 1 is erroneously determined to be unoccupied, SL process 1 may be used to receive other data, which will affect the reception of data 2.

[0165] When the above-mentioned events 1, 2, and 3 occur in the transmitting terminal, the transmitting terminal does not consider the SL processes to be unoccupied and does not clear the buffers of the SL processes. In this case, the following problems may occur: if the SL processes are not considered to be unoccupied, these SL processes cannot be used to transmit other data, and the number of available SL processes will decrease; if the buffers of the SL processes are not cleared, these SL processes cannot be used to transmit other data, and the number of available SL processes will decrease, resulting in buffer overload or false triggering of retransmission.

[0166] To solve these problems, this application provides a method for processing the SL process, including Embodiments 1 to 5. Hereinafter, Embodiments 1 to 5 will be described separately. Embodiment 1

[0167] Embodiment 1 may be used to solve the problem caused by the following situation: when event 1 occurs at the receiving terminal, the association relationship between the SCI and the SL process is not released and / or the SL process is not considered to be unoccupied. See Figure 5. The method includes the following steps:

[0168] 501: The terminal decides to perform a MAC reset on the RRC connection of the SL.

[0169] Step 501 may be described as the terminal performing a MAC reset for the RRC connection of the SL. The terminal may be a receiving terminal.

[0170] In an embodiment of this application, for example, the SL RRC connection may be a logical connection between a second source ID as a pair and a second destination ID as a pair, or a logical connection between a second source ID and a second destination ID as a pair in the access stratum (AS) layer. The SL RRC connection may also be referred to as a PC5-RRC connection. In an embodiment of this application, the SL RRC connection may include / be replaced with / correspond to any one or more of a unicast, a unicast connection, a destination address, a second source ID-second destination ID pair, and a second destination ID. In an embodiment of this application, for example, the SL RRC connection may be understood as / be replaced with a SL RRC connection, a unicast, a unicast connection, a destination address, a second source ID and a second destination ID as a pair, a second source ID-second destination ID pair, or a second destination ID. For example, the first SL RRC connection may be understood as / replaced with the first unicast, the first unicast connection, the first destination address, the second source ID1-second destination ID1 pair, or the second destination ID1.

[0171] In the embodiment of this application, for example, the destination address is used to identify unicast, multicast, or broadcast.

[0172] In the embodiment of this application, for example, a second source ID-second destination ID pair is used to identify a unicast.

[0173] In embodiments of this application, performing a MAC reset for an SL RRC connection may be understood to include / be replaced with / as performing an SL-specific MAC reset (sidelink-specific reset of the MAC entity) for an SL RRC connection.

[0174] In an embodiment of this application, for example, any two or more of the SL RRC connection, unicast connection, destination address, second source ID-second destination ID pair, second destination ID, second source ID, first source ID corresponding to the second source ID and first destination ID corresponding to the second destination ID as a pair, first destination ID corresponding to the second destination ID, first destination ID corresponding to the second destination ID, and first source ID corresponding to the second source ID may be associated / corresponding to each other.

[0175] It should be noted that step 501 does not restrict whether the terminal has performed a MAC reset for the SL RRC connection, for example, step 501 may be understood as the terminal performing / preparing to perform a MAC reset for the SL RRC connection.

[0176] 502: The terminal determines that the first SL process is unoccupied, and / or the terminal releases an association relationship associated with the first SL process.

[0177] The first SL process is / includes the SL processes associated with the SL RRC connection. For example, the first SL process may be / include one or more, or all, of the SL processes associated with the SL RRC connection.

[0178] An SL process associated with an SL RRC connection may be understood as an SL process associated with a second source ID and a second destination ID and corresponding to the SL RRC connection, or an SL process associated with a first source ID and a first destination ID and corresponding to the SL RRC connection. For example, the second source ID and second destination ID corresponding to the SL RRC connection are second source ID1 and second destination ID2, and the SL process associated with the SL RRC connection is the SL process associated with second source ID1 and second destination ID2. For example, the second source ID and second destination ID corresponding to the SL RRC connection are second source ID1 and second destination ID2, and the first source ID and first destination ID corresponding to second source ID1 and second destination ID2 are first source ID1 and first destination ID2, and the SL process associated with the SL RRC connection is the SL process associated with first source ID1 and first destination ID2.

[0179] In an embodiment of this application, the first SL process or the SL process associated with the SL RRC connection may include / be replaced with any one or more of the SL process associated with a unicast connection, the SL process associated with a destination address, the SL process associated with a second destination ID, the SL process associated with a second source ID-second destination ID pair, the SL process associated with a first destination ID, and the SL process associated with a first source ID-first destination ID pair. For example, the association relationship associated with the first SL process includes an association relationship between the first SL process and an SCI, and / or an association relationship between the first SL process and one or more of an SL process ID, a first destination ID, a first source ID, and a communication type.

[0180] In embodiments of this application, determining that an SL process is unoccupied may include or be replaced with any one or more of considering the SL process to be unoccupied, releasing the SL process, and deactivating the SL process. For example, determining that a first SL process is unoccupied may be understood as releasing the first SL process.

[0181] In an embodiment of the present application, releasing an association relationship associated with an SL process may include / be replaced with deleting an association relationship associated with an SL process. For example, releasing an association relationship associated with a first SL process may include / be replaced with deleting an association relationship associated with the first SL process.

[0182] For example, see FIG. 6. For association relationships that exist in the terminal or previously existed in the terminal and are related to SL processes, see the left side of FIG. 6. When the terminal determines to perform a MAC reset on the SL RRC connection where the first source ID and the first destination ID corresponding to the SL RRC connection are first source ID1 and first destination ID1, respectively, and the SL processes related to the SL RRC connection are SL process 1 and SL process 2, the terminal releases SL process 1 and SL process 2 and releases the association relationships related to SL process 1 and SL process 2. In this case, for association relationships that exist in the terminal and are related to the SL processes, see the right side of FIG. 6. It should be noted that the association relationships related to the SL processes shown in FIG. 6 are merely an example, and that in actual implementation, the association relationships related to the SL processes may be different. This is not a limitation in this application.

[0183] Optionally, step 501 includes one or more of the following actions: (1) an upper layer of the terminal's MAC layer requests a MAC reset for the SL RRC connection; (2) the terminal / terminal's MAC layer is requested to perform a MAC reset for the SL RRC connection; (3) an upper layer of the terminal's MAC layer requests the terminal's MAC layer to perform a MAC reset for the SL RRC connection; (4) the terminal's MAC layer decides to perform a MAC reset for the SL RRC connection; and (5) the terminal's MAC layer performs a MAC reset for the SL RRC connection.

[0184] Optionally, the terminal determining that the first SL process is unoccupied comprises a MAC layer of the terminal determining that the first SL process is unoccupied.

[0185] Optionally, the terminal releasing an association relationship associated with the first SL process comprises a MAC layer of the terminal releasing an association relationship associated with the first SL process.

[0186] For example, the MAC layer of the terminal may specifically be the MAC entity of the terminal.

[0187] For example, layers above the MAC layer include an RRC layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.

[0188] Optionally, when the following condition 3 is met, the terminal performs one or more of the actions in step 501 or (1) to (5). Condition 3 includes any one or more of: an upper layer of the RRC layer of the terminal requesting the RRC layer of the terminal to release the SL RRC connection; an upper layer of the RRC layer of the terminal requesting to release the SL RRC connection; an upper layer of the RRC layer of the terminal indicating to the RRC layer of the terminal to release the SL unicast connection (PC5 unicast link) of the upper layer of the RRC layer of the terminal; an upper layer of the RRC layer of the terminal indicating to the RRC layer of the terminal to release the SL unicast connection of the upper layer of the RRC layer of the terminal; the SL unicast connection of the upper layer of the RRC layer of the terminal being released; the RRC layer of the terminal / terminal being requested to release the SL RRC connection; the RRC layer of the terminal / terminal being indicated to release the SL unicast connection of the upper layer of the RRC layer of the terminal; and the RRC layer of the terminal / terminal releasing the SL RRC connection.

[0189] Specifically, condition 1 (when an SL RLF occurs) and condition 2 (when the terminal receives an SL RRC reconfiguration message with full configuration) trigger the terminal to decide to perform a MAC reset for the SL RRC connection or to perform a MAC reset for the SL RRC connection. Additionally, condition 3 may trigger the terminal to perform the aforementioned actions.

[0190] In an embodiment of this application, for example, the upper layer of the RRC layer of the terminal may be a V2X layer, a non-access stratum (NAS) layer, an application (APP) layer, or the like.

[0191] In the embodiments of this application, a request may be understood as including / replaced with / as any one or more of setting and displaying.

[0192] According to the method provided in embodiment 1, when the terminal decides to perform a MAC reset on the SL RRC connection or when the terminal performs a MAC reset on the SL RRC connection, the terminal determines that the first SL process is unoccupied, and as a result, the SL process may be used to receive other data. This avoids a reduction in the number of available SL processes and improves the data reception rate. According to the method provided in embodiment 1, when the terminal decides to perform a MAC reset on the SL RRC connection or when the terminal performs a MAC reset on the SL RRC connection, the terminal releases the association relationship related to the first SL process to prevent the terminal from erroneously clearing other data or to ensure reception of data related to the first SL process. This can improve the reliability of data reception. Embodiment 2

[0193] Embodiment 2 may be used to solve the problem caused by the following situation: when event 1 occurs at the transmitting terminal, the SL process is not considered to be unoccupied and / or the buffer of the SL process is not cleared. See Figure 7. The method includes the following steps:

[0194] 701: The terminal decides to perform a MAC reset for an RRC connection in SL.

[0195] Step 701 may be described as the terminal performing a MAC reset for the RRC connection of the SL. The terminal may be a transmitting terminal. For a related description of step 701, refer to step 501. The details will not be described again here.

[0196] 702: The terminal determines that the first SL process is unoccupied, and / or the terminal clears the buffer of the first SL process.

[0197] For a related description of the "first SL process" in embodiment 2, please refer to embodiment 1. The details will not be described again here.

[0198] For the related description of "determining that the SL process is unoccupied" in embodiment 2, please refer to embodiment 1. The details will not be described again here.

[0199] In an embodiment of this application, clearing the buffer of an SL process may include / be replaced with deleting the buffer of the SL process. For example, clearing the buffer of a first SL process may include / be replaced with deleting the buffer of the first SL process. For example, when the first source ID and the first destination ID corresponding to the SL RRC connection are first source ID1 and first destination ID1, respectively, and the SL processes associated with the SL RRC connection are the SL processes associated with the first source ID1 and first destination ID1 (e.g., SL process 1 and SL process 2), if the terminal determines to perform a MAC reset for the SL RRC connection, the terminal releases SL process 1 and SL process 2 and / or clears the buffers of SL process 1 and SL process 2.

[0200] Optionally, step 701 includes one or more of the following actions: (1) an upper layer of the terminal's MAC layer requests a MAC reset for the SL RRC connection; (2) the terminal / terminal's MAC layer is requested to perform a MAC reset for the SL RRC connection; (3) an upper layer of the terminal's MAC layer requests the terminal's MAC layer to perform a MAC reset for the SL RRC connection; (4) the terminal's MAC layer decides to perform a MAC reset for the SL RRC connection; and (5) the terminal's MAC layer performs a MAC reset for the SL RRC connection.

[0201] Optionally, the terminal determining that the first SL process is unoccupied comprises a MAC layer of the terminal determining that the first SL process is unoccupied.

[0202] Optionally, the terminal clearing the buffer of the first SL process includes a MAC layer of the terminal clearing the buffer of the first SL process. For a related description of the optional method, see embodiment 1. The details will not be described again here. For example, the MAC layer of the terminal may specifically be a MAC entity of the terminal.

[0203] Optionally, when condition 3 is met, the terminal performs one or more actions in step 701 or (1) to (5). For a related description of condition 3, please refer to embodiment 1. The details will not be described again here.

[0204] Optionally, when the following condition 4 is met, the terminal performs any one or more of the actions in step 701 or (1) to (5). Condition 4 may be that the terminal transmits an SL RRC Reconfiguration message, or that the terminal transmits an SL RRC Reconfiguration message and the terminal receives an SL RRC Reconfiguration Complete message. The SL RRC Reconfiguration message includes a full configuration indication. The SL RRC Reconfiguration message is associated with an SL RRC connection. The SL RRC Reconfiguration Complete message is associated with an SL RRC connection. The SL RRC Reconfiguration Complete message corresponds to the SL RRC Reconfiguration message.

[0205] For example, when the terminal sends an SL RRC Reconfiguration message for the SL RRC connection, or when the terminal sends an SL RRC Reconfiguration message for the SL RRC connection and receives an SL RRC Reconfiguration Complete message, the SL RRC Reconfiguration message includes a full configuration indication. The first source ID and first destination ID corresponding to the SL RRC connection are first source ID1 and first destination ID1, respectively, and the SL processes associated with the SL RRC connection are the SL processes associated with first source ID1 and first destination ID1 (e.g., SL process 1 and SL process 2). The terminal determines that SL process 1 and SL process 2 are unoccupied and / or clears the buffers of SL process 1 and SL process 2.

[0206] Specifically, in a case where the terminal transmits an SL RRC reconfiguration message and determines to perform a MAC reset for the SL RRC connection, the terminal sets the SL RRC reconfiguration message, or when / before / after the terminal transmits the RRC reconfiguration message, the terminal determines to perform a MAC reset for the SL RRC connection. This is not limited in this application. Setting the SL RRC reconfiguration message may be understood as generating or determining the SL RRC reconfiguration message.

[0207] The transmission of the SL RRC reconfiguration message may be specifically performed by the RRC layer of the terminal.

[0208] Specifically, condition 1 (when an SL RLF occurs) and condition 2 (when the terminal receives an SL RRC reconfiguration message with full configuration) trigger the terminal to decide to perform a MAC reset for the SL RRC connection or to perform a MAC reset for the SL RRC connection. Additionally, condition 3 and / or condition 4 may trigger the terminal to perform the aforementioned actions.

[0209] It should be noted that the terminal may also perform step 702 directly when the terminal sends an SL RRC reconfiguration message, or when the terminal sends an SL RRC reconfiguration message and receives an SL RRC reconfiguration complete message.

[0210] According to the method provided in embodiment 2, when the terminal decides to perform a MAC reset on the SL RRC connection or when the terminal performs a MAC reset on the SL RRC connection, the terminal determines that the first SL processes are unoccupied, so that these SL processes may be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data reception rate. According to the method provided in embodiment 2, when the terminal decides to perform a MAC reset on the SL RRC connection or when the terminal performs a MAC reset on the SL RRC connection, the terminal clears the buffer of the first SL process, so that storage space may be released, or these SL processes may be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data reception rate. Embodiment 3

[0211] Embodiment 3 may be used to solve problems caused by one or more of the following actions: when event 2 occurs at the receiving terminal, the association relationship between the SCI and the SL process is not released, the SL process is considered to be unoccupied, and the buffer of the SL process is cleared. Furthermore, embodiment 3 may be used to solve problems caused by the following situations: when event 2 occurs at the transmitting terminal, the SL process is not considered to be unoccupied and / or the buffer of the SL process is not cleared. See Figure 8. The method includes the following steps.

[0212] 801: The terminal releases the RRC connection of the SL, i.e., the terminal skips the transmission or reception of unicast data.

[0213] The terminal may be a transmitting terminal or a receiving terminal. For a related description of the RRC connection of the SL, please refer to embodiment 1. The details will not be described again here.

[0214] 802: The terminal performs one or more of the following actions: the terminal determines that the first SL process is unoccupied; the terminal releases an association relationship associated with the first SL process; and the terminal clears a buffer of the first SL process.

[0215] The first SL process is / includes an SL process associated with an SL RRC connection. For example, the first SL process may be / include one or more or all of the SL processes associated with an SL RRC connection. For related descriptions of "first SL process" or "SL process associated with an SL RRC connection," refer to embodiment 1. Details will not be described again here. Optionally, when the terminal is a receiving terminal, the association relationship associated with the first SL process includes an association relationship between the first SL process and an SCI, and / or an association relationship between the first SL process and one or more of an SL process ID, a first destination ID, a first source ID, and a communication type.

[0216] In embodiment 3, for related descriptions of "determining that the SL process is unoccupied" and "releasing the association relationship related to the SL process", please refer to embodiment 1, and for related descriptions of "clearing the buffer of the SL process", please refer to embodiment 2. The details will not be described again here.

[0217] For example, when a terminal releases an SL RRC connection where the first source ID and first destination ID corresponding to the SL RRC connection are first source ID1 and first destination ID1, respectively, and the SL processes associated with the SL RRC connection are the SL processes associated with first source ID1 and first destination ID1 (e.g., SL process 1 and SL process 2), the terminal performs one or more of the following actions: determining that SL process 1 and SL process 2 are unoccupied, clearing the buffers of SL process 1 and SL process 2, and releasing the association relationships associated with SL process 1 and SL process 2.

[0218] Optionally, the terminal releasing the RRC connection of the SL includes the RRC layer of the terminal releasing the RRC connection of the SL, or requesting an upper layer of the RRC layer of the terminal to release the RRC connection.

[0219] Optionally, the terminal determining that the first SL process is unoccupied comprises a MAC entity of the terminal determining that the first SL process is unoccupied.

[0220] Optionally, the terminal releasing an association relationship associated with the first SL process comprises a MAC entity of the terminal releasing an association relationship associated with the first SL process.

[0221] Optionally, the terminal clearing a buffer of the first SL process comprises a MAC entity of the terminal clearing a buffer of the first SL process.

[0222] Optionally, when condition 3 is met, the RRC layer of the terminal releases the RRC connection of the SL.

[0223] According to the method provided in embodiment 3, when a terminal releases the SL RRC connection, the terminal determines that the first SL processes are unoccupied, so that these SL processes may be used to transmit or receive other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception rate. According to the method provided in embodiment 3, when a terminal releases the SL RRC connection, the buffer of the first SL process may be cleared, so that storage space may be released, or these SL processes may be used to transmit or receive other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception rate. According to the method provided in embodiment 3, when a terminal releases the SL RRC connection, the association relationship related to the first SL process may be released. This prevents the receiving terminal from erroneously clearing other data, improving the reliability of data reception. Alternatively, the reception of data related to the first SL process is guaranteed, improving the reliability of data reception. Embodiment 4

[0224] Embodiment 4 may be used to solve problems caused by one or more of the following actions: when event 3 occurs at the receiving terminal, the association relationship between the SCI and the SL process is not released, the SL process is considered to be unoccupied, and the buffer of the SL process is cleared. Furthermore, embodiment 4 may be used to solve problems caused by the following situations: when event 3 occurs at the transmitting terminal, the SL process is not considered to be unoccupied and / or the buffer of the SL process is not cleared. See Figure 9. The method includes the following steps.

[0225] 901: The terminal skips sending or receiving sidelink data to a destination address.

[0226] The destination address is used to distinguish between multicast, broadcast, and unicast.

[0227] In embodiments of this application, the destination address may include / be replaced with / correspond to any one or more of multicast, multicast service, broadcast, broadcast service, unicast, unicast connection, SL RRC connection, second source ID-second destination ID pair, second destination ID, first source ID-first destination ID pair, and first destination ID.

[0228] In embodiments of this application, the destination address may alternatively include, be replaced with, or correspond to one or more of the following: destination address, multicast, multicast service, broadcast service, SL RRC connection, unicast, unicast connection, destination address, second source ID and second destination ID as a pair, second source ID-second destination ID pair, second destination ID, first source ID and first destination ID as a pair, first source ID-first destination ID pair, or first destination ID. For example, the first destination address may be understood as or replaced with the first multicast, first multicast service, first broadcast, first broadcast service, first SL RRC connection, first unicast, first unicast connection, first destination address, second source ID1-second destination ID1 pair, second destination ID1, first source ID1-first destination ID1 pair, or first destination ID1.

[0229] It should be noted that skipping transmission or reception may be understood as transmission or reception having been previously performed and (re)transmission or reception not currently being performed. This is not limited to future transmission or reception. 902: The terminal performs one or more of the following actions: the terminal determines that the second SL process is unoccupied; the terminal releases an association relationship related to the second SL process; and the terminal clears the buffer of the second SL process. For example, the action in step 902 may be performed by the MAC layer of the terminal.

[0230] The second SL process is / includes the SL process associated with the destination address. For example, the second SL process may be / include one or more or all of the SL processes associated with the destination address.

[0231] The destination address-related SL process may be understood as an SL process related to a second destination ID corresponding to the destination address or an SL process related to a first destination ID corresponding to the destination address. For example, the second destination ID corresponding to the destination address is second destination ID2, and the SL process related to the destination address is the SL process related to second destination ID2. For example, the second destination ID corresponding to the destination address is second destination ID2, and the first destination ID corresponding to second destination ID2 is first destination ID2, and the SL process related to the destination address is the SL process related to first destination ID2. In embodiments of this application, the destination address-related SL process or the first SL process may include or be replaced with any one or more of an SL process related to a multicast / multicast service, an SL process related to a broadcast / broadcast service, an SL process related to a second destination ID, and an SL process related to a first destination ID.

[0232] For example, when the terminal is a receiving terminal, the association relationship associated with the second SL process includes an association relationship between the second SL process and an SCI, and / or an association relationship between the second SL process and one or more of an SL process ID, a first destination ID, a first source ID, and a communication type.

[0233] In embodiment 4, for related descriptions of "determining that the SL process is unoccupied" and "releasing the association relationship related to the SL process", please refer to embodiment 1, and for related descriptions of "clearing the buffer of the SL process", please refer to embodiment 2. Details will not be described again here.

[0234] For example, see FIG. 10 . Multicast is used as an example. For association relationships that exist in the terminal or previously existed in the terminal and are related to SL processes, see the left side of FIG. 10 . When the first source ID and the first destination ID corresponding to the destination address are the first destination ID 2 and the first destination ID 2, respectively, and the SL processes related to the destination address are the SL processes 3 and 4, if the terminal skips receiving SL data for the destination address, the terminal releases the SL processes 3 and 4 and / or releases the association relationships with the SL processes 3 and 4. In this case, for association relationships that exist in the terminal and are related to the SL processes, see the right side of FIG. 10 . It should be noted that the association relationships related to the SL processes shown in FIG. 10 are merely an example, and that in actual implementation, the association relationships related to the SL processes may be different. This is not a limitation in this application.

[0235] Optionally, the terminal skipping sending or receiving SL data includes the transmission corresponding to the destination address being stopped or the terminal no longer needing to send or receive SL data corresponding to the destination address (in other words, the terminal is no longer interested in the transmission corresponding to the destination address).

[0236] The transmission corresponding to the destination address may include a multicast transmission or a broadcast transmission corresponding to the destination address.

[0237] Stopping transmission corresponding to a destination address may be understood as stopping multicast or broadcast transmission corresponding to the destination address, in other words, multicast or broadcast to the destination address is stopped or is no longer sent.

[0238] The terminal not needing to send or receive SL data corresponding to the destination address may include the terminal determining that SL data corresponding to the destination address no longer needs to be sent or received, and the terminal no longer being interested in transmissions corresponding to the destination address.

[0239] A terminal being no longer interested in a transmission means that the terminal was previously interested but is no longer interested, and this does not necessarily mean that the terminal is interested in future transmissions.

[0240] Specifically, the upper layer of the RRC layer of the terminal may request (or indicate or configure) that it is no longer interested in transmissions corresponding to the destination address. The upper layer of the RRC layer of the terminal may request (or indicate or configure) that transmissions to the destination address be terminated.

[0241] According to the method provided in embodiment 4, when a terminal skips transmitting or receiving SL data for a destination address, the terminal determines that the second SL processes are unoccupied, and as a result, these SL processes can be used to transmit or receive other data. This avoids a decrease in the number of available SL processes and improves the data transmission / reception speed. According to the method provided in embodiment 4, when a terminal skips transmitting or receiving SL data for a destination address, the buffer of the second SL process can be cleared, and as a result, storage space can be released, or the SL process can be used to transmit or receive other data. This avoids a decrease in the number of available SL processes and improves the data transmission / reception speed. According to the method provided in embodiment 4, when a terminal skips transmitting or receiving SL data for a destination address, the association relationship related to the second SL process can be released, to prevent the receiving terminal from erroneously clearing other data or to ensure the reception of data related to the first SL process. This can improve the reliability of data reception.

[0242] Embodiment 5 may be used to solve problems caused by one or more of the following actions: when event 3 occurs at the receiving terminal, the association relationship between the SCI and the SL process is not released, the SL process is considered to be unoccupied, and the buffer of the SL process is cleared. Furthermore, embodiment 5 may be used to solve problems caused by the following situations: when event 3 occurs at the transmitting terminal, the SL process is not considered to be unoccupied and / or the buffer of the SL process is not cleared. See Figure 11. The method includes the following steps.

[0243] 1101: The terminal decides to perform a MAC reset on the destination address.

[0244] In the embodiments of this application, performing a MAC reset on a destination address may be understood to include / replace / as performing an SL-specific MAC reset (sidelink-specific reset of a MAC entity) on the destination address. For a related description of the destination address, see embodiment 4. The details will not be described again here.

[0245] Step 1101 may also be described as the terminal performing a MAC reset on the destination address.

[0246] The destination address is used to identify a multicast or broadcast.

[0247] Optionally, before step 1101, the method further includes: the terminal skipping the transmission or reception of SL data for the destination address. Also, for a related description of the following action, i.e., "the terminal skips the transmission or reception of SL data for the destination address," please refer to embodiment 4. The details will not be described again here.

[0248] 1102: The terminal performs one or more of the following actions: the terminal determines that the second SL process is unoccupied; the terminal releases an association relationship associated with the second SL process; and the terminal clears a buffer of the second SL process, where the second SL process is the SL process associated with the destination address.

[0249] Optionally, the association relationship associated with the second SL process includes an association relationship between the second SL process and an SCI, and / or an association relationship between the second SL process and one or more of an SL process ID, a first destination ID, a first source ID, and a communication type.

[0250] See step 902 above for a related explanation of step 1102. The details will not be repeated here.

[0251] According to the method provided in embodiment 5, when a terminal performs a MAC reset for a destination address, it determines that the second SL processes are unoccupied, and as a result, these SL processes may be used to transmit or receive other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception speed. According to the method provided in embodiment 5, when a terminal performs a MAC reset for a destination address, the buffer of the second SL process may be cleared, and as a result, storage space may be released, or the SL process may be used to transmit or receive other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception speed. According to the method provided in embodiment 5, when a terminal performs a MAC reset for a destination address, the association relationship related to the second SL process may be released. This prevents the receiving terminal from erroneously clearing other data, and improves the reliability of data reception. Alternatively, reception of data related to the first SL process is guaranteed, improving the reliability of data reception.

[0252] Additionally, in addition to the above-described first to fifth embodiments, the following solutions 1 and 2 may also be used.

[0253] Solution 1: PC5-S transmission for the destination address is stopped at a higher layer of the RRC layer, or the higher layer of the RRC layer requests (or indicates or configures) to terminate PC5-S transmission for the destination address, and the terminal performs one or more of the following actions: the terminal determines that the fourth SL process is unoccupied, the terminal releases the association relationship related to the fourth SL process, and the terminal clears the buffer of the fourth SL process. The fourth SL process refers to the SL process related to the destination address or the PC5-S of the destination address.

[0254] Solution 2: PC5-S transmission for the destination address is stopped in a higher layer of the RRC layer, or the higher layer of the RRC layer requests (or indicates or configures) termination of PC5-S transmission for the destination address, the terminal performs a MAC reset for the destination address or the PC5-S of the destination address, and the terminal performs one or more of the following actions: the terminal determines that the fourth SL process is unoccupied; the terminal releases the association relationship related to the fourth SL process; and the terminal clears the buffer of the fourth SL process. Currently, in the existing NR V2X protocol, Mode 1 and Mode 2 cannot coexist, and retransmissions cannot be performed between different resource configuration modes. Specifically, data newly transmitted using Mode 1 resources cannot be retransmitted using Mode 2 resources, and data newly transmitted using Mode 2 resources cannot be retransmitted using Mode 1 resources. When the resource configuration mode is switched / changed (mode switching for short), the processing mechanism for the SL process is not specified on the transmitting terminal side. After the mode switching, if the processes occupied in the original resource setting mode are still occupied, the number of processes available to the transmitting terminal may decrease. To solve this problem, this application further provides a method for processing SL processes shown in Embodiment 6 and Embodiment 7. Hereinafter, the methods will be described separately. The terminal in Embodiment 6 and Embodiment 7 may be a transmitting terminal. Embodiment 6

[0255] Refer to Figure 12. The method for processing the SL process according to embodiment 6 includes the following steps.

[0256] 1201: The terminal determines that the resource configuration mode is the first resource configuration mode.

[0257] Step 1201 may also be described as follows: the terminal determines that the resource configuration mode is switched from the second resource configuration mode to the first resource configuration mode (i.e., the resource configuration mode of the terminal before the mode switching is the second resource configuration mode), or the terminal determines that the resource configuration mode is switched from the first resource configuration mode and the second resource configuration mode to the first resource configuration mode (i.e., before the mode switching, the resource configuration mode of the terminal is the first resource configuration mode and the second resource configuration mode).

[0258] In this application, switching may be substituted for changing.

[0259] The first resource configuration mode may be Mode 1 or Mode 2. The terminal determining that the resource configuration mode is the first resource configuration mode may include any one of the following: a MAC layer of the terminal determining that the resource configuration mode is the first resource configuration mode; a terminal / MAC layer of the terminal being configured with the first resource configuration mode as the resource configuration mode; an RRC layer of the terminal setting the first resource configuration mode as the resource configuration mode; and an RRC layer of the terminal setting the resource configuration mode in the MAC layer of the terminal as the first resource configuration mode. For example, specifically, when a MAC entity of the terminal configures that SL resources are associated with Mode 1, the terminal determines that the resource configuration mode is Mode 1. When an RRC layer of the terminal configures that SL resources are associated with Mode 2, the terminal determines that the resource configuration mode is Mode 2.

[0260] 1202: The terminal determines that the third SL process is unoccupied and / or clears the buffer of the third SL process.

[0261] The third SL process is an SL process associated with the second resource configuration mode, i.e., the third SL process or the SL process associated with the second resource configuration mode may be understood as an SL process that transmits data using resources corresponding to the second resource configuration mode and / or an SL process associated with resources corresponding to the second resource configuration mode.

[0262] If the first resource configuration mode is mode 1, the second resource configuration mode is mode 2. If the first resource configuration mode is mode 2, the second resource configuration mode is mode 1.

[0263] According to the method provided in embodiment 6, when the terminal determines that the resource configuration mode is the first resource configuration mode, the terminal determines that the third SL process is unoccupied, so that these SL processes can be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data reception speed. The buffer of the third SL process is cleared, so that storage space can be released, and the SL process can also be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception speed.

[0264] Optionally, the resources corresponding to the first resource configuration mode include configured SL grant resources (i.e., SL CG resources) or dynamic SL grant resources (i.e., SL DG resources) (i.e., the first resource configuration mode is Mode 1). Before step 1202, the method further includes the terminal (which may be, for example, a HARQ entity of the terminal) acquiring the configured SL grant resources or the dynamic SL grant resources (i.e., the Mode 1 resources are acquired and the resources are optionally newly transmitted resources), and / or the terminal determining that the number of unoccupied SL processes is less than or equal to a first threshold.

[0265] Optionally, the terminal acquiring the configured SL grant resource or the dynamic SL grant resource includes the terminal acquiring the configured SL grant resource or the dynamic SL grant resource and acquiring data transmitted on the configured SL grant resource or the dynamic SL grant resource.

[0266] The first threshold may be set / displayed / sent to the terminal by the network device, may be preset, may be specified in a protocol, may be stored in the terminal by a device manufacturer before the terminal is delivered from the factory, or may be preset in the terminal by the network device / another device when the terminal is connected to the network. For example, the first threshold may be 0, 2, 3, etc.

[0267] For example, the number of free SL processes being less than or equal to a first threshold may be understood as all SL processes being occupied, or the number of unoccupied SL processes being less than or equal to the number of SL processes required by the terminal.

[0268] After step 1201, the terminal may perform step 1202 directly, or may perform step 1202 when configured SL grant resources or dynamic SL grant resources are obtained and / or when the number of unoccupied SL processes is less than or equal to a first threshold.

[0269] When the first resource configuration mode is mode 1, the SL resources of the terminal are scheduled by the network device, and the terminal selects an SL process only after obtaining configured SL grant resources or dynamic SL grant resources. Therefore, the terminal may perform step 1202 when / after obtaining configured SL grant resources or dynamic SL grant resources.

[0270] Optionally, the resources corresponding to the first resource configuration mode include selection sidelink resources (i.e., the first resource configuration mode is Mode 2). Before step 1202, the method further includes the terminal determining the selection SL resources (i.e., the terminal performs resource selection or needs to determine resources), and / or the number of unoccupied SL processes is less than or equal to a first threshold.

[0271] After step 1201, the terminal may directly perform step 1202, or may perform step 1202 when the selected SL resource is determined and / or when the number of unoccupied SL processes is less than or equal to a first threshold.

[0272] It should be noted that when the first resource configuration mode is Mode 2, the SL resource of the terminal is selected by the terminal, and the terminal determines the SL process and performs resource selection. Therefore, the terminal may perform step 1202 when / after determining to perform resource selection.

[0273] Optionally, before step 1202, the method further includes: the terminal determining to perform a MAC reset for the second resource configuration mode. Specifically, the mode switch triggers a MAC reset for the second resource configuration mode, and the MAC reset triggers execution of step 1202.

[0274] In embodiments of this application, performing a MAC reset for the second resource configuration mode may be understood to include / replace / as performing an SL-specific MAC reset (sidelink-specific reset of the MAC entity) for the second resource configuration mode.

[0275] Optionally, during a particular implementation of step 1202, one or more third SL processes may be determined to be unoccupied and / or one or more buffers of the third SL processes may be cleared based on one or more of the following information:

[0276] Information 1: Priority of data related to the third SL process

[0277] Information 2: Delay requirements related to the third SL process

[0278] Information 3: Reliability requirements related to the third SL process

[0279] For example, in information 1, the terminal may determine that one or more SL processes associated with data having the lowest priority or a priority lower than a priority threshold are unoccupied, and / or the terminal may clear buffers corresponding to one or more SL processes.

[0280] For example, in information 2, the terminal may determine that one or more SL processes associated with data having the highest latency requirement or a latency requirement lower than a latency threshold are unoccupied, and / or the terminal may clear buffers corresponding to one or more SL processes.

[0281] For example, in information 3, the terminal may determine that one or more SL processes associated with data having the lowest reliability requirement or a reliability requirement lower than the reliability threshold are unoccupied, and / or the terminal may clear the buffers corresponding to one or more SL processes.

[0282] Mode switching may occur frequently in the terminal. If a process is released immediately after a mode switch, severe packet loss may occur. Services with high priority, low latency requirements, and high reliability requirements may not meet the requirements, and this optional method may be used to avoid this situation. Additionally, the terminal may determine that one or more SL processes associated with data are unoccupied after a period after the mode switch, and / or the terminal may clear buffers corresponding to one or more SL processes.

[0283] In embodiment 6, the terminal may process the SL processes one by one. For example, one SL process may be used to process one SL process, multiple SL processes may be used to process multiple SL processes, or all SL processes may be processed at once. This is not limited in this application. In this specification, "processing" includes determining that the SL process is unoccupied and / or clearing the buffer corresponding to the SL process.

[0284] Optionally, the method further includes the terminal releasing 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 the resources can be subsequently used by another terminal. Thus, resource utilization is improved.

[0285] Refer to Figure 13. The method for processing the SL process according to embodiment 7 includes the following steps.

[0286] 1301: The terminal decides to perform a MAC reset for the second resource configuration mode.

[0287] During a specific implementation of step 1301, the terminal may perform step 1301 when the second resource configuration mode is switched to another resource configuration mode. For example, the terminal may perform step 1301 when the resource configuration mode is switched from the second resource configuration mode to the first resource configuration mode. Alternatively, the terminal may 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. Alternatively, the terminal may perform step 1301 when triggered by another trigger condition.

[0288] The second resource configuration mode may be mode 1 or mode 2.

[0289] Optionally, before step 1301, the method further includes: the terminal determining that the resource configuration mode is the first resource configuration mode. For a related description of this step, see above step 1201. The details will not be described again here.

[0290] 1302: The terminal determines that the third SL process is unoccupied and / or clears the buffer of the third SL process.

[0291] Optionally, during a particular implementation of step 1302, one or more third SL processes may be determined to be unoccupied and / or one or more buffers of the third SL processes may be cleared based on one or more of the following information:

[0292] Information 1: Priority of data related to the third SL process

[0293] Information 2: Delay requirements related to the third SL process

[0294] Information 3: Reliability requirements related to the third SL process

[0295] For related descriptions of optional methods, please refer to the above-mentioned embodiment 6. The details will not be described again here.

[0296] Optionally, the method further includes the terminal releasing SL resources corresponding to the second resource configuration mode and / or configurations corresponding to SL sources corresponding to the second resource configuration mode, so that the resources can be subsequently used by another terminal, thus improving resource utilization.

[0297] According to the method provided in embodiment 7, when the terminal determines to perform MAC reset for the second resource configuration mode, the terminal determines that the third SL processes are unoccupied, so that these SL processes can be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data reception speed. The buffer of the third SL process is cleared, so that storage space can be released, and the SL process can also be used to transmit other data. This avoids a reduction in the number of available SL processes and improves the data transmission / reception speed.

[0298] Additionally, in mode switching scenarios, this application further provides embodiment 8 to improve resource utilization.

[0299] Refer to Figure 14. The method for releasing SL resources according to embodiment 8 includes the following steps.

[0300] 1401: The terminal determines that the resource configuration mode is the first resource configuration mode.

[0301] 1402: The terminal releases sidelink resources corresponding to the second resource configuration mode and / or configurations corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0302] For the related description of step 8, please refer to the related description in embodiment 6. The details will not be described again here. In embodiment 8, the SL resources related to the second resource configuration mode and / or the configuration corresponding to the SL resources related to the second resource configuration mode are released, so that the resources can be used by another terminal thereafter. Therefore, resource utilization is improved.

[0303] The methods shown in embodiments 6 to 8 are also applicable to the LTE system. When the methods are used in the LTE system, it is necessary to replace mode 1 with mode 3 and mode 2 with mode 4 for understanding.

[0304] In the above-described embodiment of this application, regardless of which parameters (e.g., destination address, second resource configuration mode, RRC connection of SL) are MAC reset, whether a MAC reset is performed for the parameters is not limited. For example, it can be understood that the terminal performs / prepares to perform a MAC reset for the parameters.

[0305] In the aforementioned embodiment of this application, the buffer of the SL process of the transmitting terminal may be referred to as an HARQ buffer, and the buffer of the SL process of the receiving terminal may be referred to as a soft buffer. In this application, regarding an SL process as being unoccupied may be described as releasing the SL process or deactivating the SL process, and an unoccupied SL process may also be described as a deactivated SL process. Similarly, regarding an SL process as being occupied may be described as activating the SL process, and an occupied SL process may also be described as an activated SL process.

[0306] The methods provided in the foregoing embodiments may be combined when there is no conflict between the solutions. In addition to being performed by the terminal, the methods provided in the foregoing embodiments may also be performed by other devices.

[0307] The foregoing mainly describes the solutions of the embodiments of this application from the perspective of methods. It should be understood that to implement the aforementioned functions, the terminal includes at least one of a corresponding hardware structure or a corresponding software module for performing each function. Those skilled in the art should readily recognize that this application may be implemented by hardware or a combination of hardware and computer software, in combination with the example units and algorithm steps described in the embodiments disclosed in this specification. Whether a function is performed by hardware or by hardware driven by computer software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered to go beyond the scope of this application.

[0308] In the embodiments of this application, the functional units of the terminal may be divided based on the above-mentioned example method. For example, the terminal may be divided based on the corresponding functions, or two or more functions may be integrated into one processing unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit. It should be noted that in the embodiments of this application, the division into units is merely an example and represents only a logical functional division. In actual implementation, other division methods may be used.

[0309] For example, FIG. 15 is a schematic diagram of a possible structure of an apparatus (denoted as apparatus 150) used in the aforementioned embodiments. Apparatus 150 includes a processing unit 1501 and a communication unit 1502. Optionally, apparatus 150 further includes a storage unit 1503. Apparatus 150 may be configured to exemplify the structure of a terminal in the aforementioned embodiments. In this case, processing unit 1501 is configured to control and manage actions of the terminal. For example, processing unit 1501 is configured to perform the steps of FIGS. 5, 7, 8, 9, 11, 12, 13, and 14 and / or actions performed by the terminal in other processes described in the embodiments of this application. Processor 1501 may use communication unit 1502 to communicate with other network entities, for example, to transmit SL data or SCI to other terminals. Storage unit 1503 is configured to store program codes and data of the terminal.

[0310] For example, the apparatus 150 may be a device, a chip, or a chip system.

[0311] When the apparatus 150 is a device, the processing unit 1501 may be a processor, and the communication unit 1502 may be a communication interface, a transceiver, or an input interface and / or an output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the transceiver may be an input circuit, and the output interface may be an output circuit.

[0312] When the device 150 is a chip or a chip system, the communication unit 1502 may be a communication interface, an input interface and / or an output interface, an interface circuit, an output circuit, an input circuit, a pin, related circuits, etc. on the chip or chip system. The processing unit 1501 may be a processor, a processing circuit, a logic circuit, etc.

[0313] When the integrated unit in FIG. 15 is implemented in the form of a software functional module and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions in the embodiments of this application may essentially contribute to the prior art, or all or part of the technical solutions may be implemented in the form of a software product. A computer software product is stored in a storage medium and includes a plurality of instructions that enable a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to perform all or part of the steps of the method in the embodiments of this application. Storage media for storing computer software products include any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0314] An embodiment of this application further provides a schematic diagram of the hardware structure of the device. See Figure 16 or Figure 17. The device includes a processor 1601, and optionally further includes a memory 1602 connected to the processor 1601.

[0315] The processor 1601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to control program execution in the solutions of this application. Alternatively, the processor 1601 may 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 be one or more devices, circuits, or processing cores configured to process data (e.g., computer program instructions).

[0316] The memory 1602 may be a ROM or another type of static storage device capable of storing static information and instructions, a RAM or another type of dynamic storage device capable of storing information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or another optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in the form of instructions or data structures and that can be accessed by a computer. This is not limited to this embodiment of the application. The memory 1602 may exist independently (in which case the memory 1602 may be located external to the device or internal to the device) or may be integrated with the processor 1601. The memory 1602 may include computer program code. The processor 1601 is configured to execute computer program codes stored in the memory 1602 to implement the methods provided in the embodiments of this application.

[0317] See FIG. 16. In a first possible implementation, the device further includes a transceiver 1603. The processor 1601, the memory 1602, and the transceiver 1603 are connected via a bus. The transceiver 1603 is configured to communicate with another device or a communication network. Optionally, the transceiver 1603 may include a transmitter and a receiver. A component within the transceiver 1603 configured to implement a receiving function may be considered a receiver, and the receiver is configured to perform the receiving step in the embodiments of this application. A component within the transceiver 1603 configured to implement a transmitting function may be considered a transmitter, and the transmitter is configured to perform the transmitting step in the embodiments of this application.

[0318] Based on a first possible implementation, the structural diagram shown in FIG. 16 may be used to illustrate the structure of the terminal in the aforementioned embodiment. In this case, processor 1601 is configured to control and manage the operation of the terminal. For example, processor 1601 is configured to perform the steps of FIGS. 5, 7, 8, 9, 11, 12, 13, and 14 and / or actions performed by the terminal in other processes described in the embodiments of this application. Processor 1601 may use transceiver 1603 to communicate with other network entities, for example, to transmit SL data or SCI to other terminals. Memory 1602 is configured to store program codes and data for the terminal.

[0319] In a second possible implementation, the processor 1601 includes a logic circuit and an input interface and / or an output interface. For example, the output interface is configured to perform a transmitting action in a corresponding manner, and the input interface is configured to perform a receiving action in a corresponding manner. See FIG. 17. Based on the second possible implementation, the structural diagram shown in FIG. 17 may be used to illustrate the terminal in the aforementioned embodiment. In this case, the processor 1601 is configured to control and manage the operation of the terminal. For example, the processor 1601 is configured to perform the steps of FIGS. 5, 7, 8, 9, 11, 12, 13, and 14 and / or actions performed by the terminal in other processes described in the embodiments of this application. The processor 1601 may use the input interface and / or output interface to communicate with other network entities, for example, to transmit SL data or SCI to other terminals. The memory 1602 is configured to store program codes and data for the terminal.

[0320] In the implementation process, the steps of the methods provided in the embodiments may be completed using instructions in the form of hardware integrated logic circuits or software in a processor. The steps of the methods disclosed with reference to the embodiments of this application may be directly executed by a hardware processor, or may be executed using a combination of hardware and software modules in a processor.

[0321] An embodiment of this application further provides a computer-readable storage medium containing computer-executable instructions, which, when run on a computer, enable the computer to perform any one of the methods described above.

[0322] An embodiment of the present application further provides a computer program product including computer-executable instructions that, when run on a computer, enable the computer to perform any one of the methods described above.

[0323] An embodiment of the present application further provides a communication system including the aforementioned terminal.

[0324] An embodiment of the present application further provides an apparatus including a processor and an interface, wherein the processor is coupled to a memory using the interface, and when the processor executes a computer program or computer-executable instructions in the memory, any of the methods provided in the above-mentioned embodiments are performed.

[0325] In the description of this application, unless otherwise specified, " / " means "or." For example, A / B may represent A or B. In this specification, the term "and / or" describes only the association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent three cases: only A exists, both A and B exist, and only B exists. In the description of this application, unless otherwise specified, "at least one" means one or more, and "multiple" means two or more.

[0326] Additionally, in order to clearly describe the technical solutions in the embodiments of this application, terms such as "first", "second", etc. are used in the embodiments of this application to distinguish between identical or similar items that basically provide the same function or purpose. Those skilled in the art will understand that terms such as "first", "second", etc. do not limit the number or execution order, and terms such as "first", "second", etc. do not indicate clear differences.

[0327] All or part of the foregoing embodiments may be implemented using software, hardware, firmware, or any combination thereof. When a software program is used to implement an embodiment, the embodiment may be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of this application are generated, in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) transmission. A computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or data center, that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state drives (SSDs)).

[0328] Although this application has been described with reference to embodiments, in the process of implementing this application for which protection is claimed, those skilled in the art may understand and implement other variations of the disclosed embodiments by referring to the accompanying drawings, the disclosed content, and the appended claims. In the claims, "comprising" does not exclude other components or steps, and "a" or "one" does not exclude the meaning of "plurality." A single processor or other unit may implement several functions recited in the claims. Although several measures are recited in mutually different dependent claims, this does not mean that these measures cannot be combined to produce better effects.

[0329] Although this application has been described with reference to specific features and embodiments thereof, it is clear that various modifications and combinations may be made thereto without departing from the scope of protection of this application. Correspondingly, the specification and the accompanying drawings are merely exemplary descriptions of this application as defined by the appended claims, and any or all of the modifications, variations, combinations or equivalents covering the scope of this application are considered. It is clear that a person skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application intends to cover these modifications and variations of this application, provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims

1. 1. A method for processing a sidelink process, applied to a terminal, comprising: determining to perform a Medium Access Control (MAC) reset for a sidelink Radio Resource Control (RRC) connection; determining, by a MAC entity of the terminal, that a first sidelink process is unoccupied; releasing an association relationship associated with the first sidelink process; and clearing a buffer of the first sidelink process, wherein the association relationship is between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type; the first sidelink process is a sidelink process associated with the RRC connection; The method, wherein determining to perform a MAC reset on a sidelink RRC connection includes requesting, by an upper layer of a MAC layer of the terminal, to perform a MAC reset on the RRC connection.

2. The method of claim 1 , further comprising: requesting, by an upper layer of an RRC layer of the terminal, to release the RRC connection.

3. 1. An apparatus for processing a sidelink process, comprising: a processing unit, the processing unit comprising: determining to perform a Medium Access Control (MAC) reset for a sidelink Radio Resource Control (RRC) connection; and configured to: determine, by a MAC entity of the device, that a first sidelink process is unoccupied; release an association relationship associated with the first sidelink process; and clear a buffer of the first sidelink process, the association relationship being between the first sidelink process and one or more of a first source identifier, a first destination identifier, a sidelink process identifier, and a communication type; the first sidelink process is a sidelink process associated with the RRC connection. The apparatus, wherein the processing unit is further configured to request, at an upper layer of a MAC layer, a MAC reset for the RRC connection.

4. The processing unit The apparatus of claim 3 , further configured to request, at an upper layer of an RRC layer, to release the RRC connection.

5. A computer-readable storage medium containing computer-executable instructions, which when executed on a computer enable the computer to perform the method of any one of claims 1 to 2.

6. A computer program comprising computer-executable instructions, which when run on a computer enable the computer to carry out the method of any one of claims 1 to 2.

Images