[go: up one dir, main page]

WO2020088584A1 - 副链路释放方法、终端及网络侧设备 - Google Patents

副链路释放方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2020088584A1
WO2020088584A1 PCT/CN2019/114668 CN2019114668W WO2020088584A1 WO 2020088584 A1 WO2020088584 A1 WO 2020088584A1 CN 2019114668 W CN2019114668 W CN 2019114668W WO 2020088584 A1 WO2020088584 A1 WO 2020088584A1
Authority
WO
WIPO (PCT)
Prior art keywords
secondary link
terminal
release
timer
connection
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/114668
Other languages
English (en)
French (fr)
Inventor
梁敬
郑倩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to EP19880605.1A priority Critical patent/EP3876664A4/en
Priority to KR1020217016328A priority patent/KR102710697B1/ko
Publication of WO2020088584A1 publication Critical patent/WO2020088584A1/zh
Priority to US17/245,081 priority patent/US12185416B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a secondary link release method, terminal, and network side device.
  • LTE sidelink sidelink
  • sidelink also known as sidelink or sidelink
  • NR New Radio
  • the technical problem to be solved by the present disclosure is to provide a secondary link release method, terminal and network side device, which can support the terminal to release the established connection on the sidelink.
  • an embodiment of the present disclosure provides a secondary link release method, which is applied to a first terminal and includes:
  • the secondary link release timer is configured or pre-configured by the network-side device, or the secondary link release timer is configured by the second terminal or the second terminal from the network side Obtained in the configuration;
  • an embodiment of the present disclosure provides a secondary link release method, which is applied to a second terminal and includes:
  • an embodiment of the present disclosure provides a secondary link release method, which is applied to network-side devices and includes:
  • an embodiment of the present disclosure provides a first terminal, including:
  • An obtaining module configured to obtain a secondary link release timer, wherein the secondary link release timer is configured or pre-configured by the network side device, or the secondary link release timer is configured by the second terminal or The second terminal is obtained from the network side configuration;
  • An activation module configured to start or restart the secondary link release timer after transmitting and receiving data on the secondary link connection with the second terminal;
  • the sending module is configured to send a secondary link connection release message to the second terminal after the secondary link release timer expires, or notify a higher layer of the first terminal.
  • an embodiment of the present disclosure provides a second terminal, including:
  • a receiving module configured to receive a secondary link connection release message sent by the first terminal
  • a release module configured to release the secondary link connection with the first terminal.
  • an embodiment of the present disclosure provides a network-side device, including:
  • the configuration module is configured to configure a secondary link release timer for the first terminal, for the first terminal to release the secondary link connection after the secondary link release timer expires.
  • embodiments of the present disclosure provide a communication device, including: a memory, a processor, and a program stored on the memory and executable on the processor, and the program is implemented as described above when executed by the processor Steps in the secondary link release method.
  • an embodiment of the present disclosure provides a computer-readable storage medium that stores a program on the computer-readable storage medium, and the program is executed by a processor to implement the secondary link release method described above. step.
  • the network-side device configures or pre-configures the secondary link release timer for the first terminal. After the secondary link release timer expires, the first terminal releases the secondary link connection with the second terminal.
  • the disclosed technical solution can support the terminal to release the established connection on the sidelink.
  • FIG. 1 is a schematic flowchart of a secondary link release method applied to a first terminal according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a secondary link release method applied to a second terminal according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a secondary link release method applied to a network-side device according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a first terminal according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a second terminal according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a network-side device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of the composition of a terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of the composition of a network-side device according to an embodiment of the present disclosure.
  • LTE sidelink sidelink
  • sidelink also known as sidelink or sidelink
  • QoS Quality of Service
  • advanced V2X services such as autonomous driving, sensor expansion, etc.
  • advanced V2X services will be supported through the new air interface NR sidelink.
  • LTE Long Term Evolution
  • UE User Equipment
  • the UE sends sidelink control information (sidelink control information, SCI) through the physical sidelink control channel (PSCCH), and schedules the transmission of the physical sidelink shared channel (PSSCH) to send data .
  • SCI sidelink control information
  • PSCCH physical sidelink control channel
  • PSSCH physical sidelink shared channel
  • the LTE sidelink design supports two resource allocation modes, namely scheduled resource allocation (Scheduled resource allocation) mode and autonomous resource selection (autonomous resource selection) mode.
  • the former is controlled by the network-side device and allocates resources for each UE, and the latter is independently selected by the UE.
  • LTE supports sidelink carrier aggregation (Carrier Aggregation, CA).
  • CA Carrier Aggregation
  • the CA and Uu interfaces (ie, downlink and uplink) of LTE sidelink are different.
  • PCC primary carrier
  • SCC secondary carrier
  • the UE in autonomous resource selection mode independently performs resource sensing and resource reservation on each CC.
  • LTE sidelink is suitable for specific public safety matters (such as emergency communications in disaster places such as fire or earthquake), or vehicle-to-everything (V2X) communications.
  • IoV communication includes various services, for example, basic safety communication, advanced (automatic) driving, formation, sensor expansion, etc. Since LTE sidelink only supports broadcast communication, it is mainly used for basic security communication. Other advanced V2X services will be supported through New Radio (NR) sidelink.
  • NR New Radio
  • the 5G NR system can be used in operating frequency bands above 6 GHz that LTE does not support, and supports a larger operating bandwidth.
  • the current version of the NR system only supports the interface between the base station and the terminal, and does not yet support the sidelink interface for direct communication between terminals.
  • the embodiments of the present disclosure provide a secondary link release method, a terminal, and a network side device, which can support the terminal to release an established connection on a sidelink.
  • An embodiment of the present disclosure provides a secondary link release method, which is applied to a first terminal, as shown in FIG. 1, and includes:
  • Step 101 Obtain a secondary link release timer, where the secondary link release timer is configured or pre-configured by the network side device, or the secondary link release timer is configured by the second terminal or by the second terminal Obtained from the network side configuration;
  • Step 102 After transmitting and receiving data on the secondary link connection with the second terminal, start or restart the secondary link release timer;
  • Step 103 After the secondary link release timer expires, send a secondary link connection release message to the second terminal, or notify the upper layer of the first terminal.
  • the network side device configures or pre-configures the secondary link release timer for the first terminal, or the second terminal configures or obtains the secondary link release timer from the network side configuration, and the secondary link release timer After the timeout, the first terminal releases the secondary link connection with the second terminal.
  • the terminal can be supported to release the established connection on the sidelink.
  • the notification of the upper layer of the first terminal includes at least one of the following:
  • the acquiring the secondary link release timer configured by the network side device includes:
  • the secondary link release timer is configured by the second terminal or obtained by the second terminal from the network side configuration, and the acquiring the secondary link release timer includes:
  • duration of the secondary link release timer is determined in at least one of the following ways:
  • Network side device configuration or pre-configuration
  • the configuration of the network side device is no longer required by the method specified in the protocol, and the signaling interaction between the network side device and the terminal can be omitted.
  • the duration of the secondary link release timer can be flexibly adjusted through network-side device configuration or pre-configuration.
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal; the identifier of the first terminal and the identifier of the second terminal can enable the second terminal to accurately learn the secondary link connection that needs to be released;
  • the indication information of the cause of the release of the secondary link connection, and the indication information of the cause of the release of the secondary link connection may enable the second terminal to learn the cause of the release of the secondary link connection.
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • the method further includes at least one of the following:
  • the first terminal may release the secondary link connection after receiving the connection release response message fed back by the second terminal, or may release the secondary link itself when the connection release response message fed back by the second terminal is not received connection.
  • the receiving the connection release response message fed back by the second terminal includes at least one of the following:
  • Radio Link Control Radio Link Control
  • the secondary link connection between the release and the second terminal includes at least one of the following:
  • the radio resource control (RRC) connection with the network side is released. This can support the RRC connection between the terminal disconnection and the network side.
  • RRC radio resource control
  • the secondary link release timer and the data inactivity timer are started or restarted in at least one of the following ways:
  • the data inactivity timer is started or restarted, and the secondary link release timer is not started or restarted.
  • the first terminal and the network side transmit and receive data through the Uu port.
  • the releasing RRC connection includes at least one of the following:
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection. That is, in the technical solution of the present disclosure, the terminal may release the established secondary link unicast connection or the established secondary link multicast connection.
  • An embodiment of the present disclosure also provides a secondary link release method, which is applied to the second terminal, as shown in FIG. 2, including:
  • Step 201 Receive a secondary link connection release message sent by the first terminal
  • Step 202 Release the secondary link connection with the first terminal.
  • the second terminal after receiving the secondary link connection release message sent by the first terminal, the second terminal releases the secondary link connection with the first terminal.
  • the terminal can be supported on the sidelink Release the established connection.
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal; the identifier of the first terminal and the identifier of the second terminal can enable the second terminal to accurately learn the secondary link connection that needs to be released;
  • the indication information of the cause of the release of the secondary link connection, and the indication information of the cause of release of the secondary link connection may enable the second terminal to learn the cause of the release of the secondary link connection.
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • the secondary link connection between the release and the first terminal includes at least one of the following:
  • connection release response message is fed back to the first terminal, which can facilitate the first terminal to release the secondary link connection with the second terminal after receiving the connection release response message.
  • the feedback of the connection release response message to the first terminal includes at least one of the following:
  • the physical layer of the second terminal feeds back a connection release response message to the first terminal
  • the radio link control RLC layer of the second terminal feeds back a connection release response message to the first terminal;
  • the second terminal feeds back a connection release response message to the first terminal.
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection. That is, in the technical solution of the present disclosure, the terminal may release the established secondary link unicast connection or the established secondary link multicast connection.
  • An embodiment of the present disclosure also provides a secondary link release method, which is applied to network-side devices, as shown in FIG. 3, including:
  • Step 301 Configure a secondary link release timer for the first terminal, for the first terminal to release the secondary link connection after the secondary link release timer expires.
  • the network-side device configures or pre-configures the secondary link release timer for the first terminal. After the secondary link release timer expires, the first terminal releases the secondary link connection with the second terminal by
  • the technical solution of the present disclosure can support the terminal to release the established connection on the sidelink.
  • the configuring the secondary link release timer for the first terminal includes:
  • the base station configures a secondary link release timer for UE1, a secondary link unicast link is established between UE1 and UE2, where UE1 may be the sending end in secondary link transmission and UE2 is the secondary link The receiving end in transmission, or UE2 may be the sending end in secondary link transmission, and UE1 is the receiving end in secondary link transmission.
  • UE1 transmits on the secondary link, such as sending or receiving the MAC layer or other layer protocol data unit (Protocol Data Unit, PDU) and / or service data unit (Service Data Unit (SDU), start or restart the secondary Link release timer.
  • PDU Packed Data Unit
  • SDU Service Data Unit
  • Step 1 The base station configures a secondary link release timer for UE1 through dedicated signaling or system messages.
  • UE1 performs secondary link transmission, the link is automatically released based on the secondary link release timer.
  • the secondary link release timer can act on the sidelink MAC layer of UE1, and can also act on other protocol layers.
  • the duration of the secondary link release timer can be specified by the protocol, or can be dynamically configured by the base station.
  • the base station can dynamically configure the duration of the secondary link release timer based on the sidelink service type of UE1.
  • Step 2 When UE1 is transmitting a sidelink unicast link, it sends or receives a data packet, such as MAC SDU, then starts or restarts the secondary link release timer;
  • a data packet such as MAC SDU
  • Step 3 When UE1 does not send and receive sidelink data packets for a period of time, the secondary link release timer continues to run. When the secondary link release timer expires, UE1 automatically initiates the process of releasing the sidelink unicast link;
  • Step 4. UE1 sends a unicast connection release message to the peer UE2.
  • the unicast connection release message includes at least one of the following configuration information:
  • UE identification information including the IDs of UEs at both ends of the unicast connection, such as the ID of UE1 and the ID of UE2;
  • Cause value used to indicate the reason for the UE sending the unicast connection release message.
  • the reason for the unicast connection release message includes at least one of the following:
  • the secondary link release timer expires.
  • Step 5 After receiving the unicast connection release message of UE1, UE2 releases the unicast connection.
  • the specific behavior of releasing the unicast connection may include at least one of the following:
  • the second timer is one or more timers configured by the first terminal or the second terminal or the base station configuration or protocol; or stop The first terminal configuration or the second terminal configuration or the base station configuration or a protocol agreed timer;
  • Step 6 After receiving the unicast connection release message from UE1, UE2 may send feedback information to UE1 before releasing the unicast connection, or after releasing the unicast connection. After one or more of the conditions, UE1 confirms that the unicast connection with UE2 is successfully released.
  • UE1 receives the connection release response message fed back from the physical layer of UE2;
  • UE1 receives the connection release response message fed back from the RLC layer of UE2;
  • UE1 receives a new message from UE2, which is used in response to the unicast connection establishment release message.
  • Step 7 After UE1 confirms that the unicast connection with UE2 is successfully released, UE1 releases the secondary link connection with UE2.
  • the specific behavior of releasing the unicast connection may include at least one of the following:
  • step 6 and step 7 are optional steps.
  • the network-side device configures or pre-configures the secondary link release timer for the first terminal. After the secondary link release timer expires, the first terminal releases the secondary link connection with the second terminal by
  • the technical solution of the present disclosure can support the terminal to release the established secondary link unicast connection on the sidelink.
  • the base station configures a secondary link release timer for UE1, a secondary link multicast link is established between UE1 and UE2, where UE1 may be the sender in secondary link transmission and UE2 is the secondary link The receiving end in transmission, or UE2 may be the sending end in secondary link transmission, and UE1 is the receiving end in secondary link transmission.
  • UE1 transmits on the secondary link, such as sending or receiving the MAC layer or other layer protocol data unit (Protocol Data Unit, PDU) and / or service data unit (Service Data Unit (SDU), start or restart the secondary Link release timer.
  • PDU Packed Data Unit
  • SDU Service Data Unit
  • Step 1 The base station configures a secondary link release timer for UE1 through dedicated signaling or system messages.
  • UE1 performs secondary link transmission, the link is automatically released based on the secondary link release timer.
  • the secondary link release timer can act on the sidelink MAC layer of UE1, and can also act on other protocol layers.
  • the duration of the secondary link release timer can be specified by the protocol or can be dynamically configured by the base station.
  • the base station can dynamically configure the duration of the secondary link release timer based on the sidelink service type of UE1.
  • Step 2 When UE1 is transmitting a sidelink multicast link, it sends or receives a data packet, such as MAC SDU, then starts or restarts the secondary link release timer;
  • a data packet such as MAC SDU
  • Step 3 When UE1 does not send and receive sidelink data packets for a period of time, the secondary link release timer continues to run. When the secondary link release timer expires, UE1 automatically initiates the process of releasing the sidelink multicast link;
  • Step 4. UE1 sends a multicast connection release message to the peer UE2.
  • the multicast connection release message includes at least one of the following configuration information:
  • UE identification information including the IDs of the UEs at both ends of the multicast connection, such as the ID of UE1 and the ID of UE2;
  • Cause value used to instruct the UE to send the cause of the multicast connection release message.
  • the reason for the multicast connection release message includes at least one of the following:
  • the secondary link release timer expires.
  • Step 5 After receiving the multicast connection release message of UE1, UE2 releases the multicast connection.
  • the specific behavior of releasing the multicast connection may include at least one of the following:
  • the second timer is one or more timers configured by the first terminal or the second terminal or the base station configuration or protocol; or stop The first terminal configuration or the second terminal configuration or the base station configuration or a protocol agreed timer;
  • Step 6 After receiving the multicast connection release message of UE1, UE2 may send feedback information to UE1 before releasing the multicast connection, or after releasing the multicast connection. After one or more of the conditions, UE1 confirms that the multicast connection with UE2 is successfully released.
  • UE1 receives the connection release response message fed back from the physical layer of UE2;
  • UE1 receives the connection release response message fed back from the RLC layer of UE2;
  • UE1 receives a new message from UE2, and the new message is used in response to a multicast connection establishment release message.
  • Step 7 After UE1 confirms that the multicast connection with UE2 is successfully released, UE1 releases the secondary link connection with UE2.
  • the specific behavior of releasing the multicast connection may include at least one of the following:
  • step 6 and step 7 are optional steps.
  • the network-side device configures or pre-configures the secondary link release timer for the first terminal. After the secondary link release timer expires, the first terminal releases the secondary link connection with the second terminal by
  • the technical solution of the present disclosure can support the terminal to release the established secondary link multicast connection on the sidelink.
  • the base station configures a secondary link release timer and a data inactivity timer for UE1, and a secondary link link is established between UE1 and UE2, where UE1 may be the sender in secondary link transmission, UE2 It is the receiving end in secondary link transmission, or UE2 may be the sending end in secondary link transmission, and UE1 is the receiving end in secondary link transmission. Both data transmission and reception on the secondary link and Uu port of UE1 may affect the start and restart of the two timers of the secondary link release timer and the data inactivity timer.
  • Step 1 The base station configures two timers for UE1 through dedicated signaling or system messages, which are a data inactivity timer and a secondary link release timer on the Uu port, respectively.
  • the two timers can be configured in the same message or in two messages. When they are configured in two messages, the order of the two messages is not limited.
  • the data inactivity timer on the Uu port refers to that if the UE does not send and receive data from the Uu port (that is, data transmission and reception with the base station) for a period of time, the UE will leave the RRC connection state.
  • Step 2 For the start and restart of the two timers, there may be at least one of the following situations:
  • both timers start or restart
  • both timers start or restart
  • Step 3 When the secondary link release timer expires, UE1 releases the secondary link connection with UE2.
  • the specific behavior of releasing the secondary link connection may include at least one of the following:
  • the secondary link connection is a secondary link multicast connection or a secondary link unicast connection.
  • the network-side device configures or pre-configures the secondary link release timer and data inactivity timer for the first terminal. After the secondary link release timer expires, the first terminal releases the The secondary link connection. After the data inactivity timer expires, the first terminal releases the RRC connection with the network side device.
  • the terminal can be supported to release the established secondary link connection on the sidelink. And release the RRC connection with the network side device.
  • An embodiment of the present disclosure also provides a first terminal, as shown in FIG. 4, including:
  • the obtaining module 11 is configured to obtain a secondary link release timer, wherein the secondary link release timer is configured or pre-configured by the network side device, or the secondary link release timer is configured or configured by the second terminal The second terminal is obtained from the network side configuration;
  • the starting module 12 is configured to start or restart the secondary link release timer after sending and receiving data on the secondary link connection with the second terminal;
  • the sending module 13 is configured to send a secondary link connection release message to the second terminal after the secondary link release timer expires, or notify a higher layer of the first terminal.
  • the network side device configures or pre-configures the secondary link release timer for the first terminal, or the second terminal configures or obtains the secondary link release timer from the network side configuration, and the secondary link release timer After the timeout, the first terminal releases the secondary link connection with the second terminal.
  • the terminal can be supported to release the established connection on the sidelink.
  • the notification of the upper layer of the first terminal includes at least one of the following:
  • the acquiring module is specifically configured to acquire the secondary link release timer configured by the network side device through dedicated signaling or system messages.
  • the secondary link release timer is configured by the second terminal or obtained by the second terminal from the network side configuration, and the acquiring module is specifically configured to acquire the secondary link release timer configuration sent by the second terminal.
  • duration of the secondary link release timer is determined in at least one of the following ways:
  • Network side device configuration or pre-configuration
  • the configuration of the network side device is no longer required by the method specified in the protocol, and the signaling interaction between the network side device and the terminal can be omitted.
  • the duration of the secondary link release timer can be flexibly adjusted through network-side device configuration or pre-configuration.
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal; the identifier of the first terminal and the identifier of the second terminal can enable the second terminal to accurately learn the secondary link connection that needs to be released;
  • the indication information of the cause of the release of the secondary link connection, and the indication information of the cause of the release of the secondary link connection may enable the second terminal to learn the cause of the release of the secondary link connection.
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • a receiving module configured to receive a connection release response message fed back by the second terminal
  • a release module configured to release the secondary link connection with the second terminal.
  • the first terminal may release the secondary link connection after receiving the connection release response message fed back by the second terminal, or may release the secondary link itself when the connection release response message fed back by the second terminal is not received connection.
  • the receiving module is specifically used to perform at least one of the following:
  • release module is specifically used to perform at least one of the following:
  • the obtaining module is also used to obtain a data inactivity timer configured by the network side device;
  • the release module is configured to release the radio resource control RRC connection with the network side after the data inactivity timer expires. This can support the RRC connection between the terminal disconnection and the network side.
  • the starting module is specifically configured to start or restart the secondary link release timer and the data inactivity timer in at least one of the following ways:
  • the data inactivity timer is started or restarted, and the secondary link release timer is not started or restarted.
  • the release module is specifically configured to perform at least one of the following:
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection. That is, in the technical solution of the present disclosure, the terminal may release the established secondary link unicast connection or the established secondary link multicast connection.
  • An embodiment of the present disclosure also provides a second terminal, as shown in FIG. 5, including:
  • the receiving module 21 is configured to receive the secondary link connection release message sent by the first terminal;
  • the release module 22 is configured to release the secondary link connection with the first terminal.
  • the second terminal after receiving the secondary link connection release message sent by the first terminal, the second terminal releases the secondary link connection with the first terminal.
  • the terminal can be supported on the sidelink Release the established connection.
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal; the identifier of the first terminal and the identifier of the second terminal can enable the second terminal to accurately learn the secondary link connection that needs to be released;
  • the indication information of the cause of the release of the secondary link connection, and the indication information of the cause of the release of the secondary link connection may enable the second terminal to learn the cause of the release of the secondary link connection.
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • the release module is specifically configured to perform at least one of the following:
  • a second sending module configured to send a secondary link release timer configuration to the first terminal, wherein the secondary link release timer is configured by the second terminal or configured by the second terminal from the network side Obtained.
  • the feedback module is configured to feed back a connection release response message to the first terminal, which can facilitate the first terminal to release the secondary link connection with the second terminal after receiving the connection release response message.
  • the feedback module is specifically configured to perform at least one of the following:
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection. That is, in the technical solution of the present disclosure, the terminal may release the established secondary link unicast connection or the established secondary link multicast connection.
  • An embodiment of the present disclosure also provides a network-side device, as shown in FIG. 6, including:
  • the configuration module 31 is configured to configure a secondary link release timer for the first terminal, for the first terminal to release the secondary link connection after the secondary link release timer expires.
  • the network-side device configures or pre-configures the secondary link release timer for the first terminal. After the secondary link release timer expires, the first terminal releases the secondary link connection with the second terminal by
  • the technical solution of the present disclosure can support the terminal to release the established connection on the sidelink.
  • the configuration module is specifically configured to configure the secondary link release timer for the first terminal through dedicated signaling or system messages.
  • the configuration module is further configured to configure the data inactivity timer for the first terminal, for the first terminal to release the time between the data inactivity timer and the network side after the data inactivity timer expires. Radio resource control RRC connection.
  • An embodiment of the present disclosure also provides a communication device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the computer program is executed by the processor as described above. Steps in the secondary link release method.
  • the communication device may be a network-side device or a terminal.
  • the network-side device 500 includes: a processor 501, a transceiver 502, a memory 503, a user interface 504, and a bus interface, where:
  • the network-side device 500 further includes: a computer program stored on the memory 503 and running on the processor 501.
  • the computer program is executed by the processor 501 and implements the following steps: Link release timer.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 501 and various circuits of the memory represented by the memory 503 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, and therefore, they will not be further described in this article.
  • the bus interface provides an interface.
  • the transceiver 502 may be a plurality of elements, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium.
  • the user interface 504 may also be an interface that can be externally connected to a desired device.
  • the connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, and a joystick.
  • the processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 501 in performing operations.
  • the configuring the secondary link release timer for the first terminal includes:
  • the terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, and a user input unit 607 , Interface unit 608, memory 609, processor 610, and power supply 611 and other components.
  • a radio frequency unit 601 a radio frequency unit 601
  • a network module 602 an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, and a user input unit 607 , Interface unit 608, memory 609, processor 610, and power supply 611 and other components.
  • the terminal structure shown in FIG. 8 does not constitute a limitation on the terminal, and the terminal may include more or less components than those illustrated, or combine certain components, or arrange different components.
  • the terminals include but are not limited to mobile phones, tablet computers, notebook computers, palmtop computers, vehicle-mounted terminals, wearable devices, pedometers, and the like.
  • the processor 610 When the terminal is the first terminal connected to the secondary link, the processor 610 is used to acquire a secondary link release timer, wherein the secondary link release timer is configured or pre-configured by the network-side device, or The secondary link release timer is configured by the second terminal or obtained by the second terminal from the network side configuration; after data is transmitted and received on the secondary link connection with the second terminal, the secondary link is started or restarted Release timer; after the secondary link release timer expires, send a secondary link connection release message to the second terminal to notify the upper layer of the first terminal.
  • the secondary link release timer is configured or pre-configured by the network-side device, or The secondary link release timer is configured by the second terminal or obtained by the second terminal from the network side configuration; after data is transmitted and received on the secondary link connection with the second terminal, the secondary link is started or restarted Release timer; after the secondary link release timer expires, send a secondary link connection release message to the second terminal to notify the upper layer of the first terminal.
  • the notification of the upper layer of the first terminal includes at least one of the following:
  • the acquiring the secondary link release timer configured by the network side device includes:
  • the secondary link release timer is configured by the second terminal or obtained by the second terminal from the network side configuration, and the acquiring the secondary link release timer includes:
  • duration of the secondary link release timer is determined in at least one of the following ways:
  • Network side device configuration or pre-configuration
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • the receiving the connection release response message fed back by the second terminal includes at least one of the following:
  • the secondary link connection between the release and the second terminal includes:
  • the radio resource control RRC connection with the network side is released.
  • the secondary link release timer and the data inactivity timer are started or restarted in at least one of the following ways:
  • the data inactivity timer is started or restarted, and the secondary link release timer is not started or restarted.
  • the releasing of the RRC connection includes:
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection.
  • the processor 610 is configured to receive a secondary link connection release message sent by the first terminal; and release the secondary link connection with the first terminal.
  • the secondary link connection release message includes at least one of the following information:
  • the identifier of the first terminal
  • the identifier of the second terminal
  • the reason for releasing the secondary link connection includes at least one of the following:
  • the secondary link release timer expires
  • the secondary link connection between the release and the first terminal includes at least one of the following:
  • the feedback of the connection release response message to the first terminal includes at least one of the following:
  • the physical layer of the second terminal feeds back a connection release response message to the first terminal
  • the radio link control RLC layer of the second terminal feeds back a connection release response message to the first terminal;
  • the second terminal feeds back a connection release response message to the first terminal.
  • the secondary link connection includes a secondary link unicast connection or a secondary link multicast connection.
  • the radio frequency unit 601 may be used to receive and send signals during sending and receiving information or during a call. Specifically, after receiving the downlink data from the base station, the processor 610 processes the data; The uplink data is sent to the base station.
  • the radio frequency unit 601 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 601 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides users with wireless broadband Internet access through the network module 602, such as helping users send and receive e-mail, browse web pages, and access streaming media.
  • the audio output unit 603 may convert the audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into an audio signal and output as sound. Moreover, the audio output unit 603 may also provide audio output related to a specific function performed by the terminal 600 (eg, call signal reception sound, message reception sound, etc.).
  • the audio output unit 603 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 604 is used to receive audio or video signals.
  • the input unit 604 may include a graphics processor (Graphics, Processing, Unit, GPU) 6041 and a microphone 6042, and the graphics processor 6041 may process a still picture or a video image obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode The data is processed.
  • the processed image frame may be displayed on the display unit 606.
  • the image frame processed by the graphics processor 6041 may be stored in the memory 609 (or other storage medium) or sent via the radio frequency unit 601 or the network module 602.
  • the microphone 6042 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 601 in the case of a telephone call mode and output.
  • the terminal 600 further includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 6061 according to the brightness of the ambient light, and the proximity sensor can close the display panel 6061 and / or when the terminal 600 moves to the ear Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when at rest, and can be used to identify terminal postures (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc .; sensor 605 can also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be repeated here.
  • the display unit 606 is used to display information input by the user or information provided to the user.
  • the display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display (Liquid Crystal) (LCD), an organic light emitting diode (Organic Light-Emitting Diode, OLED), or the like.
  • LCD Liquid Crystal
  • OLED Organic Light-Emitting Diode
  • the user input unit 607 may be used to receive input numeric or character information, and generate key signal input related to user settings and function control of the terminal.
  • the user input unit 607 includes a touch panel 6071 and other input devices 6072.
  • the touch panel 6071 also known as a touch screen, can collect user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc. on or near the touch panel 6071 operating).
  • the touch panel 6071 may include a touch detection device and a touch controller.
  • the touch detection device detects the user's touch orientation, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into contact coordinates, and then sends To the processor 610, the command sent by the processor 610 is received and executed.
  • the touch panel 6071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the user input unit 607 may also include other input devices 6072.
  • other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the touch panel 6071 may be overlaid on the display panel 6061. After the touch panel 6071 detects a touch operation on or near it, it is transmitted to the processor 610 to determine the type of touch event, and then the processor 610 according to the touch The type of event provides corresponding visual output on the display panel 6061.
  • the touch panel 6071 and the display panel 6061 are implemented as two independent components to realize the input and output functions of the terminal, in some embodiments, the touch panel 6071 and the display panel 6061 may be integrated to The input and output functions of the terminal are implemented, which is not limited here.
  • the interface unit 608 is an interface for connecting an external device to the terminal 600.
  • the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input / output (I / O) port, video I / O port, headphone port, etc.
  • the interface unit 608 may be used to receive input from external devices (eg, data information, power, etc.) and transmit the received input to one or more elements within the terminal 600 or may be used between the terminal 600 and external devices Transfer data between.
  • the memory 609 can be used to store software programs and various data.
  • the memory 609 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one function required application programs (such as sound playback function, image playback function, etc.), etc .; the storage data area may store Data created by the use of mobile phones (such as audio data, phone books, etc.), etc.
  • the memory 609 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 610 is the control center of the terminal, and uses various interfaces and lines to connect the various parts of the entire terminal, executes or executes the software programs and / or modules stored in the memory 609, and calls the data stored in the memory 609 to execute Various functions and processing data of the terminal, so as to monitor the terminal as a whole.
  • the processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs, etc.
  • the modulation processor mainly handles wireless communication. It can be understood that, the foregoing modem processor may not be integrated into the processor 610.
  • the terminal 600 may further include a power supply 611 (such as a battery) that supplies power to various components.
  • a power supply 611 (such as a battery) that supplies power to various components.
  • the power supply 611 may be logically connected to the processor 610 through a power management system, so as to implement management of charging, discharging, and power consumption management through the power management system And other functions.
  • the terminal 600 includes some unillustrated functional modules, which will not be repeated here.
  • An embodiment of the present disclosure also provides a computer-readable storage medium that stores a computer program on the computer-readable storage medium, and when the computer program is executed by a processor, implements the steps in the secondary link release method described above .
  • the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processor (Digital Signal Processing, DSP), digital signal processing device (DSP Device, DSPD), programmable Logic device (Programmable Logic Device, PLD), field programmable gate array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, others for performing the functions described in this disclosure Electronic unit or its combination.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device digital signal processing device
  • DSPD digital signal processing device
  • PLD programmable Logic Device
  • FPGA field programmable gate array
  • controller microcontroller
  • microprocessor others for performing the functions described in this disclosure Electronic unit or its combination.
  • the techniques described herein may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described herein.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory may be implemented in the processor or external to the processor.
  • the embodiments of the embodiments of the present disclosure may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present disclosure may take the form of computer program products implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer readable memory that can guide a computer or other programmable data processing user equipment to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including instruction means, which The instruction device implements the functions specified in one block or multiple blocks in the flowchart one flow or multiple flows and / or block diagrams.
  • These computer program instructions can also be loaded on a computer or other programmable data processing user equipment, so that a series of operating steps are performed on the computer or other programmable user equipment to generate computer-implemented processing, and thus on the computer or other programmable user equipment
  • the instructions executed above provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and / or block diagrams.

Landscapes

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

Abstract

本公开提供了副链路释放方法、终端及网络侧设备，其中，副链路释放方法，应用于第一终端，包括：获取副链路释放定时器，其中，副链路释放定时器由网络侧设备配置或预配置，或者，副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；在与第二终端之间的副链路连接上进行数据收发后，启动或重启副链路释放定时器；在副链路释放定时器超时后，向第二终端发送副链路连接释放消息，或者，通知第一终端的高层。

Description

副链路释放方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2018年11月1日在中国提交的中国专利申请号No.201811297557.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种副链路释放方法、终端及网络侧设备。
背景技术
长期演进(Long Term Evolution，LTE)副链路(sidelink，也可称为侧链路或边链路)基于广播机制的通信，无法满足支持高级车联网(vehicle to everything，V2X)业务的服务质量(Quality of Service，QoS)需求，例如自动驾驶，传感器扩展等等要求低时延、高可靠、大数据量的高级V2X业务，这些高级V2X业务将通过新空口(New Radio，NR)sidelink得以支持。
但是对于sidelink，目前尚未有技术支持终端断开sidelink上的连接。
发明内容
本公开要解决的技术问题是提供一种副链路释放方法、终端及网络侧设备，可以支持终端在sidelink上释放已建立的连接。
为解决上述技术问题，本公开的实施例提供技术方案如下：
第一方面，本公开的实施例提供一种副链路释放方法，应用于第一终端，包括：
获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
第二方面，本公开的实施例提供一种副链路释放方法，应用于第二终端，包括：
接收第一终端发送的副链路连接释放消息；
释放与所述第一终端之间的副链路连接。
第三方面，本公开的实施例提供一种副链路释放方法，应用于网络侧设备，包括：
为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
第四方面，本公开的实施例提供一种第一终端，包括：
获取模块，用于获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
启动模块，用于在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
发送模块，用于在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
第五方面，本公开的实施例提供一种第二终端，包括：
接收模块，用于接收第一终端发送的副链路连接释放消息；
释放模块，用于释放与所述第一终端之间的副链路连接。
第六方面，本公开的实施例提供一种网络侧设备，包括：
配置模块，用于为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
第七方面，本公开的实施例提供一种通信设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的程序，所述程序被所述处理器执行时实现如上所述的副链路释放方法中的步骤。
第八方面，本公开的实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有程序，所述程序被处理器执行时实现如上所述的副链 路释放方法中的步骤。
本公开的实施例具有以下有益效果：
上述方案中，网络侧设备为第一终端配置或预配置副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
附图说明
图1为本公开实施例应用于第一终端的副链路释放方法的流程示意图；
图2为本公开实施例应用于第二终端的副链路释放方法的流程示意图；
图3为本公开实施例应用于网络侧设备的副链路释放方法的流程示意图；
图4为本公开实施例的第一终端的结构示意图；
图5为本公开实施例的第二终端的结构示意图；
图6为本公开实施例的网络侧设备的结构示意图；
图7为本公开实施例的终端的组成示意图；
图8为本公开实施例的网络侧设备的组成示意图。
具体实施方式
为使本公开的实施例要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。
长期演进(Long Term Evolution，LTE)副链路(sidelink，也可称为侧链路或边链路)基于广播机制的通信，无法满足支持高级车联网(V2X)业务的服务质量(Quality of Service，QoS)需求，例如自动驾驶，传感器扩展等等要求低时延、高可靠、大数据量的高级V2X业务，这些高级V2X业务将通过新空口NR sidelink得以支持。
长期演进(Long Term Evolution，LTE)系统支持副链路(sidelink，也可称为侧链路或边链路)，用于终端(User Equipment，UE)之间不通过网络侧设备进行直接数据传输。
UE通过物理副链路控制信道(Physical sidelink Control Channel,PSCCH)发送副链路控制信息(sidelink Control Information，SCI)，调度物理副链路共 享信道(Physical sidelink Shared Channel，PSSCH)的传输以发送数据。该传输是以广播形式进行的，接收端并不向发送端反馈接收是否成功。
LTE sidelink设计支持两种资源分配模式，分别是调度资源分配(Scheduled resource allocation)模式与自主资源选择(autonomous resource selection)模式。前者由网络侧设备控制并为每个UE分配资源，后者由UE自主选择资源。
从第15个发布版本开始，LTE支持sidelink载波汇聚(Carrier Aggregation，CA)。LTE sidelink的CA与Uu接口(即downlink与uplink)不同，没有主载波(Primary component carrier，PCC)与辅载波(Secondary component carrier，SCC)之分。自主资源选择模式的UE在每个CC上独立进行资源感知(sensing)与资源预留。
LTE sidelink的设计适用于特定的公共安全事务(如火灾场所或地震等灾难场所进行紧急通讯)，或车联网(vehicle to everything，V2X)通信等。车联网通信包括各种业务，例如，基本安全类通信，高级(自动)驾驶，编队，传感器扩展等等。由于LTE sidelink只支持广播通信，因此主要用于基本安全类通信，其他高级V2X业务将通过新空口(New Radio，NR)sidelink支持。
5G NR系统可用于LTE所不支持的6GHz以上工作频段，支持更大的工作带宽，但目前版本的NR系统只支持基站与终端间的接口，尚不支持终端之间直接通信的sidelink接口。
另外，对于sidelink，目前尚未有技术支持终端断开sidelink上的连接。
针对上述问题，本公开的实施例针提供一种副链路释放方法、终端及网络侧设备，可以支持终端在sidelink上释放已建立的连接。
本公开实施例提供了一种副链路释放方法，应用于第一终端，如图1所示，包括：
步骤101：获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
步骤102：在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
步骤103：在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，或者，第二终端配置或从网络侧配置中获得副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述通知所述第一终端的高层包括以下至少一项：
通知第一终端的高层所述副链路连接的释放和/或释放原因；
通知第一终端的高层所述副链路释放定时器超时；
通知第一终端的高层所述副链路连接失败；
通知所述第一终端的高层所述第一终端发生了无线链路失败。
进一步地，所述获取网络侧设备配置的副链路释放定时器包括：
获取网络侧设备通过专用信令或系统消息配置的所述副链路释放定时器。
进一步地，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得，所述获取副链路释放定时器包括：
获取由第二终端发送的副链路释放定时器配置。
进一步地，所述副链路释放定时器的时长通过以下至少一种方式确定：
协议规定；
网络侧设备配置或预配置。
通过协议规定的方式不再需要网络侧设备配置，能够省去网络侧设备与终端之间的信令交互。通过网络侧设备配置或预配置可以灵活调整副链路释放定时器的时长。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；通过第一终端的标识和所述第二终端的标识可以使得第二终端准确获知需要释放的副链路连接；
副链路连接释放原因的指示信息，通过副链路连接释放原因的指示信息可以使得第二终端获知副链路连接释放原因。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，所述方法还包括以下至少之一：
接收所述第二终端反馈的连接释放响应消息，释放与所述第二终端之间的副链路连接；
释放与所述第二终端之间的副链路连接。
本实施例中，第一终端可以在接收到第二终端反馈的连接释放响应消息后释放副链路连接，也可以在未接收到第二终端反馈的连接释放响应消息时，自行释放副链路连接。
进一步地，所述接收所述第二终端反馈的连接释放响应消息包括以下至少一种：
接收所述第二终端的物理层反馈的连接释放响应消息；
接收所述第二终端的无线链路控制(Radio Link Control，RLC)层反馈的连接释放响应消息；
接收所述第二终端的连接释放响应消息。
进一步地，所述释放与所述第二终端之间的副链路连接包括以下至少一种：
重置媒体介入控制(Media Access Control，MAC)层；
停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因。
进一步地，还包括：
获取网络侧设备配置的数据不活跃定时器；
在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制(Radio Resource Control，RRC)连接。这样可以支持终端断开和网络侧之间的RRC连接。
进一步地，采用以下至少一种方式启动或重启所述副链路释放定时器和所述数据不活跃定时器：
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器，不启动或不重启所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述数据不活跃定时器，不启动或不重启所述副链路释放定时器。
需要说明的是，第一终端与网络侧之间通过Uu口进行收发数据。
进一步地，所述释放RRC连接包括以下至少一种：
重置MAC层；
停止除第三定时器之外其他所有运行的定时器，所述第三定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因；
进入RRC空闲态或RRC非激活态。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。即本公开的技术方案中，终端可以释放已建立的副链路单播连接，也可以释放已建立的副链路组播连接。
本公开实施例还提供了一种副链路释放方法，应用于第二终端，如图2所示，包括：
步骤201：接收第一终端发送的副链路连接释放消息；
步骤202：释放与所述第一终端之间的副链路连接。
本实施例中，第二终端在接收到第一终端发送的副链路连接释放消息后，释放与第一终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；通过第一终端的标识和所述第二终端的标识可以 使得第二终端准确获知需要释放的副链路连接；
副链路连接释放原因的指示信息，通过副链路连接释放原因的指示信息可以使得第二终端获知副链路连接释放原因。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，所述释放与所述第一终端之间的副链路连接包括以下至少一种：
重置媒体介入控制MAC层；
停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第二终端的高层副链路连接的释放和/或释放原因。
进一步地，还包括：
向所述第一终端发送副链路释放定时器配置，其中，所述副链路释放定时器由所述第二终端配置或由所述第二终端从网络侧配置中获得。
进一步地，还包括：
向所述第一终端反馈连接释放响应消息，这样可以方便第一终端在接收到连接释放响应消息后，释放与第二终端之间的副链路连接。
进一步地，所述向所述第一终端反馈连接释放响应消息包括以下至少一种：
所述第二终端的物理层向所述第一终端反馈连接释放响应消息；
所述第二终端的无线链路控制RLC层向所述第一终端反馈连接释放响应消息；
所述第二终端向所述第一终端反馈连接释放响应消息。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。即本公开的技术方案中，终端可以释放已建立的副链路单播连接，也可以释放已建立的副链路组播连接。
本公开实施例还提供了一种副链路释放方法，应用于网络侧设备，如图 3所示，包括：
步骤301：为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述为第一终端配置副链路释放定时器包括：
通过专用信令或系统消息为所述第一终端配置所述副链路释放定时器。
进一步地，还包括：
为所述第一终端配置所述数据不活跃定时器，用于所述第一终端在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
下面结合具体的实施例对本公开的技术方案进行进一步介绍：
实施例一
本实施例中，基站为UE1配置副链路释放定时器，UE1与UE2之间建立有副链路单播链路，其中，UE1可以是副链路传输中的发送端，UE2是副链路传输中的接收端，或者UE2可以是副链路传输中的发送端，UE1是副链路传输中的接收端。在UE1在副链路上进行传输，比如发送或者接收到MAC层或其他层的协议数据单元(Protocol Data Unit，PDU)和/或服务数据单元(Service Data Unit，SDU)时，启动或重启副链路释放定时器，当副链路释放定时器超时后，UE1自动释放副链路单播链路。
本实施例的副链路释放方法包括以下步骤：
步骤1、基站通过专有信令或系统消息为UE1配置副链路释放定时器，用于UE1进行副链路传输时，基于副链路释放定时器进行链路的自动释放。该副链路释放定时器可以作用于UE1的sidelink MAC层，也可以作用于其他协议层。
其中，副链路释放定时器的时长可以由协议规定，也可以由基站动态配置。基站可以基于UE1的sidelink业务类型，来动态配置该副链路释放定时器的时长。
步骤2、当UE1在进行sidelink单播链路传输时，发送或接收数据包，如 MAC SDU，则启动或重启该副链路释放定时器；
步骤3、当一段时间内UE1没有进行sidelink数据包的收发，则副链路释放定时器持续运行，当副链路释放定时器超时后，UE1自动发起释放sidelink单播链路的过程；
步骤4、UE1向对端的UE2发送单播连接释放消息，所述单播连接释放消息包括以下配置信息的至少一项：
UE标示信息，包括单播连接两端UE的ID，比如UE1的ID以及UE2的ID；
Cause value，用于指示UE发送单播连接释放消息的原因。
其中，单播连接释放消息的原因包括以下至少一种：
副链路连接失败；
副链路释放定时器超时等。
步骤5、UE2接收到UE1的单播连接释放消息后，释放所述单播连接。释放所述单播连接的具体行为可以包括以下至少之一：
重置MAC；
停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；或者停止所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知UE2的高层sidelink单播连接的释放和/或相应的释放原因(cause value)。
步骤6、UE2在接收到UE1的单播连接释放消息后，在释放所述单播连接前，或者，在释放所述单播连接后，可以发送反馈信息给UE1，此时，如满足下述条件的一项或多项后，UE1确认与UE2之间的单播连接被释放成功。
UE1接收到来自UE2的物理层反馈的连接释放响应消息；
UE1接收到来自UE2的RLC层反馈的连接释放响应消息；
UE1接收到来自UE2的新消息，所述新消息用于对单播连接建立释放消息的应答。
步骤7、UE1确认与UE2之间的单播连接被释放成功后，UE1释放与 UE2之间的副链路连接，释放所述单播连接的具体行为可以包括以下至少之一：
重置MAC；
停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；或者停止所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；第一定时器可以与第二定时器相同，也可以与第二定时器不同；
释放无线承载以及对应的协议层实体；
通知UE1的高层sidelink单播连接的释放和/或相应的释放原因(cause value)。
其中，步骤6和步骤7为可选步骤。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的副链路单播连接。
实施例二
本实施例中，基站为UE1配置副链路释放定时器，UE1与UE2之间建立有副链路组播链路，其中，UE1可以是副链路传输中的发送端，UE2是副链路传输中的接收端，或者UE2可以是副链路传输中的发送端，UE1是副链路传输中的接收端。在UE1在副链路上进行传输，比如发送或者接收到MAC层或其他层的协议数据单元(Protocol Data Unit，PDU)和/或服务数据单元(Service Data Unit，SDU)时，启动或重启副链路释放定时器，当副链路释放定时器超时后，UE1自动释放副链路组播链路。
本实施例的副链路释放方法包括以下步骤：
步骤1、基站通过专有信令或系统消息为UE1配置副链路释放定时器，用于UE1进行副链路传输时，基于副链路释放定时器进行链路的自动释放。该副链路释放定时器可以作用于UE1的sidelink MAC层，也可以作用于其他协议层。
其中，副链路释放定时器的时长可以由协议规定，也可以由基站动态配 置。基站可以基于UE1的sidelink业务类型，来动态配置该副链路释放定时器的时长。
步骤2、当UE1在进行sidelink组播链路传输时，发送或接收数据包，如MAC SDU，则启动或重启该副链路释放定时器；
步骤3、当一段时间内UE1没有进行sidelink数据包的收发，则副链路释放定时器持续运行，当副链路释放定时器超时后，UE1自动发起释放sidelink组播链路的过程；
步骤4、UE1向对端的UE2发送组播连接释放消息，所述组播连接释放消息包括以下配置信息的至少一项：
UE标示信息，包括组播连接两端UE的ID，比如UE1的ID以及UE2的ID；
Cause value，用于指示UE发送组播连接释放消息的原因。
其中，组播连接释放消息的原因包括以下至少一种：
副链路连接失败；
副链路释放定时器超时等。
步骤5、UE2接收到UE1的组播连接释放消息后，释放所述组播连接。释放所述组播连接的具体行为可以包括以下至少之一：
重置MAC；
停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；或者停止所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知UE2的高层sidelink组播连接的释放和/或相应的释放原因(cause value)。
步骤6、UE2在接收到UE1的组播连接释放消息后，在释放所述组播连接前，或者，在释放所述组播连接后，可以发送反馈信息给UE1，此时，如满足下述条件的一项或多项后，UE1确认与UE2之间的组播连接被释放成功。
UE1接收到来自UE2的物理层反馈的连接释放响应消息；
UE1接收到来自UE2的RLC层反馈的连接释放响应消息；
UE1接收到来自UE2的新消息，所述新消息用于对组播连接建立释放消息的应答。
步骤7、UE1确认与UE2之间的组播连接被释放成功后，UE1释放与UE2之间的副链路连接，释放所述组播连接的具体行为可以包括以下至少之一：
重置MAC；
停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；或者停止所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；第一定时器可以与第二定时器相同，也可以与第二定时器不同；
释放无线承载以及对应的协议层实体；
通知UE1的高层sidelink组播连接的释放和/或相应的释放原因(cause value)。
其中，步骤6和步骤7为可选步骤。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的副链路组播连接。
实施例三
本实施例中，基站为UE1配置副链路释放定时器和数据不活跃定时器，UE1与UE2之间建立有副链路链路，其中，UE1可以是副链路传输中的发送端，UE2是副链路传输中的接收端，或者UE2可以是副链路传输中的发送端，UE1是副链路传输中的接收端。在UE1在副链路和Uu口上的数据收发都可能会影响到副链路释放定时器和数据不活跃定时器两个定时器的启动与重启。
本实施例的副链路释放方法包括以下步骤：
步骤1、基站通过专有信令或系统消息给UE1配置两个定时器，分别为Uu口上的数据不活跃定时器与副链路释放定时器。这两个定时器可以在同一条消息中配置，或者在两条消息中配置，在两条消息中配置时，两条消息的顺序不限定。所述Uu口上的数据不活跃定时器指的是，如果UE在一段时间 内没有Uu口的数据收发(即和基站间的数据收发)，则UE会离开RRC连接态。
步骤2、对于两个定时器的启动和重启，可能有以下几种情况至少之一：
如果UE1在sidelink上进行了数据的收发，则两个计时器都启动或重启；
如果UE1在sidelink上进行了数据的收发，只重启副链路释放定时器，不重启的数据不活跃定时器；
如果UE1在Uu口上进行了数据的收发，则两个计时器都启动或重启；
如果UE1在Uu口上进行了数据的收发，则只重启的数据不活跃定时器，不重启副链路释放定时器。
步骤3、当副链路释放定时器超时后，UE1释放与UE2的副链路连接，释放副链路连接的具体行为可以包括以下至少之一：
重置MAC；
停止除第三定时器之外其他所有运行的定时器，所述第三定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；或者停止所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知UE1的高层sidelink副链路连接的释放和/或相应的释放原因(cause value)；
进入RRC空闲态(IDLE)或RRC非激活态(INACTIVE)。
其中，副链路连接为副链路组播连接或副链路单播连接。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器和数据不活跃定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，在数据不活跃定时器超时后，第一终端释放与网络侧设备之间的RRC连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的副链路连接，以及释放与网络侧设备之间的RRC连接。
本公开实施例还提供了一种第一终端，如图4所示，包括：
获取模块11，用于获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
启动模块12，用于在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
发送模块13，用于在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，或者，第二终端配置或从网络侧配置中获得副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述通知所述第一终端的高层包括以下至少一项：
通知第一终端的高层所述副链路连接的释放和/或释放原因；
通知第一终端的高层所述副链路释放定时器超时；
通知第一终端的高层所述副链路连接失败；
通知所述第一终端的高层所述第一终端发生了无线链路失败。
进一步地，所述获取模块具体用于获取网络侧设备通过专用信令或系统消息配置的所述副链路释放定时器。
进一步地，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得，所述获取模块具体用于获取由第二终端发送的副链路释放定时器配置。
进一步地，所述副链路释放定时器的时长通过以下至少一种方式确定：
协议规定；
网络侧设备配置或预配置。
通过协议规定的方式不再需要网络侧设备配置，能够省去网络侧设备与终端之间的信令交互。通过网络侧设备配置或预配置可以灵活调整副链路释放定时器的时长。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；通过第一终端的标识和所述第二终端的标识可以使得第二终端准确获知需要释放的副链路连接；
副链路连接释放原因的指示信息，通过副链路连接释放原因的指示信息 可以使得第二终端获知副链路连接释放原因。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，还包括：
接收模块，用于接收所述第二终端反馈的连接释放响应消息；
释放模块，用于释放与所述第二终端之间的副链路连接。
本实施例中，第一终端可以在接收到第二终端反馈的连接释放响应消息后释放副链路连接，也可以在未接收到第二终端反馈的连接释放响应消息时，自行释放副链路连接。
进一步地，所述接收模块具体用以执行以下至少一种：
接收所述第二终端的物理层反馈的连接释放响应消息；
接收所述第二终端的无线链路控制RLC层反馈的连接释放响应消息；
接收所述第二终端的连接释放响应消息。
进一步地，所述释放模块具体用以执行以下至少一种：
重置媒体介入控制MAC层；
停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因。
进一步地，所述获取模块还用于获取网络侧设备配置的数据不活跃定时器；
还包括：
释放模块，用于在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。这样可以支持终端断开和网络侧之间的RRC连接。
进一步地，所述启动模块具体用于采用以下至少一种方式启动或重启所述副链路释放定时器和所述数据不活跃定时器：
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器，不启动或不重启所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述数据不活跃定时器，不启动或不重启所述副链路释放定时器。
进一步地，所述释放模块具体用于执行以下至少一种：
重置MAC层；
停止除第三定时器之外其他所有运行的定时器，所述第三定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因；
进入RRC空闲态或RRC非激活态。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。即本公开的技术方案中，终端可以释放已建立的副链路单播连接，也可以释放已建立的副链路组播连接。
本公开实施例还提供了一种第二终端，如图5所示，包括：
接收模块21，用于接收第一终端发送的副链路连接释放消息；
释放模块22，用于释放与所述第一终端之间的副链路连接。
本实施例中，第二终端在接收到第一终端发送的副链路连接释放消息后，释放与第一终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；通过第一终端的标识和所述第二终端的标识可以使得第二终端准确获知需要释放的副链路连接；
副链路连接释放原因的指示信息，通过副链路连接释放原因的指示信息可以使得第二终端获知副链路连接释放原因。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，所述释放模块具体用于执行以下至少一种：
重置媒体介入控制MAC层；
停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第二终端的高层副链路连接的释放和/或释放原因。
进一步地，还包括：
第二发送模块，用于向所述第一终端发送副链路释放定时器配置，其中，所述副链路释放定时器由所述第二终端配置或由所述第二终端从网络侧配置中获得。
进一步地，还包括：
反馈模块，用于向所述第一终端反馈连接释放响应消息，这样可以方便第一终端在接收到连接释放响应消息后，释放与第二终端之间的副链路连接。
进一步地，所述反馈模块具体用于执行以下至少一种：
通过所述第二终端的物理层向所述第一终端反馈连接释放响应消息；
通过所述第二终端的无线链路控制RLC层向所述第一终端反馈连接释放响应消息；
向所述第一终端反馈连接释放响应消息。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。即本公开的技术方案中，终端可以释放已建立的副链路单播连接，也可以释放已建立的副链路组播连接。
本公开实施例还提供了一种网络侧设备，如图6所示，包括：
配置模块31，用于为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
本实施例中，网络侧设备为第一终端配置或预配置副链路释放定时器，在副链路释放定时器超时后，第一终端释放与第二终端之间的副链路连接，通过本公开的技术方案，能够支持终端在sidelink上释放已建立的连接。
进一步地，所述配置模块具体用于通过专用信令或系统消息为所述第一终端配置所述副链路释放定时器。
进一步地，所述配置模块还用于为所述第一终端配置所述数据不活跃定时器，用于所述第一终端在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
本公开实施例还提供了一种通信设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如上所述的副链路释放方法中的步骤。
该通信设备可以为网络侧设备或终端。
在该通信设备为网络侧设备时，如图7所示，网络侧设备500包括：处理器501、收发机502、存储器503、用户接口504和总线接口，其中：
在本公开实施例中，网络侧设备500还包括：存储在存储器503上并可在处理器501上运行的计算机程序，计算机程序被处理器501、执行时实现如下步骤：为第一终端配置副链路释放定时器。
在图7中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器501代表的一个或多个处理器和存储器503代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机502可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口504还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器501负责管理总线架构和通常的处理，存储器503可以存储处理器501在执行操作时所使用的数据。
进一步地，所述为第一终端配置副链路释放定时器包括：
通过专用信令或系统消息为所述第一终端配置所述副链路释放定时器。
进一步地，计算机程序被处理器501、执行时还实现如下步骤：
为所述第一终端配置所述数据不活跃定时器。
在该通信设备为终端时，如图8所示，该终端600包括但不限于：射频 单元601、网络模块602、音频输出单元603、输入单元604、传感器605、显示单元606、用户输入单元607、接口单元608、存储器609、处理器610、以及电源611等部件。本领域技术人员可以理解，图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
在终端为副链路连接的第一终端时，所述处理器610用于获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，通知所述第一终端的高层。
进一步地，所述通知所述第一终端的高层包括以下至少一项：
通知第一终端的高层所述副链路连接的释放和/或释放原因；
通知第一终端的高层所述副链路释放定时器超时；
通知第一终端的高层所述副链路连接失败；
通知所述第一终端的高层所述第一终端发生了无线链路失败。
进一步地，所述获取网络侧设备配置的副链路释放定时器包括：
获取网络侧设备通过专用信令或系统消息配置的所述副链路释放定时器。
进一步地，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得，所述获取副链路释放定时器包括：
获取由第二终端发送的副链路释放定时器配置。
进一步地，所述副链路释放定时器的时长通过以下至少一种方式确定：
协议规定；
网络侧设备配置或预配置。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；
副链路连接释放原因的指示信息。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，计算机程序被处理器610、执行时还实现如下步骤：
接收所述第二终端反馈的连接释放响应消息；
释放与所述第二终端之间的副链路连接。
进一步地，所述接收所述第二终端反馈的连接释放响应消息包括以下至少一种：
接收所述第二终端的物理层反馈的连接释放响应消息；
接收所述第二终端的无线链路控制RLC层反馈的连接释放响应消息；
接收所述第二终端的连接释放响应消息。
进一步地，所述释放与所述第二终端之间的副链路连接包括：
重置媒体介入控制MAC层；
停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因。
进一步地，计算机程序被处理器610、执行时还实现如下步骤：
获取网络侧设备配置的数据不活跃定时器；
在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
进一步地，采用以下至少一种方式启动或重启所述副链路释放定时器和所述数据不活跃定时器：
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器，不启动或不重启所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
在与网络侧之间进行数据收发后，启动或重启所述数据不活跃定时器，不启动或不重启所述副链路释放定时器。
进一步地，所述释放RRC连接包括：
重置MAC层；
停止除第三定时器之外其他所有运行的定时器，所述第三定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第一终端的高层副链路连接的释放和/或释放原因；
进入RRC空闲态或RRC非激活态。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。
在终端为副链路连接的第二终端时，处理器610用于接收第一终端发送的副链路连接释放消息；释放与所述第一终端之间的副链路连接。
进一步地，所述副链路连接释放消息包括以下信息中的至少一项：
所述第一终端的标识；
所述第二终端的标识；
副链路连接释放原因的指示信息。
进一步地，所述副链路连接释放原因包括以下至少一种：
副链路释放定时器超时；
副链路连接失败。
进一步地，所述释放与所述第一终端之间的副链路连接包括以下至少一种：
重置媒体介入控制MAC层；
停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
释放无线承载以及对应的协议层实体；
通知所述第二终端的高层副链路连接的释放和/或释放原因。
进一步地，计算机程序被处理器610执行时还实现如下步骤：
向所述第一终端发送副链路释放定时器配置，其中，所述副链路释放定时器由所述第二终端配置或由所述第二终端从网络侧配置中获得。
进一步地，计算机程序被处理器610、执行时还实现如下步骤：
向所述第一终端反馈连接释放响应消息。
进一步地，所述向所述第一终端反馈连接释放响应消息包括以下至少一种：
所述第二终端的物理层向所述第一终端反馈连接释放响应消息；
所述第二终端的无线链路控制RLC层向所述第一终端反馈连接释放响应消息；
所述第二终端向所述第一终端反馈连接释放响应消息。
进一步地，所述副链路连接包括副链路单播连接或副链路组播连接。
应理解的是，本公开实施例中，射频单元601可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器610处理；另外，将上行的数据发送给基站。通常，射频单元601包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元601还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块602为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元603可以将射频单元601或网络模块602接收的或者在存储器609中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元603还可以提供与终端600执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元603包括扬声器、蜂鸣器以及受话器等。
输入单元604用于接收音频或视频信号。输入单元604可以包括图形处理器(Graphics Processing Unit，GPU)6041和麦克风6042，图形处理器6041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元606上。经图形处理器6041处理后的图像帧可以存储在存储器609(或其它存储介质)中或者经由射频单元601或网络模块602进行发送。麦克风6042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元601发送到移动通信基站的 格式输出。
终端600还包括至少一种传感器605，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板6061的亮度，接近传感器可在终端600移动到耳边时，关闭显示面板6061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器605还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元606用于显示由用户输入的信息或提供给用户的信息。显示单元606可包括显示面板6061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板6061。
用户输入单元607可用于接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元607包括触控面板6071以及其他输入设备6072。触控面板6071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板6071上或在触控面板6071附近的操作)。触控面板6071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器610，接收处理器610发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板6071。除了触控面板6071，用户输入单元607还可以包括其他输入设备6072。具体地，其他输入设备6072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板6071可覆盖在显示面板6061上，当触控面板6071检测到在其上或附近的触摸操作后，传送给处理器610以确定触摸事件的类 型，随后处理器610根据触摸事件的类型在显示面板6061上提供相应的视觉输出。虽然在图8中，触控面板6071与显示面板6061是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板6071与显示面板6061集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元608为外部装置与终端600连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元608可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端600内的一个或多个元件或者可以用于在终端600和外部装置之间传输数据。
存储器609可用于存储软件程序以及各种数据。存储器609可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器609可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器610是终端的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器609内的软件程序和/或模块，以及调用存储在存储器609内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器610可包括一个或多个处理单元；可选的，处理器610可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器610中。
终端600还可以包括给各个部件供电的电源611(比如电池)，可选的，电源611可以通过电源管理系统与处理器610逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端600包括一些未示出的功能模块，在此不再赘述。
本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储 介质上存储有计算机程序，所述计算机程序被处理器执行时实现上所述的副链路释放方法中的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白，本公开实施例的实施例可提供为方法、装置、或计算机程序产品。因此，本公开实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开实施例是参照根据本公开实施例的方法、用户设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理用户设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理用户设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理用户设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理用户设备上，使得在计算机或其他可编程用户设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程用户设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本公开实施例的可选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括可选实施例以及落入本公开实施例范围的所有变更和修改。
还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者用户设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者用户设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者用户设备中还存在另外的相同要素。
以上所述的是本公开的可选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (33)

  1. 一种副链路释放方法，应用于第一终端，包括：
    获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
    在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
    在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
  2. 根据权利要求1所述的方法，其特征在于，所述通知所述第一终端的高层包括以下至少一项：
    通知所述第一终端的高层所述副链路连接的释放和/或释放原因；
    通知所述第一终端的高层所述副链路释放定时器超时；
    通知所述第一终端的高层所述副链路连接失败；
    通知所述第一终端的高层所述第一终端发生了无线链路失败。
  3. 根据权利要求1所述的副链路释放方法，其中，所述获取网络侧设备配置的副链路释放定时器包括：
    获取网络侧设备通过专用信令或系统消息配置的所述副链路释放定时器。
  4. 根据权利要求1所述的副链路释放方法，其中，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得，所述获取副链路释放定时器包括：
    获取由第二终端发送的副链路释放定时器配置。
  5. 根据权利要求1所述的副链路释放方法，其中，所述副链路释放定时器的时长通过以下至少一种方式确定：
    协议规定；
    网络侧设备配置或预配置。
  6. 根据权利要求1所述的副链路释放方法，其中，所述副链路连接释放消息包括以下信息中的至少一项：
    所述第一终端的标识；
    所述第二终端的标识；
    副链路连接释放原因的指示信息。
  7. 根据权利要求6所述的副链路释放方法，其中，所述副链路连接释放原因包括以下至少一种：
    副链路释放定时器超时；
    副链路连接失败。
  8. 根据权利要求1所述的副链路释放方法，还包括以下至少之一：
    接收所述第二终端反馈的连接释放响应消息，释放与所述第二终端之间的副链路连接；
    释放与所述第二终端之间的副链路连接。
  9. 根据权利要求8所述的副链路释放方法，其中，所述接收所述第二终端反馈的连接释放响应消息包括以下至少一种：
    接收所述第二终端的物理层反馈的连接释放响应消息；
    接收所述第二终端的无线链路控制RLC层反馈的连接释放响应消息；
    接收所述第二终端的连接释放响应消息。
  10. 根据权利要求8所述的副链路释放方法，其中，所述释放与所述第二终端之间的副链路连接包括以下至少之一：
    重置媒体介入控制MAC层；
    停止除第一定时器之外其他所有运行的定时器，所述第一定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
    释放无线承载以及对应的协议层实体；
    通知所述第一终端的高层副链路连接的释放和/或释放原因。
  11. 根据权利要求1-10中任一项所述的副链路释放方法，还包括：
    获取网络侧设备配置的数据不活跃定时器；
    在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
  12. 根据权利要求11所述的副链路释放方法，其中，采用以下至少一种方式启动或重启所述副链路释放定时器和所述数据不活跃定时器：
    在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
    在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器，不启动或不重启所述数据不活跃定时器；
    在与网络侧之间进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
    在与网络侧之间进行数据收发后，启动或重启所述数据不活跃定时器，不启动或不重启所述副链路释放定时器。
  13. 根据权利要求11所述的副链路释放方法，其中，所述释放RRC连接包括以下至少之一：
    重置MAC层；
    停止除第三定时器之外其他所有运行的定时器，所述第三定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
    释放无线承载以及对应的协议层实体；
    通知所述第一终端的高层副链路连接的释放和/或释放原因；
    进入RRC空闲态或RRC非激活态。
  14. 根据权利要求1所述的副链路释放方法，其中，
    所述副链路连接包括副链路单播连接或副链路组播连接。
  15. 一种副链路释放方法，应用于第二终端，包括：
    接收第一终端发送的副链路连接释放消息；
    释放与所述第一终端之间的副链路连接。
  16. 根据权利要求15所述的副链路释放方法，其中，所述副链路连接释放消息包括以下信息中的至少一项：
    所述第一终端的标识；
    所述第二终端的标识；
    副链路连接释放原因的指示信息。
  17. 根据权利要求16所述的副链路释放方法，其中，所述副链路连接释放原因包括以下至少一种：
    副链路释放定时器超时；
    副链路连接失败。
  18. 根据权利要求15所述的副链路释放方法，其中，所述释放与所述第一终端之间的副链路连接包括以下至少一种：
    重置媒体介入控制MAC层；
    停止除第二定时器之外其他所有运行的定时器，所述第二定时器为一个或多个由所述第一终端配置或第二终端配置或基站配置或协议约定的定时器；
    释放无线承载以及对应的协议层实体；
    通知所述第二终端的高层副链路连接的释放和/或释放原因。
  19. 根据权利要求15所述的副链路释放方法，还包括：
    向所述第一终端发送副链路释放定时器配置，其中，所述副链路释放定时器由所述第二终端配置或由所述第二终端从网络侧配置中获得。
  20. 根据权利要求15所述的副链路释放方法，还包括：
    向所述第一终端反馈连接释放响应消息。
  21. 根据权利要求20所述的副链路释放方法，其中，所述向所述第一终端反馈连接释放响应消息包括以下至少一种：
    所述第二终端的物理层向所述第一终端反馈连接释放响应消息；
    所述第二终端的无线链路控制RLC层向所述第一终端反馈连接释放响应消息；
    所述第二终端向所述第一终端反馈连接释放响应消息。
  22. 根据权利要求15-21中任一项所述的副链路释放方法，其中，所述副链路连接包括副链路单播连接或副链路组播连接。
  23. 一种副链路释放方法，应用于网络侧设备，包括：
    为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
  24. 根据权利要求23所述的副链路释放方法，其中，所述为第一终端配置副链路释放定时器包括：
    通过专用信令或系统消息为所述第一终端配置所述副链路释放定时器。
  25. 根据权利要求23所述的副链路释放方法，还包括：
    为所述第一终端配置数据不活跃定时器，用于所述第一终端在所述数据 不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
  26. 一种第一终端，包括：
    获取模块，用于获取副链路释放定时器，其中，所述副链路释放定时器由网络侧设备配置或预配置，或者，所述副链路释放定时器由第二终端配置或由第二终端从网络侧配置中获得；
    启动模块，用于在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器；
    发送模块，用于在所述副链路释放定时器超时后，向所述第二终端发送副链路连接释放消息，或者，通知所述第一终端的高层。
  27. 根据权利要求26所述的第一终端，其中，
    所述获取模块还用于获取网络侧设备配置的数据不活跃定时器；
    还包括：
    释放模块，用于在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
  28. 根据权利要求27所述的第一终端，其中，所述启动模块具体用于采用以下至少一种方式启动或重启所述副链路释放定时器和所述数据不活跃定时器：
    在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
    在与第二终端之间的副链路连接上进行数据收发后，启动或重启所述副链路释放定时器，不启动或不重启所述数据不活跃定时器；
    在与网络侧之间进行数据收发后，启动或重启所述副链路释放定时器和所述数据不活跃定时器；
    在与网络侧之间进行数据收发后，启动或重启所述数据不活跃定时器，不启动或不重启所述副链路释放定时器。
  29. 一种第二终端，包括：
    接收模块，用于接收第一终端发送的副链路连接释放消息；
    释放模块，用于释放与所述第一终端之间的副链路连接。
  30. 一种网络侧设备，包括：
    配置模块，用于为第一终端配置副链路释放定时器，用于所述第一终端在所述副链路释放定时器超时后，释放副链路连接。
  31. 根据权利要求30所述的网络侧设备，其中，所述配置模块还用于为所述第一终端配置数据不活跃定时器，用于所述第一终端在所述数据不活跃定时器超时后，释放和网络侧之间的无线资源控制RRC连接。
  32. 一种通信设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求1至14中任一项所述的副链路释放方法中的步骤或实现如权利要求15至22中任一项所述的副链路释放方法中的步骤或如权利要求23至25中任一项所述的副链路释放方法中的步骤。
  33. 一种计算机可读存储介质，所述计算机可读存储介质上存储有程序，所述程序被处理器执行时实现如权利要求1至14中任一项所述的副链路释放方法中的步骤或实现如权利要求15至22中任一项所述的副链路释放方法中的步骤或如权利要求23至25中任一项所述的副链路释放方法中的步骤。
PCT/CN2019/114668 2018-11-01 2019-10-31 副链路释放方法、终端及网络侧设备 Ceased WO2020088584A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19880605.1A EP3876664A4 (en) 2018-11-01 2019-10-31 Sidelink release method, terminal and network side device
KR1020217016328A KR102710697B1 (ko) 2018-11-01 2019-10-31 사이드링크 해제 방법 및 단말측 장치
US17/245,081 US12185416B2 (en) 2018-11-01 2021-04-30 Sidelink release method, terminal and network side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811297557.0A CN111132381A (zh) 2018-11-01 2018-11-01 副链路释放方法、终端及网络侧设备
CN201811297557.0 2018-11-01

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/245,081 Continuation US12185416B2 (en) 2018-11-01 2021-04-30 Sidelink release method, terminal and network side device

Publications (1)

Publication Number Publication Date
WO2020088584A1 true WO2020088584A1 (zh) 2020-05-07

Family

ID=70463500

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/114668 Ceased WO2020088584A1 (zh) 2018-11-01 2019-10-31 副链路释放方法、终端及网络侧设备

Country Status (5)

Country Link
US (1) US12185416B2 (zh)
EP (1) EP3876664A4 (zh)
KR (1) KR102710697B1 (zh)
CN (1) CN111132381A (zh)
WO (1) WO2020088584A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11576225B2 (en) * 2019-12-16 2023-02-07 Qualcomm Incorporated Sidelink unicast connection states
WO2021185437A1 (en) * 2020-03-18 2021-09-23 Telefonaktiebolaget Lm Ericsson (Publ) Determination of operational state
KR20210140977A (ko) * 2020-05-14 2021-11-23 삼성전자주식회사 무선 통신 시스템에서 사이드링크 mac 리셋을 처리하기 위한 장치 및 방법
CN111642032B (zh) * 2020-05-19 2023-06-27 广东小天才科技有限公司 一种配置rrc状态的方法及网络设备
US20210409984A1 (en) * 2020-06-30 2021-12-30 Samsung Electronics Co., Ltd. Method of monitoring data inactivity and an electronic device performing the method
CN113873683B (zh) * 2020-06-30 2024-11-15 华为技术有限公司 一种通信方法及装置
CN113873580B (zh) * 2020-06-30 2024-11-22 华为技术有限公司 通信的方法和装置
KR20230039611A (ko) * 2020-07-17 2023-03-21 엘지전자 주식회사 데이터 비활성 타이머를 기반으로 중계를 수행하는 방법 및 장치
CN113973285B (zh) * 2020-07-24 2025-05-09 夏普株式会社 用户设备执行的方法以及用户设备
KR102700303B1 (ko) * 2020-09-01 2024-08-30 엘지전자 주식회사 사이드링크 릴레잉에서 이종 네트워크 재선택을 수행하기 위한 방법 및 장치
EP4278836A4 (en) * 2021-01-13 2025-01-22 Qualcomm Incorporated Relay adaptation layer configuration for sidelink interface
WO2023039791A1 (en) * 2021-09-16 2023-03-23 Qualcomm Incorporated Rrc timer for layer 2 ue-to-network relay
US20240414810A1 (en) * 2021-09-29 2024-12-12 Nec Corporation Method, device and computer storage medium of communication
CN116209099A (zh) * 2021-11-29 2023-06-02 华为技术有限公司 侧行链路通信方法和装置
US12396044B2 (en) * 2022-06-03 2025-08-19 Qualcomm Incorporated Radio link management for sidelink carrier aggregation component carriers
KR20250034449A (ko) * 2022-07-08 2025-03-11 베이징 시아오미 모바일 소프트웨어 컴퍼니 리미티드 Sidelink 설정 방법, 장치, 저장 매체 및 단말
CN117062250A (zh) * 2023-08-15 2023-11-14 深圳市广和通无线通信软件有限公司 一种数据链路的自适应调整方法、装置、设备和介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法
US20180103460A1 (en) * 2016-10-06 2018-04-12 Samsung Electronics Co., Ltd. Method and system for managing wireless communication in vehicle-to-anything communication system
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9693265B2 (en) * 2012-01-26 2017-06-27 Nokia Technologies Oy Method and apparatus for mobile terminal mobility
WO2015163624A1 (en) * 2014-04-24 2015-10-29 Lg Electronics Inc. Method for releasing a sidelink radio bearer for d2d communication system and device therefor
CN107771410B (zh) * 2015-05-26 2021-03-19 Lg 电子株式会社 在无线通信系统中通过ue实现的解除链接方法和使用所述方法的ue
EP3397003B1 (en) * 2016-01-25 2020-07-01 Kyocera Corporation Communication method, wireless terminal and base station
WO2017135784A1 (ko) * 2016-02-05 2017-08-10 엘지전자 주식회사 무선 통신 시스템에서 단말에 의해 수행되는 v2x 동작 방법 및 상기 방법을 이용하는 단말
CN108633074B (zh) * 2017-03-23 2022-05-13 华硕电脑股份有限公司 无线通信系统中报告侧链路服务的辅助信息的方法和设备
US11219088B2 (en) * 2017-09-28 2022-01-04 Lg Electronics Inc. Method and apparatus for configuring release cause
CN110944306A (zh) * 2018-09-25 2020-03-31 维沃移动通信有限公司 一种旁链路的链路释放方法及终端

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107645774A (zh) * 2016-07-20 2018-01-30 普天信息技术有限公司 V2x网络中调度pc5口资源的确认方法
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
US20180103460A1 (en) * 2016-10-06 2018-04-12 Samsung Electronics Co., Ltd. Method and system for managing wireless communication in vehicle-to-anything communication system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Sidelink Resource Allocation Mechanism for NR V2X", 3GPP DRAFT; R1-1811904, 12 October 2018 (2018-10-12), Chengdu, China, pages 1 - 13, XP051519227 *
MEDIATEK INC: "On NR Uu to Support NR V2X Services.", 3GPP DRAFT; R1-1808283, 24 August 2018 (2018-08-24), Gothenburg, Sweden, pages 1 - 3, XP051515667 *
See also references of EP3876664A4 *

Also Published As

Publication number Publication date
KR102710697B1 (ko) 2024-09-25
EP3876664A4 (en) 2021-12-29
KR20210083321A (ko) 2021-07-06
US12185416B2 (en) 2024-12-31
EP3876664A1 (en) 2021-09-08
CN111132381A (zh) 2020-05-08
US20210251039A1 (en) 2021-08-12

Similar Documents

Publication Publication Date Title
WO2020088584A1 (zh) 副链路释放方法、终端及网络侧设备
CN111800837B (zh) 中继重选方法、设备及介质
JP7246513B2 (ja) リソース割り当て方法、リリース方法、端末及びネットワーク機器
KR102473470B1 (ko) 사이드링크의 링크 실패 검사 방법 및 단말기
CN113038634B (zh) 唤醒信号配置方法、唤醒信号处理方法及相关设备
US12114200B2 (en) Sidelink connection control method, terminal, and network side device
WO2021129508A1 (zh) 唤醒信号处理方法、唤醒信号配置方法及相关设备
CN110730504A (zh) 一种寻呼指示方法、装置及系统
WO2020143754A1 (zh) 连接建立方法、终端设备及网络设备
EP4142387A1 (en) Paging response method, terminal, and network device
WO2020088585A1 (zh) 副链路连接建立、资源分配方法、终端及网络侧设备
WO2021027680A1 (zh) 数据接收方法、发送方法、终端及网络设备
WO2020063263A1 (zh) 旁链路的链路释放方法及终端
CN113301601A (zh) 信息上报方法、用户设备及网络侧设备
WO2021057647A1 (zh) 节能信号接收方法、节能信号发送方法及相关设备
CN111050422B (zh) 一种非连续接收的控制方法及终端
EP4087283A1 (en) Multicast service transmission method, transmission processing method, and related device
WO2020001424A1 (zh) 载波聚合配置信息的处理方法和终端
WO2019056959A1 (zh) 完整性保护方法、终端和基站
CN113259077B (zh) 带宽部分激活或去激活方法、副链路连接释放方法及设备
CN111436026B (zh) 副链路组播通信的配置方法和终端
CN111836379B (zh) 辅助信息上报方法、配置方法、终端和网络侧设备
CN113453162B (zh) 业务的接收方法、配置方法、终端和网络侧设备
CN111615085A (zh) 资源获取方法、第一终端和第二终端
WO2020024876A1 (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: 19880605

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217016328

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019880605

Country of ref document: EP

Effective date: 20210601