WO2020156052A1 - 链路释放信息传输方法、装置及设备 - Google Patents

链路释放信息传输方法、装置及设备 Download PDF

Info

Publication number
WO2020156052A1
WO2020156052A1 PCT/CN2020/070644 CN2020070644W WO2020156052A1 WO 2020156052 A1 WO2020156052 A1 WO 2020156052A1 CN 2020070644 W CN2020070644 W CN 2020070644W WO 2020156052 A1 WO2020156052 A1 WO 2020156052A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
information
link
link release
release information
Prior art date
Application number
PCT/CN2020/070644
Other languages
English (en)
French (fr)
Inventor
王达
赵亚利
Original Assignee
电信科学技术研究院有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院有限公司 filed Critical 电信科学技术研究院有限公司
Publication of WO2020156052A1 publication Critical patent/WO2020156052A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present disclosure relates to the field of communication technology, in particular to a method, device and equipment for link release information transmission.
  • the service of the direct communication interface only supports the broadcast service.
  • the service of the direct communication interface will be more abundant than that of LTE, except for the broadcast service.
  • it also supports unicast and multicast services.
  • Mode3 and Mode4 are supported.
  • Mode3 is the resource allocation mode for network scheduling
  • Mode4 is the resource allocation mode independently selected by the terminal
  • NR subdivides the resource allocation mode independently selected by the terminal (Mode2 in NR).
  • One of the subdivision modes is Mode2d, that is, one user terminal UE (scheduling UE) schedules the communication resources of other UEs (the terminal schedules the resource allocation mode of other terminals).
  • an association relationship needs to be established between the sending and receiving UEs
  • Mode2d mode an association relationship needs to be established between the scheduling UE and other scheduled UEs.
  • the purpose of the present disclosure is to provide a link release information transmission method, device, and equipment, which can realize the timely release of links between terminals and avoid waste of channel resources.
  • the embodiments of the present disclosure provide a link release information transmission method, which is applied to a first terminal, and includes:
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the link release information after receiving the link release information, it also includes:
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the first terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the second terminal;
  • the first terminal When the first terminal is a scheduled terminal in the first resource allocation mode, stop receiving link resources allocated by the second terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • the method further includes:
  • the scheduling terminal When the first terminal is a scheduled terminal in the first resource allocation mode, the scheduling terminal is searched, and after stopping receiving the link resource allocated by the second terminal, the link resource is obtained through the searched scheduling terminal.
  • the method further includes:
  • the link resource is obtained through a resource allocation mode other than the first resource allocation mode.
  • the link release information after receiving the link release information, it also includes:
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the method before sending the link release confirmation message, the method further includes:
  • the embodiments of the present disclosure provide a method for transmitting link release information, which is applied to a second terminal, and includes:
  • Send link release information where the link release information is used to release the link between the first terminal and the second terminal, where the first terminal is a receiving terminal of the link release information.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the link release information after sending the link release information, it also includes:
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the second terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the first terminal;
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, stop receiving the link resource allocated by the first terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • the method further includes:
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, search for the scheduled terminal, and after stopping receiving the link resource allocated by the first terminal, obtain the link resource through the searched scheduling terminal.
  • the method further includes:
  • the link resource is acquired through a resource allocation mode other than the first resource allocation mode.
  • the link release information after sending the link release information, it also includes:
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the terminal device is a first terminal and includes a transceiver, a memory, a processor, and a device that is stored on the memory and can run on the processor.
  • Computer program ;
  • the processor is configured to receive link release information, where the link release information is used to instruct to release the link between the first terminal and the second terminal, and the second terminal is the source of the link release information. Sending terminal.
  • the terminal device is a second terminal and includes a transceiver, a memory, a processor, and a device that is stored on the memory and can run on the processor.
  • Computer program ;
  • the processor is configured to send link release information, the link release information is used to release the link between the first terminal and the second terminal, and the first terminal is the reception of the link release information terminal.
  • the embodiments of the present disclosure provide a link release information transmission device, which is applied to a first terminal, and includes:
  • the receiving module is configured to receive link release information, where the link release information is used to instruct to release the link between the first terminal and the second terminal, and the second terminal is the source of the link release information Sending terminal.
  • the embodiments of the present disclosure provide a link release information transmission device, which is applied to a second terminal, and includes:
  • the sending module is configured to send link release information, where the link release information is used to release the link between the first terminal and the second terminal, where the first terminal is the receiving of the link release information terminal.
  • the embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored, and the program is executed by a processor to implement the link release information transmission method applied to the first terminal, or The steps in the link release information transmission method applied to the second terminal above are implemented.
  • the link release information transmission method of the embodiment of the present disclosure can receive link release information, and the link release information is used to indicate the release of the first terminal (that is, the receiving terminal of the link release information) and the second terminal (that is, the link Releasing the link between the sending terminal of the information can realize that the first terminal releases the link with the second terminal in time based on the link release information, thereby avoiding the waste of channel resources.
  • Figure 1 is a schematic diagram of V2X communication
  • FIG. 2 is a schematic flowchart of a link release information transmission method applied to a first terminal according to an embodiment of the disclosure
  • Figure 3 is a schematic diagram of the application of scenario one
  • Figure 4 is a schematic diagram of the application of scenario two;
  • Figure 5 is a schematic diagram of the application of scenario three;
  • Figure 6 is a schematic diagram of the application of scenario four;
  • FIG. 7 is a schematic flowchart of a link release information transmission method applied to a second terminal according to an embodiment of the disclosure.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the disclosure.
  • FIG. 1 it is a schematic diagram of V2X (Vehicle to Everything) communication in related technologies.
  • Direct communication between devices is allowed between devices, such as UE1 and UE2.
  • the side-line communication link between the device and the device is defined as a Sidelink (side-line) link, and its corresponding wireless interface is called a direct communication interface (also called a Sidelink interface); the network (base station eNodeB) and direct
  • Uu link the corresponding interface
  • Uu interface Uu interface
  • Typical direct communication scenarios include the following three types: one-to-one communication (unicast) between direct communication terminals; one device can send the same data to all devices in a communication group at a time (multicast); one device can send the same data to all devices in a communication group at a time (multicast); All nearby devices send the same data (broadcast).
  • a method for transmitting link release information according to an embodiment of the present disclosure, applied to a first terminal includes:
  • Step 201 Receive link release information, where the link release information is used to instruct the release of the link between the first terminal and the second terminal, where the second terminal is the sending terminal of the link release information .
  • the first terminal can receive link release information, and the link release information is used to indicate the release of the link between the first terminal and the second terminal (that is, the terminal that sends the link release information). It is realized that the first terminal releases the link with the second terminal in time based on the link release information, thereby avoiding channel resource waste.
  • the embodiments of the present disclosure are mainly aimed at the unicast and multicast scenarios in the NR V2X system, and the first resource allocation mode (Mode2d mode, the resource allocation mode of the terminal scheduling terminal (other terminals)) scenario.
  • the first terminal can be the sending terminal of the unicast service
  • the second terminal can be the receiving terminal of the unicast service
  • the first terminal can be the receiving terminal of the unicast service
  • the second terminal can be the unicast service.
  • the sending terminal of the service for the multicast scenario, the first terminal can be the sending terminal of the multicast service, and the second terminal can be the receiving terminal of the multicast service, or the first terminal is the receiving terminal of the multicast service, and the second terminal It is the sending terminal of the multicast service; for the Mode2d scenario, the first terminal may be a scheduling terminal, and the second terminal is a scheduled terminal, or the first terminal is a scheduled terminal, and the second terminal is a scheduling terminal.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the link release information includes the first information
  • the purpose of notifying the first terminal that the received information is link release information will be realized.
  • the first information not only exists explicitly in the link release information, but can also exist in other implicit ways, such as a scrambling code as the link release information, or, in addition to carrying the first information, the link release information also This goal can be achieved by itself, for example, by occupying configured or pre-configured specific resources to send link release information.
  • the link release information may not include the first information.
  • the link release information includes the second information
  • the purpose of informing the first terminal to feed back link confirmation information after receiving the link release information will be realized.
  • the feedback link confirmation information may also be network configuration, or pre-configuration, or implemented by means of group manager configuration in a group. In this case, the link release information may not include the second information.
  • the link release information includes the third information
  • the first terminal will be notified to feed back the resources occupied by the link confirmation information.
  • the resources occupied by the feedback link confirmation information may also be implemented by means of network configuration or pre-configuration.
  • the third information may not be included in the link release information.
  • the first terminal will confirm the target terminal of the link release, that is, the first terminal is determined by the terminal identifier included in the link release information to determine whether the first terminal is link release information
  • the target receiver, and/or the sender that determines the link release information can also exist in other implicit ways, such as a scrambling code as the link release information.
  • the link release information may not include the first identifier. One logo.
  • the first terminal in the multicast scenario will confirm the target terminal group for the link release.
  • the first terminal is a service data receiving terminal in a multicast scenario.
  • the connection with the service data sending terminal in the group corresponding to the first group identifier may be released based on the first group identifier.
  • the first group of identifiers can also exist in other implicit ways, for example, as a scrambling code for the link release information. In this case, the link release information may not include the link release information.
  • the first set of logos are examples of the link release information.
  • the link release information can be sent using radio resource control RRC (Radio Resource Control) signaling, or using side link control information SCI (Sidelink Control Information), or using side link feedback control information SFCI (Sidelink Feedback Control Information) is sent.
  • RRC Radio Resource Control
  • SCI Seglink Control Information
  • SFCI Sidelink Feedback Control Information
  • RRC signaling is used to send link release information, where the RRC signaling includes at least one of the following:
  • Terminal ID or group ID that is, the first identification or the first group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID; for Mode The 2d scenario includes the dispatching terminal ID and/or the dispatched terminal ID. If the RRC signaling is scrambled using the terminal ID or group ID, there is no need to include the terminal ID or group ID in the RRC signaling.
  • the resource used for sending the link release confirmation signal (that is, the third information), such as indicating the SFCI resource or SCI resource used for sending the link release confirmation signal. If the resource used for sending the link release confirmation signal is indicated in the SCI that sends the RRC signaling, there is no need to include the resource occupied by the link release confirmation signal in the RRC signaling.
  • the side link control information SCI is used to send link release information, where the SCI includes at least one of the following:
  • Terminal ID identification
  • group ID ie, first identification or first group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID Item:
  • the terminal ID includes the dispatching terminal ID and/or the dispatched terminal ID. If the SCI is scrambled using the terminal ID or group ID, there is no need to include the terminal ID or group ID in the SCI.
  • the resource used for sending the link release confirmation information (that is, the third information), such as indicating the SFCI resource or SCI resource used for sending the link release confirmation information. If the resources used for sending the link release confirmation signal are configured through network configuration or pre-configuration, it is not necessary to include the resources occupied by the link release confirmation signal in the SCI.
  • the side link feedback control information SFCI is used to send link release information, where the SFCI may be:
  • Method 1 Use a sequence to indicate that the SFCI is link release information, the sequence and the Hybrid Automatic Repeat Request (Hybrid Automatic Repeat Request) sequence transmitted on the SFCI, and/or the side link service request SR transmitted on the SFCI
  • the (Service request) sequence is orthogonal, and the sequence can be configured on the network side, or specified by the standard, or pre-configured. Further, the sequence is related to the terminal ID that sends the link release information, or the terminal ID that receives the link release information, or the terminal group ID.
  • the generating factor that generates the sequence includes the terminal ID or the terminal group ID , Used to solve the conflict problem caused by the transmission signal of other terminals on the resource, so that the receiving end determines the link release target terminal or target terminal group.
  • Method 2 Including at least one of the following:
  • Terminal ID or group ID ie, first identification or first group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID
  • the terminal ID includes the dispatching terminal ID and/or the dispatched terminal ID. If the SFCI is scrambled using the terminal ID or the group ID, there is no need to include the terminal ID and the group ID in the SFCI. Or, if the terminal has agreed on the resource of the sending link release information SFCI, the terminal ID or group ID is not needed, or only the ID or group ID of one of the terminals can be transmitted to solve the problem that other terminals are on the resource.
  • the conflict problem caused by the transmission signal makes the receiving end determine the link release target terminal or target terminal group.
  • the resource used for sending the link release confirmation signal (that is, the third information), for example, indicate the SFCI resource or SCI resource used for sending the link release confirmation information. If the resources used for sending the link release confirmation signal are configured through network configuration or pre-configuration, there is no need to include the resources occupied by the link release confirmation signal in the SFCI.
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the first terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the second terminal;
  • the first terminal When the first terminal is a scheduled terminal in the first resource allocation mode, stop receiving link resources allocated by the second terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal, that is, a Mode2d resource allocation mode scenario.
  • the method further includes:
  • the scheduling terminal When the first terminal is a scheduled terminal in the first resource allocation mode, the scheduling terminal is searched, and after stopping receiving the link resource allocated by the second terminal, the link resource is obtained through the searched scheduling terminal.
  • the scheduled terminal after the link is released, if the scheduled terminal still has business data to send, it will search for the scheduling terminal before stopping receiving the link resource allocated by the second terminal, so as to stop receiving the link allocated by the second terminal. After the resource, the link resource is obtained through the searched scheduling terminal.
  • the search scheduling terminal may also search for the second terminal. Therefore, optionally, after stopping receiving the link resources allocated by the second terminal, pass the searched other scheduling terminals (that is, the scheduling terminals other than the second terminal) Obtain link resources.
  • the step of searching for dispatching terminals can be before or after the step of receiving link release information, and if the dispatched terminal has no service to send, the dispatched terminal does not need to search for other available dispatching terminals or the searched terminal
  • the scheduling terminal obtains the link resource until the scheduled terminal has a service that needs to be sent and then searches or obtains the link resource through the searched scheduling terminal.
  • the scheduled terminal may not be able to search for other scheduled terminals. Therefore, the method further includes:
  • the link resource is obtained through a resource allocation mode other than the first resource allocation mode.
  • the resource allocation mode may also be a network-scheduled resource allocation mode Mode1, a terminal-selected resource allocation mode Mode2a, or a terminal resource allocation mode authorized based on network configuration Mode2c.
  • the network configuration information or pre-configuration information or link release information configures whether the first terminal sends/feeds back link release confirmation information after receiving the link release information. Therefore, after receiving the link release information, it also includes:
  • the first terminal after receiving the link release information, the first terminal sends a link release confirmation message to inform the second terminal that the first terminal successfully receives the link release information.
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the link release confirmation information includes the fourth information
  • the purpose of notifying the second terminal that the received information is the link release confirmation information will be realized.
  • the link release confirmation information can also achieve the purpose by itself, for example, occupying configured or pre-configured specific resources to send link release confirmation information.
  • the link release confirmation information may not include the fourth information.
  • the second terminal will confirm the target terminal of the link release, that is, the second terminal judges whether the second terminal is a link based on the terminal identifier included in the link release confirmation information
  • the target receiver of the release confirmation message, and/or the sender of the link release confirmation message is determined.
  • the link release confirmation information can also be omitted. Including the second identification.
  • the second terminal in the multicast scenario will confirm the link release target terminal group.
  • the second terminal is a service data sending terminal in a multicast scenario.
  • it can learn that the service data receiving terminal in the group corresponding to the second group identifier has received the service data based on the second group identifier.
  • the second group of identifiers can also exist in other implicit ways, such as as a scrambling code for the link release confirmation message.
  • the link release confirmation message can also be included Does not include the second set of identifiers.
  • the link release confirmation information can be sent using RRC signaling, or using SCI, or using SFCI.
  • RRC signaling is used to send link release confirmation information, where the RRC signaling includes at least one of the following:
  • Terminal ID or group ID ie, second identification or second group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID; for Mode The 2d scenario includes the dispatching terminal ID and/or the dispatched terminal ID. If the RRC signaling is scrambled using the terminal ID or group ID, there is no need to include the terminal ID or group ID in the RRC signaling.
  • the SCI is used to send the link release confirmation message, where the SCI includes at least one of the following:
  • Terminal ID or group ID ie, second identification or second group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID
  • the terminal ID includes the dispatching terminal ID and/or the dispatched terminal ID. If the SCI is scrambled using the terminal ID or group ID, there is no need to include the terminal ID or group ID in the SCI.
  • SFCI is used to send link release confirmation information, where the SFCI may be:
  • Method 1 If the link release information indicates the resource location of the link release confirmation information, for example, the SCI of the link release information indicates the SFCI resource location of the link release confirmation information, then the HARQ feedback with unicast and multicast services
  • the sending method is similar.
  • the link release confirmation message is sent by occupying the indicated SFCI resource position.
  • the link release confirmation message can be sequence or bit information, which is used to indicate the reception of link release information, such as ACK (confirm that the reception is correct) or NACK (Acknowledge reception error, need to retransmit link release information).
  • Method 2 Use a sequence to indicate that the SFCI is a link release confirmation message.
  • This sequence is orthogonal to the HARQ sequence transmitted on the SFCI, and/or the SR sequence transmitted on the SFCI is orthogonal, and the sequence can be configured on the network side, or Standard requirements, or pre-configured. Further, the sequence is related to the terminal ID that sent the link release confirmation information, or the terminal ID that received the link release information, or the terminal group ID, and is used to solve the conflict problem caused by the transmission signal of other terminals on the resource , So that the receiving end determines the link release target terminal or target terminal group.
  • Method 3 Including at least one of the following:
  • Terminal ID or group ID ie, second identification or second group identification
  • the terminal ID includes at least one of the receiving terminal ID, the sending terminal ID, and the group ID
  • the terminal ID includes the dispatching terminal ID and/or the dispatched terminal ID. If the SFCI is scrambled using the terminal ID or the group ID, there is no need to include the terminal ID and the group ID in the SFCI.
  • the terminal ID or group ID is not required, or only the ID or group ID of one of the terminals can be transmitted to solve the problem that other terminals are in the resource
  • the conflict problem caused by the transmission signal on the network causes the receiving end to determine the link release target terminal or target terminal group.
  • the method further includes:
  • the link release confirmation information can be sent after the link release confirmation information is confirmed based on the configuration, the network configuration information or the pre-configuration information, or the link release information.
  • Scenario 1 Unicast scenario, as shown in Figure 3:
  • Terminal B sends link release information to terminal A; wherein, terminal B can obtain link resources in mode1 or mode2, which is the resource allocation mode selected by the terminal, and send link release information to terminal A, or can forward the link through the base station The method of releasing information sends link release information to terminal A.
  • Sending link release information can be achieved through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the SFCI resource agreed between the transmitting and receiving terminals.
  • send SCI and SFCI where SCI is used to indicate the resource location of SFCI, and SFCI is used to carry link release information.
  • terminal A After terminal A receives the link release information sent by terminal B, it is based on the network configuration information or pre-configuration information or link release information to indicate whether to send link release confirmation information.
  • Terminal B sends link release confirmation information; among them, terminal A can use mode1 or mode2 to obtain link resources and send link release confirmation information to terminal B, or it can transmit link release confirmation information to terminal B through the base station.
  • Send link release confirmation message If the network configuration information or preconfiguration information or link release information indicates the resource for sending the link release confirmation information, the link release confirmation information is sent through the resource indicated by the network configuration information or the preconfiguration information or the link release information. Specifically, through network configuration, broadcast signaling configuration is used. In addition to the link release information, other information can also complete the configuration of whether the link release confirmation signal is sent between the terminals.
  • terminal B needs to receive the link release confirmation information (such as ACK) sent by terminal A before it can release the connection with terminal A.
  • the link connection, association relationship and/or link resources of the link If the link release confirmation information sent by the terminal A is not received, for example, the sent link release confirmation information is not received or the received link release confirmation information is NACK, the link release information needs to be retransmitted.
  • the link release information is retransmitted N times, and the link release confirmation message is still not received or the link release confirmation message received is NACK, then the link connection, association relationship and/or link resources with terminal A are released, At this time, it means that the link condition between terminal B and terminal A is far or poor, where N is an integer greater than or equal to 1, which can be configured through network configuration or pre-configuration or standard regulations.
  • terminal B after terminal B sends the link release information, it waits for a period of timer T. If the link release confirmation message is not received within timer T, that is, the timer T times out, the link with terminal A is released Link connection, association relationship and/or link resources, etc.
  • the link release information can be retransmitted, and the timer T is reset every time the link release information is retransmitted
  • the timer T can be configured through the network or pre-configured or specified by the standard.
  • Sending the link release confirmation message can be implemented through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the agreed SFCI resource between the transceiver terminal; or SCI and SFCI are sent, where SCI is used to indicate the SFCI Resource location, SFCI is used to carry link release confirmation information.
  • Terminal A releases the link connection, association relationship and/or link resource, etc. with terminal B; for example, releases the stored terminal B ID, or side link RRC configuration related to terminal B, or signaling Radio bearer SRB (Signalling Radio Bearer), or data radio bearer DRB (Data Radio Bearer) and other information, and/or release semi-persistent scheduling SPS (Semi-Persistent Scheduling) resources reserved for unicast services with terminal B (used by Resources for sending or receiving SPS services), SPS process, HARQ process, etc., and/or clearing the buffer buffer for unicast service with terminal B, etc.
  • SPS Semi-Persistent Scheduling
  • terminal B After terminal B sends the link release information, or after terminal B receives the link release confirmation information sent by terminal A, terminal B releases the link connection, association relationship, and/or link resources with terminal A; for example, , Release the stored terminal A ID, or the RRC configuration related to terminal A, or SRB, or DRB and other information, and/or release the SPS resources reserved for unicast services with terminal A (used to send or receive SPS services) Resource), SPS process, HARQ process, etc., and/or clear the buffer for unicast service with terminal A.
  • Scenario 2 Multicast scenario (Sending terminal sends multicast signals to multiple receiving terminals)
  • the process is the same as the above scenario-unicast process, and it is not here anymore. Repeat. Only when the link is released, it is necessary to release the stored counterpart terminal ID, or the RRC configuration related to the multicast service, or information such as SRB, or DRB, and/or release the SPS resources reserved for the multicast service (for sending Or receive the resources of SPS service), SPS process, HARQ process, etc., and/or clear the buffer related to the multicast service.
  • the receiving terminal of the link release information is the receiving terminal of the multicast service
  • the sending terminal of the link release information is the sending terminal of the multicast service
  • Terminal B sends link release information to terminal A 1 and terminal A 2.
  • the link release information is a multicast signal, where terminal B can use mode 1 or mode 2 to obtain link resources and send it to terminal A 1 and
  • the terminal A 2 sends the link release information, or the link release information may be sent to the terminal A 1 and the terminal A 2 through the base station forwarding the link release information.
  • Sending link release information can be achieved through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the SFCI resource agreed between the transmitting and receiving terminals.
  • send SCI and SFCI where SCI is used to indicate the resource location of SFCI, and SFCI is used to carry link release information.
  • the group ID is included in the link release information.
  • terminal A 1/terminal A 2 After terminal A 1/terminal A 2 receives the link release information sent by terminal B, it is based on the network configuration information or pre-configuration information or link release information to indicate whether to send link release confirmation information, if it is confirmed to send link release Confirm the information, send link release confirmation information to terminal B; among them, terminal A1/terminal A2 can use mode1 or mode2 to obtain link resources, and send link release confirmation information to terminal B, or it can be forwarded by the base station Link release confirmation message is sent to terminal B by means of link release confirmation message. If the network configuration information or preconfiguration information or link release information indicates the resource for sending the link release confirmation information, the link release confirmation information is sent through the resource indicated by the network configuration information or the preconfiguration information or the link release information. Specifically, through network configuration, broadcast signaling configuration is used. In addition to the link release information, other information can also complete the configuration of whether the link release confirmation signal is sent between the terminals.
  • terminal B needs to receive the link sent by terminal A1/terminal A2 (all receiving terminals of link release information) Only by releasing the confirmation information (such as ACK) can the link connection, association relationship and/or link resources of the multicast service with the terminal A1/terminal 2 be released. If there is at least one receiving terminal for link release information, the link release confirmation message sent by the terminal is not received by the terminal or the received link release confirmation message is NACK, the link release information needs to be retransmitted.
  • confirmation information such as ACK
  • the link release information is retransmitted N times, there is still no link release confirmation message received or the received link release confirmation message is NACK, then the multicast service chain between terminal A 1 and terminal A 2 is released Link connection, association relationship and/or link resources, etc., at this time, it means that the link condition of the multicast service between terminal B and terminal A1/terminal A2 is far or poor, where N is an integer greater than or equal to 1, It can be configured through the network or pre-configured or specified by standards. In another implementation method, after terminal B sends the link release information, it waits for a period of timer T.
  • the link release confirmation message is not received within timer T, that is, the timer T times out, it will release and terminal A 1/
  • the link connection, association relationship and/or link resources of the multicast service between terminal A 2 (or when the link release confirmation message is received as NACK, the link release information can be retransmitted, and the link release information can be retransmitted each time the chain is retransmitted.
  • Channel release information, reset timer T) where timer T can be configured through the network or pre-configured or specified by standards.
  • Sending the link release confirmation message can be implemented through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the agreed SFCI resource between the transceiver terminal; or SCI and SFCI are sent, where SCI is used to indicate the SFCI Resource location, SFCI is used to carry link release confirmation information.
  • Terminal A 1/Terminal A 2 releases the link connection, association relationship and/or link resource with terminal B; for example, releases the stored terminal B ID or the side link RRC related to terminal B Configure, or SRB, or DRB information, and/or release SPS resources (resources for sending or receiving SPS services) reserved for multicast services with terminal B, SPS process, HARQ process, etc., and/or Clear the buffer for performing multicast services with the second terminal, etc.
  • terminal B After terminal B sends the link release information, or after terminal B receives the link release confirmation information sent by terminal A 1 and terminal A 2, terminal B releases the link connection and association with terminal A 1 and terminal A 2.
  • Relationship and/or link resources, etc. for example, release the stored terminal A 1 ID, terminal A 2 ID, or RRC configuration related to terminal A 1, or SRB, or DRB information, RRC configuration related to terminal A 2, or SRB, or DRB and other information, and/or release SPS resources reserved for multicast services with terminal A 1 and terminal A 2 (resources for sending or receiving SPS services), SPS process, HARQ process, etc., and / Or clear the buffer for multicast service with terminal A 1 and terminal A 2.
  • Scenario 3 Mode2d scenario
  • terminal A is the dispatching terminal
  • terminal B is the dispatched terminal, as shown in Figure 5:
  • the scheduled terminal sends link release information to the scheduling terminal; wherein the scheduled terminal can obtain link resources in mode 1 or mode 2 and send link release information to the scheduling terminal, or can forward link release information through the base station Ways to send link release information to the dispatch terminal.
  • Sending link release information can be achieved through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the SFCI resource agreed between the transmitting and receiving terminals.
  • send SCI and SFCI where SCI is used to indicate the resource location of SFCI, and SFCI is used to carry link release information.
  • the dispatching terminal based on the indication of whether to send link release confirmation information in the network configuration information or pre-configuration information or link release information, if the link release confirmation information is confirmed to be sent, the dispatching terminal sends the link release information to the dispatched terminal after receiving the link release information.
  • the link release confirmation message is shown in step S501a in FIG. 5.
  • the scheduling terminal After receiving the link release information sent by the scheduled terminal, the scheduling terminal stops allocating resources to the scheduled terminal; for example, the scheduling terminal releases the scheduled terminal ID, the RRC configuration related to the scheduled terminal, or information such as SRB or DRB , And stop allocating resources to the scheduled terminal. After sending the link release information, the scheduled terminal can stop receiving the resources allocated by the scheduling terminal.
  • the dispatched terminal does not need to search for other available dispatching terminals or obtain link resources through the searched dispatching terminal, until the dispatched terminal has a service to send and then search or search again
  • the scheduling terminal obtains link resources. If the dispatched terminal finds that there are other available dispatching terminals around and the dispatched terminal has services to send, it selects other dispatching terminals to apply for resources. If the scheduled terminal does not search for other available scheduling terminals around, it enters other resource allocation modes, such as Mode1, or Mode2a, or Mode2c.
  • the scheduled terminal can first send link release information, and then search for other available scheduling terminals around; or the scheduled terminal can first search for other available scheduling terminals around, and then send link release information; or both can be performed simultaneously . That is, the scheduled terminal can continuously search for other available scheduling terminals around it, regardless of whether the link release information is sent or not, so that after sending the link release information, it can quickly switch to other scheduling terminals to apply for resources.
  • Scenario 4 Mode2d scenario
  • terminal A is the dispatched terminal
  • terminal B is the dispatching terminal
  • the scheduling terminal sends link release information to the scheduled terminal; wherein the scheduling terminal can use mode1 or mode2 to obtain link resources and send link release information to the scheduled terminal, or it can forward the link release information through the base station. Ways to send link release information to the scheduled terminal.
  • Sending link release information can be achieved through RRC signaling, SCI or SFCI.
  • the SFCI can also be sent through the SFCI resource agreed between the transmitting and receiving terminals.
  • send SCI and SFCI where SCI is used to indicate the resource location of SFCI, and SFCI is used to carry link release information.
  • the scheduled terminal based on the indication of whether to send link release confirmation information in the network configuration information or pre-configuration information or link release information, if the sending of the link release confirmation information is confirmed, the scheduled terminal will send it to the dispatching terminal after receiving the link release information
  • the link release confirmation message is shown in step S601a in FIG. 6.
  • the scheduling terminal stops allocating resources to the scheduled terminal; for example, the scheduling terminal releases the scheduled terminal ID, the RRC configuration related to the scheduled terminal, or information such as SRB or DRB, and stops allocating resources to the scheduled terminal.
  • the scheduled terminal After receiving the link release information sent by the scheduling terminal, the scheduled terminal stops receiving the resources allocated by the scheduling terminal; for example, the scheduled terminal releases the scheduling terminal ID, the RRC configuration related to the scheduling terminal, or information such as SRB or DRB, and Stop receiving resources allocated by the scheduling terminal.
  • the dispatched terminal does not need to search for other available dispatching terminals or obtain link resources through the searched dispatching terminal, until the dispatched terminal has a service that needs to be sent and then search or search again.
  • the scheduling terminal obtains link resources. If the dispatched terminal finds that there are other available dispatching terminals around and the dispatched terminal has services to send, it selects other dispatching terminals to apply for resources. If the scheduled terminal does not search for other available scheduling terminals around, it enters other resource allocation modes, such as Mode1, or Mode2a, or Mode2c.
  • the scheduled terminal can search for other available scheduling terminals around before or after receiving the link release information, that is, the scheduled terminal can continuously search for other available scheduling terminals around, regardless of whether the link release information is received or not. , So that after receiving the link release information, you can quickly switch to other scheduling terminals to apply for resources.
  • the link release information transmission method of the embodiments of the present disclosure can receive link release information, and the link release information is used to indicate the release of the first terminal and the second terminal (that is, the sending terminal of the link release information). ), the first terminal can release the link with the second terminal in time based on the link release information, thereby avoiding the waste of channel resources.
  • an embodiment of the present disclosure provides a method for transmitting link release information, which is applied to a second terminal, and includes:
  • Step 701 Send link release information, where the link release information is used to release a link between a first terminal and the second terminal, where the first terminal is a receiving terminal of the link release information.
  • the second terminal can send link release information, and the link release information is used to indicate the release of the link between the first terminal and the second terminal (that is, the sending terminal of the link release information), so that the first terminal can receive After the link release information sent by the second terminal, the link with the second terminal is released in time based on the link release information, thereby avoiding channel resource waste.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the link release information after sending the link release information, it also includes:
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the second terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the first terminal;
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, stop receiving the link resource allocated by the first terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • the method further includes:
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, search for the scheduled terminal, and after stopping receiving the link resource allocated by the first terminal, obtain the link resource through the searched scheduling terminal.
  • the method further includes:
  • the link resource is acquired through a resource allocation mode other than the first resource allocation mode.
  • the link release information after sending the link release information, it also includes:
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • this method is applied to the second terminal, and it cooperates with the link release information transmission method applied to the first terminal to realize the link release information transmission, and the above link release information transmission method applied to the first terminal
  • the implementation of the embodiment is applicable to this method, and the same technical effect can also be achieved.
  • an embodiment of the present disclosure provides a terminal device.
  • the terminal device is a first terminal, and includes a transceiver 820, a memory 830, a processor 810, and a The computer program running on the processor 810;
  • the processor 810 is configured to receive link release information, where the link release information is used to instruct to release the link between the first terminal and the second terminal, where the second terminal is the link release The sending terminal of the information.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • processor is also used for:
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the first terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the second terminal;
  • the first terminal When the first terminal is a scheduled terminal in the first resource allocation mode, stop receiving link resources allocated by the second terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • processor is also used for:
  • the scheduling terminal When the first terminal is a scheduled terminal in the first resource allocation mode, the scheduling terminal is searched, and after stopping receiving the link resource allocated by the second terminal, the link resource is obtained through the searched scheduling terminal.
  • processor is also used for:
  • the link resource is obtained through a resource allocation mode other than the first resource allocation mode.
  • the transceiver is also used for:
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • processor is also used for:
  • an embodiment of the present disclosure provides a terminal device, the terminal device is a second terminal, a transceiver 820, a memory 830, a processor 810, and the The computer program running on the processor 810;
  • the processor 810 is configured to send link release information, where the link release information is used to release the link between the first terminal and the second terminal, where the first terminal is the link release information The receiving terminal.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • processor is used for:
  • the link connection, association relationship, and link between the first terminal and the second terminal are released At least one of the resources;
  • the second terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the first terminal;
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, stop receiving the link resource allocated by the first terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • processor is also used for:
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, search for the scheduled terminal, and after stopping receiving the link resource allocated by the first terminal, obtain the link resource through the searched scheduling terminal.
  • processor is also used for:
  • the link resource is acquired through a resource allocation mode other than the first resource allocation mode.
  • the transceiver is also used for:
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 810 and various circuits of the memory represented by the memory 830 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein.
  • the bus interface provides the interface.
  • the transceiver 820 may be a plurality of elements, that is, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the user interface 840 may also be an interface capable of connecting externally and internally with the required equipment, and the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.
  • the processor 810 is responsible for managing the bus architecture and general processing, and the memory 830 can store data used by the processor 810 when performing operations.
  • the embodiment of the present disclosure also provides a link release information transmission device, which is applied to a first terminal, and includes:
  • the receiving module is configured to receive link release information, where the link release information is used to instruct to release the link between the first terminal and the second terminal, and the second terminal is the source of the link release information Sending terminal.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the device further includes:
  • the first release processing module is configured to release the link between the first terminal and the second terminal when the first terminal is a receiving terminal or a sending terminal in a side link unicast or multicast scenario At least one of path connection, association relationship, and link resource;
  • the first terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the second terminal;
  • the first terminal When the first terminal is a scheduled terminal in the first resource allocation mode, stop receiving link resources allocated by the second terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • the device further includes:
  • the first processing module is configured to search for the scheduled terminal when the first terminal is the scheduled terminal in the first resource allocation mode, and after stopping receiving the link resource allocated by the second terminal, through the searched The scheduling terminal obtains link resources.
  • the device further includes:
  • the second processing module is configured to obtain link resources through resource allocation modes other than the first resource allocation mode after stopping receiving the link resources allocated by the second terminal if the scheduling terminal is not found.
  • the device further includes:
  • the confirmation message sending module is used to send the link release confirmation message.
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the device further includes:
  • the confirmation module is used to determine whether to send link release confirmation information according to network configuration information or pre-configuration information or link release information.
  • the device can receive link release information, and the link release information is used to instruct to release the link between the first terminal and the second terminal (that is, the sending terminal of the link release information), so that the first terminal can be based on the link.
  • the channel release information releases the link with the second terminal in time, thereby avoiding channel resource waste.
  • the device is a device to which the above-mentioned link release information transmission method applied to the first terminal is applied, and the implementation of the embodiment of the above-mentioned link release information transmission method applied to the first terminal is applicable to this device, The same technical effect can also be achieved.
  • the embodiment of the present disclosure provides a link release information transmission device, which is applied to a second terminal, and includes:
  • the sending module is configured to send link release information, where the link release information is used to release the link between the first terminal and the second terminal, where the first terminal is the receiving of the link release information terminal.
  • the link release information includes at least one of the following:
  • First information where the first information is used to indicate that the current information is link release information
  • Second information where the second information is used to indicate whether to feed back link release confirmation information
  • Third information where the third information is used to indicate the resources occupied by the feedback link release confirmation information
  • the first set of logos The first set of logos.
  • the first identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the first group identifier includes:
  • the identifier of the group where the second terminal is located is located.
  • the device further includes:
  • the second release processing module is configured to release the link between the first terminal and the second terminal when the second terminal is a receiving terminal or a sending terminal in a sidelink unicast or multicast scenario At least one of path connection, association relationship, and link resource;
  • the second terminal is a scheduling terminal in the first resource allocation mode, stop allocating link resources to the first terminal;
  • the second terminal When the second terminal is a scheduled terminal in the first resource allocation mode, stop receiving the link resource allocated by the first terminal;
  • the first resource allocation mode is a resource allocation mode of the terminal scheduling terminal.
  • the device further includes:
  • the third processing module is configured to search for the scheduled terminal when the second terminal is the scheduled terminal in the first resource allocation mode, and after stopping receiving the link resource allocated by the first terminal, through the searched The scheduling terminal obtains link resources.
  • the device further includes:
  • the fourth processing module is configured to, if the scheduling terminal is not found, after stopping receiving the link resource allocated by the first terminal, obtain the link resource through a resource allocation mode other than the first resource allocation mode.
  • the device further includes:
  • the confirmation message receiving module is used to receive the link release confirmation message.
  • the link release confirmation information includes at least one of the following:
  • Fourth information where the fourth information is used to indicate that the current information is link release confirmation information
  • the second identifier includes:
  • the identifier of the second terminal is the identifier of the second terminal.
  • the second group of identifiers include:
  • the identifier of the group where the second terminal is located is located.
  • the device can send link release information, and the link release information is used to instruct to release the link between the first terminal and the second terminal (that is, the sending terminal of the link release information), so that the first terminal can be After the link release information sent by the second terminal, the link with the second terminal is released in time based on the link release information, thereby avoiding channel resource waste.
  • the device is a device to which the link release information transmission method applied to the second terminal described above is applied, and the implementation of the embodiment of the link release information transmission method applied to the second terminal is applicable to this device, The same technical effect can also be achieved.
  • the embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method for transmitting the link release information as applied to the first terminal is realized, or the Steps in the method for transmitting link release information of the second terminal.
  • Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • terminals described in this specification include but are not limited to smart phones, tablet computers, etc., and many of the described functional components are referred to as modules, in order to more particularly emphasize the independence of their implementation methods.
  • an identified executable code module may include one or more physical or logical blocks of computer instructions. For example, it may be constructed as an object, process, or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different bits. When these instructions are logically combined together, they constitute a module and implement the requirements of the module. purpose.
  • the executable code module may be a single instruction or many instructions, and may even be distributed on multiple different code segments, distributed in different programs, and distributed across multiple memory devices.
  • operating data can be identified within the module, and can be implemented in any suitable form and organized in any suitable type of data structure. The operating data may be collected as a single data set, or may be distributed in different locations (including on different storage devices), and at least partly may only exist as electronic signals on the system or network.
  • the module can be realized by software, taking into account the level of hardware technology in the related technology, the module can be realized by software.
  • the hardware circuit includes conventional very large-scale integration (VLSI) circuits or gate arrays, and semiconductors or other discrete components in related technologies such as logic chips and transistors.
  • VLSI very large-scale integration
  • Modules can also be implemented with programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP Device, DSPD), programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and others for performing the functions described in this disclosure Electronic unit or its combination.
  • ASICs application specific integrated circuits
  • DSP digital signal processors
  • DSP Device digital signal processing devices
  • DPD digital signal processing devices
  • PLD programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

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

Abstract

本公开提供一种链路释放信息传输方法、装置及设备。该方法应用于第一终端，包括：接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。

Description

链路释放信息传输方法、装置及设备
相关申请的交叉引用
本申请主张在2019年2月2日在中国提交的中国专利申请No.201910108017.1的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种链路释放信息传输方法、装置及设备。
背景技术
相关技术中的长期演进LTE(Long Term Evolution)系统中，直接通信接口的业务只支持广播业务，而对于新空口NR(New Radio)，直接通信接口的业务相对LTE会更加丰富，除了支持广播业务之外，还支持单播和组播业务。并且在LTE系统中，支持Mode3和Mode4，Mode3为网络调度的资源分配模式，Mode4为终端自主选择的资源分配模式，而NR对终端自主选择的资源分配模式(NR中为Mode2)进行了细分，其中一种细分模式为Mode2d，即由一个用户终端UE(调度UE)调度其他UE的通信资源(终端调度其他终端的资源分配模式)。对于单播和组播业务，都需要收发UE之间建立关联关系，对于Mode2d模式，调度UE和其他被调度UE之间也需要建立关联关系。
然而，对于单播，组播业务，如果业务完成或者某一方终端离开，在已建立的关联关系未释放的情况下，则会造成终端不知道该关联关系已断开，继续占用信道资源发送信息，造成了信道资源浪费。同样，对于Mode2d模式，调度终端和被调度终端之间，在已建立的关联关系未释放的情况下，如果业务完成(被调度终端不需要再被调度资源)或者某一方终端离开，则会造成终端不知道该关联关系已断开，调度终端会继续分配资源，或者被调度UE继续申请资源，造成了信道资源浪费。
发明内容
本公开的目的是提供一种链路释放信息传输方法、装置及设备，能够实现终端间链路的及时释放，避免信道资源浪费。
为达到上述目的，本公开的实施例提供一种链路释放信息传输方法，应用于第一终端，包括：
接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，在接收链路释放信息之后，还包括：
当所述第一终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第一终端为第一资源分配模式中的调度终端，则停止向所述第二终端分配链路资源；
当所述第一终端为第一资源分配模式中的被调度终端，则停止接收所述第二终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述方法还包括：
当所述第一终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述方法还包括：
若未搜索到调度终端，则在停止接收所述第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，在接收链路释放信息之后，还包括：
发送链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，在发送链路释放确认信息之前，所述方法还包括：
根据网络配置信息或预配置信息或链路释放信息，确定是否发送链路释放确认信息。
为达到上述目的，本公开的实施例提供一种链路释放信息传输方法，应用于第二终端，包括：
发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，在发送链路释放信息之后，还包括：
当所述第二终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第二终端为第一资源分配模式中的调度终端，则停止向所述第一终端分配链路资源；
当所述第二终端为第一资源分配模式中的被调度终端，则停止接收所述第一终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述方法还包括：
当所述第二终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第一终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述方法还包括：
若未搜索到调度终端，则在停止接收所述第一终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，在发送链路释放信息之后，还包括：
接收链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
为达到上述目的，本公开的实施例提供一种终端设备，所述终端设备为第一终端，包括收发器、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；
所述处理器用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
为达到上述目的，本公开的实施例提供一种终端设备，所述终端设备为第二终端，包括收发器、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；
所述处理器用于发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
为达到上述目的，本公开的实施例提供一种链路释放信息传输装置，应用于第一终端，包括：
接收模块，用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
为达到上述目的，本公开的实施例提供一种链路释放信息传输装置，应用于第二终端，包括：
发送模块，用于发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
为达到上述目的，本公开的实施例提供一种计算机可读存储介质，其上存储有计算机程序，所述程序被处理器执行时实现如上应用于第一终端的链路释放信息传输方法，或者实现如上应用于第二终端的链路释放信息传输方法中的步骤。
本公开的上述技术方案的有益效果如下：
本公开实施例的链路释放信息传输方法，能够接收链路释放信息，而该链路释放信息用于指示释放第一终端(即链路释放信息的接收终端)与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为V2X通信示意图；
图2为本公开实施例的应用于第一终端的链路释放信息传输方法的流程示意图；
图3为场景一的应用示意图；
图4为场景二的应用示意图；
图5为场景三的应用示意图；
图6为场景四的应用示意图；
图7为本公开实施例的应用于第二终端的链路释放信息传输方法的流程示意图；
图8为本公开实施例的终端设备的结构示意图。
具体实施方式
为使本公开要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。
如图1所示，为相关技术中车到一切V2X(Vehicle to Everything)通信示意图。设备和设备之间允许直接进行设备之间的直接通信，如UE1和UE2。为了便于描述，定义设备和设备之间的侧行通信链路为Sidelink(侧行)链路，其对应的无线接口称为直接通信接口(也称为Sidelink接口)；网络(基站eNodeB)与直接通信设备之间的蜂窝通信链路称之为Uu link，其对应的接口称为Uu接口。
典型的直接通信场景包括如下三种：直接通信终端之间一对一通信(单播)；一个设备一次可以给一个通信群组里的所有设备发送相同数据(组播)；一个设备一次可以给所有附近的设备发送相同数据(广播)。
如图2所示，本公开实施例的一种链路释放信息传输方法，应用于第一终端，包括：
步骤201，接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
按照上述步骤201，该第一终端能够接收链路释放信息，而该链路释放信息用于指示释放第一终端与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
本公开的实施例，主要针对NR V2X系统中的单播、组播场景，以及第一资源分配模式(Mode2d模式，终端调度终端(其他终端)的资源分配模式)场景中。对于单播场景，第一终端可以为单播业务的发送终端，第二终端则为该单播业务的接收终端，或者第一终端为单播业务的接收终端，第二终端则为该单播业务的发送终端；对于组播场景，第一终端可以为组播业务的发送终端，第二终端则为该组播业务的接收终端，或者第一终端为组播业务的接收终端，第二终端则为该组播业务的发送终端；对于Mode2d场景，第一终端可以为调度终端，则第二终端为被调度终端，或者第一终端为被调度终端，则第二终端为调度终端。
可选地，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
这里，若链路释放信息包括第一信息，将实现告知第一终端接收到的信息为链路释放信息的目的。当然，第一信息除显性存在于链路释放信息中，还可以其他隐性方式存在，如作为链路释放信息的加扰扰码，或者，除携带该第一信息外，链路释放信息也可通过自身来达到该目的，例如，占用配置或预配置的特定资源发送链路释放信息，此时，该链路释放信息中也能够不包括该第一信息。
若链路释放信息包括第二信息，将实现告知第一终端在接收到链路释放信息后反馈链路确认信息的目的。当然，第二信息除显性存在于链路释放信息中，还可以其他隐性方式存在，如作为链路释放信息的加扰扰码。或者，反馈链路确认信息也可是网络配置，或者预配置，或者通过组中簇头(group manager)配置等方式实现的，此时，该链路释放信息中也能够不包括该第二信息。
若链路释放信息包括第三信息，将实现告知第一终端反馈链路确认信息占用的资源。当然，反馈链路确认信息占用的资源也可是网络配置，或者预配置等方式实现的，此时，该链路释放信息中也能够不包括该第三信息。
若链路释放信息包括第一标识，将实现第一终端对链路释放目标终端的确认，即第一终端由链路释放信息中包括的终端标识，判断该第一终端是否为链路释放信息的目标接收端，和/或确定链路释放信息的发送端。当然，第一标识除显性存在于链路释放信息中，还可以其他隐性方式存在，如作为链 路释放信息的加扰扰码，此时，该链路释放信息中也能够不包括该第一标识。
若链路释放信息包括第一组标识，将实现组播场景第一终端对链路释放的目标终端组的确认。例如，第一终端为组播场景的业务数据接收终端，在接收到链路释放信息后，可基于该第一组标识，释放与该第一组标识对应组内的业务数据发送终端的连接。当然，第一组标识除显性存在于链路释放信息中，还可以其他隐性方式存在，如作为链路释放信息的加扰扰码，此时，该链路释放信息中也能够不包括该第一组标识。
在该实施例中，链路释放信息可采用无线资源控制RRC(Radio Resource Control)信令发送，或者采用侧行链路控制信息SCI(Sidelink Control Information)发送，或者采用侧行链路反馈控制信息SFCI(Sidelink Feedback Control Information)发送。
具体地，采用RRC信令发送链路释放信息，其中RRC信令中包括以下至少一项：
1)指示链路释放信息域(即第一信息)，例如采用布尔BOOLEAN类型或者枚举ENUMERATED类型：
BOOLEAN类型(true or false)，当链路释放信息域值为true，则表示该RRC信令包含链路释放信息；
ENUMERATED类型，当链路释放信息域值为枚举类型中的release，则表示该RRC信令包含链路释放信息。
2)终端ID或组ID(即第一标识或第一组标识)，其中，对于单播或组播场景，终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，包括调度终端ID和/或被调度终端ID。如果RRC信令是使用终端ID或组ID加扰的，则不需要在RRC信令中包含终端ID或组ID。
3)指示是否发送反馈链路释放确认信息(即第二信息)，如指示第一终端是否发送反馈链路释放确认信息等。如果是通过网络配置，或者预配置，或者通过组中簇头(group manager)配置等方式指示是否发送反馈链路释放确认信息，则不需要在RRC信令中包含是否发送反馈链路释放确认信息的指示。
4)指示用于发送链路释放确认信号所使用的资源(即第三信息)，如指 示用于发送链路释放确认信息所使用的SFCI资源，或者SCI资源等等。如果是在发送该RRC信令的SCI中指示用于发送链路释放确认信号所使用的资源，则不需要在RRC信令中包含链路释放确认信号占用的资源。
或者，采用侧行链路控制信息SCI发送链路释放信息，其中SCI中包括以下至少一项：
1)SCI类型域(即第一信息)，表示该SCI为链路释放信息，例如1比特，该1比特＝1时，表示该SCI为链路释放信息。
2)终端ID(identification)或组ID(即第一标识或第一组标识)，其中，对于单播或组播场景，该终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，该终端ID包括调度终端ID和/或被调度终端ID。如果SCI是使用终端ID或组ID加扰的，则不需要在SCI中包含终端ID或组ID。
3)指示是否发送反馈链路释放确认信息(即第二信息)，如指示第一终端是否发送反馈链路释放确认信息等。如果是通过网络配置，或者预配置，或者通过组中簇头(group manager)配置等方式指示是否发送反馈链路释放确认信息，则不需要在SCI中包含是否发送反馈链路释放确认信息的指示。
4)指示用于发送链路释放确认信息所使用的资源(即第三信息)，如指示用于发送链路释放确认信息所使用的SFCI资源，或者SCI资源等等。如果是通过网络配置，或者预配置等方式配置用于发送链路释放确认信号所使用的资源，则不需要在SCI中包含链路释放确认信号占用的资源。
又或者，采用侧行链路反馈控制信息SFCI发送链路释放信息，其中SFCI可以为：
方式1：采用序列表示该SFCI为链路释放信息，该序列与SFCI上传输的混合自动重传请求HARQ(Hybrid Automatic Repeat Request)序列，和/或，SFCI上传输的侧行链路服务请求SR(Service request)序列都是正交的，该序列可以是网络侧配置，或标准规定，或预配置的。进一步地，该序列与发送该链路释放信息的终端ID，或接收该链路释放信息的终端ID，或终端组ID相关，例如，生成该序列的生成因子包括所述终端ID或终端组ID，用于解决其他终端在该资源上的传输信号导致的冲突问题，使得接收端确定链路释 放目标终端或目标终端组。
方式2：包括以下至少一项：
1)SFCI类型域(即第一信息)，表示该SFCI为链路释放信息，例如1比特，该1比特＝1时，表示该SFCI为链路释放信息。
2)终端ID或组ID(即第一标识或第一组标识)，其中，对于单播或组播场景，该终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，该终端ID包括调度终端ID和/或被调度终端ID。如果SFCI是使用终端ID或组ID加扰的，则不需要在SFCI中包含终端ID和组ID。或者，如果终端之间约定好该发送链路释放信息SFCI的资源，则不需要该终端ID或组ID，或者可以只传输其中一个终端的ID或组ID，用于解决其他终端在该资源上的传输信号导致的冲突问题，使得接收端确定链路释放目标终端或目标终端组。
3)指示是否发送反馈链路释放确认信息(即第二信息)，如指示第一终端是否发送反馈链路释放确认信息等。如果是通过网络配置，或者预配置，或者通过组中簇头(group manager)配置等方式指示是否发送反馈链路释放确认信息，则不需要在SCI中包含是否发送反馈链路释放确认信息的指示。
4)指示用于发送链路释放确认信号所使用的资源(即第三信息)，如，指示用于发送链路释放确认信息所使用的SFCI资源，或者SCI资源等等。如果是通过网络配置，或者预配置等方式配置用于发送链路释放确认信号所使用的资源，则不需要在SFCI中包含链路释放确认信号占用的资源。
应该知道的是，在该实施例中，针对不同场景，执行终端间的链路释放方式是存在差异的，往往会基于应用场景以及第一终端的类型进行不同链路释放方式，所以，可选地，在接收链路释放信息之后，还包括：
当所述第一终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第一终端为第一资源分配模式中的调度终端，则停止向所述第二终端分配链路资源；
当所述第一终端为第一资源分配模式中的被调度终端，则停止接收所述 第二终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式，即Mode2d资源分配模式场景。
此外，考虑到Mode2d场景，链路释放后，被调度终端仍有业务数据需要发送的情况，可选地，所述方法还包括：
当所述第一终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
这样，在链路释放后，被调度终端仍有业务数据需要发送的情况，会在停止接收第二终端分配的链路资源之前，先搜索调度终端，从而在停止接收第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。其中，搜索调度终端可能还搜索到第二终端，所以，可选地，在停止接收第二终端分配的链路资源之后，通过搜索到的其他调度终端(即除第二终端外的调度终端)获取链路资源。当然，搜索调度终端的步骤，可以在接收链路释放信息的步骤之前或之后，且如果被调度终端没有业务需要发送，则被调度终端不需要搜索其他可用的调度终端或不需要通过搜索到的调度终端获取链路资源，直到被调度终端有业务需要发送再搜索或再通过搜索到的调度终端获取链路资源。
然而，被调度终端也可能搜索不到其他调度终端，因此，所述方法还包括：
若未搜索到调度终端，则在停止接收所述第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
这里，考虑到需要释放第二终端的链路，可选地，对于未搜索到其他调度终端(即除第二终端外的调度终端)的情况，会在停止接收第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。其中，资源分配模式除Mode2d模式之外，还可以是网络调度的资源分配模式Mode1、终端自选的资源分配模式Mode2a或者基于网络配置授权的终端资源分配模式Mode2c。
还应该知道的是，本公开实施例中，网络配置信息或预配置信息或链路 释放信息会配置第一终端在接收链路释放信息之后，是否发送/反馈链路释放确认信息。所以，在接收链路释放信息之后，还包括：
发送链路释放确认信息。
如此，第一终端在接收链路释放信息之后，通过发送链路释放确认信息，来告知第二终端，第一终端成功接收链路释放信息。
可选地，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
这里，若链路释放确认信息包括第四信息，将实现告知第二终端接收到的信息为链路释放确认信息的目的。当然，第四信息除显性存在于链路释放确认信息中，还可以其他隐性方式存在，如作为链路释放确认信息的加扰扰码，或者，除携带该第四信息外，链路释放确认信息也可通过自身来达到该目的，例如，占用配置或预配置的特定资源发送链路释放确认信息，此时，该链路释放确认信息中也能够不包括该第四信息。
若链路释放确认信息包括第二标识，将实现第二终端对链路释放目标终端的确认，即第二终端由链路释放确认信息中包括的终端标识，判断该第二终端是否为链路释放确认信息的目标接收端，和/或确定链路释放确认信息的发送端。当然，第二标识除显性存在于链路释放确认信息中，还可以其他隐性方式存在，如作为链路释放确认信息的加扰扰码，此时，该链路释放确认信息中也能够不包括该第二标识。
若链路释放确认信息包括第二组标识，将实现组播场景第二终端对链路释放目标终端组的确认。例如，第二终端为组播场景的业务数据发送终端， 在接收到链路释放确认信息后，可基于该第二组标识，获知与该第二组标识对应组内的业务数据接收终端已收到链路释放信息。当然，第二组标识除显性存在于链路释放确认信息中，还可以其他隐性方式存在，如作为链路释放确认信息的加扰扰码，此时，该链路释放确认信息中也能够不包括该第二组标识。
在该实施例中，链路释放确认信息可采用RRC信令发送，或者采用SCI发送，或者采用SFCI发送。
具体地，采用RRC信令发送链路释放确认信息，其中RRC信令中包括以下至少一项：
1)指示链路释放确认信息域(即第四信息)，例如采用BOOLEAN类型或者ENUMERATED类型：
BOOLEAN类型(true or false)，当链路释放确认信息域值为true，则表示该RRC信令包含链路释放确认信息；
ENUMERATED类型，当链路释放确认信息域值为枚举类型中的ACK，则表示该RRC信令包含链路释放确认信息。
2)终端ID或组ID(即第二标识或第二组标识)，其中，对于单播或组播场景，终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，包括调度终端ID和/或被调度终端ID。如果RRC信令是使用终端ID或组ID加扰的，则不需要在RRC信令中包含终端ID或组ID。
或者，采用SCI发送链路释放确认信息，其中SCI中包括以下至少一项：
1)SCI类型域(即第四信息)，表示该SCI为链路释放确认信息，例如1比特，该1比特＝1时，表示该SCI为链路释放确认信息。
2)终端ID或组ID(即第二标识或第二组标识)，其中，对于单播或组播场景，该终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，该终端ID包括调度终端ID和/或被调度终端ID。如果SCI是使用终端ID或组ID加扰的，则不需要在SCI中包含终端ID或组ID。
又或者，采用SFCI发送链路释放确认信息，其中SFCI可以为：
方式1：如果链路释放信息指示了链路释放确认信息的资源位置，例如通过链路释放信息的SCI指示了链路释放确认信息的SFCI资源位置，则与单 播、组播业务的HARQ反馈发送方式类似，占用指示的SFCI资源位置发送链路释放确认信息，该链路释放确认信息可以为序列或比特信息，用于表示链路释放信息的接收情况，例如ACK(确认接收正确)或NACK(确认接收错误，需要重传链路释放信息)。
方式2：采用序列表示该SFCI为链路释放确认信息，该序列与SFCI上传输的HARQ序列，和/或，SFCI上传输的SR序列都是正交的，该序列可以是网络侧配置，或标准规定，或预配置的。进一步地，该序列与发送该链路释放确认信息的终端ID，或接收该链路释放信息的终端ID，或终端组ID相关，用于解决其他终端在该资源上的传输信号导致的冲突问题，使得接收端确定链路释放目标终端或目标终端组。
方式3：包括以下至少一项：
1)SFCI类型域(即第四信息)，表示该SFCI为链路释放确认信息，例如1比特，该1比特＝1时，表示该SFCI为链路释放确认信息。
2)终端ID或组ID(即第二标识或第二组标识)，其中，对于单播或组播场景，该终端ID包括接收终端ID，发送终端ID，组ID中的至少一项；对于Mode 2d场景，该终端ID包括调度终端ID和/或被调度终端ID。如果SFCI是使用终端ID或组ID加扰的，则不需要在SFCI中包含终端ID和组ID。或者，如果终端之间约定好该发送链路释放确认信息SFCI的资源，则不需要该终端ID或组ID，或者可以只传输其中一个终端的ID或组ID，用于解决其他终端在该资源上的传输信号导致的冲突问题，使得接收端确定链路释放目标终端或目标终端组。
该实施例中，基于是否发送链路释放确认信息，可选地，在发送链路释放确认信息之前，所述方法还包括：
根据网络配置信息或预配置信息或链路释放信息，确定是否发送链路释放确认信息。
如此，即可基于配置，由网络配置信息或预配置信息，或基于链路释放信息确认发送链路释放确认信息后，发送链路释放确认信息。
下面将以NR的直连系统为例，针对不同场景说明本公开实施例的链路释放信息传输方法的应用：
场景一、单播场景，如图3所示：
S301，终端乙向终端甲发送链路释放信息；其中，终端乙可以采用mode1或者终端自选的资源分配模式mode2获得链路资源，并向终端甲发送链路释放信息，或者可以通过基站转发链路释放信息的方式向终端甲发送链路释放信息。
具体链路释放信息设计方式如上内容，这里不再赘述。发送链路释放信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI。或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放信息。
S302，终端甲接收终端乙发送的链路释放信息后，基于网络配置信息或预配置信息或链路释放信息中是否发送链路释放确认信息的指示，若确认发送链路释放确认信息，则向终端乙发送链路释放确认信息；其中，终端甲可以采用mode1或者mode2模式获得链路资源，并向终端乙发送链路释放确认信息，或者可以通过基站转发链路释放确认信息的方式向终端乙发送链路释放确认信息。如果网络配置信息或预配置信息或链路释放信息指示了发送链路释放确认信息的资源，则通过网络配置信息或预配置信息或链路释放信息指示的资源发送该链路释放确认信息。具体地，通过网络配置，是采用广播信令配置。而除链路释放信息外，还可由其他信息完成终端之间对链路释放确认信号是否发送的配置。
并且，如果网络配置信息或预配置信息或链路释放信息配置了发送链路释放确认信息，则终端乙需接收到终端甲发送的链路释放确认信息(如ACK)，才可以释放与终端甲的链路连接、关联关系和/或链路资源等。如果没有接收到终端甲发送的链路释放确认信息，例如，发送的链路释放确认信息没有接收到或者接收到链路释放确认信息为NACK，则需要重传链路释放信息。若N次重传链路释放信息，仍然没有接收到链路释放确认信息或接收到链路释放确认信息为NACK，则释放与终端甲的链路连接、关联关系和/或链路资源等，此时表示终端乙与终端甲之间的链路条件较远或较差，其中N为大于等于1的整数，可通过网络配置或预配置或标准规定。另一种实现的方法，终 端乙在发送链路释放信息后，等待一段时间timer T，如果在timer T内，没有接收到链路释放确认信息，即timer T超时，则释放与终端甲的链路连接、关联关系和/或链路资源等(或者当接收到链路释放确认信息为NACK时，可以进行重传链路释放信息，每次重传链路释放信息，重置timer T)，其中timer T可以通过网络配置或预配置或标准规定。
此外，具体链路释放确认信息设计如上述内容，这里不再赘述。发送链路释放确认信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI；或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放确认信息。
当然，若网络配置信息或预配置信息或链路释放信息指示不发送链路释放确认信息，则无需向第二终端发送链路释放确认信号。
S303，终端甲释放与终端乙之间的链路连接、关联关系和/或链路资源等；如，释放存储的终端乙ID，或与终端乙相关的侧行链路RRC配置，或信令无线承载SRB(Signalling Radio Bearer)，或数据无线承载DRB(Data Radio Bearer)等信息，和/或释放为与终端乙进行单播业务预留的半静态调度SPS(Semi-Persistent Scheduling)资源(用于发送或接收SPS业务的资源)，SPS进程，HARQ进程等等，和/或清空与终端乙进行单播业务的缓存buffer等。
S304，终端乙发送链路释放信息后，或者终端乙接收终端甲发送的链路释放确认信息后，终端乙释放与终端甲之间的链路连接、关联关系和/或链路资源等；如，释放存储的终端甲ID，或与终端甲相关的RRC配置，或SRB，或DRB等信息，和/或释放为与终端甲进行单播业务预留的SPS资源(用于发送或接收SPS业务的资源)，SPS进程，HARQ进程等等，和/或清空与终端甲进行单播业务的buffer。
场景二、组播场景(发送终端向多个接收终端发送组播信号)
组播场景中，若链路释放信息的接收终端为组播业务的发送终端，链路释放信息的发送终端为组播业务的接收终端，则与上述场景一单播的流程一样，这里不再赘述。只是在释放链路时，需要释放存储的对方终端ID，或与组播业务相关的RRC配置，或SRB，或DRB等信息，和/或释放为组播业务 预留的SPS资源(用于发送或接收SPS业务的资源)，SPS进程，HARQ进程等等，和/或清空组播业务相关的buffer。
组播场景中，若链路释放信息的接收终端为组播业务的接收终端，链路释放信息的发送终端为组播业务的发送终端，则如图4所示：
S401，终端乙向终端甲1和终端甲2发送链路释放信息；其中，该链路释放信息为组播信号，其中，终端乙可以采用mode1或者mode2获得链路资源，并向终端甲1和终端甲2发送链路释放信息，或者可以通过基站转发链路释放信息的方式向终端甲1和终端甲2发送链路释放信息。
具体链路释放信息设计方式如上内容，这里不再赘述。发送链路释放信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI。或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放信息。此时，链路释放信息中包括组ID。
S402，终端甲1/终端甲2接收终端乙发送的链路释放信息后，基于网络配置信息或预配置信息或链路释放信息中是否发送链路释放确认信息的指示，若确认发送链路释放确认信息，则向终端乙发送链路释放确认信息；其中，终端甲1/终端甲2可以采用mode1或者mode2模式获得链路资源，并向终端乙发送链路释放确认信息，或者可以通过基站转发链路释放确认信息的方式向终端乙发送链路释放确认信息。如果网络配置信息或预配置信息或链路释放信息指示了发送链路释放确认信息的资源，则通过网络配置信息或预配置信息或链路释放信息指示的资源发送该链路释放确认信息。具体地，通过网络配置，是采用广播信令配置。而除链路释放信息外，还可由其他信息完成终端之间对链路释放确认信号是否发送的配置。
并且，如果网络配置信息或预配置信息或链路释放信息配置了发送链路释放确认信息，则终端乙需接收到终端甲1/终端甲2(链路释放信息的所有接收终端)发送的链路释放确认信息(如ACK)，才可以释放与终端甲1/终端甲2之间组播业务的链路连接、关联关系和/或链路资源等。如果存在至少一个链路释放信息的接收终端，其发送的链路释放确认信息没有被终端乙接 收到或者接收到链路释放确认信息为NACK，则需要重传链路释放信息。若N次重传链路释放信息，仍然存在没有接收到链路释放确认信息或接收到链路释放确认信息为NACK的情况，则释放与终端甲1/终端甲2之间组播业务的链路连接、关联关系和/或链路资源等，此时表示终端乙与终端甲1/终端甲2之间组播业务的链路条件较远或较差，其中N为大于等于1的整数，可通过网络配置或预配置或标准规定。另一种实现的方法，终端乙在发送链路释放信息后，等待一段时间timer T，如果在timer T内，没有接收到链路释放确认信息，即timer T超时，则释放与终端甲1/终端甲2之间组播业务的链路连接、关联关系和/或链路资源等(或者当接收到链路释放确认信息为NACK时，可以进行重传链路释放信息，每次重传链路释放信息，重置timer T)，其中timer T可以通过网络配置或预配置或标准规定。
此外，具体链路释放确认信息设计如上述内容，这里不再赘述。发送链路释放确认信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI；或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放确认信息。
当然，若网络配置信息或预配置信息或链路释放信息指示不发送链路释放确认信息，则无需向第二终端发送链路释放确认信号。
S403，终端甲1/终端甲2释放与终端乙之间的链路连接、关联关系和/或链路资源等；如，释放存储的终端乙ID，或与终端乙相关的侧行链路RRC配置，或SRB，或DRB等信息，和/或释放为与终端乙进行组播业务预留的SPS资源(用于发送或接收SPS业务的资源)，SPS进程，HARQ进程等等，和/或清空与第二终端进行组播业务的buffer等。
S404，终端乙发送链路释放信息后，或者终端乙接收终端甲1/终端甲2发送的链路释放确认信息后，终端乙释放与终端甲1和终端甲2之间的链路连接、关联关系和/或链路资源等；如，释放存储的终端甲1ID，终端甲2ID，或与终端甲1相关的RRC配置，或SRB，或DRB等信息，与终端甲2相关的RRC配置，或SRB，或DRB等信息，和/或释放为与终端甲1和终端甲2进行组播业务预留的SPS资源(用于发送或接收SPS业务的资源)，SPS进 程，HARQ进程等等，和/或清空与终端甲1和终端甲2进行组播业务的buffer。
场景三、Mode2d场景，且终端甲为调度终端，终端乙为被调度终端，如图5所示：
S501，被调度终端向调度终端发送链路释放信息；其中，被调度终端可以采用mode1或者mode2模式获得链路资源，并向调度终端发送链路释放信息，或者可以通过基站转发链路释放信息的方式向调度终端发送链路释放信息。
具体链路释放信息设计方法如上内容，这里不再赘述。发送链路释放信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI。或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放信息。
其中，基于网络配置信息或预配置信息或链路释放信息中是否发送链路释放确认信息的指示，若确认发送链路释放确认信息，则调度终端接收链路释放信息后，向被调度终端发送链路释放确认信息，如图5中步骤S501a所示。
S502，调度终端接收被调度终端发送的链路释放信息后，停止向被调度终端分配资源；如，调度终端释放被调度终端ID，与被调度终端相关的RRC配置，或SRB，或DRB等信息，并停止向被调度终端分配资源。而被调度终端在发送该链路释放信息后，可停止接收调度终端分配的资源。
S503，若被调度终端仍然有业务需要发送，则被调度终端搜索周围其他可用的调度终端。
如果被调度终端没有业务需要发送，则被调度终端不需要搜索其他可用的调度终端或不需要通过搜索到的调度终端获取链路资源，直到被调度终端有业务需要发送再搜索或再通过搜索到的调度终端获取链路资源。如果被调度终端搜索到周围有其他可用的调度终端并且被调度终端有业务需要发送，则选择其他调度终端申请资源。如果被调度终端没有搜索到周围有可用的其他调度终端，则进入其他资源分配模式，例如Mode1，或者Mode2a，或者Mode2c。
其中，被调度终端可以先发送链路释放信息，之后再搜索周围其他可用的调度终端；或者被调度终端可以先搜索周围其他可用的调度终端，再发送链路释放信息；或者两者可以同时进行。即被调度终端可以一直持续搜索周围其他可用的调度终端，与发送链路释放信息与否没有关系，便于当发送链路释放信息之后，可以快速切换到其他调度终端申请资源。
场景四、Mode2d场景，且终端甲为被调度终端，终端乙为调度终端，如图6所示：
S601，调度终端向被调度终端发送链路释放信息；其中，调度终端可以采用mode1或者mode2模式获得链路资源，并向被调度终端发送链路释放信息，或者可以通过基站转发链路释放信息的方式向被调度终端发送链路释放信息。
具体链路释放信息设计方法如上内容，这里不再赘述。发送链路释放信息可以通过RRC信令、SCI或者SFCI实现。其中，发送SFCI，除可使用上述mode1、mode2模式、或者基站转发的方式外，还可以通过收发终端之间约定好的SFCI资源发送该SFCI。或者发送SCI和SFCI，其中SCI用于指示SFCI的资源位置，SFCI用于承载链路释放信息。
其中，基于网络配置信息或预配置信息或链路释放信息中是否发送链路释放确认信息的指示，若确认发送链路释放确认信息，则被调度终端接收链路释放信息后，向调度终端发送链路释放确认信息，如图6中步骤S601a所示。
S602，调度终端停止向被调度终端分配资源；如，调度终端释放被调度终端ID，与被调度终端相关的RRC配置，或SRB，或DRB等信息，并停止向被调度终端分配资源。
S603，被调度终端接收调度终端发送的链路释放信息后，停止接收调度终端分配的资源；如被调度终端释放调度终端ID，与调度终端相关的RRC配置，或SRB，或DRB等信息，并停止接收调度终端分配的资源。
S604，若被调度终端仍然有业务需要发送，则被调度终端搜索周围其他可用的调度终端。
如果被调度终端没有业务需要发送，则被调度终端不需要搜索其他可用 的调度终端或不需要通过搜索到的调度终端获取链路资源，直到被调度终端有业务需要发送再搜索或再通过搜索到的调度终端获取链路资源。如果被调度终端搜索到周围有其他可用的调度终端并且被调度终端有业务需要发送，则选择其他调度终端申请资源。如果被调度终端没有搜索到周围有可用的其他调度终端，则进入其他资源分配模式，例如Mode1，或者Mode2a，或者Mode2c。
其中，被调度终端可以在接收链路释放信息之前或之后，搜索周围其他可用的调度终端，即被调度终端可以一直持续搜索周围其他可用的调度终端，与接收到链路释放信息与否没有关系，便于当接收到链路释放信息之后，可以快速切换到其他调度终端申请资源。
综上所述，本公开实施例的链路释放信息传输方法，能够接收链路释放信息，而该链路释放信息用于指示释放第一终端与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
如图7所示，本公开的实施例提供一种链路释放信息传输方法，应用于第二终端，包括：
步骤701，发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
第二终端能够发送链路释放信息，而该链路释放信息用于指示释放第一终端与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端在接收第二终端发送的链路释放信息后，基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，在发送链路释放信息之后，还包括：
当所述第二终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第二终端为第一资源分配模式中的调度终端，则停止向所述第一终端分配链路资源；
当所述第二终端为第一资源分配模式中的被调度终端，则停止接收所述第一终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述方法还包括：
当所述第二终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第一终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述方法还包括：
若未搜索到调度终端，则在停止接收所述第一终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，在发送链路释放信息之后，还包括：
接收链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
需要说明的是，该方法应用于第二终端，是与上述应用于第一终端的链路释放信息传输方法配合实现链路释放信息传输的，上述应用于第一终端的链路释放信息传输方法的实施例的实现方式适用于该方法，也能达到相同的技术效果。
如图8所示，本公开的实施例提供一种终端设备，所述终端设备为第一终端，包括：收发器820、存储器830、处理器810及存储在所述存储器830上并可在所述处理器810上运行的计算机程序；
所述处理器810用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述处理器还用于：
当所述第一终端为侧行链路单播或组播场景中的接收终端或者发送终端， 则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第一终端为第一资源分配模式中的调度终端，则停止向所述第二终端分配链路资源；
当所述第一终端为第一资源分配模式中的被调度终端，则停止接收所述第二终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述处理器还用于：
当所述第一终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述处理器还用于：
若未搜索到调度终端，则在停止接收所述第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，所述收发器还用于：
在所述处理器的控制下发送链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述处理器还用于：
根据网络配置信息或预配置信息或链路释放信息，确定是否发送链路释放确认信息。
另外，如图8所示，本公开的实施例提供一种终端设备，所述终端设备为第二终端，收发器820、存储器830、处理器810及存储在所述存储器830上并可在所述处理器810上运行的计算机程序；
所述处理器810用于发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述处理器用于：
当所述第二终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第二终端为第一资源分配模式中的调度终端，则停止向所述第一终端分配链路资源；
当所述第二终端为第一资源分配模式中的被调度终端，则停止接收所述第一终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述处理器还用于：
当所述第二终端为第一资源分配模式中的被调度终端，则搜索调度终端， 并在停止接收所述第一终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述处理器还用于：
若未搜索到调度终端，则在停止接收所述第一终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，所述收发器还用于：
在所述处理器的控制下接收链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器810代表的一个或多个处理器和存储器830代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发器820可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口840还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器810负责管理总线架构和通常的处理，存储器830可以存储处理器810在执行操作时所使用的数据。
本公开的实施例还提供一种链路释放信息传输装置，应用于第一终端，包括：
接收模块，用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述装置还包括：
第一释放处理模块，用于当所述第一终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第一终端为第一资源分配模式中的调度终端，则停止向所述第二终端分配链路资源；
当所述第一终端为第一资源分配模式中的被调度终端，则停止接收所述第二终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述装置还包括：
第一处理模块，用于当所述第一终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述装置还包括：
第二处理模块，用于若未搜索到调度终端，则在停止接收所述第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
其中，所述装置还包括：
确认信息发送模块，用于发送链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述装置还包括：
确认模块，用于根据网络配置信息或预配置信息或链路释放信息，确定是否发送链路释放确认信息。
该装置能够接收链路释放信息，而该链路释放信息用于指示释放第一终端与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
需要说明的是，该装置是应用了上述应用于第一终端的链路释放信息传输方法的装置，上述应用于第一终端的链路释放信息传输方法的实施例的实现方式适用于该装置，也能达到相同的技术效果。
本公开的实施例提供一种链路释放信息传输装置，应用于第二终端，包括：
发送模块，用于发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接 收终端。
其中，所述链路释放信息包括以下至少一项：
第一信息，所述第一信息用于指示当前信息为链路释放信息；
第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
第一标识；
第一组标识。
其中，所述第一标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第一组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
其中，所述装置还包括：
第二释放处理模块，用于当所述第二终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
当所述第二终端为第一资源分配模式中的调度终端，则停止向所述第一终端分配链路资源；
当所述第二终端为第一资源分配模式中的被调度终端，则停止接收所述第一终端分配的链路资源；
其中，所述第一资源分配模式为终端调度终端的资源分配模式。
其中，所述装置还包括：
第三处理模块，用于当所述第二终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第一终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
其中，所述装置还包括：
第四处理模块，用于若未搜索到调度终端，则在停止接收所述第一终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获 取链路资源。
其中，所述装置还包括：
确认信息接收模块，用于接收链路释放确认信息。
其中，所述链路释放确认信息包括以下至少一项：
第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
第二标识；
第二组标识。
其中，所述第二标识包括：
所述第一终端的标识；和/或
所述第二终端的标识。
其中，所述第二组标识包括：
所述第一终端所在的组的标识；和/或
所述第二终端所在的组的标识。
该装置能够发送链路释放信息，而该链路释放信息用于指示释放第一终端与第二终端(即链路释放信息的发送终端)之间的链路，可实现第一终端在接收第二终端发送的链路释放信息后，基于该链路释放信息及时释放与第二终端之间的链路，从而避免信道资源浪费。
需要说明的是，该装置是应用了上述应用于第二终端的链路释放信息传输方法的装置，上述应用于第二终端的链路释放信息传输方法的实施例的实现方式适用于该装置，也能达到相同的技术效果。
本公开的实施例还提供一种计算机可读存储介质，其上存储有计算机程序，所述程序被处理器执行时实现如上应用于第一终端的链路释放信息传输方法，或者实现如上应用于第二终端的链路释放信息传输方法中的步骤。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器 (CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
进一步需要说明的是，此说明书中所描述的终端包括但不限于智能手机、平板电脑等，且所描述的许多功能部件都被称为模块，以便更加特别地强调其实现方式的独立性。
本公开实施例中，模块可以用软件实现，以便由各种类型的处理器执行。举例来说，一个标识的可执行代码模块可以包括计算机指令的一个或多个物理或者逻辑块，举例来说，其可以被构建为对象、过程或函数。尽管如此，所标识模块的可执行代码无需物理地位于一起，而是可以包括存储在不同位里上的不同的指令，当这些指令逻辑上结合在一起时，其构成模块并且实现该模块的规定目的。
实际上，可执行代码模块可以是单条指令或者是许多条指令，并且甚至可以分布在多个不同的代码段上，分布在不同程序当中，以及跨越多个存储器设备分布。同样地，操作数据可以在模块内被识别，并且可以依照任何适当的形式实现并且被组织在任何适当类型的数据结构内。所述操作数据可以作为单个数据集被收集，或者可以分布在不同位置上(包括在不同存储设备上)，并且至少部分地可以仅作为电子信号存在于系统或网络上。
在模块可以利用软件实现时，考虑到相关技术中的硬件工艺的水平，所以可以以软件实现的模块，在不考虑成本的情况下，本领域技术人员都可以搭建对应的硬件电路来实现对应的功能，所述硬件电路包括常规的超大规模集成(VLSI)电路或者门阵列以及诸如逻辑芯片、晶体管之类的相关技术中的半导体或者是其它分立的元件。模块还可以用可编程硬件设备，诸如现场可编程门阵列、可编程阵列逻辑、可编程逻辑设备等实现。
上述范例性实施例是参考该些附图来描述的，许多不同的形式和实施例是可行而不偏离本公开精神及教示，因此，本公开不应被建构成为在此所提出范例性实施例的限制。更确切地说，这些范例性实施例被提供以使得本公开会是完善又完整，且会将本公开范围传达给那些熟知此项技术的人士。在 该些图式中，组件尺寸及相对尺寸也许基于清晰起见而被夸大。在此所使用的术语只是基于描述特定范例性实施例目的，并无意成为限制用。如在此所使用地，除非该内文清楚地另有所指，否则该单数形式“一”、“一个”和“该”是意欲将该些多个形式也纳入。会进一步了解到该些术语“包含”及/或“包括”在使用于本说明书时，表示所述特征、整数、步骤、操作、构件及/或组件的存在，但不排除一或更多其它特征、整数、步骤、操作、构件、组件及/或其族群的存在或增加。除非另有所示，陈述时，一值范围包含该范围的上下限及其间的任何子范围。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
以上所述是本公开的可选的实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (28)

  1. 一种链路释放信息传输方法，应用于第一终端，包括：
    接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
  2. 根据权利要求1所述的方法，其中，所述链路释放信息包括以下至少一项：
    第一信息，所述第一信息用于指示当前信息为链路释放信息；
    第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
    第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
    第一标识；
    第一组标识。
  3. 根据权利要求2所述的方法，其中，所述第一标识包括：
    所述第一终端的标识；和/或
    所述第二终端的标识。
  4. 根据权利要求2所述的方法，其中，所述第一组标识包括：
    所述第一终端所在的组的标识；和/或
    所述第二终端所在的组的标识。
  5. 根据权利要求1所述的方法，其中，在接收链路释放信息之后，还包括：
    当所述第一终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
    当所述第一终端为第一资源分配模式中的调度终端，则停止向所述第二终端分配链路资源；
    当所述第一终端为第一资源分配模式中的被调度终端，则停止接收所述第二终端分配的链路资源；
    其中，所述第一资源分配模式为终端调度终端的资源分配模式。
  6. 根据权利要求1所述的方法，还包括：
    当所述第一终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第二终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
  7. 根据权利要求6所述的方法，还包括：
    若未搜索到调度终端，则在停止接收所述第二终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
  8. 根据权利要求1所述的方法，其中，在接收链路释放信息之后，还包括：
    发送链路释放确认信息。
  9. 根据权利要求8所述的方法，其中，所述链路释放确认信息包括以下至少一项：
    第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
    第二标识；
    第二组标识。
  10. 根据权利要求9所述的方法，其中，所述第二标识包括：
    所述第一终端的标识；和/或
    所述第二终端的标识。
  11. 根据权利要求9所述的方法，其中，所述第二组标识包括：
    所述第一终端所在的组的标识；和/或
    所述第二终端所在的组的标识。
  12. 根据权利要求8所述的方法，其中，在发送链路释放确认信息之前，所述方法还包括：
    根据网络配置信息或预配置信息或链路释放信息，确定是否发送链路释放确认信息。
  13. 一种链路释放信息传输方法，应用于第二终端，包括：
    发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
  14. 根据权利要求13所述的方法，其中，所述链路释放信息包括以下至少一项：
    第一信息，所述第一信息用于指示当前信息为链路释放信息；
    第二信息，所述第二信息用于指示是否反馈链路释放确认信息；
    第三信息，所述第三信息用于指示反馈链路释放确认信息占用的资源；
    第一标识；
    第一组标识。
  15. 根据权利要求14所述的方法，其中，所述第一标识包括：
    所述第一终端的标识；和/或
    所述第二终端的标识。
  16. 根据权利要求14所述的方法，其中，所述第一组标识包括：
    所述第一终端所在的组的标识；和/或
    所述第二终端所在的组的标识。
  17. 根据权利要求13所述的方法，其中，在发送链路释放信息之后，还包括：
    当所述第二终端为侧行链路单播或组播场景中的接收终端或者发送终端，则释放所述第一终端与所述第二终端之间的链路连接、关联关系以及链路资源中的至少一项；
    当所述第二终端为第一资源分配模式中的调度终端，则停止向所述第一终端分配链路资源；
    当所述第二终端为第一资源分配模式中的被调度终端，则停止接收所述第一终端分配的链路资源；
    其中，所述第一资源分配模式为终端调度终端的资源分配模式。
  18. 根据权利要求14所述的方法，还包括：
    当所述第二终端为第一资源分配模式中的被调度终端，则搜索调度终端，并在停止接收所述第一终端分配的链路资源之后，通过搜索到的调度终端获取链路资源。
  19. 根据权利要求18所述的方法，还包括：
    若未搜索到调度终端，则在停止接收所述第一终端分配的链路资源之后，通过除所述第一资源分配模式之外的资源分配模式获取链路资源。
  20. 根据权利要求14所述的方法，其中，在发送链路释放信息之后，还 包括：
    接收链路释放确认信息。
  21. 根据权利要求20所述的方法，其中，所述链路释放确认信息包括以下至少一项：
    第四信息，所述第四信息用于指示当前信息为链路释放确认信息；
    第二标识；
    第二组标识。
  22. 根据权利要求21所述的方法，其中，所述第二标识包括：
    所述第一终端的标识；和/或
    所述第二终端的标识。
  23. 根据权利要求21所述的方法，其中，所述第二组标识包括：
    所述第一终端所在的组的标识；和/或
    所述第二终端所在的组的标识。
  24. 一种终端设备，所述终端设备为第一终端，包括收发器、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
    所述处理器用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
  25. 一种终端设备，所述终端设备为第二终端，包括收发器、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序；其中，
    所述处理器用于发送链路释放信息，所述链路释放信息用于释放第一终端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
  26. 一种链路释放信息传输装置，应用于第一终端，包括：
    接收模块，用于接收链路释放信息，所述链路释放信息用于指示释放所述第一终端与第二终端之间的链路，其中所述第二终端为所述链路释放信息的发送终端。
  27. 一种链路释放信息传输装置，应用于第二终端，包括：
    发送模块，用于发送链路释放信息，所述链路释放信息用于释放第一终 端与所述第二终端之间的链路，其中所述第一终端为所述链路释放信息的接收终端。
  28. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述程序被处理器执行时实现如权利要求1至12任一项所述的链路释放信息传输方法，或者实现如权利要求13至23任一项所述的链路释放信息传输方法中的步骤。
PCT/CN2020/070644 2019-02-02 2020-01-07 链路释放信息传输方法、装置及设备 WO2020156052A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910108017.1 2019-02-02
CN201910108017.1A CN111526501A (zh) 2019-02-02 2019-02-02 一种链路释放信息传输方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2020156052A1 true WO2020156052A1 (zh) 2020-08-06

Family

ID=71840811

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070644 WO2020156052A1 (zh) 2019-02-02 2020-01-07 链路释放信息传输方法、装置及设备

Country Status (2)

Country Link
CN (1) CN111526501A (zh)
WO (1) WO2020156052A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113873580A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 通信的方法和装置
KR20230112689A (ko) * 2021-03-05 2023-07-27 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx 타이머에 관련된 ue의 동작 방법
CN115669205A (zh) * 2022-08-17 2023-01-31 北京小米移动软件有限公司 连接释放方法、装置、存储介质及芯片

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105072563A (zh) * 2015-07-28 2015-11-18 北京博信视通科技有限公司 一种设备到设备通信的方法和装置
US20170339609A1 (en) * 2016-05-17 2017-11-23 Lg Electronics Inc. Method and apparatus for determining pdu session identity in wireless communication system
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法
CN108632743A (zh) * 2017-03-24 2018-10-09 上海诺基亚贝尔股份有限公司 通信方法、网络设备以及终端设备
CN109246659A (zh) * 2017-06-15 2019-01-18 中兴通讯股份有限公司 一种通信控制方法、装置及计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106604336B (zh) * 2011-09-29 2020-03-20 华为技术有限公司 通信模式切换的方法和装置
WO2014117369A1 (zh) * 2013-01-31 2014-08-07 富士通株式会社 通信方法、配置信息处理方法及其装置、通信系统
CN107771410B (zh) * 2015-05-26 2021-03-19 Lg 电子株式会社 在无线通信系统中通过ue实现的解除链接方法和使用所述方法的ue
WO2016190687A1 (ko) * 2015-05-26 2016-12-01 엘지전자 주식회사 무선 통신 시스템에서 단말에 의해 수행되는 링크 해제 방법 및 상기 방법을 이용하는 단말
KR102072588B1 (ko) * 2015-11-19 2020-02-03 엘지전자 주식회사 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치
CN105517191B (zh) * 2016-01-07 2019-04-12 宇龙计算机通信科技(深圳)有限公司 D2d中继通信中的连接管理方法及装置、终端和基站
CN107333334B (zh) * 2016-04-29 2020-01-31 普天信息技术有限公司 副链路半持续调度的配置方法和装置
CN108307472B (zh) * 2016-08-12 2023-06-30 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105072563A (zh) * 2015-07-28 2015-11-18 北京博信视通科技有限公司 一种设备到设备通信的方法和装置
US20170339609A1 (en) * 2016-05-17 2017-11-23 Lg Electronics Inc. Method and apparatus for determining pdu session identity in wireless communication system
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法
CN108632743A (zh) * 2017-03-24 2018-10-09 上海诺基亚贝尔股份有限公司 通信方法、网络设备以及终端设备
CN109246659A (zh) * 2017-06-15 2019-01-18 中兴通讯股份有限公司 一种通信控制方法、装置及计算机可读存储介质

Also Published As

Publication number Publication date
CN111526501A (zh) 2020-08-11

Similar Documents

Publication Publication Date Title
US20220150871A1 (en) Ue information reporting method, internet of vehicles resource configuration method, and apparatuses
CN109075919B (zh) 拆分承载双/多连接重传分集
US10785606B2 (en) Methods for handling quasi co-location (QCL) configuration for multicast transmissions
US11044055B2 (en) Methods of sharing HARQ process IDs between semi-persistent scheduling and dynamic grants
JP6564783B2 (ja) ユーザ装置、及び間欠受信方法
WO2020156052A1 (zh) 链路释放信息传输方法、装置及设备
WO2020063742A1 (zh) 终端直通通信的资源分配方法和装置
CN103238306A (zh) 支持从/向多个设备数据传输的设备到设备簇增强
JP2016502822A (ja) 無線通信における肯定応答タイミングの選択
WO2016202227A1 (zh) 一种层2链路标识的选择、通知方法及装置
WO2020248258A1 (zh) 无线通信方法、收端设备和发端设备
WO2021237721A1 (zh) Harq-ack码本的反馈方法和终端设备
WO2022213847A1 (zh) 一种处理资源重叠的方法及装置
US20240015755A1 (en) Cast type and coordination based inter-ue operation for nr sidelink
WO2020151407A1 (zh) 一种资源、载波重选方法及装置
US20210092716A1 (en) Acknowledgement information sending method, acknowledgement information receiving method, communications device, and network device
US12069614B2 (en) Sidelink configuration method and apparatus
TW201725930A (zh) 處理用於服務細胞的傳送／接收的裝置及方法
US12041635B2 (en) Method and apparatus for configuring transmission time interval, data transmission method and apparatus and system
WO2021004136A1 (zh) 组播反馈资源确定方法及装置、存储介质、用户设备
JP7241169B2 (ja) 端末、通信システム及び通信方法
JP7089592B2 (ja) 情報フィードバック方法及び装置、コンピュータ記憶媒体
KR20230088910A (ko) 정보 전송 처리 방법, 장치 및 단말
CN111294753B (zh) 用于v2x业务的资源分配方法、资源使用方法及装置、存储介质、终端、基站
WO2022021811A1 (zh) 无线通信方法、终端设备和网络设备

Legal Events

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

Ref document number: 20749175

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20749175

Country of ref document: EP

Kind code of ref document: A1