WO2019029661A1 - 一种传输方法和网络设备 - Google Patents

一种传输方法和网络设备 Download PDF

Info

Publication number
WO2019029661A1
WO2019029661A1 PCT/CN2018/099819 CN2018099819W WO2019029661A1 WO 2019029661 A1 WO2019029661 A1 WO 2019029661A1 CN 2018099819 W CN2018099819 W CN 2018099819W WO 2019029661 A1 WO2019029661 A1 WO 2019029661A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
network node
message
information
network
Prior art date
Application number
PCT/CN2018/099819
Other languages
English (en)
French (fr)
Inventor
王瑞
戴明增
罗海燕
徐小英
耿婷婷
张宏卓
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to BR112020002752-9A priority Critical patent/BR112020002752A2/pt
Priority to EP18844764.3A priority patent/EP3570584B1/en
Priority to ES18844764T priority patent/ES2901695T3/es
Priority to EP21202599.3A priority patent/EP3998796A1/en
Priority to JP2020508042A priority patent/JP7139412B2/ja
Priority to CA3072715A priority patent/CA3072715C/en
Priority to KR1020227015572A priority patent/KR102585617B1/ko
Priority to RU2020109982A priority patent/RU2780471C2/ru
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201880013339.1A priority patent/CN110326321B/zh
Priority to KR1020207007175A priority patent/KR102397469B1/ko
Publication of WO2019029661A1 publication Critical patent/WO2019029661A1/zh
Priority to US16/449,709 priority patent/US11178538B2/en
Priority to US17/222,745 priority patent/US20210227378A1/en
Priority to JP2022142248A priority patent/JP7394940B2/ja

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • 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
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of field communication and, more particularly, to a transmission method and a network device.
  • the base station can be composed of a Centralized Unit (CU) and a Distributed Unit (DU), that is, in the original access network.
  • CU Centralized Unit
  • DU Distributed Unit
  • the function of the base station is split, and part of the functions of the base station are deployed in one CU, and the remaining functions are deployed in multiple DUs, and multiple DUs share one CU, which can save cost and facilitate network expansion.
  • the shards of the CU and the DU can be split according to the protocol stack.
  • One possible way is to deploy the Radio Resource Control (RRC) and the Packet Data Convergence Protocol (PDCP) layer in the CU.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • DU Physical layer
  • the network device After the terminal device accesses the cell, the network device establishes the corresponding context of the terminal device, and after the terminal device state changes, the network device processes the terminal device context accordingly. For example, when the terminal device is connected from the connected state to the idle state, the network device releases the context of the terminal device.
  • a new RRC state/RRC sub-state is introduced for the terminal device, which is called an inactive state (also called a third state).
  • the CU needs to notify the DU to perform linkage. Context processing, there is currently no corresponding solution to solve the context management method of the CU and the DU to the terminal device when the network device functions are separated.
  • the network device finds that the radio link failure (RLF) of the terminal device and the handover (Hand Over, HO) scenario have no corresponding solution to solve the context management method of the CU and the DU to the terminal device.
  • RLF radio link failure
  • Hand Over, HO handover
  • the transmission method and the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • a transmission method includes: receiving, by a first network node, a first message sent by a terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; the first network The node sends the first message to the first system; the first network node receives the second message sent by the first system according to the first message, where the second message includes the identifier information of the terminal device, and the identifier information of the terminal device.
  • the first network node obtains context information of the terminal device saved by the first network node, or the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the first network node receives a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; the first network node sends the second network node to the second network node. a first message; the first network node receives the second message sent by the second network node according to the first message, where the second message includes the identifier information of the terminal device, and the identifier information of the terminal device is used by the first network
  • the node acquires context information of the terminal device saved by the first network node, or the second message includes context information of the terminal device.
  • the second network node is a control plane node of the first system.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the method before the first network node receives the first message sent by the terminal device, the method further includes: the first network node receiving the first system sending And the first network node stores the context information of the terminal device according to the third message, or releases the context information of the terminal device.
  • the method before the first network node receives the first message sent by the terminal device, the method further includes: receiving, by the first network node, an indication message sent by the first system, where the indication message is used to indicate the The terminal device enters an inactive state; the first network node sends the indication message to the terminal device.
  • the first network node sends the first message to the first system, including: Transmitting, by the network node, the first message to the second network node, where the second network node is a control plane node of the first system, where the first network node receives the second network sent by the first system according to the first message
  • the message includes: the first network node receiving the second message sent by the second network node according to the first message.
  • the identifier information of the terminal device The first interface is used for the first network node and the at least one of the recovery identification information of the terminal device, the identification information of the terminal device of the first interface, the temporary identifier information of the cell radio network, and the physical cell identifier information. Data transmission and information interaction between the first systems.
  • the context information of the terminal device At least one of a radio resource control configuration, a data radio bearer parameter, identification information of the terminal device, cell identity information, and connection information of the first interface, where the first interface is used by the first network node and the first system Data transfer and information interaction between.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • a transmission method includes: receiving, by a first system, a first message from a terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; And sending, by the first network node, a second message, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to acquire the saved by the first network node Context information of the terminal device, or the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the second network node receives a first message from the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; and the second network node is configured according to the first message, Sending a second message to the first network node, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the context information of the terminal device saved by the first network node, Alternatively, the second message includes context information of the terminal device.
  • the second network node is a control plane node of the first system.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the first system receives the first message from the terminal device, including: the second network node receives the first message from the terminal device,
  • the second network node is a control plane node of the first system, where the first system sends a second message to the first network node according to the first message, including: the second network node according to the first message, Sending the second message to the first network node.
  • the method further includes: the second network node sends a fourth message to the third network node, where the fourth The message includes the identification information of the terminal device, the identifier information of the terminal device is used by the third network node to obtain the context information of the terminal device saved by the third network node, or the fourth message includes the context information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the method before the first system receives the first message from the terminal device, the method further includes: the first system sending an indication message to the first network node, where the indication message is used to indicate the terminal The device enters an inactive state; the first network node sends the indication message to the terminal device.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • a third aspect provides a transmission method, where the method includes: receiving, by a third network node, a fourth message sent by a second network node, where the fourth message includes identifier information of the terminal device, where the identifier information of the terminal device is used.
  • the third network node acquires context information of the terminal device saved by the first network node, or the fourth message includes context information of the terminal device; and the third network node establishes the terminal device according to the fourth message.
  • Context information, the context information of the terminal device is context information of the access layer; wherein the second network node is a control plane node of the first system, and the third network node is a user plane node of the first system.
  • the third network node is a user plane node of the first system.
  • the method before the third network node receives the fourth message sent by the second network node, the method further includes: the third network node receiving the second The fifth message sent by the network node; the third network node stores the context information of the terminal device according to the fifth message, or releases part of the context information of the terminal device.
  • the context information of the terminal device includes connection information of the second interface, connection information of the third interface, and fourth At least one of connection information of an interface, a radio resource control configuration, a data radio bearer parameter, current security context information, a packet data convergence protocol state, cell identification information, and identification information for identifying the terminal device, the second The interface is used for data transmission and/or information interaction between the third network node and the core network, and the third interface is used for data transmission between the third network node and the second network node. Or information interaction, the fourth interface is used for data transmission and/or information interaction between the third network node and the first network node.
  • the terminal device context information saved at the third network node includes connection information of the first interface, connection information of the second interface, current security context information, packet data convergence protocol status, and identification
  • the identifier information of the terminal device, and the context information of the terminal device released by the third network node includes at least one of a packet data convergence protocol state and connection information of the fourth interface.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • a fourth aspect provides a transmission method, where the method includes: receiving, by a first network node, a first message sent by a terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; the first network node Determining the identification information of the terminal device according to the first message; the first network node acquiring the context information of the terminal device saved by the first network node according to the identifier information of the terminal device, or the first network node is configured according to the The identifier information of the terminal device is received by the first system, where the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the first network node receives a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; the first network node determines, according to the first message, Identification information of the terminal device; the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device, or the first network node according to the identification information of the terminal device Receiving a second message sent by the second network node, where the second message includes context information of the terminal device.
  • the second network node is a control plane node of the first system.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the method before the first network node receives the first message sent by the terminal device, the method further includes: the first network node receiving the first system sending And the first network node stores the context information of the terminal device according to the third message, or releases the context information of the terminal device.
  • the method before the first network node receives the first message sent by the terminal device, the method further includes: receiving, by the first network node, an indication message sent by the first system, where the indication message is used to indicate the The terminal device enters an inactive state; the first network node sends the indication message to the terminal device.
  • the first network node receives, according to the identifier information of the terminal device, the first system sends
  • the second message includes: the first network node receiving, according to the identifier information of the terminal device, a second message sent by the second network node, where the second network node is a control plane node of the first system.
  • the identifier information of the terminal device The first interface is used for the first network node and the at least one of the recovery identification information of the terminal device, the identification information of the terminal device of the first interface, the temporary identifier information of the cell radio network, and the physical cell identifier information. Data transmission and information interaction between the first systems.
  • the context information of the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, and connection information of the first interface, where the first interface is used for data transmission and information interaction between the first network node and the first system.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control function layer; and/or the first system includes a packet data convergence protocol layer, a service data adaptation layer, and a radio resource At least one of the control layer functions.
  • a fifth aspect provides a transmission method, where the method includes: receiving, by a first system, a sixth message sent by a first network node, where the sixth message includes identifier information of the terminal device, where the sixth message is used to indicate the first
  • the system obtains the context information of the terminal device saved by the first system; the first system sends a second message to the first network node according to the second message, where the second message includes context information of the terminal device, where The context information of the terminal device is the context information of the access layer.
  • the second network node receives the sixth message sent by the first network node, where the sixth message includes the identifier information of the terminal device, where the fifth message is used to indicate that the second network node obtains the Context information of the terminal device saved by the network node; the second network node sends a second message to the first network node according to the second message, where the second message includes identification information of the terminal device, where the terminal device The identifier information is used by the first network node to obtain context information of the terminal device saved by the first network node, or the second message includes context information of the terminal device.
  • the second network node is a control plane node of the first system.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the first system receives the sixth message sent by the first network node, where the second network node receives the sixth a message that the second network node is a control plane node of the first system, where the first system sends a second message to the first network node according to the sixth message, including: the second network node according to the Six messages, the second message is sent to the first network node.
  • the method before the first system receives the sixth message sent by the first network node, the method further includes: the first system sending an indication message to the first network node, where the indication message is used to indicate the The terminal device enters an inactive state; the first network node sends the indication message to the terminal device.
  • the method further includes: the second network node sends a seventh message to the third network node, where the seventh The message includes the identification information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the context information of the terminal device saved by the first network node, or the seventh message includes the context information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control layer function; and/or the first system includes a packet data convergence protocol layer, a service data adaptation layer, and a radio resource Control at least one of the functional layers.
  • a sixth aspect provides a transmission method, the method comprising: determining, by a first network node, a radio link failure between the first network node and the terminal device, where the first network node includes a radio link layer control protocol layer At least one of the media intervention control layer and the physical layer function; the first network node sends a sixth message to the first system, where the sixth message is used to indicate the first network node to the second network node A wireless link failure occurs with the terminal device, and the second network node includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the method further includes: receiving, by the first network node, a seventh message sent by the first system, where the seventh message is used to indicate the first The network node releases the context of the terminal device.
  • the first network node sends a sixth message to the first system, including: A network node sends the sixth message to the second network node, where the second network node is a control plane node of the first system.
  • the sixth message includes At least one of identification information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • a seventh aspect provides a transmission method, the method comprising: receiving, by a first system, a sixth message sent by a first network node, where the sixth message is used to indicate to the first system that the first network node and the terminal device
  • the wireless link fails, the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function, and the first system includes a packet data convergence protocol layer, a service data adaptation layer, and At least one of a radio resource control layer function;
  • the first system sets a timer according to the sixth message; if the timer expires, the first system sends a seventh message to the first network node, the seventh message And indicating, by the first network node, the context of the terminal device is released; if the timer does not time out, the first system receives the RRC connection message, and the first system stops the timer.
  • the first system receives the sixth message that is sent by the first network node, that the second network node receives the sixth
  • the second network node is a control plane node of the first system.
  • the first system sets a timer according to the sixth message, and the second network node sets a timer according to the sixth message.
  • the method further includes: the timer expires, the second network node sends an eighth to the third network node And the eighth message is used to indicate that the third network node releases part of the context information of the terminal device, where the third network node is a user plane node of the first system.
  • the sixth message includes the terminal At least one of identification information of the device, radio link failure indication information, and a cell radio network temporary identifier.
  • the eighth aspect provides a network device, where the network device includes: a transceiver module, configured to receive a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; and a processing module, The transceiver module is configured to send the first message to the first system; the transceiver module is further configured to receive a second message that is sent by the first system according to the first message, where the second message includes identifier information of the terminal device, The identifier information of the terminal device is used by the first network node to obtain the context information of the terminal device saved by the first network node, or the second message includes the context information of the terminal device, where the context information of the terminal device is Intrusion context information.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is further configured to receive a third message that is sent by the first system, where the first network node stores the terminal according to the third message.
  • the transceiver module is further configured to receive an indication message sent by the first system, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; the first network node The indication message is sent to the terminal device.
  • the transceiver module is configured to send the first message to the second network node, and receive the The second message sent by the second network node according to the first message; wherein the second network node is a control plane node of the first system.
  • the identifier information of the terminal device The first interface is used for the first network node and the at least one of the recovery identification information of the terminal device, the identification information of the terminal device of the first interface, the temporary identifier information of the cell radio network, and the physical cell identifier information. Data transmission and information interaction between the first systems.
  • the context information of the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, and connection information of the first interface, where the first interface is used for data transmission and information interaction between the first network node and the first system.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • a network device includes: a transceiver module, configured to receive a first message from the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; And sending, by the first network node, a second message, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to acquire the first network node.
  • the context information of the terminal device is saved, or the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is a transceiver module of the second network node, and the second network node is a control plane node of the first system.
  • the transceiver module is further configured to send a fourth message to the third network node, where the fourth message includes the terminal Identification information of the device, the identifier information of the terminal device is used by the third network node to obtain context information of the terminal device saved by the third network node, or the second message includes context information of the terminal device;
  • the third network node is a user plane node of the first system.
  • the transceiver module is further configured to send an indication message to the first network node, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; the first network node sends The terminal device sends the indication message.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • a network device includes: a transceiver module, configured to receive a fourth message sent by the second network node, where the fourth message includes identifier information of the terminal device, and identifier information of the terminal device.
  • the third network node is configured to acquire the context information of the terminal device that is saved by the first network node, or the fourth message includes the context information of the terminal device, and the processing module is configured to establish the terminal according to the fourth message.
  • Context information of the device, the context information of the terminal device is context information of the access layer; wherein the second network node is a control plane node of the first system, and the third network node is a user plane node of the first system.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is further configured to receive a fifth message that is sent by the second network node, where the processing module is further configured to store according to the fifth message.
  • the context information of the terminal device includes connection information of the second interface, connection information of the third interface, and fourth At least one of connection information of an interface, a radio resource control configuration, a data radio bearer parameter, current security context information, a packet data convergence protocol state, cell identification information, and identification information for identifying the terminal device, the second The interface is used for data transmission and/or information interaction between the third network node and the core network, and the third interface is used for data transmission between the third network node and the second network node. Or information interaction, the fourth interface is used for data transmission and/or information interaction between the third network node and the first network node.
  • the first network node includes At least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function Kind.
  • the eleventh aspect provides a network device, where the network device includes: a transceiver module, configured to receive a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; And determining, according to the first message, identifier information of the terminal device; the processing module is further configured to acquire context information of the terminal device saved by the first network node according to the identifier information of the terminal device, or the processing The module is further configured to receive, according to the identifier information of the terminal device, a second message sent by the first system, where the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • a transceiver module configured to receive a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device; And determining, according to the first message, identifier information of the terminal device; the processing module is further configured to acquire context information of the terminal device saved by the first network node
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is further configured to receive a third message that is sent by the first system, and the processing module is further configured to: The context information of the terminal device is stored, or the context information of the terminal device is released.
  • the transceiver module further receives and receives an indication message sent by the first system, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; and sends the Indicate the message.
  • the processing module is a processing module of the second network node, the second network The node is the control plane node of the first system.
  • the terminal device The identification information is at least one of the recovery identification information of the terminal device, the identification information of the terminal device of the first interface, the temporary identifier information of the cell radio network, and the physical cell identifier information, where the first interface is used for the first network. Data transmission and information interaction between the node and the first system.
  • the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, and a connection information of the first interface, where the first interface is used for data transmission and information interaction between the first network node and the first system. .
  • the first possible to the fourth possible implementation manner of the eleventh aspect in the fifth possible implementation manner of the eleventh aspect, includes at least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control function layer; and/or the first system includes a packet data convergence protocol layer and a service data adaptation layer. And at least one of the radio resource control layer functions.
  • a network device includes: a transceiver module, configured to receive a sixth message sent by the first network node, where the sixth message includes identifier information of the terminal device, where the sixth message is used And acquiring, by the first system, the context information of the terminal device saved by the first system; the processing module, configured to send, according to the sixth message, a second message to the first network node, where the second message includes a context of the terminal device Information, the context information of the terminal device is context information of the access layer.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is a transceiver module of the second network node
  • the processing module is a processing module of the second network node
  • the second network The node is the control plane node of the first system.
  • the transceiver module is further configured to send a seventh message to the third network node, where the seventh message includes The identification information of the terminal device, the identifier information of the terminal device is used by the first network node to obtain the context information of the terminal device saved by the first network node, or the seventh message includes the context information of the terminal device;
  • the third network node is a user plane node of the first system.
  • the first possible implementation of the first and second possible implementations of the twelfth aspect in the third possible implementation of the twelfth aspect, includes at least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control layer function; and/or the first system includes a packet data convergence protocol layer and a service data adaptation layer. And at least one of the radio resource control function layers.
  • a network device includes: a processing module, configured to determine that a radio link failure occurs between the first network node and the terminal device, where the first network node includes a radio link layer At least one of a control protocol layer, a media intervention control layer, and a physical layer function; the transceiver module is configured to send a sixth message to the first system, where the sixth message is used to indicate the first network to the second network node A radio link failure occurs between the node and the terminal device, and the second network node includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is further configured to receive a seventh message sent by the first system, where the seventh message is used to indicate the first network node Release the context of the terminal device.
  • the transceiver module is a transceiver module of the second network node, where the processing module is a processing module of the second network node, the second network node being a control plane node of the first system.
  • the The six message includes at least one of identification information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • a network device includes: a transceiver module, configured to receive a sixth message sent by the first network node, where the sixth message is used to indicate the first network node to the first system A wireless link failure occurs with the terminal device, where the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function, where the first system includes a packet data convergence protocol layer, At least one of a service data adaptation layer and a radio resource control layer function; a processing module, configured to set a timer according to the sixth message; if the timer expires, the first system sends the first network node to the first network node Seventh message, the seventh message is used to indicate that the first network node releases the context of the terminal device; if the timer does not time out, the first system receives the RRC connection message, and the first system stops the timer.
  • a transceiver module configured to receive a sixth message sent by the first network node, where the sixth message is used to indicate the first
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • the transceiver module is a transceiver module of the second network node
  • the processing module is a processing module of the second network node
  • the second network node is The control plane node of the first system.
  • the transceiver module is further configured to: the timer expires, and send an eighth message to the third network node.
  • the eighth message is used to indicate that the third network node releases the context information of the terminal device, where the third network node is a user plane node of the first system.
  • the sixth message At least one of identification information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier is included.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for And the method of any one of the possible implementations of the first aspect, wherein the at least one processor invokes the instruction stored in the memory, The processing operations performed by the network device in the method of the first aspect and any one of the possible implementation manners of the first aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for And the method of any one of the possible implementations of the second aspect and the second aspect, wherein the at least one processor invokes the instruction stored in the memory, The processing operation performed by the network device in the method in any one of the possible implementation manners of the second aspect and the second aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for The method of any one of the third aspect and the third aspect, wherein the at least one processor invokes the instruction stored in the memory, The processing operations performed by the network device in the method in any one of the possible implementations of the third aspect and the third aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for And the method of any one of the possible implementations of the fourth aspect and the fourth aspect, wherein the at least one processor invokes the instruction stored in the memory, The processing operations performed by the network device in the method in any one of the possible implementations of the fourth aspect and the fourth aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for And the method of any one of the possible implementations of the fifth aspect and the fifth aspect, wherein the at least one processor invokes the instruction stored in the memory, And performing the processing operations performed by the network device in the method in any one of the possible implementation manners of the fifth aspect and the fifth aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver being for And the method of any one of the possible implementations of the sixth aspect and the sixth aspect, wherein the at least one processor invokes the instruction stored in the memory, The processing operation performed by the network device in the method in any one of the possible implementation manners of the sixth aspect and the sixth aspect.
  • a network device comprising a memory, a transceiver, and at least one processor, the memory, the transceiver, and the at least one processor being interconnected by a line, the transceiver And the method of any one of the seventh aspect and the seventh aspect, wherein the at least one processor invokes the instruction stored in the memory And performing the processing operations performed by the network device in the method in any one of the possible implementation manners of the seventh aspect and the seventh aspect.
  • a chip system for use in a network device, the chip system comprising: at least one processor, at least one memory, and an interface circuit, wherein the interface circuit is responsible for information interaction between the chip system and the outside world
  • the at least one memory, the interface circuit, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the at least one processor to perform the various aspects described above The operation of the network device in the method.
  • a communication system comprising: a network device, and/or a terminal device; wherein the network device is the network device described in the above aspects.
  • a twenty-fourth aspect a computer program product for use in a network device, the computer program product comprising a series of instructions, when the instructions are executed, to perform the method of the above aspects The operation of the network device.
  • a computer readable storage medium is provided, the instructions being stored in a computer readable storage medium, when executed on a computer, causing the computer to perform the method of the various aspects described above.
  • FIG. 1 is a schematic diagram of an application scenario of a technical solution according to an embodiment of the present application.
  • FIG. 2 is another schematic diagram of an application scenario of a technical solution according to an embodiment of the present application.
  • FIG. 3 is still another schematic diagram of an application scenario of a technical solution according to an embodiment of the present application.
  • FIG. 4 is still another schematic diagram of an application scenario according to the technical solution of the embodiment of the present application.
  • FIG. 5 is still another schematic diagram of an application scenario according to the technical solution of the embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 7 is another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 8 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 9 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 10 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 11 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 12 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 13 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 14 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 15 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 16 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 17 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 18 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 19 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 20 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 21 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 22 is still another schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 23 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 24 is another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 25 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 26 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 27 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 28 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 29 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 30 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 31 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 32 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 33 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 34 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 35 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 36 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of an application scenario of the technical solution of the embodiment of the present application. As shown in FIG. Part of the function is separated into a first network node and a second network node.
  • FIG. 2 is a schematic diagram of another application scenario of the technical solution of the embodiment of the present application.
  • a CU-DU segmentation is introduced, and the DU may correspond to FIG.
  • the first network node in the CU corresponds to the second network node in FIG.
  • first network node and the second network node may be two physical or logical separation modules in an overall network architecture, or may be two logical network elements that are completely independent.
  • the second network node may separate the control plane from the user plane to form a user plane of the second network node and a control plane of the second network node.
  • the CU has a Radio Resource Control (RRC) or a partial RRC control function, and includes all protocol layer functions or partial protocol layer functions of the existing base station; for example, only the RRC function or part of the RRC function, or the RRC function or service is included.
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link layer control protocols
  • MAC Media Access Control
  • the DU has all or part of the protocol layer functions of the existing base station, that is, part of the protocol layer functional units of the RRC/SDAP/PDCP/RLC/MAC/PHY, such as a part of the RRC function and protocol layer functions such as PDCP/RLC/MAC/PHY. Or include protocol layer functions such as PDCP/RLC/MAC/PHY, or include protocol layer functions such as RLC/MAC/PHY or include partial RLC/MAC/PHY functions, or only all or part of PHY functions; The functions of the various protocol layers may vary and are within the scope of this application.
  • different protocol layers may be separately deployed in the first network node and the second network node, and one possible implementation manner is that at least the first protocol layer is deployed in the second network node. Deploying at least a second protocol layer and a third protocol layer in the first network node,
  • the first protocol layer may be an RRC layer
  • the second protocol layer may be a MAC layer
  • the third protocol layer may be a PHY layer.
  • first protocol layer the second protocol layer, and the third protocol layer is merely exemplary, and should not be construed as limiting the application.
  • the first protocol layer and the second protocol layer may also be existing protocols (for example, LTE protocol) or other protocol layers defined in future protocols, which is not specifically limited in this application.
  • new relay nodes also have new technological advances.
  • the relay node is only deployed with layer 2 (for example, including a resource link control (RLC) layer, a MAC layer, etc.)
  • the protocol stack architecture of layer 1 eg, including the PHY layer
  • all protocol stack functions above layer 2 are not deployed, such as all RRC layer functions. Therefore, the data or signaling generated by the host base station needs to be forwarded by the relay node to the terminal device.
  • the first network node in the embodiment of the present application may correspond to the DU in the CU-DU architecture, and may also correspond to the foregoing relay node, where the second network node may correspond to the CU in the CU-DU architecture, or Corresponding to the above-mentioned host base station.
  • FIG. 3 is a schematic diagram of still another application scenario according to the technical solution of the embodiment of the present application.
  • the RRC layer is placed in the CU, and the MAC layer is placed in the DU.
  • the DU air interface sends the RRC message to the CU through the interface between the CU and the DU after the DU processing.
  • the CU is generated, the CU is sent to the DU through the interface between the CU and the DU.
  • the CU sends the packet to the terminal device through the air interface.
  • FIG. 4 is a schematic diagram of still another application scenario according to the technical solution of the embodiment of the present application.
  • the DU has a partial RRC function, such as the processing of the signaling radio bearer SRB0, and the RRC message may be performed by the DU. deal with.
  • the transport layer protocol of the control plane is the Stream Control Transmission Protocol (SCTP), and the transmitted application layer message is an F1AP (Application Protocol) message.
  • the transport layer protocol of the user plane is the GPRS Tunnelling Protocol-User plane (GTP-U) at the user level.
  • FIG. 5 is a schematic diagram of still another application scenario according to the technical solution of the embodiment of the present application.
  • the CU-CP when the CU performs control plane and user plane separation, the CU-CP is responsible for controlling the surface function, such as SRB.
  • the processing may have an RRC layer and a PDCP layer responsible for processing the SRB;
  • the CU-UP is responsible for user plane functions, such as DRB management, and is connected to the core network user plane network element, and may have an SDAP layer and a PDCP layer responsible for processing the DRB.
  • the E1 interface is the interface between the CU-CP and the CU-UP. Between CU-UP and DU is an F1-U connection, and between CU-CP and DU is an F1-C connection. There is an Ng-U connection between the CU-UP and the core network, and an Ng-C connection between the CU-CP and the core network.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • 5G fifth-generation
  • the network device in the embodiment of the present application may be a device for communicating with the terminal device, for example, may be a base station (Base Transceiver Station, BTS) and a base station controller (Base Station Controller) in the GSM system or CDMA.
  • BTS Base Transceiver Station
  • Base Station Controller Base Station Controller
  • the combination of the BSC may also be a base station (NodeB, NB) and a radio network controller (RNC) in the WCDMA system, or may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system.
  • BTS Base Transceiver Station
  • Base Station Controller Base Station Controller
  • the combination of the BSC may also be a base station (NodeB, NB) and a radio network controller (RNC) in the WCDMA system, or may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system.
  • NodeB NodeB
  • RNC
  • the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and an access network device in a future 5G network, such as a next-generation base station, or a future evolved public land mobile network (PLMN). ) Access network equipment in the network, etc.
  • a future 5G network such as a next-generation base station, or a future evolved public land mobile network (PLMN).
  • PLMN public land mobile network
  • the wireless network control node and the base station are separated.
  • the baseband module and the radio frequency module are separated, that is, the radio frequency.
  • the remote data center (Data Center, DC) scenario requires two different networks to interconnect; the large and small station scenarios, the large and small stations are connected to each other; the LTE and Wifi aggregation (LTE-Wifi aggregation, LWA) scenarios;
  • LTE-Wifi aggregation LTE-Wifi aggregation, LWA
  • There are various non-cell scenarios in the 5G system terminal can freely switch between cells, there is no clear boundary between cells), there is a control node and all cells are connected, or under the cell Connected to each transport node; in the CRAN scenario, there is a scenario where the BBU is split; in the CRAN virtualization scenario, a part of the BBU is deployed in a centralized manner, virtualized, and another part of the functions are deployed separately, and there is a possibility of physical separation between the two parts; It is understood that different system/system coexistence scenarios are within the scope of this application.
  • the present application describes various embodiments in connection with a terminal device.
  • the terminal device may also refer to a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, and a user agent.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • FIG. 6 shows a schematic flowchart of a transmission method 100 according to an embodiment of the present application. As shown in FIG. 6, the transmission method 100 includes:
  • the first network node receives a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device.
  • the first network node sends the first message to the first system.
  • the first network node receives the second message that is sent by the first system according to the first message, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the The context information of the terminal device saved by the first network node, or the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the context information of the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, identifier information of the terminal device, cell identifier information, and connection information of the first interface, where the first interface is used. Data transmission and information interaction between the first network node and the first system.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device that is carried by the second message, or reconstructs context information of the terminal device.
  • the first message is an RRC connection recovery setup request message or an RRC connection re-establishment request message.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or the first system includes a packet data convergence protocol layer and service data adaptation. At least one of layer and radio resource control functions.
  • the terminal device sends a first message to the first network node, where the first message is used to request to establish a radio resource control connection of the terminal device, and the first message is forwarded because the first network node does not have a partial RRC function.
  • the first system processes the first message, and sends a second message to the first network node, where the first network node receives the first system according to the And a second message sent by the first message, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the context information of the terminal device saved by the first network node, or
  • the second message includes context information of the terminal device.
  • the first network node is a DU
  • the first system is a CU
  • the terminal device sends an RRC connection recovery setup request message to the DU
  • the DU forwards the RRC connection recovery setup request message to the CU through the F1 interface
  • the CU receives the message.
  • the F1 interface control plane message is sent to the DU
  • the DU is used to indicate that the DU finds the context information of the terminal device saved by the DU, or is used to instruct the DU to reconstruct the context information of the terminal device.
  • the DU After receiving the control plane message, the DU finds the saved context information of the terminal device or re-establishes the context information of the terminal device, and the CU sends an RRC message to the terminal device.
  • the RRC message is sent to the DU through the F1 interface, and is forwarded by the DU to the DU.
  • the terminal device is configured to indicate that the RRC connection establishment succeeds or fails.
  • FIG. 7 shows another schematic flowchart of a transmission method 100 according to an embodiment of the present application. As shown in FIG. 7, the transmission method 100 further includes:
  • the first system sends a first command to the terminal device, where the first command is used to indicate that the terminal device enters an inactive state.
  • the first system sends a first command to the first network node, where the first command is used to indicate that the terminal device enters an inactive state, and the first network node does not parse or change the content of the first command.
  • the first command is processed by the protocol layer deployed on the first network node, the processed first command is sent to the terminal device.
  • the first command may be an RRC message
  • the CU commands the terminal device to enter an inactive mode by using an RRC message, where the RRC message carries an inactive mode indication and a resume ID of the terminal device.
  • the first command may also include an indication of whether to suspend one or more Signaling Radio Bearers (SRBs)/Data Radio Bearers (DRBs) and/or corresponding radio bearer identification information.
  • SRBs Signaling Radio Bearers
  • DRBs Data Radio Bearers
  • the RRC message is sent by the CU to the DU through the F1 interface, and the DU process is sent to the terminal device.
  • the message is an RRC Connection Release message.
  • the message is an RRC Connection Suspend message.
  • step S102 may also occur before step S101.
  • the first system sends a third message to the first network node, where the third message is used to indicate to the first network node that the terminal device enters an inactive state.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the terminal device accesses the first network node and the cell managed by the first system to establish an RRC connection, and the first system determines that the terminal device is in an inactive mode, and then the first network node is in the inactive mode.
  • Sending a third message the third message is used to indicate to the first network node that the terminal device enters an inactive state.
  • the CU sends an indication message to the DU through the F1 interface, which is used to indicate that the terminal device performs an inactive mode.
  • the indication is sent by the F1 interface control plane message, and the indication message includes a combination of one or more of the following information: the identification information of the terminal device on the F1 interface (the terminal device identification information on the F1AP CU side, and the terminal on the F1AP DU side)
  • the device identification information or the terminal device identification information of a single interface enters the inactive mode indication, and returns the identifier of the Resume ID (when the network indicates that the UE enters the inactive mode, the identifier is allocated to the UE, and is used when the UE requests the network to resume the RRC connection.
  • the cell radio network of the terminal device temporarily identifies the C-RNTI, and the terminal device context identifier information (for association with the context that the terminal device saves at the DU, for example, the terminal may be Whether the Context ID of the device, or the ID of the other format, suspends one or more signaling radio bearers (SRBs)/data radio bearers (DRBs) indications and/or corresponding radio bearer identification information.
  • SRBs signaling radio bearers
  • DRBs data radio bearers
  • the CU when the CU sends the first command to the DU through the F1 interface, the CU is carried in the same F1AP message as the third message in the RRC container container and S102.
  • the first system sends data belonging to the terminal device from the core network to the first network node, and the first network node is responsible for scheduling air interface transmission resources for the terminal device, and further The downlink data is sent to the terminal device.
  • the terminal device first requests the uplink data transmission resource from the first network node, and then sends the uplink data to the first network node on the authorized uplink resource, and then the first The network node sends to the first system.
  • the first system does not necessarily know. .
  • the first system has sent all the data from the core network belonging to a certain terminal device to the second network node, and prepares to instruct the terminal device to enter the inactive mode. Therefore, the first system sends the first command to the terminal device and sends the data.
  • the third message is sent to the first network node, and there is uplink and/or downlink data transmission between the first network node and the terminal device.
  • the third device may generate The downlink data is lost, and/or, after the first network node receives the third message, the data transmission and reception of the terminal device is suspended, and the uplink data may be lost.
  • the method 100 further includes:
  • the first system determines that the uplink or downlink data of the first network node is transmitted.
  • the first system negotiates with the first network node before sending the third message and the first command, and waits for the first network node to be ready (for example, after the uplink and downlink data is sent), and then sends the first One command and third message.
  • the first system may send a data sending status query message to the first network node, where the data sending status query message is used to query whether the first network node has completed data transmission with the terminal device, and the first network node sends a response.
  • the message is sent to the first system, the response message is used to indicate whether data transmission between the first network node of the first system and the terminal device has been completed.
  • the first system sends a first command to the terminal device, where the method 100 further includes:
  • the first system sends the first command to the first network node
  • the first network node determines that the uplink or downlink data of the first network node is transmitted, the first network node sends the first command to the terminal device.
  • the first network node determines the content of the first command, that is, the first network node determines that the first system is about to command the terminal device to enter an inactive mode, so as to perform corresponding processing, and the first network node is ready ( For example, after the uplink and downlink data is sent, the first command is sent to the terminal device, and the context information of the terminal device is processed according to the specific content of the third message.
  • the manner in which the first network node can know the content of the first command may be:
  • the first network node can interpret the content of the first command, for example, having the capability of decoding the RRC message;
  • the F1 interface message carrying the first command carries an indication, which is used to indicate the content of the first command, for example, indicating that the terminal device enters an inactive mode;
  • the content of the first command by the type of the F1AP message carrying the first command, for example, the first command and the third message are carried in the same F1AP message, and the content of the third message can be inferred.
  • the content of a command is to indicate that the terminal device enters the inactive mode.
  • the method 100 further includes:
  • the first system determines, according to the first interface information, that data transmission between the first network node and the terminal device is completed.
  • the first system can know that the data transmission between the first network node and the terminal device has ended.
  • the first network node reports the data buffer status associated with the terminal device, and when the downlink data buffer is 0, the downlink data transmission is completed.
  • the data cache state is reported.
  • the first network node periodically informs the first system of its data cache status.
  • the periodic reporting is configured by the first network node.
  • the first system sends a first command to the terminal device, where the method 100 further includes:
  • the first system sends the first command and the third information to the first network node by using an F1 message, and if there is data/signaling transmission between the first network node and the terminal device, the first network node sends a characterization indication.
  • the F1 message of the process failure is sent to the first system. If the data/signaling transmission between the first network node and the terminal device ends, the F1 message indicating that the process is successful is sent to the first system, and the first command is sent. Give the terminal device.
  • the sequence in which the first network node sends the F1 message indicating that the process is successful to the first system and the first network node sends the first command to the terminal device is not limited.
  • the first system saves context information of the terminal device.
  • the first system saves context information for the terminal device, including a combination of one or more of the following information: RRC configuration information, current security context, PDCP status, C-RNTI, global cell identifier, ECGI, physical cell Identifies the physical cell identifier PCI, resume ID, S1/NG interface connection related information (for example, the interface control plane UE identifier, interface user plane tunnel information TEID, IP address, etc.), F1 interface connection related information (for example, can be an interface) Control plane UE identifier, interface user plane tunnel information TEID, IP address, etc.).
  • RRC configuration information for example, current security context, PDCP status, C-RNTI, global cell identifier, ECGI, physical cell Identifies the physical cell identifier PCI, resume ID, S1/NG interface connection related information (for example, the interface control plane UE identifier, interface user plane tunnel information TEID, IP address, etc.), F1 interface connection related information (for example, can be an interface) Control plane UE identifier,
  • the first network node saves context information of the terminal device.
  • the context information saved by the DU for the terminal device includes a combination of one or more of the following information: RRC configuration information, DRB parameters (eg, DRB identification information and QoS parameter information), resume ID (if provided by the CU,
  • the DU may correspond to the identification information of the internal terminal device of the DU according to the identification information of the interface terminal device, and the F1 interface may be related to the information (for example, the interface control plane UE identifier, the interface user plane tunnel information TEID, the IP address, etc.), MAC Configuration information (eg, logical channel identification information and scheduling priority information (eg, priority bit rate PBR and token bucket depth BSD, etc.)).
  • the DU is reset to the MAC configured by the terminal device.
  • the DU is re-established as the RLC corresponding to the radio bearer (Radio Bear, RB) that the terminal device suspends.
  • Radio Bear Radio Bear
  • the terminal device stores context information of the terminal device according to the first command.
  • the terminal device After receiving the RRC message, the terminal device stores the context information of the terminal device, and specifically includes a combination of one or more of the following information: RRC configuration, current security context, PDCP status, C-RNTI, original service.
  • RRC configuration current security context
  • PDCP status current security context
  • C-RNTI original service.
  • the cell ID of the primary cell and the corresponding PCI resume ID.
  • the terminal device resets the MAC.
  • the terminal device suspends the SRB and the DRB except the SRB0.
  • the terminal device suspends one or more SRB/DRBs according to the indication in the first command, and keeps the remaining RBs. Accordingly, the terminal device re-establishes the RLC of the suspended RB.
  • steps S101-S105 are processes when the terminal device enters the inactive mode.
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the terminal device initiates an RRC connection recovery setup procedure, and sends an RRC connection recovery setup request message for restoring its RRC connection.
  • the RRC connection recovery setup request message carries the resume ID of the terminal device.
  • the target base station may find the source base station (SeNB) according to the cell identity (eg, PCI) included in the UE resume message, and then request the C-RNTI from the SeNB. /resume ID corresponds to the context of the UE.
  • the cell identity eg, PCI
  • the first network node sends the first message to the first system.
  • the first network node since the first network node does not have the partial RRC function, after the first network node receives the first message, the content of the first message is not parsed or changed, and the first message is sent to the first network. After the protocol layer deployed on the node performs corresponding processing, the processed first message is sent to the first system through the F1 interface.
  • the DU after receiving the foregoing RRC connection recovery setup request message, the DU sends the message to the CU through the F1 interface.
  • the message is carried by an RRC container in an F1AP message (eg, initial UE message, initial UL RRC message).
  • the first system sends a second message to the first network node according to the first message, where the second message is used to indicate that the first network node acquires context information of the terminal device saved by the first network node,
  • the second message includes identification information of the terminal device.
  • the CU parses the content of the message, so as to determine that the first message is a message that the terminal device requests to restore the RRC connection, and then resumes establishing an RRC connection for the terminal device. If the RRC connection of the terminal device is successfully restored, the F1 interface control plane message is sent to the DU, which is used to instruct the DU to find and use the context information of the terminal device saved by the DU, and restore the RRC connection of the terminal device.
  • control plane message carries one or a combination of the following information: the identifier information of the terminal device on the F1 interface (the terminal device identifier information on the F1AP CU side, the terminal device identifier information on the F1AP DU side, or a separate End device identification information of the interface), UE resume ID, SRB/DRB identification information and/or corresponding configuration information.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device that is carried by the second message.
  • the first network node After receiving the second message, acquires context information saved by the first network node, and restores corresponding configuration and transmission resources of the terminal device.
  • the DU finds the context information of the terminal device saved by the DU according to the terminal device identification information of the F1 interface or the resume ID of the terminal device, and restores the corresponding configuration and transmission resources of the terminal device.
  • the first network node uses the second message to carry the SRB/DRB identifier information and/or the corresponding configuration information.
  • the first network node generates protocol stack configuration information (for example, an RLC layer configuration, a MAC layer configuration, a PHY layer configuration) of the terminal device according to the second message, and uses the protocol stack configuration information to pass the F1 interface.
  • the first system is configured to encapsulate the protocol stack configuration information in the first indication information and send the information to the terminal device.
  • the first system sends the first indication information to the terminal device, where the first indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the first indication information may be an RRC message
  • the CU sends an RRC message to the terminal device to indicate that the RRC connection recovery establishment of the terminal device is successful or failed.
  • the RRC message is sent to the DU through the F1 interface, and is processed by the DU. Forward to the terminal device.
  • the first network node is unable to restore the context information of the terminal device, and then sends a response message to the first system, indicating that the context association of the terminal device of the first system fails, and optionally the first system Sending the first indication information to the UE, indicating that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the method further includes one or a combination of the following information: SRB/DRB identification information and corresponding configuration information, protocol stack configuration information.
  • S111, S121, S131, S141, and S150 are processes when the terminal device resumes from the inactive mode.
  • FIG. 8 shows still another schematic flowchart of a transmission method 100 according to an embodiment of the present application. As shown in FIG. 8, the transmission method 100 includes:
  • the second network node sends the first suspension indication information to the third network node, where the first suspension indication information is used to indicate that the terminal device enters an inactive state.
  • the second network node is a control plane node of the foregoing first system, where the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the second network node comprises an RRC layer and a PDCP layer for processing RRC messages.
  • the third network node includes a SDAP layer and a PDCP layer for processing user plane data.
  • the second network node and the third network node respectively correspond to the control plane node and the user plane node of the first system.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP.
  • the terminal device accesses the cell managed by the first network node and the second network node to establish an RRC connection, and the second network node determines to set the terminal device to an inactive mode, and the second network node And saving the context information to the terminal device, and sending the suspension indication information to the third network node, where the suspension indication information is used to indicate to the third network node that the terminal device enters an inactive state.
  • the UE accesses a cell managed by the CU-DU and establishes an RRC connection.
  • the CU decides to put the UE in inactive mode.
  • the CU-CP saves the AS context for the UE, including one or more of the following: RRC configuration, current security context, PDCP status, C-RNTI, cell identity of the serving primary cell, and corresponding PCI, resume ID, S1 (LTE) /NG (connected to the core network called NG port at 5G)
  • the interface is connected with related information
  • the F1 interface is connected with related information
  • the E1 interface is related.
  • the CU-CP sends a suspend indication to the CU-UP through the E1 interface, indicating that the UE performs an inactive mode.
  • the indication is sent by the E1 interface control plane message, and the message includes a combination of one or more of the following information: the identification information of the terminal device on the E1 interface (the terminal device identification information on the E1AP CU side, and the terminal device on the E1AP DU side)
  • the identification information or the terminal device identification information of a single interface enters the inactive mode indication /suspend indication, and the UE ID (for association to the context saved by the UE at the DU, may be the Context ID of the UE, C-RNTI or other ID of the format, such as the terminal device identification information on the F1AP DU side, the terminal device identification information on the F1AP CU side, or the F1 interface has only one interface UEID) (the CU-UP should be able to correspond to the internal UE ID according to the E1 port UE ID, or Further follow
  • the RRC configuration may be all content within the RRC Connection Reconfiguration.
  • the third network node stores context information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the context information of the terminal device includes connection information of the second interface, connection information of the third interface, connection information of the fourth interface, radio resource control configuration, data radio bearer parameters, current security context information, and packet data convergence.
  • the second interface is used for data transmission and/or information interaction between the third network node and the core network
  • the third interface is used between the third network node and the second network node.
  • Data transmission and/or information interaction is performed
  • the fourth interface is used for data transmission and/or information interaction between the third network node and the first network node.
  • the terminal device context information saved at the third network node includes connection information of the first interface, connection information of the second interface, current security context information, a packet data convergence protocol status, and a identifier for identifying the terminal device. Identification information.
  • the third network node stores context information of the terminal device for the terminal device.
  • the CU-UP stores the AS context of the UE, including RRC configuration, current security context, PDCP status, DRB parameters (such as DRB identification information and QoS parameter information, and correspondence between DRB and QoS flow), S1/NG.
  • Connection related information such as tunnel endpoint address on the core network side and CU-UP side, interface UE ID, PDU session parameters, etc.
  • F1 connection related information such as tunnel endpoint address on the DU and CU-UP side, interface UE ID, data
  • Flow parameter, DRB parameter, etc. E1 connection related information (such as tunnel endpoint address on CU-CP and CU-UP side, interface UE ID, etc.), resume ID (if CU-CP provides, if CU-CP does not provide
  • the CU-UP may identify itself, that is, according to the UE ID of the E1 interface.
  • the PDU session parameter includes QoS flow parameter information.
  • one possible situation is to retain information related to the S1/NG interface connection of the core network (user plane), resume ID (or other internal ID for identifying the UE), current Security context, one or more combinations of PDCP states.
  • the second context is released, that is, the related information (user plane) of the F1 interface connection, for example, the information about the fourth interface.
  • the invention is not limited to the case of other reserved portions, the release portion.
  • CU-CP one possible situation is to retain information related to the S1/NG interface connection of the core network (control plane), RRC configuration information, C-RNTI, global cell identity ECGI, physical cell Identifies one or more combinations of physical cell identifiers PCI, resume IDs.
  • the second network node sends a second suspension indication information to the first network node, where the second suspension indication information is used to indicate that the terminal device enters an inactive state and/or instructs the first network node to delete the terminal device.
  • Context is used to indicate that the terminal device enters an inactive state and/or instructs the first network node to delete the terminal device.
  • the CU-CP sends a suspend indication to the DU through the F1 interface, indicating that the UE performs an inactive mode.
  • the indication is sent by the F1 interface control plane message, and the message includes a combination of one or more of the following information: F1AP CU side UEID, F1AP DU side UEID (or F1 port has only one interface UEID), enters inactive mode indication, UE The ID (for association with the context in which the UE is saved in the DU, which may be the Context ID of the UE, the C-RNTI or other format ID), whether to suspend the indication of one or more SRB/DRBs. It may also include the RRC connection suspend message sent by the S165 to the UE (in the form of an RRC container.)
  • the first network node stores context information of the terminal device.
  • the DU stores the AS context of the UE, and specifically includes an RRC configuration, a DRB parameter, F1/E1 connection related information (such as a tunnel endpoint address, an interface UE ID, a DRB parameter, etc.), a resume ID, and the like.
  • DU reset is the MAC configured for this UE.
  • the RRE corresponding to the RB that the DU Reestablish UE suspends.
  • the second network node sends a first command to the terminal device, where the first command is used to indicate that the terminal device enters an inactive state.
  • the CU-CP sends an RRC message through the F1 interface to command the UE to enter an inactive mode (which can be sent together with step 5).
  • the RRC message carries an entry into the inactive mode indication and the resumeID of the UE.
  • the RRC message is sent to the DU through the F1 interface, and the DU process is forwarded to the UE.
  • the message is an RRC Connection Suspend message.
  • the CU when the CU sends the RRC message to the DU through the F1 interface, the CU is carried in the same F1AP message as the indication information of the RRC container and the S163.
  • the terminal device stores context information of the terminal device according to the first command.
  • the method 100 before the sending, by the second network node, the first command to the terminal device, the method 100 includes:
  • the second network node sends an inactivity timer to the third network node, where the inactive timer is used by the third network node to determine whether the terminal device is in an inactive state;
  • the third network node determines that the uplink data sent by the terminal device is not received, and/or the third network node determines that the downlink data sent by the core network is not received;
  • the third network node sends a terminal device inactive state indication to the second network node, where the terminal device inactive state indicates whether the second network node determines whether to notify the terminal device to enter an inactive state.
  • the CU-CP sends an inactive timer T to the CU-UP.
  • the CU-CP carries the inactive timer corresponding to the UE in the UE Context Setup request, and may also be the inactive timer corresponding to the cell in the case of the Cell setup, or the inactive timer corresponding to the gNB in the E1setup. That is, the inactive timer may be a UE granularity, or may be a cell or a gNB granularity.
  • the CU-UP finds that the UE has no uplink data when it exceeds the T time, and/or, if the UE does not have downlink data after the T time, it notifies the CU-CP timer to expire.
  • CU-UP starts timer-dl and timer-ul for downlink data and uplink data respectively.
  • the timer-dl starts counting down.
  • the timer-dl is reset.
  • the timer-ul starts counting down.
  • the timer-ul resets. Only when both timer-dl and timer-ul arrive, the CU-UP considers that the UE satisfies the inactive condition and sends an indication to the CU-CP.
  • the CU-CP decides to let the UE perform the inactive state, the CU-CP notifies the CU-UP and the DU, respectively. Both the CU-UP and the DU may or may not retain the UE context, which may be specified by the protocol, or may be an indication that the CU-CP gives or does not retain the UE context.
  • the CU-CP may, according to the timer arrival indication of the CU-UP, the no-data indication sent by the DU, comprehensively consider whether to let the UE enter the inactive state.
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the terminal device sends the first message to the first network node, including:
  • the third network node determines to receive downlink data sent by the core network
  • the third network node sends a notification message to the second network node, where the notification message is used by the second network node to send a paging message to the terminal device;
  • the terminal device sends the first message to the first network node according to the paging message.
  • the CU-UP when the CU-UP finds that the core network has data, the CU-UP notifies the CU-CP, and the CU-CP initiates RAN paging in the RAN notificatin area to notify the UE (for example, the CU-CP sends the gNB in all RAN notification areas). RAN paging message). The UE receives the RAN paging message and initiates an RRC connection resume procedure.
  • the first network node forwards the first message to the second network node.
  • the method 100 further includes:
  • the second network node acquires context information of the terminal device saved by the second network node.
  • the CU-CP After receiving the RRC connection resume message forwarded by the DU, the CU-CP first determines whether it has a UE context. If not, the corresponding source gNB is found based on the source cell ID (either directly or implicitly in the resume ID) provided in the RRC connection resume message, and the UE context is requested from the source gNB. If the CU-CP successfully obtains the UE context, a message is sent to the CU-UP and the DU, respectively.
  • the CU-CP has a UE context. If the CU-UP and the DU reserve the UE context, the message sent by the CU-CP on the F1/E1 port may be the UE context resume, and the UE ID/resume ID is included for the DU and the CU-UP to find the UE context.
  • the message sent by the F1 port may be the UE context setup, including the UE context (RRC configuration, such as the protocol stack configuration of the SRB and the DRB), and the information required for establishing the user plane tunnel of the F1 interface connection (for example, CU-CP). Side IP address and GTP-U tunnel endpoint ID TEID).
  • the message sent on the E1 interface may be the UE context setup, including the UE context (RRC configuration, such as the protocol stack configuration of the DRB), and the transmission channel of the user plane that establishes the S1 interface of the DRB (for example, the IP address and core of the core network side).
  • the tunnel end identifier (TEID) corresponding to the network side PDU session and the transmission channel of the user plane connected to the F1 interface for example, the IP address on the DU side and the tunnel end identifier TEID corresponding to the DR side on the DU side).
  • the CU-CP may be the same or different.
  • the message sent by the CU-CP on the E1 port may be the UE context setup/resume depending on whether the CU-UP has a UE context.
  • the message sent by the CU-CP on the F1 port is the UE context setup.
  • the message sent by the CU-CP on the F1 port may be the UE context setup, including the UE context (RRC configuration, such as the protocol stack configuration of the SRB and the DRB), and the information required for establishing the user plane tunnel of the F1 interface connection. (for example, the IP address on the CU-CP side and the GTP-U tunnel endpoint identifier TEID).
  • RRC configuration such as the protocol stack configuration of the SRB and the DRB
  • the information required for establishing the user plane tunnel of the F1 interface connection for example, the IP address on the CU-CP side and the GTP-U tunnel endpoint identifier TEID).
  • the message sent by the E1 interface may be a UE context setup, including a UE context (RRC configuration, such as a protocol stack configuration of the DRB), and a transmission channel of a user plane that establishes an S1 interface connection of the PDU session (for example, an IP address of the core network side and The tunnel end identifier (TEID) corresponding to the core network side PDU session and the transmission channel of the user plane connected to the F1 interface (for example, the IP address on the DU side and the tunnel end identifier TEID corresponding to the DR side on the DU side).
  • RRC configuration such as a protocol stack configuration of the DRB
  • a transmission channel of a user plane that establishes an S1 interface connection of the PDU session for example, an IP address of the core network side and The tunnel end identifier (TEID) corresponding to the core network side PDU session and the transmission channel of the user plane connected to the F1 interface (for example, the IP address on the DU side and the tunnel end identifier TE
  • the second network node sends a fourth message to the third network node according to the first message, where the fourth message is used to indicate that the third network node acquires context information of the terminal device saved by the third network node.
  • the fourth message includes identification information of the terminal device.
  • the CU-CP can successfully resume the RRC connection of the UE.
  • the resume indication is sent to the CU-UP through the E1 interface control plane message, and is used to indicate that the CU-UP resumes the RRC connection of the UE.
  • the interface message carries one or a combination of the following information: E1AP CU side UEID, E1AP DU side UEID, UE resume ID.
  • the third network node acquires context information of the terminal device saved by the third network node according to the identifier information of the terminal device that is carried by the fourth message.
  • the CU-UP finds the UE AS context according to the interface UE ID or the resume ID of the UE, and restores the UE configuration.
  • the CU-UP replies with a resume confirmation message to the CU-CP.
  • the second network node sends a second message to the first network node according to the first message, where the second message is used to indicate that the first network node acquires context information of the terminal device saved by the first network node.
  • the second message includes identification information of the terminal device.
  • the CU-CP can successfully resume the RRC connection of the UE.
  • the resume indication is sent to the DU through the F1 interface control plane message, and is used to indicate that the DU resumes the RRC connection of the UE.
  • the interface message carries one or a combination of the following information: F1AP CU side UEID, F1AP DU side UEID, UE resume ID.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device that is carried by the second message.
  • the second network node sends the first indication information to the terminal device, where the first indication information is used to indicate that the RRC connection recovery setup of the terminal device succeeds or fails. It should be understood that S171-S177 is a processing flow when the terminal device recovers from the inactive mode.
  • S175 and S176 may be performed prior to S173 and S174, and the application is not limited thereto.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 9 is still another schematic flowchart of a transmission method 100 according to an embodiment of the present application. Different from the processing when the terminal device enters the inactive mode in FIG. 7, the first network node has context information on the terminal device. Processing, the transmission method 100 includes:
  • the first system sends a third message to the first network node, where the third message is used to indicate to the first network node that the terminal device enters an inactive state and/or instructs the first network node to delete the terminal device.
  • Context
  • the first network node processes the first command and the third message in the same manner as FIG. 7 except for the content of the message in S102 in FIG. 7. For brevity, details are not described herein again.
  • the first network node releases context information of the terminal device.
  • the first network node processes the context information of the terminal device, and the transmission method 100 includes:
  • the first system sends a second message to the first network node according to the first message, where the second message is used to indicate that the first network node re-establishes context information of the terminal device, where the second message includes the terminal. Identification information of the device.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function layer.
  • the CU parses the content of the message, so as to determine that the first message is a message that the terminal device requests to restore the RRC connection, and then resumes establishing an RRC connection for the terminal device. If the RRC connection of the terminal device is successfully restored, the F1 interface control plane message is sent to the DU, which is used to instruct the DU to restore the context configuration for the terminal device, including the protocol stack configuration of the SRB and the DRB, and the F1 interface for establishing the SRB and the DRB. The control plane of the connection and the transmission channel of the user plane.
  • the interface control plane message carries one or a combination of the following information: the identifier information of the terminal device on the F1 interface (the terminal device identifier information on the F1AP CU side, the terminal device identifier information on the F1AP DU side, or a separate Terminal device identification information of the interface), the terminal device identification information (for the context information associated with the terminal device to be saved in the DU, may be the Context ID of the terminal device, C-RNTI or other format ID), the terminal The device's signaling radio bearer list (SRB list) and/or data radio bearer list (DRB list), and the corresponding protocol stack configuration, the F1 interface user plane tunnel establishment information corresponding to the DRB list (for example, the CU side IP address and GTP) -U tunnel endpoint ID TEID).
  • the terminal device identification information for the context information associated with the terminal device to be saved in the DU, may be the Context ID of the terminal device, C-RNTI or other format ID
  • SRB list signaling radio bearer list
  • the first network node re-establishes context information of the terminal device according to the identifier information of the terminal device carried in the second message.
  • the first network node after receiving the second message, the first network node establishes context information for the terminal device, performs corresponding configuration, and allocates transmission resources.
  • the first network node generates protocol stack configuration information of the terminal device according to the second message (for example, may be an RLC layer configuration, a MAC layer configuration, a PHY layer configuration), and sends the protocol stack configuration information through the F1 interface.
  • the first system is configured to encapsulate the protocol stack configuration information in the first indication information and send the information to the terminal device.
  • S111, S121, and S150 are the same as those shown in FIG. 6 except that the processing of the terminal device is different from that of the terminal device shown in FIG. 6, and the steps are the same as those shown in FIG. 6. For brevity, details are not described herein again.
  • FIG. 10 shows still another schematic flowchart of a transmission method 100 according to an embodiment of the present application.
  • the transmission method 100 includes:
  • the first network node releases context information of the terminal device.
  • the processing when the terminal device enters the inactive mode is the same as the processing when the terminal device enters the inactive mode in the transmission method shown in FIG. 8, and the third network node and the first network node receive After the suspension indication information sent by the second network node, the third network node saves the context information of the terminal device, and the first network node releases the context information of the terminal device.
  • the second network node sends a second message to the first network node according to the first message, where the second message is used to indicate that the first network node reestablishes context information of the terminal device, where the second message includes data.
  • the first network node is configured according to at least one of a data radio bearer list, a signaling radio bearer list, a radio resource control configuration, a data radio bearer parameter, the terminal device identifier information, the cell identifier information, and the first interface connection information.
  • One is to reconstruct context information of the terminal device.
  • the CU when the CU receives the RRC connection resume message of the UE, it initiates a DRB+SRB connection establishment to the DU. Finally, the DU forwards the RRC connection resume message sent by the CU to the UE.
  • the second network node is a control plane node of the first system
  • the third network node is a user plane node of the first system
  • the first system includes a packet data convergence protocol layer, a service data adaptation layer, and At least one of the radio resource control layer functions.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP.
  • FIG. 11 shows still another schematic flowchart of a transmission method 100 according to an embodiment of the present application. As shown in FIG. 11, the transmission method 100 includes:
  • the third network node releases part of the context information of the terminal device.
  • the context information of the terminal device includes connection information of the second interface, connection information of the third interface, connection information of the fourth interface, radio resource control configuration, data radio bearer parameters, current security context information, and packet data convergence.
  • the third interface is used for data transmission and/or information interaction between the third network node and the second network node, where the fourth interface is used by the third network node and the first network node. Data transfer and/or information interaction.
  • connection information of the first interface includes connection information of the fourth interface.
  • the context information of the terminal device released by the third network node includes at least one of a packet data convergence protocol state and connection information of the fourth interface.
  • the processing when the terminal device enters the inactive mode is the same as the processing when the terminal device enters the inactive mode in the transmission method shown in FIG. 8, the third network node and the first network node. After receiving the suspension indication information sent by the second network node, the third network node releases part of the context information of the terminal device, and the first network node releases the context information of the terminal device.
  • the second network node sends a fourth message to the third network node according to the second message, where the fourth message is used to indicate that the third network node reestablishes context information of the terminal device, where the fourth message includes the The identification information of the terminal device, the data radio bearer list of the terminal device, the radio resource control configuration, the information for establishing the F1 port connection, and the at least one of the information for establishing the E1 port connection; S181, the third network node According to the identification information of the terminal device, the data radio bearer list of the terminal device, and the radio resource control configuration, used to establish the information of the F1 port connection, is used to establish the information of the E1 port connection, and reconstruct the context information of the terminal device.
  • the CU-CP when the CU-CP receives the RRC connection resume request message of the UE, it initiates an F1 interface connection for the UE to the CU-UP, and initiates an E1 interface connection for the UE.
  • the message for the F1 interface of the UE includes, for example, an F1 interface UE identifier, a DRB ID, an IP address on the DU side, a tunnel end identifier TEID corresponding to the DR side DRB, a correspondence between the DRB and the QoS flow, and the like.
  • the E1 interface connection for the UE includes, for example, an E1 interface UE identifier, a resume ID, and the like.
  • the CP-CP initiates a DRB+SRB connection setup to the DU and an F1 interface connection for the UE.
  • the DU forwards the RRC connection resume message sent by the CU to the UE.
  • S180 and S181 may be before S178 and S179, or may be after S178 and S179, and the application is not limited thereto.
  • the second network node is a control plane node of the first system
  • the third network node is a user plane node of the first system
  • the first system includes a packet data convergence protocol layer and a service data adaptation layer.
  • the radio resource control layer functions.
  • the second network node includes at least one of a packet data convergence protocol layer and a radio resource control layer function
  • the third network node includes at least one of a packet data convergence protocol layer and a service data adaptation layer function.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP.
  • FIG. 12 shows still another schematic flowchart of the transmission method 100 according to the embodiment of the present application.
  • the main difference between the transmission method shown in FIG. 12 and the transmission method shown in FIG. 7 to FIG. 11 is as follows: FIG. 7 to FIG.
  • the first network node and the first system (or the second network node) are all informed that the terminal device enters an inactive state, the resume device is assigned a resume ID, and the terminal device context is matched.
  • the HO failure, the RLF, the underlying integrity check failure, and the RRC connection reconfiguration failure are caused by the RRC connection reestablishment
  • the random access and the RRC connection establishment triggered by the RRC connection reestablishment are caused.
  • the DU does not know that the terminal device has accessed the cell, and regards it as a new terminal device, and the CU recognizes that the terminal device has been accessed through the C-RNTI carried in the RRC connection re-establishment message, and The context information of the terminal device has been saved at the DU.
  • the transmission method 100 includes:
  • the terminal device accesses the first network node and the cell managed by the first system, and acquires a first cell radio network temporary identifier of the terminal device.
  • the terminal device accesses the first network node and the cell managed by the first system, and the C-RNTI allocated by the first network node or the first system to the terminal device is C-RNTI1, and the terminal device
  • the first network node and the first system store context information of the terminal device for the terminal device.
  • the terminal device sends a random access preamble sequence to the first network node, where the random access preamble sequence is used by the terminal device to initiate random access.
  • the first network node sends a random access response message to the terminal device, where the random access response message includes a second cell radio network temporary identifier of the terminal device.
  • the first network node sends second indication information to the first system, where the second indication information includes a second cell radio network temporary identifier of the terminal device.
  • the second indication information includes cell identity information that is accessed by the terminal device, such as a PCI or an E-UTRAN Cell Global Identifier.
  • the second indication information is sent by using an F1 control plane message (such as an F1AP message), where the F1 control plane message includes at least one of the following information: identifier information of the terminal device on the F1 interface (for example, the F1AP may be Terminal device identification information on the DU side or terminal device identification information of a single interface), the second cell radio network temporary identifier (C-RNTI2), and cell identification information.
  • F1 control plane message such as an F1AP message
  • the F1 control plane message includes at least one of the following information: identifier information of the terminal device on the F1 interface (for example, the F1AP may be Terminal device identification information on the DU side or terminal device identification information of a single interface), the second cell radio network temporary identifier (C-RNTI2), and cell identification information.
  • identifier information of the terminal device on the F1 interface for example, the F1AP may be Terminal device identification information on the DU side or terminal device identification information of a single interface
  • C-RNTI2 second cell radio network temporary
  • the terminal device sends a first message to the first network node, where the first message includes identifier information of the terminal device.
  • the identifier information of the terminal device is at least one of first cell radio network temporary identifier information and corresponding physical cell identifier information.
  • the first message is an RRC connection re-establishment request message
  • the terminal device sends an RRC connection re-establishment request message, where the original base station PCI and the original C-RNTI1 are carried in the RRC connection re-establishment request message.
  • the DU sends the above RRC message to the CU through the F1 interface.
  • the second indication information in S112 is carried in the same F1AP message.
  • the F1AP message is an initial UE message, which is used to represent access of a new terminal device.
  • the first network node sends the first message to the first system.
  • the first network node since the first network node does not have the partial RRC function, after the first network node receives the first message, the content of the first message is not parsed or changed, and the first message is sent to the first network node. After the corresponding protocol layer is processed, the processed first message is sent to the first system through the F1 interface.
  • the DU after receiving the RRC connection re-establishment request message, the DU sends the message to the CU through the F1 interface.
  • the message is carried by the RRC container in the initial UE message of the F1AP.
  • the first system sends a second message to the first network node according to the first message, where the second message is used to indicate that the first network node acquires context information of the terminal device saved by the first network node,
  • the second message includes identification information of the terminal device.
  • the CU can reestablish the RRC connection for the terminal device, the CU sends a second message to the DU through the F1 interface, and is used to instruct the DU to find the original context information of the terminal device saved by the DU, and perform delta delta based on the original context information.
  • Configuration after the delta is configured, the DU establishes a context for the terminal device.
  • the delta configuration includes replacing the original C-RNTI1 with C-RNTI2, and/or refreshing the identification information of the F1AP terminal device.
  • the second message includes a combination of one or more of the following information: identification information of the terminal device of the F1 interface (terminal device identification information on the F1AP CU side, terminal device identification information on the F1AP DU side, or a separate interface)
  • the terminal device identification information), the original C-RNTI1, the new C-RNTI2, the cell identifier, and the terminal device context identification information may be the Context ID or other format of the terminal device) ID).
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device that is carried by the second message.
  • the first network node acquires the context information saved by the first network node, and performs delta configuration based on the original context information, for example, the delta configuration specifically includes replacing the original C-RNTI1. It is C-RNTI2, and/or refreshes the identification information of the F1AP terminal device.
  • the first system sends the first indication information to the terminal device, where the first indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the first indication information may be an RRC message, where the RRC message is used to indicate that the terminal device RRC re-establishment succeeds or fails.
  • the RRC message is sent by the CU to the DU through the F1 interface, and is processed by the DU and sent to the terminal device. Further, when the CU sends the RRC message to the DU through the F1 interface control plane, the RRC message may be sent in the same F1AP message as the second message in S133.
  • the first indication information is an RRC re-establishment message, where the F1AP message is an initial context setup message, which is used to indicate that the DU establishes a context for the newly accessed UE. Otherwise, the CU sends an RRC reestablishment failure message to the terminal device.
  • the terminal device sends an RRC connection re-establishment complete message to the first system according to the first indication information.
  • the RRC connection re-establishment completion message is sent by the The first system.
  • the transmission method 100 is described in detail above with reference to FIG. 6 to FIG. 12, in which the first network node cannot send the terminal device because the first network node does not have a partial RRC function.
  • the message is parsed, and the message can only be sent to the first system (or the second network node) for parsing through the interface;
  • the transmission method 200 according to the embodiment of the present application will be described in detail below with reference to FIG. 13 to FIG.
  • the first network node has a partial RRC function, and is capable of parsing and/or replying to a partial RRC message, such as SRB0.
  • FIG. 13 shows a schematic flowchart of a transmission method 200 according to an embodiment of the present application. As shown in FIG. 13, the transmission method 200 includes:
  • the first network node receives a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device;
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device, or
  • the first network node receives the second message sent by the first system according to the identifier information of the terminal device, where the second message includes context information of the terminal device.
  • the first network node sends a response message to the terminal device, to notify the terminal device that the RRC connection setup fails.
  • the response message includes a cause value for indicating a cause of the RRC connection setup failure, for example, the context acquisition failure at the first network node.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function, and at least a part of a radio resource control layer function.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the first network node receives the second message sent by the first system according to the identifier information of the terminal device, including:
  • the first network node receives the second message sent by the second network node according to the identifier information of the terminal device, where the second network node is a control plane node of the first system.
  • the first network node receives a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device, and the first network node determines the terminal device according to the first message. Identification information.
  • the first network node If the first network node stores the context information of the terminal device, the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device, where the first network node sends The first system sends a fourth message, where the fourth message is used to indicate that the first system acquires context information of the terminal device saved by the second network node.
  • the first network node acquires a fifth message sent by the first system, where the fifth message includes a signaling radio bearer list and/or data wireless of the terminal device. a bearer list, the first network node reestablishing context information of the terminal device according to the identifier information of the terminal device and the at least one of a signaling radio bearer list and a data radio bearer list of the terminal device.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 14 shows another schematic flowchart of a transmission method 200 according to an embodiment of the present application.
  • the transmission method 200 includes:
  • the first network node receives a third message sent by the first system, where the third message is used to indicate to the first network node that the terminal device enters an inactive state.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function layer.
  • the first system saves context information of the terminal device.
  • the first network node saves context information of the terminal device.
  • the first system sends a first command to the terminal device, where the first command is used to indicate that the terminal device enters an inactive state;
  • the terminal device stores context information of the terminal device according to the first command.
  • the RRC connection resume message may be sent by using a UL RRC message transfer message. If not saved, the Intiail UL RRC message transfer needs to be sent to send the RRC connection resume message.
  • steps S201-S205 are the same as the steps of S101-S105 in FIG. 7, which are the processing when the terminal device enters the inactive mode. For brevity, no further details are provided herein.
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the terminal device initiates an RRC connection recovery setup procedure, and sends an RRC connection recovery setup request message for restoring its RRC connection.
  • the RRC connection recovery setup request message carries the resume ID of the terminal device.
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node is configured to perform the RRC function, and after the first network node receives the first message, the first message may be parsed to determine the identifier information of the terminal device.
  • the identifier information is a resume ID of the terminal device.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device.
  • the DU can find the context information of the terminal device saved by the DU according to the resume ID, and restore the corresponding configuration and transmission resources of the terminal device.
  • the first network node sends a fifth message to the first system according to the first message, where the fifth message is used to indicate that the first system acquires context information of the terminal device that is saved by the first system.
  • the DU sends a fifth message to the CU through the F1 interface, and after receiving the fifth message of the F1 interface, the CU can find the context information of the terminal device saved by the CU, and can carry the information based on the context information and the fifth message.
  • the information is successfully restored to establish an RRC connection of the terminal device, and the corresponding configuration and transmission resources of the terminal device are restored.
  • the fifth message may carry indication information for indicating that the first network node does not completely acquire the context of the terminal device.
  • the first system carries the configuration information of the terminal device in the first indication information, based on the indication information, for the first network node to reconstruct the context of the terminal device.
  • the first system acquires context information of the terminal device saved by the first system according to the fifth message.
  • the first system sends first indication information to the first network node, where the first indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the message may further carry configuration information of the terminal device (for example, an SRB list and/or a DRB list including the terminal device, and a corresponding protocol stack configuration, and an F1 interface user plane tunnel corresponding to the DRB list.
  • Establish information (such as the IP address on the CU side and the GTP-U tunnel endpoint ID TEID).
  • the message indicates that the first network node deletes the terminal device context, or suspends the terminal device context.
  • the first network node sends the second indication information to the terminal device, to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the first system sends the second indication information to the terminal device, to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the second indication information may be an RRC message
  • the CU sends an RRC message to the terminal device to indicate that the RRC connection recovery of the terminal device is successfully established or failed.
  • the RRC message is sent to the DU through the F1 interface, and is processed by the DU. Forward to the terminal device.
  • the DU generates the second indication message based on the first indication message, and sends the second indication message to the terminal device.
  • FIG. 15 shows still another schematic flowchart of a transmission method 200 according to an embodiment of the present application.
  • the transmission method 200 includes:
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device.
  • the first network node sends a fifth message to the second network node according to the first message, where the fifth message is used to instruct the second network node to acquire the context of the terminal device saved by the second network node.
  • Information, the fifth message includes context information of the terminal device.
  • the second network node is a control plane node of the first system
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function layer.
  • the second network node acquires context information of the terminal device saved by the second network node according to the identifier information of the terminal device that is carried by the fifth message.
  • the second network node sends a seventh message to the third network node, where the seventh message is used to indicate that the third network node acquires context information of the terminal device saved by the third network node, where the seventh message includes Identification information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP.
  • the third network node acquires context information of the terminal device saved by the third network node according to the identifier information of the terminal device that is carried by the seventh message.
  • the second network node sends the second indication information to the terminal device, where the second indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • FIG. 16 shows still another schematic flowchart of a transmission method 200 according to an embodiment of the present application.
  • the transmission method 200 includes:
  • the first network node releases context information of the terminal device.
  • the transmission method 200 further includes:
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the terminal device initiates an RRC connection recovery setup procedure, and sends an RRC connection recovery setup request message for restoring its RRC connection.
  • the RRC connection recovery setup request message carries the resume ID of the terminal device.
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node is configured to perform the RRC function, and after the first network node receives the first message, the first message may be parsed to determine the identifier information of the terminal device.
  • the identifier information is a resume ID of the terminal device.
  • the first network node sends a fourth message to the first system, where the fourth message is used to indicate that the first system acquires context information of the terminal device that is saved by the second network node.
  • the fourth message includes identifier information of the terminal device.
  • the identifier information is a resume ID of the terminal device.
  • the DU sends a fourth message to the CU through the F1 interface, and after receiving the fourth message of the F1 interface, the CU can find the context information of the terminal device saved by the CU, and can carry the information based on the context information and the fifth message.
  • the information is successfully restored to establish an RRC connection of the terminal device, and the corresponding configuration and transmission resources of the terminal device are restored.
  • the first system acquires context information of the terminal device saved by the first system according to the fourth message, and restores the success or failure of establishing an RRC connection of the terminal device.
  • the first system sends a fifth message to the first network node, where the fifth message is used to indicate that the RRC connection recovery establishment of the terminal device of the first network node is successful.
  • the fifth message includes a signaling radio bearer list and/or a data radio bearer list of the terminal device;
  • the fifth message is used to indicate that the RRC connection recovery setup failure of the terminal device of the first network node.
  • the fifth message is used to indicate that the first network deletes or suspends context information of the terminal device.
  • the first system After the first system finds the context information of the terminal device saved by the first system, it sends a fifth message to the first network node, where the fifth message is used to instruct the first network node to reconstruct the Context information of the terminal device, where the fifth message includes a signaling radio bearer list and/or a data radio bearer list of the terminal device, and after receiving the fifth message, the first network node may be configured according to the terminal device Resetting the context information of the terminal device by using at least one of the identification information and the signaling radio bearer list and the data radio bearer list of the terminal device.
  • the CU After the CU receives the F1 interface message, if the RRC connection of the terminal device is successfully restored, the CU sends an F1 interface control plane message to the DU to indicate that the DU configures the protocol stack of the SRB and the DRB for the terminal device recovery context. And establishing a control plane for the F1 interface connection and a transmission channel for the user plane.
  • the interface control plane message carries one or a combination of the following information: the identifier information of the terminal device on the F1 interface (the terminal device identifier information on the F1AP CU side, the terminal device identifier information on the F1AP DU side, or a separate Terminal device identification information of the interface), C-RNTI, terminal device context identification information (for context information associated with the terminal device to be saved in the DU, may be the Context ID of the terminal device, or an ID of another format),
  • the first network node re-establishes context information of the terminal device according to the identifier information of the terminal device and the at least one of a signaling radio bearer list and a data radio bearer list of the terminal device.
  • the first system sends the second indication information to the terminal device, where the first indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • the first network node sends the second indication information to the terminal device, where the first indication information is used to indicate that the RRC connection recovery establishment of the terminal device succeeds or fails.
  • FIG. 17 shows still another schematic flowchart of a transmission method 200 according to an embodiment of the present application. As shown in FIG. 17, the method 200 includes:
  • the terminal device sends a first message to the first network node, where the first message is used to request to restore a radio resource control connection of the terminal device.
  • the processing when the terminal device enters the inactive mode is the same as the processing when the terminal device enters the inactive mode in the transmission method shown in FIG. 10, and details are not described herein for brevity.
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node sends a fifth message to the second network node according to the first message, where the fifth message is used to instruct the second network node to obtain the context information of the terminal device saved by the second network node.
  • the fifth message includes context information of the terminal device.
  • the second network node is a control plane node that is a first system, and the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function. S281.
  • the second network node acquires context information of the terminal device saved by the second network node according to the fifth message.
  • the second network node sends a seventh message to the third network node, where the seventh message is used to indicate that the third network node acquires context information of the terminal device saved by the third network node, where the seventh message includes Identification information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP.
  • the third network node acquires context information of the terminal device saved by the third network node according to the identifier information of the terminal device that is carried by the seventh message.
  • the second network node sends a sixth message to the first network node, where the sixth message includes at least one of a signaling radio bearer list and a data radio bearer list of the terminal device, and identifier information of the terminal device.
  • the sixth message is used to indicate that the first network node re-establishes context information of the terminal device;
  • the first network node re-establishes context information of the terminal device according to at least one of a signaling radio bearer list and a data radio bearer list of the terminal device and the identifier information of the terminal device that are carried by the sixth message.
  • the second network node if the second network node can restore the RRC connection of the terminal device, the second network node sends the second indication information to the terminal device, where the second indication information is used to indicate that the RRC connection of the terminal device is restored and established. Success or failure.
  • S82 and S283 may be before S284 and S85, or may be after S284 and S85, and the application is not limited thereto.
  • FIG. 18 shows still another schematic flowchart of a transmission method 200 according to an embodiment of the present application. As shown in FIG. 18, the method 200 includes:
  • the second network node sends a seventh message to the third network node, where the seventh message is used to indicate that the third network node re-establishes context information of the terminal device saved by the third network node, where the seventh message includes a data radio bearer list of the terminal device and identification information of the terminal device.
  • the second network node is a control plane node of the first system
  • the third network node is a user plane node of the first system.
  • the first system is a CU
  • the second network node is a CU-CP
  • the third network node is a CU-UP. S288.
  • the third network node re-establishes the context information of the terminal device according to the data radio bearer list of the terminal device and the identifier information of the terminal device that are carried by the seventh message.
  • the second network node can restore the RRC connection of the terminal device, the second network node sends second indication information to the terminal device, where the second indication information is used to indicate that the terminal device is in the RRC connection recovery. Established successfully or failed.
  • S87 and S288 may be before S284 and S85, or may be after S284 and S85, and the application is not limited thereto.
  • FIG. 19 is still another schematic flowchart of the transmission method 200 of the embodiment of the present application. It should be understood that the transmission method shown in FIG. 19 is the same as the transmission method shown in FIG. 12, except that the method in FIG. 19 is different.
  • the first network node has a partial RRC function, and the first network node in FIG. 12 does not have an RRC function.
  • the transmission method 200 includes:
  • the terminal device accesses the first network node and the cell managed by the first system, and acquires a first cell radio network temporary identifier of the terminal device.
  • the terminal device sends a random access preamble sequence to the first network node, where the random access preamble sequence is used by the terminal device to initiate random access.
  • the first network node sends a random access response message to the terminal device, where the random access response message includes a second cell wireless network temporary identifier of the terminal device;
  • the first network node sends second indication information to the first system, where the second indication information includes a second cell radio network temporary identifier of the terminal device.
  • the terminal device sends a first message to the first network node, where the first message includes identifier information of the terminal device.
  • the identifier information of the terminal device is at least one of first cell radio network temporary identifier information and physical cell identifier information.
  • the first message is an RRC connection re-establishment request message
  • the terminal device sends an RRC connection re-establishment request message, where the original base station PCI and the original C-RNTI1 are carried in the RRC connection re-establishment request message.
  • the DU forwards the above RRC message to the CU through the F1 interface.
  • the second indication information in the S112 is carried in the same F1AP message, where the RRC connection re-establishment request message is an RRC container.
  • the F1AP message is an initial UE message.
  • the first network node determines, according to the first message, identifier information of the terminal device.
  • the first network node is configured to perform the RRC function, and after the first network node receives the first message, the first message may be parsed to determine the identifier information of the terminal device.
  • the first message is an RRC connection re-establishment request message.
  • the identifier information is at least one of radio network temporary identifier information and physical cell identifier information of the terminal device.
  • the first network node acquires context information of the terminal device saved by the first network node according to the identifier information of the terminal device.
  • the DU may find the context information of the terminal device saved by the DU according to the PCI and/or C-RNTI1 of the terminal device. Restore the corresponding configuration and transmission resources of the terminal device.
  • the first network node sends third indication information to the terminal device, where the third indication information is used to indicate that the RRC connection re-establishment succeeds or fails.
  • the DU sends an RRC message to the terminal device, indicating that the RRC connection re-establishment of the terminal device is successful. Otherwise, the DU sends an RRC reestablishment failure message to the terminal device.
  • the first network node sends fourth indication information to the first system according to the first message, where the fourth indication information is used to indicate that the cell wireless network temporary identifier of the terminal device is changed.
  • the DU sends configuration information to the CU through the F1 interface, and is used to indicate that the C-RNTI of the terminal device changes.
  • the configuration information includes a combination of one or more of the following information: identification information of the terminal device of the F1 interface (terminal device identification information on the F1AP CU side, terminal device identification information on the F1AP DU side, or a terminal of a separate interface) Device identification information), original C-RNTI1, new C-RNTI2, cell identifier, and context identification information of the terminal device (for context associated with the terminal device being saved at the DU, may be the Context ID or other format of the terminal device ID).
  • the first system generates, according to the fourth indication information, a corresponding RRC configuration and/or an RB configuration for the terminal device, and sends the information to the first network device, where the first network device generates the third indication information.
  • S233 occurs after S243.
  • the terminal device sends an RRC connection re-establishment complete message to the first system according to the third indication information.
  • the RRC connection re-establishment completion message is sent by the The first system.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control layer function.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • FIG. 20 shows a schematic flowchart of a transmission method 300 according to an embodiment of the present application. As shown in FIG. 20, the method 300 includes:
  • the first network node determines that a radio link failure occurs between the first network node and the terminal device.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function.
  • the DU finds that the RLF of the link with the terminal device may be caused by a physical layer (such as the number of out-of-sync times exceeding a threshold), exceeding the number of retransmissions of the RLC layer, and the like.
  • a physical layer such as the number of out-of-sync times exceeding a threshold
  • the first network node sends an eighth message to the second network node, where the eighth message is used to indicate to the second network node that a radio link failure occurs between the first network node and the terminal device.
  • the second network node includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function.
  • the eighth message includes at least one of identifier information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • the DU sends a notification message to the CU through the F1 interface, and is used to notify the DU that the terminal device generates an RLF.
  • the message includes a combination of one or more of the following information: identity information of the terminal device on the F1 interface (terminal device identification information on the F1AP CU side, terminal device identification information on the F1AP DU side, or a terminal of a separate interface) Device identification information), C-RNTI, terminal device context identification information (for context associated with the terminal device to be saved at the DU, may be the Context ID of the terminal device or other format ID), RLF indication, RLF reason ( For example, physical layer reasons, RLC layer reasons).
  • the second network node sets a timer according to the eighth message.
  • the second network node sends a ninth message to the first network node, where the ninth message is used to indicate that the first network node releases the context of the terminal device.
  • the CU notifies the DU through the F1 interface, releases the context information of the terminal device, and releases the F1 interface connection.
  • the CU releases the NG interface.
  • the second network node stops the timer if the timer does not time out and the second network node receives the RRC connection message.
  • FIG. 21 is another schematic flowchart of a transmission method 300 according to an embodiment of the present application. As shown in FIG. 21, the method 300 includes:
  • the first network node determines that a radio link failure occurs between the first network node and the terminal device.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function.
  • the first network node sends an eighth message to the second network node, where the eighth message is used to indicate to the second network node that a radio link failure occurs between the first network node and the terminal device.
  • the second network node is a control plane node that is a first system
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the eighth message includes at least one of identifier information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • the DU sends a notification message to the CU-CP through the F1 interface, and is used to notify the DU that the UE has an RLF.
  • the message includes a combination of one or more of the following information: F1 interface UE ID (F1APDU side UEID, F1APCU side UEID or interface UEID), C-RNTI, UEID (for association with the UE to be saved at the DU) Context, which may be the Context ID of the UE or other format ID), RLF indication, RLF reason (physical layer reason, RLC layer reason).
  • the second network node sets a timer according to the eighth message.
  • the second network node sends a ninth message to the first network node, where the ninth message is used to indicate that the first network node releases the context information of the terminal device.
  • the timer expires, and the second network node sends a tenth message to the third network node, where the tenth message is used to indicate that the first network node releases the context information of the terminal device.
  • the third network node is a user plane node of the first system.
  • the CU-CP notifies the DU through the F1 interface, releases the context of the UE and releases the F1 connection.
  • the CU-CP notifies the CU-UP through the E1 interface, releases the context of the UE and releases the Ng-U interface, and the F1 interface and the E1 interface are connected.
  • the CU releases the NG interface.
  • the second network node stops the timer if the timer does not time out and the second network node receives the RRC connection message.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 22 shows a schematic flowchart of a transmission method 400 according to an embodiment of the present application. As shown in FIG. 22, the transmission method 400 includes:
  • the terminal device accesses the first network node and the cell managed by the first system, and establishes an RRC connection.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function.
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function.
  • first network node and the first system are different network nodes when the network device part functions are separated, and the network device includes the first network node and the first system.
  • the first network node may be a source DU
  • the first system may be a source CU.
  • the transmission method in FIG. 14 is to solve the problem of switching the terminal device from the source DU under the source CU to the target DU under the target CU. .
  • the terminal device accesses a cell managed by the CU-DU, and establishes an RRC connection.
  • the C-RNTI of the terminal device is C-RNTI1.
  • Context information of the terminal device is stored at the CU and the DU.
  • the first system determines to switch the terminal device to the fifth network node, and sends a handover request message to the fifth network node.
  • the source CU decides to switch the terminal device to the target CU, and sends a handover request message to the target CU through an inter-base station interface or an interface between the base station and the core network entity RAN-CN.
  • the fifth network node sends a handover preparation message to the fourth network node, where the handover preparation message is used to request the fourth network node to configure the terminal device.
  • the fourth network node may be a target DU
  • the fifth network node may be a target CU.
  • the fourth network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function.
  • the fifth network node includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the handover preparation message is sent to the target DU for requesting the target DU to configure the terminal device.
  • the message includes one or a combination of the following information: the identification information of the terminal device on the F1 interface (the terminal device identification information on the F1AP CU side, the terminal device identification information on the F1AP DU side, or a terminal of a separate interface) Device identification information), the context identification information of the terminal device (the context information used for association to the terminal device to be saved at the DU may be the Context ID of the terminal device or an ID of another format), the SRB list of the terminal device and/or Or DRB list, FB interface configuration information (such as CU side tunnel address and GTP-U TEID), and cellID (such as PCI or ECGI).
  • the identification information of the terminal device on the F1 interface the terminal device identification information on the F1AP CU side, the terminal device identification information on the F1AP DU side, or a terminal of a separate interface
  • Device identification information the context identification information of the terminal device (
  • the fourth network node sends a cell radio network temporary identifier and/or a dedicated random access resource to the fifth network node according to the handover preparation message.
  • the DU allocates a C-RNTI 2 and/or a dedicated RACH resource to the terminal device, and sends the CACH to the CU through the F1 interface message.
  • the specific RACH resource related information includes: beam identification information beam ID, physical resource indication.
  • the fifth network node sends a handover command to the first system, where the handover command includes the cell radio network temporary identifier and/or a dedicated random access resource.
  • the target CU sends a handover command to the source CU through an inter-base station interface or a RAN-CN interface.
  • the handover command carries a configuration performed by the target CU for the terminal device, and includes a C-RNTI2 and a dedicated RACH resource.
  • the first system sends configuration information to the terminal device, where the configuration information includes the cell wireless network temporary identifier and/or a dedicated random access resource.
  • the terminal device accesses the fifth network node by using the cell radio network temporary identifier and/or a dedicated random access resource.
  • the transmission method of the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 23 shows a schematic block diagram of a network device 500 according to an embodiment of the present application.
  • the network device 500 includes:
  • the transceiver module 510 is configured to receive a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device;
  • the processing module 520 is configured to control the transceiver module to send the first message to the first system; the transceiver module is further configured to receive a second message that is sent by the first system according to the first message, where the second message includes the terminal device
  • the identification information of the terminal device is used by the first network node to obtain context information of the terminal device saved by the first network node, or the second message includes context information of the terminal device, where the terminal device
  • the context information is the context information of the access layer.
  • the transceiver module 510 is further configured to receive a third message sent by the first system, where the first network node stores context information of the terminal device according to the third message, or releases context information of the terminal device. .
  • the transceiver module 510 is further configured to receive an indication message sent by the first system, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; the first network node sends the terminal to the terminal The device sends the indication message.
  • the transceiver module 510 is specifically configured to send the first message to the second network node, and receive the second message sent by the second network node according to the first message, where the second network node is the first A control plane node of a system.
  • the identifier information of the terminal device is at least one of recovery identification information of the terminal device, identifier information of the terminal device of the first interface, temporary identifier information of the cell radio network, and physical cell identifier information, where the first The interface is used for data transmission and information interaction between the first network node and the first system.
  • the context information of the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, identifier information of the terminal device, cell identifier information, and connection information of the first interface, where the first interface is used. Data transmission and information interaction between the first network node and the first system.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 24 shows a schematic flowchart of a network device 600 according to an embodiment of the present application.
  • the network device 600 includes:
  • the transceiver module 610 is configured to receive a first message from the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device;
  • the processing module 620 is configured to send, according to the first message, a second message to the first network node, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the Context information of the terminal device saved by a network node, or the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the transceiver module 610 is a transceiver module of the second network node
  • the processing module 620 is a processing module of the second network node
  • the second network node is a control plane node of the first system.
  • the transceiver module 610 is further configured to send a fourth message to the third network node, where the fourth message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the third network node to obtain the third message.
  • the context information of the terminal device saved by the network node, or the second message includes context information of the terminal device; wherein the third network node is a user plane node of the first system.
  • the transceiver module 610 is further configured to send an indication message to the first network node, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; the first network node sends the indication to the terminal device Send the indication message.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 25 shows a schematic flowchart of a network device 700 according to an embodiment of the present application.
  • the network device 700 includes:
  • the transceiver module 710 is configured to receive a fourth message sent by the second network node, where the fourth message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the third network node to obtain the saved by the first network node. Context information of the terminal device, or the fourth message includes context information of the terminal device;
  • the processing module 720 is configured to establish context information of the terminal device according to the fourth message, where the second network node is a control plane node of the first system, and the third network node is a user plane node of the first system .
  • the transceiver module 710 is further configured to receive a fifth message sent by the second network node, where the processing module is further configured to store context information of the terminal device according to the fifth message, or release part of the terminal device Context information, the context information of the terminal device is the context information of the access layer.
  • the context information of the terminal device includes connection information of the second interface, connection information of the third interface, connection information of the fourth interface, radio resource control configuration, data radio bearer parameters, current security context information, and packet data convergence.
  • the third interface is used for data transmission and/or information interaction between the third network node and the second network node, where the fourth interface is used by the third network node and the first network node. Data transfer and/or information interaction.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function; and/or
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 26 shows a schematic flowchart of a network device 800 according to an embodiment of the present application.
  • the network device 800 includes:
  • the transceiver module 810 is configured to receive a first message sent by the terminal device, where the first message is used to request to establish a radio resource control connection of the terminal device;
  • the processing module 820 is configured to determine, according to the first message, identifier information of the terminal device
  • the processing module 820 is further configured to acquire, according to the identifier information of the terminal device, context information of the terminal device saved by the first network node, or
  • the processing module 820 is further configured to receive, according to the identifier information of the terminal device, a second message that is sent by the first system, where the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer. .
  • the transceiver module 810 is further configured to receive a third message sent by the first system, where the processing module is further configured to store context information of the terminal device according to the third message, or release a context of the terminal device. information.
  • the transceiver module 810 further receives and receives an indication message sent by the first system, where the indication message is used to indicate to the first network node that the terminal device enters an inactive state; and sends the indication message to the terminal device.
  • the transceiver module 810 is a transceiver module of the second network node
  • the processing module 820 is a processing module of the second network node
  • the second network node is a control plane node of the first system.
  • the identifier information of the terminal device is at least one of recovery identification information of the terminal device, identifier information of the terminal device of the first interface, temporary identifier information of the cell radio network, and physical cell identifier information, where the first The interface is used for data transmission and information interaction between the first network node and the first system.
  • the context information of the terminal device includes at least one of a radio resource control configuration, a data radio bearer parameter, and connection information of the first interface, where the first interface is used by the first network node and the first system Data transfer and information interaction.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control function layer; and/or
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 27 shows a schematic flowchart of a network device 900 according to an embodiment of the present application.
  • the network device 900 includes:
  • the transceiver module 910 is configured to receive a sixth message sent by the first network node, where the sixth message includes the identifier information of the terminal device, where the sixth message is used by the first system to acquire the context of the terminal device saved by the first system. information;
  • the processing module 920 is configured to send, according to the sixth message, a second message to the first network node, where the second message includes context information of the terminal device, and the context information of the terminal device is context information of the access layer.
  • the transceiver module 910 is a transceiver module of the second network node
  • the processing module 920 is a processing module of the second network node
  • the second network node is a control plane node of the first system.
  • the transceiver module 910 is further configured to send a seventh message to the third network node, where the second message includes the identifier information of the terminal device, where the identifier information of the terminal device is used by the first network node to obtain the first message.
  • the context information of the terminal device saved by the network node, or the second message includes context information of the terminal device; wherein the third network node is a user plane node of the first system.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, a physical layer function, and a radio resource control layer function; and/or
  • the first system includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control function layer.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 28 shows a schematic flowchart of a network device 1000 according to an embodiment of the present application.
  • the network device 1000 includes:
  • the processing module 1010 is configured to determine that a radio link failure occurs between the first network node and the terminal device, where the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function. Species
  • the transceiver module 1020 is configured to send a sixth message to the first system, where the sixth message is used to indicate to the second network node that a radio link failure occurs between the first network node and the terminal device, where the second network
  • the node includes at least one of a packet data convergence protocol layer, a service data adaptation layer, and a radio resource control layer function.
  • the transceiver module 1020 is further configured to receive a seventh message sent by the first system, where the seventh message is used to indicate that the first network node releases the context of the terminal device.
  • the transceiver module 1020 is a transceiver module of the second network node, where the processing module is a processing module of the second network node, and the second network node is a control plane node of the first system.
  • the sixth message includes at least one of identifier information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 29 shows a schematic flowchart of a network device 1100 according to an embodiment of the present application. As shown in FIG. 29, the network device 1100 includes:
  • the transceiver module 1110 is configured to receive a sixth message sent by the first network node, where the sixth message is used to indicate to the first system that a radio link failure occurs between the first network node and the terminal device;
  • the processing module 1120 is configured to set a timer according to the sixth message.
  • the first system sends a seventh message to the first network node, where the seventh message is used to indicate that the first network node releases the context of the terminal device; if the timer does not time out, the first system Upon receiving the RRC connection message, the first system stops the timer.
  • the first network node includes at least one of a radio link layer control protocol layer, a media intervention control layer, and a physical layer function, where the first system includes a packet data convergence protocol layer, a service data adaptation layer, and a wireless At least one of resource control layer functions;
  • the transceiver module 1110 is a transceiver module of the second network node
  • the processing module 1120 is a processing module of the second network node
  • the second network node is a control plane node of the first system.
  • the transceiver module 1110 is further configured to: the timer expires, and send an eighth message to the third network node, where the eighth message is used to indicate that the third network node releases the context information of the terminal device, where The third network node is a user plane node of the first system.
  • the sixth message includes at least one of identifier information of the terminal device, radio link failure indication information, and a cell radio network temporary identifier.
  • the network device in the embodiment of the present application can effectively manage the context of the terminal device when the network device part function is separated into different network nodes.
  • FIG. 30 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application.
  • the network device 1200 includes a processor 1201, a memory 1202, a receiver 1203, and a transmitter 1204. Communication between these components.
  • the memory 1202 is configured to store instructions
  • the processor 1201 is configured to execute instructions stored by the memory 1202, and control the receiver 1203 to receive information and control the transmitter 1204 to transmit information.
  • the processor 1201 is configured to execute instructions stored by the memory 1202, and the processor 1201 can be used to perform corresponding operations and/or functions of the processing module 520 in the network device 500.
  • the receiver 1203 and the transmitter 1204 can be used to The corresponding operations and/or functions of the transceiver module 510 in the network device 500 are performed. For brevity, details are not described herein again.
  • FIG. 31 is a schematic structural diagram of a network device 1300 according to an embodiment of the present application.
  • the network device 1300 includes a processor 1301, a memory 1302, a receiver 1303, and a transmitter 1304. Communication between these components.
  • the memory 1302 is configured to store instructions
  • the processor 1301 is configured to execute the instructions stored by the memory 1302, and control the receiver 1303 to receive information and control the transmitter 1304 to transmit information.
  • the processor 1301 is configured to execute instructions stored by the memory 1302, and the processor 1301 can be used to perform corresponding operations and/or functions of the processing module 620 in the network device 600.
  • the receiver 1303 and the transmitter 1304 can be used to The corresponding operations and/or functions of the transceiver module 610 in the network device 600 are performed. For brevity, details are not described herein again.
  • FIG. 32 is a schematic structural diagram of a network device 1400 according to an embodiment of the present application.
  • the network device 1400 includes a processor 1401, a memory 1402, a receiver 1403, and a transmitter 1404. Communication between these components.
  • the memory 1402 is configured to store instructions
  • the processor 1401 is configured to execute instructions stored by the memory 1402, and control the receiver 1403 to receive information and control the transmitter 1404 to transmit information.
  • the processor 1401 is configured to execute instructions stored by the memory 1402, and the processor 1401 can be used to perform corresponding operations and/or functions of the processing module 720 in the network device 700.
  • the receiver 1403 and the transmitter 1404 can be used to The corresponding operations and/or functions of the transceiver module 710 in the network device 700 are performed. For brevity, details are not described herein again.
  • FIG. 33 is a schematic structural diagram of a network device 1500 according to an embodiment of the present application.
  • the network device 1500 includes a processor 1501, a memory 1502, a receiver 1503, and a transmitter 1504. Communication between these components.
  • the memory 1502 is configured to store instructions
  • the processor 1501 is configured to execute the instructions stored by the memory 1502, and control the receiver 1503 to receive information and control the transmitter 1504 to transmit information.
  • the processor 1501 is configured to execute instructions stored by the memory 1502, and the processor 1501 can be used to perform corresponding operations and/or functions of the processing module 820 in the network device 800.
  • the receiver 1503 and the transmitter 1504 can be used to The corresponding operations and/or functions of the transceiver module 810 in the network device 800 are performed. For brevity, details are not described herein again.
  • FIG. 34 is a schematic structural diagram of a network device 1600 according to an embodiment of the present application.
  • the network device 1600 includes a processor 1601, a memory 1602, a receiver 1603, and a transmitter 1604. The communication between these components is connected.
  • the memory 1602 is for storing instructions for executing the instructions stored by the memory 1602, and controlling the receiver 1603 to receive information and controlling the transmitter 1604 to transmit information.
  • the processor 1601 is configured to execute instructions stored by the memory 1602.
  • the processor 1601 can be used to perform corresponding operations and/or functions of the processing module 920 in the network device 900.
  • the receiver 1603 and the transmitter 1604 can be used to The corresponding operations and/or functions of the transceiver module 910 in the network device 900 are performed. For brevity, details are not described herein again.
  • FIG. 35 is a schematic structural diagram of a network device 1700 according to an embodiment of the present application.
  • the network device 1700 includes a processor 1701, a memory 1702, a receiver 1703, and a transmitter 1704. Communication between these components.
  • the memory 1702 is for storing instructions
  • the processor 1701 is configured to execute the instructions stored by the memory 1702, and control the receiver 1703 to receive information and control the transmitter 1704 to send information.
  • the processor 1701 is configured to execute instructions stored by the memory 1702, and the processor 1701 can be used to perform corresponding operations and/or functions of the processing module 1010 in the network device 1000.
  • the receiver 1703 and the transmitter 1704 can be used to The corresponding operations and/or functions of the transceiver module 1020 in the network device 1000 are performed. For brevity, details are not described herein again.
  • FIG. 36 is a schematic structural diagram of a network device 1800 according to an embodiment of the present application.
  • the network device 1800 includes a processor 1801, a memory 1802, a receiver 1803, and a transmitter 1804. Communication between these components.
  • the memory 1802 is for storing instructions
  • the processor 1801 is configured to execute the instructions stored by the memory 1802, and control the receiver 1803 to receive information and control the transmitter 1804 to transmit information.
  • the processor 1801 is configured to execute instructions stored by the memory 1802, and the processor 1801 can be used to perform corresponding operations and/or functions of the processing module 1120 in the network device 1100.
  • the receiver 1803 and the transmitter 1804 can be used to The corresponding operations and/or functions of the transceiver module 1110 in the network device 1100 are performed. For brevity, details are not described herein again.
  • the embodiment of the present application further provides a chip system, which is applied to a network device, where the chip system includes: at least one processor, at least one memory, and an interface circuit, where the interface circuit is responsible for information interaction between the chip system and the outside world.
  • the at least one memory, the interface circuit, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the at least one processor to perform the various aspects described above The operation of the network device in the method described.
  • the embodiment of the present application further provides a communication system, including: a network device, and/or a terminal device; wherein the network device is the network device described in the foregoing aspects.
  • the embodiment of the present application further provides a computer program product, which is applied to a network device, where the computer program product includes a series of instructions, when the instruction is executed, to perform the method described in the above aspects.
  • the operation of the network device is not limited to a network device.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the computer program product can include one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic disk), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.

Abstract

本申请提供了一种传输方法及网络设备，该传输方法包括：第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一网络节点向第一系统发送该第一消息；该第一网络节点接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息。本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。

Description

一种传输方法和网络设备
本申请要求于2018年8月11日提交中国专利局、申请号为201710685352.9、申请名称为“一种传输方法和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及领域通信领域，并且更具体地，涉及一种传输方法和网络设备。
背景技术
在第五代移动通信(the 5th Generation mobile communication technology，5G)系统中，基站可以由集中式单元(Centralized Unit,CU)和分布式单元(Distributed Unit,DU)构成，即对原接入网中的基站的功能进行拆分，将基站的部分功能部署在一个CU，将剩余功能部署在多个DU，多个DU共用一个CU，可以节省成本，以及易于网络扩展。
CU和DU的切分可以按照协议栈切分，其中一种可能的方式是将无线资源控制(Radio Resource Control，RRC)以及分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层部署在CU，其余的无线链路控制(Radio Link Control，RLC)层、介质访问控制(Media Access Control，MAC)层以及物理层部署在DU。
当终端设备接入小区后，会在网络设备建立相应的该终端设备的上下文，终端设备状态改变后，网络设备会随之处理该终端设备上下文。例如，终端设备从连接态到空闲态，网络设备会释放该终端设备的上下文。此外，5G中，为终端设备引入了一个新的RRC状态/RRC子状态，称之为inactive态(也叫第三态)，当终端设备的RRC状态发生变化时，CU需要通知DU进行联动的上下文处理，目前没有相应的方案解决在网络设备功能分离时，CU和DU对终端设备的上下文管理方法。
同时，网络设备发现终端设备发生无线链路失败(Radio Link Failure，RLF)，以及切换(Hand Over，HO)场景中也没有相应的方案解决CU和DU对终端设备的上下文管理方法。
发明内容
本申请实施例的传输方法和网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
第一方面，提供了一种传输方法，该传输方法包括：第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一网络节点向第一系统发送该第一消息；该第一网络节点接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设 备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
在一些可能的实现方式中，第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一网络节点向第二网络节点发送该第一消息；该第一网络节点接收该第二网络节点根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息。
在一些可能的实现方式中，该第二网络节点为该第一系统的控制面节点。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第一方面，在第一方面的第一种可能的实现方式中，该第一网络节点接收终端设备发送的第一消息之前，该方法还包括：该第一网络节点接收该第一系统发送的第三消息；该第一网络节点根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
在一些可能的实现方式中，该第一网络节点接收终端设备发送的第一消息之前，该方法还包括：该第一网络节点接收该第一系统发送的指示消息，该指示消息用于指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该第一网络节点向第一系统发送该第一消息，包括：该第一网络节点向第二网络节点发送该第一消息，该第二网络节点为该第一系统的控制面节点；其中，该第一网络节点接收该第一系统根据该第一消息发送的第二消息，包括：该第一网络节点接收该第二网络节点根据该第一消息发送的该第二消息。
结合第一方面、第一方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第一方面的第三种可能的实现方式中，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第一方面、第一方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第一方面的第四种可能的实现方式中，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数、该终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第一方面、第一方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第一方面的第五种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第二方面，提供了一种传输方法，该传输方法包括：第一系统接收来自于终端设备的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一系统根据该第一消息，向第一网络节点发送第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文 信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
在一些可能的实现方式中，第二网络节点接收来自于终端设备的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第二网络节点根据该第一消息，向第一网络节点发送第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息。
在一些可能的实现方式中，该第二网络节点为该第一系统的控制面节点。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第二方面，在第二方面的第一种可能的实现方式中，该第一系统接收来自于终端设备的第一消息，包括：第二网络节点接收来自于该终端设备的第一消息，该第二网络节点为该第一系统的控制面节点；其中，该第一系统根据该第一消息，向第一网络节点发送第二消息，包括：该第二网络节点根据该第一消息，向该第一网络节点发送该第二消息。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，该方法还包括：该第二网络节点向第三网络节点发送第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于该第三网络节点获取该第三网络节点保存的该终端设备的上下文信息，或者，该第四消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
在一些可能的实现方式中，该第一系统接收来自于终端设备的第一消息之前，该方法还包括：该第一系统向该第一网络节点发送指示消息，该指示消息用于指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第二方面、第二方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第二方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第三方面，提供了一种传输方法，该方法包括：第三网络节点接收第二网络节点发送的第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于该第三网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第四消息包括该终端设备的上下文信息；该第三网络节点根据该第四消息，建立该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息；其中，该第二网络节点为第一系统的控制面节点，该第三网络节点为该第一系统的用户面节点。
在一些可能的实现方式中，该第三网络节点为第一系统的用户面节点。
结合第三方面，在第三方面的第一种可能的实现方式中，该第三网络节点接收第二网络节点发送的第四消息之前，该方法还包括：该第三网络节点接收该第二网络节点发送的第五消息；该第三网络节点根据该第五消息，存储该终端设备的上下文信息，或者，释放部分该终端设备的上下文信息。
结合第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，该终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接 信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第二接口用于所述第三网络节点和核心网之间进行数据传输和/或信息交互，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行数据传输和/或信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输和/或信息交互。
在一些可能的实现方式中，该第三网络节点处保存的该终端设备上下文信息包括第一接口的连接信息、第二接口的连接信息、当前安全上下文信息、分组数据汇聚协议状态和用于识别该终端设备的标识信息，该第三网络节点释放的该终端设备的上下文信息包括分组数据汇聚协议状态和该第四接口的连接信息中的至少一种。
结合第三方面、第三方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第三方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第四方面，提供了一种传输方法，该方法包括：第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一网络节点根据该第一消息，确定该终端设备的标识信息；该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，该第一网络节点根据该终端设备的标识信息，接收第一系统发送的第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
在一些可能的实现方式中，第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；该第一网络节点根据该第一消息，确定该终端设备的标识信息；该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，该第一网络节点根据该终端设备的标识信息，接收第二网络节点发送的第二消息，该第二消息包括该终端设备的上下文信息。
在一些可能的实现方式中，该第二网络节点为该第一系统的控制面节点。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第四方面，在第四方面的第一种可能的实现方式中，该第一网络节点接收终端设备发送的第一消息之前，该方法还包括：该第一网络节点接收该第一系统发送的第三消息；该第一网络节点根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
在一些可能的实现方式中，该第一网络节点接收终端设备发送的第一消息之前，该方法还包括：该第一网络节点接收该第一系统发送的指示消息，该指示消息用于指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第四方面或第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，该第一网络节点根据该终端设备的标识信息，接收第一系统发送的第二消息，包括：该第一网络节点根据该终端设备的标识信息，接收第二网络节点发送的第二消息，该第二网络节点为该第一系统的控制面节点。
结合第四方面、第四方面的第一种和第二种可能的实现方式中的任一种可能的实现方 式，在第四方面的第三种可能的实现方式中，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第四方面、第四方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第四方面的第四种可能的实现方式中，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第四方面、第四方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第四方面的第五种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制功能层中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
第五方面，提供了一种传输方法，该方法包括：第一系统接收第一网络节点发送的第六消息，该第六消息包括该终端设备的标识信息，该第六消息用于指示该第一系统获取该第一系统保存的该终端设备的上下文信息；该第一系统根据该第二消息，向该第一网络节点发送第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
在一些可能的实现方式中，第二网络节点接收第一网络节点发送的第六消息，该第六消息包括该终端设备的标识信息，该第五消息用于指示该第二网络节点获取该第二网络节点保存的该终端设备的上下文信息；该第二网络节点根据该第二消息，向该第一网络节点发送第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息。
在一些可能的实现方式中，该第二网络节点为该第一系统的控制面节点。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第五方面，在第五方面的第一种可能的实现方式中，该第一系统接收第一网络节点发送的第六消息，包括：第二网络节点接收该第一网络节点发送的第六消息，该第二网络节点为该第一系统的控制面节点；其中，该第一系统根据该第六消息，向该第一网络节点发送第二消息，包括：该第二网络节点根据该第六消息，向该第一网络节点发送该第二消息。
在一些可能的实现方式中，该第一系统接收第一网络节点发送的第六消息之前，该方法还包括：该第一系统向该第一网络节点发送指示消息，该指示消息用于指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，该方法还包括：该第二网络节点向第三网络节点发送第七消息，该第七消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第七消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
结合第五方面、第五方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第五方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能层中的至少一种。
第六方面，提供了一种传输方法，该方法包括：第一网络节点确定该第一网络节点与该终端设备之间发生无线链路失败，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；该第一网络节点向该第一系统发送第六消息，该第六消息用于向所述第二网络节点指示所述第一网络节点与所述终端设备之间发生无线链路失败，该第二网络节点包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
结合第六方面，在第六方面的第一种可能的实现方式中，该方法还包括：该第一网络节点接收该第一系统发送的第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文。
结合第六方面或第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，该第一网络节点向该第一系统发送第六消息，包括：该第一网络节点向第二网络节点发送该第六消息，该第二网络节点为该第一系统的控制面节点。
结合第六方面、第六方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第六方面的第三种可能的实现方式中，所述第六消息包括所述终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
第七方面，提供了传输方法，该方法包括：第一系统接收第一网络节点发送的第六消息，该第六消息用于向该第一系统指示该第一网络节点与终端设备之间发生无线链路失败，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种；该第一系统根据该第六消息，设置定时器；若该定时器超时，该第一系统向该第一网络节点发送第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文；若该定时器未超时该第一系统收到无线资源控制连接消息，该第一系统停止该定时器。
结合第七方面，在第七方面第一种可能的实现方式中，该第一系统接收第一网络节点发送的第六消息，包括：第二网络节点接收该第一网络节点发送的该第六消息，该第二网络节点为该第一系统的控制面节点；其中，该第一系统根据该第六消息，设置定时器，包括：该第二网络节点根据该第六消息，设置定时器。
结合第七方面的第一种可能的实现方式，在第七方面的第二种可能的实现方式中，该方法还包括：该定时器超时，该第二网络节点向第三网络节点发送第八消息，所述第八消息用于指示该第三网络节点释放部分该终端设备的上下文信息，其中，该第三网络节点为该第一系统的用户面节点。
结合第七方面、第七方面的第一种和第二种可能的实现方式中任一种可能的实现方式，在第七方面的第三种可能的实现方式中，该第六消息包括该终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
第八方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；处理模块，用于控制该收发模块向第一系统发送该第一消息；该收发模块还用于接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第八方面，在第八方面的第一种可能的实现方式中，该收发模块还用于接收该第一系统发送的第三消息；该第一网络节点根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
在一些可能的实现方式中，该第收发模块还用于接收该第一系统发送的指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第八方面或第八方面的第一种可能的实现方式，在第八方面的第二种可能的实现方式中，该收发模块具体用于向第二网络节点发送该第一消息；接收该第二网络节点根据该第一消息发送的该第二消息；其中，该第二网络节点为该第一系统的控制面节点。
结合第八方面、第八方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第八方面的第三种可能的实现方式中，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第八方面、第八方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第八方面的第四种可能的实现方式中，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第八方面、第八方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第八方面的第五种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第九方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收来自于终端设备的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；处理模块，用于根据该第一消息，向第一网络节点发送第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第九方面，在第九方面的第一种可能的实现方式中，该收发模块为第二网络节点 的收发模块，该第二网络节点为该第一系统的控制面节点。
结合第九方面的第一种可能的实现方式，在第九方面的第二种可能的实现方式中，该收发模块还用于向第三网络节点发送第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于该第三网络节点获取该第三网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
在一些可能的实现方式中，该收发模块还用于向该第一网络节点发送指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
结合第九方面、第九方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第九方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第十方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收第二网络节点发送的第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于该第三网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第四消息包括该终端设备的上下文信息；处理模块，用于根据该第四消息，建立该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息；其中，该第二网络节点为第一系统的控制面节点，该第三网络节点为该第一系统的用户面节点。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第十方面，在第十方面的第一种可能的实现方式中，该收发模块还用于接收该第二网络节点发送的第五消息；该处理模块还用于根据该第五消息，存储该终端设备的上下文信息，或者，释放部分该终端设备的上下文信息。
结合第十方面的第一种可能的实现方式，在第十方面的第二种可能的实现方式中，该终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第二接口用于所述第三网络节点和核心网之间进行数据传输和/或信息交互，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行数据传输和/或信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输和/或信息交互。
结合第十方面、第十方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第十方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
第十一方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；处理模块，用于根据该第一消息，确定该终端设备的标识信息；该处理模块还用于根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，该处理模块还用 于根据该终端设备的标识信息，接收第一系统发送的第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第十一方面，在第十一方面的第一种可能的实现方式中，该收发模块还用于接收该第一系统发送的第三消息；该处理模块还用于根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
在一些可能的实现方式中，该收发模块还用与接收该第一系统发送的指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；向该终端设备发送该指示消息。
结合第十一方面或第十一方面的第一种可能的实现方式，在第十一方面的第二种可能的实现方式中，该处理模块为第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
结合第十一方面、第十一方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第十一方面的第三种可能的实现方式中，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第十一方面、第十一方面的第一种至第三种可能的实现方式中的任一种可能的实现方式，在第十一方面的第四种可能的实现方式中，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
结合第十一方面、第十一方面的第一种至第四种可能的实现方式中的任一种可能的实现方式，在第十一方面的第五种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制功能层中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
第十二方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收第一网络节点发送的第六消息，该第六消息包括该终端设备的标识信息，该第六消息用于第一系统获取该第一系统保存的该终端设备的上下文信息；处理模块，用于根据该第六消息，向该第一网络节点发送第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第十二方面，在第十二方面的第一种可能的实现方式中，该收发模块为第二网络节点的收发模块，该处理模块为该第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
结合第十二方面的第一种可能的实现方式，在第十二方面的第二种可能的实现方式中，该收发模块还用于向第三网络节点发送第七消息，该第七消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备 的上下文信息，或者，该第七消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
结合第十二方面、第十二方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第十二方面的第三种可能的实现方式中，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能层中的至少一种。
第十三方面，提供了一种网络设备，该网络设备包括：处理模块，用于确定该第一网络节点与该终端设备之间发生无线链路失败，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；收发模块，用于向该第一系统发送第六消息，该第六消息用于向该第二网络节点指示该第一网络节点与该终端设备之间发生无线链路失败，该第二网络节点包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第十三方面，在第十三方面的第一种可能的实现方式中，该收发模块还用于接收该第一系统发送的第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文。
结合第十三方面或第十三方面的第一种可能的实现方式，在第十三方面的第二种可能的实现方式中，该收发模块为第二网络节点的收发模块，该处理模块为第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
结合第十三方面、第十三方面的第一种和第二种可能的实现方式中的任一种可能的实现方式，在第十三方面的第三种可能的实现方式中，所述第六消息包括所述终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
第十四方面，提供了一种网络设备，该网络设备包括：收发模块，用于接收第一网络节点发送的第六消息，该第六消息用于向该第一系统指示该第一网络节点与终端设备之间发生无线链路失败，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种；处理模块，用于根据该第六消息，设置定时器；若该定时器超时，该第一系统向该第一网络节点发送第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文；若该定时器未超时该第一系统收到无线资源控制连接消息，该第一系统停止该定时器。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
结合第十四方面，在第十四方面第一种可能的实现方式中，该收发模块为第二网络节点的收发模块，该处理模块为第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
结合第十四方面的第一种可能的实现方式，在第十四方面的第二种可能的实现方式中，该收发模块还用于：该定时器超时，向第三网络节点发送第八消息，所述第八消息用于指示该第三网络节点释放该终端设备的上下文信息，其中，该第三网络节点为该第一系 统的用户面节点。
结合第十四方面、第十四方面的第一种和第二种可能的实现方式中任一种可能的实现方式，在第十四方面的第三种可能的实现方式中，该第六消息包括该终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
第十五方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第一方面及第一方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第一方面及第一方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第十六方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第二方面及第二方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第二方面及第二方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第十七方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第三方面及第三方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第三方面及第三方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第十八方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第四方面及第四方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第四方面及第四方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第十九方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第五方面及第五方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第五方面及第五方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第二十方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第六方面及第六方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第六方面及第六方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第二十一方面，提供了一种网络设备，该网络设备包括存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行第七方面及第七方面的任一种可能的实现方式中的方法中，在所述网络设备进行的消息收发的操作；所述至少一个处理器调用所述存储器中存储的所述指令，执行第七方面及第七方面的任一种可能的实现方式中的方法中，在所述网络设备进行的处理操作。
第二十二方面，提供了一种芯片系统，应用于网络设备中，该芯片系统包括：至少一个处理器、至少一个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述至少一个存储器、所述接口电路和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有指令；所述指令被所述至少一个处理器执行，以进行上述各个方面的所述的方法中所述网络设备的操作。
第二十三方面，提供了一种通信系统，包括：网络设备，和/或，终端设备；其中，所述网络设备为上述各个方面所述的网络设备。
第二十四方面，提供了一种计算机程序产品，应用于网络设备中，所述计算机程序产品包括一系列指令，当所述指令被运行时，以进行上述各个方面的所述的方法中所述网络设备的操作。
第二十五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各个方面的所述的方法。
附图说明
图1是根据本申请实施例的技术方案的应用场景的示意图。
图2是根据本申请实施例的技术方案的应用场景的另一示意图。
图3是根据本申请实施例的技术方案的应用场景的再一示意图。
图4是根据本申请实施例的技术方案的应用场景的再一示意图。
图5是根据本申请实施例的技术方案的应用场景的再一示意图。
图6是根据本申请实施例的传输方法的示意性流程图。
图7是根据本申请实施例的传输方法的另一示意性流程图。
图8是根据本申请实施例的传输方法的再一示意性流程图。
图9是根据本申请实施例的传输方法的再一示意性流程图。
图10是根据本申请实施例的传输方法的再一示意性流程图。
图11是根据本申请实施例的传输方法的再一示意性流程图。
图12是根据本申请实施例的传输方法的再一示意性流程图。
图13是根据本申请实施例的传输方法的再一示意性流程图。
图14是根据本申请实施例的传输方法的再一示意性流程图。
图15是根据本申请实施例的传输方法的再一示意性流程图。
图16是根据本申请实施例的传输方法的再一示意性流程图。
图17是根据本申请实施例的传输方法的再一示意性流程图。
图18是根据本申请实施例的传输方法的再一示意性流程图。
图19是根据本申请实施例的传输方法的再一示意性流程图。
图20是根据本申请实施例的传输方法的再一示意性流程图。
图21是根据本申请实施例的传输方法的再一示意性流程图。
图22是根据本申请实施例的传输方法的再一示意性流程图。
图23是根据本申请实施例的网络设备的示意性框图。
图24是根据本申请实施例的网络设备的另一示意性框图。
图25是根据本申请实施例的网络设备的再一示意性框图。
图26是根据本申请实施例的网络设备的再一示意性框图。
图27是根据本申请实施例的网络设备的再一示意性框图。
图28是根据本申请实施例的网络设备的再一示意性框图。
图29是根据本申请实施例的网络设备的再一示意性框图。
图30是根据本申请实施例的网络设备的再一示意性框图。
图31是根据本申请实施例的网络设备的再一示意性框图。
图32是根据本申请实施例的网络设备的再一示意性框图。
图33是根据本申请实施例的网络设备的再一示意性框图。
图34是根据本申请实施例的网络设备的再一示意性框图。
图35是根据本申请实施例的网络设备的再一示意性框图。
图36是根据本申请实施例的网络设备的再一示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例适用于各种形式的包含网络设备中部分功能分离的系统，图1示出了本申请实施例的技术方案的一种应用场景的示意图，如图1所示，该网络设备中部分功能分离为第一网络节点和第二网络节点。
具体地，图2示出了本申请实施例的技术方案的另一种应用场景的示意图，如图2所示，在CRAN架构中，引入了CU-DU的切分，DU可以对应于图1中的第一网络节点，CU对应于图1中的第二网络节点。
应理解，第一网络节点和第二网络节点可以是一个整体网络架构中的两个物理或者逻辑分离模块，也可以是完全独立的两个逻辑网元。
还应理解，该第二网络节点可以进行控制面和用户面分离，形成第二网络节点的用户面和第二网络节点的控制面。
CU具有无线资源控制(Radio Resource Control，RRC)或者部分RRC控制功能，包含现有基站的所有的协议层功能或者部分协议层功能；比如只包含RRC功能或者部分RRC功能，或者包含RRC功能或者业务数据适配协议(Service Data Adaptation Protocol,SDAP)层功能，或者包含RRC/分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层功能，或者包含RRC/PDCP以及部分无线链路层控制协议(Radio Link Control，RLC)层功能；或者包含RRC/PDCP/媒体介入控制(Media Access Control，MAC)层，甚至部分或者全部物理层PHY功能，也不排除其它任何可能性。
DU具有现有基站的全部或者部分协议层功能，即RRC/SDAP/PDCP/RLC/MAC/PHY的部分协议层功能单元，比如包含部分RRC功能和PDCP/RLC/MAC/PHY等协议层功能，或者包含PDCP/RLC/MAC/PHY等协议层功能，或者包含RLC/MAC/PHY等协议层功能或者包含部分RLC/MAC/PHY功能，或者只包含全部或者部分PHY功能；需要注意的是这里提及的各个协议层的功能可能发生变化，均在本申请保护的范围内。
应理解，在本申请实施例中，可以将不同的协议层分别部署在第一网络节点和第二网络节点中，一种可能的实现方式是，在第二网络节点中至少部署第一协议层，在第一网络节点中至少部署第二协议层和第三协议层，
例如，第一协议层可以为RRC层，第二协议层可以为MAC层，第三协议层可以为PHY层。
应理解，上述对第一协议层、第二协议层和第三协议层的列举仅为示例性说明，不应对本申请构成任何限定。该第一协议层和第二协议层也可以为现有协议(例如，LTE协议)或者未来协议中定义的其他协议层，本申请对此并未特别限定。
又例如，在5G网络中，新型的中继节点也有新的技术进展，例如，中继节点仅部署有层2(例如，包括无线链路控制(resource link control，RLC)层、MAC层等)和层1(例如，包括PHY层)的协议栈架构，而未部署层2以上的全部协议栈功能，例如全部RRC层功能。因此，宿主基站产生的数据或信令，需要由中继节点转发给终端设备。
应理解，本申请实施例中的第一网络节点可以对应于CU-DU架构中的DU，也可以对应于上述中继节点，第二网络节点可以对应于CU-DU架构中的CU，也可以对应于上述宿主基站。
图3示出了根据本申请实施例的技术方案的再一种应用场景的示意图，如图3所示，RRC层放在CU，MAC层放在DU。上行RRC消息，DU空口接收到终端设备发送的消息后，经过DU处理后，通过CU-DU之间的接口，将RRC消息发送个CU。下行RRC消息，CU生成后通过CU-DU之间的接口，发送给DU，DU处理后，通过空口发送给终端设备。
图4示出了根据本申请实施例的技术方案的再一种应用场景的示意图，如图4所示，DU具有部分RRC功能，如信令无线承载SRB0的处理，则上述RRC消息可以由DU处理。
应理解，当前第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)将CU-DU之间的接口命名为F1，F1接口上包含控制面(Control Plane，CP)和用户面(User Plane，UP)，控制面的传输层协议为流控制传输协议(Stream Control Transmission Protocol，SCTP)，传输的应用层消息为F1AP(Application Protocol)消息。用户面的传输层协议为用户层面的GPRS隧道协议(GPRS Tunnelling Protocol-User plane，GTP-U)。
图5示出了根据本申请实施例的技术方案的再一种应用场景的示意图，如图5所示，将CU进行控制面和用户面分离时，CU-CP负责控制面功能，例如SRB的处理，可能具有RRC层和负责处理SRB的PDCP层；CU-UP负责用户面功能，如DRB的管理，与核心网用户面网元对接，可能具有负责处理DRB的SDAP层和PDCP层。
E1接口是CU-CP和CU-UP之间的接口。CU-UP和DU之间是F1-U连接，CU-CP和DU之间是F1-C连接。CU-UP和核心网之间是Ng-U连接，CU-CP和核心网之间是Ng-C连接。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile Communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、未来的第五代(5th-Generation，5G)通信系统以及CRAN等通信系统。
还应理解，本申请实施例的网络设备可以是用于与终端设备进行通信的设备，例如，可以是GSM系统或CDMA中的基站(Base Transceiver Station，BTS)与基站控制器(Base Station Controller，BSC)的结合，也可以是WCDMA系统中的基站(NodeB，NB)与无线网控制器(Radio Network Controller，RNC)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的接入网设备，比如下一代基站，或未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的接入网设备等。
具体地，第三代移动通信技术(3rd-Generation，3G)中的UMTS系统，存在无线网络控制节点和基站分离的场景；在LTE系统中，存在有基带模块和射频模块分离的情景，即射频拉远的场景；数据中心(Data Center，DC)场景，需要两个不同的网络之间互联；大小站场景，大小站相互连接存在接口；LTE与Wifi聚合(LTE-Wifi aggregation，LWA)场景；在5G系统中存在各种无小区(non-cell)场景(终端可以在各个小区之间自由随意切换，各个小区之间没有明确的界线)，存在一个控制节点和所有小区连接，或者在小区下面连接各个传输节点；CRAN场景，存在BBU切分的场景；CRAN虚拟化场景，BBU的某一部分功能集中部署，虚拟化，另外一部分功能分开部署，两个部分之间存在物理分开部署可能性；应理解，不同系统/制式共存场景都在本申请适用的范围内。
本申请结合终端设备描述了各个实施例。终端设备也可以指用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者PLMN中的终端设备等。
图6示出了根据本申请实施例的传输方法100的示意性流程图，如图6所示，该传输方法100包括：
S110，第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；
S120，该第一网络节点向第一系统发送该第一消息；
S130，该第一网络节点接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数、该终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
S140，该第一网络节点根据该第二消息携带的该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，重建该终端设备的上下文信息。
可选地，该第一消息为RRC连接恢复建立请求消息或RRC连接重建立请求消息。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能 中的至少一种；和/或该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
具体而言，终端设备向第一网络节点发送第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接，由于第一网络节点不具备部分RRC功能，将该第一消息转发给该第一系统，该第一系统接收到该第一消息后，对该第一消息进行处理后，向该第一网络节点发送第二消息，该第一网络节点接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息。例如，该第一网络节点为DU，该第一系统为CU，终端设备向DU发送RRC连接恢复建立请求消息，DU通过F1接口将该RRC连接恢复建立请求消息转发给CU，CU收到该消息后，若能够恢复该终端设备的RRC连接，则发送F1接口控制面消息给DU，用于指示DU找到DU保存的该终端设备的上下文信息，或者用于指示DU重建该终端设备的上下文信息，DU收到该控制面消息后，找到保存的该终端设备的上下文信息或者重建该终端设备的上下文信息，CU向该终端设备发送RRC消息(该RRC消息通过F1接口发送给DU，由DU转发给该终端设备)，用于指示该RRC连接建立成功或者失败。
图7示出了根据本申请实施例的传输方法100的另一示意性流程图，如图7所示，该传输方法100还包括：
S101，该第一系统向该终端设备发送第一命令，该第一命令用于指示该终端设备进入非激活态。
具体而言，该第一系统向该第一网络节点发送第一命令，该第一命令用于指示该终端设备进入非激活态，该第一网络节点不对该第一命令的内容进行解析或更改，将该第一命令经过第一网络节点上部署的协议层进行相应处理后，将处理后的第一命令发送给该终端设备。
例如，该第一命令可以为RRC消息，CU通过RRC消息命令该终端设备进入inactive mode，该RRC消息中携带进入inactive mode指示和该终端设备的resume ID。该第一命令还可能包含是否挂起一个或多个信令无线承载(SRB)/数据无线承载(DRB)的指示和/或对应的无线承载标识信息。该RRC消息由CU通过F1接口发给DU，DU处理后发送给该终端设备。
可选地，该消息为RRC连接释放消息(RRC Connection Release message)。或者，该消息为RRC连接挂起消息(RRC Connection Suspend message)。
需要说明的是，步骤S102也可以发生在步骤S101之前。
S102，该第一系统向该第一网络节点发送第三消息，该第三消息用于向该第一网络节点指示该终端设备进入非激活态。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
具体而言，终端设备接入第一网络节点和第一系统管理下的小区，建立RRC连接，第一系统决定将该终端设备置为非激活态(inactive mode)，则向该第一网络节点发送第三消息，该第三消息用于向该第一网络节点指示该终端设备进入非激活态。
例如，CU通过F1接口向DU发送指示消息，用于指示该终端设备进行inactive mode。 该指示通过F1接口控制面消息发送，指示消息中包括以下信息中的一种或多种的组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，进入inactive mode指示，重返标识Resume ID(当网络指示UE进入inactive mode时为UE分配的标识，用于UE向网络请求恢复RRC连接时，携带该标识便于网络接入存储的上下文)，终端设备的小区无线网络临时标识C-RNTI，终端设备上下文标识信息(用于关联到该终端设备在DU处保存的上下文，例如可以为该终端设备的Context ID，或其他格式的ID)，是否挂起一个或多个信令无线承载(SRB)/数据无线承载(DRB)的指示和/或对应的无线承载标识信息。
进一步可选的，CU通过F1接口发送该第一命令给DU时，作为RRC容器container与S102中的第三消息携带在同一个F1AP消息中发送。
应理解，对于终端设备的下行数据传输，第一系统将来自核心网的属于该终端设备的数据发送给第一网络节点，由第一网络节点负责为该终端设备调度空口传输资源，并进一步将下行数据发送给该终端设备；类似的，对于上行数据，终端设备先向第一网络节点请求上行数据传输资源，进而在授权的上行资源上将上行数据发送给第一网络节点，之后由第一网络节点发送给第一系统。
由此可见，空口上是否有该终端设备的上下行数据传输，例如第二网络节点的下行数据缓存是否还有数据待发送，以及终端设备是否有上行数据待发送，第一系统并不一定知道。例如，第一系统已经将属于某终端设备的来自核心网的所有数据发送给第二网络节点，并准备指示该终端设备进入inactive mode，因此，第一系统发送第一命令给终端设备，并发送第三消息给第一网络节点，此时第一网络节点与该终端设备之间还有上行和/或下行数据发送，如果该终端设备收到第一命令后即进入inactive mode，则可能会产生下行数据丢失，和/或，第一网络节点收到第三消息后即挂起该终端设备的数据收发，则可能会产生上行数据的丢失。
可选地，在该第一系统向该终端设备发送第一命令之前，该方法100还包括：
该第一系统确定该第一网络节点的上行或者下行数据发送完毕。
具体而言，该第一系统在发送该第三消息和该第一命令之前，与该第一网络节点协商，待第一网络节点准备好(例如，上下行数据发送完毕后)，再发送第一命令和第三消息。具体可以为第一系统发送数据发送状态询问消息给第一网络节点，该数据发送状态询问消息用于询问第一网络节点是否已经完成与该终端设备之间的数据传输，第一网络节点发送响应消息给第一系统，该响应消息用于指示第一系统第一网络节点与该终端设备之间的数据传输是否已经完成。
可选地，该第一系统向该终端设备发送第一命令，该方法100还包括：
该第一系统向该第一网络节点发送该第一命令；
当该第一网络节点确定该第一网络节点的上行或者下行数据发送完毕，该第一网络节点向该终端设备发送该第一命令。
具体而言，该第一网络节点确定该第一命令的内容，即该第一网络节点确定该第一系统即将命令终端设备进入inactive mode，从而进行相应处理，待该第一网络节点准备好(例如，上下行数据发送完毕后)，再将第一命令发送给该终端设备，并依据该第三消息的具体内容处理该终端设备的上下文信息。第一网络节点能够知晓第一命令的内容的方式可以 为：
(1)第一网络节点能够解读出第一命令的内容，例如具备解码RRC消息的能力；
(2)携带该第一命令的F1接口消息中携带指示，用于表明该第一命令的内容，例如指示终端设备进入inactive mode；
(3)通过携带该第一命令的F1AP消息的类型推断出该第一命令的内容，例如第一命令和第三消息通过同一条F1AP消息中携带，通过第三消息的内容可以推断出该第一命令的内容为指示终端设备进入inactive mode。
可选地，在该第一系统向该终端设备发送第一命令之前，该方法100还包括：
该第一系统根据第一接口信息，确定该第一网络节点与该终端设备之间的数据传输完毕。
例如，通过F1用户面接口的流控信息，第一系统能够得知第一网络节点与该终端设备之间的数据传输已经结束。
可选地，第一网络节点上报其与该终端设备关联的数据缓存状态，当下行数据缓存为0时即表示下行数据发送完毕。
可选地，第一系统配置第一网络节点数据缓存状态为0时，进行数据缓存状态上报。
可选地，第一网络节点周期性的告知第一系统其数据缓存状态。
可选的，该周期性上报由第一网络节点配置。
可选地，该第一系统向该终端设备发送第一命令，该方法100还包括：
该第一系统通过F1消息将第一命令和第三信息发送给第一网络节点，若此时第一网络节点与该终端设备之间有数据/信令传输，则第一网络节点发送表征指示过程失败的F1消息给第一系统，若此时第一网络节点与该终端设备之间数据/信令传输结束，则发送表征指示过程成功的F1消息给第一系统，并将第一命令发送给该终端设备。其中，第一网络节点向第一系统发送表征指示过程成功的F1消息与第一网络节点将第一命令发送给该终端设备的先后顺序不受限定。
S103，该第一系统保存该终端设备的上下文信息。
具体而言，该第一系统为该终端设备保存上下文信息包括以下信息中的一种或多种的组合：RRC配置信息，当前安全上下文，PDCP状态，C-RNTI，全局小区标识ECGI，物理小区标识物理小区标识PCI，resume ID，S1/NG接口连接相关信息(例如，可以为接口控制面UE标识，接口用户面隧道信息TEID，IP地址等)，F1接口连接相关信息(例如，可以为接口控制面UE标识，接口用户面隧道信息TEID，IP地址等)。
S104，该第一网络节点保存该终端设备的上下文信息。
例如，DU为该终端设备保存的上下文信息包括以下信息中的一种或多种的组合：RRC配置信息，DRB参数(例如DRB的标识信息和QoS参数信息)，resume ID(如果CU提供的话，否则，DU可以根据接口终端设备的标识信息对应DU内部终端设备的标识信息)，F1接口连接相关信息(例如，可以为接口控制面UE标识，接口用户面隧道信息TEID，IP地址等)，MAC配置信息(例如逻辑信道标识信息和调度优先级信息(例如优先比特率PBR和令牌桶深度BSD等))。
可选的，DU重置为该终端设备配置的MAC。
进一步可选地，DU重建立为该终端设备挂起的无线承载(Radio Bear，RB)对应的 RLC。
S105，该终端设备根据该第一命令，存储该终端设备的上下文信息。
例如，该终端设备收到上述RRC消息后，存储该终端设备的上下文信息，具体包括以下信息中的一种或多种的组合：RRC配置，当前安全上下文，PDCP状态，C-RNTI，原服务主小区的小区标识和对应的PCI，resume ID。
可选的，该终端设备重置MAC。
进一步可选地，该终端设备挂起除SRB0外的SRB和DRB。或者，该终端设备依据第一命令中的指示，挂起一个或多个SRB/DRB，保持其余RB。相应地，该终端设备重建立挂起的RB的RLC。
应理解，上述步骤S101-S105为该终端设备进入inactive mode时的处理。
S111，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
例如，该终端设备发起RRC连接恢复建立流程，发送RRC连接恢复建立请求消息，用于恢复其RRC连接。该RRC连接恢复建立请求消息中携带该终端设备的resume ID。
应理解，若UE申请resume的这个eNB不是原来的eNB，则目标基站(TeNB)可以根据UE resume消息中包含的小区标识(例如PCI)等找到源基站(SeNB)，然后向SeNB索要C-RNTI/resume ID对应的UE的上下文。
S121，该第一网络节点向该第一系统发送该第一消息。
具体而言，由于第一网络节点不具备部分RRC功能，在该第一网络节点收到该第一消息后，不对该第一消息的内容进行解析或更改，将该第一消息经过第一网络节点上部署的协议层进行相应处理后，将处理后的第一消息通过F1接口发给该第一系统。
例如，DU收到上述RRC连接恢复建立请求消息后，处理后通过F1接口发送给CU。示例性的，该消息通过F1AP消息(例如initial UE message，initial UL RRC message)中的RRC container携带。
S131，该第一系统根据该第一消息，向该第一网络节点发送第二消息，该第二消息用于指示该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，该第二消息包括该终端设备的标识信息。
例如，CU收到上述F1接口消息中携带的第一消息后，解析出消息内容，从而判断出该第一消息为终端设备请求恢复RRC连接的消息，进而为该终端设备恢复建立RRC连接。若能够成功恢复建立该终端设备的RRC连接，则发送F1接口控制面消息给DU，用于指示DU找到和使用DU保存的该终端设备的上下文信息，恢复建立该终端设备的RRC连接。
可选地，该控制面消息中携带以下信息中的一种或组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，UE resume ID，SRB/DRB标识信息和/或对应的配置信息。
S141，该第一网络节点根据该第二消息携带的该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息。
具体而言，该第一网络节点收到该第二消息后，获取该第一网络节点保存的上下文信息，恢复该终端设备相应的配置和传输资源。
例如，DU根据F1接口的终端设备标识信息或者该终端设备的resume ID找到DU保存的该终端设备的上下文信息，恢复该终端设备相应的配置和传输资源。
可选地，若第二消息中携带SRB/DRB标识信息和/或对应的配置信息，该第一网络节点使用该第二消息中携带SRB/DRB标识信息和/或对应的配置信息。
进一步可选地，第一网络节点根据该第二消息生成该终端设备的协议栈配置信息(例如可以为RLC层配置，MAC层配置，PHY层配置)，并将该协议栈配置信息通过F1接口发送给第一系统，用于该第一系统将该协议栈配置信息封装在第一指示信息中发送给终端设备。
S150，该第一系统向该终端设备发送第一指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
例如，该第一指示信息可以为RRC消息，CU发送RRC消息给该终端设备，用于指示该终端设备的RRC连接恢复建立成功或失败，该RRC消息通过F1接口发给DU，由DU处理后转发给该终端设备。
可选地，该第一网络节点无法恢复终端设备的上下文信息，则向该第一系统发送响应消息，用于指示该第一系统该终端设备的上下文关联失败，进一步可选地该第一系统向UE发送第一指示信息，用于指示该终端设备的RRC连接恢复建立成功或者失败。
可选地，该第一指示信息指示该终端设备的RRC连接恢复建立成功时，还包括以下信息中的一种或组合：SRB/DRB标识信息和对应的配置信息，协议栈配置信息。
应理解，S111、S121、S131、S141和S150为该终端设备从inactive mode恢复时的处理。
图8示出了根据本申请实施例的传输方法100的再一示意性流程图，如图8所示，该传输方法100包括：
S161，第二网络节点向第三网络节点发送第一挂起指示信息，该第一挂起指示信息用于指示该终端设备进入非激活态。
可选地，该第二网络节点为上述第一系统的控制面节点，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
可选地，该第二网络节点包括RRC层，以及用于处理RRC消息的PDCP层。第三网络节点包括SDAP层和用于处理用户面数据的PDCP层。
应理解，该第二网络节点和该第三网络节点分别对应于第一系统的控制面节点和用户面节点。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。
具体而言，终端设备接入第一网络节点和第二网络节点管理下的小区，建立RRC连接，第二网络节点决定将该终端设备置为非激活态(inactive mode)，该第二网络节点为该终端设备保存上下文信息，向该第三网络节点发送挂起指示信息，该挂起指示信息用于向该第三网络节点指示该终端设备进入非激活态。
例如，UE接入CU-DU管理下的小区，建立RRC连接。CU决定将UE置为inactive mode。
CU-CP为该UE保存AS上下文，包括以下一种或多种：RRC配置，当前安全上下文，PDCP状态，C-RNTI，服务主小区的小区标识和对应的PCI，resume ID，S1(LTE)/NG(5G 的时候连到核心网叫NG口)接口连接相关信息，F1接口连接相关信息，E1接口相关信息。
CU-CP通过E1接口向CU-UP发送suspend指示，用于表明该UE进行inactive mode。该指示通过E1接口控制面消息发送，消息中包括以下信息中的一种或多种的组合：E1接口的该终端设备的标识信息(E1AP CU侧的终端设备标识信息、E1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，进入inactive mode指示/suspend指示，UE ID(用于关联到该UE在DU处保存的上下文，可以为UE的Context ID，C-RNTI或其他格式的ID，例如F1AP DU侧的终端设备标识信息，F1AP CU侧的终端设备标识信息,或者F1口只有一个接口UEID)(CU-UP应该可以根据E1口UE ID对应到内部UE ID，或者更进一步跟进E1口UEID或内部UE ID找到F1口UE ID)，是否挂起一个或多个SRB/DRB的指示，以及resume ID等。
应理解，该RRC配置可以为RRC Connection Reconfiguration里面的所有内容。
S162，第三网络节点存储该终端设备的上下文信息。
可选地，该第三网络节点为上述第一系统的用户面节点。
可选地，该终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第一接口用于所述第一网络节点和所述第一系统进行数据传输和/或信息交互，所述第二接口用于所述第三网络节点和核心网之间进行数据传输和/或信息交互，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行数据传输和/或信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输和/或信息交互。
可选地，该第三网络节点处保存的该终端设备上下文信息包括第一接口的连接信息、第二接口的连接信息、当前安全上下文信息、分组数据汇聚协议状态和用于识别该终端设备的标识信息。
具体而言，该第三网络节点收到该第二网络节点发送的挂起指示信息后，该第三网络节点为该终端设备存储该终端设备的上下文信息。
例如，CU-UP存储该UE的AS上下文，具体包括RRC配置，当前安全上下文，PDCP状态，DRB参数(例如DRB的标识信息和QoS参数信息，以及DRB和QoS flow的对应关系)，S1/NG连接相关信息(比如核心网侧和CU-UP侧的隧道端点地址，接口UE ID，PDU会话参数等)，F1连接相关信息(比如DU和CU-UP侧的隧道端点地址，接口UE ID，数据流flow参数，DRB参数等)，E1连接相关信息(比如CU-CP和CU-UP侧的隧道端点地址，接口UE ID等)，resume ID(如果CU-CP提供的话，如果CU-CP没有提供resume ID，则可能CU-UP自己进行标识，即根据E1接口UE ID进行对应)等。其中PDU会话参数包含QoS flow参数信息。
应理解，对于CU-UP而言，一种可能的情况是保留和核心网的S1/NG接口连接的相关信息(用户面)，resume ID(或其他内部用于识别该UE的ID)，当前安全上下文，PDCP状态中的一种或多种组合。释放的是第二上下文即为F1接口连接的相关信息(用户面)，例如第四接口的相关信息。本发明不限于其他保留部分，释放部分的情况。
还应理解，对于CU-CP而言，一种可能的情况是保留和核心网的S1/NG接口连接的相关信息(控制面)，RRC配置信息，C-RNTI，全局小区标识ECGI，物理小区标识物理 小区标识PCI，resume ID中的一种或多种组合。
S163，该第二网络节点向该第一网络节点发送第二挂起指示信息，该第二挂起指示信息用于指示该终端设备进入非激活态和/或指示第一网络节点删除该终端设备的上下文。
例如，CU-CP通过F1接口向DU发送suspend指示，用于表明该UE进行inactive mode。该指示通过F1接口控制面消息发送，消息中包括以下信息中的一种或多种的组合：F1AP CU侧UEID，F1AP DU侧UEID(或者F1口只有一个接口UEID)，进入inactive mode指示，UE ID(用于关联到该UE在DU出保存的上下文，可以为UE的Context ID，C-RNTI或其他格式的ID)，是否挂起一个或多个SRB/DRB的指示。可能还包含S165发给UE的RRC connection suspend消息(以RRC container的形式。)
S164，该第一网络节点存储该终端设备的上下文信息。
例如，DU存储该UE的AS上下文，具体包括RRC配置，DRB参数，F1/E1连接相关信息(比如隧道端点地址，接口UE ID，DRB参数等)，resume ID等。DU reset为该UE配置的MAC。
进一步可选地，DU Reestablish UE挂起的RB对应的RLC。
S165，该第二网络节点向该终端设备发送第一命令，该第一命令用于指示该终端设备进入非激活态。
例如，CU-CP通过F1接口发送RRC消息命令UE进入inactive mode(和步骤5可以一起发送)。该RRC消息中携带进入inactive mode指示和UE的resumeID。该RRC消息包含在CU-CP通过F1接口发给DU，DU处理后转发给UE。示例性的，该消息为RRC连接挂起消息(RRC Connection Suspend message)。
进一步可选的，CU通过F1接口发送该RRC消息给DU时，作为RRC container与S163的指示信息携带在同一个F1AP消息中发送。
S166，该终端设备根据该第一命令，存储该终端设备的上下文信息。
可选地，该第二网络节点向该终端设备发送第一命令之前，该方法100包括：
该第二网络节点向该第三网络节点发送非活跃定时器，所述非激活定时器用于所述第三网络节点判断所述终端设备是否为非活跃态；
该非活跃定时器超时时，该第三网络节点确定没有收到该终端设备发送的上行数据，和/或，该第三网络节点确定没有收到核心网发送的下行数据；
该第三网络节点向该第二网络节点发送终端设备非活跃态指示，所述终端设备非活跃态指示用于所述第二网络节点决策是否通知所述终端设备进入非激活态。
例如，CU-CP给CU-UP发送inactive timer T。CU-CP在UE Context Setup request中携带所述UE对应的inactive timer，也可以在Cell setup的时候小区对应的inactive timer，或者在E1setup时携带gNB对应的inactive timer。即所述inactive timer可以是UE粒度的，也可以是小区或gNB粒度的。
当CU-UP发现UE超过T时间没有上行数据，和/或，UE超过T时间没有下行数据，则通知CU-CP timer到时。
例如，CU-UP针对下行数据和上行数据分别启动timer-dl和timer-ul，当核心网没有数据下来时，timer-dl开始倒计时。一旦核心网有数据到来，则timer-dl重置。对于上行也类似，当DU没有数据上来，timer-ul开始倒计时。一旦DU有数据上来，则timer-ul重置。 只有当timer-dl和timer-ul都到时时，CU-UP才会认为所述UE满足inactive条件，并给CU-CP发送指示。
若CU-CP决策让UE进行inactive态，则CU-CP分别通知CU-UP和DU。CU-UP和DU都可以保留或不保留UE context，可以是协议规定，也可以是CU-CP给出保留/不保留UE context的指示。
应理解，CU-CP可能根据CU-UP的timer到时指示，DU发送的无数据指示，综合考虑是否让UE进入inactive态。
应理解，上述S161-S166为该终端设备进入inactive mode时的处理。
还应理解，上述S163和S164顺序可以在S161和S162之前，本申请并不限于此。
S171，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
可选地，该终端设备向该第一网络节点发送第一消息，包括：
该第三网络节点确定接收核心网发送的下行数据；
该第三网络节点向该第二网络节点发送通知消息，该通知消息用于该第二网络节点向该终端设备发送寻呼消息；
该终端设备根据该寻呼消息，向该第一网络节点发送该第一消息。
例如，CU-UP发现核心网有数据来时，CU-UP通知CU-CP，CU-CP在RAN notificatin area内发起RAN paging来通知UE(例如，CU-CP给所有RAN notification area内的gNB发送RAN paging消息)。UE收到RAN paging消息，发起RRC connection resume流程。
S172，该第一网络节点向第二网络节点转发该第一消息。
可选地，该第一网络节点向该第二网络节点转发该第一消息之后，该方法100还包括：
该第二网络节点获取该第二网络节点保存的该终端设备的上下文信息。
例如，CU-CP收到DU转发的RRC connection resume消息后，首先判断自己是否有UE context。如果没有，则基于RRC connection resume消息中提供的源小区ID(可以直接提供，或者隐含在resume ID中)找到对应的源gNB，并向所述源gNB索要UE上下文。如果CU-CP成功获得UE上下文，则分别向CU-UP和DU发送消息。
若UE通过源DU接入，则CU-CP有UE上下文。如果CU-UP和DU保留UE context，则CU-CP在F1/E1口发送的消息可能是UE context resume，包含UE ID/resume ID用于DU和CU-UP找到所述UE context。反之，在F1口发送的消息可能是UE context setup，包含UE context(RRC配置，例如SRB和DRB的协议栈配置)，用于建立F1接口连接的用户面隧道所需的信息(例如CU-CP侧的IP地址和GTP-U隧道端点标识TEID)等。在E1口发送的消息可能是UE context setup，包含UE context(RRC配置，例如DRB的协议栈配置)，以及建立DRB的S1接口连接的用户面的传输通道(例如核心网侧的IP地址和核心网侧PDU session对应的隧道端点标识TEID)和F1接口连接的用户面的传输通道(例如DU侧的IP地址和DU侧DRB对应的隧道端点标识TEID)等。
若UE通过其他DU接入，但CU-CP是相同的。CU-UP可能相同或不同，CU-CP在E1口发送的消息可能是UE context setup/resume取决于CU-UP有没有UE上下文。CU-CP在F1口发送的消息是UE context setup。
若UE在其他CU下的DU接入。CU-CP本来没有UE上下文，但是向源eNB获取 了UE上下文。则对应的CU-UP和DU肯定没有UE上下文。同上所述，CU-CP在F1口发送的消息可能是UE context setup，包含UE context(RRC配置，例如SRB和DRB的协议栈配置)，用于建立F1接口连接的用户面隧道所需的信息(例如CU-CP侧的IP地址和GTP-U隧道端点标识TEID)等。在E1口发送的消息可能是UE context setup，包含UE context(RRC配置，例如DRB的协议栈配置)，以及建立PDU session的S1接口连接的用户面的传输通道(例如核心网侧的IP地址和核心网侧PDU session对应的隧道端点标识TEID)和F1接口连接的用户面的传输通道(例如DU侧的IP地址和DU侧DRB对应的隧道端点标识TEID)等。
S173，该第二网络节点根据该第一消息，向该第三网络节点发送第四消息，该第四消息用于指示该第三网络节点获取该第三网络节点保存的该终端设备的上下文信息，该第四消息包括该终端设备的标识信息。
例如，CU-CP收到上述F1接口消息后，若能够成功resume UE的RRC连接。则通过E1接口控制面消息发送resume指示给CU-UP，用于指示CU-UP resume该UE的RRC连接。该接口消息中携带以下信息中的一种或组合：E1AP CU侧UEID，E1AP DU侧UEID，UE resume ID。
S174，该第三网络节点根据该第四消息携带的该终端设备的标识信息，获取该第三网络节点保存的该终端设备的上下文信息。
例如，CU-UP根据接口UE ID或UE的resume ID找到UE AS上下文，恢复UE配置。
可选地CU-UP回复resume确认消息resume confirm给CU-CP。
S175，该第二网络节点根据该第一消息，向该第一网络节点发送第二消息，该第二消息用于指示该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，该第二消息包括该终端设备的标识信息。
例如，CU-CP收到上述F1接口消息后，若能够成功resume UE的RRC连接。则通过F1接口控制面消息发送resume指示给DU，用于指示DU resume该UE的RRC连接。该接口消息中携带以下信息中的一种或组合：F1AP CU侧UEID，F1AP DU侧UEID，UE resume ID。
S176，该第一网络节点根据该第二消息携带的该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息。
S177，该第二网络节点向该终端设备发送第一指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。应理解，S171-S177为该终端设备从inactive mode恢复时的处理流程。
还应理解，S175和S176可以在S173和S174之前进行，本申请并不限于此。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图9示出了根据本申请实施例的传输方法100的再一示意性流程图，与图7中该终端设备进入inactive mode时的处理不同的是该第一网络节点对该终端设备的上下文信息的处理，该传输方法100包括：
S101，该第一系统向该第一网络节点发送第三消息，该第三消息用于向该第一网络节点指示该终端设备进入非激活态和/或指示第一网络节点删除该终端设备的上下文。
应理解，除了与图7中S102中消息内容可能不同之外，第一网络节点对第一命令和第三消息的处理方式与图7相同，为了简洁，在此不再赘述。
S106，该第一网络节点释放该终端设备的上下文信息。
应理解，除了与图7中S104可能存在不同之外，该终端设备进入inactive mode时的处理的其他步骤均相同，为了简洁，在此不再赘述。
还应理解，与图7中该终端设备从inactive mode恢复时的处理不同的是该第一网络节点对该终端设备的上下文信息的处理，该传输方法100包括：
S132，该第一系统根据该第一消息，向该第一网络节点发送第二消息，该第二消息用于指示该第一网络节点重建该终端设备的上下文信息，该第二消息包括该终端设备的标识信息。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能层中的至少一种。
例如，CU收到上述F1接口消息中携带的第一消息后，解析出消息内容，从而判断出该第一消息为终端设备请求恢复RRC连接的消息，进而为该终端设备恢复建立RRC连接。若能够成功恢复该终端设备的RRC连接，则发送F1接口控制面消息给DU，用于指示DU为该终端设备恢复上下文配置，包括SRB和DRB的协议栈配置，以及建立SRB和DRB的F1接口连接的控制面和用户面的传输通道。
可选地，该接口控制面消息中携带以下信息中的一种或组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，终端设备标识信息(用于关联到该终端设备在DU出保存的上下文信息，可以为该终端设备的Context ID，C-RNTI或其他格式的ID)，该终端设备的信令无线承载列表(SRB list)和/或数据无线承载列表(DRB list)，以及对应的协议栈配置，DRB list对应的F1接口用户面隧道建立信息(例如CU侧的IP地址和GTP-U隧道端点标识TEID)。
S142，该第一网络节点根据该第二消息携带的该终端设备的标识信息，重建该终端设备的上下文信息。
具体而言，该第一网络节点收到该第二消息后，为该终端设备建立上下文信息，进行相应的配置和分配传输资源。
可选地，第一网络节点根据该第二消息生成该终端设备的协议栈配置信息(例如可以为RLC层配置，MAC层配置，PHY层配置)，并将该协议栈配置信息通过F1接口发送给该第一系统，用于该第一系统将该协议栈配置信息封装在第一指示信息中发送给终端设备。
应理解，除了S131、S141与图6所示的该终端设备从inactive mode恢复时的处理不同外，S111、S121和S150均与图6所示步骤相同，为了简洁，在此不再赘述。
图10示出了根据本申请实施例的传输方法100的再一示意性流程图，如图10所示，该传输方法100包括：
S167，该第一网络节点释放该终端设备的上下文信息。
应理解，除S164不同外，该终端设备进入inactive mode时的处理与图8所示的传输方法中该终端设备进入inactive mode时的处理相同，该第三网络节点和该第一网络节点收 到该第二网络节点发送的挂起指示信息后，该第三网络节点保存该终端设备的上下文信息，该第一网络节点释放该终端设备的上下文信息。
与此对应的该终端设备从inactive mode恢复时的处理流程，与图8所示的流程不同的是：
S178，该第二网络节点根据该第一消息，向该第一网络节点发送第二消息，该第二消息用于指示该第一网络节点重建该终端设备的上下文信息，该第二消息包括数据无线承载列表、信令无线承载列表、无线资源控制配置、数据无线承载参数、所述终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种。
S179，该第一网络节点根据数据无线承载列表、信令无线承载列表、无线资源控制配置、数据无线承载参数、所述终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，重建该终端设备的上下文信息。
例如，当CU收到UE的RRC connection resume消息时，向DU发起DRB+SRB连接建立。最后DU转发CU发送的RRC connection resume消息给UE。
应理解，该第二网络节点为该第一系统的控制面节点，该第三网络节点为该第一系统的用户面节点，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。
图11示出了根据本申请实施例的传输方法100的再一示意性流程图，如图11所示，该传输方法100包括：
S168，该第三网络节点释放部分该终端设备的上下文信息。
可选地，该终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第二接口用于所述第三网络节点和核心网之间进行数据传输和/或信息交互，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行数据传输和/或信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输和/或信息交互。
应理解，该第一接口的连接信息包括该第四接口的连接信息。
可选地，该第三网络节点释放的该终端设备的上下文信息包括分组数据汇聚协议状态和该第四接口的连接信息中的至少一种。
应理解，除S162和S164不同外，该终端设备进入inactive mode时的处理与图8所示的传输方法中该终端设备进入inactive mode时的处理相同，该第三网络节点和该第一网络节点收到该第二网络节点发送的挂起指示信息后，该第三网络节点释放部分该终端设备的上下文信息，该第一网络节点释放该终端设备的上下文信息。
与此对应的该终端设备从inactive mode恢复时的处理流程，与图8所示的流程不同的是：
S180，该第二网络节点根据该第二消息，向该第三网络节点发送第四消息，该第四消息用于指示该第三网络节点重建该终端设备的上下文信息，该第四消息包括该终端设备的标识信息，该终端设备的数据无线承载列表，无线资源控制配置，用于建立F1口连接的信息，用于建立E1口连接的信息中的至少一种；S181，该第三网络节点根据该终端设备 的标识信息，该终端设备的数据无线承载列表，无线资源控制配置，用于建立F1口连接的信息，用于建立E1口连接的信息，重建该终端设备的上下文信息。
例如，当CU-CP收到UE的RRC connection resume request消息时，向CU-UP发起针对所述UE的F1接口连接，发起针对所述UE的E1接口连接。其中针对所述UE的F1接口连接的消息包含例如F1接口UE标识，DRB ID，DU侧的IP地址，DU侧DRB对应的隧道端点标识TEID，DRB和QoS flow的对应关系等。其中针对所述UE的E1接口连接包含例如E1接口UE标识,resume ID等。CP-CP向DU发起DRB+SRB连接建立，以及针对所述UE的F1接口连接。
最后DU转发CU发送的RRC connection resume消息给UE。
应理解，S180和S181可以在S178和S179之前，也可以在S178和S179之后，本申请并不限于此。
还应理解，该第二网络节点为该第一系统的控制面节点，该第三网络节点为该第一系统的用户面节点，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。特别地，第二网络节点包括分组数据汇聚协议层和无线资源控制层功能中的至少一种，第三网络节点包括分组数据汇聚协议层、业务数据适配层功能中的至少一种。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。
图12示出了根据本申请实施例的传输方法100的再一示意性流程图，图12所示的传输方法与图7至图11所示的传输方法的主要区别在于：图7至图11中该第一网络节点和该第一系统(或者该第二网络节点)都获知该终端设备进入inactive态，为该终端设备分配了resume ID，并对该终端设备上下文进行了匹配。
图12所示的传输方法中，由于终端设备处发生了HO失败，RLF，底层完整性校验失败、RRC连接重配失败等问题导致了RRC连接重建触发的随机接入和RRC连接建立时，DU并不知道该终端设备已经接入过该小区，会将其视为新的终端设备，而CU会通过RRC连接重建立消息中携带的C-RNTI识别出该终端设备之前已经接入，并且DU处已经保存了该终端设备的上下文信息。
如图12所示，该传输方法100包括：
S107，该终端设备接入该第一网络节点和该第一系统管理下的小区，且获取该终端设备的第一小区无线网络临时标识。
具体而言，该终端设备接入该第一网络节点和该第一系统管理下的小区，该第一网络节点或该第一系统为该终端设备分配的C-RNTI为C-RNTI1，且该第一网络节点和该第一系统为该终端设备储存了该终端设备的上下文信息。
S108，该终端设备向该第一网络节点发送随机接入前导序列，该随机接入前导序列用于该终端设备发起随机接入；
S109，该第一网络节点向该终端设备发送随机接入响应消息，该随机接入响应消息包括该终端设备的第二小区无线网络临时标识；
S112，可选地，该第一网络节点向该第一系统发送第二指示信息，该第二指示信息包括该终端设备的第二小区无线网络临时标识。
可选地，该第二指示信息包括该终端设备接入的小区标识信息，例如PCI或E-UTRAN 小区全局标识符(E-UTRAN Cell Global Identifier)。
可选地，该第二指示信息通过F1控制面消息(如F1AP消息)发送，该F1控制面消息包括以下信息中的至少一种信息：F1接口上该终端设备的标识信息(例如可以为F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)、该第二小区无线网络临时标识(C-RNTI2)、小区标识信息。
S113，该终端设备向该第一网络节点发送第一消息，该第一消息包括该终端设备的标识信息。
可选地，该终端设备的标识信息为第一小区无线网络临时标识信息和对应的物理小区标识信息的至少一种。
例如，该第一消息为RRC连接重建立请求消息，该终端设备发送RRC连接重建立请求消息，在该RRC连接重建立请求消息中携带原基站PCI和原C-RNTI1。DU将上述RRC消息通过F1接口发送给CU。进一步可选的，当DU将该第一消息封装为RRC container，与S112中的第二指示信息放于在同一条F1AP消息中携带。示例性的，该F1AP消息为initial UE message，用于表征新终端设备的接入。
S122，该第一网络节点向该第一系统发送该第一消息。
具体而言，由于第一网络节点不具备部分RRC功能，在该第一网络节点收到该第一消息后不对该第一消息的内容进行解析或更改，将该第一消息经过第一网络节点上部署的协议层进行相应处理后，将处理后的第一消息通过F1接口发给该第一系统。
例如，DU收到上述RRC连接重建立请求消息后，处理后通过F1接口发送给CU。示例性的，该消息通过F1AP的initial UE message中的RRC container携带。
S133，该第一系统根据该第一消息，向该第一网络节点发送第二消息，该第二消息用于指示该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，该第二消息包括该终端设备的标识信息。
例如，若CU可以为该终端设备重建RRC连接，CU通过F1接口向DU发送第二消息，用于指示DU找到DU保存的该终端设备的原上下文信息，并基于该原上下文信息进行增量delta配置，经该delta配置后DU为该终端设备建立了上下文。例如该delta配置包含将原C-RNTI1替换为C-RNTI2，和/或刷新F1AP终端设备的标识信息。
该第二消息包含以下信息中的一种或多种的组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，原C-RNTI1，新C-RNTI2，小区标识，终端设备上下文标识信息(用于关联到该终端设备在DU处保存的上下文，可以为该终端设备的Context ID或其他格式的ID)。
S143，该第一网络节点根据该第二消息携带的该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息。
具体而言，该第一网络节点收到该第二消息后，获取该第一网络节点保存的上下文信息，并基于该原上下文信息进行delta配置，例如该delta配置具体包括将原C-RNTI1替换为C-RNTI2，和/或刷新F1AP终端设备的标识信息。
S151，该第一系统向该终端设备发送第一指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
例如，该第一指示信息可以为RRC消息，该RRC消息用于指示该终端设备RRC重建立成功或者失败，该RRC消息由CU通过F1接口发送给DU，由DU处理后发送给该终端设备。进一步可选的，当CU通过F1接口控制面将该RRC消息发送给DU时，可以与S133中的第二消息携带于同一F1AP消息中发送。
可选地，若RRC重建立成功，该第一指示信息为RRC重建立消息，该F1AP消息为初始上下文建立消息(initial context setup message)，用于指示DU为新接入的UE建立上下文。否则，CU向该终端设备发送RRC重建失败消息。
S160，该终端设备根据该第一指示信息，向该第一系统发送RRC连接重建立完成消息。
具体而言，若该第一指示信息指示RRC连接重建立成功，则该终端设备向该第二网络节点发送RRC连接重建立完成消息，该RRC连接重建立完成消息由该第一网络节点发送给该第一系统。
上文结合图6至图12，详细得描述了根据本申请实施例的传输方法100，该传输方法100中由于该第一网络节点不具备部分RRC功能，该第一网络节点不能对终端设备发送的消息进行解析，只能通过接口将该消息发送给第一系统(或者第二网络节点)进行解析；下文将结合图13至图19，详细描述根据本申请实施例的传输方法200，该传输方法200中该第一网络节点具备部分RRC功能，能够解析和/或回复部分RRC消息，如SRB0。
图13示出了根据本申请实施例的传输方法200的示意性流程图，如图13所示，该传输方法200包括：
S210，第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；
S220，该第一网络节点根据该第一消息，确定该终端设备的标识信息；
S230，该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，
该第一网络节点根据该终端设备的标识信息，接收第一系统发送的第二消息，该第二消息包括该终端设备的上下文信息。可选地，该第一网络节点向终端设备发送响应消息，用于通知终端设备RRC连接建立失败。其中可选的，该响应消息中包含一个原因值，用于表征RRC连接建立失败的原因，例如第一网络节点处上下文获取失败。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种以及至少部分无线资源控制层功能。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
可选地，该第一网络节点根据该终端设备的标识信息，接收第一系统发送的第二消息，包括：
该第一网络节点根据该终端设备的标识信息，接收第二网络节点发送的第二消息，该第二网络节点为该第一系统的控制面节点。
应理解，S230和S240先后顺序并不限定。
具体而言，该第一网络节点接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接，该第一网络节点根据该第一消息，确定该终端设备的标 识信息。
若该第一网络节点存储了该终端设备的上下文信息，则该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，该第一网络节点向该第一系统发送第四消息，该第四消息用于指示该第一系统获取该第二网络节点保存的该终端设备的上下文信息。
若该第一网络节点没有储存该终端设备的上下文信息，该第一网络节点获取该第一系统发送的第五消息，该第五消息包括该终端设备的信令无线承载列表和/或数据无线承载列表，该第一网络节点根据该终端设备的标识信息以及该终端设备的信令无线承载列表和数据无线承载列表中的至少一种，重建该终端设备的上下文信息。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图14示出了根据本申请实施例的传输方法200的另一示意性流程图，如图14所示，该传输方法200包括：
S201，该第一网络节点接收该第一系统发送的第三消息，该第三消息用于向该第一网络节点指示该终端设备进入非激活态。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能层中的至少一种。
S202，该第一系统保存该终端设备的上下文信息；
S203，该第一网络节点保存该终端设备的上下文信息；
S204，该第一系统向该终端设备发送第一命令，该第一命令用于指示该终端设备进入非激活态；
S205，该终端设备根据该第一命令，存储该终端设备的上下文信息。
应理解，若该第一网络节点为DU，如果DU保存了该终端设备的上下文信息，则可以通过UL RRC message transfer消息发送所述RRC connection resume消息。如果未保存，则需要发送Intiail UL RRC message transfer发送所述RRC connection resume消息。
应理解，上述步骤S201-S205与图7中S101-S105步骤相同，均为该终端设备进入inactive mode时的处理，为了简洁，在此不再赘述。
S211，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
例如，该终端设备发起RRC连接恢复建立流程，发送RRC连接恢复建立请求消息，用于恢复其RRC连接。该RRC连接恢复建立请求消息中携带该终端设备的resume ID。
S221，该第一网络节点根据该第一消息，确定该终端设备的标识信息。
具体而言，由于第一网络节点具备部分RRC功能，在该第一网络节点收到该第一消息后，可以对该第一消息进行解析，确定该终端设备的标识信息。
可选地，该标识信息为该终端设备的resume ID。
S231，该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息。
例如，DU确定了RRC连接恢复建立请求消息中携带该终端设备的resume ID后，可以根据该resume ID，找到DU保存的该终端设备的上下文信息，恢复该终端设备相应的 配置和传输资源。
S241，该第一网络节点根据该第一消息，向第一系统发送第五消息，该第五消息用于指示该第一系统获取该第一系统保存的该终端设备的上下文信息。
例如，DU通过F1接口向CU发送第五消息，CU收到上述F1接口的第五消息后，若能够找到CU保存的该终端设备的上下文信息，并且能够基于该上下文信息和第五消息中携带的信息成功恢复建立该终端设备的RRC连接，则恢复该终端设备相应的配置和传输资源。
可选地，第五消息中可以携带指示信息，用于指示第一网络节点没有完全获取该终端设备的上下文。进一步可选地，该第一系统基于该指示信息，在第一指示信息中携带该终端设备的配置信息，用于第一网络节点重建该终端设备的上下文。
S250，该第一系统根据该第五消息，获取该第一系统保存的该终端设备的上下文信息；
S260，该第一系统向第一网络节点发送第一指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
可选地，若成功，则该消息可以进一步携带该终端设备的配置信息(例如包含该终端设备的SRB list和/或DRB list，以及对应的协议栈配置，DRB list对应的F1接口用户面隧道建立信息(例如CU侧的IP地址和GTP-U隧道端点标识TEID))。
可选的，若失败，则该消息指示第一网络节点删除该终端设备上下文，或挂起该终端设备上下文。
S270，第一网络节点发送第二指示信息给终端设备，用于指示该终端设备的RRC连接恢复建立成功或者失败。
或者，该第一系统发送第二指示信息给终端设备，用于指示该终端设备的RRC连接恢复建立成功或者失败。
例如，该第二指示信息可以为RRC消息，CU发送RRC消息给该终端设备，用于指示该终端设备的RRC连接恢复建立成功或失败，该RRC消息通过F1接口发给DU，由DU处理后转发给该终端设备。或者DU基于第一指示消息生成该第二指示消息，发送给终端设备。
图15示出了根据本申请实施例的传输方法200的再一示意性流程图，如图15所示，该传输方法200包括：
S271，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
应理解，图15所示的传输方法中该终端设备进入inactive mode时的处理与图8所示的传输方法中该终端设备进入inactive mode时的处理相同，为了简洁，在此不再赘述。
S272，该第一网络节点根据该第一消息，确定该终端设备的标识信息；
S273，该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息；
S274，该第一网络节点根据该第一消息，向第二网络节点发送第五消息，该第五消息用于指示该第二网络节点获取所述第二网络节点保存的所述终端设备的上下文信息，该第五消息包括该终端设备的上下文信息。
可选地，该第二网络节点为第一系统的控制面节点，该第一系统包括分组数据汇聚协 议层、业务数据适配层和无线资源控制功能层中的至少一种。
S275，该第二网络节点根据该第五消息携带的该终端设备的标识信息，获取该第二网络节点保存的该终端设备的上下文信息；
S276，该第二网络节点向该第三网络节点发送第七消息，该第七消息用于指示该第三网络节点获取该第三网络节点保存的该终端设备的上下文信息，该第七消息包括该终端设备的标识信息。
可选地，该第三网络节点为该第一系统的用户面节点。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。
S277，该第三网络节点根据该第七消息携带的该终端设备的标识信息，获取该第三网络节点保存的该终端设备的上下文信息。
应理解，该第二网络节点向该终端设备发送第二指示信息，该第二指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
图16示出了根据本申请实施例的传输方法200的再一示意性流程图，如图16所示，该传输方法200包括：
S206，该第一网络节点释放该终端设备的上下文信息。
应理解，除了与图14中S203不同之外，该终端设备进入inactive mode时的处理的其他步骤均相同，为了简洁，在此不再赘述。
还应理解，与图14中该终端设备从inactive mode恢复时的处理不同的是该第一网络节点对该终端设备的上下文信息的处理，该传输方法200还包括：
S212，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
例如，该终端设备发起RRC连接恢复建立流程，发送RRC连接恢复建立请求消息，用于恢复其RRC连接。该RRC连接恢复建立请求消息中携带该终端设备的resume ID。
S222，该第一网络节点根据该第一消息，确定该终端设备的标识信息。
具体而言，由于第一网络节点具备部分RRC功能，在该第一网络节点收到该第一消息后，可以对该第一消息进行解析，确定该终端设备的标识信息。
可选地，该标识信息为该终端设备的resume ID。
S242，该第一网络节点向该第一系统发送第四消息，第四消息用于指示该第一系统获取该第二网络节点保存的该终端设备的上下文信息。
可选地，该第四消息包括该终端设备的标识信息。
可选地，该标识信息为该终端设备的resume ID。例如，DU通过F1接口向CU发送第四消息，CU收到上述F1接口的第四消息后，若能够找到CU保存的该终端设备的上下文信息，并且能够基于该上下文信息和第五消息中携带的信息成功恢复建立该终端设备的RRC连接，则恢复该终端设备相应的配置和传输资源。
应理解，由于S206中该第一网络节点释放了该终端设备的上下文信息，所以S222之后，该第一网络节点还不能获取该终端设备的上下文信息。
S251，该第一系统根据该第四消息，获取该第一系统保存的该终端设备的上下文信息；恢复建立该终端设备的RRC连接成功或失败两种情况。
S252，该第一系统向该第一网络节点发送第五消息，该第五消息用于指示第一网络节 点该终端设备的RRC连接恢复建立成功。可选地，该第五消息包括该终端设备的信令无线承载列表和/或数据无线承载列表；
或者该第五消息用于指示第一网络节点该终端设备的RRC连接恢复建立失败。可选地，该第五消息用于指示该第一网络删除或挂起该终端设备的上下文信息。
具体而言，当该第一系统找到该第一系统保存的该终端设备的上下文信息后，会向该第一网络节点发送第五消息，该第五消息用于指示该第一网络节点重建该终端设备的上下文信息，该第五消息中包括了该终端设备的信令无线承载列表和/或数据无线承载列表，当该第一网络节点收到该第五消息后，可以根据该终端设备的标识信息以及该终端设备的信令无线承载列表和数据无线承载列表中的至少一种，重建该终端设备的上下文信息。
例如，CU收到上述F1接口消息后，若能够成功恢复该终端设备的RRC连接，则发送F1接口控制面消息给DU，用于指示DU为该终端设备恢复上下文配置SRB和DRB的协议栈，以及建立F1接口连接的控制面和用户面的传输通道。
可选地，该接口控制面消息中携带以下信息中的一种或组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，C-RNTI，终端设备上下文标识信息(用于关联到该终端设备在DU出保存的上下文信息，可以为该终端设备的Context ID，或其他格式的ID)，该终端设备的信令无线承载列表(SRB list)和/或数据无线承载列表(DRB list)，以及对应的协议栈配置，DRB list对应的F1接口建立信息(例如CU侧的IP地址和GTP-U TEID)。
S261，该第一网络节点根据该终端设备的标识信息以及该终端设备的信令无线承载列表和数据无线承载列表中的至少一种，重建该终端设备的上下文信息；
S270，该第一系统向该终端设备发送第二指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
或者，该第一网络节点向该终端设备发送第二指示信息，该第一指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
图17示出了根据本申请实施例的传输方法200的再一示意性流程图，如图17所示，该方法200包括：
S278，该终端设备向该第一网络节点发送第一消息，该第一消息用于请求恢复该终端设备的无线资源控制连接。
应理解，图17所示的传输方法中该终端设备进入inactive mode时的处理与图10所示的传输方法中该终端设备进入inactive mode时的处理相同，为了简洁，在此不再赘述。
S279，该第一网络节点根据该第一消息，确定该终端设备的标识信息；
S280，该第一网络节点根据该第一消息，向第二网络节点发送第五消息，该第五消息用于指示该第二网络节点获取该第二网络节点保存的所述终端设备的上下文信息，该第五消息包括该终端设备的上下文信息。
可选地，该第二网络节点包括为第一系统的控制面节点，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。S281，该第二网络节点根据该第五消息，获取该第二网络节点保存的所述终端设备的上下文信息。
S282，该第二网络节点向该第三网络节点发送第七消息，该第七消息用于指示该第三 网络节点获取该第三网络节点保存的该终端设备的上下文信息，该第七消息包括该终端设备的标识信息。
可选地，该第三网络节点为第一系统的用户面节点。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。
S283，该第三网络节点根据该第七消息携带的该终端设备的标识信息，获取该第三网络节点保存的该终端设备的上下文信息；
S284，该第二网络节点向该第一网络节点发送第六消息，该第六消息包括该终端设备的信令无线承载列表和数据无线承载列表中的至少一种以及该终端设备的标识信息，该第六消息用于指示该第一网络节点重建该终端设备的上下文信息；
S285，该第一网络节点根据该第六消息携带的该终端设备的信令无线承载列表和数据无线承载列表中的至少一种以及该终端设备的标识信息，重建该终端设备的上下文信息。
应理解，若该第二网络节点可以恢复该终端设备的RRC连接，则该第二网络节点向该终端设备发送第二指示信息，该第二指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
还应理解，S82和S283可以在S284和S85之前，也可以在S284和S85之后，本申请并不限于此。
图18示出了根据本申请实施例的传输方法200的再一示意性流程图，如图18所示，该方法200包括：
S287，该第二网络节点向该第三网络节点发送第七消息，该第七消息用于指示该第三网络节点重建该第三网络节点保存的该终端设备的上下文信息，该第七消息包括该终端设备的数据无线承载列表和该终端设备的标识信息。
可选地，该第二网络节点为第一系统的控制面节点，该第三网络节点为第一系统的用户面节点。
例如，该第一系统为CU，该第二网络节点为CU-CP，该第三网络节点为CU-UP。S288，该第三网络节点根据该第七消息携带的该终端设备的数据无线承载列表和该终端设备的标识信息，重建该终端设备的上下文信息。
应理解，图18所示的传输方法中该终端设备进入inactive mode时的处理与图11所示的传输方法中该终端设备进入inactive mode时的处理相同，为了简洁，在此不再赘述。
还应理解，除了S283和S284外，图18所示的传输方法中该终端设备从inactive mode恢复时的处理流程与图17所示的传输方法中该终端设备从inactive mode恢复时的处理流程相同，为了简洁，在此不再赘述。
还应理解，若该第二网络节点可以恢复该终端设备的RRC连接，则该第二网络节点向该终端设备发送第二指示信息，该第二指示信息用于指示该终端设备的RRC连接恢复建立成功或者失败。
还应理解，S87和S288可以在S284和S85之前，也可以在S284和S85之后，本申请并不限于此。
图19示出了本申请实施例的传输方法200的再一示意性流程图，应理解，图19所示的传输方法与图12所示的传输方法应用场景相同，不同的是图19中该第一网络节点具备部分RRC功能，而图12中该第一网络节点不具备RRC功能。
如图19所示，该传输方法200包括：
S207，该终端设备接入该第一网络节点和该第一系统管理下的小区，且获取该终端设备的第一小区无线网络临时标识。
S208，该终端设备向该第一网络节点发送随机接入前导序列，该随机接入前导序列用于该终端设备发起随机接入；
S209，该第一网络节点向该终端设备发送随机接入响应消息，该随机接入响应消息包括该终端设备的第二小区无线网络临时标识；
S213，该第一网络节点向该第一系统发送第二指示信息，该第二指示信息包括该终端设备的第二小区无线网络临时标识。
应理解，上述步骤与图8中S107、S108、S109和S112相同，为了简洁，在此不再赘述。
S214，该终端设备向该第一网络节点发送第一消息，该第一消息包括该终端设备的标识信息。
可选地，该终端设备的标识信息为第一小区无线网络临时标识信息和物理小区标识信息的至少一种。
例如，该第一消息为RRC连接重建立请求消息，该终端设备发送RRC连接重建立请求消息，在该RRC连接重建立请求消息中携带原基站PCI和原C-RNTI1。DU将上述RRC消息通过F1接口转发给CU。进一步可选的，当DU通过F1接口转发该消息时与S112中的第二指示信息放于在同一条F1AP消息中携带，其中RRC连接重建立请求消息为RRC container。示例性的，该F1AP消息为initial UE message。
S223，该第一网络节点根据该第一消息，确定该终端设备的标识信息。
具体而言，由于第一网络节点具备部分RRC功能，在该第一网络节点收到该第一消息后，可以对该第一消息进行解析，确定该终端设备的标识信息。
可选地，该第一消息为RRC连接重建立请求消息。
可选地，该标识信息为该终端设备的无线网络临时标识信息和物理小区标识信息的至少一种。
S232，该第一网络节点根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息。
例如，DU确定了RRC连接恢复建立请求消息中携带该终端设备的PCI和/或C-RNTI1后，可以根据该终端设备的PCI和/或C-RNTI1，找到DU保存的该终端设备的上下文信息，恢复该终端设备相应的配置和传输资源。
S233，该第一网络节点向该终端设备发送第三指示信息，该第三指示信息用于指示该RRC连接重建立成功或者失败。
例如，DU接收上述RRC消息后，若可以为该终端设备重建RRC连接，DU向该终端设备发送RRC消息，用于指示该终端设备的RRC连接重建立成功。否则，DU向该终端设备发送RRC重建失败消息。
S243，该第一网络节点根据该第一消息，向该第一系统发送第四指示信息，该第四指示信息用于指示该终端设备的小区无线网络临时标识改变。
例如，DU通过F1接口向CU发送配置信息，用于指示该终端设备的C-RNTI改变。 该配置信息包含以下信息中的一种或多种的组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，原C-RNTI1，新C-RNTI2，小区标识，终端设备的上下文标识信息(用于关联到该终端设备在DU处保存的上下文，可以为该终端设备的Context ID或其他格式的ID)。
可选地，第一系统基于第四指示信息为该终端设备生成相应的RRC配置和/或RB配置，发送给第一网络设备，用于第一网络设备生成第三指示信息。此时，S233发生在S243之后。
S253，该终端设备根据该第三指示信息，向该第一系统发送RRC连接重建立完成消息。
具体而言，若该第二指示信息指示RRC连接重建立成功，则该终端设备向该第一系统发送RRC连接重建立完成消息，该RRC连接重建立完成消息由该第一网络节点发送给该第一系统。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
图20示出了根据本申请实施例的传输方法300的示意性流程图，如图20所示，该方法300包括：
S310，第一网络节点确定该第一网络节点与该终端设备之间发生无线链路失败。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种。
例如，DU发现与该终端设备之间的链路发生RLF，其原因可能是物理层原因(如out-of-sync某时间段内次数超过门限)、超过RLC层重传次数等。
S320，该第一网络节点向该第二网络节点发送第八消息，该第八消息用于向该第二网络节点指示该第一网络节点与该终端设备之间发生无线链路失败。
可选地，该第二网络节点包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
可选地，该第八消息包括该终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
例如，DU通过F1接口向CU发送通知消息，用于告知DU该终端设备发生RLF。该消息中包含以下信息中的一种或多种的组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，C-RNTI，终端设备上下文标识信息(用于关联到该终端设备在DU处保存的上下文，可以为该终端设备的Context ID或其他格式的ID)，RLF指示，RLF原因(例如物理层原因，RLC层原因)。
S330，该第二网络节点根据该第八消息，设置定时器；
S340，该定时器超时，该第二网络节点向该第一网络节点发送第九消息，该第九消息用于指示该第一网络节点释放该终端设备的上下文。
例如，若该定时器超时，则CU通过F1接口通知DU，释放该终端设备的上下文信息同时释放F1接口连接。
进一步可选的，CU释放NG接口。
应理解，若该定时器未超时该第二网络节点收到无线资源控制连接消息，则该第二网络节点停止该定时器。
图21示出了根据本申请实施例的传输方法300的另一示意性流程图，如图21所示，该方法300包括：
S311，第一网络节点确定该第一网络节点与该终端设备之间发生无线链路失败。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种。
S321，该第一网络节点向该第二网络节点发送第八消息，该第八消息用于向该第二网络节点指示该第一网络节点与该终端设备之间发生无线链路失败。
可选地，该第二网络节点包括为第一系统的控制面节点，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。可选地，该第八消息包括该终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
例如，DU通过F1接口向CU-CP发送通知消息，用于告知DU该UE发生RLF。该消息中包含以下信息中的一种或多种的组合：F1接口UE ID(F1APDU侧UEID，F1APCU侧UEID或接口UEID)，C-RNTI，UEID(用于关联到该UE在DU处保存的上下文，可以为UE的Context ID或其他格式的ID)，RLF指示，RLF原因(物理层原因，RLC层原因)。
S331，该第二网络节点根据该第八消息，设置定时器；
S341，该定时器超时，该第二网络节点向该第一网络节点发送第九消息，该第九消息用于指示该第一网络节点释放该终端设备的上下文信息；
S342，该定时器超时，该第二网络节点向该第三网络节点发送第十消息，该第十消息用于指示该第一网络节点释放该终端设备的上下文信息。
可选地，该第三网络节点为该第一系统的用户面节点。
例如，若该定时器超时，则CU-CP通过F1接口通知DU，释放UE的context同时释放F1连接。CU-CP通过E1接口通知CU-UP，释放UE的context同时释放Ng-U接口，F1接口以及E1接口连接。
进一步可选的，CU释放NG接口。
应理解，S341和S342并没有先后顺序。
还应理解，若该定时器未超时该第二网络节点收到无线资源控制连接消息，则该第二网络节点停止该定时器。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图22示出了根据本申请实施例的传输方法400的示意性流程图，如图22所示，该传输方法400包括：
S410，终端设备接入第一网络节点和第一系统管理下的小区，建立RRC连接。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种。
可选地，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
应理解，该第一网络节点和第一系统为网络设备部分功能分离时的不同网络节点，该网络设备包括该第一网络节点和该第一系统。
还应理解，该第一网络节点可以为源DU，该第一系统可以为源CU，图14所述传输方法是为了解决将终端设备从源CU下的源DU切换至目标CU下的目标DU。
例如，终端设备接入CU-DU管理下的小区，建立RRC连接。该终端设备的C-RNTI为C-RNTI1。CU和DU处存储了该终端设备的上下文信息。
S420，该第一系统确定将该终端设备切换至第五网络节点，向所述第五网络节点发送切换请求消息。
例如，源CU决定将该终端设备切换至目标CU，并通过基站间接口或者基站与核心网实体RAN-CN之间的接口将切换请求消息发送给目标CU。
S430，该第五网络节点向第四网络节点发送切换准备消息，该切换准备消息用于请求该第四网络节点为该终端设备进行配置。
应理解，该第四网络节点可以为目标DU，该第五网络节点可以为目标CU。
可选地，该第四网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种。
可选地，该第五网络节点包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
例如，目标CU进行准入控制后，若允许接入该终端设备，则发送切换准备消息给目标DU，用于请求目标DU为该终端设备进行配置。该消息中包含以下信息中的一种或几种的组合：F1接口的该终端设备的标识信息(F1AP CU侧的终端设备标识信息、F1AP DU侧的终端设备标识信息或一个单独的接口的终端设备标识信息)，终端设备的上下文标识信息(用于关联到该终端设备在DU处保存的上下文信息，可以为该终端设备的Context ID或其他格式的ID)，该终端设备的SRB list和/或DRB list，DRB对应的F1接口建立信息(如CU侧隧道地址和GTP-U TEID)，cellID(如PCI或ECGI)。
S440，该第四网络节点根据该切换准备消息，向该第五网络节点发送小区无线网络临时标识和/或专用随机接入资源。
例如，DU收到上述消息后，为终端设备分配C-RNTI 2和/或专用RACH资源，并通过F1接口消息中发给CU。示例性的，具体的RACH资源相关信息包含：波束标识信息beam ID，物理资源指示。
S450，该第五网络节点向该第一系统发送切换命令，该切换命令包括该小区无线网络临时标识和/或专用随机接入资源。
例如，目标CU通过基站间接口或RAN-CN接口转发将切换命令发送给源CU。该切换命令携带目标CU为该终端设备进行的配置，包含C-RNTI2和专用RACH资源。
S460，该第一系统向该终端设备发送配置信息，该配置信息包括该小区无线网络临时标识和/或专用随机接入资源；
S470，该终端设备使用该小区无线网络临时标识和/或专用随机接入资源接入该第五网络节点。
本申请实施例的传输方法，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
上文结合图6至图22，详细得描述了根据本申请实施例的传输方法，下文结合图23至36，详细描述根据本申请实施例的网络设备。
图23示出了根据本申请实施例的网络设备500的示意性框图，如图23所示，该网络设备500包括：
收发模块510，用于接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；
处理模块520，用于控制该收发模块向第一系统发送该第一消息；该收发模块还用于接收该第一系统根据该第一消息发送的第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该收发模块510还用于接收该第一系统发送的第三消息；该第一网络节点根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
可选地，该第收发模块510还用于接收该第一系统发送的指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
可选地，该收发模块510具体用于向第二网络节点发送该第一消息；接收该第二网络节点根据该第一消息发送的该第二消息；其中，该第二网络节点为该第一系统的控制面节点。
可选地，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
可选地，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数、该终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图24示出了根据本申请实施例的网络设备600的示意性流程图，如图24所示，该网络设备600包括：
收发模块610，用于接收来自于终端设备的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；
处理模块620，用于根据该第一消息，向第一网络节点发送第二消息，该第二消息包括该终端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该收发模块610为第二网络节点的收发模块，该处理模块620为该第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
可选地，该收发模块610还用于向第三网络节点发送第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于该第三网络节点获取该第三网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
可选地，该收发模块610还用于向该第一网络节点发送指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；该第一网络节点向该终端设备发送该指示消息。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图25示出了根据本申请实施例的网络设备700的示意性流程图，如图25所示，该网络设备700包括：
收发模块710，用于接收第二网络节点发送的第四消息，该第四消息包括该终端设备的标识信息，该终端设备的标识信息用于第三网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第四消息包括该终端设备的上下文信息；
处理模块720，用于根据该第四消息，建立该终端设备的上下文信息；其中，该第二网络节点为第一系统的控制面节点，该第三网络节点为该第一系统的用户面节点。
可选地，该收发模块710还用于接收该第二网络节点发送的第五消息；该处理模块还用于根据该第五消息，存储该终端设备的上下文信息，或者，释放部分该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第二接口用于所述第三网络节点和核心网之间进行数据传输和/或信息交互，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行数据传输和/或信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输和/或信息交互。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图26示出了根据本申请实施例的网络设备800的示意性流程图，如图26所示，该网络设备800包括：
收发模块810，用于接收终端设备发送的第一消息，该第一消息用于请求建立该终端设备的无线资源控制连接；
处理模块820，用于根据该第一消息，确定该终端设备的标识信息；
该处理模块820还用于根据该终端设备的标识信息，获取该第一网络节点保存的该终端设备的上下文信息，或者，
该处理模块820还用于根据该终端设备的标识信息，接收第一系统发送的第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该收发模块810还用于接收该第一系统发送的第三消息；该处理模块还用于根据该第三消息，存储该终端设备的上下文信息，或者，释放该终端设备的上下文信息。
可选地，该收发模块810还用与接收该第一系统发送的指示消息，该指示消息用于向该第一网络节点指示该终端设备进入非激活态；向该终端设备发送该指示消息。
可选地，该收发模块810为第二网络节点的收发模块，该处理模块820为该第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
可选地，该终端设备的标识信息为该终端设备的恢复识别信息、第一接口的该终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
可选地，该终端设备的上下文信息包括无线资源控制配置、数据无线承载参数和第一接口的连接信息中的至少一种，该第一接口用于该第一网络节点和该第一系统之间进行数据传输和信息交互。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制功能层中的至少一种；和/或
该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图27示出了根据本申请实施例的网络设备900的示意性流程图，如图27所示，该网络设备900包括：
收发模块910，用于接收第一网络节点发送的第六消息，该第六消息包括该终端设备的标识信息，该第六消息用于第一系统获取该第一系统保存的该终端设备的上下文信息；
处理模块920，用于根据该第六消息，向该第一网络节点发送第二消息，该第二消息包括该终端设备的上下文信息，该终端设备的上下文信息为接入层的上下文信息。
可选地，该收发模块910为第二网络节点的收发模块，该处理模块920为该第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
可选地，该收发模块910还用于向第三网络节点发送第七消息，该第二消息包括该终 端设备的标识信息，该终端设备的标识信息用于该第一网络节点获取该第一网络节点保存的该终端设备的上下文信息，或者，该第二消息包括该终端设备的上下文信息；其中，该第三网络节点为该第一系统的用户面节点。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种；和/或
该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制功能层中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图28示出了根据本申请实施例的网络设备1000的示意性流程图，如图28所示，该网络设备1000包括：
处理模块1010，用于确定该第一网络节点与该终端设备之间发生无线链路失败，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；
收发模块1020，用于向该第一系统发送第六消息，该第六消息用于向该第二网络节点指示该第一网络节点与该终端设备之间发生无线链路失败，该第二网络节点包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
可选地，该收发模块1020还用于接收该第一系统发送的第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文。
可选地，该收发模块1020为第二网络节点的收发模块，该处理模块为第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
可选地，所述第六消息包括所述终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图29示出了根据本申请实施例的网络设备1100的示意性流程图，如图29所示，该网络设备1100包括：
收发模块1110，用于接收第一网络节点发送的第六消息，该第六消息用于向该第一系统指示该第一网络节点与终端设备之间发生无线链路失败；
处理模块1120，用于根据该第六消息，设置定时器；
若该定时器超时，该第一系统向该第一网络节点发送第七消息，该第七消息用于指示该第一网络节点释放该终端设备的上下文；若该定时器未超时该第一系统收到无线资源控制连接消息，该第一系统停止该定时器。
可选地，该第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种，该第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种；
可选地，该收发模块1110为第二网络节点的收发模块，该处理模块1120为第二网络节点的处理模块，该第二网络节点为该第一系统的控制面节点。
可选地，该收发模块1110还用于：该定时器超时，向第三网络节点发送第八消息，所述第八消息用于指示该第三网络节点释放该终端设备的上下文信息，其中，该第三网络 节点为该第一系统的用户面节点。
可选地，该第六消息包括该终端设备的标识信息、无线链路失败指示信息和小区无线网络临时标识中的至少一种。
本申请实施例的网络设备，可以实现在网络设备部分功能分离为不同网络节点时，有效地对该终端设备的上下文进行管理。
图30是根据本申请实施例的网络设备1200的结构示意图。如图30所示，该网络设备1200包括处理器1201、存储器1202、接收器1203和发送器1204。这些部件之间通信连接。该存储器1202用于存储指令，该处理器1201用于执行该存储器1202存储的指令，并控制该接收器1203接收信息以及控制该发送器1204发送信息。
其中，该处理器1201用于执行该存储器1202存储的指令，该处理器1201可以用于执行网络设备500中处理模块520相应的操作和/或功能，该接收器1203和发送器1204可以用于执行网络设备500中收发模块510相应的操作和/或功能，为了简洁，此处不再赘述。
图31是根据本申请实施例的网络设备1300的结构示意图。如图31所示，该网络设备1300包括处理器1301、存储器1302、接收器1303和发送器1304。这些部件之间通信连接。该存储器1302用于存储指令，该处理器1301用于执行该存储器1302存储的指令，并控制该接收器1303接收信息以及控制该发送器1304发送信息。
其中，该处理器1301用于执行该存储器1302存储的指令，该处理器1301可以用于执行网络设备600中处理模块620相应的操作和/或功能，该接收器1303和发送器1304可以用于执行网络设备600中收发模块610相应的操作和/或功能，为了简洁，此处不再赘述。
图32是根据本申请实施例的网络设备1400的结构示意图。如图32所示，该网络设备1400包括处理器1401、存储器1402、接收器1403和发送器1404。这些部件之间通信连接。该存储器1402用于存储指令，该处理器1401用于执行该存储器1402存储的指令，并控制该接收器1403接收信息以及控制该发送器1404发送信息。
其中，该处理器1401用于执行该存储器1402存储的指令，该处理器1401可以用于执行网络设备700中处理模块720相应的操作和/或功能，该接收器1403和发送器1404可以用于执行网络设备700中收发模块710相应的操作和/或功能，为了简洁，此处不再赘述。
图33是根据本申请实施例的网络设备1500的结构示意图。如图33所示，该网络设备1500包括处理器1501、存储器1502、接收器1503和发送器1504。这些部件之间通信连接。该存储器1502用于存储指令，该处理器1501用于执行该存储器1502存储的指令，并控制该接收器1503接收信息以及控制该发送器1504发送信息。
其中，该处理器1501用于执行该存储器1502存储的指令，该处理器1501可以用于执行网络设备800中处理模块820相应的操作和/或功能，该接收器1503和发送器1504可以用于执行网络设备800中收发模块810相应的操作和/或功能，为了简洁，此处不再赘述。
图34是根据本申请实施例的网络设备1600的结构示意图。如图34所示，该网络设备1600包括处理器1601、存储器1602、接收器1603和发送器1604。这些部件之间通信 连接。该存储器1602用于存储指令，该处理器1601用于执行该存储器1602存储的指令，并控制该接收器1603接收信息以及控制该发送器1604发送信息。
其中，该处理器1601用于执行该存储器1602存储的指令，该处理器1601可以用于执行网络设备900中处理模块920相应的操作和/或功能，该接收器1603和发送器1604可以用于执行网络设备900中收发模块910相应的操作和/或功能，为了简洁，此处不再赘述。
图35是根据本申请实施例的网络设备1700的结构示意图。如图35所示，该网络设备1700包括处理器1701、存储器1702、接收器1703和发送器1704。这些部件之间通信连接。该存储器1702用于存储指令，该处理器1701用于执行该存储器1702存储的指令，并控制该接收器1703接收信息以及控制该发送器1704发送信息。
其中，该处理器1701用于执行该存储器1702存储的指令，该处理器1701可以用于执行网络设备1000中处理模块1010相应的操作和/或功能，该接收器1703和发送器1704可以用于执行网络设备1000中收发模块1020相应的操作和/或功能，为了简洁，此处不再赘述。
图36是根据本申请实施例的网络设备1800的结构示意图。如图36所示，该网络设备1800包括处理器1801、存储器1802、接收器1803和发送器1804。这些部件之间通信连接。该存储器1802用于存储指令，该处理器1801用于执行该存储器1802存储的指令，并控制该接收器1803接收信息以及控制该发送器1804发送信息。
其中，该处理器1801用于执行该存储器1802存储的指令，该处理器1801可以用于执行网络设备1100中处理模块1120相应的操作和/或功能，该接收器1803和发送器1804可以用于执行网络设备1100中收发模块1110相应的操作和/或功能，为了简洁，此处不再赘述。
本申请实施例还提供了一种芯片系统，应用于网络设备中，该芯片系统包括：至少一个处理器、至少一个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述至少一个存储器、所述接口电路和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有指令；所述指令被所述至少一个处理器执行，以进行上述各个方面的所述的方法中所述网络设备的操作。
本申请实施例还提供了一种通信系统，包括：网络设备，和/或，终端设备；其中，所述网络设备为上述各个方面所述的网络设备。
本申请实施例还提供了一种计算机程序产品，应用于网络设备中，所述计算机程序产品包括一系列指令，当所述指令被运行时，以进行上述各个方面的所述的方法中所述网络设备的操作。
在本申请实施例中，应注意，本申请实施例上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通 用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用 介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (29)

  1. 一种传输方法，其特征在于，包括：
    第一网络节点接收终端设备发送的第一消息，所述第一消息用于请求建立所述终端设备的无线资源控制连接；
    所述第一网络节点向第一系统发送所述第一消息；
    所述第一网络节点接收所述第一系统根据所述第一消息发送的第二消息，所述第二消息包括所述终端设备的标识信息，所述终端设备的标识信息用于所述第一网络节点获取所述第一网络节点保存的所述终端设备的上下文信息，或者，所述第二消息包括所述终端设备的上下文信息，所述终端设备的上下文信息为接入层的上下文信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络节点接收终端设备发送的第一消息之前，所述方法还包括：
    所述第一网络节点接收所述第一系统发送的第三消息；
    所述第一网络节点根据所述第三消息，存储所述终端设备的上下文信息，或者，释放所述终端设备的上下文信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一网络节点向第一系统发送所述第一消息，包括：
    所述第一网络节点向第二网络节点发送所述第一消息，所述第二网络节点为所述第一系统的控制面节点；
    其中，所述第一网络节点接收所述第一系统根据所述第一消息发送的第二消息，包括：
    所述第一网络节点接收所述第二网络节点根据所述第一消息发送的所述第二消息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述终端设备的标识信息为所述终端设备的恢复识别信息、第一接口的所述终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，所述第一接口用于所述第一网络节点和所述第一系统之间进行数据传输和信息交互。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述终端设备的上下文信息包括无线资源控制配置、数据无线承载参数、所述终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，所述第一接口用于所述第一网络节点和所述第一系统之间进行数据传输和信息交互。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
    所述第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
  7. 一种传输方法，其特征在于，包括：
    第一系统接收来自于终端设备的第一消息，所述第一消息用于请求建立所述终端设备的无线资源控制连接；
    所述第一系统根据所述第一消息，向第一网络节点发送第二消息，所述第二消息包括所述终端设备的标识信息，所述终端设备的标识信息用于所述第一网络节点获取所述第一 网络节点保存的所述终端设备的上下文信息，或者，所述第二消息包括所述终端设备的上下文信息，所述终端设备的上下文信息为接入层的上下文信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第一系统接收来自于终端设备的第一消息，包括：
    第二网络节点接收来自于所述终端设备的第一消息，所述第二网络节点为所述第一系统的控制面节点；
    其中，所述第一系统根据所述第一消息，向第一网络节点发送第二消息，包括：
    所述第二网络节点根据所述第一消息，向所述第一网络节点发送所述第二消息。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第二网络节点向第三网络节点发送第四消息，所述第四消息包括所述终端设备的标识信息，所述终端设备的标识信息用于所述第三网络节点获取所述第三网络节点保存的所述终端设备的上下文信息，或者，所述第二消息包括所述终端设备的上下文信息；
    其中，所述第三网络节点为所述第一系统的用户面节点。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
    所述第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
  11. 一种传输方法，其特征在于，包括：
    第三网络节点接收第二网络节点发送的第四消息，所述第四消息包括所述终端设备的标识信息，所述终端设备的标识信息用于所述第三网络节点获取所述第一网络节点保存的所述终端设备的上下文信息，或者，所述第四消息包括所述终端设备的上下文信息，所述终端设备的上下文信息为接入层的上下文信息；
    所述第三网络节点根据所述第四消息，建立所述终端设备的上下文信息；
    其中，所述第二网络节点为第一系统的控制面节点，所述第三网络节点为所述第一系统的用户面节点。
  12. 根据权利要求11所述的方法，其特征在于，所述第三网络节点接收第二网络节点发送的第四消息之前，所述方法还包括：
    所述第三网络节点接收所述第二网络节点发送的第五消息；
    所述第三网络节点根据所述第五消息，存储所述终端设备的上下文信息，或者，释放部分所述终端设备的上下文信息。
  13. 根据权利要求12所述的方法，其特征在于，所述终端设备的上下文信息包括第二接口的连接信息、第三接口的连接信息、第四接口的连接信息、无线资源控制配置、数据无线承载参数、当前安全上下文信息、分组数据汇聚协议状态、小区标识信息和用于识别所述终端设备的标识信息中的至少一种，所述第二接口用于所述第三网络节点和核心网之间进行数据传输，所述第三接口用于所述第三网络节点和所述第二网络节点之间进行信息交互，所述第四接口用于所述第三网络节点和第一网络节点之间进行数据传输。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，所述第一网络节点包括无线链路层控制协议层、媒体介入控制层和物理层功能中的至少一种；和/或
    所述第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的 至少一种。
  15. 一种传输方法，其特征在于，包括：
    第一网络节点接收终端设备发送的第一消息，所述第一消息用于请求建立所述终端设备的无线资源控制连接；
    所述第一网络节点根据所述第一消息，确定所述终端设备的标识信息；
    所述第一网络节点根据所述终端设备的标识信息，获取所述第一网络节点保存的所述终端设备的上下文信息，或者，
    所述第一网络节点根据所述终端设备的标识信息，接收第一系统发送的第二消息，所述第二消息包括所述终端设备的上下文信息，所述终端设备的上下文信息为接入层的上下文信息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一网络节点接收终端设备发送的第一消息之前，所述方法还包括：
    所述第一网络节点接收所述第一系统发送的第三消息；
    所述第一网络节点根据所述第三消息，存储所述终端设备的上下文信息，或者，释放所述终端设备的上下文信息。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第一网络节点根据所述终端设备的标识信息，接收第一系统发送的第二消息，包括：
    所述第一网络节点根据所述终端设备的标识信息，接收第二网络节点发送的第二消息，所述第二网络节点为所述第一系统的控制面节点。
  18. 根据权利要求15至17中任一项所述的方法，其特征在于，所述终端设备的标识信息为所述终端设备的恢复识别信息、第一接口的所述终端设备的标识信息、小区无线网络临时标识信息和物理小区标识信息中的至少一种，所述第一接口用于所述第一网络节点和所述第一系统之间进行数据传输和信息交互。
  19. 根据权利要求15至18中任一项所述的方法，其特征在于，所述终端设备的上下文信息包括无线资源控制配置、数据无线承载参数、所述终端设备的标识信息、小区标识信息和第一接口的连接信息中的至少一种，所述第一接口用于所述第一网络节点和所述第一系统之间进行数据传输和信息交互。
  20. 根据权利要求15至19中任一项所述的方法，其特征在于，所述第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种；和/或
    所述第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
  21. 一种传输方法，其特征在于，包括：
    第一系统接收第一网络节点发送的第六消息，所述第六消息包括所述终端设备的标识信息，所述第六消息用于所述第一系统获取所述第一系统保存的所述终端设备的上下文信息；
    所述第一系统根据所述第六消息，向所述第一网络节点发送第二消息，所述第二消息包括所述终端设备的上下文信息，所述终端设备的上下文信息为接入层的上下文信息。
  22. 根据权利要求21所述的方法，其特征在于，所述第一系统接收第一网络节点发 送的第六消息，包括：
    第二网络节点接收所述第一网络节点发送的第六消息，所述第二网络节点为所述第一系统的控制面节点；
    其中，所述第一系统根据所述第六消息，向所述第一网络节点发送第二消息，包括：
    所述第二网络节点根据所述第六消息，向所述第一网络节点发送所述第二消息。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    所述第二网络节点向第三网络节点发送第七消息，所述第七消息包括所述终端设备的标识信息，所述终端设备的标识信息用于所述第一网络节点获取所述第一网络节点保存的所述终端设备的上下文信息，或者，所述第七消息包括所述终端设备的上下文信息；
    其中，所述第三网络节点为所述第一系统的用户面节点。
  24. 根据权利要求21至23中任一项所述的方法，其特征在于，所述第一网络节点包括无线链路层控制协议层、媒体介入控制层、物理层功能和无线资源控制层功能中的至少一种；和/或
    所述第一系统包括分组数据汇聚协议层、业务数据适配层和无线资源控制层功能中的至少一种。
  25. 一种网络设备，其特征在于，包括：存储器、收发器和至少一个处理器，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述收发器用于执行权利要求1-24中任一所述的方法中，在所述网络设备进行的消息收发的操作；
    所述至少一个处理器调用所述存储器中存储的所述指令，执行权利要求1-24中任一所述的方法中在所述网络设备进行的处理操作。
  26. 一种芯片系统，应用于网络设备中，其特征在于，包括：至少一个处理器、至少一个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述至少一个存储器、所述接口电路和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有指令；所述指令被所述至少一个处理器执行，以进行如权利要求1-24中任一所述的方法中所述网络设备的操作。
  27. 一种计算机可读存储介质，应用于网络设备中，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在计算设备上运行时，以进行如权利要求1-24中任一所述的方法中所述网络设备的操作。
  28. 一种通信系统，其特征在于，包括：网络设备，和/或，终端设备；
    其中，所述网络设备为权利要求25所述的网络设备。
  29. 一种计算机程序产品，应用于网络设备中，其特征在于，所述计算机程序产品包括一系列指令，当所述指令被运行时，以进行如权利要求1-24中任一所述的方法中所述网络设备的操作。
PCT/CN2018/099819 2017-08-11 2018-08-10 一种传输方法和网络设备 WO2019029661A1 (zh)

Priority Applications (13)

Application Number Priority Date Filing Date Title
KR1020227015572A KR102585617B1 (ko) 2017-08-11 2018-08-10 전송 방법 및 네트워크 디바이스
ES18844764T ES2901695T3 (es) 2017-08-11 2018-08-10 Método de transmisión y dispositivo de red
EP21202599.3A EP3998796A1 (en) 2017-08-11 2018-08-10 Transmission method and network device
JP2020508042A JP7139412B2 (ja) 2017-08-11 2018-08-10 伝送方法およびネットワークデバイス
CA3072715A CA3072715C (en) 2017-08-11 2018-08-10 Transmission method and network device
BR112020002752-9A BR112020002752A2 (pt) 2017-08-11 2018-08-10 método de transmissão, dispositivo de rede, sistema de chip, mídia de armazenamento legível por computador, produto de programa de computador, sistema de rede e sistema de comunicações
RU2020109982A RU2780471C2 (ru) 2017-08-11 2018-08-10 Способ передачи и сетевое устройство
EP18844764.3A EP3570584B1 (en) 2017-08-11 2018-08-10 Transmission method and network device
CN201880013339.1A CN110326321B (zh) 2017-08-11 2018-08-10 一种传输方法和网络设备
KR1020207007175A KR102397469B1 (ko) 2017-08-11 2018-08-10 전송 방법 및 네트워크 디바이스
US16/449,709 US11178538B2 (en) 2017-08-11 2019-06-24 Transmission method and network device
US17/222,745 US20210227378A1 (en) 2017-08-11 2021-04-05 Transmission method and network device
JP2022142248A JP7394940B2 (ja) 2017-08-11 2022-09-07 伝送方法およびネットワークデバイス

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710685352.9 2017-08-11
CN201710685352.9A CN109391963B (zh) 2017-08-11 2017-08-11 一种传输方法和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/449,709 Continuation US11178538B2 (en) 2017-08-11 2019-06-24 Transmission method and network device

Publications (1)

Publication Number Publication Date
WO2019029661A1 true WO2019029661A1 (zh) 2019-02-14

Family

ID=65270943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099819 WO2019029661A1 (zh) 2017-08-11 2018-08-10 一种传输方法和网络设备

Country Status (9)

Country Link
US (2) US11178538B2 (zh)
EP (2) EP3570584B1 (zh)
JP (2) JP7139412B2 (zh)
KR (2) KR102585617B1 (zh)
CN (4) CN110662267B (zh)
BR (1) BR112020002752A2 (zh)
CA (2) CA3225953A1 (zh)
ES (1) ES2901695T3 (zh)
WO (1) WO2019029661A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2017438131B2 (en) * 2017-10-31 2021-05-20 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Indication method for context identification, acquisition method, user equipment and base station
CN113473513A (zh) * 2021-09-02 2021-10-01 成都爱瑞无线科技有限公司 链路故障检测及处理方法、装置、系统及存储介质
CN114073031A (zh) * 2019-08-14 2022-02-18 华为技术有限公司 一种通信方法及相关设备

Families Citing this family (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018170377A1 (en) * 2017-03-17 2018-09-20 Intel Corporation Re-transmission of pdcp pdus by centralized nodes of a ran architecture
US20210014818A9 (en) 2017-08-10 2021-01-14 Kyungmin Park Time Alignment Timer Information
CN110583094A (zh) * 2017-09-05 2019-12-17 Oppo广东移动通信有限公司 传输数据的方法和网络设备
US10873916B2 (en) 2017-12-29 2020-12-22 Ofinno, Llc Base station power control
US10772008B2 (en) * 2018-01-11 2020-09-08 Comcast Cable Communications, Llc Cell configuration for packet duplication
CN110035498B (zh) 2018-01-12 2022-08-26 华为技术有限公司 一种通信方法，设备及其系统
US11924670B2 (en) * 2018-04-06 2024-03-05 Telefonaktiebolaget Lm Ericsson (Publ) QoS flow management over E1
US11178719B2 (en) * 2018-05-07 2021-11-16 Htc Corporation Device and method of handling an radio resource control resume procedure
US11412554B2 (en) * 2018-05-10 2022-08-09 Apple Inc. E1 interface setup in NG-RAN
KR102630472B1 (ko) * 2018-08-09 2024-01-29 지티이 코포레이션 통합된 액세스 및 백홀 베어러 관리를 위한 방법, 장치 및 시스템
CN110876209B (zh) * 2018-08-31 2022-11-18 财团法人工业技术研究院 连接重定向方法以及用户设备
CN111526544A (zh) * 2019-02-01 2020-08-11 北京三星通信技术研究有限公司 连接重建方法、上下文获取方法、上下文管理方法、连接重建方法、节点和介质
US20220132600A1 (en) * 2019-02-12 2022-04-28 Lg Electronics Inc. Early data transmission in cu-du split
EP3925409A4 (en) * 2019-02-12 2022-11-02 Nokia Technologies Oy PROCEDURE FOR CHANGING THE CENTRALIZED NETWORK DEVICE
CN111698111B (zh) * 2019-03-14 2022-12-16 中国移动通信有限公司研究院 一种网络单元的管理方法及装置、系统、存储介质
CN111698731B (zh) * 2019-03-14 2023-01-10 中国移动通信有限公司研究院 协议实体建立、数据缓存方法及其装置、设备、存储介质
CN113853831A (zh) * 2019-03-28 2021-12-28 瑞典爱立信有限公司 Iab节点释放过程
CN111757548B (zh) * 2019-03-29 2022-05-24 华为技术有限公司 通信方法和通信装置
CN111757424B (zh) * 2019-03-29 2022-03-22 大唐移动通信设备有限公司 一种无线接入网的共享方法及装置
CN113455097A (zh) * 2019-03-29 2021-09-28 华为技术有限公司 链路失败的恢复方法和设备
CN112423272A (zh) * 2019-08-05 2021-02-26 华为技术有限公司 数据传输的方法和装置
CN114223253A (zh) * 2019-08-14 2022-03-22 中兴通讯股份有限公司 用于网络共享分体架构的网络重新选择
EP4016948A4 (en) 2019-08-15 2022-07-20 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR COMPRESSING AN ETHERNET HEADER, AND METHOD AND APPARATUS FOR DECOMPRESSING AN ETHERNET HEADER
EP3982689B1 (en) * 2019-08-16 2023-10-25 LG Electronics Inc. Method by which terminal transmits/receives signal for performing random access channel procedure in wireless communication system, and device therefor
WO2021062797A1 (zh) * 2019-09-30 2021-04-08 华为技术有限公司 配置方法和装置
CN112702711B (zh) * 2019-10-23 2022-08-09 普天信息技术有限公司 车联网终端无线连接方法和装置
CN110944365B (zh) * 2019-11-28 2021-10-22 武汉虹旭信息技术有限责任公司 一种基于5g核心网的多参考点关联方法及系统
WO2021134597A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 一种测量信息的上报、收集方法及装置
WO2021134728A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 一种上下文管理方法及装置
CN113556703A (zh) * 2020-04-03 2021-10-26 华为技术有限公司 无线通信方法和通信装置
CN111556506B (zh) * 2020-04-28 2023-09-22 锐迪科微电子科技（上海）有限公司 异常链路的处理方法及设备
CN113747521B (zh) * 2020-05-29 2023-02-17 维沃移动通信有限公司 网络切换方法、装置、通信设备及系统
CN113939044A (zh) * 2020-06-29 2022-01-14 华为技术有限公司 一种通信方法和装置
CN113873587B (zh) * 2020-06-30 2023-09-22 华为技术有限公司 一种用于iab网络通信的方法及相关设备
US20230189380A1 (en) * 2020-07-29 2023-06-15 Intel Corporation Small data exchange handling by a user equipment in inactive state
KR102606029B1 (ko) * 2020-08-06 2023-11-23 오피노 엘엘씨 업링크 리소스 릴리스
GB2597793A (en) * 2020-08-06 2022-02-09 Nec Corp Communication system
CN114095138B (zh) * 2020-08-24 2023-05-30 维沃移动通信有限公司 用户面数据的传输方法和网络节点
CN114126090B (zh) * 2020-08-26 2024-01-12 大唐移动通信设备有限公司 上行数据处理方法、装置、网络设备、终端设备及介质
CN114126091A (zh) * 2020-08-26 2022-03-01 大唐移动通信设备有限公司 上行数据处理方法、装置、网络设备、终端设备及介质
CN112469084B (zh) * 2020-11-26 2023-03-07 展讯通信（上海）有限公司 数据传输方法、装置、设备、存储介质及程序产品
EP4262300A4 (en) * 2021-01-15 2024-02-14 Huawei Tech Co Ltd COMMUNICATION METHOD AND COMMUNICATION APPARATUS
CN115022865A (zh) * 2021-03-04 2022-09-06 华为技术有限公司 一种通信方法及设备
BR112023020309A2 (pt) * 2021-04-01 2023-11-21 Google Llc Gerenciamento de conexões de rádio durante a comunicação inicial de dados por meio de uma estação base distribuída
WO2022236000A1 (en) * 2021-05-07 2022-11-10 Google Llc Managing early data communication with a ue operating in an inactive state
EP4268537A1 (en) * 2021-10-21 2023-11-01 ZTE Corporation Method, device, and system for relay configuration in wireless networks
WO2023133249A1 (en) * 2022-01-06 2023-07-13 Google Llc Managing radio resource configurations for small data communication
CN117119616A (zh) * 2022-05-16 2023-11-24 中国移动通信有限公司研究院 多cu连接管理方法、装置及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106102106A (zh) * 2016-06-20 2016-11-09 电信科学技术研究院 一种终端接入的方法、装置及网络架构
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
WO2017127440A1 (en) * 2016-01-20 2017-07-27 Qualcomm Incorporated Techniques for providing uplink-based mobility
CN107027153A (zh) * 2017-03-16 2017-08-08 上海华为技术有限公司 业务的切换方法、上下文迁移方法及相关设备

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100678181B1 (ko) * 2002-07-31 2007-02-01 삼성전자주식회사 이동통신 시스템에서 멀티미디어 방송 멀티 캐스트 서비스 데이터를 제공하는 장치 및 방법
US20100260126A1 (en) 2009-04-13 2010-10-14 Qualcomm Incorporated Split-cell relay packet routing
CN101998332B (zh) * 2009-08-17 2013-08-07 中兴通讯股份有限公司 一种寻呼紧急业务用户的方法和系统
US9609688B2 (en) 2010-04-05 2017-03-28 Qualcomm Incorporated Methods and apparatus to facilitate relay startup and radio link failure (RLF) handling
CN102340886B (zh) * 2010-07-22 2014-04-16 大唐移动通信设备有限公司 一种重建立rrc连接的方法、装置及系统
KR101705678B1 (ko) * 2010-10-04 2017-02-22 삼성전자주식회사 ３ｇｐｐ 시스템에서 ｍｄｔ 측정 보고 제어 방법 및 장치
TWI450545B (zh) * 2011-03-31 2014-08-21 Mediatek Inc 通過相關資訊報告並處理失敗事件的方法和用戶設備
EP2509374A1 (en) 2011-04-05 2012-10-10 Panasonic Corporation Detachment of a mobile terminal (MTC) from a mobile communication system
US9462628B2 (en) 2011-07-11 2016-10-04 Qualcomm Incorporated Apparatus and method for maintaining a circuit-switched voice call in a multi-RAB wireless communication system in an area of weak coverage
WO2013023678A1 (en) * 2011-08-12 2013-02-21 Nokia Siemens Networks Oy Configuration of time zones in a telecommunication network
US9961591B2 (en) * 2011-10-18 2018-05-01 Qualcomm Incorported Optimizations to circuit-switched fallback (CSFB) procedure
US9629200B2 (en) * 2012-03-07 2017-04-18 Telefonaktiebolaget L M Ericsson Controlling connection states of a mobile terminal based on communication activity
EP3171659B1 (en) * 2012-07-06 2018-12-19 NEC Corporation Method of determining expiration period of timer, network node, and non-transitory computer readable medium
WO2014019138A1 (zh) * 2012-07-31 2014-02-06 富士通株式会社 用户设备上下文的识别方法、用户设备以及基站
CN103634930A (zh) * 2012-08-22 2014-03-12 普天信息技术研究院有限公司 一种无线资源控制连接重建方法
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
CN104105219B (zh) * 2013-04-01 2017-09-01 电信科学技术研究院 一种数据传输方法及装置
EP3143827A1 (en) * 2014-05-16 2017-03-22 Telefonaktiebolaget LM Ericsson (publ) Node and method for establishing an inactivity timer in a wireless network
KR102232787B1 (ko) 2014-06-30 2021-03-26 삼성전자 주식회사 무선 통신 시스템에서 서비스 연속성을 제어하는 방법 및 장치
KR20160004061A (ko) * 2014-07-02 2016-01-12 한국전자통신연구원 스몰 셀 환경에서의 이동성 관리 방법 및 그 장치
JP6517806B2 (ja) * 2014-07-25 2019-05-22 京セラ株式会社 基地局及び移動局
WO2016074211A1 (zh) * 2014-11-14 2016-05-19 华为技术有限公司 一种数据转发的方法和控制器
US10091649B2 (en) * 2015-07-12 2018-10-02 Qualcomm Incorporated Network architecture and security with encrypted client device contexts
JP6656361B2 (ja) * 2015-09-16 2020-03-04 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 無線リソース制御（ｒｒｃ）接続を解放する方法および装置
CN106793169B (zh) * 2016-08-12 2019-04-09 展讯通信（上海）有限公司 非激活态的配置方法、进入方法及装置，基站和终端
WO2018236867A2 (en) * 2017-06-19 2018-12-27 Intel Corporation CONTROL PANEL AND USER PLANE SEPARATION IN NEW RADIO (NR) SYSTEMS

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017127440A1 (en) * 2016-01-20 2017-07-27 Qualcomm Incorporated Techniques for providing uplink-based mobility
CN106102106A (zh) * 2016-06-20 2016-11-09 电信科学技术研究院 一种终端接入的方法、装置及网络架构
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
CN107027153A (zh) * 2017-03-16 2017-08-08 上海华为技术有限公司 业务的切换方法、上下文迁移方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA; ALCATEL-LUCENT SHANGHAI BELL: "F1-C UE associated functions", 3GPP TSG RAN WG3 ADHOC NR R3-172330, no. R3-172330, 29 June 2017 (2017-06-29), XP051307739 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2017438131B2 (en) * 2017-10-31 2021-05-20 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Indication method for context identification, acquisition method, user equipment and base station
US11240782B2 (en) 2017-10-31 2022-02-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Indication method for context identification, acquisition method, user equipment and base station
CN114073031A (zh) * 2019-08-14 2022-02-18 华为技术有限公司 一种通信方法及相关设备
CN113473513A (zh) * 2021-09-02 2021-10-01 成都爱瑞无线科技有限公司 链路故障检测及处理方法、装置、系统及存储介质

Also Published As

Publication number Publication date
CN110326321A (zh) 2019-10-11
US20190313244A1 (en) 2019-10-10
KR102397469B1 (ko) 2022-05-12
EP3570584B1 (en) 2021-11-03
CN110662267B (zh) 2020-12-08
US20210227378A1 (en) 2021-07-22
CA3072715C (en) 2024-02-27
JP2020530724A (ja) 2020-10-22
CN110662268B (zh) 2021-12-14
RU2020109982A (ru) 2021-09-14
ES2901695T3 (es) 2022-03-23
EP3998796A1 (en) 2022-05-18
JP2022177088A (ja) 2022-11-30
EP3570584A1 (en) 2019-11-20
CN110662267A (zh) 2020-01-07
BR112020002752A2 (pt) 2020-08-18
EP3570584A4 (en) 2020-01-15
JP7394940B2 (ja) 2023-12-08
CN110662268A (zh) 2020-01-07
CN109391963A (zh) 2019-02-26
CN110326321B (zh) 2021-08-03
RU2020109982A3 (zh) 2021-12-08
CA3072715A1 (en) 2019-02-14
JP7139412B2 (ja) 2022-09-20
KR102585617B1 (ko) 2023-10-05
KR20220063313A (ko) 2022-05-17
US11178538B2 (en) 2021-11-16
KR20200038514A (ko) 2020-04-13
CN109391963B (zh) 2022-03-11
CA3225953A1 (en) 2019-02-14

Similar Documents

Publication Publication Date Title
JP7394940B2 (ja) 伝送方法およびネットワークデバイス
TWI665929B (zh) 處理在長期演進網路端及第五代網路端間的移動性的裝置及方法
US11758609B2 (en) Radio resource control RRC message processing method, apparatus, and system
CN108605376B (zh) 无线终端、无线站及其方法
CN109892003B (zh) 经由具有中继能力的用户装备ue在远程ue和电信网络之间建立连接的方法和系统
EP3253122A1 (en) Method, apparatus, and system for transmitting data during handover procedure
CN110167142B (zh) 无线资源控制rrc连接方法、重连接方法和装置
TWI657679B (zh) 處理系統間行動中的封包資料流的裝置及方法
JP2020523955A (ja) 通信方法および装置ならびに無線アクセス・ネットワーク
WO2021134725A1 (zh) 通信方法及装置
WO2019062794A1 (zh) 一种建立承载的方法及设备
WO2021196854A1 (zh) 通信方法、装置、设备和存储介质
RU2780471C2 (ru) Способ передачи и сетевое устройство
RU2800767C2 (ru) Способ передачи и сетевое устройство
WO2022198597A1 (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: 18844764

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018844764

Country of ref document: EP

Effective date: 20190813

ENP Entry into the national phase

Ref document number: 3072715

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2020508042

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020002752

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20207007175

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112020002752

Country of ref document: BR

Free format text: SOLICITA-SE APRESENTAR NOVAS FOLHAS REFERENTES AO RELATORIO DESCRITIVO TRADUZIDO DA PETICAO 870200023873, UMA VEZ QUE O CONJUNTO APRESENTADO TEM SUAS PAGINAS NUMERADAS INCORRETAMENTE.

ENP Entry into the national phase

Ref document number: 112020002752

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200210