Method and apparatus for processing sidelink processes

Abstract

The present application provides a method and apparatus for processing a sidelink process, which relates to the field of communication technologies. In this method, a terminal determines to perform a MAC reset on an RRC connection of the sidelink. After that, the terminal can determine that the sidelink processes associated with the RRC connection (denoted as the first sidelink processes) are not occupied, so that these SL processes can be used for receiving other data, avoiding a reduction in the number of available SL processes and improving the data reception rate. The terminal can also release the association relationships associated with the first sidelink processes, thereby avoiding the terminal from erroneously clearing other data, or ensuring the reception of data associated with the first sidelink processes, which can improve the reliability of data reception.

Description

Technical Field

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

[0002] Vehicle to everything (V2X) is a key technology for intelligent transportation systems and is considered to be one of the areas with the most industrial potential and the clearest market demand in the Internet of Things system. Generally, V2X refers to a communication network that provides vehicle information through sensors, vehicle-mounted terminals, etc. installed on vehicles to achieve direct communication between vehicles (vehicle to vehicle, V2V), vehicle to infrastructure (V2I), vehicle to network (V2N), and vehicle to pedestrian (V2P).

[0003] V2X has the characteristics of wide application space, large industrial potential, and strong social benefits, and is of great significance for promoting the innovative development of the automotive and information and communication industries, building new models and new formats of automotive and transportation services, promoting the innovation and application of technologies such as driverless, assisted driving, intelligent driving, connected driving, intelligent connected driving, autonomous driving, and car sharing, and improving traffic efficiency and safety levels.

[0004] Generally, in the V2X scenario, the communication link for direct communication between terminals can be referred to as a sidelink (SL) or a side link. The hybrid automatic repeat request (HARQ) process on the SL can be called an 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 processing SL processes to avoid a reduction in the number of available SL processes.

[0006] In a first aspect, a method for processing a sidelink process is provided, including: a terminal determines to perform a MAC reset on an RRC connection of the sidelink; the terminal determines that a first sidelink process is unoccupied; and / or, the terminal releases an association relationship associated with the first sidelink process; wherein the first sidelink process is a sidelink process associated with the RRC connection. The method provided in the first aspect can determine that the first SL process is unoccupied when the terminal determines to perform a MAC reset on the RRC connection for the SL or the terminal performs a MAC reset on the RRC connection for the SL, so that these SL processes can be used for receiving other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. By releasing the association relationship associated with the first SL process, it is possible to avoid the terminal erroneously clearing other data, or to ensure the reception of data associated with the first SL process, improving the reliability of data reception.

[0007] In a possible implementation, the terminal determines to perform a MAC reset on the RRC connection of the sidelink, including: the upper layer of the MAC layer of the terminal requests to perform a MAC reset on the RRC connection; the terminal determines that the first sidelink process is unoccupied, including: the MAC entity of the terminal determines that the first sidelink process is unoccupied; the terminal releases the association relationship associated with the first sidelink process, including: the MAC entity of the terminal releases the association relationship associated with the first sidelink process.

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

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

[0010] Second aspect, a method for processing sidelink processes is provided, including: a terminal determines to perform a MAC reset on the RRC connection for the sidelink; the terminal determines that a first sidelink process is unoccupied; and / or, the terminal clears the cache of the first sidelink process; wherein, the first sidelink process is a sidelink process associated with the RRC connection. The method provided by the second aspect can determine that the first SL process is unoccupied when the terminal determines to perform a MAC reset on the RRC connection for the SL or when the terminal performs a MAC reset on the RRC connection for the SL, so that these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes and improving the data reception rate. By clearing the cache of the first sidelink process, storage space can be released.

[0011] In a possible implementation, the terminal determines to perform a MAC reset on the RRC connection for the sidelink, including: the upper layer of the MAC layer of the terminal requests to perform a MAC reset on the RRC connection; the terminal determines that a first sidelink process is unoccupied, including: the MAC entity of the terminal determines that the first sidelink process is unoccupied; the terminal clears the cache of the first sidelink process, including: the MAC entity of the terminal clears the cache of the first sidelink process.

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

[0013] In a possible implementation, before the terminal determines to perform a MAC reset on the RRC connection for the sidelink, the method further includes: the terminal sends an SL RRC reconfiguration message, or, the terminal sends an SL RRC reconfiguration message and the terminal receives an SL RRC reconfiguration complete message; wherein, the SL RRC reconfiguration message includes an indication of full configuration.

[0014] In a third aspect, a method for processing sidelink processes is provided, including: a terminal releases the RRC connection of the sidelink; the terminal performs one or more of the following actions: the terminal determines that a first sidelink process is unoccupied, the terminal releases the association relationship associated with the first sidelink process, the terminal clears the cache of the first sidelink process; wherein, the first sidelink process is a sidelink process associated with the RRC connection. The method provided in the third aspect can determine that the first SL process is unoccupied when the terminal releases the RRC connection of the SL, so that these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. By clearing the cache of the first SL process, the storage space can be released. By releasing the association relationship associated with the first SL process, it is possible to avoid the receiving terminal erroneously clearing other data, thereby improving the reliability of data reception.

[0015] In a possible implementation, the terminal releases the RRC connection of the sidelink, including: the RRC layer of the terminal releases the RRC connection, or, the upper layer of the RRC layer of the terminal requests to release the RRC connection; the terminal determines that the first sidelink process is unoccupied, including: the MAC entity of the terminal determines that the first sidelink process is unoccupied; the terminal releases the association relationship associated with the first sidelink process, including: the MAC entity of the terminal releases the association relationship associated with the first sidelink process; the terminal clears the cache of the first sidelink process, including: the MAC entity of the terminal clears the cache of the first sidelink process.

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

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

[0018] Fourth aspect, a method for processing sidelink processes is provided, including: for a destination address, the terminal no longer sends or receives sidelink data; the terminal performs one or more of the following actions: the terminal determines that a second sidelink process is unoccupied; the terminal releases the association relationship associated with the second sidelink process; the terminal clears the cache of the second sidelink process; wherein, the second sidelink process is a sidelink process associated with the destination address. The method provided by the fourth aspect can determine that the second SL process is unoccupied when the terminal no longer sends or receives SL data for a destination address, so that these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes and improving the data reception rate. By clearing the cache of the second SL process, storage space can be released. By releasing the association relationship associated with the second SL process, it is possible to prevent the receiving terminal from erroneously clearing other data.

[0019] In a possible implementation manner, that the terminal no longer sends or receives sidelink data includes: the transmission corresponding to the destination address terminates, or, the terminal does not need to send or receive sidelink data corresponding to the destination address.

[0020] In a possible implementation manner, the association relationship associated with the second sidelink process includes: the association relationship between the second sidelink process and the SCI, and / or, the 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] Fifth aspect, a method for processing sidelink processes is provided, including: for a destination address, the terminal determines to perform a MAC reset; the terminal performs one or more of the following actions: the terminal determines that a second sidelink process is unoccupied; the terminal releases the association relationship associated with the second sidelink process; the terminal clears the cache of the second sidelink process; wherein, the second sidelink process is a sidelink process associated with the destination address. The method provided by the fifth aspect can determine that the second SL process is unoccupied when the terminal performs a MAC reset for a destination address, so that these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes and improving the data reception rate. By clearing the cache of the second SL process, storage space can be released. By releasing the association relationship associated with the second SL process, it is possible to prevent the receiving terminal from erroneously clearing other data and improve the reliability of data reception.

[0022] In a possible implementation manner, before the terminal determines to perform a MAC reset, the method further includes: for the destination address, the terminal no longer sends or receives sidelink data.

[0023] In a possible implementation, the association relationship associated with the second sidelink process includes: the association relationship between the second sidelink process and the SCI, and / or the 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] In a sixth aspect, a method for processing a sidelink process is provided, including: a terminal determines that a resource configuration mode is a first resource configuration mode; the terminal determines that a third sidelink process is unoccupied, and / or clears the cache of the third sidelink process; wherein the third sidelink process is a sidelink process associated with a second resource configuration mode. For the method provided in the sixth aspect, if the terminal determines that the resource configuration mode is the first resource configuration mode, since the second resource configuration mode and the first resource configuration mode cannot exist simultaneously, the terminal does not adopt the resources of the second resource configuration mode. At this time, by determining that the third SL process is unoccupied, these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes and improving the data reception rate. By clearing the cache of the third SL process, storage space can be released.

[0025] In a possible implementation, the resources corresponding to the first resource configuration mode include configured sidelink authorization resources and / or dynamic sidelink authorization resources. Before the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process, the method further includes: the terminal obtains the configured sidelink authorization resources or dynamic sidelink authorization resources, and / or determines 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. Before the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process, the method further includes: the terminal determines the selected sidelink resources, and / or determines that the number of unoccupied sidelink processes is less than or equal to a first threshold.

[0027] In a possible implementation, before the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process, the method further includes: for the second resource configuration mode, the terminal determines to perform a MAC reset.

[0028] In a possible implementation, the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process, including: the terminal determines that one or more of the third sidelink processes are unoccupied according to one or more of the priority of the data associated with the third sidelink process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, and / or clears the cache of one or more of the third sidelink processes. In the terminal, the situation of frequent mode switching may occur. If the process is released immediately after the mode switch, serious packet loss may occur, and the requirements may not be met for services with high priority, low latency requirements, and high reliability requirements. This possible implementation can avoid this situation.

[0029] In a possible implementation, the method further includes: the terminal releases the sidelink resources corresponding to the second resource configuration mode and / or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode, so that these resources can be used by other terminals subsequently, improving resource utilization.

[0030] In a seventh aspect, a method for processing a sidelink process is provided, including: for a second resource configuration mode, the terminal determines to perform a MAC reset; the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process; wherein, the third sidelink process is a sidelink process associated with the second resource configuration mode. For the method provided in the seventh aspect, if the terminal performs a MAC reset for the second resource configuration mode, by determining that the third SL process is unoccupied, these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. By clearing the cache of the third SL process, storage space can be released.

[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 determines that the resource configuration mode is the first resource configuration mode.

[0032] In a possible implementation, the terminal determines that the third sidelink process is unoccupied, and / or clears the cache of the third sidelink process, including: the terminal determines that one or more of the third sidelink processes are unoccupied according to one or more of the priority of the data associated with the third sidelink process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, and / or clears the cache of one or more of the third sidelink processes.

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

[0034] In an eighth aspect, a method for releasing sidelink resources is provided, including: The terminal determines that the resource configuration mode is the first resource configuration mode; The terminal releases the sidelink resources corresponding to the second resource configuration mode and / or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode. By releasing the SL resources associated with the second resource configuration mode and / or the configuration corresponding to the SL resources associated with the second resource configuration mode in the eighth aspect, these resources can be used by other terminals subsequently, improving resource utilization.

[0035] In a ninth aspect, an apparatus for processing sidelink processes is provided, including: A processing unit, configured to: Determine to perform a MAC reset on the RRC connection of the sidelink; Determine that the first sidelink process is unoccupied; and / or, Release the association relationship associated with the first sidelink process; Wherein, the first sidelink process is a sidelink process associated with the RRC connection.

[0036] In a possible implementation, the processing unit is specifically configured to: Request to perform a MAC reset on the RRC connection at the upper layer of the MAC layer; Determine that the first sidelink process is unoccupied at the MAC entity; Release the association relationship associated with the first sidelink process at the MAC entity.

[0037] In a possible implementation, the processing unit is further configured to: Request to release the RRC connection at the upper layer of the RRC layer.

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

[0039] In a tenth aspect, an apparatus for processing sidelink processes is provided, including: A processing unit, configured to: Determine to perform a MAC reset on the RRC connection of the sidelink; Determine that the first sidelink process is unoccupied; and / or, Empty the cache 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 specifically configured to: Request to perform a MAC reset on the RRC connection at the upper layer of the MAC layer; Determine that the first sidelink process is unoccupied at the MAC entity; Empty the cache of the first sidelink process at the MAC entity.

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

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

[0043] In an eleventh aspect, an apparatus for processing a sidelink process is provided, including: a processing unit configured to: release the RRC connection of the sidelink; perform one or more of the following actions: determine that a first sidelink process is unoccupied, release an association relationship associated with the first sidelink process, and clear a cache 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 to release the RRC connection at a layer above the RRC layer; determine that the first sidelink process is unoccupied at the MAC entity; release the association relationship associated with the first sidelink process at the MAC entity; clear the cache of the first sidelink process at the MAC entity.

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

[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] In a twelfth aspect, an apparatus for processing a sidelink process is provided, including: a processing unit configured to; no longer send or receive sidelink data for a destination address; 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; clear a cache of the second sidelink process; wherein, the second sidelink process is a sidelink process associated with the destination address.

[0048] In a possible implementation, no longer sending or receiving sidelink data includes: termination of transmission corresponding to the destination address, or no need to send or receive sidelink data corresponding to the destination address.

[0049] In a possible implementation, the association relationship associated with the second sidelink process includes: the association relationship between the second sidelink process and the SCI, and / or the 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] In a thirteenth aspect, a device for processing a sidelink process is provided, including: a processing unit, configured to: for a destination address, determine to perform a MAC reset; perform one or more of the following actions: determine that the second sidelink process is unoccupied; release the association relationship associated with the second sidelink process; clear the cache of the second sidelink process; where 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: for the destination address, no longer send or receive sidelink data.

[0052] In a possible implementation, the association relationship associated with the second sidelink process includes: the association relationship between the second sidelink process and the SCI, and / or the 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] In a fourteenth aspect, a device for processing a sidelink process is provided, including: a processing unit, configured to: determine that the resource configuration mode is the first resource configuration mode; determine that the third sidelink process is unoccupied, and / or clear the cache of the third sidelink process; where the third sidelink process is the 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 sidelink grant resources and / or dynamic sidelink grant resources, and the processing unit is further configured to: obtain the configured sidelink grant resources or the dynamic sidelink grant resources, and / or 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 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: for the second resource configuration mode, determine to perform a MAC reset.

[0057] In a possible implementation, the processing unit is specifically configured to: determine one or more of the third sidelink processes as unoccupied according to one or more of the priority of the data associated with the third sidelink process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, and / or empty the cache of one or more of the third sidelink processes.

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

[0059] In a fifteenth aspect, a device for processing sidelink processes is provided, including: a processing unit, configured to: determine to perform a MAC reset for the second resource configuration mode; determine one or more of the third sidelink processes as unoccupied, and / or empty the cache of one or more of the third sidelink processes; where the third sidelink process is 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: determine one or more of the third sidelink processes as unoccupied according to one or more of the priority of the data associated with the third sidelink process, the latency requirement of the data associated with the third sidelink process, and the reliability requirement of the data associated with the third sidelink process, and / or empty the cache of one or more of the third sidelink processes.

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

[0063] In a sixteenth aspect, a device for releasing sidelink resources is provided, including: a processing unit, configured to: determine that the resource configuration mode is the first resource configuration mode; release the sidelink resources corresponding to the second resource configuration mode and / or the configuration corresponding to the sidelink resources corresponding to the second resource configuration mode.

[0064] In a seventeenth aspect, a device for processing sidelink processes is provided, including: a processor. The processor is connected to a memory, where the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing any one of the methods provided in any one of the first aspect to the seventh aspect. Exemplarily, the memory and the processor may be integrated together or may be separate devices. If the latter, the memory may be located inside or outside the device for processing sidelink processes.

[0065] In a possible implementation, the processor includes logic circuits and also includes an input interface and / or an output interface. Exemplarily, the output interface is used to perform the sending action in the corresponding method, and the input interface is used to perform the receiving action in the corresponding method.

[0066] In a possible implementation, the device for processing sidelink processes further includes a communication interface and a communication bus, and the processor, the memory, and the communication interface are connected through the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. 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 used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.

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

[0068] In an eighteenth aspect, a device for releasing sidelink resources is provided, including: a processor. The processor is connected to a memory, where the memory is used to store computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing the method provided in the eighth aspect. Exemplarily, the memory and the processor may be integrated together or may be separate devices. If the latter, the memory may be located inside or outside the device for releasing sidelink resources.

[0069] In a possible implementation, the processor includes logic circuits and also includes an input interface and / or an output interface. Exemplarily, the output interface is used to perform the sending action in the corresponding method, and the input interface is used to perform the receiving action in the corresponding method.

[0070] In a possible implementation, the apparatus for releasing sidelink resources further includes a communication interface and a communication bus. The processor, the memory, and the communication interface are connected through the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. 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 used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.

[0071] In a possible implementation, the apparatus for releasing sidelink resources exists in the form of a chip product.

[0072] In a nineteenth aspect, there is provided an apparatus for processing sidelink processes, including: a processor and an interface. The processor is coupled to a memory through the interface. When the processor executes the computer program or instructions in the memory, any one of the methods provided in any one of the first aspect to the seventh aspect is executed.

[0073] In a twentieth aspect, there is provided an apparatus for releasing sidelink resources, including: a processor and an interface. The processor is coupled to a memory through the interface. When the processor executes the computer program or instructions in the memory, the method provided in the eighth aspect is executed.

[0074] In a twenty-first aspect, there is provided a computer-readable storage medium including computer-executable instructions. When the computer-executable instructions run on a computer, the computer is caused to execute any one of the methods provided in any one of the first aspect to the eighth aspect.

[0075] In a twenty-second aspect, there is provided a computer program product including computer-executable instructions. When the computer-executable instructions run on a computer, the computer is caused to execute any one of the methods provided in any one of the first aspect to the eighth aspect.

[0076] For the technical effects brought by any one of the implementations in the ninth aspect to the twenty-second aspect, reference may be made to the technical effects brought by the corresponding implementations in the first aspect to the eighth aspect, which will not be elaborated here.

[0077] It should be noted that on the premise that the solutions do not conflict, the solutions in the above aspects can be combined. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 FIG. is a schematic diagram of a communication scenario provided for an embodiment of the present application;

[0079] Figure 2 FIG. is a schematic diagram of sidelink authorization provided for an embodiment of the present application;

[0080] Figure 3Schematic diagram of a parallel HARQ process provided by an embodiment of the present application;

[0081] Figure 4 Schematic diagram of the association between an SCI and an SL process provided by an embodiment of the present application;

[0082] Figure 5 Schematic diagram of a method for processing an SL process provided by an embodiment of the present application;

[0083] Figure 6 Schematic diagram of a method for releasing the association relationship associated with an SL process provided by an embodiment of the present application;

[0084] Figure 7 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0085] Figure 8 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0086] Figure 9 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0087] Figure 10 Schematic diagram of another method for releasing the association relationship associated with an SL process provided by an embodiment of the present application;

[0088] Figure 11 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0089] Figure 12 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0090] Figure 13 Schematic diagram of another method for processing an SL process provided by an embodiment of the present application;

[0091] Figure 14 Schematic diagram of a method for releasing SL resources provided by an embodiment of the present application;

[0092] Figure 15 Schematic diagram of the composition of a terminal provided by an embodiment of the present application;

[0093] Figure 16 Schematic diagram of the hardware structure of a terminal provided by an embodiment of the present application;

[0094] Figure 17 Schematic diagram of another hardware structure of a terminal provided by an embodiment of the present application. Detailed implementation manners

[0095] In the description of this application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" herein is merely a relational description of associated objects, indicating that there can be three relationships. For example, A and / or B can represent three cases: A exists alone, A and B exist simultaneously, and B exists alone. In addition, "at least one" means one or more, and "a plurality of" means two or more. The terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. do not necessarily limit being different from each other.

[0096] It should be noted that in this application, words such as "exemplary" or "for example" are used to give examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0097] The method provided by the embodiments of this application is applicable 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, carsharing, etc.

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

[0099] The communication systems in the embodiments of this application include but are not limited to long term evolution (LTE) systems, fifth-generation (5G) systems, new radio (NR) systems, wireless local area networks (WLAN) systems, and future evolved systems or multiple communication convergence systems. Among them, the 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system.

[0100] The network device in the embodiments of the present application is an entity on the network side that is used to send signals, or receive signals, or send and receive signals. The network device can be a device deployed in a radio access network (RAN) that provides wireless communication functions for terminals. For example, it can be a transmission reception point (TRP), a base station, various forms of control nodes (such as a network controller, a radio controller (such as a radio controller in a cloud radio access network (CRAN) scenario)), etc. Specifically, the network device can be various forms of macro base stations, micro base stations (also called small stations), relay stations, access points (APs), etc., or an antenna panel of a base station. The control node can be connected to multiple base stations and configure resources for multiple terminals covered by the multiple base stations. In systems using different radio access technologies, the names of devices with base station functions may be different. For example, in an LTE system, it can be called an evolved NodeB (eNB or eNodeB), and in a 5G system or an NR system, it can be called a next generation node base station (gNB). The present application does not limit the specific name of the base station. The network device can also be a network device in a future evolved public land mobile network (PLMN), etc.

[0101] RAN) that provides wireless communication functions for terminals. For example, it can be a transmission reception point (TRP), a base station, various forms of control nodes (such as a network controller, a radio controller (such as a radio controller in a cloud radio access network (CRAN) scenario)), etc. Specifically, the network device can be various forms of macro base stations, micro base stations (also called small stations), relay stations, access points (APs), etc., or an antenna panel of a base station. The control node can be connected to multiple base stations and configure resources for multiple terminals covered by the multiple base stations. In systems using different radio access technologies, the names of devices with base station functions may be different. For example, in an LTE system, it can be called an evolved NodeB (eNB or eNodeB), and in a 5G system or an NR system, it can be called a next generation node base station (gNB). The present application does not limit the specific name of the base station. The network device can also be a network device in a future evolved public land mobile network (PLMN), etc.

[0102] The terminal in the embodiments of the present application is an entity on the user side that is used to receive signals, or send signals, or receive and send signals. The terminal is used to provide one or more of voice services and data connectivity services to users. The terminal may also be referred to as user equipment (UE), terminal device, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal may be a V2X device, for example, a smart car (smart car or intelligent car), a digital car (digitalcar), an unmanned car (unmanned car or driverless car or pilotless car or automobile), a self-driving car (self-driving car or autonomous car), a pure electric vehicle (pure EV or Battery EV), a hybrid electric vehicle (hybrid electric vehicle, HEV), a range extended electric vehicle (range extended EV, REEV), a plug-in hybrid electric vehicle (plug-in HEV, PHEV), a new energy vehicle (new energy vehicle), a roadside unit (roadsite unit, RSU). The terminal may also be a D2D device, for example, a power meter, a water meter, etc. The terminal may also be a mobile station (mobilestation, MS), a user unit (subscriber unit), a drone, an Internet of Things (Internet of Things, IoT) device, a station (station, ST) in a WLAN, a cellular phone (cellular phone), a smart phone (smart phone), a cordless phone, a wireless data card, a tablet computer, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digitalassistant, PDA) device, a laptop computer (laptop computer), a machine type communication (machine typecommunication, MTC) terminal, a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, an in-vehicle device, a wearable device (which may also be referred to as a wearable intelligent device). The terminal may also be a terminal in a next-generation communication system, for example, a terminal in a 5G system or a terminal in a future evolved PLMN, a terminal in an NR system, etc.

[0103] To make the embodiments of this application clearer, the following provides a brief introduction to the concepts and some content related to the embodiments of this application.

[0104] 1. Uplink (UL), Downlink (DL), SL

[0105] The wireless communication link through which a terminal sends data (i.e., uplink data) to a network device can be referred to as UL. The wireless communication link through which a network device sends data (i.e., downlink data) to a terminal can be referred to as DL. The UL interface and the DL interface can be collectively referred to as the Uu interface. Therefore, UL and DL can be collectively referred to as the Uu interface link.

[0106] The communication link for direct communication between terminals can be referred to as SL. SL can also be referred to as a sidelink. The data transmitted between terminals can be referred to as SL data.

[0107] Exemplarily, the data in the embodiments of this application can be understood as a transport block (TB) or a medium access control (MAC) protocol data unit (PDU). The data can also be referred to as a data packet or a message.

[0108] 2. SL resource configuration mode

[0109] The SL transmission resources adopted by the sending terminal in two terminals can be determined by any one of the following Method A and Method B.

[0110] Method A: Network device scheduling

[0111] The mode of the network device scheduling SL transmission resources can include the mode 1 (mode1) resource configuration mode (name in NR) or the mode 3 (mode3) resource configuration mode (name in LTE).

[0112] Among them, there are the following two types of SL transmission resources scheduled by the network device:

[0113] The first type: SL configured grant (CG) resources

[0114] In this case, it is not always necessary for the network device to separately allocate resources for each data transmission of the sending terminal. After the network device allocates resources for the sending terminal once, the sending terminal can use the above-allocated resources within a certain period of time in the future. The characteristic is "one allocation, multiple uses". Exemplarily, the network device can configure a periodically occurring time-domain resource for the sending terminal. Exemplarily, see Figure 2, the first time-domain resource that appears in this periodically appearing time-domain resource is symbols 4 to 9 of slot 1, and the period is 1 slot. Among them, each time the time-domain resource that appears is a grant for a SL (SL grant, hereinafter simply referred to as sidelink grant). Then, it can be understood that Figure 2 shows 4 sidelink grants. One sidelink grant corresponds to one sidelink grant ID. The sidelink grant IDs corresponding to the 4 sidelink grants are sidelink grant 0, sidelink grant 1, sidelink grant 2, and sidelink grant 3 respectively.

[0115] The SL CG resource can include SL type 1 (type1) CG (SL configured grant type 1) resource and SL type 2 (type2) CG (SL configured grant type 2) resource. The SL type1 CG resource can be the SL transmission resource directly configured by the network device to the transmitting terminal through radio resource control (RRC) signaling. The transmitting terminal can directly use this CG resource to transmit data without additional activation. The SL type1 CG resource can also be called the SL grant free resource. The SL type2 CG resource can be that the network device defines the period of the SL transmission resource through RRC signaling, and then activates this SL transmission resource through the physical downlink control channel (PDCCH) or downlink control information (DCI). The transmitting terminal cannot directly use this SL transmission resource to transmit data and can only use it after activation. The SL type2 CG resource can also be called the SL Semi-Persistent Scheduling (SL SPS) resource.

[0116] For SL, one or more CG resources can be supported on one carrier. Optionally, different SL CG resources can correspond to different indexes. Exemplarily, the CG resources with indexes 1, 2, and 3 can be denoted as SL CG1, SL CG2, and SL CG3 respectively.

[0117] The second type: SL dynamic grant (DG) resource

[0118] For example, it can be the SL transmission resource dynamically allocated by the network device to the transmitting terminal through DCI. The DCI can be carried in the PDCCH.

[0119] Method B: The transmitting terminal determines by itself

[0120] Exemplarily, the mode for the transmitting terminal to determine the SL transmission resources by itself may include the mode 2 (resource configuration mode in NR, named in NR) or the mode 4 (resource configuration mode in LTE, named in LTE).

[0121] In Method B, when the transmitting terminal is within the communication coverage of the network device, the network device may configure the SL resource pool for the transmitting terminal through a system information block (SIB) message or dedicated RRC signaling. The transmitting terminal may independently obtain the SL transmission resources from the SL resource pool to send control signals and / or data signals to the receiving terminal. When the transmitting terminal is outside the communication coverage of the network device, the transmitting terminal may independently obtain the SL transmission resources from the pre-configured SL resource pool to send control signals and / or data signals to the receiving terminal.

[0122] When obtaining the SL transmission resources from the SL resource pool, the transmitting terminal may sense or compete for the SL transmission resources. Specifically, the transmitting terminal competes with other terminals to obtain the appropriate SL transmission resources in the SL resource pool to send control signals and / or data signals. For example, the higher the priority of the V2X service or data to be transmitted in the transmitting terminal, the greater the chance of competing for the appropriate SL transmission resources in the SL resource pool.

[0123] For ease of description, this application abbreviates the mode 1 resource configuration mode, mode 2 resource configuration mode, mode 3 resource configuration mode, and mode 4 resource configuration mode as mode 1, mode 2, mode 3, and mode 4 respectively. In one possible case, in LTE V2X, mode 3 and mode 4 cannot exist simultaneously. In one possible case, in NR V2X, mode 1 and mode 2 cannot exist simultaneously.

[0124] 3. Sidelink control information (SCI)

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

[0126] 4. HARQ

[0127] HARQ is a technology that combines forward error correction (or forward error correction code) (FEC) with automatic repeat request (ARQ) method.

[0128] Among them, FEC means that the data sent by the sending end includes forward error correction codes or redundant information. When the receiving end receives the data and discovers an error through verification (for example, cyclic redundancy check (CRC) verification), it can be corrected through the forward error correction code or redundant information. In this way, the sending end can reduce the number of retransmissions (that is, re-transmit the data).

[0129] ARQ means that the receiving end judges the correctness of the received data through verification (for example, CRC verification). If the data is received correctly, the receiving end sends an acknowledgement (ACK) to inform the sending end. Otherwise, the receiving end sends a negative acknowledgement (NACK) to inform the sending end. When the sending end receives the NACK, it can re-transmit the data to the receiving end. ACK and NACK are the HARQ feedback.

[0130] In LTE V2X, since only broadcast services are supported, SL HARQ feedback is not supported. In NR V2X, unicast, multicast, and broadcast services are supported, and SL HARQ feedback is supported.

[0131] The following specifically introduces the content related to HARQ through three parts (a) to (c).

[0132] (a) HARQ process

[0133] HARQ uses the stop-and-wait protocol to send data. In the stop-and-wait protocol, after the sending end sends a transport block (TB), it stops and waits for the acknowledgement information. The receiving end can feedback ACK or NACK for this TB. However, stopping and waiting for the acknowledgement after each transmission will result in very low throughput. Therefore, the sending end can use multiple parallel HARQ processes: when one HARQ process is waiting for the acknowledgement, the sending end can use another HARQ process to continue sending data. Exemplarily, see Figure 3, the terminal uses the first HARQ process to send TB1, finishes sending TB1 at time T1, receives the HARQ feedback of TB1 at time T2. During the time period from T1 to T2, it waits for the confirmation of TB1. During this waiting period for confirmation, it can use the second HARQ process to send TB2, finishes sending TB2 at time T2, receives the HARQ feedback of TB2 at time T3. During the time period from T2 to T3, it waits for the confirmation of TB2. During this waiting period for confirmation, it can use the third HARQ process to send TB3.

[0134] A HARQ process is identified by a HARQ process ID. The sidelink grant is associated with the HARQ process, and the terminal uses this process to transmit HARQ data in the sidelink grant associated with this HARQ process.

[0135] (b) Processing mechanism of the receiver for newly transmitted data and retransmitted data

[0136] Each HARQ process has a corresponding buffer (such as HARQ buffer or soft buffer) at the receiver to perform soft combining decoding on the received data.

[0137] After the receiver receives the newly transmitted data sent by the transmitter using a HARQ process, it can put the received newly transmitted data into the buffer corresponding to this HARQ process for decoding. If the decoding fails, when it receives the retransmitted data of this newly transmitted data again, it can combine the received retransmitted data with the previously stored newly transmitted data in the buffer, put it into the buffer, and decode again. This method can be called soft combining decoding, which improves the probability of successful decoding compared with separate decoding (that is, each transmitted data is decoded separately without combining with the previous data for decoding). Similarly, if the decoding still fails, the above process can be continued, combining the newly received retransmitted data with the data in the buffer and decoding again.

[0138] Among them, the retransmitted data and the newly transmitted data of the transmitter can be the same redundancy version (RV) or different RVs of the same TB.

[0139] The HARQ process on the Uu interface is called the HARQ process, and the HARQ process on the SL can be called the SL process (SLprocess).

[0140] (c) SL data transmission based on the SL process

[0141] A sending terminal can communicate with multiple receiving terminals. That is, a sending terminal can send SCI and SL data to multiple receiving terminals. A receiving terminal can also communicate with multiple sending terminals. That is, a receiving terminal can receive SCI and SL data from multiple sending terminals. The SCI can include an SL process ID, a first destination ID, a first source ID, and a communication type.

[0142] Among them, the SL process ID is used to identify the SL process, which is similar to the HARQ process ID of the Uu interface.

[0143] The first destination ID can be used to identify the target of the SL data scheduled by the SCI. Optionally, the first destination ID can be used for packet filtering by the PHY layer of the receiving terminal. Optionally, the first destination ID can be a part of the 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.

[0144] The second destination ID is used to identify the destination of the data (e.g., target) / receiving end / receiving terminal. Exemplarily, the second destination ID is used to identify a multicast or broadcast service. Exemplarily, the second destination ID can be the identifier of the destination / receiving end / receiving terminal. Exemplarily, the second destination ID can be the Destination Layer-2 ID. Optionally, the second destination ID can be used for packet filtering by the MAC layer of the receiving terminal.

[0145] The first source ID is used to identify the source of the SL data scheduled by the SCI. Optionally, the first source ID can be used for packet filtering by the PHY layer of the receiving terminal. Optionally, the first source ID can be a part of the 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.

[0146] The second source ID is used to identify the source of the data (e.g., sender) / sending end / sending terminal. Exemplarily, the second source ID can be the identifier of the source / sending end / sending terminal. Exemplarily, the second source ID can be the source Layer-2 ID. Optionally, the second source ID can be used for packet filtering by the MAC layer of the receiving terminal.

[0147] The communication type can include any one or more of unicast, multicast, and broadcast. The communication type in the SCI is used to indicate whether the current communication is unicast, multicast, or broadcast, or to indicate whether the SL data scheduled by the SCI is unicast data, multicast data, or broadcast data.

[0148] For example, the receiving terminal can detect the surrounding SCI, and then determine whether the SL data of the SCI or the SCI scheduling is of interest according to the first destination ID, the first source ID, and the communication type in the SCI. If it is of interest, it continues to receive the SL data scheduled by the SCI.

[0149] On the sending side, there is an SL HARQ entity. All the SL processes maintained by this SL HARQ entity (e.g., 16) are shared by all connection / communication types (casttype). On the receiving side, there is an SL HARQ entity. All the SL processes maintained by this SL HARQ entity (e.g., 64) are shared by all connection / communication types.

[0150] Different sending terminals may use the same SL process ID to communicate with the same receiving terminal. For the receiving terminal, in order to be able to distinguish the data associated with the same SL process ID from different sending terminals, after the receiving terminal receives an SCI and / or data and determines that the data is newly transmitted data, it will select an unoccupied SL process (denoted as SL process 1) for this data, and associate the "SL process ID + first destination ID + first source ID + communication type" in the SCI with SL process 1. When the receiving terminal receives retransmitted data corresponding to the same "SL process ID + first destination ID + first source ID + communication type" again, it can put the retransmitted data into the buffer of SL process 1 for soft combining decoding of the received data. Among them, the "first destination ID + first source ID + communication type" can be called sidelink identification information.

[0151] 5. MAC reset

[0152] On the Uu interface, when the terminal determines to perform a MAC reset (e.g., the upper layer of the terminal's MAC layer requests a MAC reset), the MAC entity of the terminal will perform any one or more of the following: stop the running timer, cancel the triggered beam failure recovery (BFR), cancel the triggered scheduling request (SR), reset the MAC-related counters (e.g., LBT_COUNTER, BFI_COUNTER, etc.), stop the ongoing random access process, etc. The specific content can refer to Section 5.12 of TS 38.321 and will not be elaborated here.

[0153] Currently, on the SL, when the terminal determines to perform MAC reset (for example, the upper layer of the terminal's MAC layer requests MAC reset for an RRC connection of an SL), the MAC entity of the terminal will perform any one or more of the following: cancel the triggered SR that is only associated with the RRC connection of this SL, cancel the triggered SL BSR that is only associated with the RRC connection of this SL, and clear the soft buffer of the SL process associated with the RRC connection of this SL. For specific content, reference can be made to Section 5.12 of TS 38.321, which will not be elaborated here.

[0154] Currently, for an RRC connection of an SL, when an SL radio link failure (RLF) occurs, or when the receiving terminal's MAC layer receives a fullconfig SL RRC reconfiguration (RRCReconfigurationSidelink) message, the receiving terminal performs MAC reset for the RRC connection of this SL.

[0155] The fullconfig SL RRC reconfiguration message can be understood as: the SL RRC reconfiguration message includes an indication of fullconfig. Among them, the indication of fullconfig is used to indicate that the SL RRC reconfiguration message should adopt fullconfig. For example, the indication of fullconfig is "sl-ResetConfig".

[0156] For example, the fullconfig SL RRC reconfiguration message means: for an RRC connection of an SL, the receiving terminal is fully reconfigured, that is, for the RRC connection of this SL, all configurations are updated. For unicast transmission, the transmitting terminal sends the configuration of the SL to the receiving terminal through the SL RRC reconfiguration message. When the parameter "sl-ResetConfig" is included in the SL RRC reconfiguration message, it means that all SL configurations are performed for the SL.

[0157] The above is a simple introduction to the concepts and some content related to the embodiments of the present application.

[0158] Currently, on the one hand, for the SL process, the receiving terminal regards the SL process as unoccupied in the following two cases:

[0159] 1) When the receiving terminal decodes the data successfully, it regards the SL process corresponding to this data as unoccupied.

[0160] 2) The receiving terminal receives again the SCI or the new transmission SL data for scheduling the new transmission SL data corresponding to the same "SL process ID + first destination ID + first source ID + communication type", and regards the SL process corresponding to the "SL process ID + first destination ID + first source ID + communication type" as unoccupied. Specifically, the receiving terminal determines whether the "SL process ID + first destination ID + first source ID + communication type" in an SCI for scheduling the new transmission SL data is associated with an SL process (denoted as SL process 2). If it is associated, the SL process 2 will be regarded as unoccupied and the cache of the SL process 2 will be cleared, and an unoccupied SL process (denoted as SL process 3) will be selected for the SCI of the new transmission SL data or the new transmission data, and the SL process 3 will be associated with the "SL process ID + first destination ID + first source ID + communication type" in the SCI.

[0161] On the other hand, for an RRC connection of an SL, the receiving terminal performs an SL MAC reset, and the receiving terminal will clear the caches of all SL processes associated with the RRC connection of the SL.

[0162] There are the following problems in the current processing of SL processes:

[0163] For the receiving side, when the receiving terminal encounters event 1 (the receiving terminal determines to perform a MAC reset for the RRC connection of the SL or the receiving terminal performs a MAC reset for the RRC connection of the SL), event 2 (the RRC connection of the SL is released), and event 3 (the receiving terminal no longer receives multicast and / or broadcast data), the receiving terminal does not release the association relationship between the SCI (or the "SL process ID + first destination ID + first source ID + communication type") and the SL process, nor regards the SL process as unoccupied. There will be the following problems:

[0164] On the one hand, not regarding the SL process as unoccupied makes these SL processes unavailable for receiving other data, resulting in a reduction in the number of available SL processes.

[0165] On the other hand, if only the SL process is regarded as unoccupied and the association relationship between the SCI and the SL process is not released, when the receiving terminal receives again the new transmission SL data scheduled by the SCI (the SCI whose "SL process ID + first destination ID + first source ID + communication type" is the same as the previous SCI), due to the existence of the association relationship between the SCI and the SL process, the receiving terminal may wrongly clear other data in the cache of the SL process. Exemplarily, see Figure 4, if the receiving terminal receives SCI1 (including "SL process ID1 + first destination ID1 + first source ID1 + unicast"), and SCI1 is used to schedule the newly transmitted data 1. After the receiving terminal receives SCI1, it associates "SL process ID1 + first destination ID1 + first source ID1 + unicast" with SL process 1. In the subsequent process, when the receiving terminal performs MAC reset on the RRC connection of SL, it determines that SL process 1 associated with the RRC connection of this SL is not occupied, but does not release the association relationship between "SL process ID1 + first destination ID1 + first source ID1 + unicast" and SL process 1. If the receiving terminal receives SCI2 (including "SL process ID2 + first destination ID2 + first source ID2 + unicast"), and SCI2 is used to schedule the newly transmitted data 2. At this time, 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 if data 2 is not successfully received, then the cache of SL process 1 contains data 2. At this time, if the receiving terminal receives SCI3 (including "SL process ID1 + first destination ID1 + first source ID1 + unicast"), and SCI3 is used to schedule the newly transmitted data 3, that is to say, the receiving terminal receives again the SCI for scheduling the newly transmitted SL data corresponding to "SL process ID1 + first destination ID1 + first source ID1 + unicast" or the 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, therefore, the receiving terminal will empty the cache of SL process 1 associated with "SL process ID1 + first destination ID1 + first source ID1 + unicast" and regard SL process 1 as unoccupied. And at this time, there is still data 2 to be processed in the cache of SL process 1. Therefore, the terminal will wrongly empty data 2, affecting the reception of data 2. Or, because SL process 1 is wrongly regarded as unoccupied, when the transmission of data 2 is not successful, SL process 1 may be used for other data reception, affecting the reception of data 2.

[0166] For the sending terminal, when the sending terminal experiences the above-mentioned Event 1, Event 2, and Event 3, it does not regard the SL process as unoccupied and does not empty the cache of the SL process. The following problems will exist: not regarding the SL process as unoccupied makes these SL processes unavailable for sending other data, resulting in a reduction in the number of available SL processes; not emptying the cache of the SL process may make these SL processes unavailable for sending other data, resulting in a reduction in the number of available SL processes, or, the cache is relatively large, or, retransmission is wrongly triggered.

[0167] To solve these problems, the present application provides a method for processing SL processes, including Embodiment 1 to Embodiment 5, which will be described separately below.

[0168] Embodiment 1

[0169] Embodiment 1 can solve the problems caused by the fact that when an event 1 occurs in the receiving terminal, the association relationship between the SCI and the SL process is not released, and / or the SL process is not regarded as unoccupied. See Figure 5 , the method includes:

[0170] 501. The terminal determines to perform a MAC reset on the RRC connection of the SL.

[0171] Step 501 can also be described as: The terminal performs a MAC reset on the RRC connection of the SL. Wherein, the terminal can be a receiving terminal.

[0172] In various embodiments of the present application, exemplarily, the RRC connection of the SL can be: a logical connection between a pair of second source IDs and second destination IDs; or, at the access-stratum (AS) layer, a logical connection between a pair of second source IDs and second destination IDs. The RRC connection of the SL can also be referred to as a PC5-RRC connection. In various embodiments of the present application, the RRC connection of the SL can include / replace / correspond to any one or more of the following: unicast, unicast connection, destination address, pair of second source ID and second destination ID, second destination ID. In various embodiments of the present application, exemplarily, the RRC connection of the SL can be understood as / replaced by: an RRC connection of an SL, or, a unicast, or, a unicast connection, or, a destination address, or, a pair of second source ID and second destination ID, or, a pair of a second source ID and a second destination ID, or, a second destination ID. For example, the RRC connection of the first SL can be understood as / replaced by: the first unicast, or, the first unicast connection, or, the first destination address, or, the pair of second source ID1 and second destination ID1, or, the second destination ID1.

[0173] In various embodiments of the present application, exemplarily, the destination address is used to identify a unicast, or, a multicast, or, a broadcast.

[0174] In various embodiments of the present application, exemplarily, the pair of second source ID and second destination ID is used to identify a unicast.

[0175] In various embodiments of the present application, performing a MAC reset on the RRC connection of the SL can include / replace / be understood as: performing a SL-specific MAC reset (Sidelink specific reset of the MAC entity) on the RRC connection of the SL.

[0176] In each embodiment of the present application, exemplarily, any two or more of the RRC connection of the SL, the unicast connection, the destination address, the second source ID and the second destination ID pair, the second destination ID, the second source ID, the first source ID corresponding to the second source ID, and the first destination ID pair corresponding to the second destination ID, the first destination ID corresponding to the second destination ID, and the first source ID corresponding to the second source ID may be associated / correspond to each other.

[0177] It should be noted that step 501 does not limit whether the terminal has performed MAC reset for the RRC connection of the SL. For example, step 501 can be understood as: the terminal will / prepare to perform MAC reset for the RRC connection of the SL.

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

[0179] Wherein, the first SL process is / includes the SL process associated with the RRC connection of the SL. Exemplarily, the first SL process can be / includes one or more or all of the SL processes associated with the RRC connection of the SL.

[0180] The SL process associated with the RRC connection of the SL can be understood as: the SL process associated with the second source ID and the second destination ID corresponding to the RRC connection of the SL, or, the SL process associated with the first source ID and the first destination ID corresponding to the RRC connection of the SL. For example, the second source ID and the second destination ID corresponding to an RRC connection of the SL are the second source ID1 and the second destination ID2, and the SL process associated with this RRC connection of the SL is the SL process associated with the second source ID1 and the second destination ID2. For example, the second source ID and the second destination ID corresponding to an RRC connection of the SL are the second source ID1 and the second destination ID2, and the first source ID and the first destination ID corresponding to the second source ID1 and the second destination ID2 are the first source ID1 and the first destination ID2, and the SL process associated with this RRC connection of the SL is the SL process associated with the first source ID1 and the first destination ID2.

[0181] In various embodiments of the present application, the first SL process or the SL process associated with the RRC connection of SL may include / replace with any one or more of the following: the SL process associated with the unicast connection, the SL process associated with the destination address, the SL process associated with the second destination ID, the SL process associated with the pair of the second source ID and the second destination ID, the SL process associated with the first destination ID, and the SL process associated with the pair of the first source ID and the first destination ID. Exemplarily, the association relationship associated with the first SL process includes: the association relationship between the first SL process and the SCI, and / or, the association relationship between the first SL process and one or more of the SL process ID, the first destination ID, the first source ID, and the communication type.

[0182] In various embodiments of the present application, determining that the SL process is unoccupied may include / replace with any one or more of the following: considering the SL process as unoccupied, releasing the SL process, and deactivating the SL process. For example, determining that the first SL process is unoccupied can be understood as releasing the first SL process.

[0183] In various embodiments of the present application, releasing the association relationship associated with the SL process may include / replace with: deleting the association relationship associated with the SL process. For example, releasing the association relationship associated with the first SL process may include / replace with: deleting the association relationship associated with the first SL process.

[0184] Exemplarily, refer to Figure 6 , the association relationship that exists in the terminal or previously existed in the terminal and is associated with the SL process can be referred to Figure 6 on the left side in. If the terminal determines to perform MAC reset for the RRC connection of an SL, where the first source ID and the first destination ID corresponding to the RRC connection of this SL are the first source ID1 and the first destination ID1 respectively, and the SL processes associated with the RRC connection of this SL are SL process 1 and SL process 2, the terminal releases SL process 1 and SL process 2, and / or, releases the association relationship associated with SL process 1 and SL process 2. In this case, the association relationship that exists in the terminal and is associated with the SL process can be referred to Figure 6 on the right side in. It should be noted that Figure 6 the association relationship associated with the SL process shown in is only an example. In actual implementation, the association relationship associated with the SL process can be other, and the present application does not make any restrictions.

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

[0186] Optionally, the terminal determines that the first SL process is unoccupied, including: The MAC layer of the terminal determines that the first SL process is unoccupied.

[0187] Optionally, the terminal releases the association relationship associated with the first SL process, including: The MAC layer of the terminal releases the association relationship associated with the first SL process.

[0188] Exemplarily, the MAC layer of the terminal may specifically be the MAC entity of the terminal.

[0189] Exemplarily, the upper layer of the MAC layer may be the RRC layer, the radio link control (RLC) layer, the packet data convergence protocol (PDCP) layer, etc.

[0190] Optionally, when the terminal meets condition 3, it performs step 501 or any one or more of the above (1)-(5) actions. Among them, condition 3 includes any one or more of the following: The upper layer of the RRC layer of the terminal requests the RRC layer of the terminal to release the RRC connection of the SL; The upper layer of the RRC layer of the terminal requests to release the RRC connection of the SL; The upper layer of the RRC layer of the terminal instructs the release of the SL unicast link (PC5 unicast link) of the upper layer of the RRC layer of the terminal; The upper layer of the RRC layer of the terminal instructs the RRC layer of the terminal to release the SL unicast link of the upper layer of the RRC layer of the terminal; The release of the SL unicast link of the upper layer of the RRC layer of the terminal; The RRC layer / terminal of the terminal is requested to release the RRC connection of the SL; The RRC layer / terminal of the terminal is instructed to release the SL unicast link of the upper layer of the RRC layer of the terminal; The RRC layer / terminal of the terminal releases the RRC connection of the SL.

[0191] That is to say, in addition to condition 1 (SL RLF occurs) and condition 2 (the terminal receives a fully configured SL RRC reconfiguration message), condition 3 can also be the condition for triggering the terminal to determine to perform a MAC reset for the RRC connection of the SL or the terminal to perform a MAC reset for the RRC connection of the SL.

[0192] In various embodiments of the present application, by way of example, the upper layer of the RRC layer of the terminal may be the V2X layer, the non-access stratum (NAS) layer, the application (APP) layer, etc.

[0193] In various embodiments of the present application, the request may include / replace / be understood as any one or more of the following: configuration, indication.

[0194] The method provided in the first embodiment can determine that the first SL process is unoccupied when the terminal determines to perform MAC reset on the RRC connection for SL or the terminal performs MAC reset on the RRC connection for SL, so that these SL processes can be used for receiving other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. The method provided in the first embodiment can, when the terminal determines to perform MAC reset on the RRC connection for SL or the terminal performs MAC reset on the RRC connection for SL, release the association relationship associated with the first SL process, thereby avoiding the terminal from erroneously clearing other data, or ensuring the reception of data associated with the first SL process, and improving the reliability of data reception.

[0195] The second embodiment

[0196] The second embodiment can solve the problems caused by the sending terminal not considering the SL process as unoccupied and / or not clearing the cache of the SL process when event 1 occurs. Refer to Figure 7 , the method includes:

[0197] 701. The terminal determines to perform MAC reset on the RRC connection for SL.

[0198] Step 701 may also be described as: The terminal performs MAC reset on the RRC connection for SL. Wherein, the terminal may be the sending terminal. For the relevant description of step 701, refer to step 501, which will not be elaborated here.

[0199] 702. The terminal determines that the first SL process is unoccupied; and / or, the terminal clears the cache of the first SL process.

[0200] For the relevant description of the "first SL process" in the second embodiment, refer to the first embodiment, which will not be elaborated here.

[0201] For the relevant description of "determining that the SL process is unoccupied" in the second embodiment, refer to the first embodiment, which will not be elaborated here.

[0202] In each embodiment of the present application, emptying the cache of the SL process may include / replace with: deleting the cache of the SL process. For example, emptying the cache of the first SL process may include / replace with: deleting the cache of the first SL process. Exemplarily, if the terminal determines to perform MAC reset for the RRC connection of an SL, where the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively, and the SL processes associated with the RRC connection of the SL are the SL processes associated with the first source ID1 and the first destination ID1 (for example, SL process 1 and SL process 2), the terminal releases SL process 1 and SL process 2, and / or empties the caches of SL process 1 and SL process 2.

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

[0204] Optionally, the terminal determines that the first SL process is unoccupied, including: the MAC layer of the terminal determines that the first SL process is unoccupied.

[0205] Optionally, the terminal empties the cache of the first SL process, including: the MAC layer of the terminal empties the cache of the first SL process. For the relevant description of this optional method, refer to Embodiment 1, which will not be elaborated here. Exemplarily, the MAC layer of the terminal may specifically be the MAC entity of the terminal.

[0206] Optionally, when the terminal meets condition 3, it executes step 701 or any one or more of the above actions (1)-(5). For the description of condition 3, refer to Embodiment 1, which will not be elaborated here.

[0207] Optionally, when the terminal meets condition 4, it executes step 701 or any one or more of the above actions (1)-(5). Wherein, condition 4 may be: the terminal sends an SL RRC reconfiguration message, or the terminal sends an SL RRC reconfiguration message and the terminal receives an SL RRC reconfiguration complete message. Wherein, the SL RRC reconfiguration message includes an indication of full configuration. The SL RRC reconfiguration message is associated with the RRC connection of the SL. The SL RRC reconfiguration complete message is associated with the RRC connection of the SL. The SL RRC reconfiguration complete message corresponds to the SL RRC reconfiguration message.

[0208] Exemplarily, if the terminal sends an SL RRC reconfiguration message for an RRC connection of an SL, or if the terminal sends an SL RRC reconfiguration message for an RRC connection of an SL and receives an SL RRC reconfiguration complete message, where the SL RRC reconfiguration message includes an indication of full configuration. Wherein, the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively, and the SL processes associated with the RRC connection of the SL are the SL processes associated with the first source ID1 and the first destination ID1 (for example, SL process 1 and SL process 2), the terminal determines that SL process 1 and SL process 2 are unoccupied, and / or clears the caches of SL process 1 and SL process 2.

[0209] Specifically, for the terminal to send an SL RRC reconfiguration message, in the case where the terminal determines to perform a MAC reset on the RRC connection of the SL, the terminal may determine to perform a MAC reset on the RRC connection of the SL when setting the SL RRC reconfiguration message, or when sending the SL RRC reconfiguration message, before sending the SL RRC reconfiguration message, or after sending the SL RRC reconfiguration message, and this application does not make any restrictions. Wherein, setting can be understood as generating or determining.

[0210] Wherein, sending the SL RRC reconfiguration message may specifically be executed by the RRC layer of the terminal.

[0211] That is to say, in addition to condition 1 (SL RLF occurs) and condition 2 (the terminal receives a fully configured SL RRC reconfiguration message), the conditions for triggering the terminal to determine to perform a MAC reset on the RRC connection of the SL or for the terminal to perform a MAC reset on the RRC connection of the SL may also include condition 3 and / or condition 4.

[0212] It should be noted that the terminal may also directly execute step 702 when sending the SL RRC reconfiguration message, or when sending the SL RRC reconfiguration message and the terminal receives the SL RRC reconfiguration complete message.

[0213] The method provided in Embodiment 2 can determine that the first SL process is unoccupied when the terminal determines to perform a MAC reset on the RRC connection of the SL or the terminal performs a MAC reset on the RRC connection of the SL, so that these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. The method provided in Embodiment 2 can, when the terminal determines to perform a MAC reset on the RRC connection of the SL or the terminal performs a MAC reset on the RRC connection of the SL, release the storage space by clearing the cache of the first SL process, and can also make these SL processes available for sending other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate.

[0214] Embodiment 3

[0215] Embodiment 3 can solve the problems caused by one or more actions of not executing the release of the association relationship between the SCI and the SL process, regarding the SL process as unoccupied, and clearing the cache of the SL process when the receiving terminal has Event 2. It can also solve the problems caused by not regarding the SL process as unoccupied and / or not clearing the cache of the SL process when the sending terminal has Event 2. Refer to Figure 8 , the method includes:

[0216] 801. The terminal releases the RRC connection of the SL. That is, the terminal no longer receives or sends unicast data.

[0217] Among them, the terminal can be a sending terminal or a receiving terminal. For the relevant description of the RRC connection of the SL, refer to Embodiment 1, which will not be elaborated here.

[0218] 802. The terminal performs one or more of the following actions: The terminal determines the first SL process as unoccupied, the terminal releases the association relationship associated with the first SL process, and the terminal clears the cache of the first SL process.

[0219] Among them, the first SL process is / includes the SL process associated with the RRC connection of the SL. Exemplarily, the first SL process can be / includes one or more or all SL processes associated with the RRC connection of the SL. For the relevant description of the "first SL process" or the "SL process associated with the RRC connection of the SL", refer to Embodiment 1, which will not be elaborated here. Optionally, when the terminal is a receiving terminal, the association relationship associated with the first SL process includes: the association relationship between the first SL process and the SCI, and / or the association relationship between the first SL process and one or more of the SL process ID, the first destination ID, the first source ID, and the communication type.

[0220] In Embodiment 3, for the relevant description of "determining the SL process as unoccupied" and "releasing the association relationship associated with the SL process", refer to Embodiment 1, and for the relevant description of "clearing the cache of the SL process", refer to Embodiment 2, which will not be elaborated here.

[0221] Exemplarily, if the terminal releases the RRC connection of the SL, where the first source ID and the first destination ID corresponding to the RRC connection of the SL are the first source ID1 and the first destination ID1 respectively, and the SL processes associated with the RRC connection of the SL are the SL processes associated with the first source ID1 and the first destination ID1 (for example, SL process 1 and SL process 2), the terminal performs one or more of the following actions: determining SL process 1 and SL process 2 as unoccupied, clearing the caches of SL process 1 and SL process 2, and releasing the association relationships associated with SL process 1 and SL process 2.

[0222] Optionally, the terminal releases the RRC connection of the SL, including: the RRC layer of the terminal releases the RRC connection of the SL, or, the upper layer of the RRC layer of the terminal requests to release the RRC connection.

[0223] Optionally, the terminal determines that the first SL process is unoccupied, including: the MAC entity of the terminal determines that the first SL process is unoccupied.

[0224] Optionally, the terminal releases the association relationship associated with the first SL process, including: the MAC entity of the terminal releases the association relationship associated with the first SL process.

[0225] Optionally, the terminal clears the cache of the first SL process, including: the MAC entity of the terminal clears the cache of the first SL process.

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

[0227] The method provided in Embodiment 3 can, when the terminal releases the RRC connection of the SL, determine that the first SL process is unoccupied, so that these SL processes can be used for sending or receiving other data, avoid a reduction in the number of available SL processes, and improve the rate of data sending or receiving. The method provided in Embodiment 3 can, when the terminal releases the RRC connection of the SL, release the storage space by clearing the cache of the first SL process, and can also make these SL processes be used for sending or receiving other data, avoid a reduction in the number of available SL processes, and improve the rate of data sending or receiving. The method provided in Embodiment 3 can, when the terminal releases the RRC connection of the SL, release the association relationship associated with the first SL process, thereby avoiding the receiving terminal erroneously clearing other data, improving the reliability of data reception, or ensuring the reception of data associated with the first SL process, and improving the reliability of data reception.

[0228] Embodiment 4

[0229] Embodiment 4 can solve the problems caused by the receiving terminal not performing one or more of releasing the association relationship between the SCI and the SL process, regarding the SL process as unoccupied, and clearing the cache of the SL process when event 3 occurs, and can also solve the problems caused by the sending terminal not regarding the SL process as unoccupied and / or not clearing the cache of the SL process when event 3 occurs. Refer to Figure 9 , the method includes:

[0230] 901. For a destination address, the terminal no longer sends or receives SL data.

[0231] Among them, the destination address is used to identify a multicast, or a broadcast, or a unicast.

[0232] In various embodiments of the present application, the destination address may include / replace / correspond to any one or more of the following: multicast, multicast service, broadcast, broadcast service, unicast, unicast connection, RRC connection of SL, pair of second source ID and second destination ID, second destination ID, pair of first source ID and first destination ID, first destination ID.

[0233] In various embodiments of the present application, the destination address may also include / replace / correspond to any one or more of the following: a destination address, a multicast, a multicast service, a broadcast, a broadcast service, an RRC connection of SL, or a unicast, or a unicast connection, or a destination address, or a pair of second source ID and second destination ID, or a second source ID and a pair of second destination ID, or a second destination ID, or a pair of first source ID and first destination ID, or a first source ID and a pair of first destination ID, or a first destination ID. For example, the first destination address may be understood as / replaced with: the first multicast, the first multicast service, the first broadcast, the first broadcast service, the first RRC connection of SL, or the first unicast, or the first unicast connection, or the first destination address, or the pair of second source ID1 and second destination ID1, or the second destination ID1, or the pair of first source ID1 and first destination ID1, or the first destination ID1.

[0234] It should be noted that no longer sending or receiving can be understood as: there was sending or receiving before, and currently there is no (longer) sending or receiving, and it does not limit that there will never be sending or receiving in the future. 902. The terminal performs one or more of the following actions: The terminal determines that the second SL process is unoccupied; the terminal releases the association relationship associated with the second SL process; the terminal clears the cache of the second SL process. Exemplarily, the actions in step 902 may be performed by the MAC layer of the terminal.

[0235] Among them, the second SL process is / includes the SL process associated with the destination address. Exemplarily, the second SL process may be / includes one or more or all of the SL processes associated with the destination address.

[0236] The SL process associated with the destination address can be understood as: the SL process associated with the second destination ID corresponding to the destination address, or the SL process associated with the first destination ID corresponding to the destination address. For example, if the second destination ID corresponding to a destination address is the second destination ID2, the SL process associated with this destination address is the SL process associated with the second destination ID2. For example, if the second destination ID corresponding to a destination address is the second destination ID2, and the first destination ID corresponding to the second destination ID2 is the first destination ID2, the SL process associated with this destination address is the SL process associated with the first destination ID2. In various embodiments of the present application, the first SL process or the SL process associated with the destination address may include / replace any one or more of the following: the SL process associated with multicast / multicast service, the SL process associated with broadcast / broadcast service, the SL process associated with the second destination ID, and the SL process associated with the first destination ID.

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

[0238] In Embodiment 4, for the related descriptions of "determining the SL process as unoccupied" and "releasing the association relationship associated with the SL process", reference can be made to Embodiment 1. For the related description of "clearing the cache of the SL process", reference can be made to Embodiment 2, and details will not be repeated.

[0239] Exemplarily, refer to Figure 10 , taking multicast as an example, the association relationship existing in the terminal or previously existing in the terminal and associated with the SL process can be seen in Figure 10 on the left side. If for a destination address, the terminal no longer receives SL data, where the first source ID and the first destination ID corresponding to this destination address are the first source ID2 and the first destination ID2 respectively, the SL processes associated with this destination address are SL process 3 and SL process 4, and the terminal releases SL process 3 and SL process 4, and / or releases the association relationship associated with SL process 3 and SL process 4. In this case, the association relationship existing in the terminal and associated with the SL process can be seen in Figure 10 on the right side. It should be noted that Figure 10 the association relationship associated with the SL process shown is only an example. In actual implementation, the association relationship associated with the SL process can be other, and the present application does not make any restrictions.

[0240] Optionally, the terminal no longer sends or receives SL data, including: the termination of the transmission corresponding to the destination address, or the terminal does not need to send or receive the SL data corresponding to the destination address (that is, the terminal is no longer interested in the transmission corresponding to the destination address).

[0241] The transmission corresponding to the destination address may include: multicast transmission or broadcast transmission corresponding to the destination address.

[0242] The termination of the transmission corresponding to the destination address can be understood as: the termination of the multicast transmission or broadcast transmission corresponding to the destination address. That is to say, the multicast or broadcast for this destination address terminates / no longer sends.

[0243] That the terminal does not need to send or receive SL data corresponding to the destination address may include: the terminal determines that it does not need to send or receive SL data corresponding to the destination address; the terminal is no longer interested in the transmission corresponding to the destination address.

[0244] It should be noted that being no longer interested can be understood as being interested before and not (any longer) interested currently, without limiting that it will never be interested in the future.

[0245] Specifically, the upper layer of the RRC layer of the terminal may request (or indicate or configure) to be no longer interested in the transmission corresponding to a destination address. The upper layer of the RRC layer of the terminal may request (or indicate or configure) the termination of the transmission corresponding to a destination address.

[0246] The method provided in the fourth embodiment can, when the terminal no longer sends or receives SL data for a destination address, determine the second SL process as unoccupied, so that these SL processes can be used for the transmission or reception of other data, avoid the reduction of the number of available SL processes, and improve the rate of data transmission or reception. The method provided in the fourth embodiment can, when the terminal no longer sends or receives SL data for a destination address, release the storage space by clearing the cache of the second SL process, and also enable these SL processes to be used for the transmission or reception of other data, avoid the reduction of the number of available SL processes, and improve the rate of data transmission or reception. The method provided in the fourth embodiment can, when the terminal no longer sends or receives SL data for a destination address, release the association relationship associated with the second SL process, thereby avoiding the receiving terminal wrongly clearing other data, or ensuring the reception of data associated with the first SL process, and improving the reliability of data reception.

[0247] Embodiment Five

[0248] Embodiment Five can solve the problems caused by the receiving terminal not executing one or more of releasing the association relationship between the SCI and the SL process, considering the SL process as unoccupied, and clearing the cache of the SL process when event 3 occurs, and can also solve the problems caused by the sending terminal not considering the SL process as unoccupied and / or not clearing the cache of the SL process when event 3 occurs. Refer to Figure 11 , the method includes:

[0249] 1101. For a destination address, the terminal determines to perform a MAC reset.

[0250] In various embodiments of the present application, performing a MAC reset for a destination address may include / replace / be understood as: performing a sidelink specific reset of the MAC entity for a destination address. For the related description of the destination address, refer to Embodiment 4 and details will not be repeated.

[0251] Step 1101 may also be described as: for a destination address, the terminal performs a MAC reset.

[0252] Among them, the destination address is used to identify a multicast or a broadcast.

[0253] Optionally, before step 1101, the method further includes: for the destination address, the terminal stops sending or receiving sidelink data. For the related description of "for the destination address, the terminal stops sending or receiving sidelink data", refer to Embodiment 4 and details will not be repeated.

[0254] 1102. The terminal performs one or more of the following actions: the terminal determines that the second sidelink process is unoccupied; the terminal releases the association relationship associated with the second sidelink process; the terminal clears the cache of the second sidelink process; where the second sidelink process is the sidelink process associated with the destination address.

[0255] Optionally, the association relationship associated with the second sidelink process includes: the association relationship between the second sidelink process and the SCI, and / or, the association relationship between the second sidelink process and one or more of the sidelink process ID, the first destination ID, the first source ID, and the communication type.

[0256] For the related description of step 1102, refer to step 902 above and details will not be repeated.

[0257] The method provided in the fifth embodiment can determine that the second SL process is unoccupied when the terminal performs MAC reset for a destination address, so that these SL processes can be used for sending or receiving other data, avoiding a reduction in the number of available SL processes and improving the data sending or receiving rate. The method provided in the fifth embodiment can, when the terminal performs MAC reset for a destination address, release the storage space by clearing the cache of the second SL process, and can also make these SL processes available for sending or receiving other data, avoiding a reduction in the number of available SL processes and improving the data sending or receiving rate. The method provided in the fifth embodiment can, when the terminal performs MAC reset for a destination address, release the association relationship associated with the second SL process, thereby avoiding the receiving terminal erroneously clearing other data and improving the reliability of data reception, or ensuring the reception of data associated with the first SL process and improving the reliability of data reception.

[0258] In addition to the above-mentioned Embodiments 1 to 5, there may also be the following Solutions 1 and 2.

[0259] Solution 1: The PC5-S transmission for a destination address is terminated at a layer above the RRC layer; or, a layer above the RRC layer requests (or indicates or configures) the termination of the PC5-S transmission for a 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 associated with the fourth SL process, and the terminal clears the cache of the fourth SL process. The fourth SL process refers to the SL process associated with the PC5-S of the destination address or the destination address.

[0260] Solution 2: The PC5-S transmission for a destination address terminates at the upper layer of the RRC layer; or, the upper layer of the RRC layer requests (or indicates or configures) the termination of the PC5-S transmission for a destination address. The terminal performs a MAC reset for the PC5-S of the destination address or 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 associated with the fourth SL process, and the terminal clears the cache of the fourth SL process. Currently, in the existing protocols of NR V2X, mode1 and mode2 cannot exist simultaneously, and retransmission cannot be performed between different resource configuration modes. That is, data newly transmitted using the resources of mode1 cannot be retransmitted using the resources of mode2, and data newly transmitted using the resources of mode2 cannot be retransmitted using the resources of mode1. In the case of a switch / change in the resource configuration mode (referred to as mode switch for short), on the sending terminal side, the mechanism for processing the SL process is not specified. After the mode switch, if the process occupied in the original resource configuration mode is still occupied, it may lead to a reduction in the number of available processes for the sending terminal. To solve this problem, this application also provides the methods for processing the SL process shown in Embodiment Six and Embodiment Seven, which are described separately below. The terminals in Embodiment Six and Embodiment Seven can both be sending terminals.

[0261] Embodiment Six

[0262] See Figure 12 , the method for processing the SL process provided by Embodiment Six includes:

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

[0264] Step 1201 can also be described as: The terminal determines that the resource configuration mode switches from the second resource configuration mode to the first resource configuration mode (that is, the resource configuration mode of the terminal before the switch is the second resource configuration mode), or, the terminal determines that the resource configuration mode switches from the first resource configuration mode and the second resource configuration mode to the first resource configuration mode (that is, the resource configuration mode of the terminal before the switch is the first resource configuration mode and the second resource configuration mode).

[0265] In this application, switch can be replaced by change.

[0266] Among them, the first resource configuration mode can be mode1 or mode2. The terminal determining that the resource configuration mode is the first resource configuration mode can include any one or more of the following: the MAC layer of the terminal determines that the resource configuration mode is the first resource configuration mode; the MAC layer / terminal of the terminal is configured with the resource configuration mode as the first resource configuration mode, the RRC layer of the terminal configures the resource configuration mode as the first resource configuration mode, and the RRC layer of the terminal configures the resource configuration mode for the MAC layer of the terminal as the first resource configuration mode. For example, specifically, when the MAC entity of the terminal is configured with the SL resource associated with mode1, the terminal determines that the resource configuration mode is mode1. When the RRC layer of the terminal configures the SL resource associated with mode2, the terminal determines that the resource configuration mode is mode2.

[0267] 1202. The terminal determines that the third SL process is unoccupied, and / or clears the cache of the third SL process.

[0268] Among them, the third SL process is the SL process associated with the second resource configuration mode. That is to say, the third SL process or the SL process associated with the second resource configuration mode can be understood as: the SL process that uses the resources corresponding to the second resource configuration mode to send data, and / or the SL process associated with the resources corresponding to the second resource configuration mode.

[0269] Among them, if the first resource configuration mode is mode1, then the second resource configuration mode is mode2. If the first resource configuration mode is mode2, then the second resource configuration mode is mode1.

[0270] For the method provided in the sixth embodiment, if the terminal determines that the resource configuration mode is the first resource configuration mode, by determining that the third SL process is unoccupied, these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes, and the data reception rate can be improved. By clearing the cache of the third SL process, the storage space can be released, and these SL processes can also be used for sending other data, avoiding a reduction in the number of available SL processes, and the data sending or reception rate can be improved.

[0271] Optionally, the resources corresponding to the first resource configuration mode include the configured SL authorization resources (i.e., SL CG resources) or the dynamic SL authorization resources (i.e., SL DG resources) (that is, the first resource configuration mode is mode1). Before step 1202, the method further includes: the terminal (such as the HARQ entity of the terminal) obtains the configured SL authorization resources or the dynamic SL authorization resources (that is, obtains the resources of mode1, and optionally, the resources can be new transmission resources), and / or determines that the number of unoccupied SL processes is less than or equal to the first threshold.

[0272] Optionally, the terminal obtaining the configured SL authorization resource or the dynamic SL authorization resource may include: the terminal obtains the configured SL authorization resource or the dynamic SL authorization resource, and obtains the data transmitted on the configured SL authorization resource or the dynamic SL authorization resource.

[0273] Among them, the first threshold may be configured / indicated / sent by the network device to the terminal, may be pre-configured, may be specified by the protocol, may be stored in the terminal by the device manufacturer before the terminal leaves the factory, or may be pre-configured in the terminal by the network device / other devices when the terminal connects to the network. For example, the first threshold may be 0, 2, 3, etc.

[0274] Exemplarily, the number of unoccupied SL processes is less than or equal to the first threshold, which can be understood as that all SL processes are occupied, or the number of unoccupied SL processes is less than or equal to the number of SL processes required by the terminal.

[0275] After step 1201, the terminal may directly execute step 1202, or may execute step 1202 when it obtains the configured SL authorization resource or the dynamic SL authorization resource, and / or the number of unoccupied SL processes is less than or equal to the first threshold.

[0276] It should be noted that in the case where the first resource configuration mode is mode1, the SL resources of the terminal are scheduled by the network device. After the terminal obtains the configured SL authorization resource or the dynamic SL authorization resource, it then selects the SL process. Therefore, the terminal may execute step 1202 when / after it obtains the configured SL authorization resource or the dynamic SL authorization resource.

[0277] Optionally, the resources corresponding to the first resource configuration mode include the selected SL resource (selection sidelink resource) (that is, the first resource configuration mode is mode2). Before step 1202, the method further includes: the terminal determines the selected SL resource (that is, the terminal needs to perform resource selection or needs to determine the resources), and / or the number of unoccupied SL processes is less than or equal to the first threshold.

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

[0279] It should be noted that in the case where the first resource configuration mode is mode2, the SL resources of the terminal are self-selected. The terminal determines the SL process and performs resource selection. Therefore, the terminal may execute step 1202 when / after it needs / to determine to perform resource selection.

[0280] Optionally, before step 1202, the method further includes: for the second resource configuration mode, the terminal determines to perform a MAC reset. That is, the mode switch triggers a MAC reset for the second resource configuration mode, and this MAC reset triggers the execution of step 1202.

[0281] In various embodiments of the present application, performing a MAC reset for the second resource configuration mode may include / replace / be understood as: performing a sidelink specific reset of the MAC entity for the second resource configuration mode.

[0282] Optionally, when specifically implemented, step 1202 may determine one or more of the third SL processes as unoccupied based on one or more of the following information, and / or clear the caches of one or more of the third SL processes.

[0283] Information 1: The priority of the data associated with the third SL process.

[0284] Information 2: The latency requirement of the data associated with the third SL process.

[0285] Information 3: The reliability requirement of the data associated with the third SL process.

[0286] For example, for Information 1, the terminal may determine the SL processes associated with one or more data with the lowest priority or lower than a priority threshold as unoccupied and / or clear the corresponding caches.

[0287] For example, for Information 2, the terminal may determine the SL processes associated with one or more data with the highest latency requirement or lower than a latency threshold as unoccupied and / or clear the corresponding caches.

[0288] For example, for Information 3, the terminal may determine the SL processes associated with one or more data with the lowest reliability requirement or lower than a reliability threshold as unoccupied and / or clear the corresponding caches.

[0289] In the terminal, the situation of frequent mode switching may occur. If the process is released immediately after the mode switch, serious packet loss may occur, and it may not meet the requirements for services with high priority, low latency requirements, and high reliability requirements. This optional method can avoid this situation. Additionally, the terminal may also determine the SL processes associated with one or more data as unoccupied and / or clear the corresponding caches after a period of time after the mode switch.

[0290] In Embodiment 6, the terminal may process SL processes one by one. For example, it may use one SL process to process one SL process, or it may process multiple SL processes multiple by multiple, or it may process all SL processes at once. This application does not make any restrictions. The processing here includes determining that the SL process is not occupied and / or clearing the corresponding cache.

[0291] Optionally, the method further includes: The terminal releases the SL resources corresponding to the second resource configuration mode and / or the configuration corresponding to the SL resources corresponding to the second resource configuration mode, so that these resources can be used by other terminals later, improving resource utilization.

[0292] Embodiment 7

[0293] See Figure 13 , the method for processing SL processes provided in Embodiment 7 includes:

[0294] 1301. For the second resource configuration mode, the terminal determines to perform a MAC reset.

[0295] In specific implementation of step 1301, the terminal may execute step 1301 when switching from the second resource configuration mode to other resource configuration modes. For example, the terminal may execute step 1301 when the resource configuration mode switches from the second resource configuration mode to the first resource configuration mode, or the terminal may also execute step 1301 when the resource configuration mode switches from the first resource configuration mode and the second resource configuration mode to the first resource configuration mode. The terminal may also execute step 1301 under the trigger of other trigger conditions.

[0296] Among them, the second resource configuration mode may be mode1 or mode2.

[0297] Optionally, before step 1301, the method further includes: The terminal determines that the resource configuration mode is the first resource configuration mode. The relevant description of this step can be seen in step 1201 above and will not be elaborated here.

[0298] 1302. The terminal determines that the third SL process is not occupied and / or clears the cache of the third SL process.

[0299] Optionally, in specific implementation of step 1302, one or more of the following information may be used to determine that one or more of the third SL processes are not occupied and / or clear the cache of one or more of the third SL processes.

[0300] Information 1: The priority of the data associated with the third SL process.

[0301] Information 2: The latency requirement of the data associated with the third SL process.

[0302] Information 3, reliability requirements for data associated with the third SL process.

[0303] For the relevant description of this optional method, refer to Embodiment Six above, and details will not be repeated here.

[0304] Optionally, the method further includes: the terminal releases the SL resources corresponding to the second resource configuration mode and / or the configuration corresponding to the SL resources corresponding to the second resource configuration mode, so that these resources can be used by other terminals subsequently, improving resource utilization.

[0305] For the method provided in Embodiment Seven, if, for the second resource configuration mode, the terminal determines to perform MAC reset, by determining that the third SL process is unoccupied, these SL processes can be used for sending other data, avoiding a reduction in the number of available SL processes, and improving the data reception rate. By clearing the cache of the third SL process, storage space can be released, and these SL processes can also be used for sending other data, avoiding a reduction in the number of available SL processes, and improving the data sending or reception rate.

[0306] In addition, in the mode switching scenario, the present application also provides Embodiment Eight to improve resource utilization.

[0307] Embodiment Eight

[0308] Refer to Figure 14 , the method for releasing SL resources provided in Embodiment Eight includes:

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

[0310] 1402. The terminal releases the SL resources corresponding to the second resource configuration mode and / or the configuration corresponding to the SL resources corresponding to the second resource configuration mode.

[0311] For the relevant description of Embodiment Eight, refer to the relevant description in Embodiment Six above, and details will not be repeated here. By releasing the SL resources associated with the second resource configuration mode and / or the configuration corresponding to the SL resources associated with the second resource configuration mode, these resources can be used by other terminals subsequently, improving resource utilization.

[0312] The methods shown in Embodiments Six to Eight are also applicable to the LTE system. Only need to understand by replacing mode1 with mode3 and mode2 with mode4.

[0313] In the above embodiments of the present application, regardless of which parameter (for example, destination address, second resource configuration mode, RRC connection of SL) is used for MAC reset, it is not limited whether the MAC reset has been performed for this parameter. For example, it can be understood that the terminal will / is preparing to perform MAC reset for this parameter.

[0314] In the above embodiments of the present application, the buffer of the SL process of the transmitting terminal can be referred to as the HARQ buffer, and the buffer of the SL process of the receiving terminal can be referred to as the soft buffer. In the present application, the SL process being regarded as unoccupied can also be described as releasing the SL process or deactivating the SL process, and the unoccupied SL process can also be described as the deactivated SL process. Similarly, the SL process being regarded as occupied can also be described as activating the SL process, and the occupied SL process can also be described as the activated SL process.

[0315] The methods provided in the above embodiments can be combined when the solutions do not conflict. The methods provided in the above embodiments can be executed not only by the terminal but also by other devices.

[0316] The above mainly introduces the solutions of the embodiments of the present application from the perspective of the method. It can be understood that in order for the terminal to implement the above functions, it includes at least one of the corresponding hardware structures and software modules for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0317] The embodiments of the present application can divide the functions of the terminal according to the above method examples. For example, each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0318] Exemplarily, Figure 15FIG. 0 shows a possible schematic structural diagram of the device (denoted as device 150) involved in the above embodiments. The device 150 includes a processing unit 1501 and a communication unit 1502. Optionally, it further includes a storage unit 1503. The device 150 can be used to illustrate the structure of the terminal in the above embodiments. In this case, the processing unit 1501 is used to control and manage the actions of the terminal. For example, the processing unit 1501 is used to execute Figure 5 , Figure 7 , Figure 8 , Figure 9 , Figure 11 , Figure 12 , Figure 13 and Figure 14 in each step, and / or the actions performed by the terminal in other processes described in the embodiments of the present application. The processing unit 1501 can communicate with other network entities through the communication unit 1502. For example, it can transmit SL data, SCI, etc. to another terminal. The storage unit 1503 is used to store the program code and data of the terminal.

[0319] Exemplarily, the device 150 can be a device, a chip, or a chip system.

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

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

[0322] Figure 15If the integrated unit in [the above] is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of this application. The storage media storing the computer software product include: various media such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs that can store program codes.

[0323] The embodiments of this application also provide a schematic diagram of the hardware structure of a device. Refer to Figure 16 or Figure 17 , this device includes a processor 1601. Optionally, it further includes a memory 1602 connected to the processor 1601.

[0324] The processor 1601 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the programs of the solution of this application. The processor 1601 can also include multiple CPUs, and the processor 1601 can be a single-CPU processor or a multi-CPU processor. Here, the processor can refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0325] The memory 1602 can be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium, or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer. The embodiments of the present application do not impose any restrictions on this. The memory 1602 can exist independently (in this case, the memory 1602 can be located outside the device or inside the device), or it can be integrated with the processor 1601. Among them, the memory 1602 can contain computer program code. The processor 1601 is used to execute the computer program code stored in the memory 1602, so as to implement the method provided by the embodiments of the present application.

[0326] In the first possible implementation, refer to Figure 16 , the device further includes a transceiver 1603. The processor 1601, the memory 1602, and the transceiver 1603 are connected through a bus. The transceiver 1603 is used to communicate with other devices or communication networks. Optionally, the transceiver 1603 can include a transmitter and a receiver. The device in the transceiver 1603 for implementing the receiving function can be regarded as a receiver, and the receiver is used to execute the receiving steps in the embodiments of the present application. The device in the transceiver 1603 for implementing the sending function can be regarded as a transmitter, and the transmitter is used to execute the sending steps in the embodiments of the present application.

[0327] Based on the first possible implementation, Figure 16 The structural schematic diagram shown can be used to illustrate the structure of the terminal involved in the above embodiments. In this case, the processor 1601 is used to control and manage the actions of the terminal. For example, the processor 1601 is used to execute Figure 5 , Figure 7 , Figure 8 , Figure 9 , Figure 11 , Figure 12 , Figure 13 and Figure 14Each step in, and / or actions performed by a terminal in other processes described in embodiments of the present application. The processor 1601 can communicate with other network entities through the transceiver 1603. For example, SL data or SCI can be transmitted between the processor 1601 and another terminal. The memory 1602 is used to store program codes and data of the terminal.

[0328] In a second possible implementation, the processor 1601 includes logic circuits and an input interface and / or an output interface. Exemplarily, the output interface is used to perform the sending actions in the corresponding method, and the input interface is used to perform the receiving actions in the corresponding method. Based on the second possible implementation, refer to Figure 17 , Figure 17 The schematic structural diagram shown can be used to illustrate the terminal involved in the above embodiments. In this case, the processor 1601 is used to control and manage the actions of the terminal. For example, the processor 1601 is used to execute Figure 5 , Figure 7 , Figure 8 , Figure 9 , Figure 11 , Figure 12 , Figure 13 and Figure 14 Each step in, and / or actions performed by a terminal in other processes described in embodiments of the present application. The processor 1601 can communicate with other network entities through the input interface and / or the output interface. For example, SL data or SCI can be transmitted between the processor 1601 and another terminal. The memory 1602 is used to store program codes and data of the terminal.

[0329] In the implementation process, each step in the method provided in this embodiment can be completed by the integrated logic circuit in the hardware of the processor or by instructions in software form. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or executed and completed by a combination of the hardware and software modules in the processor.

[0330] Embodiments of the present application also provide a computer-readable storage medium, including computer-executable instructions, which when running on a computer, cause the computer to execute any of the above methods.

[0331] Embodiments of the present application also provide a computer program product, including computer-executable instructions, which when running on a computer, cause the computer to execute any of the above methods.

[0332] Embodiments of the present application also provide a communication system, including: the above terminal.

[0333] The embodiment of the present application also provides a device, including: a processor and an interface. The processor is coupled to a memory through the interface. When the processor executes a computer program or computer-executable instructions in the memory, any one of the methods provided in the above embodiments is executed.

[0334] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" in this application is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In the description of the present application, unless otherwise specified, "at least one" means one or more, and "a plurality" means two or more than two.

[0335] In addition, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and effects. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily mean different.

[0336] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can 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 processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that contains one or more media integrated. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0337] Although the present application has been described in connection with various embodiments, those skilled in the art will understand and realize other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims during the implementation of the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0338] Although the present application has been described in connection with specific features and their embodiments, it is obvious that various modifications and combinations can be made without departing from the scope of protection of the present application. Accordingly, the present specification and the drawings are merely exemplary illustrations of the present application defined by the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of protection of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A method for processing sidelink processes, characterized in that, including: The terminal determines to perform Media Access Control (MAC) reset on the Radio Resource Control (RRC) connection of the sidelink on the opposite side; The terminal determines that the first sidelink process is unoccupied; wherein, the first sidelink process is a sidelink process associated with the RRC connection.

2. The method according to claim 1, wherein: The terminal determines to perform MAC reset on the RRC connection of the sidelink on the opposite side, including: the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection; The terminal determines that the first sidelink process is unoccupied, including: the MAC entity of the terminal determines that the first sidelink process is unoccupied.

3. The method according to claim 2, wherein Before the upper layer of the MAC layer of the terminal requests to perform MAC reset on the RRC connection, the method further includes: The upper layer of the RRC layer of the terminal requests to release the RRC connection.

4. An apparatus for processing sidelink processes, characterized in that, including: A processing unit, configured to: Determine to perform MAC reset on the RRC connection of the sidelink on the opposite side; Determine that the first sidelink process is unoccupied; wherein, the first sidelink process is a sidelink process associated with the RRC connection.

5. The device according to claim 4, characterized in that The processing unit is specifically configured to: Request to perform MAC reset on the RRC connection at the upper layer of the MAC layer; Determine that the first sidelink process is unoccupied at the MAC entity.

6. The device according to claim 5, characterized in that, The processing unit is further configured to: Request to release the RRC connection at the upper layer of the RRC layer.

7. An apparatus for processing a sidelink process, characterized in that, including: A processor; The processor is connected to a memory, and the memory is used to store computer execution instructions. The processor executes the computer execution instructions stored in the memory so that the device implements the method according to any one of claims 1-3.

8. A computer-readable storage medium, characterized in that, including computer execution instructions, when the computer execution instructions run on a computer, enabling the computer to execute the method according to any one of claims 1-3.

9. A computer program product, characterized in that, including computer execution instructions, when the computer execution instructions run on a computer, enabling the computer to execute the method according to any one of claims 1-3.

Images