CN111526501A

CN111526501A - Link release information transmission method, device and equipment

Info

Publication number: CN111526501A
Application number: CN201910108017.1A
Authority: CN
Inventors: 王达; 赵亚利
Original assignee: Telecommunications Science and Technology Research Institute Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-02-02
Filing date: 2019-02-02
Publication date: 2020-08-11
Also published as: WO2020156052A1

Abstract

The invention provides a link release information transmission method, a device and equipment, and relates to the technical field of communication. The method is applied to a first terminal and comprises the following steps: and receiving link release information, wherein the link release information is used for indicating the release of a link between the first terminal and a second terminal, and the second terminal is a sending terminal of the link release information. The scheme of the invention can realize the timely release of the link between the terminals and avoid the waste of channel resources.

Description

Link release information transmission method, device and equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a device for transmitting link release information.

Background

In a conventional long Term evolution LTE (long Term evolution) system, services of a direct communication interface only support broadcast services, and for a new air interface nr (new radio), the services of the direct communication interface are richer than that of LTE, and besides the broadcast services, unicast and multicast services are also supported. In the LTE system, Mode3 and Mode4 are supported, Mode3 is a resource allocation Mode for network scheduling, Mode4 is a resource allocation Mode autonomously selected by the terminal, and NR subdivides the resource allocation Mode autonomously selected by the terminal (Mode2 in NR), where one subdivision Mode is Mode2d, that is, one user terminal UE (scheduling UE) schedules communication resources of other UEs (resource allocation Mode in which the terminal schedules other terminals). For both unicast and multicast services, association needs to be established between the UE for transceiving, and for Mode2d, association needs to be established between the scheduling UE and other scheduled UEs.

However, for unicast and multicast services, if the service is completed or a terminal leaves, and the established association is not released, the terminal may not know that the association has been disconnected, and continue to occupy channel resources to send information, thereby wasting channel resources. Similarly, for the Mode2d Mode, if the established association relationship between the scheduling terminal and the scheduled terminal is not released, if the service is completed (the scheduled terminal does not need to be scheduled with resources any more) or a terminal leaves, the terminal may not know that the association relationship has been disconnected, the scheduling terminal may continue to allocate resources, or the scheduled UE continues to apply for resources, which results in waste of channel resources.

Disclosure of Invention

The invention aims to provide a link release information transmission method, a device and equipment, which can realize the timely release of links between terminals and avoid the waste of channel resources.

To achieve the above object, an embodiment of the present invention provides a method for transmitting link release information, which is applied to a first terminal, and includes:

and receiving link release information, wherein the link release information is used for indicating the release of a link between the first terminal and a second terminal, and the second terminal is a sending terminal of the link release information.

Wherein the link release information comprises at least one of:

the first information is used for indicating that the current information is link release information;

second information, the second information being used for indicating whether to feed back link release acknowledgement information;

third information, the third information being used for indicating resources occupied by the feedback link release acknowledgement information;

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein, after receiving the link release information, the method further comprises:

when the first terminal is a receiving terminal or a sending terminal in a side link unicast or multicast scene, releasing at least one of link connection, association relationship and link resources between the first terminal and the second terminal;

when the first terminal is a scheduling terminal in a first resource allocation mode, stopping allocating link resources to the second terminal;

when the first terminal is a scheduled terminal in a first resource allocation mode, stopping receiving the link resource allocated by the second terminal;

the first resource allocation mode is a resource allocation mode of a terminal scheduling terminal.

Wherein the method further comprises:

and when the first terminal is the scheduled terminal in the first resource allocation mode, searching the scheduling terminal, and after stopping receiving the link resource allocated by the second terminal, acquiring the link resource through the searched scheduling terminal.

Wherein the method further comprises:

and if the scheduling terminal is not searched, after stopping receiving the link resource allocated by the second terminal, acquiring the link resource through a resource allocation mode except the first resource allocation mode.

and sending the link release confirmation information.

Wherein the link release confirmation information comprises at least one of:

fourth information, the fourth information being used to indicate that the current information is link release confirmation information;

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein, before sending the link release confirmation information, the method further comprises:

and determining whether to send link release confirmation information according to the network configuration information or the pre-configuration information or the link release information.

To achieve the above object, an embodiment of the present invention provides a method for transmitting link release information, which is applied to a second terminal, and includes:

and sending link release information, wherein the link release information is used for releasing a link between a first terminal and the second terminal, and the first terminal is a receiving terminal of the link release information.

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein, after the link release information is sent, the method further comprises:

when the second terminal is a receiving terminal or a sending terminal in a side link unicast or multicast scene, releasing at least one of link connection, association relationship and link resources between the first terminal and the second terminal;

when the second terminal is a scheduling terminal in a first resource allocation mode, stopping allocating link resources to the first terminal;

when the second terminal is a scheduled terminal in a first resource allocation mode, stopping receiving the link resource allocated by the first terminal;

Wherein the method further comprises:

and when the second terminal is the scheduled terminal in the first resource allocation mode, searching the scheduling terminal, and after stopping receiving the link resource allocated by the first terminal, acquiring the link resource through the searched scheduling terminal.

Wherein the method further comprises:

and if the scheduling terminal is not searched, after stopping receiving the link resource allocated by the first terminal, acquiring the link resource through a resource allocation mode except the first resource allocation mode.

link release confirmation information is received.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

In order to achieve the above object, an embodiment of the present invention provides a terminal device, where the terminal device is a first terminal, and includes a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor;

the processor is configured to receive link release information, where the link release information is used to instruct to release a link between the first terminal and a second terminal, and the second terminal is a sending terminal of the link release information.

In order to achieve the above object, an embodiment of the present invention provides a terminal device, which is a second terminal and includes a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor;

the processor is configured to send link release information, where the link release information is used to release a link between a first terminal and the second terminal, and the first terminal is a receiving terminal of the link release information.

To achieve the above object, an embodiment of the present invention provides a link release information transmission apparatus, applied to a first terminal, including:

a receiving module, configured to receive link release information, where the link release information is used to instruct to release a link between the first terminal and a second terminal, and the second terminal is a sending terminal of the link release information.

To achieve the above object, an embodiment of the present invention provides a link release information transmission apparatus, applied to a second terminal, including:

a sending module, configured to send link release information, where the link release information is used to release a link between a first terminal and a second terminal, and the first terminal is a receiving terminal of the link release information.

To achieve the above object, an embodiment of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a link release information transmission method as applied to a first terminal or implements steps in a link release information transmission method as applied to a second terminal.

The technical scheme of the invention has the following beneficial effects:

the link release information transmission method of the embodiment of the invention can receive the link release information, and the link release information is used for indicating the release of the link between the first terminal (namely the receiving terminal of the link release information) and the second terminal (namely the sending terminal of the link release information), so that the first terminal can release the link between the first terminal and the second terminal in time based on the link release information, and the waste of channel resources is avoided.

Drawings

FIG. 1 is a schematic view of V2X communication;

fig. 2 is a flowchart illustrating a link release information transmission method applied to a first terminal according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an application of scenario one;

FIG. 4 is a schematic diagram of an application of scenario two;

FIG. 5 is a schematic diagram of an application of scenario three;

FIG. 6 is an application diagram of scenario four;

fig. 7 is a flowchart illustrating a link release information transmission method applied to a second terminal according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.

Fig. 1 is a schematic diagram of Vehicle-to-all V2X (Vehicle to event) communication in the prior art. Device-to-device allows direct communication between devices, such as UE1 and UE 2. For convenience of description, a Sidelink communication link between a device and a device is defined as a Sidelink link, and a corresponding wireless interface of the Sidelink link is called a direct communication interface (also called a Sidelink interface); the cellular communication link between the network (base station eNodeB) and the direct communication device is called Uulink and its corresponding interface is called Uu interface.

Typical direct communication scenarios include the following three: one-to-one communication (unicast) between direct communication terminals; a device can send the same data to all devices in a communication group at a time (multicast); one device can send the same data (broadcast) to all nearby devices at once.

As shown in fig. 2, a method for transmitting link release information according to an embodiment of the present invention is applied to a first terminal, and includes:

step 201, receiving link release information, where the link release information is used to indicate to release a link between the first terminal and a second terminal, where the second terminal is a sending terminal of the link release information.

According to the step 201, the first terminal can receive the link release information, and the link release information is used to instruct to release the link between the first terminal and the second terminal (i.e. the sending terminal of the link release information), so that the first terminal can timely release the link with the second terminal based on the link release information, thereby avoiding the waste of channel resources.

The embodiment of the invention is mainly directed to a unicast and multicast scenario in an NR V2X system, and a first resource allocation Mode (Mode2d Mode, resource allocation Mode of a terminal scheduling terminal (other terminal)). For a unicast scene, the first terminal may be a sending terminal of a unicast service, and the second terminal is a receiving terminal of the unicast service, or the first terminal is a receiving terminal of the unicast service, and the second terminal is a sending terminal of the unicast service; for a multicast scenario, the first terminal may be a sending terminal of a multicast service, and the second terminal is a receiving terminal of the multicast service, or the first terminal is a receiving terminal of the multicast service, and the second terminal is a 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.

Optionally, the link release information includes at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Here, if the link release information includes the first information, the purpose of informing the first terminal that the received information is the link release information is achieved. Of course, the first information may explicitly exist in the link release information, or may exist in other implicit manners, such as scrambling code as the link release information, or, in addition to carrying the first information, the link release information may also achieve the purpose through itself, for example, the link release information is sent by occupying a configured or preconfigured specific resource, and at this time, the link release information may also not include the first information.

And if the link release information comprises the second information, the purpose of informing the first terminal of feeding back the link confirmation information after receiving the link release information is realized. Of course, the second information may exist in other implicit manners besides explicitly existing in the link release information, such as scrambling code as the link release information. Alternatively, the link confirmation information may be fed back by network configuration, or pre-configuration, or by group header (group manager) configuration, and in this case, the link release information may not include the second information.

And if the link release information comprises third information, informing the first terminal of feeding back the resources occupied by the link confirmation information. Of course, the resource occupied by the feedback link confirmation information may also be implemented in a network configuration, or a pre-configuration, and the like, and in this case, the link release information may also not include the third information.

If the link release information comprises the first identification, the confirmation of the first terminal to the link release target terminal is realized, namely the first terminal judges whether the first terminal is a target receiving terminal of the link release information or not and/or determines a transmitting terminal of the link release information according to the terminal identification included in the link release information. Of course, the first identifier may also exist in other implicit manners besides explicitly existing in the link release information, such as scrambling code as the link release information, and at this time, the link release information may also not include the first identifier.

And if the link release information comprises the first group identification, confirming the target terminal group of the link release by the first terminal in the multicast scene. For example, the first terminal is a service data receiving terminal in a multicast scenario, and after receiving the link release information, the first terminal may release a connection with a service data sending terminal in a group corresponding to the first group identifier based on the first group identifier. Of course, the first group identifier may exist in other implicit manners besides explicitly existing in the link release information, such as scrambling code as the link release information, and at this time, the link release information may not include the first group identifier.

In this embodiment, the link release information may be sent by using radio resource Control rrc (radio resource Control) signaling, or by using sidelink Control information sci (sidelink Control information), or by using sidelink Feedback Control information sfci (sidelink Feedback Control information).

Specifically, the link release information is sent by using an RRC signaling, where the RRC signaling includes at least one of the following:

1) indicating a link release information field (i.e., first information), for example, using BOOLEAN type or ENUMERATED type:

a BOOLEAN type (true or false), wherein when the domain value of the link release information is true, the RRC signaling contains link release information;

and when the domain value of the link release information is release in the enumeration type, indicating that the RRC signaling contains the link release information.

2) A terminal ID or a group ID (i.e., a first identity or a first group identity), wherein the terminal ID includes at least one of a receiving terminal ID, a transmitting terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, a scheduling terminal ID and/or a scheduled terminal ID are included. If the RRC signaling is scrambled using the terminal ID or the group ID, there is no need to include the terminal ID or the group ID in the RRC signaling.

3) Whether to send the feedback link release confirmation information (i.e., the second information) is indicated, such as whether to send the feedback link release confirmation information by the first terminal. If the sending of the feedback link release confirmation information is indicated by network configuration, or pre-configuration, or by group head (group manager) configuration, etc., the indication of sending the feedback link release confirmation information is not required to be included in the RRC signaling.

4) The resource (i.e., the third information) used for transmitting the link release confirmation signal is indicated, such as SFCI resource or SCI resource used for transmitting the link release confirmation signal. If the SCI sending the RRC signaling indicates the resource used for sending the link release confirmation signal, the RRC signaling does not need to include the resource occupied by the link release confirmation signal.

Or, the link release information is sent by using sidelink control information SCI, wherein the SCI includes at least one of the following:

1) the SCI type field (i.e., the first information) indicates that the SCI is link release information, for example, 1 bit, and if the 1 bit is 1, the SCI is link release information.

2) A terminal ID (identification) or a group ID (i.e. a first identity or a first group identity), wherein the terminal ID includes at least one of a receiving terminal ID, a sending terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, the terminal ID includes a scheduling terminal ID and/or a scheduled terminal ID. If the SCI is scrambled using a terminal ID or a group ID, there is no need to include the terminal ID or the group ID in the SCI.

3) Whether to send the feedback link release confirmation information (i.e., the second information) is indicated, such as whether to send the feedback link release confirmation information by the first terminal. If the sending of the feedback link release confirmation information is indicated by network configuration, or pre-configuration, or by group head (group manager) configuration, etc., the SCI does not need to include the indication of sending the feedback link release confirmation information.

4) The resource (i.e., the third information) used for transmitting the link release confirmation information is indicated, such as SFCI resource or SCI resource used for transmitting the link release confirmation information, etc. If the resource used for sending the link release confirmation signal is configured through network configuration, or pre-configuration, etc., the SCI does not need to include the resource occupied by the link release confirmation signal.

Or, the side link feedback control information SFCI is adopted to send the link release information, where the SFCI may be:

mode 1: the sequence is used for representing that the SFCI is link release information, the sequence is orthogonal to a hybrid Automatic Repeat request (HARQ) (hybrid Automatic Repeat request) sequence transmitted on the SFCI, and/or a sidelink Service Request (SR) (service request) sequence transmitted on the SFCI, and the sequence can be configured on the network side, or specified by a standard, or preconfigured. Further, the sequence is related to a terminal ID that sends the link release information, or a terminal ID that receives the link release information, or a terminal group ID, for example, a generation factor that generates the sequence includes the terminal ID or the terminal group ID, and is used to solve a collision problem caused by transmission signals of other terminals on the resource, so that the receiving end determines a link release target terminal or a target terminal group.

Mode 2: including at least one of:

1) the SFCI type field (i.e., the first information) indicates that the SFCI is the link release information, for example, 1 bit, and when the 1 bit is 1, indicates that the SFCI is the link release information.

2) A terminal ID or a group ID (i.e., a first identity or a first group identity), wherein the terminal ID includes at least one of a receiving terminal ID, a transmitting terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, the terminal ID includes a scheduling terminal ID and/or a scheduled terminal ID. If the SFCI is scrambled using the terminal ID or the group ID, the terminal ID and the group ID need not be included in the SFCI. Or, if the resource for sending the link release information SFCI is agreed between the terminals, the terminal ID or the group ID is not needed, or only the ID or the group ID of one of the terminals may be transmitted for solving the collision problem caused by the transmission signals of the other terminals on the resource, so that the receiving end determines the link release target terminal or the target terminal group.

4) The resource (i.e., the third information) used for transmitting the link release confirmation signal is indicated, for example, SFCI resource or SCI resource used for transmitting the link release confirmation signal is indicated, and so on. If the resources used for sending the link release confirmation signal are configured through network configuration, pre-configuration or the like, the SFCI does not need to include the resources occupied by the link release confirmation signal.

It should be noted that, in this embodiment, for different scenarios, different link release manners between terminals are executed, and different link release manners are often performed based on the application scenario and the type of the first terminal, so optionally, after receiving the link release information, the method further includes:

the first resource allocation Mode is a resource allocation Mode in which the terminal schedules the terminal, that is, a Mode2d resource allocation Mode scenario.

In addition, considering the Mode2d scenario, after the link is released, the scheduled terminal still has a condition that the service data needs to be sent, optionally, the method further includes:

Therefore, after the link is released, the scheduled terminal still has a condition that the service data needs to be sent, and the scheduled terminal is searched before stopping receiving the link resource allocated by the second terminal, so that the link resource is obtained through the searched scheduled terminal after stopping receiving the link resource allocated by the second terminal. In this case, the searching scheduling terminal may also search for the second terminal, so it is preferable that after stopping receiving the link resource allocated by the second terminal, the link resource is acquired by the other searched scheduling terminals (i.e. scheduling terminals other than the second terminal). Of course, the step of searching for the scheduling terminal may be before or after the step of receiving the link release information, and if the scheduled terminal has no service to transmit, the scheduled terminal does not need to search for other available scheduling terminals or obtain the link resource through the searched scheduling terminal until the scheduled terminal has a service to transmit and then search or obtain the link resource through the searched scheduling terminal.

However, the scheduled terminal may not search for other scheduling terminals, and therefore, the method further includes:

Here, considering that the link of the second terminal needs to be released, it is preferable that, in the case where no other scheduling terminal (i.e., a scheduling terminal other than the second terminal) is searched, the link resource is acquired through a resource allocation pattern other than the first resource allocation pattern after stopping receiving the link resource allocated by the second terminal. Besides the Mode2d Mode, the resource allocation Mode may be a network scheduled resource allocation Mode1, a terminal self-selected resource allocation Mode2a, or a terminal resource allocation Mode2c authorized based on network configuration.

It should also be appreciated that, in the embodiment of the present invention, the network configuration information or the pre-configuration information or the link release information configures whether the first terminal sends/feeds back the link release confirmation information after receiving the link release information. Therefore, after receiving the link release information, the method further includes:

and sending the link release confirmation information.

Thus, after receiving the link release information, the first terminal sends the link release confirmation information to inform the second terminal that the first terminal successfully receives the link release information.

Optionally, the link release confirmation information includes at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Here, if the link release confirmation information includes the fourth information, the purpose of informing that the information received by the second terminal is the link release confirmation information is achieved. Of course, the fourth information may also exist in other implicit manners besides explicitly existing in the link release confirmation information, such as scrambling code used as the link release confirmation information, or the link release confirmation information may also achieve the purpose by itself except carrying the fourth information, for example, the link release confirmation information is sent by occupying a configured or preconfigured specific resource, and at this time, the link release confirmation information may also not include the fourth information.

If the link release confirmation information comprises the second identification, the confirmation of the second terminal to the link release target terminal is realized, namely the second terminal judges whether the second terminal is the target receiving terminal of the link release confirmation information or not and/or determines the sending terminal of the link release confirmation information according to the terminal identification included in the link release confirmation information. Of course, the second identifier may also exist in other implicit manners besides explicitly existing in the link release confirmation information, such as scrambling code as the link release confirmation information, and at this time, the link release confirmation information may also not include the second identifier.

And if the link release confirmation information comprises the second group identification, the confirmation of the second terminal to the link release target terminal group in the multicast scene is realized. For example, the second terminal is a service data sending terminal in a multicast scenario, and after receiving the link release confirmation information, the second terminal may learn, based on the second group identifier, that the service data receiving terminal in the group corresponding to the second group identifier has received the link release information. Of course, the second group identifier may exist in other implicit manners besides explicitly existing in the link release confirmation information, such as scrambling code as the link release confirmation information, and at this time, the link release confirmation information may also not include the second group identifier.

In this embodiment, the link release confirmation message may be sent using RRC signaling, or may be sent using SCI, or may be sent using SFCI.

Specifically, the link release acknowledgement information is sent by using an RRC signaling, where the RRC signaling includes at least one of the following:

1) indicating a link release acknowledgement information field (i.e. fourth information), for example, using a bolean type or an estimated type:

a BOOLEAN type (true or false), wherein when the domain value of the link release confirmation information is true, the RRC signaling contains the link release confirmation information;

and an estimated type, wherein when the domain value of the link release acknowledgement information is ACK in the enumeration type, the RRC signaling indicates that the RRC signaling includes the link release acknowledgement information.

2) A terminal ID or a group ID (i.e., a second identifier or a second group identifier), wherein the terminal ID includes at least one of a receiving terminal ID, a transmitting terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, a scheduling terminal ID and/or a scheduled terminal ID are included. If the RRC signaling is scrambled using the terminal ID or the group ID, there is no need to include the terminal ID or the group ID in the RRC signaling.

Or, sending link release confirmation information by using SCI, wherein the SCI comprises at least one of the following items:

1) the SCI type field (i.e., the fourth information) indicates that the SCI is the link release acknowledgement information, for example, 1 bit, and if the 1 bit is 1, the SCI is the link release acknowledgement information.

2) A terminal ID or a group ID (i.e., a second identity or a second group identity), wherein the terminal ID includes at least one of a receiving terminal ID, a transmitting terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, the terminal ID includes a scheduling terminal ID and/or a scheduled terminal ID. If the SCI is scrambled using a terminal ID or a group ID, there is no need to include the terminal ID or the group ID in the SCI.

Or, the SFCI is adopted to send the link release acknowledgement information, where the SFCI may be:

mode 1: if the link release information indicates the resource location of the link release confirmation information, for example, the SFCI resource location of the link release confirmation information is indicated by the SCI of the link release information, the link release confirmation information is sent by occupying the indicated SFCI resource location, similar to the HARQ feedback sending method of unicast and multicast services, and the link release confirmation information may be sequence or bit information for indicating the receiving condition of the link release information, for example, ACK (correct reception confirmation) or NACK (wrong reception confirmation, which requires retransmission of the link release information).

Mode 2: and indicating the SFCI as the link release confirmation information by adopting a sequence, wherein the sequence is orthogonal to the HARQ sequence transmitted on the SFCI and/or the SR sequence transmitted on the SFCI, and the sequence can be configured on the network side, or specified by a standard, or preconfigured. Further, the sequence is related to the terminal ID that sends the link release confirmation information, or the terminal ID that receives the link release information, or the terminal group ID, and is used to solve the problem of collision caused by transmission signals of other terminals on the resource, so that the receiving end determines the link release target terminal or the target terminal group.

Mode 3: including at least one of:

1) the SFCI type field (i.e., the fourth information) indicates that the SFCI is the link release acknowledgement information, for example, 1 bit, and when the 1 bit is 1, indicates that the SFCI is the link release acknowledgement information.

2) A terminal ID or a group ID (i.e., a second identity or a second group identity), wherein the terminal ID includes at least one of a receiving terminal ID, a transmitting terminal ID, and a group ID for a unicast or multicast scenario; for the Mode2d scenario, the terminal ID includes a scheduling terminal ID and/or a scheduled terminal ID. If the SFCI is scrambled using the terminal ID or the group ID, the terminal ID and the group ID need not be included in the SFCI. Or, if the resource for sending the link release acknowledgment information SFCI is agreed between the terminals, the terminal ID or the group ID is not needed, or only the ID or the group ID of one of the terminals may be transmitted for solving the collision problem caused by the transmission signals of the other terminals on the resource, so that the receiving end determines the link release target terminal or the target terminal group.

In this embodiment, based on whether the link release confirmation information is sent, optionally, before sending the link release confirmation information, the method further includes:

Thus, the network configuration information or the pre-configuration information can be used for confirming the sending of the link release confirmation information based on the configuration, or the link release confirmation information can be sent after the sending of the link release confirmation information is confirmed based on the link release information.

The application of the link release information transmission method according to the embodiment of the present invention will be described below with respect to different scenarios by taking an NR direct connection system as an example:

scenario one, unicast scenario, as shown in fig. 3:

s301, the terminal B sends link release information to the terminal A; the terminal b may obtain the link resource by using the mode1 or the terminal-selected resource allocation mode2, and send the link release information to the terminal a, or may send the link release information to the terminal a by forwarding the link release information through the base station.

The specific link release information design method is as above, and is not described herein again. The transmission of the link release information may be implemented by RRC signaling, SCI, or SFCI. The SFCI may be transmitted using the mode1, the mode2, or the base station forwarding method, or may be transmitted using SFCI resources defined between the transmitting and receiving terminals. Or transmitting SCI and SFCI, wherein the SCI is used for indicating the resource position of the SFCI, and the SFCI is used for carrying the link release information.

S302, after receiving the link release information sent by the terminal B, the terminal A sends link release confirmation information to the terminal B if the link release confirmation information is confirmed to be sent based on the indication whether the link release confirmation information is sent in the network configuration information or the pre-configuration information or the link release information; the terminal a may obtain link resources in a mode1 or a mode2, and send link release confirmation information to the terminal b, or may send link release confirmation information to the terminal b by forwarding the link release confirmation information through the base station. And if the network configuration information or the pre-configuration information or the link release information indicates the resource for sending the link release confirmation information, sending the link release confirmation information through the resource indicated by the network configuration information or the pre-configuration information or the link release information. Specifically, the network configuration is a broadcast signaling configuration. Besides the link release information, other information can also complete the configuration of whether the link release confirmation signal is sent or not between the terminals.

And, if the network configuration information or the pre-configuration information or the link release information configures the sending link release confirmation information, the terminal b needs to receive the link release confirmation information (such as ACK) sent by the terminal a, and can release the link connection, association relationship and/or link resources with the terminal a. 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. If the link release confirmation information is retransmitted for N times, the link connection, the association relation and/or the link resource with the terminal A are/is released if the link release confirmation information is still not received or the received link release confirmation information is NACK, and at this time, the link condition between the terminal B and the terminal A is far or poor, wherein N is an integer greater than or equal to 1 and can be configured or preconfigured or specified by a standard. Another implementation method is that the terminal b waits for a period of time for a timer T after sending the link release information, and if no link release confirmation information is received in the timer T, that is, the timer T times out, the link connection, association, and/or link resources with the terminal a are released (or when receiving the link release confirmation information as NACK, the terminal b may retransmit the link release information, and retransmit the link release information each time, and reset the timer T), where the timer T may be configured or preconfigured or specified by a standard.

In addition, the specific link release confirmation information is designed as described above, and is not described herein again. The sending of the link release confirmation information may be implemented by RRC signaling, SCI, or SFCI. Wherein, the sending SFCI may use the mode1, the mode2, or the mode of forwarding by the base station, and may also send the SFCI through the SFCI resources appointed between the transmitting and receiving terminals; or transmitting SCI and SFCI, wherein the SCI is used for indicating the resource position of the SFCI, and the SFCI is used for carrying the link release confirmation information.

Of course, if the network configuration information or the pre-configuration information or the link release information indicates not to send the link release confirmation information, the link release confirmation signal does not need to be sent to the second terminal.

S303, the terminal A releases link connection, association relation and/or link resource and the like with the terminal B; for example, the stored terminal b ID, or the sidelink RRC configuration related to the terminal b, or the information such as the signaling Radio bearer srb (signaling Radio bearer), or the data Radio bearer drb (data Radio bearer) is released, and/or the Semi-Persistent Scheduling SPS (Semi-Persistent Scheduling) resource (resource for transmitting or receiving SPS service), the SPS process, the HARQ process, and the like reserved for the unicast service with the terminal b is released, and/or the buffer for the unicast service with the terminal b is emptied.

S304, after the terminal B sends the link release information, or after the terminal B receives the link release confirmation information sent by the terminal A, the terminal B releases the link connection, the association relation and/or the link resources and the like between the terminal B and the terminal A; for example, the stored terminal a ID, or RRC configuration related to the terminal a, or SRB, or DRB, etc. information is released, and/or SPS resources (resources for transmitting or receiving SPS services), SPS processes, HARQ processes, etc. reserved for unicast services with the terminal a are released, and/or a buffer for unicast services with the terminal a is cleared.

Scenario two, multicast scenario (transmitting terminal sends multicast signal to multiple receiving terminals)

In the multicast scenario, if the receiving terminal of the link release information is the sending terminal of the multicast service and the sending terminal of the link release information is the receiving terminal of the multicast service, the same procedure as the unicast procedure in the scenario above is not repeated here. Only when releasing the link, it is necessary to release the stored ID of the opposite terminal, or RRC configuration related to the multicast service, or SRB, or DRB, and/or to release SPS resources (resources for transmitting or receiving SPS services), SPS processes, HARQ processes, and the like reserved for the multicast service, and/or to clear buffers related to the multicast service.

In a multicast scenario, if a receiving terminal of the link release information is a receiving terminal of a multicast service and a sending terminal of the link release information is a sending terminal of the multicast service, as shown in fig. 4:

s401, the terminal B sends link release information to the terminal A1 and the terminal A2; the link release information is a multicast signal, where the terminal b may obtain link resources by using a mode1 or a mode2, and send the link release information to the terminals a 1 and a 2, or may send the link release information to the terminals a 1 and a 2 by forwarding the link release information through the base station.

The specific link release information design method is as above, and is not described herein again. The transmission of the link release information may be implemented by RRC signaling, SCI, or SFCI. The SFCI may be transmitted using the mode1, the mode2, or the base station forwarding method, or may be transmitted using SFCI resources defined between the transmitting and receiving terminals. Or transmitting SCI and SFCI, wherein the SCI is used for indicating the resource position of the SFCI, and the SFCI is used for carrying the link release information. At this time, the link release information includes the group ID.

S402, after receiving the link release information sent by the terminal B, the terminal A1/the terminal A2 sends the link release confirmation information to the terminal B if the link release confirmation information is confirmed to be sent based on the indication whether the link release confirmation information is sent in the network configuration information or the pre-configuration information or the link release information; the terminal a 1/the terminal a 2 may obtain link resources in a mode of mode1 or a mode of mode2, and send link release confirmation information to the terminal b, or may send the link release confirmation information to the terminal b in a manner of forwarding the link release confirmation information by the base station. And if the network configuration information or the pre-configuration information or the link release information indicates the resource for sending the link release confirmation information, sending the link release confirmation information through the resource indicated by the network configuration information or the pre-configuration information or the link release information. Specifically, the network configuration is a broadcast signaling configuration. Besides the link release information, other information can also complete the configuration of whether the link release confirmation signal is sent or not between the terminals.

And, if the network configuration information or the pre-configuration information or the link release information configures the sending link release confirmation information, the terminal b needs to receive the link release confirmation information (e.g. ACK) sent by the terminal a 1/the terminal a 2 (all receiving terminals of the link release information), so as to release the link connection, association relationship and/or link resources of the multicast service between the terminal a 1/the terminal a 2. If at least one receiving terminal of the link release information exists, the link release confirmation information sent by the receiving terminal is not received by the terminal B or the received link release confirmation information is NACK, the link release information needs to be retransmitted. If the link release information is retransmitted for N times, if the link release confirmation information is still not received or the received link release confirmation information is NACK, link connection, association relation and/or link resources of the multicast service between the terminal A1 and the terminal A2 are released, and at this time, the link condition of the multicast service between the terminal B and the terminal A1 and the terminal A2 is far or poor, wherein N is an integer greater than or equal to 1, and the link release condition can be configured or preconfigured through a network or specified by a standard. Another implementation method is that the terminal b waits for a period of time for a timer T after sending the link release information, and if no link release confirmation information is received in the timer T, that is, the timer T times out, the link connection, association, and/or link resources of the multicast service between the terminal a 1 and the terminal a 2 are released (or when receiving the link release confirmation information as NACK, the link release information may be retransmitted, and the timer T is reset every time the link release information is retransmitted), where the timer T may be configured or preconfigured or specified by a standard.

S403, the terminal A1/the terminal A2 release link connection, association relation and/or link resources and the like with the terminal B; for example, the stored terminal b ID, or the sidelink RRC configuration related to the terminal b, or the SRB, or the DRB, etc. information is released, and/or SPS resources (resources for transmitting or receiving SPS services), SPS processes, HARQ processes, etc. reserved for the multicast service with the terminal b are released, and/or a buffer for the multicast service with the second terminal is cleared, etc.

S404, after the terminal B sends the link release information, or after the terminal B receives the link release confirmation information sent by the terminal A1/the terminal A2, the terminal B releases the link connection, the association relation and/or the link resources and the like between the terminal A1 and the terminal A2; for example, the stored information of the terminal a 1ID, the terminal a 2ID, or the RRC configuration related to the terminal a 1, or the information of the SRB, or the DRB, etc., the information of the RRC configuration related to the terminal a 2, or the information of the SRB, or the DRB, etc., is released, and/or the SPS resources (resources for transmitting or receiving the SPS service), the SPS process, the HARQ process, etc., reserved for the multicast service with the terminal a 1 and the terminal a 2 are released, and/or the buffer for the multicast service with the terminal a 1 and the terminal a 2 is emptied.

Scenario three, Mode2d scenario, where terminal a is a scheduling terminal and terminal b is a scheduled terminal, as shown in fig. 5:

s501, the scheduled terminal sends link release information to the scheduling terminal; the scheduled terminal may obtain the link resource in a mode1 or a mode2 mode and send the link release information to the scheduling terminal, or may send the link release information to the scheduling terminal by forwarding the link release information through the base station.

If the link release confirmation information is confirmed to be sent based on the indication of whether the link release confirmation information is sent in the network configuration information, the pre-configuration information, or the link release information, the scheduling terminal receives the link release information and then sends the link release confirmation information to the scheduled terminal, as shown in step S501a in fig. 5.

S502, 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 information such as the ID of the scheduled terminal, RRC configuration related to the scheduled terminal, SRB, or DRB, and stops allocating resources to the scheduled terminal. And the scheduled terminal can stop receiving the resource allocated by the scheduling terminal after transmitting the link release information.

S503, if the scheduled terminal still has the service to send, the scheduled terminal searches for other available scheduling terminals around the scheduled terminal.

If the scheduled terminal has no service to send, the scheduled terminal does not need to search other available scheduling terminals or obtain link resources through the searched scheduling terminals until the scheduled terminal has the service to send and then search or obtain the link resources through the searched scheduling terminals. And if the scheduled terminal searches other available scheduling terminals around and the scheduled terminal has service to transmit, selecting other scheduling terminals to apply for resources. If the scheduled terminal does not search other available scheduling terminals in the surrounding, other resource allocation modes are entered, such as Mode1, or Mode2a, or Mode2 c.

The scheduled terminal may send the link release information first, and then search for other available scheduling terminals around; or the scheduled terminal can search other available scheduling terminals around first and then send the link release information; or both may be performed simultaneously. That is, the scheduled terminal can continuously search other available scheduling terminals around all the time, and has no relation with whether the link release information is sent or not, so that the scheduled terminal can be quickly switched to other scheduling terminals to apply for resources after the link release information is sent.

Scenario four, Mode2d scenario, where terminal a is a scheduled terminal and terminal b is a scheduling terminal, as shown in fig. 6:

s601, the scheduling terminal sends link release information to the scheduled terminal; the scheduling terminal may obtain link resources in a mode1 or a mode2 mode, and send link release information to the scheduled terminal, or may send link release information to the scheduled terminal by forwarding the link release information through the base station.

If the transmission of the link release confirmation information is confirmed based on the indication of whether to send the link release confirmation information in the network configuration information, the pre-configuration information, or the link release information, the scheduled terminal receives the link release information and then sends the link release confirmation information to the scheduling terminal, as shown in step S601a in fig. 6.

S602, the scheduling terminal stops allocating resources to the scheduled terminal; for example, the scheduling terminal releases information such as the ID of the scheduled terminal, RRC configuration related to the scheduled terminal, SRB, or DRB, and stops allocating resources to the scheduled terminal.

S603, after the scheduled terminal receives the link release information sent by the scheduling terminal, the scheduled terminal stops receiving the resource allocated by the scheduling terminal; for example, the scheduled terminal releases the information of the scheduling terminal ID, RRC configuration related to the scheduling terminal, or SRB, or DRB, and stops receiving the resource allocated by the scheduling terminal.

S604, if the scheduled terminal still has the service to send, the scheduled terminal searches other available scheduling terminals around.

The scheduled terminal may search other available scheduling terminals around before or after receiving the link release information, that is, the scheduled terminal may continuously search other available scheduling terminals around, regardless of whether the link release information is received, so that after receiving the link release information, the scheduled terminal may quickly switch to the other scheduling terminals to apply for resources.

In summary, the link release information transmission method according to the embodiment of the present invention can receive the link release information, where the link release information is used to indicate to release the link between the first terminal and the second terminal (i.e., the sending terminal of the link release information), and the first terminal can timely release the link with the second terminal based on the link release information, thereby avoiding channel resource waste.

As shown in fig. 7, an embodiment of the present invention provides a link release information transmission method, which is applied to a second terminal, and includes:

step 701, sending link release information, where the link release information is used to release a link between a first terminal and a 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 for indicating to release a link between the first terminal and the second terminal (namely, a sending terminal of the link release information), so that the first terminal can timely release the link between the first terminal and the second terminal based on the link release information after receiving the link release information sent by the second terminal, and the waste of channel resources is avoided.

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the method further comprises:

link release confirmation information is received.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

It should be noted that, the method is applied to the second terminal, and is used for realizing the transmission of the link release information in cooperation with the above-mentioned link release information transmission method applied to the first terminal, and the implementation manner of the embodiment of the link release information transmission method applied to the first terminal is applicable to the method, and can also achieve the same technical effect.

As shown in fig. 8, an embodiment of the present invention provides a terminal device, where the terminal device is a first terminal, and the terminal device includes: a transceiver 820, a memory 830, a processor 810, and a computer program stored on the memory 830 and executable 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 a link between the first terminal and a second terminal, where the second terminal is a sending terminal of the link release information.

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the processor is further configured to:

Wherein the transceiver is further configured to:

and sending the link release confirmation information.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the processor is further configured to:

In addition, as shown in fig. 8, an embodiment of the present invention provides a terminal device, where the terminal device is a second terminal, and the terminal device includes a transceiver 820, a memory 830, a processor 810, and a computer program stored in the memory 830 and operable on the processor 810;

the processor 810 is configured to 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.

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the processor is configured to:

Wherein the processor is further configured to:

Wherein the transceiver is further configured to:

link release confirmation information is received.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 810, and various circuits, represented by memory 830, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 820 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 840 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 810 is responsible for managing the bus architecture and general processing, and the memory 830 may store data used by the processor 810 in performing operations.

The embodiment of the present invention further provides a link release information transmission apparatus, applied to a first terminal, including:

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the apparatus further comprises:

a first release processing module, configured to release at least one of a link connection, an association relationship, and a link resource between the first terminal and the second terminal when the first terminal is a receiving terminal or a sending terminal in a sidelink unicast or multicast scenario;

Wherein the apparatus further comprises:

and the first processing module is used for searching the scheduling terminal when the first terminal is the scheduled terminal in the first resource allocation mode, and acquiring the link resource through the searched scheduling terminal after stopping receiving the link resource allocated by the second terminal.

Wherein the apparatus further comprises:

and the second processing module is used for acquiring the link resources through a resource allocation mode except the first resource allocation mode after stopping receiving the link resources allocated by the second terminal if the scheduling terminal is not searched.

Wherein the apparatus further comprises:

and the confirmation information sending module is used for sending the link release confirmation information.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the apparatus further comprises:

and the confirmation module is used for determining whether to send the link release confirmation information according to the network configuration information or the pre-configuration information or the link release information.

The device can receive the link release information, the link release information is used for indicating the release of the link between the first terminal and the second terminal (namely the sending terminal of the link release information), and the link between the first terminal and the second terminal can be released in time based on the link release information, so that the waste of channel resources is avoided.

It should be noted that, the apparatus is an apparatus to which the above-mentioned link release information transmission method applied to the first terminal is applied, and the implementation manner of the above-mentioned link release information transmission method applied to the first terminal is applied to the apparatus, and the same technical effect can be achieved.

An embodiment of the present invention provides a link release information transmission apparatus, applied to a second terminal, including:

Wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

Wherein the first identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the first group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

Wherein the apparatus further comprises:

a second release processing module, configured to release at least one of a link connection, an association relationship, and a link resource 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;

Wherein the apparatus further comprises:

and the third processing module is used for searching the scheduling terminal when the second terminal is the scheduled terminal in the first resource allocation mode, and acquiring the link resource through the searched scheduling terminal after stopping receiving the link resource allocated by the first terminal.

Wherein the apparatus further comprises:

and the fourth processing module is configured to, if the scheduling terminal is not searched, obtain the link resource in a resource allocation mode other than the first resource allocation mode after stopping receiving the link resource allocated by the first terminal.

Wherein the apparatus further comprises:

and the confirmation information receiving module is used for receiving the link release confirmation information.

Wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

Wherein the second identifier comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

Wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

The device can send link release information, and the link release information is used for indicating the release of the link between the first terminal and the second terminal (namely the sending terminal of the link release information), so that the link between the first terminal and the second terminal can be released in time based on the link release information after the first terminal receives the link release information sent by the second terminal, and the waste of channel resources is avoided.

It should be noted that, the apparatus is an apparatus to which the above-mentioned link release information transmission method applied to the second terminal is applied, and the implementation manner of the above-mentioned link release information transmission method applied to the second terminal is applied to the apparatus, and the same technical effect can be achieved.

An embodiment of the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a link release information transmission method as applied to a first terminal as above, or implements steps in a link release information transmission method as applied to a second terminal as above.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It is further noted that the terminals described in this specification include, but are not limited to, smart phones, tablets, etc., and that many of the functional components described are referred to as modules in order to more particularly emphasize their implementation independence.

In embodiments of the present invention, modules may be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be constructed as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different bits which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Likewise, operational data may be identified within the modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

When a module can be implemented by software, considering the level of existing hardware technology, a module implemented by software may build a corresponding hardware circuit to implement a corresponding function, without considering cost, and the hardware circuit may include a conventional Very Large Scale Integration (VLSI) circuit or a gate array and an existing semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

The exemplary embodiments described above are described with reference to the drawings, and many different forms and embodiments of the invention may be made without departing from the spirit and teaching of the invention, therefore, the invention is not to be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of elements may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Unless otherwise indicated, a range of values, when stated, includes the upper and lower limits of the range and any subranges therebetween.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for transmitting link release information is applied to a first terminal, and is characterized by comprising the following steps:

2. The method of claim 1, wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

3. The method of claim 2, wherein the first identification comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

4. The method of claim 2, wherein the first set of identifiers comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

5. The method of claim 1, further comprising, after receiving the link release information:

6. The method of claim 1, further comprising:

7. The method of claim 6, further comprising:

8. The method of claim 1, further comprising, after receiving the link release information:

and sending the link release confirmation information.

9. The method of claim 8, wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

10. The method of claim 9, wherein the second identification comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

11. The method of claim 9, wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

12. The method of claim 8, wherein prior to sending the link release confirmation information, the method further comprises:

13. A method for transmitting link release information is applied to a second terminal, and is characterized by comprising the following steps:

14. The method of claim 13, wherein the link release information comprises at least one of:

a first identifier;

a first set of identifications.

15. The method of claim 14, wherein the first identification comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

16. The method of claim 14, wherein the first set of identifiers comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

17. The method of claim 13, further comprising, after sending the link release information:

18. The method of claim 14, further comprising:

19. The method of claim 18, further comprising:

20. The method of claim 14, after sending the link release information, further comprising:

link release confirmation information is received.

21. The method of claim 20, wherein the link release confirmation information comprises at least one of:

a second identifier;

a second group identification.

22. The method of claim 21, wherein the second identification comprises:

an identity of the first terminal; and/or

An identity of the second terminal.

23. The method of claim 21, wherein the second group identification comprises:

an identifier of a group in which the first terminal is located; and/or

And the identification of the group where the second terminal is located.

24. A terminal device, being a first terminal, comprising a transceiver, a memory, a processor and a computer program stored on the memory and executable on the processor; it is characterized in that the preparation method is characterized in that,

25. A terminal device, which is a second terminal, comprising a transceiver, a memory, a processor and a computer program stored on the memory and executable on the processor; it is characterized in that the preparation method is characterized in that,

26. A link release information transmission apparatus applied to a first terminal, comprising:

27. A link release information transmission apparatus applied to a second terminal, comprising:

28. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the link release information transmission method according to any one of claims 1 to 12 or the steps in the link release information transmission method according to any one of claims 13 to 23.