WO2018170706A1 - 通信方法及其设备 - Google Patents

通信方法及其设备 Download PDF

Info

Publication number
WO2018170706A1
WO2018170706A1 PCT/CN2017/077388 CN2017077388W WO2018170706A1 WO 2018170706 A1 WO2018170706 A1 WO 2018170706A1 CN 2017077388 W CN2017077388 W CN 2017077388W WO 2018170706 A1 WO2018170706 A1 WO 2018170706A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
information
entity
connection
access network
Prior art date
Application number
PCT/CN2017/077388
Other languages
English (en)
French (fr)
Inventor
李濛
邓强
黄正磊
杨艳梅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/077388 priority Critical patent/WO2018170706A1/zh
Priority to CN201780084667.6A priority patent/CN110214460B/zh
Priority to EP17901872.6A priority patent/EP3585110B1/en
Publication of WO2018170706A1 publication Critical patent/WO2018170706A1/zh
Priority to US16/569,735 priority patent/US11202250B2/en

Links

Images

Classifications

    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006—Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • 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
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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

  • Embodiments of the present application relate to the field of communications, and, more particularly, to a communication method and apparatus therefor.
  • the power capacity of the terminal device is usually limited. Therefore, when the terminal device has no data transmission, the terminal device is converted from a Radio Resource Control Connected (RRC Connected) state to a radio resource control connection idle (Radio Resource Control).
  • RRC Connected Radio Resource Control
  • the Idle, RRC-Idle state or radio resource control connection is idle in an inactive state to reduce the power consumption of the terminal device.
  • the radio resource control connection state is simply referred to as a connection state
  • the radio resource control connection idle state is simply referred to as an idle state
  • the radio resource control connection idle inactive state is simply referred to as an inactive state.
  • the terminal device in the idle state transmits or receives data
  • some resources released when the connection state is converted to the idle state are restored, for example, re-establishing the bearer, restoring the connection, and the like.
  • the introduction of the idle state can reduce the power consumption of the terminal device, when the terminal device transitions from the idle state to the connected state, the network device needs to obtain the context information of the terminal device, thus causing additional delay.
  • the network device when the terminal device is in an inactive state, if the network device is switched from the inactive state to the connected state, the network device also needs to obtain the context information of the terminal device, which also brings additional delay.
  • the embodiment of the present application provides a communication method, which can be beneficial to reducing the delay of converting a terminal device into a connected state.
  • a communication method including: a first control plane function entity acquires access network information of a terminal device, where the terminal device is in an idle state or an inactive state; and the first control plane function entity is configured according to The access network information sends the context information of the terminal device to the access network device.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • the context information of the terminal device includes: user plane context information of the terminal device; and control plane context information of the terminal device.
  • the context information of the terminal device may include only control plane context information of the terminal device.
  • control plane context information and the user plane context information may be carried in the same message or may be carried in different messages.
  • control plane context information and the user plane context information are carried in different messages, the application is implemented. The example does not limit the order in which the above two messages are executed.
  • the method further includes: the first control plane function entity receiving the first identifier sent by the access network device Information and second standard
  • the first identification information is used to identify a connection between the access network device and the first control plane entity; the second identification information is used to identify the access network device and user
  • the first control plane function entity can acquire the access network device and the first control according to the first identifier information by acquiring the first identifier information and the second identifier information sent by the access network device. a first connection between the functional entities, and a second connection between the access network device and the user plane functional entity according to the second identification information.
  • the terminal device When the terminal device has a data transmission requirement, the terminal device can be directly used. Connections communicate without waiting for the process of establishing a connection, which helps to reduce latency.
  • the method further includes: sending an update request message to the user plane function entity, where the update request message includes the Second identifier information; receiving an update response message sent by the user plane function entity.
  • the first control plane function entity can send the update request message to the user plane function entity, so that the user plane function entity can obtain the second identifier information of the access network device, and thus can establish a connection with the access network device.
  • the second connection can be established.
  • the method further includes: the first control plane function entity acquiring the access network information of the terminal device, including The first control plane function entity acquires the access network information of the terminal device, and the first control plane function entity receives the connection of the terminal device from the network capability open function entity or the second control plane function entity. And the first control plane function entity receives the location prediction information of the terminal device from the network capability open function entity or the second control plane function entity, and acquires the terminal device according to the location prediction information. Access network information.
  • the second control plane function entity when the first control plane function entity receives the access network information of the terminal device or the location prediction information of the terminal device from the second control plane function entity, the second control plane function entity is also sent by receiving the network capability open function entity.
  • the access network information of the terminal device obtained by the message or the location prediction information of the terminal device.
  • the method when the terminal device is in an inactive state, the method further includes: the first control plane function entity The context information of the terminal device is obtained from the access network device where the terminal device currently resides.
  • the method further includes: the first control plane function entity acquiring current location information of the terminal device or the Information about the access network device of the terminal device when the terminal device is switched to the connected state.
  • the access network information includes identification information and/or cell identification information that can access the network device.
  • the method further includes: the first control plane function entity sends a feedback message to the network capability open function entity,
  • the feedback message includes current location information of the terminal device or information of the access network device of the terminal device when the terminal device is converted into a connected state.
  • the network capability open function entity can further optimize the access network device that may be accessed when the terminal device is converted into the connected state according to the feedback information sent by the control plane function entity, and improve the accuracy of the pre-established connection.
  • a second aspect of the present invention provides a communication method, including: an access network device receiving context information of a terminal device sent by a first control plane function entity, where the terminal device is in an idle state or an inactive state; The device performs data transmission with the terminal device according to the context information of the terminal device.
  • the method further includes: The first identification information and the second identification information sent by the first control plane function entity, where the first identifier information includes identifier information of a connection between the access network device and the first control plane entity;
  • the second identification information includes identification information of a connection between the access network device and a user plane functional entity.
  • the method further includes: the access network device sending, to the first control plane function entity, the current current of the terminal device Location information or information of the access network device.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • a core network device for performing the method of any of the above first aspect or any of the possible implementations of the first aspect.
  • the core network device comprises means for performing the method of any of the above-described first aspects or any of the possible implementations of the first aspect.
  • an access network device for performing the method in any of the foregoing second aspect or any possible implementation of the aspect.
  • the access network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • a core network device is provided, the core network device comprising: a transceiver, a memory, a processor, and a bus system.
  • the transceiver, the memory and the processor are connected by the bus system, the memory is for storing instructions for executing instructions stored by the memory to control the transceiver to receive and/or transmit signals, and
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • an access network device comprising: a transceiver, a memory, a processor, and a bus system.
  • the transceiver, the memory and the processor are connected by the bus system
  • the memory is for storing instructions for executing instructions stored by the memory to control the transceiver to receive signals and/or transmit signals
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a seventh aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the second aspect or any of the possible implementations of the second aspect.
  • FIG. 1 is a schematic structural diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of an application scenario of another embodiment of the present application.
  • FIG. 3 shows a schematic diagram of a state transition relationship of a terminal device.
  • FIG. 4 shows a schematic flow chart of a method of an embodiment of the present application.
  • FIG. 5 shows a schematic flow chart of a method of another embodiment of the present application.
  • FIG. 6 shows a schematic flow chart of a method of an embodiment of the present application.
  • FIG. 7 shows a schematic flow chart of a method of an embodiment of the present application.
  • FIG. 8 shows a schematic flow chart of a method of an embodiment of the present application.
  • FIG. 9 shows a schematic flow chart of a method of an embodiment of the present application.
  • FIG. 10 shows a schematic flow chart of a method of an embodiment of the present application.
  • Figure 11 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 12 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 13 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 14 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 15 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 16 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 17 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 18 shows a schematic flow chart of a method of one embodiment of the present application.
  • FIG. 19 shows a schematic flow chart of a method of an embodiment of the present application.
  • Figure 20 shows a schematic flow chart of a method of one embodiment of the present application.
  • Figure 21 shows a schematic flow chart of a method of one embodiment of the present application.
  • FIG. 22 shows a schematic block diagram of a core network device of one embodiment of the present application.
  • FIG. 23 shows a schematic block diagram of an access network device according to an embodiment of the present application.
  • Figure 24 is a block diagram showing the schematic structure of an apparatus of one embodiment of the present invention.
  • Figure 25 is a block diagram showing the schematic structure of an apparatus of another embodiment of the present invention.
  • the terminal device may 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, and a wireless communication.
  • Device user agent, or user device.
  • 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.
  • the access network device may be a network device used for communication with the terminal device, for example, may be a base station (Base Transceiver Station, BTS) in the GSM system or CDMA, or may be WCDMA.
  • BTS Base Transceiver Station
  • the base station (NodeB, NB) in the system may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or the base station may be a relay station, an access point, an in-vehicle device, a wearable device, and a future 5G.
  • a network side device in the network such as a Next Generation Radio Access Network (NG-(R)AN) or the like.
  • NG-(R)AN Next Generation Radio Access Network
  • the present application introduces a schematic diagram of an application scenario of an embodiment of the present application in conjunction with FIG. 1 and FIG. Specifically, the network element involved in the embodiment of the present application is as follows:
  • SCS Service Capability Server
  • AS Application Server
  • SCEF Service Capability Exposure Function
  • Network Exposure Function Used to securely open the services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network function to the outside.
  • Access and Mobility Management Function (AMF) entity main functions include the endpoint of the radio access network control plane, the endpoint of non-access signaling, mobility management, lawful interception, access authorization or authentication Wait.
  • AMF Access and Mobility Management Function
  • Session Management Function entity: used for session management, IP address allocation and management, selection of manageable user plane functions, endpoints for policy control and charging function interfaces, and downlink data notification.
  • SMF Session Management Function
  • Next Generation User Plane (NG-UP) entity used for packet routing and forwarding, quality of service (QoS) processing of user plane data, and so on.
  • QoS quality of service
  • Mobility Management Entity Used for control plane management of the core network.
  • the main functions include mobility management, session management, access control, network element selection, and storage user context.
  • Evolved Serving Mobile Location Center (E-SMLC) entity provides information related to the location of the terminal device, and the like.
  • the RRC-connected state in the present application may also be referred to as an RRC connected state or a connected state.
  • the RRC-idle state may also be referred to as an RRC idle state or an idle state, which is not limited in this application.
  • FIG. 1 is a schematic structural diagram of an application scenario of an embodiment of the present application.
  • a 4G system under the application service capability open architecture in the 3GPP system is shown.
  • the data sent by the SCS/AS is transmitted to the SCEF through the API interface.
  • the SCEF interacts with the HSS to verify whether the SCS/AS is authorized.
  • the SCEF sends data to the MME through the T6a interface for network related control and optimization.
  • a Home Subscriber Server is a server for storing user subscription information, and is mainly responsible for managing subscription data of a user and location information of a mobile user.
  • S-GW Serving GateWay
  • SAE System Architecture Evolution
  • a packet data network gateway is a gateway responsible for accessing a packet data network (PDN) of a terminal device, and assigns an IP address to the terminal device, and is also a 3GPP and a non-3GPP access system. Mobility anchor.
  • the Policy and Charging Rules Function (PCRF) functional entity includes policy control decisions and flow-based charging control functions.
  • the Evolved Universal Terrestrial Radio Access Network includes an eNB to provide radio resources for the terminal device to access the network, which can provide higher uplink and downlink rates, lower transmission delay, and more reliability. Wireless transmission.
  • the S1-MME is a control plane interface between the eNB and the MME, and is used to control bearer and connection between the terminal device and the network, and send non-access stratum (NAS) messages;
  • S1-U It is a reference point of the user plane between the eNB and the S-GW, and provides a packet data unit of the user plane between the eNB and the S-GW through the tunnel.
  • LTE-Uu is a wireless connection interface between the terminal device and the eNB.
  • FIG. 2 is a schematic structural diagram of an application scenario of another embodiment of the present application.
  • the data sent by the SCS/AS is transmitted to the Network Exposure Function (NEF) entity.
  • NEF Network Exposure Function
  • AUSF Authentication Service Function
  • the NEF sends the data to the AMF and the SMF for network related control and optimization.
  • the NEF entity is used to securely open the services and capabilities and the like provided by the 3GPP network functions to the outside.
  • the main functions of the Next Generation User Plane (NG-UP) entity include packet routing and forwarding, and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the Next Generation-((Radio) Access Network, (R)AN) provides network resources for terminal access.
  • the main functions of the AUSF entity include user authentication and the like.
  • DN Data Network
  • Internet A network used to transmit data, such as the Internet.
  • the N2 interface is a reference point of the (R)AN and the control plane of the core network, and is used for sending the NAS message.
  • the N3 interface is a reference point of the user plane between the (R)AN and the NG-UP entity, and is used for transmitting the user. Surface data, etc.
  • FIG. 3 shows a schematic diagram of a state transition relationship of a terminal device.
  • the terminal device performs network attachment and transitions from an idle state to a connected state. Then, in some cases, for example, when the terminal device does not perform data transmission for a long time, the connection state is switched to the idle state, and when the terminal device has the data transmission requirement, the idle state is switched to the connected state. In other cases, for example, when the terminal device does not move (such as a water meter, an electric meter or a temperature, a humidity sensor, etc.), or the terminal device moves at a very low rate, the terminal device may transition to an inactive state, after which When the terminal device has a data transmission requirement, it transitions from an inactive state to a connected state.
  • the terminal device may transition to an inactive state, after which When the terminal device has a data transmission requirement, it transitions from an inactive state to a connected state.
  • the eNB releases the RRC connection and the Data Radio Bearer (DRB) between the terminal device and the eNB without releasing the eNB and the MME.
  • DRB Data Radio Bearer
  • the terminal device transitions from the inactive state to the connected state, if the terminal device accesses the target base station, the connection maintained between the source base station and the MME or the source base station and the S-GW will not continue to provide services for the terminal device, thus The target device through which the terminal device accesses establishes a connection with the MME or the S-GW to transmit data of the terminal device.
  • the terminal device accesses the target base station, and the target base station directly connects to the source base station (for example, there is an X2 interface), then the target base station requests the source base station for the context information of the terminal device.
  • the source base station transmits the terminal device context information to the target base station.
  • the target base station sends a path switch request to the MME, after which the target base station sends a context connection release message to the source base station.
  • the terminal device successfully accesses the target base station.
  • the source base station needs to keep the context information of the terminal device all the time, so that when the target base station establishes a connection with the terminal device, the target base station can acquire the terminal device from the source base station. Contextual information, thus causing unnecessary resource consumption.
  • the target base station when the terminal device moves out of the coverage of the source base station, if there is no direct connection between the target base station and the source base station, the target base station sends the context information of the terminal device to the MME, and then the MME forwards the context of the terminal device to the source base station.
  • the MME After receiving the context information response of the terminal device sent by the source base station, the MME forwards the context information of the terminal device to the target base station; after that, the target base station sends a path switch request to the MME, and waits for the acknowledgement information, and then the target base station sends the source base station to the source base station.
  • the transmitting terminal device context connection release information At this time, the terminal device successfully accesses the new base station. Therefore, in this solution, the number of interaction signaling between the network device and the terminal device is large, the network load is large, and the delay for establishing the connection is large.
  • the embodiment of the present application provides a communication method and a device thereof, which can pre-deliver the context information of the terminal device before the terminal device has the data transmission requirement, and further, can establish a connection between the network devices in advance. Therefore, the time required for the terminal device to wait for the transmission of the context information is reduced, thereby reducing the delay in establishing the connection and improving the user experience.
  • FIG. 4 shows a schematic flow chart of a method of an embodiment of the present application. As shown in FIG. 4, the method 400 includes:
  • Step 410 The first control plane function entity acquires access network information of the terminal device, where the terminal device is in an idle state or an inactive state.
  • Step 420 The first control plane function entity sends the context information of the terminal device to the access network device according to the access network information.
  • the first control plane entity may be any one of the following: an MME, an AMF entity, and an SMF entity. It should be understood that an entity having a function similar to the AMF entity or the SMF entity falls within the scope of the embodiment of the present application. The application is not limited.
  • the AMF entity or the SMF entity may be an independent physical device, or may be integrated with other functional entities on the same physical device, and is not limited.
  • the method 400 can be applied to the application scenario shown in FIG. 1 or FIG. 2, that is, the first control plane functional entity may be the MME in FIG. 1 or the AMF entity or SMF shown in FIG. 2.
  • the entity, correspondingly, the access network device may be the eNB shown in Figure 1, or may be the NG-(R) AN shown in Figure 2.
  • the access network information may include cell information, such as an E-UTRAN Cell Global Identifier (ECGI), a base station identifier, and the like.
  • cell information such as an E-UTRAN Cell Global Identifier (ECGI), a base station identifier, and the like.
  • the first control plane function entity may determine the access network device corresponding to the access network information according to the access network information, and send the context information of the terminal device to the access network device.
  • the access network device may be one or more, and the access network device may be an access network device that is accessed when the terminal device predicted by the predicted network element is converted into the connected state.
  • the predicted network element may be a functional entity such as NEF or SCEF, which is not limited in this application.
  • the manner in which the first control plane function entity acquires the access network information of the terminal device may be the access network information that is sent by the predicted prediction network element.
  • the manner in which the first control plane function entity obtains the access network information may also be that the first control plane function entity initiates a request to the other network element to obtain the access network information and the like, which is not limited in this application.
  • the terminal device when the terminal device is in an idle state or an inactive state, the terminal device does not access any access network device, in which case, when there is data transmission demand between the terminal device and a certain access network device.
  • the terminal device needs to establish a connection with the access network device, and then the first control plane function entity sends the context information of the terminal device to the access network device, that is, when the first control plane functional entity
  • the terminal device can perform data transmission with the access network device, and then the terminal device Before starting the data transmission, it is necessary to wait for the first control plane function entity to send the context information of the terminal device to the access network device, so there is a large delay.
  • the first control plane function entity acquires the context information of the terminal device from the access network device currently camped by the terminal device, and the access network device and the terminal determined according to the access network information in step 420 When the access network device currently camped on by the device is the same access network device, the context information of the terminal device may not be sent to the currently camped access network device.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • the foregoing method further includes:
  • the first control plane function entity establishes a first connection with the access network device, where the first connection is used to transmit control signaling of the terminal device between the access network device and the first control plane functional entity, where A control plane function entity is an MME or an AMF entity; the user plane function entity establishes a second connection with the access network device, and the second connection is used to transmit the terminal device between the access network device and the user plane functional entity Data, in this case, the terminal device is still in an idle state or an inactive state, wherein the user plane function entity is an S-GW entity or an NG-UP entity.
  • the access network device is an eNB
  • the first control plane function entity is an MME
  • the first connection may be an S1-MME connection between the eNB and the MME
  • the second connection may be The S1-U connection between the eNB and the S-GW entity is connected.
  • the access network device is an NG-(R)AN
  • the first control plane functional entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the first connection may be an N2 connection between the NG-(R)AN and the AMF entity
  • the second connection may be between the NG-(R)AN and the NG-UP entity.
  • N3 connection It should be understood that, in some scenarios, the first connection may also be used to transmit data, which is not limited in this application.
  • the context information of the terminal device includes: user plane context information of the terminal device; and control plane context information of the terminal device.
  • the user plane context information may include at least one of the following information: QoS information of the second connection, such as QoS information of the PDU session in the 5G system, QoS information carried by the network in the 4G system; and the second connection in the user plane functional entity
  • QoS information of the second connection such as QoS information of the PDU session in the 5G system, QoS information carried by the network in the 4G system
  • the S1-U is connected to the General Packet Radio Service Tunneling Protocol Tunnel Endpoint Identifier (gTP-TEID) in the S-GW, for example, in the 5G system.
  • the N3 is connected to the Tunnel Info in the NG-UP, where the user plane function entity includes an S-GW, an NG-UP, and the like.
  • the control plane context information may include at least one of the following information: security context information of the first connection, such as a key of the first connection, etc.; and may further include identification information of the first connection in the control plane function entity, for example
  • security context information of the first connection such as a key of the first connection, etc.
  • identification information of the first connection in the control plane function entity for example
  • the S1-MME is connected to the MME-UE-S1AP-ID in the MME
  • the N2 in the 5G system is connected to the AMF signaling connection identification (AMF signaling connection identification) in the AMF entity
  • the control plane context information may also be Including: handover restriction information, etc.
  • the context information of the terminal device may include only control plane context information of the terminal device.
  • the method when the terminal device is in an inactive state, the method further includes: The first control plane function entity acquires context information of the terminal device from an access network device that the terminal device currently resides; or the context of the at least one terminal device that is stored locally by the first control plane function entity
  • the context information of the terminal device is selected in the information, for example, the context information of the terminal device is determined according to the identifier information of the terminal device. It should be understood that there may be other manners for obtaining the context information of the terminal device, which is not limited in this application.
  • the control plane context information and the user plane context information may be carried in the same message, or may be carried in different messages.
  • the embodiment of the present application does not limit the sequence in which the two messages are executed.
  • the Initial Context Setup Request message carries the context information of the terminal device, where the initialization context is established.
  • the request message carries indication information indicating that the DRB between the terminal device and the access network device is not immediately established.
  • the initial initialization request message includes an indication bit, which is used to indicate that the access network device does not immediately establish a DRB with the terminal device.
  • the DRB between the terminal device and the access network device is not immediately established, and the terminal device initiates the initiative to the access network device only when the terminal device has the data transmission requirement.
  • the DRB is established only after the DRB request is established or the terminal device establishes an RRC connection with the access network device.
  • the initial context setup request message carries the identifier “MME-UE-S1AP-ID” in which the S1-MME is connected in the MME.
  • the “MME-UE-S1AP-ID” may be 211, and therefore, the eNB And the MME is configured to establish, according to the foregoing identifier, a first connection between the access network device and the first control plane functional entity; further, the initial context setup request message carries the identifier “gTP” of the S1-U connection in the S-GW.
  • - TEID for example, the "gTP-TEID" in the S-GW may be 7e10b568. Therefore, the eNB and the S-GW may establish a second connection between the access network device and the user plane functional entity according to the foregoing identifier.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the N2 connection setup response message and the N3 connection setup request message respectively carry the terminal device control plane context information and The user plane context information, where the N2 connection setup response message or the N3 connection setup request message carries indication information indicating that the DRB between the terminal device and the access network device is not immediately established.
  • the N2 connection setup response message includes an indication bit for indicating that the DRB between the terminal device and the access network device is not immediately established.
  • the DRB between the terminal device and the access network device is not immediately established, and only when the terminal device determines that there is a data transmission requirement.
  • the DRB request is initiated to the access network device or the terminal device establishes an RRC connection with the access network device, the DRB is established.
  • the foregoing N2 setup response message carries the identifier "AMF Signaling Connection ID" in which the N2 is connected in the AMF entity. Therefore, the (R)AN and the AMF entity may establish a connection between the access network device and the second control plane function entity AMF entity according to the foregoing identifier. Further, the N3 setup request message carries the first control plane function entity storage. N3 is connected to the identification information in the NG-UP. Therefore, the (R)AN and the NG-UP can establish a connection between the access network device and the user plane function entity NG-UP according to the foregoing identification information.
  • the method further includes: receiving, by the first control plane function entity, the The first identifier information and the second identifier information sent by the access network device, where the first identifier information is used to identify a connection between the access network device and the first control plane entity; The identification information is used to identify a connection between the access network device and a user plane functional entity.
  • first identifier information and the second identifier information may be carried in the same message, and may be carried in different messages.
  • the application is not limited.
  • the first identifier information and the second identifier information may be carried in an initialization context. Create a reply message (Initial Context Setup Response).
  • the first identifier information may be identifier information of the connection between the access network device and the first control plane function entity in the access network device, for example, in the 4G system, the access network device is an eNB, A control plane function entity is an MME, and the eNB carries the first identifier information in the initial context setup response message sent to the MME, where the first identifier information is the identifier of the S1-MME connected to the eNB "ENB-UE-S1AP- ID, for example, the "ENB-UE-S1AP-ID" may be 2; the second identification information is identification information of the connection between the access network device and the user plane functional entity in the access network device, for example, in a 4G system The second identifier information is the identifier "gTP-TEID" that the S1-U is connected to in the eNB.
  • the "gTP-TEID" may be 6f84e480.
  • the access network device is an NG-(R) AN device
  • the first control plane function entity is an SMF entity
  • the first identifier information includes an identifier of the N2 connection in the (R) AN device.
  • R) AN Signaling Connection ID R
  • the second identification information is used to identify the connection between the access network device and the user plane functional entity, for example, in a 5G system, then the second identification information is N3 connected in the (R) AN device Tunnel information "RAN Tunnel info”.
  • the method further includes: sending an update request message to the user plane function entity, where the update request message includes the second identifier information; and receiving, by the user plane function entity, Update the response message.
  • the user plane function entity may be an S-GW in a 4G system, and the user plane function entity may be an NG-UP entity in a 5G system.
  • the first control plane function entity may carry the second identifier information in the update request message, and send the update request message to the user plane function entity, to establish the second connection, when the user plane function entity receives the After the message, the update response message is sent to the first control plane function entity, and the first control plane function entity is notified to establish the completion of the second connection.
  • the second identifier information is stored, and then the update request message is sent to the user plane function entity, where the update request message is sent.
  • the user plane function entity Carrying the second identifier information of the second connection in the access network device, the user plane function entity establishes a second connection according to the second identifier information carried in the update request message, and completes the second connection and then goes to the control plane function entity.
  • An update response message is returned, for example, the update response message can be a confirmation message.
  • the first control plane function entity is an MME
  • the user plane function entity is an S-GW entity
  • the second identifier information includes an identifier of the S1-U connection in the eNB.
  • the MME sends the identification information of the S1-U connection in the eNB to the S-GW entity, where the identifier information is carried in the bearer modification request message, where the update request message is updated.
  • the request message is: when the S-GW establishes an S1-U connection according to the foregoing identification information, and after the connection establishment is completed, the bearer modification reply message is returned to the MME, where the update response message is the update response message.
  • the AMF entity Storing the second identifier information of the second connection in the access network device, for example, the second identifier information is connected to the N3
  • the identification information in the NG-(R) AN device further, the AMF entity sends the N3 connection information in the NG-(R) AN device to the NG-UP entity through the SMF entity, and the identifier information is carried in the user plane update.
  • the user plane update request message is the above update request message
  • the NG-UP entity establishes an N3 connection according to the foregoing identification information, and returns a user face update reply message to the SMF entity after the connection establishment is completed, and updates the reply here.
  • the message is the above update response message.
  • the terminal device when the terminal device is in an idle state or an inactive state, the first connection between the control plane function entity and the access network device has been established, and the second network establishment between the access network device and the user plane function entity is established. It has also been established.
  • a radio bearer with the target access network device When the terminal device has data transmission requirements, a radio bearer with the target access network device will be established, and data transmission will be performed using the first connection and/or the second connection.
  • the first control plane function entity acquires access network information of the terminal device, where the first control plane function entity acquires access network information of the terminal device.
  • the first control plane function entity acquires access network information of the terminal device from the network capability open function entity or the second control plane function entity; or the first control plane function entity functions from the network capability open function
  • the entity or the second control plane function entity acquires location prediction information of the terminal device, and acquires access network information of the terminal device according to the location prediction information.
  • the foregoing solution may include two cases: in one case, the first control plane function entity receives the access network information of the terminal device or the location prediction information of the terminal device from the network capability open function entity.
  • the network capability open function entity may be an SCEF entity in the application scenario of FIG. 1 or an NEF entity in the application scenario of FIG. 2, which is not limited in this application.
  • the position prediction information of the terminal device may include the predicted latitude and longitude coordinates or the predicted GPS information of the terminal device at a specified time, and the like.
  • the first control plane function entity learns the change. For example, in the application scenario shown in FIG. 1, the MME releases the context of the terminal device sent by the eNB. a message (Context Release Message), determining that the terminal device is switched from the connected state to the idle state or the inactive state; further, the first control plane function entity triggers the network element responsible for collecting the information to collect information about the terminal device, such as a historical moving track, Direction of movement, speed, navigation information, etc. It should be understood that the network element responsible for information collection may be an existing network element, such as an E-SMLC entity, or a new network element, which is not limited in this application.
  • the network element responsible for information collection may be an existing network element, such as an E-SMLC entity, or a new network element, which is not limited in this application.
  • the network element responsible for information collection informs the predicted network element of the related information of the collected terminal device, and the predicted network element predicts the location and time of the terminal device to be converted into the connected state, and the predicted manner may be matched by the historical information, or according to Navigation information and mobile speed prediction.
  • the predicted network element may be an existing network element, such as a SCEF entity, or may be a new network element, which is not limited in this application.
  • the prediction network element may generate prediction information, where the prediction information carries the location information when the terminal device is converted into the connected state and the identifier information of the terminal device, and further, the prediction information may further carry the terminal device into the connected state. Time information.
  • the network can open the function when the prediction information sent by the network element to the network capability open function entity carries the location information when the terminal device is converted into the connected state, the identifier information of the terminal device, and the time when the terminal device is converted into the connected state.
  • the entity generates a timer, and the initial time when the timer starts to be is the time when the network capability open function entity receives the prediction information sent by the predicted network element.
  • the network capability open function entity moves to the first control plane.
  • the function entity sends a connection establishment request message, and the time duration of the timer is the time interval between the time when the terminal device converts to the connected state and the current time.
  • the predicted network element generates a timer, and the timer duration of the timer is converted to a connected state by the terminal device.
  • the time interval between the time and the current time, and the initial time when the timer starts to count is the time when the prediction network element determines the prediction information.
  • the prediction network element sends the prediction information to the network capability open function entity, where the prediction information is carried.
  • the network capability opening function entity After receiving the prediction information, the network capability opening function entity sends the first message to the first control plane function entity, where the first message carries the location information when the terminal device is converted into the connected state and the identifier information of the terminal device, The first control plane function entity obtains the access network information of the terminal device in the step 410 according to the foregoing message; or the first message directly carries the access network information of the terminal device and the identifier information of the terminal device, The first control plane function entity learns the access network information of the terminal device by using the first message.
  • connection establishment request message may explicitly indicate that the first control plane function entity initiates the establishment process of the first connection and/or the second connection, and may also implicitly instruct the first control plane function entity to initiate the first connection and / or the establishment process of the second connection.
  • the foregoing connection establishment request message may include location information for indicating that the first connection is established and/or the second connection is established, and the location information when the terminal device is converted to the connected state, for example, ECGI, And identification information of the terminal device, such as an International Mobile Subscriber Identity (IMSI).
  • IMSI International Mobile Subscriber Identity
  • the name of the connection establishment request message may be used to indicate that the first connection is established and/or the second connection is established. Therefore, the implicit connection establishment request message includes the terminal device converting to the connection. Location information, such as ECGI, and identification information of the terminal device, such as IMSI.
  • the first control plane function entity acquires access network information of the terminal device or location prediction information of the terminal device from the second control plane function entity.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the information content carried in the second message sent by the second control plane function entity passes through the receiving network.
  • the message sent by the capability open function entity is obtained.
  • the method further includes: the first control plane function entity acquiring current location information of the terminal device or an access network device accessed when the terminal device is converted into a connected state Access network information.
  • the first control plane function entity obtains the access network information of the access network device that is actually accessed when the terminal device is converted into the connected state or the previous location information of the terminal device, and the foregoing information may be used when the terminal device is converted into the connected state.
  • the actually accessed access network device is sent to the first control plane functional entity.
  • the access network device that is actually accessed when the terminal device is switched to the connected state may be one of the access network devices in the foregoing step 420, or may be another access network device, and the application does not do this. limited.
  • the access network device that is actually accessed when the terminal device is switched to the connected state may send the current location information of the terminal device to the first control plane function entity, or may actually access the terminal device when the terminal device is converted into the connected state.
  • the access network information of the network device is sent to the first control plane function entity. It should be understood that the access network information includes the identifier information and/or the cell identifier information of the target access network device.
  • the first control plane function entity sends a feedback message to the network capability open function entity, where the feedback message includes current location information of the terminal device or the The access network information of the access network device accessed when the terminal device is switched to the connected state.
  • the network capability open function entity can further optimize the access network device that may be accessed when the terminal device is converted into the connected state according to the feedback information sent by the control plane function entity, and improve the pre-established connection. Authenticity.
  • FIG. 5 is a schematic flowchart of a method according to another embodiment of the present application.
  • the execution body of the method may be an access network device. As shown in FIG. 5, the method 500 includes:
  • Step 510 The access network device receives the context information of the terminal device sent by the first control plane function entity, where the terminal device is in an idle state or an inactive state.
  • Step 520 The access network device performs data transmission with the terminal device according to the context information of the terminal device.
  • the above communication includes uplink communication and/or downlink communication.
  • the method 500 can be applied to the application scenario shown in FIG. 1 or FIG. 2, that is, the first control plane functional entity may be the MME in FIG. 1 or the AMF entity shown in FIG. 2 or The SMF entity, correspondingly, the access network device may be the eNB shown in FIG. 1, or may be the NG-(R) AN device shown in FIG. 2.
  • the method further includes: first identifier information and second identifier information that are sent to the first control plane function entity, where the first identifier information includes the Identification information of a connection between the network access device and the first control plane entity; the second identification information includes identification information of a connection between the access network device and a user plane functional entity.
  • the method further includes the first identifier information and the second identifier information that are sent by the access network device to the first control plane function entity, where the first identifier information is used to identify the a connection between the network access device and the first control plane entity; the second identifier information is used to identify a connection between the access network device and a user plane functional entity.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • Context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to the terminal device. Reduce the delay.
  • FIG. 6 shows a schematic flow chart of a method of an embodiment of the present application.
  • the control plane function entity is an MME entity
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF.
  • the method includes:
  • Step 601 The SCEF entity sends a connection establishment request message to the MME.
  • the MME determines, according to the context release message sent by the terminal device, that the terminal device is switched from the connected state to the idle state or the inactive state. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message may explicitly indicate that the MME establishes a connection for the terminal device, and may also implicitly instruct the MME to establish a connection for the terminal device.
  • the SCEF entity Before sending the foregoing connection establishment request message, the SCEF entity may convert the identifier of the terminal device outside the core network into an identifier of the terminal device inside the core network.
  • connection setup request message may be the first message shown in the embodiment of FIG.
  • the foregoing connection establishment request message may include the indication position for indicating that the S1-MME connection is established and/or the S1-U connection is established, and the predicted location information when the terminal device is converted into the connected state,
  • the ECGI the identification information of the terminal device, and the like, for example, the IMSI
  • the identification information of the terminal device may be an identifier of the terminal device outside the core network, or may be an identifier of the terminal device inside the core network.
  • the name of the connection establishment request message may be used to indicate that the first network connection is established and/or the second connection is established. Therefore, the implicit connection establishment request message includes the terminal device converting to Location information when connected, such as ECGI, and identification information of the terminal device, etc., such as IMSI.
  • the MME After receiving the connection establishment request message sent by the SCEF entity, if the connection establishment request message sent in step 601 is an explicit message, the MME determines the value of the connection identifier bit according to the indication in the connection establishment request message. Start establishing a connection, for example, to indicate that the identity bit value for establishing a connection is 1.
  • the MME finds the corresponding eNB in the relationship list stored locally by the MME according to the predicted location information when the terminal device is converted to the connected state in the connection establishment request message. Therefore, the eNB shown in FIG. 6 is the step of the embodiment of FIG. In the access network device described in 420, the MME predicts that the terminal device will access the eNB when it transitions to the connected state.
  • step 602 the MME sends an initialization context setup request message to the eNB.
  • the initialization context setup request message may carry the context information of the S1-MME connected between the eNB and the MME in the MME, for example, the connection port number of the S1-MME connected in the MME; and the eNB and the S-GW entity
  • the inter-S1-U connects the context information in the S-GW entity, for example, the tunnel number of the S1-U connected to the S-GW entity end. This tunnel number is already pre-existing in the MME when the terminal device attaches to the network.
  • control plane context information of the terminal device includes the context information of the S1-MME connection between the eNB and the MME in the MME;
  • user plane context information of the terminal device includes the S1-U connection between the eNB and the S-GW entity. Context information in the S-GW entity.
  • the initialization context setup request message includes an indication bit that does not immediately establish a DRB between the terminal device and the eNB, and the initialization context setup request message is further used to notify the eNB of context information belonging to the terminal device, where the initial context setup request message is further A resource used to trigger an eNB to allocate a connection to a terminal device.
  • the eNB After receiving the message, the eNB stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the MME, and the eNB and the S-GW.
  • the S1-Us between the entities are connected to the identification information in the S-GW entity, and the network resources are respectively allocated for the foregoing connections.
  • the initial context information request message in the embodiment of FIG. 6 is included in the first identifier information and the second identifier information in the embodiment of FIG. 4.
  • Step 603 The initialization context establishment reply message sent by the eNB to the MME.
  • the initialization context setup reply message may carry the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the eNB, that is, the first identifier information in the embodiment of FIG. 4, and the eNB and the S The identification information gTP-TEID of the S1-U connection between the GWs in the S-GW entity, that is, the second identification information in the embodiment of FIG.
  • the MME After receiving the initialization context setup request reply message, the MME determines that the S1-MME connection establishment of the eNB and the MME is completed.
  • Step 604 The MME sends a bearer modification request message to the S-GW entity.
  • the bearer modification request message may carry the identifier information gTP-TEID of the S1-U connected in the eNB.
  • Step 605 The S-GW entity sends a bearer modification reply message to the MME.
  • the message may be used to confirm the bearer modification request message sent by the receiving step 604, and determine that the S1-U connection establishment between the eNB and the S-GW is completed.
  • Step 606 When the terminal device has uplink data to be sent, establish a connection with the eNB.
  • the connection may include the terminal device establishing an RRC connection and the DRB with the eNB, and the terminal device may send the uplink data to the eNB.
  • Step 607 The terminal device performs uplink data transmission.
  • step 608 the eNB sends a notification message to the MME.
  • the notification message may include an internal ID of the terminal device. It should be understood that the notification message is the third message in the embodiment of FIG. 4, and is used to inform the MME of the location information of the current terminal device and/or the accessed eNB information.
  • step 609 the MME sends a feedback message to the SCEF entity.
  • the feedback message may be used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by the foregoing process.
  • the feedback message may include location information of the current terminal device or eNB information of the access.
  • the first control plane function entity is an SMF entity
  • the second control panel function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is an NEF entity
  • Step 701 The NEF entity sends a terminal device connection establishment request message to the AMF entity, where the message includes location information when the terminal device is converted into the connected state, and identifier information of the terminal device.
  • the AMF determines that the terminal device changes from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the AMF can predict the network element.
  • the prediction information of the terminal device is transmitted to the NEF, and the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF generates a connection establishment request message according to the information.
  • the AMF entity can find the corresponding NG-(R) AN device in the mapping list of the AMF entity stored locally according to the location information when the terminal device in the connection establishment request message is converted into the connection state, and therefore, in FIG. 7
  • the illustrated NG-(R) AN device is the access network device described in step 420 of the embodiment of Figure 4.
  • the setup request message may be the first message in the embodiment of FIG. 4, and the connection setup request message may explicitly indicate that the control plane function entity initiates the establishment process of the N2 connection and/or the N3 connection, or may implicitly Instructing the control plane function entity to initiate the establishment of the N2 connection and/or the N3 connection, that is to say.
  • the first connection is specifically an N2 connection in the embodiment of FIG. 7
  • the second connection is specifically an N3 connection in the embodiment of FIG.
  • step 702 the AMF entity sends an N3 connection notification message to the SMF entity.
  • the N3 connection notification message may be the second message described in the embodiment of FIG. 4.
  • the N3 connection notification message includes the information carried in the connection establishment request message in step 701.
  • the N3 connection notification message is further used to request the SMF entity to return the context information stored by the N3 connection in the SMF entity to the AMF entity.
  • the notification message may be a PDU session activation request message.
  • Step 703 After receiving the message of step 702, the SMF entity sends an N3 connection establishment request message to the AMF entity.
  • the connection establishment request message carries the context information of the N3 connection in the SMF entity, and specifically includes the identifier information of the N3 connection in the SMF entity.
  • Step 704 The N3 connection establishment request message received by the AMF entity is forwarded to the NG-(R) AN device, and the N2 connection establishment response message is sent to the NG-(R) AN device.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the N3 connection establishment request message may include N3 connection endpoint information at the NG-UP entity, and the N2 connection establishment response message includes N2 connection identification information in the AMF entity, etc., it should be understood that the N2 connection establishment response message and/or the N3 connection
  • the setup request message may also include indication information that does not require a wireless connection to be established immediately.
  • the NG-(R)AN may save the identification information of the N3 connection in the NG-UP and the identification information of the N2 connection in the AMF.
  • step 705 the NG-(R) AN device sends an N2 connection setup complete message and an N3 connection setup response message to the AMF entity.
  • the N3 connection setup response message may include N3 connection identifier information at the NG-(R) AN device, and the N2 setup complete message may include N2 connection identifier information at the NG-(R) AN.
  • the AMF After receiving the message sent in step 705, the AMF obtains the identification information of the N2 connection at the NG-(R) AN device, and the N2 connection establishment is completed.
  • step 706 the AMF entity forwards the N3 connection setup response message to the SMF entity.
  • Step 707 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity.
  • the user plane update request message may include context information for the N3 connection in the NG-(R) AN device in the N3 connection setup response message.
  • the NG-UP entity After receiving the message, the NG-UP entity stores information about the NG-(R) AN device used to establish the N3 connection, and the N3 connection establishment is completed.
  • Step 708 The NG-UP entity sends a user plane update response message to the SMF entity, to confirm that the N3 connection establishment is completed.
  • step 709 when the terminal device has uplink data to be sent, the terminal device establishes a wireless connection with the NG-(R) AN device.
  • the wireless connection may include the terminal device establishing an RRC connection and a DRB with the NG-(R) AN device.
  • the terminal device since the terminal device sends the uplink data connection, the terminal device can directly send the uplink data, and step 710, the uplink data is transmitted.
  • the above method further includes steps 711-712.
  • step 711 the NG-(R) AN device sends a notification message to the AMF entity.
  • the notification message is the third message in the embodiment of FIG. 4, and the notification message indicates that the NG-(R)AN has successfully provided services for the terminal device. It should be understood that the notification message includes the identification information of the terminal device.
  • Step 712 The AMF sends a feedback message to the NEF, where the message is used to indicate that the terminal device can perform data transmission by using the N3 and N2 connections established by the foregoing process, where the feedback message includes context information of the terminal device.
  • FIG. 7 shows detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. 7. Moreover, the various steps in FIG. 7 may be performed in a different order than that presented in FIG. 7, and it is possible that not all operations in FIG. 7 are to be performed.
  • FIG. 8 shows a schematic flow chart of a method of an embodiment of the present application.
  • the control plane function entity is an MME
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity.
  • the method includes:
  • Step 801 The SCEF entity sends a connection establishment request message to the MME.
  • the MME determines, according to the context release message sent by the terminal device, that the terminal device changes from the connected state to the idle state or the inactive state. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the message may explicitly indicate that the MME establishes a connection for the terminal device, and may also implicitly instruct the MME to establish a connection for the terminal device.
  • connection setup request message may be the first message shown in the embodiment of FIG.
  • the connection establishment request message includes location information for indicating that the S1-MME connection is established and/or the S1-U connection is established, and the location information when the terminal device is converted to the connected state, for example, ECGI. And identification information of the terminal device, etc., such as IMSI.
  • the name of the foregoing connection establishment request message is used to indicate that the first network connection is established and/or the second connection is established. Therefore, the implicit connection establishment request message includes the terminal device converting to the connection. Location information, such as ECGI, and identification information of the terminal device, such as IMSI.
  • the MME After receiving the connection establishment request message sent by the SCEF entity, if the connection establishment request message sent in step 801 is an explicit message, the MME determines the value of the connection identifier bit according to the indication in the connection establishment request message. Start establishing a connection, for example, to indicate that the identity bit value for establishing a connection is 1.
  • the MME may find the corresponding eNB, that is, the eNB shown in FIG. 8 , in the mapping relationship list stored locally by the MME according to the location information when the terminal device in the connection establishment request message is converted into the connected state.
  • step 802 the MME sends an initialization context setup request message to the eNB.
  • the initialization context setup request message carries the context information of the S1-MME connection between the eNB and the MME in the MME, for example, the connection port number of the S1-MME connected in the MME, and between the MME and the S-GW entity.
  • the S1-U connects the context information in the S-GW entity, for example, the tunnel number of the S1-U connection at the S-GW end. This tunnel number is already pre-existing in the MME when the terminal device attaches to the network.
  • the MME sends the context information of the terminal device to the eNB.
  • the initialization context setup request message includes an indication bit that does not immediately establish a DRB between the terminal device and the eNB.
  • the eNB After receiving the context setup request message, the eNB stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the MME, and the MME and the MME
  • the S1-U between the S-GW entities connects the identification information in the S-GW, and allocates network resources for the S1-U connection and the S1-MME connection, respectively.
  • Step 803 An initialization context setup reply message sent to the MME, where the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the eNB, corresponding to FIG.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB and the MME is completed.
  • Step 804 The MME sends a bearer modification request message to the S-GW entity, where the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the eNB.
  • the bearer modification request message in step 804 includes indication information, which is used to indicate that the S-GW caches the data information of the terminal device delivered by the P-GW entity locally, when the S-GW entity learns the terminal. After the device has successfully connected to the eNB, the cached data information is sent to the eNB.
  • the S-GW entity caches the data information of the terminal device instead of transmitting the data information of the terminal device to the buffer at the eNB by the S-GW, the network load of the eNB can be not increased.
  • Step 805 The S-GW entity sends a bearer modification reply message to the MME, where the message is used to confirm the receiving the bearer modification request message sent by the step 804, and the S1-U connection establishment between the eNB and the S-GW entity is completed.
  • Step 806 Receive downlink data of the terminal device by the P-GW entity.
  • Step 807 The S-GW entity sends the downlink data to the terminal device according to the bearer modification request message received from the MME.
  • Step 808 Send a downlink data notification message to the MME, and the S-GW entity informs the MME that the downlink data of the terminal device needs to be sent.
  • the MME sends a paging message to the terminal device.
  • the terminal device establishes a connection with the eNB.
  • the connection includes the terminal device establishing an RRC connection with the eNB and the DRB.
  • the terminal device can receive the downlink data sent by the eNB.
  • the MME sends a notification message, which indicates that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by the foregoing process.
  • Step 810 The MME sends a feedback message to the SCEF entity, where the feedback message is used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by the foregoing process, where the feedback message includes context information of the terminal device.
  • FIG. 8 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 8 may be performed in a different order than that presented in FIG. 8, and it is possible that not all operations in FIG. 8 are to be performed.
  • FIG. 9 shows a schematic flow chart of a method of an embodiment of the present application.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is an NEF entity
  • Step 901 The NEF entity sends a terminal device connection establishment request message to the AMF entity, where the message includes predicted location information, such as ECGI, and identifier information of the terminal device when the terminal device converts to the connected state.
  • predicted location information such as ECGI
  • the AMF entity determines, according to the context release message sent by the terminal device, that the terminal device transitions from the connected state to the idle state or the inactive state, and further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • the AMF entity finds the corresponding NG-(R) AN device in the mapping relationship list stored locally by the AMF entity according to the predicted location information when the terminal device in the connection establishment request message is converted into the connected state, and therefore, in FIG.
  • the illustrated NG-(R) AN device is the access network device described in step 420 of the embodiment of FIG. 4, and the AMF entity predicts that the terminal device will access the NG-(R) AN device when converted to the connected state.
  • connection establishment request message may explicitly indicate that the control plane function entity initiates the establishment process of establishing an N2 connection and/or establishing an N3 connection, and may also implicitly instruct the control plane function entity to initiate establishment of an N2 connection and/or establish N3.
  • the connection establishment process that is, the first connection in the embodiment shown in FIG. 4 or FIG. 5 is specifically an N2 connection in the embodiment of FIG. 9, and the second connection is specifically an N3 connection in the embodiment of FIG.
  • connection setup message message may explicitly or implicitly instruct the AMF entity to establish a connection for the terminal device.
  • Step 902 The AMF entity sends an N3 connection notification message to the SMF entity.
  • the N3 connection notification message may be the second notification message described in the embodiment of FIG. 4, where the N3 connection notification message is further used to request the SMF entity to return the context information of the N3 connection in the SMF entity to the AM entity F.
  • the notification message may be a PDU session activation request message.
  • Step 903 After receiving the message of step 902, the SMF entity sends an N3 connection establishment request message to the AMF entity, where the connection establishment request message includes the identifier information of the N3 connection in the SMF entity.
  • Step 904 The AMF entity forwards the N3 connection setup request message received from the SMF entity to the NG-(R) AN device, and sends an N2 connection setup response message to the NG-(R) AN device.
  • step 904 the SMF entity sends the context information of the terminal device to the NG-(R) AN device.
  • the N3 connection establishment request message and the N2 connection establishment response message may be one message or two different messages. If two different messages are used, the sequence of sending the messages is not limited.
  • the NG-(R) AN device After receiving the message sent in step 904, the NG-(R) AN device saves the identification information of the N3 connection in the NG-(R) AN and the identification information of the N2 connection in the AMF entity.
  • step 905 the NG-(R) AN device sends an N2 connection setup complete message and an N3 connection setup response message to the AMF entity.
  • the N3 connection setup response message may include the N3 connection identifier information and the like in the NG-(R) AN device; the N2 setup complete message may include the N2 connection identifier information and the like in the NG-(R) AN device.
  • the AMF entity stores the identifier information of the N2 connection in the NG-(R) AN device, and the N2 connection establishment is completed.
  • step 906 the AMF entity forwards the N3 connection setup response message to the SMF entity.
  • Step 907 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity, where the user plane update request message includes the identifier information of the N3 connected to the NG-(R) AN device.
  • the NG-UP entity stores the identifier information of the N3 connected to the NG-(R) AN device, and the N3 connection establishment is completed.
  • the setup response message in step 907 may include indication information, which is used to indicate that the NG-UP caches the data information of the current terminal device delivered by the DN locally, and when the NG-UP learns that the terminal device has succeeded. After connecting to the NG-(R)AN, the cached data information is sent to the NG-(R) AN.
  • Step 908 The NG-UP entity sends a user plane update response message to the SMF entity, to confirm that the N3 connection establishment is completed.
  • step 909 the data network sends downlink data to the NG-UP entity.
  • Step 910 The NG-UP entity caches downlink data sent to the terminal device according to the connection establishment response message received from the SMF entity.
  • step 911 the SMF entity sends a downlink data notification message to the AMF entity.
  • the notification message may be used to notify the AMF entity that the downlink data of the terminal device needs to be transmitted.
  • Step 912 The AMF entity sends a paging message to the terminal device, and the terminal device establishes a wireless connection with the NG-(R) AN device; the NG-(R) AN device sends a downlink data transmission request to the NG-UP entity, and the terminal device performs downlink During data transmission, a wireless connection is established between the terminal device and the NG-(R) AN device, and the NG-UP entity transmits downlink data to the terminal device.
  • step 913 the AMF entity sends a feedback message to the NEF entity.
  • the message can be used to identify the N3 connection and the N2 connection that the terminal device can establish using the foregoing process.
  • Data transmission is performed, and the feedback message includes context information of the terminal device.
  • FIG. 9 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 9 may be performed in a different order than that presented in FIG. 9, and it is possible that not all operations in FIG. 9 are to be performed.
  • FIG. 10 shows a schematic flow chart of a method of an embodiment of the present application.
  • the control plane function entity is an MME entity
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity.
  • the method includes:
  • Step 1001 The SCEF entity sends a connection establishment request message to the MME.
  • the MME determines that the terminal device is switched from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the message may explicitly indicate that the MME establishes a connection for the terminal device, and may also implicitly instruct the MME to establish a connection for the terminal device.
  • the connection establishment request message includes location information for indicating that the S1-MME connection is established and/or the S1-U connection is established, and the location information when the terminal device is converted to the connected state, for example, ECGI. And identification information of the terminal device, etc., such as IMSI.
  • the name of the foregoing connection establishment request message is used to indicate that the first network connection is established and/or the second connection is established. Therefore, the implicit connection establishment request message includes the terminal device converting to the connection. Location information, such as ECGI, and identification information of the terminal device, such as IMSI.
  • the MME After receiving the connection establishment request message sent by the SCEF entity, if the connection establishment request message sent in step 1001 is an explicit message, the MME determines the value of the connection identifier bit according to the indication in the connection establishment request message. Start establishing a connection, for example, to indicate that the identity bit value for establishing a connection is 1.
  • the MME finds the corresponding eNB in the mapping relationship list stored in the MME according to the location information in the connection state in the connection establishment request message, and the eNB is the access network device in step 420 of the embodiment of FIG. 4 . .
  • step 1002 the MME sends an initialization context setup request message to the eNB.
  • the initialization context setup request message carries the connection port number of the S1-MME connection between the eNB and the MME in the MME, and the tunnel of the S1-U connection between the eNB and the S-GW entity in the S-GW entity. Number, this tunnel number is already pre-existing in the MME when the terminal device attaches to the network.
  • the initialization context setup request message may include an indication bit for indicating that the DRB between the terminal device and the eNB is not immediately established.
  • the eNB After receiving the message, the eNB stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the MME, and the eNB and the S-GW.
  • the identification information of the S1-U connection between the entities in the S-GW entity is respectively allocated network resources for the S1-MME connection and the S1-U connection.
  • the initialization context setup request message in the embodiment of FIG. 10 may be the first connection setup request message or the second connection setup request message in the embodiment of FIG.
  • Step 1003 An initialization context setup reply message sent to the MME, where the initialization context establishes a reply
  • the message carries the identification information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB in the eNB, and the identification information gTP- of the S1-U connection between the eNB and the S-GW entity in the eNB.
  • TEID TEID.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB and the MME is completed.
  • the initialization context setup request reply message in the embodiment of FIG. 10 may be the first connection setup request reply message or the second connection setup request reply message in the embodiment of FIG.
  • step 1004 the MME sends a bearer modification request message to the S-GW entity, where the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the eNB.
  • Step 1005 The S-GW entity sends a bearer modification reply message to the MME, where the message is used to confirm the receiving the bearer modification request message sent by the step 604, and the S1-U connection establishment between the eNB and the S-GW entity is completed.
  • bearer modification request message is the update request message in the embodiment of FIG. 4
  • bearer modification reply message is the update response message in the embodiment of FIG. 4.
  • Step 1006 The P-GW entity generates downlink data that is sent to the terminal device.
  • step 1007 the eNB caches downlink data of the terminal device.
  • step 1008 the MME sends a paging message to the terminal device.
  • Step 1009 After receiving the paging message, the terminal device establishes a wireless connection with the eNB.
  • the wireless connection may include an RRC connection and a DRB between the terminal device and the eNB, and the terminal device may receive downlink data sent by the eNB.
  • step 1011 the eNB sends a notification message to the MME.
  • the notification message may be used to inform the MME that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by the foregoing process.
  • step 1012 the MME sends a feedback message to the SCEF entity.
  • the message may be used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by using the foregoing process, where the feedback message includes context information of the terminal device.
  • FIG. 10 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 10 may be performed in a different order than that presented in FIG. 10, and it is possible that not all operations in FIG. 10 are to be performed.
  • Figure 11 shows a schematic flow chart of a method of one embodiment of the present application.
  • the control plane function entity includes an AMF entity and an SMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is an NEF entity.
  • the method includes:
  • Step 1101 The NEF sends a terminal device connection establishment request message to the AMF, where the message includes predicted location information when the terminal device is converted into the connected state, and identifier information of the terminal device.
  • the AMF entity determines, according to the context release message sent by the terminal device, that the terminal device transitions from the connected state to the idle state or the inactive state. Further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • connection establishment request message may explicitly indicate that the control plane function entity initiates the N2 connection establishment process and/or the establishment process of the N3 connection, and may also implicitly instruct the control plane function entity to initiate establishment of the N2 connection and/or establish N3.
  • the establishment process of the connection that is, the first connection in the embodiment shown in FIG. 4 or FIG. 5 is in the embodiment of FIG. Specifically, it is an N2 connection, and the second connection is specifically an N3 connection in the embodiment of FIG.
  • connection setup message message may explicitly or implicitly instruct the AMF entity to establish a connection for the terminal device.
  • Step 1102 The AMF entity sends an N3 connection notification message to the SMF entity, where the message is used to request the SMF entity to return the identifier information of the N3 connection in the SMF entity to the AMF entity.
  • Step 1103 After receiving the message of step 1102, the SMF entity sends an N3 connection establishment request message to the AMF entity, where the connection establishment request message carries the identification information of the N3 connection in the NG-UP entity.
  • Step 1104 The AMF entity forwards the N3 connection setup request message received from the SMF entity to the NG-(R) AN device, and sends an N2 connection setup response message to the NG-(R) AN device.
  • the N3 connection establishment request message and the N2 connection establishment response message may be one message or two different messages. If two different messages are used, the sequence of sending the messages is not limited.
  • N3 connection request message is the second connection request message described in the embodiment of FIG. 4 or FIG. 5
  • the N2 connection request message is the first connection request message described in the implementation of FIG. 4 or FIG.
  • the NG-(R) AN device After receiving the message sent in step 1104, the NG-(R) AN device saves the identification information of the N3 connection in the NG-UP entity and the identifier of the N2 connection in the AMF entity. information.
  • an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes identification information of N3 connected at the NG-(R) AN device, and the like;
  • the N2 setup complete message includes identification information of N2 connected at the NG-(R) AN device, and the like.
  • the AMF entity After receiving the message sent in step 1105, the AMF entity stores the context information of the N2 connected to the NG-(R) AN device, and the N2 connection establishment is completed.
  • step 1106 the AMF entity forwards the N3 connection setup response message to the SMF entity.
  • Step 1107 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity, where the message includes context information of the N3 connected to the NG-(R) AN device.
  • the NG-UP After receiving the message, the NG-UP stores the context information used to establish the N3 connection. At this point, the N3 connection establishment is completed.
  • Step 1108 The NG-UP entity sends a user plane update response message to the SMF entity.
  • the user plane update response message may be used to confirm that the N3 connection establishment is completed.
  • Step 1109 the DN sends the downlink data of the terminal device to the NG-(R) AN device via the NG-UP entity.
  • Step 1110 The NG-(R) AN device caches downlink data of the terminal device sent by the DN.
  • Step 1111 The AMF entity sends a paging message to the terminal device.
  • Step 1112 After the terminal device receives the paging message, the terminal device establishes a wireless connection with the NG-(R) AN device.
  • Step 1113 The NG-(R) AN device sends the buffered downlink data of the terminal device to the terminal device.
  • step 1114 the NG-(R) AN device sends a notification message to the AMF entity.
  • the notification message can be used to inform the AMF entity that the connection has succeeded. It should be understood that the notification message includes identification information of the terminal device.
  • Step 1115 The AMF entity sends a feedback message to the NEF entity, where the message is used to indicate that the terminal device can perform data transmission by using the N3 and N2 connections established by the foregoing process, where the feedback message includes context information of the terminal device.
  • FIG. 11 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG.
  • the various steps in FIG. 11 may be performed in a different order from that presented in FIG. 11, and may not be performed. All the operations in Figure 11. Specific embodiments of the embodiments of the present application are described below in conjunction with specific examples.
  • Figure 12 shows a schematic flow chart of a method of the present application.
  • the control plane function entity is an MME entity
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity
  • eNB1 and eNB2 are both access network devices, as shown in FIG. 12, Methods include:
  • Step 1201 The SCEF entity sends a connection establishment request message to the MME.
  • the MME determines that the terminal device is switched from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the SCEF entity may first convert the identifier of the terminal device outside the core network into the identifier of the terminal device inside the core network.
  • the foregoing message may explicitly indicate that the MME establishes a connection for the terminal device, and may also implicitly instruct the MME to establish a connection for the terminal device.
  • connection setup request message may be the first message shown in the embodiment of FIG.
  • the connection establishment request message includes location information for indicating that the S1-MME connection is established and/or the S1-U connection is established, and the location information when the terminal device is converted to the connected state, for example, ECGI. And identification information of the terminal device, etc., such as IMSI.
  • the MME After receiving the connection establishment request message sent by the SCEF entity, if the connection establishment request message sent in step 1201 is an explicit message, the MME determines whether to establish a connection according to the identifier bit in the connection establishment request message, for example, A connection is established when the flag value indicating that the connection is established is 1.
  • the name of the foregoing connection establishment request message may be used to indicate that the first network connection is established and/or the second connection is established.
  • the implicit connection establishment request message includes location information when the terminal device converts to the connected state, such as ECGI, and identification information of the terminal device, etc., such as IMSI.
  • the MME finds the corresponding eNB1 and eNB2 in the relationship list stored locally by the MME according to the location information when the terminal device in the connection establishment request message is converted into the connection state, and the eNB1 and the eNB2 are the access network in the embodiment of FIG.
  • the device, the MME predicts that the terminal device will access the eNB1 or the eNB2 when it is converted to the connected state.
  • step 1202 the MME sends a mapping identification request to the S-GW entity.
  • the S-GW entity has a one-to-one mapping relationship for a specific connection of the terminal device, that is, the gTP-TEID in one S-GW entity corresponds to the gTP-TEID in one eNB.
  • the gTP-TEID in one S-GW entity corresponds to a gTP-TEID in a plurality of eNBs, that is, a one-to-many mapping. Therefore, the mapping identification request can be used to request the S-GW entity to allocate the gTP-TEID in the S-GW for each of the plurality of eNBs.
  • downlink data For the downlink data, if the eNB's caching method is used, downlink data needs to be sent to multiple eNBs at the same time. Therefore, the data acquired by the S-GW entity from the P-GW entity needs to send downlink data to multiple eNBs.
  • the MME sends an initialization context setup request message to the eNB1, where the initialization context setup request message carries the context information of the S1-MME connected between the eNB1 and the MME in the MME, for example, the connection port of the S1-MME connected in the MME. And the context information of the S1-U connection between the eNB1 and the S-GW entity in the S-GW entity, for example, the tunnel number of the S1-U connected to the S-GW. The tunnel number is already pre-assigned when the terminal device attaches to the network. There is MME.
  • control plane context information of the terminal device includes context information of the S1-MME connection between the eNB1 and the MME in the MME; the user plane context information of the terminal device includes between the eNB1 and the S-GW entity.
  • S1-U connects context information in the S-GW entity.
  • the initialization context setup request message includes an indication bit that does not immediately establish a DRB between the terminal device and the eNB1, and the initialization context setup request message is further used to notify the eNB1 of context information about the terminal device, such as a network capability of the terminal device.
  • the initial context setup request message is also used to trigger the eNB1 to allocate resources required for the terminal device to connect to the terminal device.
  • the eNB1 After receiving the message, the eNB1 stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the eNB1 in the MME, and the MME and the S-GW.
  • the S1-U between the entities connects the identification information in the S-GW entity, and respectively allocates network resources for the foregoing connections.
  • the initialization context setup request message in the embodiment of FIG. 12 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 1204a an initialization context setup reply message sent to the MME, where the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB1 in the eNB1, that is, the embodiment of FIG.
  • the MME may store the ENB-UE-S1AP-ID. At this point, the S1-MME connection establishment of the eNB1 and the MME is completed.
  • step 1205a the MME sends a bearer modification request message to the S-GW entity, where the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the S-GW entity.
  • step 1206a the S-GW entity sends a bearer modification reply message to the MME, which is used to confirm the bearer modification request message sent by the receiving step 604, and the S1-U bearer between the eNB1 and the S-GW entity is established.
  • the MME sends an initialization context setup request message to the eNB2, where the initialization context setup request message carries the identifier information of the S1-MME connection between the eNB2 and the MME in the MME, and the S1-between the eNB2 and the S-GW entity.
  • U is connected to the S-GW entity identification information.
  • the initialization context setup request message includes an indication bit for indicating that the DRB between the terminal device and the eNB2 is not immediately established.
  • the eNB2 After receiving the message, the eNB2 stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the eNB2 in the MME, and the eNB2 and the S-GW.
  • the S1-U between the entities connects the identification information in the S-GW entity, and respectively allocates network resources for the foregoing connections.
  • the initialization context setup request message in the embodiment of FIG. 12 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 1204b an initialization context setup reply message sent to the MME, where the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB2 in the eNB2, that is, the embodiment of FIG.
  • the MME may store the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB2 and the MME is completed.
  • step 1205a the MME sends a bearer modification request message to the S-GW entity, where the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the eNB2.
  • step 1206a the S-GW entity sends a bearer modification reply message to the MME.
  • the message may be used to confirm the bearer modification request message sent by the receiving step 604, and determine that the S1-U connection establishment between the eNB2 and the S-GW entity is completed.
  • step 1207 when the terminal device needs to perform uplink data transmission, a wireless connection with the eNB1 is established.
  • the upper wireless connection may include an RRC connection and a DRB established between the terminal device and the eNB1, and the terminal device may send the uplink data to the eNB1.
  • step 1208 the terminal device performs uplink data transmission.
  • the eNB1 sends a notification message to the MME.
  • the notification message is the third message in the embodiment of FIG. 4, and is used to inform the MME of the location information of the current terminal device or the accessed eNB1 information.
  • Step 1210 The MME sends a feedback message to the SCEF entity, where the message is used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by the foregoing process, where the feedback message includes location information of the current terminal device. Or information of the accessed eNB1.
  • FIG. 12 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 12 may be performed in a different order than that presented in FIG. 12, and it is possible that not all operations in FIG. 12 are to be performed.
  • Figure 13 shows a schematic flow chart of a method of the present application.
  • the control plane function entity is the MME
  • the user plane function entity is the S-GW entity
  • the network capability open function entity is the SCEF entity
  • the eNB1 and the eNB2 are both access network devices, as shown in FIG. include:
  • step 1301 the SCEF entity sends a connection establishment request message to the MME.
  • the MME determines, according to the context release message sent by the terminal device, that the terminal device changes from the connected state to the idle state or the inactive state. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the SCEF Before sending the foregoing message, the SCEF first converts the identifier of the terminal device outside the core network into the identifier of the terminal device in the core network.
  • the connection establishment request message in step 1301 may explicitly indicate that the MME establishes a connection for the terminal device, or may The MME is implicitly instructed to establish a connection for the terminal device.
  • connection setup request message may be the first message shown in the embodiment of FIG.
  • the foregoing connection establishment request message includes an identifier bit for indicating establishment of an S1-MME connection and/or an establishment of an S1-U connection, and location information when the terminal device converts to a connected state, for example,
  • the ECGI, and the identity information of the terminal device, such as the IMSI should be understood that the identifier information of the terminal device may be an identifier of the terminal device outside the core network, or may be an identifier of the terminal device inside the core network.
  • the MME After receiving the connection establishment request message sent by the SCEF entity, if the connection establishment request message sent in step 1201 is an explicit message, the MME determines whether to establish a connection according to the identifier bit in the connection establishment request message, for example, A connection is established when the flag value indicating that the connection is established is 1. Specifically, in the implicit indication manner, the name of the foregoing connection establishment request message may be used to indicate establishing a first network connection and/or establishing a second connection.
  • the implicit connection establishment request message may include location information when the terminal device converts to the connected state, such as ECGI, and identification information of the terminal device, etc., such as IMSI.
  • the MME converts the location information in the connected state according to the location information in the connection establishment request message,
  • the corresponding eNB1 and eNB2 are found in the mapping relationship list stored in the MME.
  • the eNB1 and the eNB2 are the access network devices in the embodiment of FIG. 4, and the MME predicts that the terminal device accesses the eNB1 or the eNB2 when it is converted into the connected state.
  • step 1302 the MME sends a mapping identification request to the S-GW entity.
  • mapping identification request is consistent with the description in the foregoing embodiment, and details are not described herein again.
  • Step 1303a the MME sends an Initialization Context Setup Request message to the eNB1, where the Initialization Context Setup Request message carries the S1-MME connection between the eNB1 and the MME, the identification information in the MME, and the S1-U between the eNB1 and the S-GW entity.
  • the connection identifies the information in the S-GW entity.
  • the initialization context setup request message includes an indication bit for indicating that the DRB between the terminal device and the eNB1 is not immediately established.
  • eNB1 After receiving the message, eNB1 stores the identity information MME-UE-S1AP-ID of the S1-MME connection between the MME and the eNB1 in the MME, and the S1-U connection between the eNB1 and the S-GW entity at the S-GW.
  • the identification information in the entity allocates network resources for the S1-MME connection and the S1-U connection, respectively.
  • the initialization context setup request message in the embodiment of FIG. 13 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 1304a the initialization context setup reply message sent by the eNB1 to the MME.
  • the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB1 in the eNB1, that is, the first identifier information in the embodiment of FIG. 4, and the eNB1 and the S The identification information gTP-TEID of the S1-U between the GWs in the eNB2, that is, the second identification information in the embodiment of FIG.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID. At this point, the S1-MME connection establishment of the eNB1 and the MME is completed.
  • step 1303b the MME sends an Initialization Context Setup Request message to the eNB2.
  • the initialization context setup request message carries the identifier information of the S1-MME connection between the eNB2 and the MME in the MME, and the identifier information of the S1-U connection between the eNB2 and the S-GW entity in the S-GW entity. .
  • the initialization context setup request message includes an indication bit that does not immediately establish a DRB between the terminal device and the eNB2.
  • eNB2 After receiving the message, eNB2 stores the identity information MME-UE-S1AP-ID of the S1-MME connection between the MME and the eNB2 in the MME, and the S1-U connection between the eNB2 and the S-GW entity at the S-GW.
  • the identification information in the entity allocates network resources for the S1-MME connection and the S1-U connection, respectively.
  • the initialization context setup request message in the embodiment of FIG. 13 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 1304b the initialization context setup reply message sent by the eNB2 to the MME.
  • the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the eNB2 in the eNB2, that is, the first identifier information in the embodiment of FIG. 4, and the eNB2 and the S
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB2 and the MME is completed.
  • step 1305 the MME sends a bearer modification request message to the S-GW entity.
  • the bearer modification request message carries the identifier information gTP-TEID that the S1-U connects to the eNB2, and the identifier information gTP-TEID that the S1-U connects to the eNB1.
  • Step 1306 The S-GW entity sends a bearer modification reply message to the MME.
  • the message may be used to confirm the bearer modification request message sent by the receiving step 604.
  • the S1-U connection between the eNB2 and the S-GW entity, and the establishment of the S1-U connection between the eNB1 and the S-GW entity are completed.
  • the bearer modification request message sent by the MME to the S-GW entity carries both the eNB1 and the S-GW entity.
  • step 1307 is performed to establish a wireless connection with the eNB1.
  • the wireless connection may include an RRC connection and a DRB established between the terminal device and the eNB1, and the terminal device may send the uplink data to the eNB1.
  • Step 1308 The terminal device sends uplink data.
  • Step 1309 eNB1 sends a notification message to the MME.
  • the notification message may be the third message in the embodiment of FIG. 4, and is used to inform the MME of the location information of the current terminal device or the information of the accessed eNB1.
  • step 1310 the MME sends a feedback message to the SCEF entity.
  • the message may be used to indicate that the terminal device can perform data transmission by using the S1-MME and the S1-U established by using the foregoing process, where the feedback message includes location information of the current terminal device or eNB1 information accessed.
  • FIG. 12 and FIG. 13 shows a schematic flow chart of the terminal device transitioning to the connected state when the terminal device has the uplink data transmission requirement in the 4G system, and the terminal device has the downlink data transmission requirement
  • the process of establishing a connection may be the same as steps 1201 to 1206b, or may be the same as steps 1301 to 1306b, and will not be described again for the sake of brevity.
  • FIG. 13 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 13 may be performed in a different order than that presented in FIG. 13, and it is possible that not all operations in FIG. 13 are to be performed.
  • Figure 14 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is an NEF entity
  • Step 1401 The NEF entity sends a terminal device connection establishment request message to the AMF entity.
  • the AMF entity determines that the terminal device transitions from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information. The message includes predicted location information when the terminal device is converted to the connected state, and identifier information of the terminal device.
  • the setup request message may be the first message in the embodiment of FIG. 4, and the connection setup request message may explicitly indicate that the control plane function entity initiates the establishment process of establishing an N2 connection and/or establishing an N3 connection, or may be hidden. Instructing the control plane function entity to initiate the establishment of the N2 connection and/or the establishment of the N3 connection, that is, the diagram In the embodiment shown in Fig. 4, the first connection is specifically an N2 connection in the embodiment of Fig. 14, and the second connection is specifically an N3 connection in the embodiment of Fig. 14.
  • connection setup message may explicitly or implicitly instruct the AMF entity to establish a connection for the terminal device.
  • step 1402 the AMF entity sends an N3 connection notification message to the SMF entity.
  • the N3 connection notification message may be the second message described in the embodiment of FIG. 4, where the N3 connection notification message includes the information carried in the connection establishment request message in step 1401.
  • Step 1403 After receiving the message of step 1402, the SMF entity sends an N3 connection establishment request message to the AMF entity.
  • the connection establishment request message carries the context information of the N3 connection in the SMF entity, and specifically includes the identifier information of the N3 connection in the SMF entity. It should be understood that, in the context information of the terminal device carried in the connection establishment request message, the SMF entity or the AMF entity predicts that the access network device accessed when the terminal device is converted into the connected state is (R) AN1 device or (R) AN2. device.
  • Step 1404a the AMF entity forwards the N3 connection setup request message received from the SMF entity to the (R) AN1 device, and sends an N2 connection setup response message to the (R) AN1 device.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the user plane context information of the terminal device includes context information of the N3 connection in the SMF; the control plane context information of the terminal device includes context information of the N2 connection in the AMF entity.
  • the (R) AN1 after receiving the message sent in step 1404a, at this time, the (R) AN1 device saves information for establishing an N3 connection, for example, N3 is connected to the identification information in the NG-UP entity, and is used to establish N2.
  • the connected information for example, holds the identification information of the N2 connection in the AMF entity.
  • an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes context information connected to the (3) AN1 device with N3, including identity information of the N3 connection at the (R) AN1 device, and the like; the N2 setup complete message includes the N2 connection in the (R) AN1 device. Context information, including identification information of N3 connected at (R) AN1, and the like.
  • step 1404b the AMF forwards the N3 Connection Setup Request message received from the SMF to the (R) AN2 device, which also sends an N2 Connection Setup Response message to the (R) AN2 device.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the AN2 device receives the message sent in step 1404a, at this time, the (R) AN2 device saves context information for establishing an N3 connection, for example, N3 connects the identification information in the NG-UP entity, and is used for Establish context information of the N2 connection, for example, save the identification information of the N2 connection in the AMF entity.
  • an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes context information that is connected to the N3 in the (R) AN2, including identity information of the N3 connection in the (R) AN2 device, and the like;
  • the N2 setup complete message includes the N2 connection to the (R) AN2 device.
  • Context information in the middle including identification information of N3 connected in (R) AN2, and the like.
  • the AMF After receiving the message sent in step 1405a, the AMF stores the context information of the N2 connected to the (R) AN2 device, and the N2 connection establishment is completed.
  • the AMF entity forwards the N3 connection setup response message to the SMF entity, the N3
  • the connection setup response message carries context information in which the N3 is connected to the (R) AN2 device and/or the (R) AN1 device.
  • the user plane context information of the UE includes context information in which the N3 is connected in the (R) AN2 device and/or the (R) AN1 device.
  • Step 1407 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity.
  • the user plane update request message may include context information in which the N3 is connected to the (R)AN2 and/or the (R)AN1 in the N3 connection setup response message.
  • the NG-UP After receiving the message, the NG-UP stores the context information of the N3 connected to the (R) AN1 device and/or stores the context information of the N3 connected to the (R) AN2 device, and the N3 connection establishment is completed.
  • Step 1408 The NG-UP entity sends a user plane update response message to the SMF entity.
  • the user plane update response message may be used to confirm that the N3 connection establishment is completed.
  • the step 1406 may be respectively refined into two N3 connection setup response messages sent by the AMF entity to the SMF entity, where the two N3 connection setup response messages respectively include N3 connection identifier information at the (R) AN2 device, and N3.
  • the order of execution of the two N3 setup response messages in the embodiment of the present application is not limited. That is to say, the two N3 connection response messages are actually used to establish a connection between the (R) AN1 device and the user plane functional entity and (R) the connection between the AN2 device and the user plane functional entity.
  • step 1407 may be respectively refined into two user plane update request messages sent by the SMF entity to the NG-UP entity, where the two user plane update request messages respectively carry the identifier information of the N3 connected to the (R) AN2 device.
  • the order of execution of the two user plane update request messages in the embodiment of the present application is not limited.
  • step 1408 can be separately refined into two user plane update response messages sent by the NG-UP entity to the SMF entity, and the two user plane update response messages are respectively used to confirm (R) AN1 device and user plane functional entity.
  • the connection between the (R) AN2 device and the user plane function entity is completed, and the order of execution of the two user plane update response messages in the embodiment of the present application is not limited.
  • connection between the (R) AN1 device and the first control plane entity is completed, and the connection between the (R) AN1 device and the user plane functional entity is completed; similarly, the (R) AN2 device and the first The connection between the control plane entities is established, and the connection between the (R) AN2 device and the user plane functional entity is completed.
  • the terminal device when the terminal device needs to perform uplink data transmission, the terminal device establishes a wireless connection with the access network device, for example, when the (R) AN1 device converts the terminal device into a connected state, the access network actually accessed. When the device is in use, then the terminal device will establish a wireless connection with the (R) AN1 device.
  • the terminal device can transmit the uplink data and perform the uplink data transmission.
  • the (R) AN1 device may send a notification message to the AMF entity, it being understood that the notification message is
  • the third message in the embodiment of FIG. 4 is used to notify the AMF entity that the (R) AN1 device has successfully provided services for the terminal device. It should be understood that the notification message includes the identification information of the terminal device.
  • the AMF entity sends a feedback message to the NEF entity, and the message may be used to indicate that the terminal device can perform data transmission by using the N3 and N2 connections established by the foregoing process, where the feedback message includes context information of the terminal device.
  • Steps 909 to 913 are similar, or are similar to the steps 1109 to 1115 shown in FIG. 11, and are not described herein again.
  • FIG. 14 shows detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 14 may be performed in a different order than that presented in FIG. 14, and it is possible that not all operations in FIG. 14 are to be performed.
  • Figure 15 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is NEF
  • the source access device (Source AN) device accessed by the terminal device terminal device before being in the idle state or the inactive state is shown in the embodiment, and the terminal device is determined to be connected to the connected state according to the access network information of the terminal device.
  • Target Access device (Target AN) that may be connected.
  • the method includes:
  • Step 1501 The NEF entity sends a connection establishment request message to the AMF entity.
  • the AMF entity determines that the terminal device changes from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, then the AMF may The access network information determines a target access network (Target AN) device of the terminal device.
  • Target AN target access network
  • Step 1502a the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message may be used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • Step 1503a The source access network device sends the context information of the terminal device to the target access network device.
  • step 1504a the target access network device sends a transmission success notification message to the AMF entity.
  • the transmission success notification message may be used to notify the AMF entity that the context information of the terminal device has been received.
  • Another alternative way for the target access network device to obtain context information for the terminal device may be replaced by steps 1502b-1504b.
  • Step 1502b the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the AMF entity.
  • step 1503b the source access network device sends a context transfer message to the AMF entity.
  • the context transmission message carries context information of the terminal device.
  • Step 1504b the AMF entity forwards the context information of the terminal device obtained from the source access network device to the target access network device.
  • the context information of the terminal device may include information for establishing an N3 connection, such as identity information of the N3 connection in the NG-UP entity, and information for establishing an N2 connection, for example, identity information in the AMF entity.
  • the Target RAN device After receiving the message sent in step 1506, the Target RAN device saves the Target RAN device.
  • the information for establishing the N3 connection for example, the identification information of the N3 connection in the NG-UP entity, and the information for establishing the N2 connection, for example, the identification information of the N2 connection in the AMF entity.
  • an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes information connected to the Target RAN device with N3, including identification information of the N3 connection at the Target RAN device, and the like;
  • the N2 Setup Complete message contains information of the Target RAN device related to the N2 connection, including the N3 connection. Identification information at the Target RAN device, etc.
  • the AMF entity After receiving the message sent in step 1505b, the AMF entity stores the context information of the N2 connection in the Target RAN device, and the N2 connection establishment is completed.
  • step 1506 the AMF entity forwards the N3 Connection Setup Response message to the SMF entity.
  • Step 1507 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity.
  • the user plane update request message includes context information for the N3 connection in the Target RAN device in the N3 connection setup response message.
  • the NG-UP After receiving the message, the NG-UP stores information about the Target RAN device used to establish the N3 connection, and the N3 connection establishment is completed.
  • Step 1508 The NG-UP entity sends a user plane update response message to the SMF entity, to confirm that the N3 connection establishment is completed.
  • step 1509 is performed to establish a wireless connection
  • step 1510 is performed to perform uplink data transmission.
  • step 1511d the Target AN device sends a context release request message to the Source AN device.
  • the context release request message is used to indicate that the source AN device deletes the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1512d the Target AN device sends a notification message to the AMF entity.
  • the notification message may be the third message in the embodiment of FIG. 4, and the notification message is used to notify the AMF entity that the Target AN device has successfully provided services for the terminal device, and it should be understood that the notification message includes the identifier of the terminal device. information.
  • step 1513d the AMF entity sends a feedback message to the NEF entity.
  • the message may be used to indicate that the terminal device can perform data transmission by using the N3 and N2 connections established by the foregoing process, where the feedback message includes context information of the terminal device.
  • steps 1511d-1513d may also be replaced by steps 1511e-1513e.
  • step 1511e the Target AN device sends a context release request message to the AMF entity.
  • the context release request message may be used to request the AMF entity to forward the context release request message to the source AN device. It should also be understood that another function of the context release request message is to notify the AMF entity that the Target AN device has successfully succeeded as the terminal device.
  • the service is provided.
  • the notification message includes identifier information of the terminal device.
  • the AMF entity performs step 1512e, and the AMF sends a context release request message to the source AN device, where the context release request message is used to instruct the source AN device to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1513e the AMF entity sends a feedback message to the NEF entity.
  • the message may be used to identify the number of N3 and N2 connections that the terminal device can establish using the foregoing process.
  • the feedback message includes context information of the terminal device.
  • the AMF entity determines, according to the context release message sent by the terminal device, that the terminal device transitions from the connected state to the idle state or the inactive state, and further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • Figure 16 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an MME
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity
  • the terminal device terminal device is shown in the embodiment of the present application.
  • a source access network device for example, a Source eNB
  • a target access network that may be accessed when the terminal device that is predicted according to the access network information of the terminal device is converted into a connected state Device (for example, Target eNB).
  • the method includes:
  • step 1601 the SCEF entity sends a connection establishment request message to the MME.
  • the AMF entity determines that the terminal device changes from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, the MME may
  • the access network information determines a target access network device (Target eNB) of the terminal device.
  • step 1602a the MME sends a context transmission notification message to the source access network device.
  • the context transmission notification message may be used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • Step 1603a the source access network device sends the context information of the terminal device to the target access network device.
  • step 1604a the target access network device sends a transmission success notification message to the MME.
  • the transmission success notification message may be used to notify the MME that the context information of the terminal device has been received.
  • Another alternative way for the target access network device to obtain context information for the terminal device may be replaced by steps 1602b-1604b.
  • Step 1602b The MME sends a context transmission notification message to the source access network device, where the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the MME.
  • Step 1603b The source access network device sends a context transmission message to the MME, where the context transmission message carries context information of the terminal device.
  • step 1604b the MME sends an Initialization Context Setup Request message to the Target eNB.
  • the initialization context setup request message carries the context information of the S1-MME connected between the Target eNB and the MME in the MME, for example, the identifier information of the S1-MMW connected in the MME, and between the MME and the S-GW entity.
  • S1-U connects the context information in the S-GW entity, for example, the identity information of the S1-U connection at the S-GW end.
  • the initialization context setup request message includes an indication bit that does not immediately establish a DRB between the terminal device and the Target eNB, and the initialization context setup request message is further used to notify the target eNB about the terminal device.
  • Context information such as the network capability of the terminal device, the tunnel number of the S1-U connection in the S-GW entity, and the initial context setup request message is also used to trigger the Target eNB to allocate a connection for the terminal device. resource of.
  • the Target eNB After receiving the message, the Target eNB stores the information carried in the initialization context setup request message, for example, the identifier information MME-UE-S1AP-ID of the S1-MME connected between the MME and the Target eNB in the MME, and the eNB and the S - Identification information of the S1-U connection between the GW entities in the S-GW entity.
  • the initial context setup request message in the embodiment of FIG. 16 includes the first identifier information or the second identifier information in the embodiment of FIG. 4.
  • Step 1605b an initialization context setup reply message sent to the MME.
  • the initialization context setup reply message may carry the identifier information ENB-UE-S1AP-ID of the S1-MME connected between the MME and the Target eNB in the Target eNB, that is, the first identifier information in the embodiment of FIG. 4, and the eNB.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB and the MME is completed.
  • Step 1606 The MME sends a bearer modification request message to the S-GW entity.
  • the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the eNB.
  • Step 1607 The S-GW entity sends a bearer modification reply message to the MME, where the message is used to confirm the bearer modification request message sent by the step 604, and the S1-U connection establishment between the Target eNB and the S-GW entity is completed.
  • step 1608 is performed to establish a wireless connection
  • step 1609 is performed to perform uplink data transmission.
  • step 1610d the TargeteNB sends a context release request message to the Source eNB.
  • the context release request message is used to indicate that the source eNB deletes the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1611d the TargeteNB sends a notification message to the MME.
  • the notification message may be the third message in the embodiment of FIG. 4, and the notification message is used to inform the MME that the Target eNB has successfully provided services for the terminal device. It should be understood that the notification message may include the identification information of the terminal device. .
  • step 1612d the MME sends a feedback message to the SCEF entity.
  • the message may be used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by using the foregoing process, where the feedback message includes context information of the terminal device.
  • steps 1610d-1612d may also be replaced by steps 1610e-1612e.
  • step 1610e the Target eNB sends a context release request message to the MME.
  • the Context Release Request message may be used to request the MME to forward the Context Release Request message to the Source eNB. It is also understood that another function of the Context Release Request message is to inform the MME that the Target eNB has successfully provided services for the terminal device.
  • the notification message includes identifier information of the terminal device.
  • the MME performs step 1611e, and the MME sends a context release request message to the source eNB, where the context release request message is used to instruct the source eNB to delete the stored context information of the terminal device, which is beneficial to save network resources.
  • step 1612e the MME sends a feedback message to the SCEF entity.
  • the message may be used to indicate that the terminal device can perform data transmission by using the S1-MME connection and the S1-U connection established by using the foregoing process, where the feedback message includes context information of the terminal device.
  • FIG. 16 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. 16. Moreover, the various steps in FIG. 16 may be performed in a different order than that presented in FIG. 16, and it is possible that not all operations in FIG. 16 are to be performed.
  • Figure 17 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an SMF
  • the second control panel function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is an NEF entity
  • the application The source access device (Source AN) device that the terminal device terminal device accesses before being in an idle state or an inactive state is shown in the embodiment, and the terminal device that is predicted according to the access network information of the terminal device is converted into a connected state.
  • Target Access device (Target AN) that may be connected.
  • the method includes:
  • Step 1701 The NEF entity sends a connection establishment request message to the AMF entity.
  • the AMF entity determines that the terminal device changes from the connected state to the idle state or the inactive state according to the context release message sent by the terminal device. Further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is predicted to be converted into a connected state. Further, the NEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, then the AMF entity may The access network information determines a target access network (Target AN) device of the terminal device.
  • Target AN target access network
  • Step 1702a the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • Step 1703a The source access network device sends the context information of the terminal device to the target access network device.
  • Step 1704a the target access network device sends a transmission success notification message to the AMF entity.
  • the transmission success notification message may be used to notify the AMF entity that the context information of the terminal device has been received.
  • Another alternative way for the target access network device to obtain context information for the terminal device may be replaced by steps 1702b-1704b.
  • Step 1702b the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message may be used to notify the source access network device to send the context information of the terminal device to the AMF entity.
  • step 1703b the source access network device sends a context transfer message to the AM entity F.
  • the context transmission message carries context information of the terminal device.
  • Step 1704b the AMF entity forwards the N3 connection setup request message received from the SMF entity to the Target RAN device, and sends an N2 connection setup response message to the Target RAN device.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the source RAN device After receiving the message sent by step 1704b, the source RAN device saves information for establishing an N3 connection, for example, N3 is connected to the identity information of the Target RAN device, and is used to establish an N2 connection.
  • the information for example, holds the identification information of the N2 connection in the AMF entity.
  • step 1705b an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes information that is connected to the N3 in the Target RAN device, including N3 connection identifier information at the Target RAN device, and the like;
  • the N2 setup complete message includes information of the Target RAN device related to the N2 connection, including N3 is connected to the identification information at the Target RAN device, and the like.
  • the AMF After receiving the message sent by step 1705b, the AMF stores the context information of the N2 connection in the Target RAN device, and the N2 connection establishment is completed.
  • step 1706 the AMF entity forwards the N3 connection setup response message to the SMF entity.
  • Step 1707 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP.
  • the user plane update request message may include context information for the N3 connection in the NG-(R)AN in the N3 connection setup response message.
  • the NG-UP entity After receiving the message, the NG-UP entity stores information about the Target RAN device used to establish the N3 connection, and the N3 connection establishment is completed.
  • Step 1708 the NG-UP entity sends a user plane update response message to the SMF entity.
  • the user plane update response message may be used to confirm that the N3 connection establishment is completed.
  • step 1708 is performed, and the DN transmits the downlink transmission to the NG-UP entity.
  • Step 1709 The NG-UP entity caches downlink data of the terminal device.
  • Step 1710 The NG-UP sends a paging message to the terminal device by using the Target RAN device.
  • step 1711 the terminal device establishes a wireless connection with the Target RAN device.
  • Step 1712 The SMF entity sends downlink data of the terminal device to the Target RAN device.
  • the Target RAN device sends downlink data to the terminal device.
  • step 1714d the Target RAN device sends a context release request message to the Source RAN device.
  • the context release request message is used to instruct the source RAN device to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1714d may also be replaced by steps 1714e-1715e.
  • step 1714e the Target RAN device sends a context release request message to the AMF entity.
  • the context release request message is used to request the AMF entity to forward the context release request message to the source RAN device. It should also be understood that another function of the context release request message is to notify the AMF entity that the Target RAN device has successfully provided the terminal device.
  • the service optionally, includes the identification information of the terminal device in the notification message.
  • the AMF entity performs step 1715e, and the AMF entity sends a context release request message to the source RAN device, where the context release request message is used to instruct the source RAN device to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • FIG. 17 shows detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Further, the respective steps in FIG. 17 may be performed in a different order from that presented in FIG. 17, and it is possible that not all operations in FIG. 17 are to be performed.
  • Figure 18 shows a schematic flow chart of a method of the present application.
  • the interface function entity is an MME
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity
  • the terminal device terminal device is in an idle state or an inactive state in the embodiment of the present application.
  • step 1801 the SCEF entity sends a connection establishment request message to the MME.
  • the MME determines, according to the context release message sent by the terminal device, that the terminal device changes from the connected state to the idle state or the inactive state. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, the MME may
  • the access network information determines a target access network device (Target eNB) of the terminal device.
  • step 1802a the MME sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • Step 1803a the source access network device sends the context information of the terminal device to the target access network device.
  • step 1804a the target access network device sends a transmission success notification message to the MME.
  • the transmission success notification message may be used to notify the MME that the context information of the terminal device has been received.
  • Another alternative way for the target access network device to obtain context information for the terminal device may be replaced by steps 1802b-1804b.
  • step 1802b the MME sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the MME.
  • step 1803b the source access network device sends a context transfer message to the MME.
  • the context transmission message carries context information of the terminal device.
  • step 1804b the MME sends an Initialization Context Setup Request message to the TargeteNB.
  • the initialization context setup request message carries the context information of the S1-MME connected between the Target eNB and the MME in the MME, for example, the identifier information of the S1-MME connected in the MME, and the eNB and the S-GW entity.
  • S1-U connects context information in the S-GW entity, such as identification information that the S1-U is connected to in the S-GW entity.
  • the Target eNB After receiving the message, the Target eNB stores the information carried in the initialization context setup request message, for example, the identifier information MME-terminal device-S1AP-ID of the S1-MME connected between the MME and the Target eNB in the MME, and the eNB and the eNB The S1-U between the S-GW entities connects the identification information in the S-GW entity.
  • the initialization context setup request message in the embodiment of FIG. 18 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 1805b an initialization context setup reply message sent to the MME.
  • the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected to the Target eNB between the MME and the Target eNB, that is, the first identifier information in the embodiment of FIG. 4, and the Target The identification information gTP-TEID of the S1-U connection between the eNB and the S-GW entity in the Target eNB, That is, the second identification information in the embodiment of FIG.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB and the MME is completed.
  • Step 1806 the MME sends a bearer modification request message to the S-GW entity.
  • the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected in the Target eNB.
  • Step 1807 The S-GW entity sends a bearer modification reply message to the MME.
  • the message may be used to confirm the bearer modification request message sent by the receiving step 604, and the S1-U connection establishment between the Target eNB and the S-GW entity is completed.
  • Step 1808 the DN sends downlink data to the S-GW entity.
  • Step 1809 The S-GW entity caches downlink data sent by the DN.
  • the S-GW entity informs the MME of the downlink data of the terminal device by using a Downlink Data Notification (DNN).
  • DNN Downlink Data Notification
  • the MME sends a paging message to the terminal device.
  • step 1811 the terminal device establishes a wireless connection with the Target eNB, and further, performs steps 1812 and 1813 to perform downlink data transmission.
  • step 1814d the Target eNB sends a context release request message to the Source eNB.
  • the context release request message is used to indicate that the source eNB deletes the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1814d may also be replaced by steps 1814e-1815e.
  • step 1814e the Target eNB sends a context release request message to the MME.
  • the Context Release Request message is used to request the MME to forward the Context Release Request message to the Source eNB. It should also be understood that another function of the Context Release Request message is to inform the MME that the Target eNB has successfully provided services for the terminal device.
  • the notification message includes the identification information of the terminal device.
  • the MME performs step 1815e, and the MME sends a context release request message to the source eNB, where the context release request message is used to instruct the source eNB to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • FIG. 18 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. 18. Moreover, the various steps in FIG. 18 may be performed in a different order than that presented in FIG. 18, and it is possible that not all operations in FIG. 18 are to be performed.
  • Figure 19 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an SMF entity
  • the second control plane function entity is an AMF entity
  • the user plane function entity is an NG-UP entity
  • the network capability open function entity is NEF
  • the present application In the embodiment, a source access network (Source RAN) device that is accessed when the terminal device is in the connected state, and a possible target access network when the terminal device is converted into the connected state according to the access network information of the terminal device are shown.
  • Target RAN source access network
  • the method includes:
  • step 1901 the NEF entity sends a connection establishment request message to the AMF entity.
  • the AMF entity determines, according to the context release message sent by the terminal device, that the terminal device transitions from the connected state to the idle state or the inactive state, and further, the AMF entity can pass the prediction.
  • the network element sends the prediction information of the terminal device to the NEF entity, where the prediction information includes a location and a time at which the terminal device is converted into a connected state, and further, the NEF entity generates a connection establishment according to the foregoing information. Ask for news.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, then the AMF entity may The access network information determines a target access network (Target RAN) device of the terminal device.
  • Target RAN target access network
  • Step 1902a the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • Step 1903a The source access network device sends the context information of the terminal device to the target access network device.
  • Step 1904a the target access network device sends a transmission success notification message to the AMF entity.
  • the transmission success notification message may be used to notify the AMF entity that the context information of the terminal device has been received.
  • Another alternative way for the target access network device to obtain context information for the terminal device may be replaced by steps 1902b-1904b.
  • Step 1902b the AMF entity sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the AMF entity.
  • Step 1903b the source access network device sends a context transfer message to the AMF entity.
  • the context transmission message carries context information of the terminal device.
  • Step 1904b the AMF entity forwards the N3 connection setup request message received from the SMF entity to the Target RAN device, and sends an N2 connection setup response message to the Target RAN device.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the N3 connection establishment request message includes context information about the NG-UP entity stored in the SMF entity, including PDU Session identification information, N3 connection endpoint information at the NG-UP, PDU session quality service, and the like.
  • the N2 connection setup response message includes context information of the N2 connection in the AMF entity, including an endpoint of the N2 connection in the AMF entity, and the like. It is worth noting that the message contains the "No need to establish a wireless connection immediately" flag.
  • the Target RAN device After receiving the message sent in step 1904b, the Target RAN device saves information for establishing an N3 connection, such as N3 connection information in the Target RAN device, and information for establishing an N2 connection, for example, saving the N2 connection in the AMF. Identification information in .
  • step 1905b an N2 connection setup complete message and an N3 connection setup response message are sent to the AMF entity.
  • the N3 connection setup response message includes information that is connected to the N3 in the Target RAN device, including the N3 connection identifier information in the Target RAN device, and the N2 setup complete message includes the N3 connection identifier information in the Target RAN device.
  • the AMF entity After receiving the message sent in step 1905b, the AMF entity stores the context information of the N2 connection in the Target RAN device, and the N2 connection establishment is completed.
  • step 1906 the AMF entity forwards the N3 Connection Setup Response message to the SMF entity.
  • Step 1907 After receiving the N3 connection setup response message, the SMF entity sends a user plane update request message to the NG-UP entity.
  • the user plane update request message includes context information for the N3 connection in the Target RAN device in the N3 connection setup response message.
  • the NG-UP entity After receiving the message, the NG-UP entity stores an identification letter for establishing an N3 connection in the Target RAN device. At this point, the N3 connection is established.
  • Step 1908 the NG-UP sends a user plane update response message to the SMF entity, to confirm that the N3 connection establishment is completed.
  • the DN transmits the downlink transmission to the NG-UP entity.
  • Step 1909 the NG-UP transmits the downlink data of the terminal device to the Target RAN device.
  • the Target RAN device caches downlink data of the terminal device.
  • Step 1911 The NG-UP entity transmits downlink data of the terminal device to the Source RAN device.
  • Step 1912 The Source RAN device caches downlink data of the terminal device.
  • both the Source RAN device and the Target RAN device cache data to reduce the target RAN device prediction inaccurate to the terminal due to the first control plane function entity, so that the terminal device cannot send the Target RAN device.
  • the case of receiving downlink data For example, in the case where the terminal device is still in the Source RAN range, the downlink data of the terminal device may still be received from the Source RAN device.
  • step 1913 the terminal device establishes a wireless connection with the Target RAN device.
  • Step 1914 The Target RAN device sends the downlink data of the terminal device to the terminal device.
  • step 1916d the Target RAN device sends a context release request message to the Source RAN device.
  • the context release request message is used to instruct the source RAN device to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • step 1916d may also be replaced by steps 1916e-1917e.
  • Step 1916e The Target RAN device sends a context release request message to the AMF entity, where the context release request message is used to request the AMF to forward the context release request message to the Source RAN device, and it should be understood that another function of the context release request message is to notify The AMF entity, the Target RAN device has successfully served the terminal device.
  • the notification message includes the identification information of the terminal device.
  • the AMF entity performs step 1917e, and the AMF entity sends a context release request message to the source RAN device, where the context release request message is used to instruct the source RAN device to delete the context information of the stored terminal device, which is beneficial to save network resources.
  • FIG. 19 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Further, the respective steps in FIG. 19 may be performed in a different order from that presented in FIG. 19, respectively, and it is possible that not all operations in FIG. 19 are to be performed.
  • Figure 20 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an MME
  • the user plane function entity is an S-GW entity
  • the network capability open function entity is a SCEF entity
  • the terminal device terminal device is shown in the embodiment of the present application.
  • a source access network device (Source eNB) that is accessed before being in an idle state or an inactive state
  • a target access network device that may be accessed when the terminal device predicted according to the access network information of the terminal device is converted into a connected state ( Target eNB).
  • the method includes:
  • step 2001 the SCEF entity sends a connection establishment request message to the MME.
  • the MME determines, according to the context release message sent by the terminal device, that the terminal device is switched from the connected state to the idle state or the inactive state. Further, the MME can predict the network element. And transmitting the prediction information of the terminal device to the SCEF entity, where the prediction information includes predicting a location and a time when the terminal device converts to the connected state, and further, the SCEF entity generates a connection establishment request message according to the foregoing information.
  • the connection establishment request message carries the access network information of the terminal device, for example, the ECGI carrying the terminal device in the connection establishment request message, and the identification information of the terminal device or the identification information of the access network device, the MME may
  • the access network information determines a target access network device (Target eNB) of the terminal device.
  • step 2002a the MME sends a context transmission notification message to the source access network device.
  • the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the target access network device.
  • the context notification message carries the identifier information of the target access network device.
  • step 2003a the source access network device sends the context information of the terminal device to the target access network device.
  • step 2004a the target access network device sends a transmission success notification message to the MME.
  • the transmission success notification message may be used to notify the MME that the context information of the terminal device has been received.
  • Another alternative manner in which the target access network device obtains the context information of the terminal device may be replaced by steps 2002b-2004b.
  • step 2002b the MME sends a context transmission notification message to the source access network device, where the context transmission notification message is used to notify the source access network device to send the context information of the terminal device to the MME.
  • step 2003b the source access network device sends a context transmission message to the MME, where the context transmission message carries the context information of the terminal device.
  • step 2004b the MME sends an Initialization Context Setup Request message to the TargeteNB.
  • the initialization context setup request message carries the context information of the S1-MME connected between the Target eNB and the MME in the MME, for example, the identifier information of the S1-MME connected in the MME, and between the Target eNB and the S-GW entity.
  • the S1-U connects context information in the S-GW entity, such as the identification information that the S1-U is connected in the S-GW entity.
  • the initialization context setup request message in the embodiment of FIG. 20 is included in the first identifier information or the second identifier information in the embodiment of FIG.
  • Step 2005b an initialization context setup reply message sent to the MME.
  • the initialization context setup reply message carries the identifier information ENB-UE-S1AP-ID of the S1-MME connected to the Target eNB between the MME and the Target eNB, that is, the first identifier information in the embodiment of FIG. 4, and the Target The identification information gTP-TEID of the S1-U between the eNB and the S-GW entity in the Target eNB, that is, the second identification information in the embodiment of FIG.
  • the MME After receiving the initialization context setup request reply message, the MME stores the ENB-UE-S1AP-ID, and the S1-MME connection establishment of the eNB and the MME is completed.
  • step 2006 the MME sends a bearer modification request message to the S-GW entity, where the bearer modification request message carries the identifier information gTP-TEID of the S1-U connected to the Target eNB.
  • step 2007, the S-GW entity sends a bearer modification reply message to the MME.
  • the message may be used to confirm the bearer modification request message sent by the receiving step 604, and the S1-U bearer between the Target eNB and the S-GW is established.
  • step 2008 the DN transmits the downlink data of the terminal device to the S-GW entity.
  • step 2009 the S-GW entity sends downlink data of the terminal device to the Target eNB.
  • step 2010 the Target eNB buffers downlink data of the terminal device that is sent by the S-GW entity.
  • step 2011 the S-GW sends the downlink data of the terminal device to the Source eNB.
  • Step 2012 The Source eNB buffers downlink data of the terminal device that is sent by the S-GW entity.
  • step 2014 the Source eNB initiates paging to the terminal device.
  • step 2015 the terminal device establishes a wireless connection with the Target eNB.
  • step 2017d the Target eNB sends a context release request message to the Source eNB.
  • the context release request message is used to indicate that the source eNB deletes the context information of the stored terminal device, which is beneficial to save network resources.
  • step 2017d can also be replaced by steps 2017e-2018e.
  • step 2017e the Target eNB sends a context release request message to the MME.
  • the Context Release Request message is used to request the MME to forward the Context Release Request message to the Source eNB. It should also be understood that another function of the Context Release Request message is to inform the MME that the Target eNB has successfully provided services for the terminal device.
  • the notification message includes the identification information of the terminal device.
  • the MME will perform step 2018e, and the MME sends a context release request message to the source eNB, where the context release request message is used to instruct the source eNB to delete the stored context information of the terminal device, which is beneficial to save network resources.
  • FIG. 20 illustrates detailed steps or operations of an embodiment of the present application, but these steps or operations are merely examples, and other embodiments of the present application may also perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 20 may be performed in a different order than that presented in FIG. 20, and it is possible that not all operations in FIG. 20 are to be performed.
  • target access network device described in the foregoing embodiments of FIG. 15 to FIG. 20 refers to an access network device that predicts possible access when the terminal device converts to the connected state.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • Figure 21 shows a schematic flow chart of a method of the present application.
  • the first control plane function entity is an SMF2 entity
  • the second control plane function entity is an AMF entity
  • the user plane function entity is an NG-UP1 entity, an NG-UP2 entity, and a next generation user plane anchor point (NG- UP anchor) entity
  • the network capability open functional entity is an NEF entity, as shown in FIG. 21, the method includes:
  • Step 2101 The NEF entity sends a terminal device terminal connection establishment request message to the AMF entity, where the connection establishment request message includes location information when the terminal device resumes the connection state, and identifier information of the terminal device terminal device, that is, the connection establishment request message.
  • the context information of the terminal device is included.
  • the setup request message may be the first message in the embodiment of FIG. 4, and the connection setup request message may explicitly indicate that the control plane function entity initiates the establishment process of establishing an N2 connection and/or establishing an N3 connection, or may be hidden.
  • the control plane function entity is instructed to initiate the establishment of the N2 connection and/or the establishment of the N3 connection. That is, the first network connection in the embodiment shown in FIG. 4 is specifically the N2 connection in the embodiment of FIG. 21, and the second The network connection is specifically an N3 connection in the embodiment of Fig. 21.
  • connection setup message may explicitly or implicitly instruct the AMF entity to establish a network connection for the terminal device terminal device.
  • the AMF entity After receiving the connection establishment request message, the AMF entity selects the SMF1 as the first control plane function entity according to the local policy and the location information when the terminal device resumes the connection state.
  • Step 2102 The AMF entity sends an N3 connection notification message to the SMF1, where the N3 connection notification message is a figure.
  • the N3 connection notification message includes the information carried in the connection establishment request message of step 2101.
  • the notification message may be a PDU session establishment request message, where the message carries identifier information for indicating connection pre-establishment, and can be used to request the SMF2 to send an N3 connection establishment request message to the NG-UP2.
  • Step 2103a after the SMF1 entity receives the N3 connection notification message of step 2102, the terminal device acquires the terminal device context information of the terminal device.
  • the SMF1 selects the NG-UP2 entity as the user plane function entity of the terminal device according to the local policy and the location information when the terminal device resumes the connection state, and the NG-UP1 is the user plane function entity when the terminal device is in the connected state last time.
  • the SMF1 entity creates context information for the N3 connection for the terminal device.
  • the context information of the N3 connection includes the identification information of the N3 connection in the NG-UP2, and the N9 is connected to the identification information at the NG-UP2.
  • IP Internet Protocol
  • the SMF1 entity or the AMF entity predicts that the access network device accessed when the terminal device resumes the connection state is the (R) AN device.
  • the SMF1 entity sends a user context request message to the NG-UP2, where the user context request message carries the context information of the N3 connection in the SMF1 entity.
  • the identification information including the N3 connection in the NG-UP2 is included, and the N9 stored in the SMF2 is connected to the identification information at the NG-UP anchor.
  • the N9 connection is a connection between the NG-UP entity and the NG-UP anchor entity. Since there may be multiple NG-UP entities connected to the NG-UP anchor entity, the N9 connection is used to transmit the multiple NG- Data between UP entities.
  • the NG-UP2 entity After receiving the message sent in step 2104a, the NG-UP2 entity saves the information for establishing the N9 connection, for example, the identification information of the N9 connected to the NG-UP anchor entity. And information for establishing an N3 connection, for example, saving the identification information of the N3 connection in the NG-UP2 entity.
  • step 2104b the NG-UP2 entity sends a user context response message to the SMF1 entity.
  • Step 2105 The SMF1 sends an N3 connection change request to the NG-UP anchor entity, where the connection change request message includes the N9 connection identifier information at the NG-UP2.
  • the N3 connection change request is further used to notify the NG-UP1 entity that the NG-UP anchor does not delete the information, for example, the NG-UP1 entity in the N3 connection change request used to notify the NG-UP anchor entity not to delete the NG-UP1 entity.
  • the information has a flag value of 1.
  • the terminal device connection establishment request message sent by the NEF entity to the AMF entity in step 2101 includes the terminal at the same time. Access network device information when the device was last connected.
  • the terminal device connection establishment request message sent by the NEF entity to the AMF entity includes the access network device information (for example, (R) AN2 device information) when the terminal device is in the connected state last time, the core network device
  • the access network device information for example, (R) AN2 device information
  • the core network device The steps of the interaction process for establishing user context information with the (R) AN2 device device are similar to steps 702 through 708 in FIG. 7, or similar to steps 902 through 908 in FIG. 9, or with step 1102 in FIG.
  • the steps up to 1108 are similar and will not be described here.
  • the N3 Connection Change Request message includes context information about NG-UP2 stored in the SMF1 entity, the context information including endpoint information of the N3 connection at the NG-UP2 entity, the IP address of the NG-UP2, and the like.
  • step 2106 the NG-UP anchor entity sends an N3 connection change response message to the SMF1 entity. At this point, the N9 connection is established.
  • Step 2107 The SMF1 entity sends an N3 connection establishment request message to the AMF entity, where the message includes context information created by the SMF1 entity for the N3 connection.
  • the N3 connection establishment request message includes the SMF1 entity transmitting the PDU session identifier of the terminal device to the NG-(R) AN device, the quality of service description of the PDU session, and the identity information of the N3 connection in the NG-UP2 entity.
  • Step 2108 the AMF entity forwards the N3 connection setup request message received from the SMF1 entity to the NG-(R) AN device, and the AMF entity also sends an N2 connection setup response message to the NG-(R) AN entity.
  • the N3 connection setup request message and the N2 connection setup response message may be one message or two different messages. If there are two different messages, the order of sending the messages is not limited in this application.
  • the N3 Connection Setup Request message includes information about the NG-UP2 entity stored in the SMF1 entity, the information including PDU session identification information, N3 connection endpoint information at the NG-UP2 entity, PDU session quality service, and the like.
  • the N2 connection setup response message includes information of the AMF entity, including the endpoint of the N2 connection at the AMF entity, and the like. It is worth noting that the message contains the "No need to establish a wireless connection immediately" flag.
  • the NG-(R)AN After receiving the message sent in step 2108, the NG-(R)AN saves the information for establishing the N3 connection, for example, the identification information of the N3 connection at the NG-UP2, and the Establish information about the N2 connection, for example, save the identification information of the N2 connection in the AMF.
  • the NG-(R) AN device sends an N2 connection setup complete message and an N3 connection setup response message to the AMF entity.
  • the N3 connection setup response message includes information connected to the N3 in the NG-(R)AN, including the N3 connection identifier information at the NG-(R) AN device, and the like;
  • the N2 setup complete message includes the N2 connection Information of the NG-(R) AN device, including identification information of the N2 connected to the NG-(R) AN device, and the like.
  • the AMF After receiving the message sent in step 2109, the AMF stores the context information of the N2 connected to the NG-(R) AN device, and the N2 connection establishment is completed.
  • the AMF entity forwards the N3 connection setup response message to the SMF1 entity, where the N3 connection setup response message carries the context information of the N3 connection in the NG-(R) AN device.
  • Step 2111 After receiving the N3 connection setup response message, the SMF1 entity sends a user plane update request message to the NG-UP2 entity.
  • the user plane update request message may include context information that is used in the N3 connection setup response message for the N3 connection to be created for the terminal device in the NG-(R) AN device.
  • the NG-UP2 entity After receiving the message, the NG-UP2 entity stores the terminal device context information in the NG-(R) AN device for establishing the N3 connection, and the N3 connection establishment is completed.
  • Step 2112 The NG-UP entity sends a user plane update response message to the SMF1 entity, where the user plane update response message can be used to confirm that the N3 connection establishment is completed.
  • connection between the NG-(R) AN device and the first control plane entity is completed, and the connection between the NG-(R) AN and the user plane functional entity is completed.
  • Step 2113 The SMF2 sends a terminal device IP address prompt message to the AMF, where the message includes an IP address assigned by the SMF2 to the terminal device.
  • the identifier information indicating that the AS does not need to delete the IP address of the original terminal device is included.
  • Step 2114 The AMF sends a terminal device IP address prompt message to the NEF, where the message includes an IP address assigned by the SMF2 to the terminal device.
  • the identifier information indicating that the AS does not need to delete the IP address of the original terminal device is included.
  • step 2115 when the terminal device needs to perform uplink data transmission, the terminal device establishes a wireless network connection with the target access network device, for example, when the (R)AN device is the target access network device, then the terminal The device will establish a wireless network connection with the (R)AN device.
  • the terminal device can transmit the uplink data and perform the uplink data transmission.
  • Step 2116 it should be understood that if the (R) AN device is the target access network of the terminal device, the (R) AN device may send a notification message to the AMF entity, which should be understood to be the third in the embodiment of FIG.
  • the message is used to inform the AMF entity that the (R) AN device has successfully provided services for the terminal device. It should be understood that the notification message includes the identification information of the terminal device.
  • the AMF entity sends a notification message to the SMF1 entity, where the message is used by the (R)AN to successfully provide the terminal device with the identification information of the terminal device.
  • Step 2117 The SMF1 entity sends a session termination request message to the NG-UP1 entity, to notify the NG-UP1 entity to delete the context information of the stored terminal device. After the NG-UP1 entity deletes the stored terminal device context information, NG-UP1 sends a session termination response message to the SMF1 entity.
  • the transmission process with the target access network device is similar to steps 909 to 913 shown in FIG. 9 or similar to the steps 1109 to 1115 shown in FIG. Let me repeat.
  • FIG. 22 is a schematic structural block diagram of a network device according to an embodiment of the present invention.
  • FIG. 22 is a schematic block diagram of a core network device 2200 according to an embodiment of the present invention. It should be understood that the core network device 2200 can perform the various steps performed by the first control plane functional entity in the methods of FIGS. 4 through 21, and to avoid repetition, it will not be described in detail herein.
  • the core network device 2200 includes:
  • the acquiring unit 2210 is configured to acquire access network information of the terminal device, where the terminal device is in an idle state or an inactive state.
  • the sending unit 2220 is configured to send the context information of the terminal device to the access network device according to the access network information acquired by the obtaining unit 2210.
  • the actions performed by the acquisition unit 2210 may be implemented by a processor, and the actions performed by the transmitting unit 2220 may be implemented by the transceiver under the control of the processor.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • FIG. 23 is a schematic structural block diagram of an access network device according to an embodiment of the present invention.
  • FIG. 23 is a schematic block diagram of an access network device 2300 according to an embodiment of the present invention. It should be understood that the access network device 2300 can perform the steps performed by the access network device in the methods of FIGS. 4 to 21, and to avoid repetition, it will not be described in detail herein.
  • the access network device 2300 includes:
  • the receiving unit 2310 is configured to receive, by the first control plane function entity, the uplink information of the terminal device, where the terminal device is in an idle state or an inactive state.
  • the communication unit 2320 is configured to perform communication with the terminal device according to the context information of the terminal device received by the receiving unit 2310.
  • the actions performed by the acquisition unit 2310 may be implemented by a processor, and the actions performed by the transmitting unit 2320 may be implemented by a transceiver under the control of the processor.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • FIG. 24 is a block diagram showing the schematic structure of an apparatus of one embodiment of the present invention.
  • FIG. 24 shows a device 2400 provided by an embodiment of the present invention. It should be understood that the apparatus 2400 is capable of performing the various steps performed by the first control plane functional entity in the methods of FIGS. 4-21, which are not described in detail herein in order to avoid redundancy.
  • Device 2400 includes:
  • a memory 2410 configured to store a program
  • transceiver 2420 configured to communicate with other devices
  • the processor 2430 is configured to execute a program in the memory 2410, and the processor 2430 is respectively connected to the memory 2410 and the transceiver 2420, and is configured to execute the instruction stored by the memory 2410 to execute the instruction. Perform the following steps:
  • the processor 2430 is configured to obtain, by using the transceiver 2420, access network information of the terminal device, where the terminal device is in an idle state or an inactive state, and send the foregoing to the access network device according to the access network information. Context information of the terminal device.
  • the device 2400 may be specifically the first control plane functional entity in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the first control plane functional entity in the foregoing method embodiment.
  • the first control plane function entity in the embodiment of the present application sends the access network information corresponding to the access network information to the access network device corresponding to the access network information in advance by acquiring the access network information of the terminal device.
  • the context information of the terminal device when the terminal device has a data transmission requirement, that is, when the terminal device needs to switch from the idle state to the connected state or from the inactive state to the connected state, there is no need to wait for the context information transmission process of the terminal device, which is beneficial to reduce Hours of delay.
  • FIG. 25 is a block diagram showing the schematic structure of an apparatus of one embodiment of the present invention.
  • FIG. 25 shows an apparatus 2500 provided by an embodiment of the present invention. It should be understood that the apparatus 2500 is capable of performing the various steps performed by the access network device in the methods of FIGS. 4-20, which are not described in detail herein in order to avoid redundancy.
  • Apparatus 2500 includes:
  • a memory 2510 configured to store a program
  • a transceiver 2520 configured to communicate with other devices
  • processor 2530 for executing a program in the memory 2510, the processor 2530 being respectively connected to the memory 2510 and the transceiver 2520 for executing the instruction stored by the memory 2510 to execute the instruction Perform the following steps:
  • the processor 2530 is configured to receive, by using the transceiver 2520, the context information of the terminal device that is sent by the first control plane function entity, where the terminal device is in an idle state or an inactive state; according to the context information of the terminal device, The terminal device communicates.
  • the device 2500 may be specifically the access network device in the foregoing embodiments 4 to 21, and may be used to perform various steps and/or processes corresponding to the access network device in the foregoing method embodiments.
  • 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 invention 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 invention 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 invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本申请实施例提供一种通信方法，包括：当终端设备处于空闲态或非激活态时，第一控制面功能实体获取所述终端设备的接入网信息；所述第一控制面功能实体向所述接入网信息对应的接入网设备发送所述终端设备的上下文信息。因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。

Description

通信方法及其设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法及其设备。
背景技术
终端设备的功率容量通常是受限的，因此在终端设备没有数据传输的情况下，将终端设备由无线资源控制连接(Radio Resource ControlConnected，RRC Connected)状态转换为无线资源控制连接空闲(Radio Resource Control Idle，RRC-Idle)状态或者无线资源控制连接空闲非激活(inactive)状态，以降低终端设备的功耗。其中，无线资源控制连接状态简称为连接态，无线资源控制连接空闲状态简称为空闲态，无线资源控制连接空闲非激活状态简称为非激活状态。
在一种情况下，当处于空闲态的终端设备发送或接收数据时，会恢复由连接态转换为空闲态时释放的一些资源，例如，重新建立承载，恢复连接等。虽然空闲态的引入可以降低终端设备的功耗，但终端设备从空闲态转换为连接态时，网络设备需要获取终端设备的上下文信息，因此会带来额外的时延。
在另外一种情况下，当终端设备处于非激活态时，如果从非激活态转换为连接态时，网络设备也同样需要获取终端设备的上下文信息，同样会带来额外的时延。
因此，在终端设备从空闲态或非激活态转换为连接态时如何降低时延，是目前亟待解决的技术问题。
发明内容
本申请实施例提供一种通信方法，能够有利于降低终端设备转换为连接态的时延。
第一方面，提出一种通信方法，包括：第一控制面功能实体获取终端设备的接入网信息，其中，所述终端设备处于空闲态或非激活态；所述第一控制面功能实体根据所述接入网信息，向接入网设备发送所述终端设备的上下文信息。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
结合第一方面，在第一方面的第一种可能的实现方式中，所述终端设备的上下文信息包括：所述终端设备的用户面上下文信息；以及所述终端设备的控制面上下文信息。
可选地，作为本申请一个实施例，所述终端设备的上下文信息可以只包括所述终端设备的控制面上下文信息。
应理解，控制面上下文信息和用户面上下文信息可以携带在同一条消息中，也可以携带在不同的消息中，当控制面上下文信息和用户面上下文信息携带在不同的消息中时，本申请实施例不限定上述两条消息执行的先后顺序。
结合第一方面及其上述实现方式，在第一方面的第二种可能的实现方式中，所述方法还包括：所述第一控制面功能实体接收所述接入网设备发送的第一标识信息和第二标 识信息；其中，所述第一标识信息用于标识所述接入网设备与所述第一控制面实体之间的连接；所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接因此，第一控制面功能实体通过获取接入网设备发送的第一标识信息和第二标识信息，能够根据该第一标识信息预先建立接入网设备与第一控制面功能实体之间的第一连接，以及根据该第二标识信息预先建立接入网设备与用户面功能实体之间的第二连接，当终端设备具有数据传输需求时，可以直接利用建立好的连接进行通信，而不用等待建立连接的过程，有利于减小时延。
结合第一方面及其上述实现方式，在第一方面的第三种可能的实现方式中，所述方法还包括：向所述用户面功能实体发送更新请求消息，所述更新请求消息包括所述第二标识信息；接收所述用户面功能实体发送的更新响应消息。
也就是说，第一控制面功能实体通过向用户面功能实体发送更新请求消息，能够使得用户面功能实体获得接入网设备的第二标识信息，因而能够建立与接接入网设备之间的第二连接。
结合第一方面及其上述实现方式，在第一方面的第四种可能的实现方式中，所述方法还包括：所述第一控制面功能实体获取所述终端设备的接入网信息，包括：所述第一控制面功能实体获取所述终端设备的接入网信息，包括：所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体接收所述终端设备的接入网信息；或者，所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体接收所述终端设备的位置预测信息，并根据所述位置预测信息获取所述终端设备的接入网信息。
应理解，当第一控制面功能实体从第二控制面功能实体接收终端设备的接入网信息或终端设备的位置预测信息时，第二控制面功能实体也是通过接收网络能力开放功能实体发送的消息获得的终端设备的接入网信息或终端设备的位置预测信息。
结合第一方面及其上述实现方式，在第一方面的第五种可能的实现方式中，所述终端设备处于非激活态时，所述方法还包括：所述第一控制面功能实体从所述终端设备当前所驻留的接入网设备中获取所述终端设备的上下文信息。
结合第一方面及其上述实现方式，在第一方面的第六种可能的实现方式中，所述方法还包括：所述第一控制面功能实体获取所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的的接入网设备的信息。
应理解，该接入网信息中包括可以接入网设备的标识信息和/或小区标识信息。
结合第一方面及其上述实现方式，在第一方面的第七种可能的实现方式中，所述方法还包括：所述第一控制面功能实体向所述网络能力开放功能实体发送反馈消息，其中，所述反馈消息包括所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的接入网设备的信息。
因此，网络能力开放功能实体能够根据控制面功能实体发送的反馈信息，进一步优化预测该终端设备转换为连接态时可能接入的接入网设备，提高预先建立连接的准确性。
第二方面，提出一种通信方法，包括：接入网设备接收第一控制面功能实体发送的终端设备的上下文信息，其中，所述终端设备处于空闲态或非激活态；所述接入网设备根据所述终端设备的上下文信息，与所述终端设备进行数据传输。
结合第二方面，在第二方面的第一种可能的实现方式中，所述方法还包括：向所述 第一控制面功能实体发送的第一标识信息和第二标识信息，其中，所述第一标识信息包括所述接入网设备与所述第一控制面实体之间的连接的标识信息；所述第二标识信息包括所述接入网设备与用户面功能实体之间的连接的标识信息。
结合第二方面及其上述实现方式，在第二方面的第二种可能的实现，所述方法还包括：所述接入网设备向所述第一控制面功能实体发送所述终端设备的当前位置信息或所述接入网设备的信息。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
第三方面，提供了一种核心网设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该核心网设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面，提供了一种接入网设备，用于执行上述第二方面或第方面的任意可能的实现方式中的方法。具体地，该接入网设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。第五方面，提供了一种核心网设备，该核心网设备包括：收发器、存储器、处理器和总线系统。其中，该收发器、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制收发器接收和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种接入网设备，包括：收发器、存储器、处理器和总线系统。其中，该收发器、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制收发器接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第八方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
附图说明
图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是本发明另一个实施例的装置的示意性结构框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
在本申请实施例中，终端设备可以指用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备等。
进一步地，在本申请实施例中，接入网设备可以是用于与终端设备进行通信的网络设备，例如，可以是GSM系统或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者该基站可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络侧设备，例如下一代无线接入网(Next Generation Radio Access Network，NG-(R)AN)等。
首先，本申请结合图1和图2介绍本申请实施例应用场景的示意性图。具体地，本申请实施例涉及的网元如下：
业务能力服务器(Service Capability Server，SCS)：用于业务逻辑的实现，向用户提供应用层的信息，应用服务器(Application Server，AS)：用于业务逻辑的实现，向用户提供应用层的信息。
业务能力开放功能(Service Capability Exposure Function，SCEF)实体：用于认证授权，支持外部实体发现网络、策略执行、跨运营商的记账、与外部实体互联的相关功能 等。
网络开放功能(Network Exposure Function，NEF)实体：用于安全地向外部开放由第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)网络功能提供的业务和能力。
接入管理功能(Access and Mobility Management Function，AMF)实体：主要功能包括无线接入网络控制面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等。
会话管理功能(Session Management Function，SMF)实体：用于会话管理，IP地址分配和管理，选择可管理用户面功能，策略控制和收费功能接口的终结点，下行数据通知等。
下一代用户面(Next Generation User Plane，NG-UP)实体：用于分组路由和转发，用户面数据的服务质量(Quality of Service，QoS)处理等。
移动管理实体(Mobility Management Entity，MME)：用于核心网的控制面管理，主要功能包括移动性管理、会话管理、接入控制、网元选择、存储用户上下文等。
演进的移动服务位置中心(Evolved Serving Mobile Location Center，E-SMLC)实体：提供与终端设备位置相关的信息等。
应理解，本申请中RRC-connected态也可以简称为RRC连接态或连接态，RRC-idle态也可以额简称为RRC空闲态或空闲态，本申请不做限定。
还应理解，本申请中描述的RAN、NG-(R)AN和(R)AN均指5G网络中的网络侧设备，在具体实施例的描述中，它们之间可以相互替代。图1示出了本申请一个实施例的应用场景的示意性架构图。如图1所示，示出了在3GPP系统中应用业务能力开放架构的下的4G系统。首先，SCS/AS发送的数据会通过API接口传输到SCEF。此后，SCEF与HSS交互以验证SCS/AS是否被授权，之后，SCEF通过T6a接口将数据发送至MME，用于进行网络的相关控制与优化。
在图1中，归属用户服务器(Home Subscriber Server，HSS)用于存储用户签约信息的服务器，主要负责管理用户的签约数据及移动用户的位置信息。
服务网关(Serving GateWay，S-GW)属于用户面功能实体，负责用户面数据路由处理，终结处于空闲态的终端设备的下行数据发送；管理和存储终端设备的系统结构演进(System Architecture Evolution，SAE)上下文信息，是3GPP系统内部用户面的锚点。
分组数据网网关(Packet Data Network Gateway，P-GW)为负责终端设备接入分组数据网(Packet Data Network，PDN)的网关，为终端设备分配IP地址，同时是3GPP和非3GPP接入系统的移动性锚点。
策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)功能实体包含策略控制决策和基于流计费控制的功能。
演进的通用陆地无线接入网络(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)包括eNB，为终端设备接入网络提供无线资源，可以提供更高的上下行速率，更低的传输延迟和更加可靠的无线传输。
其中，S1-MME是eNB和MME之间的控制面接口，用于控制终端设备和网络之间的承载和连接，以及非接入层(Non-access Stratum,NAS)消息的发送；S1-U是eNB和S-GW间用户面的参考点，提供eNB和S-GW间的用户面的分组数据单元通过隧道的传 输；LTE-Uu是终端设备和eNB之间的无线连接接口。
应理解，上述连接的名称仅仅是示例性的，本申请实施例不限于此。
图2示出了本申请另一实施例的应用场景的示意性架构图。如图2所示，在5G系统中，SCS/AS发送的数据会传输到络开放功能(Network Exposure Function，NEF)实体。此后，NEF实体与认证服务功能(AUthentication Server Function，AUSF)实体交互以验证SCS/AS是否被授权，之后，NEF将数据发送至AMF与SMF，用于进行网络的相关控制与优化。
在图2中，NEF实体用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
下一代用户面(Next Generation User Plane，NG-UP)实体主要功能包括分组路由和转发，用户面数据的服务质量(Quality of Service，QoS)处理等。
下一代(无线)接入网络Next Generation-((Radio)Access Network，(R)AN)为终端的接入提供网络资源。
AUSF实体主要功能包括用户鉴权等。
数据网络(Data Network，DN)用于传输数据的网络，例如互联网(Internet)等。
其中，N2接口为(R)AN和核心网控制面的参考点，用于NAS消息的发送等；N3接口为(R)AN和NG-UP实体之间用户面的参考点，用于传输用户面的数据等。
应理解，上述连接的名称仅仅是示例性的，本申请实施例不限于此。
图3示出了终端设备的状态转换关系示意图。如图3所示，终端设备进行网络附着，从空闲态转换为连接态。之后，在一些情况下，例如终端设备长时间不进行数据传输时，从连接态转换为空闲态，当终端设备具有数据传输需求时，从空闲态转换为连接态。在另外一些情况下，例如，当终端设备不移动(如水表、电表或温度、湿度传感器等)，或终端设备以很低速率移动时，终端设备可能会转换为非激活(inactive)态，之后当终端设备具有数据传输需求时，从非激活态转换为连接态。
以LTE系统为例，如果终端设备处于非激活态，那么eNB会释放终端设备与eNB之间的RRC连接和数据无线承载(Data Radio Bearer，DRB)，而不会释放位于eNB和MME之间的S1-MME连接，以及位于eNB与S-GW之间的S1-U连接。因此，在终端设备从inactive态转换为连接态时，仅仅需要建立RRC连接和DRB，相比于空闲态转换为连接态的过程，缩短了终端设备与MME之间建立连接的时延，以及缩短了终端设备与S-GW之间建立连接的时延。
然而，当终端设备从非激活态转换为连接态时，如果终端设备接入目标基站，那么源基站与MME或源基站与S-GW之间保持的连接将无法为终端设备继续提供服务，因此，终端设备通过接入的目标基站将与MME或S-GW建立连接，以传输终端设备的数据。
例如，当终端设备移出源基站的覆盖范围时，终端设备接入目标基站，该目标基站与源基站之间直接连接(例如存在X2接口)，那么目标基站向源基站请求终端设备的上下文信息，之后源基站将终端设备上下文信息发送给目标基站。此后，目标基站向MME发送路径切换请求，之后，目标基站向源基站发送上下文连接释放消息。这时，终端设备成功接入目标基站。因此，对于源基站和目标基站之间存在直接连接的情况下，源基站需要一直保留终端设备的上下文信息，以便于目标基站与终端设备建立连接时，目标基站可以从源基站处获取终端设备的上下文信息，因此带来不必要的资源消耗。
再例如，当终端设备移动出源基站的覆盖范围时，若目标基站与源基站之间不存在直接连接，则目标基站向MME发送终端设备的上下文信息，之后MME向源基站转发终端设备的上下文信息；MME接收到源基站发送的终端设备的上下文信息响应之后，将终端设备的上下文信息转发至目标基站；此后，目标基站向MME发送路径切换请求，并等待确认信息之后，目标基站向源基站发送终端设备上下文连接释放信息。这时，终端设备成功接入新的基站。因此，在这种方案中，网络设备与终端设备之间的交互信令数量多，网络负载大，建立连接的时延大。
基于上述问题，本申请实施例提供一种通信的方法及其设备，能够在终端设备具有数据传输需求之前，预先下发终端设备的上下文信息，进一步地，能够提前建立网络设备之间的连接，因此，减少了终端设备等待上下文信息传输所需的时间，进而减小建立连接的时延，提高用户体验。
图4示出了本申请一个实施例的方法的示意性流程图。如图4所示，该方法400包括：
步骤410，第一控制面功能实体获取终端设备的接入网信息，其中，终端设备处于空闲态或非激活态；
步骤420，第一控制面功能实体根据接入网信息，向接入网设备发送终端设备的上下文信息。
具体地，第一控制面实体可以为下列中的任意一种：MME、AMF实体、SMF实体，应理解，具备与AMF实体或SMF实体相似功能的实体都落入本申请实施例的范围，本申请不做限定。此外，AMF实体或SMF实体可以为独立的物理设备，也可以与其它功能实体集成在同一个物理设备上，不予限定。
应理解，方法400可以应用于图1或图2示出的应用场景，也就是说，第一控制面功能实体可以为图1中的MME，也可以为图2中示出的AMF实体或SMF实体，相应地，接入网设备可以为图1中示出的eNB，也可以为图2中示出的NG-(R)AN。
其中，接入网信息可以包括小区信息，例如E-UTRAN小区全球标识符(E-UTRAN Cell Global Identifier，ECGI)、基站标识等。
在步骤420中，第一控制面功能实体可以根据接入网信息确定该接入网信息对应的接入网设备，并向该接入网设备发送终端设备的上下文信息。
还应理解，接入网设备可以为一个，也可以为多个，该接入网设备可以为预测网元所预测的终端设备转换为连接态时接入的接入网设备。其中，预测网元可以为NEF或SCEF等功能实体，本申请不做限定。
具体地，第一控制面功能实体获取终端设备的接入网信息的方式可以为接收预测网元发送的接入网信息。
应理解，第一控制面功能实体获取接入网信息的方式也可以为第一控制面功能实体主动向其它网元发起请求，以获得接入网信息等，本申请不做限定。
也就是说，当终端设备处于空闲态或非激活态时，终端设备没有接入任何接入网设备，在这种情况下，当终端设备与某个接入网设备之间具有数据传输需求时，首先终端设备需要建立与该接入网设备之间的连接，随后第一控制面功能实体再向该接入网设备发送终端设备的上下文信息，也就是说，当第一控制面功能实体向接入网设备发送终端设备的上下文信息之后，终端设备才能与接入网设备之间进行数据传输，那么终端设备 在开始进行数据传输之前，需要等待第一控制面功能实体向接入网设备发送终端设备的上下文信息的过程，因此存在较大的时延。
还应理解，当第一控制面功能实体从终端设备当前驻留的接入网设备中获取终端设备的上下文信息时，并且，根据步骤420中的接入网信息确定的接入网设备与终端设备当前驻留的接入网设备是同一接入网设备时，可以不向当前驻留的接入网设备发送该终端设备的上下文信息。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
可选地，上述方法还包括：
第一控制面功能实体建立与接入网设备之间的第一连接，该第一连接用于在接入网设备与第一控制面功能实体之间传输终端设备的控制信令，其中，第一控制面功能实体为MME或AMF实体；用户面功能实体建立与接入网设备之间的第二连接，该第二连接用于在接入网设备与用户面功能实体之间传输终端设备的数据，此时，该终端设备仍处于空闲态或非激活态，其中，用户面功能实体为S-GW实体或NG-UP实体。
例如，在图1示出的应用场景下，接入网设备为eNB，第一控制面功能实体为MME，那么该第一连接可以为eNB与MME之间的S1-MME连接，第二连接可以为连接eNB和S-GW实体之间的S1-U连接；而在图2示出的应用场景下，接入网设备为NG-(R)AN，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，那么该第一连接可以为NG-(R)AN与AMF实体之间的N2连接，第二连接可以为NG-(R)AN和NG-UP实体之间的N3连接。应理解，在某些场景下，该第一连接也可以用于传输数据，本申请不做限定。
可选地，作为本申请一个实施例，终端设备的上下文信息包括：所述终端设备的用户面上下文信息；以及所述终端设备的控制面上下文信息。
其中，用户面上下文信息可以包括下列信息中的至少一项：第二连接的QoS信息，例如5G系统中PDU会话的QoS信息，4G系统中网络承载的QoS信息；第二连接在用户面功能实体中的标识信息，例如，4G系统中S1-U连接在S-GW中的通用分组无线服务隧道协议隧道端点标识(General Packet Radio Service Tunnelling Protocol Tunnel Endpoint Identifier，gTP-TEID)，又例如5G系统中N3连接在NG-UP中的隧道信息(Tunnel Info)，其中，用户面功能实体包括S-GW、NG-UP等。
其中，控制面上下文信息可以包括下列信息中的至少一项：第一连接的安全上下文信息，例如第一连接的密钥等；还可以包括第一连接在控制面功能实体中的标识信息，例如，4G系统中S1-MME连接在MME中的MME-UE-S1AP-ID，5G系统中的N2连接在AMF实体中的AMF信令连接标识(AMF signaling connection identification)等；控制面上下文信息还可以包括：切换限制(handover restriction)信息等。
可选地，作为本申请一个实施例，所述终端设备的上下文信息可以只包括所述终端设备的控制面上下文信息。
可选地，作为本申请一个实施例，所述终端设备处于非激活态时，所述方法还包括： 所述第一控制面功能实体从所述终端设备当前所驻留的接入网设备中获取所述终端设备的上下文信息；或者，第一控制面功能实体从本地存储的至少一个终端设备的上下文信息中选择上述终端设备的上下文信息，例如根据终端设备的标识信息确定该终端设备的上下文信息，应理解，获取终端设备上下文信息的方式还可能有其它方式，本申请不做限定。
对于步骤420，当终端设备的上下文信息包括控制面上下文信息和用户面上下文信息时，控制面上下文信息和用户面上下文信息可以携带在同一条消息中，也可以分别携带在不同的消息中。当控制面上下文信息和用户面上下文信息携带在不同的消息中时，本申请实施例不限定上述两条消息执行的先后顺序。
具体地，在如图1所示的应用场景下，当第一控制面功能实体为MME时，初始化上下文建立请求消息(Initial Context Setup Request)携带终端设备的上下文信息，其中，所述初始化上下文建立请求消息中携带用于指示不立即建立所述终端设备与接入网设备之间的DRB的指示信息。
例如，上述初始化上下建立请求消息中包括一个指示位，该指示位用于指示接入网设备不立即建立与终端设备之间的DRB。
也就是说，当接入网设备接收到初始化上下文建立请求消息后，不立即建立终端设备与接入网设备之间的DRB，只有当终端设备有数据传输需求时，主动向接入网设备发起建立DRB的请求或者终端设备与接入网设备建立完成RRC连接之后，才建立DRB。
示例性地，上述初始上下文建立请求消息中携带S1-MME连接在MME中的标识“MME-UE-S1AP-ID”，例如，该“MME-UE-S1AP-ID”可以为211，因此，eNB和MME能够根据上述标识，建立接入网设备与第一控制面功能实体之间的第一连接；进一步地，上述初始化上下文建立请求消息中携带S1-U连接在S-GW中的标识“gTP-TEID”，例如，该S-GW中的“gTP-TEID”可以为7e10b568，因此，eNB和S-GW可以根据上述标识，建立接入网设备与用户面功能实体之间的第二连接。
在图2所示的应用场景下，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，N2连接建立响应消息和N3连接建立请求消息分别携带终端设备控制面上下文信息和用户面上下文信息，其中，所述N2连接建立响应消息或N3连接建立请求消息中携带用于指示不立即建立所述终端设备与接入网设备之间的DRB的指示信息。
例如，上述所述N2连接建立响应消息中包括一个指示位，用于指示不立即建立终端设备与接入网设备之间的DRB。
也就是说，当接入网设备接收到所述N2连接建立响应消息或N3连接建立请求消息后，不立即建立终端设备与接入网设备之间的DRB，只有当终端设备确定有数据传输需求时，主动向接入网设备发起建立DRB的请求或者终端设备与接入网设备建立完成RRC连接之后，建立DRB。
示例性地，上述N2建立响应消息中携带N2连接在AMF实体中的标识“AMF Signaling Connection ID”。因此(R)AN和AMF实体可以根据上述标识，建立接入网设备与第二控制面功能实体AMF实体之间的连接；进一步地，上述N3建立请求消息中携带第一控制面功能实体存储的N3连接在NG-UP中的标识信息。因此，(R)AN和NG-UP可以根据上述标识信息，建立接入网设备与用户面功能实体NG-UP之间的连接。
可选地，作为本申请一个实施例，所述方法还包括：第一控制面功能实体接收所述 接入网设备发送的第一标识信息和第二标识信息，其中，所述第一标识信息用于标识所述接入网设备与所述第一控制面实体之间的连接；所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接。
应理解，上述第一标识信息和第二标识信息可以携带在同一消息中，也可以携带在不同的消息中，本申请不做限定，例如第一标识信息和第二标识信息可以携带在初始化上下文建立回复消息(Initial Context Setup Response)中。
示例性地，第一标识信息可以为接入网设备与第一控制面功能实体之间的连接在接入网设备中的标识信息，例如，在4G系统中，接入网设备为eNB，第一控制面功能实体为MME，那么eNB将在向MME发送的初始上下文建立响应消息中携带第一标识信息，该第一标识信息即S1-MME连接在eNB中的标识“ENB-UE-S1AP-ID”，例如该“ENB-UE-S1AP-ID”可以为2；第二标识信息为接入网设备与用户面功能实体之间的连接在接入网设备中的标识信息，例如在4G系统中，那么第二标识信息为S1-U连接在eNB中的标识“gTP-TEID”，例如该“gTP-TEID”可以为6f84e480。
又例如，在5G系统中，接入网设备为NG-(R)AN设备，第一控制面功能实体为SMF实体，那么第一标识信息包括N2连接在(R)AN设备中的标识“(R)AN Signaling Connection ID”；第二标识信息用于标识接入网设备与用户面功能实体之间的连接，例如在5G系统中，那么第二标识信息为N3连接在(R)AN设备中的隧道信息“RAN Tunnel info”。
可选地，作为本申请一个实施例，上述方法还包括：向所述用户面功能实体发送更新请求消息，所述更新请求消息包括所述第二标识信息；接收所述用户面功能实体发送的更新响应消息。
具体地，上述用户面功能实体在4G系统中可以为S-GW，上述用户面功能实体在5G系统中可以为NG-UP实体。
也就说，第一控制面功能实体可以将第二标识信息携带在更新请求消息中，向用户面功能实体发送该更新请求消息，用于建立上述第二连接，当用户面功能实体接收到该消息后，向第一控制面功能实体发送更新响应消息，通知第一控制面功能实体建立完成所述第二连接。
换种方式说，由于第一控制面功能设备接收接入网设备发送的第二标识信息后，将存储该第二标识信息，随后向用户面功能实体发送更新请求消息时，该更新请求消息中携带第二连接在接入网设备中的第二标识信息，用户面功能实体将根据该更新请求消息携带的第二标识信息，建立第二连接，完成建立第二连接后将向控制面功能实体返回更新响应消息，例如，该更新响应消息可以为一个确认消息。
示例性地，在图1所示的应用场景下，上述第一控制面功能实体为MME，上述用户面功能实体为S-GW实体，那么第二标识信息包括S1-U连接在eNB中的标识为“gTP-TEID”，进一步地，MME将向S-GW实体发送该S1-U连接在eNB中的标识信息，该标识信息携带在承载修改请求消息中，此处承载修改请求消息即上述更新请求消息，当S-GW根据上述标识信息，建立S1-U连接，当连接建立完成后，向MME返回承载修改回复消息，此处承载修改回复消息即上述更新响应消息。
示例性地，在图2所示的应用场景下，当第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，上述用户面功能实体包括NG-UP实体，那么AMF实体将存储所述第二连接在接入网设备中的第二标识信息，例如该第二标识信息为N3连接在 NG-(R)AN设备中的标识信息，进一步地，AMF实体将通过SMF实体向NG-UP实体发送N3连接在NG-(R)AN设备中的标识信息，该标识信息携带在用户面更新请求消息中，此处用户面更新请求消息即上述更新请求消息，NG-UP实体根据上述标识信息，建立N3连接，当连接建立完成后，向SMF实体返回用户面更新回复消息，此处更新回复消息即上述更新响应消息。
基于上述步骤，终端设备处于空闲态或非激活态时，控制面功能实体和接入网设备之间的第一连接已经建立完成，接入网设备和用户面功能实体之间的第二网络建立也已经建立完成，当终端设备具有数据传输需求的时候，将建立与目标接入网设备之间的无线承载，使用上述第一连接和/或第二连接进行数据传输。
可选地，作为本申请一个实施例，所述第一控制面功能实体获取所述终端设备的接入网信息，包括：所述第一控制面功能实体获取所述终端设备的接入网信息，包括：所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体获取所述终端设备的接入网信息；或者，所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体获取所述终端设备的位置预测信息，并根据所述位置预测信息获取所述终端设备的接入网信息。
上述方案可以包括两种情况：一种情况为，第一控制面功能实体从网络能力开放功能实体中接收终端设备的接入网信息或终端设备的位置预测信息。
具体地，上述网络能力开放功能实体可以为图1应用场景下的SCEF实体，也可以为图2应用场景下的NEF实体，本申请不做限定。
其中，终端设备的位置预测信息可以包括终端设备在指定时刻的预测的经纬度坐标或预测的GPS信息等，本申请不做限定。
例如，当终端设备由连接态转换为空闲态或非激活态时，第一控制面功能实体会获知此变化，例如在图1示出的应用场景下，MME通过eNB发送的终端设备的上下文释放消息(Context Release Message)，确定终端设备从连接态转换为空闲态或非激活态；进一步地，第一控制面功能实体触发负责信息收集的网元收集终端设备的相关信息，例如历史移动轨迹，移动方向，速度，导航信息等。应理解，该负责信息收集的网元可能是已有网元，例如E-SMLC实体等，也可能是新网元，本申请不做限定。进一步地，负责信息收集的网元将收集的终端设备的相关信息告知预测网元，由预测网元预测终端设备转换为连接态的位置和时刻，该预测的方式可以通过匹配历史信息，或者根据导航信息和移动速度预测。应理解，该预测网元可能是已有网元，例如SCEF实体等，也可能是新网元，本申请不做限定。最后，预测网元将会生成预测信息，该预测信息中携带预测终端设备转换为连接态时的位置信息和终端设备的标识信息，进一步地，该预测信息中还可以携带终端设备转换为连接态的时刻信息。
可选地，预测网元向网络能力开放功能实体发送的预测信息中携带终端设备转换为连接态时的位置信息、终端设备的标识信息和终端设备转换为连接态的时刻时，网络能开放功能实体将产生一个定时器，该定时器开始计时的初始时刻为网络能力开放功能实体收到预测网元发送的预测信息的时刻，当定时器超时时，该网络能力开放功能实体向第一控制面功能实体发送连接建立请求消息，该定时器的计时时长为终端设备转换为连接态的时刻与当前时刻的时间间隔。
可选地，预测网元生成一个定时器，定时器的计时时长为终端设备转换为连接态的 时刻与当前时刻的时间间隔，而定时器开始计时的初始时刻为预测网元确定预测信息的时刻，当定时器超时时，预测网元向网络能力开放功能实体发送预测信息，该预测信息中携带终端设备转换为连接态时的位置信息、终端设备的标识信息。
当网络能力开放功能实体接收到预测信息后，会向第一控制面功能实体发送上述第一消息，该第一消息中携带终端设备转换为连接态时的位置信息和终端设备的标识信息，以用于第一控制面功能实体根据上述消息获取步骤410中的所述的终端设备的接入网信息；或者，该第一消息中直接携带终端设备的接入网信息和终端设备的标识信息，第一控制面功能实体通过该第一消息获知终端设备的接入网信息。
应理解，该连接建立请求消息可以显式地指示第一控制面功能实体启动第一连接和/或第二连接的建立过程，也可以隐式地指示第一控制面功能实体启动第一连接和/或第二连接的建立过程。
具体地，在显式的指示方式中，上述连接建立请求消息可以包括用于指示建立第一连接和/或建立第二连接的标识位、终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如国际移动用户标识(International Mobile Subscriber Identity，IMSI)。
具体地，在隐式的消息中，上述连接建立请求消息的名称即可以用于指示建立第一连接和/或建立第二连接，因此，隐式的连接建立请求消息中包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
另外一种情况中，第一控制面功能实体从第二控制面功能实体中获取终端设备的接入网信息或终端设备的位置预测信息。
在这种情况下，在5G系统中，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，第二控制面功能实体发送的第二消息中携带的信息内容通过接收网络能力开放功能实体发送的消息获得。
可选地，作为本申请一个实施例，上述方法还包括：所述第一控制面功能实体获取所述终端设备的当前位置信息或所述终端设备转换为连接态时接入的接入网设备的接入网信息。
也就是说，第一控制面功能实体获取终端设备转换为连接态时实际接入的接入网设备的接入网信息或终端设备的前期位置信息，上述信息可以为终端设备转换为连接态时实际接入的接入网设备发送至第一控制面功能实体的。应理解，终端设备转换为连接态时实际接入的接入网设备可以为上述步骤420中接入网设备中的一个接入网设备，也可以是另外的接入网设备，本申请不做限定。
因此，终端设备转换为连接态时实际接入的接入网设备可以将终端设备的当前位置信息发送至第一控制面功能实体，也可以将终端设备转换为连接态时实际接入的接入网设备的接入网信息发送至第一控制面功能实体，应理解，该接入网信息中包括可以目标接入网设备的标识信息和/或小区标识信息。
可选地，作为本申请一个实施例，所述第一控制面功能实体向所述网络能力开放功能实体发送反馈消息，其中，所述反馈消息中包括所述终端设备的当前位置信息或所述终端设备转换为连接态时接入的接入网设备的接入网信息。
也就是说，网络能力开放功能实体能够根据控制面功能实体发送的反馈信息，进一步优化预测该终端设备转换为连接态时可能接入的接入网设备，提高预先建立连接的准 确性。
图5示出了本申请另一实施例的方法的示意性流程图，该方法的执行主体可以为接入网设备，如图5所示，该方法500包括：
步骤510，接入网设备接收第一控制面功能实体发送的终端设备的上下文信息，其中，终端设备处于空闲态或非激活态。
步骤520，接入网设备根据终端设备的上下文信息，与终端设备进行数据传输。
应理解，上述通信包括上行通信和/或下行通信。
其中，终端设备的上下文信息可以参考图4所示实施例中的描述，不再赘述。
还应理解，方法500可以应用于图1或图2示出的应用场景，也就是说，第一控制面功能实体可以为图1中的MME，也可以为图2中示出的AMF实体或SMF实体，相应地，接入网设备可以为图1中示出的eNB，也可以为图2中示出的NG-(R)AN设备。
可选地，作为本申请一个实施例，所述方法还包括：向所述第一控制面功能实体发送的第一标识信息和第二标识信息，其中，所述第一标识信息包括所述接入网设备与所述第一控制面实体之间的连接的标识信息；所述第二标识信息包括所述接入网设备与用户面功能实体之间的连接的标识信息。
可选地，所述方法还包括所述接入网设备向所述第一控制面功能实体发送的第一标识信息和第二标识信息，其中，所述第一标识信息用于标识所述接入网设备与所述第一控制面实体之间的连接；所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
下面结合具体的例子，描述本申请实施例的具体方案。
图6示出了本申请一个实施例的方法的示意性流程图。在该实施例中，控制面功能实体为MME实体，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF，如图6所示，该方法包括：
步骤601，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤601之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
其中，连接建立请求消息可以显式地指示MME为终端设备建立连接，也可以隐式地指示MME为终端设备建立连接。
在发送上述连接建立请求消息之前，SCEF实体可以将终端设备在核心网外部的标识转换为终端设备在核心网内部的标识。
应理解，该连接建立请求消息可以为图4实施例中示出的第一消息。
具体地，在显式的指示方式中，上述连接建立请求消息可以包括用于指示建立S1-MME连接和/或建立S1-U连接的标识位、终端设备转换为连接态时的预测位置信息， 例如ECGI，以及所述终端设备的标识信息等，例如IMSI，应理解，该终端设备的标识信息可以为终端设备在核心网外部的标识，也可以为终端设备在核心网内部的标识。
具体地，在隐式的消息中，上述连接建立请求消息的名称即可以用于指示建立第一网络连接和/或建立第二连接，因此，隐式的连接建立请求消息中包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
MME在收到SCEF实体发送的连接建立请求消息后，若步骤601发送的连接建立请求消息为显式的消息，则MME根据上述连接建立请求消息中的指示建立连接的标识位的值，判断需要开始建立连接，例如用于指示建立连接的标识位值为1。
此后，MME根据连接建立请求消息中终端设备转换为连接态时的预测位置信息，在MME本地存储的关系列表中找到对应的eNB，因此，图6中示出的该eNB即图4实施例步骤420中描述的接入网设备，MME预测终端设备转换为连接态时将接入该eNB。
步骤602，MME向eNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中可以携带eNB与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MME连接在MME中的连接端口号；以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW实体端的隧道编号，此隧道编号在终端设备附着网络时已经预存在MME中。
应理解，终端设备的控制面上下文信息包括eNB与MME之间的S1-MME连接在MME中的上下文信息；终端设备的用户面上下文信息包括eNB与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息。
具体地，该初始化上下文建立请求消息中包括不立即建立终端设备与eNB之间的DRB的指示位，初始化上下文建立请求消息还用于告知eNB属于终端设备的上下文信息，该初始上下文建立请求消息还用于触发eNB为终端设备分配连接所需的资源。
在接收到消息之后，eNB储存上述初始化上下文建立请求消息中携带的信息，例如MME与eNB之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的的标识信息，为上述连接分别分配网络资源。
应理解，图6实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息和第二标识信息。
步骤603，eNB向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息可以携带MME与eNB之间的S1-MME连接在eNB中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB与S-GW之间的S1-U连接在S-GW实体中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，确定eNB和MME的S1-MME连接建立完成。
步骤604，MME向S-GW实体发送承载修改请求消息。
其中，该承载修改请求消息中可以携带S1-U连接在eNB中的标识信息gTP-TEID。
步骤605，S-GW实体向MME发送承载修改回复消息。
其中，该消息可以用于确认接收步骤604发送的承载修改请求消息，确定eNB和S-GW之间的S1-U连接建立完成。
步骤606，当终端设备存在待发送的上行数据时，建立与eNB之间的连接。
其中，该连接可以包括终端设备与eNB建立RRC连接与DRB，此时终端设备可以向eNB发送上行数据。
步骤607，终端设备进行上行数据传输。
步骤608，eNB向MME发送通知消息。
其中，该通知消息可以包含终端设备的内部ID。应理解，该通知消息即为图4实施例中的第三消息，用于告知MME当前终端设备所处的位置信息和/或接入的eNB信息。
步骤609，MME向SCEF实体发送反馈消息。
其中，该反馈消息可以用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输。该反馈消息可以包括当前终端设备所处的位置信息或接入的eNB信息。应理解，图6示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图6中的各种操作的变形。此外，图6中的各个步骤可以分别按照与图6所呈现的不同的顺序来执行，并且有可能并非要执行图6中的全部操作。图6示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF实体，第二控制面板功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF实体，如图7所示，该方法包括：
步骤701，NEF实体向AMF实体发送终端设备连接建立请求消息，该消息包括终端设备转换为连接态时的位置信息，以及终端设备的标识信息。
应理解，在步骤701之前，如图4实施例的描述，AMF根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF能够通过预测网元向NEF发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF根据上述信息，生成连接建立请求消息。
此后，AMF实体可以根据连接建立请求消息中的终端设备转换为连接态时的位置信息，在AMF实体在本地存储的映射关系列表中找到对应的NG-(R)AN设备，因此，图7中示出的NG-(R)AN设备即图4实施例步骤420中描述的接入网设备。
应理解，该建立请求消息可以为图4实施例中的第一消息，该连接建立请求消息可以显式地指示控制面功能实体启动N2连接和/或N3连接的建立过程，也可以隐式地指示控制面功能实体启动N2连接和/或N3连接的建立过程也就是说。图4或图5示出的实施例中第一连接在图7实施例中具体为N2连接，第二连接在图7实施例中具体为N3连接。
步骤702，AMF实体向SMF实体发送N3连接通知消息。
其中，该N3连接通知消息可以为图4实施例中描述的第二消息。该N3连接通知消息中包括步骤701中连接建立请求消息中携带的信息。该N3连接通知消息还用于请求SMF实体向AMF实体返回N3连接在SMF实体中存储的上下文信息，具体地，该通知消息可以为PDU会话激活请求消息。
步骤703，SMF实体收到步骤702的消息之后，向AMF实体发送N3连接建立请求消息。
其中，该连接建立请求消息中携带N3连接在SMF实体中的上下文信息，具体地，包括N3连接在SMF实体中的标识信息。
步骤704，AMF实体接收的N3连接建立请求消息转发至NG-(R)AN设备，并向NG-(R)AN设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
N3连接建立请求消息可以包括N3连接在NG-UP实体处的端点信息等，N2连接建立响应消息包括N2连接在AMF实体中的标识信息等，应理解，N2连接建立响应消息和/或N3连接建立请求消息中还可以包括无需立即建立无线连接的指示信息。
NG-(R)AN在收到步骤704发送的消息后，可以保存N3连接在NG-UP中的标识信息，以及N2连接在AMF中的标识信息。
进一步地，在步骤705中，NG-(R)AN设备向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。
其中，N3连接建立响应消息可以包括N3连接在NG-(R)AN设备处的标识信息等；N2建立完成消息可以包括N2连接在NG-(R)AN处的标识信息等。
AMF接收到步骤705发送的消息后，获取N2连接在NG-(R)AN设备处的标识信息，至此，N2连接建立完成。
并且，步骤706，AMF实体将N3连接建立响应消息转发至SMF实体处。
步骤707，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息。
其中，该用户面更新请求消息可以包括N3连接建立响应消息中用于N3连接在NG-(R)AN设备中的上下文信息。
NG-UP实体在接收到消息后，储存用于建立N3连接的有关NG-(R)AN设备的信息，至此，N3连接建立完成。
步骤708，NG-UP实体向SMF实体发送用户面更新响应消息，用于确认N3连接建立完成。
可选地，步骤709，当终端设备具有待发送的上行数据时，终端设备与NG-(R)AN设备之间建立无线连接。
其中，该无线连接可以包括终端设备与NG-(R)AN设备建立RRC连接与DRB。
进一步地，由于终端设备发送上行数据的连接已经建立完毕，因此终端设备可以直接发送上行数据，进行步骤710，上行数据的传输。
可选地，上述方法还包括步骤711-712。
步骤711，NG-(R)AN设备向AMF实体发送通知消息。
应理解，该通知消息为图4实施例中的第三消息，该通知消息表征NG-(R)AN已成功为终端设备提供服务，应理解，该通知消息中包括终端设备的标识信息。
步骤712，AMF向NEF发送反馈消息，该消息用于表征终端设备能够利用前述过程建立的N3和N2连接进行数据传输，该反馈消息中包括终端设备的上下文信息。应理解，图7示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图7中的各种操作的变形。此外，图7中的各个步骤可以分别按照与图7所呈现的不同的顺序来执行，并且有可能并非要执行图7中的全部操作。图8示出了本申请一个实施例的方法的示意性流程图。在该实施例中，控制面功能实体为MME，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，如图8所示，该方法包括：
步骤801，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤801之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
其中，此消息可以显式地指示MME为终端设备建立连接，也可以隐式地指示MME为终端设备建立连接。
应理解，该连接建立请求消息可以为图4实施例中示出的第一消息。
具体地，在显式的指示方式中，上述连接建立请求消息包括用于指示建立S1-MME连接和/或建立S1-U连接的标识位、终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
具体地，在隐式的消息中，上述连接建立请求消息的名称即用于指示建立第一网络连接和/或建立第二连接，因此，隐式的连接建立请求消息中包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
MME在收到SCEF实体发送的连接建立请求消息后，若步骤801发送的连接建立请求消息为显式的消息，则MME根据上述连接建立请求消息中的指示建立连接的标识位的值，判断需要开始建立连接，例如用于指示建立连接的标识位值为1。
此后，MME可以根据连接建立请求消息中的终端设备转换为连接态时的位置信息，在MME本地存储的映射关系列表中找到对应的eNB，即图8中示出的eNB。
步骤802，MME向eNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带eNB与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MME连接在MME中的连接端口号，以及MME与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW端的隧道编号，此隧道编号在终端设备附着网络时已经预存在MME中。
通过步骤802，MME向eNB发送终端设备的上下文信息。
具体地，该初始化上下文建立请求消息中包括不立即建立终端设备与eNB之间的DRB的指示位。
在接收到上下文建立请求消息之后，eNB储存上述初始化上下文建立请求消息中携带的信息，例如MME与eNB之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及MME与S-GW实体之间的S1-U连接在S-GW中的的标识信息，并为S1-U连接和S1-MME连接分别分配网络资源。
步骤803，向MME发送的初始化上下文建立回复消息，该初始化上下文建立回复消息携带了MME与eNB之间的S1-MME连接在eNB中的标识信息ENB-UE-S1AP-ID，对应于图4实施例中的第一标识信息，以及eNB与S-GW之间的S1-U连接在eNB中的的标识信息gTP-TEID，对应于图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB和MME的S1-MME连接建立完成。
步骤804，MME向S-GW实体发送承载修改请求消息，该承载修改请求消息中携带S1-U连接在eNB中的标识信息gTP-TEID。
进一步地，步骤804中的承载修改请求消息包括指示信息，该指示信息用于指示S-GW将P-GW实体下发的终端设备的数据信息缓存在本地，当S-GW实体得知该终端 设备已经成功连接至eNB后，向eNB发送缓存的数据信息。
应理解，由于S-GW实体缓存终端设备的数据信息，而不是将S-GW将终端设备的数据信息发送至eNB处缓存，能够不增加该eNB的网络负载。
步骤805，S-GW实体向MME发送承载修改回复消息，该消息用于确认接收步骤804发送的承载修改请求消息，eNB和S-GW实体之间的S1-U连接建立完成。
步骤806，由P-GW实体接收终端设备的下行数据。
步骤807，S-GW实体根据从MME中接收到的承载修改请求消息，缓存P-GW实体向终端设备发送下行数据。
步骤808，向MME发送下行数据通知消息，由S-GW实体告知MME具有终端设备的下行数据需要发送。
步骤809，MME向终端设备发送寻呼消息；终端设备将建立与eNB之间的连接，该连接包括终端设备与eNB建立RRC连接与DRB，此时终端设备可以接收eNB发送的下行数据；eNB向MME发送通知消息，该通知消息表征该终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输。
步骤810，MME向SCEF实体发送反馈消息，该反馈消息用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，图8示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图8中的各种操作的变形。此外，图8中的各个步骤可以分别按照与图8所呈现的不同的顺序来执行，并且有可能并非要执行图8中的全部操作。
图9示出了本申请一个实施例的方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF实体，如图7所示，该方法包括：
步骤901，NEF实体向AMF实体发送终端设备连接建立请求消息，该消息包括终端设备转换为连接态时的预测位置信息，例如ECGI，以及终端设备的标识信息。
应理解，在步骤901之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。此后，AMF实体根据连接建立请求消息中的终端设备转换为连接态时的预测位置信息，在AMF实体在本地存储的映射关系列表中找到对应的NG-(R)AN设备，因此，图9中示出的该NG-(R)AN设备即图4实施例步骤420中描述的接入网设备，AMF实体预测终端设备转换为连接态时将接入该NG-(R)AN设备。
应理解，该连接建立请求消息可以显式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也可以隐式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也就是说，图4或图5示出的实施例中第一连接在图9实施例中具体为N2连接，第二连接在图9实施例中具体为N3连接。
还应理解，该连接建立消息消息可以显式或隐式的指示AMF实体为终端设备建立连接。
步骤902，AMF实体向SMF实体发送N3连接通知消息。
其中，该N3连接通知消息可以为图4实施例中描述的第二通知消息，该N3连接通知消息还用于请求SMF实体向AM实体F返回N3连接在SMF实体中的上下文信息具体地，该通知消息可以为PDU会话激活请求消息，。
步骤903，SMF实体收到步骤902的消息之后，向AMF实体发送N3连接建立请求消息，该连接建立请求消息中包括N3连接在SMF实体中的标识信息。
步骤904，AMF实体将从SMF实体处接收的N3连接建立请求消息转发至NG-(R)AN设备，并向NG-(R)AN设备发送N2连接建立响应消息。
即通过步骤904，SMF实体将终端设备的上下文信息发送至NG-(R)AN设备。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息，若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
NG-(R)AN设备在收到步骤904发送的消息后，保存N3连接在NG-(R)AN中的标识信息，以及N2连接在AMF实体中的标识信息。
进一步地，在步骤905中，NG-(R)AN设备向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。
其中，N3连接建立响应消息可以包括N3连接在NG-(R)AN设备中的标识信息等；N2建立完成消息可以包括N2连接在NG-(R)AN设备中的标识信息等。
可选地，AMF实体接收到步骤905发送的消息后，储存N2连接在NG-(R)AN设备中的标识信息，至此，N2连接建立完成。
并且，步骤906，AMF实体将N3连接建立响应消息转发至SMF实体。
步骤907，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息，用户面更新请求消息包括N3连接在NG-(R)AN设备中的标识信息。
可选地，NG-UP实体在接收到消息后，储存N3连接在NG-(R)AN设备中的标识信息，至此，N3连接建立完成。
进一步地，步骤907中的建立响应消息可以包括指示信息，该指示信息用于指示NG-UP将DN下发的当前终端设备的数据信息缓存在本地，当NG-UP得知该终端设备已经成功连接至NG-(R)AN后，向NG-(R)AN发送缓存的数据信息。
步骤908，NG-UP实体向SMF实体发送用户面更新响应消息，用于确认N3连接建立完成。
步骤909，数据网络向NG-UP实体发送下行数据。
步骤910，NG-UP实体根据从SMF实体中接收到的连接建立响应消息，缓存向终端设备发送的下行数据。
步骤911，SMF实体向AMF实体发送下行数据通知消息。
其中，该通知消息可以用于F告知AMF实体具有的终端设备下行数据需要进行传输。
步骤912，AMF实体向终端设备发送寻呼消息，终端设备与NG-(R)AN设备建立无线连接；NG-(R)AN设备向NG-UP实体发送下行数据传输请求，当终端设备进行下行数据传输时，终端设备与NG-(R)AN设备之间已经建立无线连接，NG-UP实体向终端设备发送下行数据。
步骤913，AMF实体向NEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够了利用前述过程建立的N3连接和N2连接 进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，图9示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图9中的各种操作的变形。此外，图9中的各个步骤可以分别按照与图9所呈现的不同的顺序来执行，并且有可能并非要执行图9中的全部操作。
图10示出了本申请一个实施例的方法的示意性流程图。在该实施例中，控制面功能实体为MME实体，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，如图10所示，该方法包括：
步骤1001，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤1001之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
其中，此消息可以显式地指示MME为终端设备建立连接，也可以隐式地指示MME为终端设备建立连接。
具体地，在显式的指示方式中，上述连接建立请求消息包括用于指示建立S1-MME连接和/或建立S1-U连接的标识位、终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
具体地，在隐式的消息中，上述连接建立请求消息的名称即用于指示建立第一网络连接和/或建立第二连接，因此，隐式的连接建立请求消息中包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
MME在收到SCEF实体发送的连接建立请求消息后，若步骤1001发送的连接建立请求消息为显式的消息，则MME根据上述连接建立请求消息中的指示建立连接的标识位的值，判断需要开始建立连接，例如用于指示建立连接的标识位值为1。
此后，MME根据连接建立请求消息中的终端设备转换为连接态时的位置信息，在MME本地存储的映射关系列表中找到对应的eNB，该eNB即图4实施例步骤420中的接入网设备。
步骤1002，MME向eNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带eNB与MME之间的S1-MME连接在MME中的连接端口号，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的隧道编号，此隧道编号在终端设备附着网络时已经预存在MME中。
具体地，该初始化上下文建立请求消息中可以包括用于指示不立即建立终端设备与eNB之间的DRB的指示位。
在接收到消息之后，eNB储存上述初始化上下文建立请求消息中携带的信息，例如MME与eNB之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的的标识信息，为S1-MME连接和S1-U连接分别分配网络资源。
应理解，图10实施例中的初始化上下文建立请求消息可以为图4实施例中的第一连接建立请求消息或第二连接建立请求消息。
步骤1003，向MME发送的初始化上下文建立回复消息，该初始化上下文建立回复 消息携带了MME与eNB之间的S1-MME连接在eNB中的标识信息ENB-UE-S1AP-ID，以及eNB与S-GW实体之间的S1-U连接在eNB中的的标识信息gTP-TEID。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB和MME的S1-MME连接建立完成。
应理解，图10实施例中的初始化上下文建立请求回复消息可以为图4实施例中的第一连接建立请求回复消息或第二连接建立请求回复消息。
步骤1004，MME向S-GW实体发送承载修改请求消息，该承载修改请求消息中携带S1-U连接在eNB中的标识信息gTP-TEID。
步骤1005，S-GW实体向MME发送承载修改回复消息，该消息用于确认接收步骤604发送的承载修改请求消息，eNB和S-GW实体之间的S1-U连接建立完成。
应理解，上述承载修改请求消息即图4实施例中的更新请求消息，上述承载修改回复消息即图4实施例中的更新响应消息。
步骤1006，P-GW实体产生向终端设备发送的下行数据。
步骤1007，eNB缓存终端设备的下行数据。
步骤1008，MME向终端设备发送寻呼消息。
步骤1009，终端设备接收到寻呼消息后，建立与eNB之间的无线连接。
该无线连接可以包括终端设备与eNB之间的RRC连接与DRB，此时终端设备可以接收eNB发送的下行数据。
步骤1011，eNB向MME发送通知消息。
其中，该通知消息可以用于告知MME该终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输。
步骤1012，MME向SCEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，图10示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图10中的各种操作的变形。此外，图10中的各个步骤可以分别按照与图10所呈现的不同的顺序来执行，并且有可能并非要执行图10中的全部操作。图11示出了本申请一个实施例的方法的示意性流程图。在该实施例中，控制面功能实体包括AMF实体和SMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF实体，如图11所示，该方法包括：
步骤1101，NEF向AMF发送终端设备连接建立请求消息，该消息包括终端设备转换为连接态时的预测位置信息，以及终端设备的标识信息。
应理解，在步骤1101之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。
应理解，该连接建立请求消息可以显式地指示控制面功能实体启动N2连接建立过程和/或N3连接的建立过程，也可以隐式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也就是说，图4或图5示出的实施例中第一连接在图11实施例 中具体为N2连接，第二连接在图11实施例中具体为N3连接。
还应理解，该连接建立消息消息可以显式或隐式的指示AMF实体为终端设备建立连接。
步骤1102，AMF实体向SMF实体发送N3连接通知消息，该消息用于请求SMF实体向AMF实体返回N3连接在SMF实体中的标识信息。
步骤1103，SMF实体收到步骤1102的消息之后，向AMF实体发送N3连接建立请求消息，该连接建立请求消息中携带N3连接在NG-UP实体中的标识信息。
步骤1104，AMF实体将从SMF实体处接收的N3连接建立请求消息转发至NG-(R)AN设备，并向NG-(R)AN设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息，若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
还应理解，N3连接请求消息为图4或图5实施例中描述的第二连接请求消息，N2连接请求消息为图4或图5实施中描述的第一连接请求消息。
NG-(R)AN设备在收到步骤1104发送的消息后，此时，NG-(R)AN设备保存N3连接在NG-UP实体中的标识信息，以及保存N2连接在AMF实体中的标识信息。
进一步地，在步骤1105中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。N3连接建立响应消息包括N3连接在NG-(R)AN设备处的标识信息等；N2建立完成消息包括N2连接在NG-(R)AN设备处的标识信息等。
AMF实体接收到步骤1105发送的消息后，储存N2连接在NG-(R)AN设备中的上下文信息，至此，N2连接建立完成。
并且，步骤1106，AMF实体将N3连接建立响应消息转发至SMF实体处。
步骤1107，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息，消息包括N3连接在NG-(R)AN设备中的上下文信息。
NG-UP在接收到消息后，储存用于建立N3连接的上下文信息，至此，N3连接建立完成。
步骤1108，NG-UP实体向SMF实体发送用户面更新响应消息。
其中，该用户面更新响应消息可以用于确认N3连接建立完成。
步骤1109，DN经由NG-UP实体向NG-(R)AN设备发送终端设备的下行数据。
步骤1110，NG-(R)AN设备缓存DN发送的终端设备的下行数据。
步骤1111，AMF实体向终端设备发送寻呼消息。
步骤1112，当终端设备接收寻呼消息后，终端设备与NG-(R)AN设备建立无线连接。
步骤1113，NG-(R)AN设备向终端设备发送缓存的该终端设备的下行数据。
步骤1114，NG-(R)AN设备向AMF实体发送通知消息。
其中，该通知消息可以用于告知AMF实体连接已成功。应理解，该通知消息中包括终端设备的标识信息。
步骤1115，AMF实体向NEF实体发送反馈消息，该消息用于表征终端设备能够了利用前述过程建立的N3和N2连接进行数据传输，该反馈消息中包括终端设备的上下文信息。应理解，图11示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图11中的各种操作的变形。此外，图11中的各个步骤可以分别按照与图11所呈现的不同的顺序来执行，并且有可能并非要执行 图11中的全部操作。下面结合具体的例子，描述本申请实施例的具体方案。
图12示出了本申请一个方法的示意性流程图。在该实施例中，控制面功能实体为MME实体，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，eNB1和eNB2均为接入网设备，如图12所示，该方法包括：
步骤1201，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤1201之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
其中，在发送上述消息之前，SCEF实体可以首先将终端设备在核心网外部的标识转换为终端设备在核心网内部的标识。
其中，上述消息可以显式地指示MME为终端设备建立连接，也可以隐式地指示MME为终端设备建立连接。
应理解，该连接建立请求消息可以为图4实施例中示出的第一消息。
具体地，在显式的指示方式中，上述连接建立请求消息包括用于指示建立S1-MME连接和/或建立S1-U连接的标识位、终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
MME在收到SCEF实体发送的连接建立请求消息后，若步骤1201发送的连接建立请求消息为显式的消息，则MME根据上述连接建立请求消息中的标识位，判断是否建立连接，例如用于指示建立连接的标识位值为1时，建立连接。
具体地，在隐式的指示方式中，上述连接建立请求消息的名称即可以用于指示建立第一网络连接和/或建立第二连接。此外，隐式的连接建立请求消息中包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
此后，MME根据连接建立请求消息中的终端设备转换为连接态时的位置信息，在MME本地存储的关系列表中找到对应的eNB1和eNB2，该eNB1和eNB2即图4实施例中的接入网设备，MME预测终端设备转换为连接态时将接入该eNB1或eNB2。
步骤1202，MME向S-GW实体发送映射识别请求。
在通常的情况下，S-GW实体对于终端设备的某个特定连接，是一对一的映射映射关系，即一个S-GW实体中的gTP-TEID对应着一个eNB中的gTP-TEID。但是在本发明中，一个S-GW实体中的gTP-TEID对应着多个eNB中的gTP-TEID，即一对多的映射。因此该映射识别请求可以用于请求S-GW实体为多个eNB中每个eNB分配在S-GW中的gTP-TEID。对于下行数据而言，如果使用eNB的缓存方法，需要同时向多个eNB发送下行数据，因此，S-GW实体从P-GW实体获取的数据需要向多个eNB发送下行数据。
步骤1203a，MME向eNB1发送初始化上下文建立请求消息，该初始化上下文建立请求消息中携带eNB1与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MME连接在MME中的连接端口号，以及eNB1与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW端的隧道编号，此隧道编号在终端设备附着网络时已经预存在MME中。
应理解，终端设备的控制面上下文信息包括eNB1与MME之间的S1-MME连接在MME中的上下文信息；终端设备的用户面上下文信息包括eNB1与S-GW实体之间的 S1-U连接在S-GW实体中的上下文信息。
具体地，该初始化上下文建立请求消息中包括不立即建立终端设备与eNB1之间的DRB的指示位，初始化上下文建立请求消息还用于告知eNB1关于终端设备的上下文信息，比如终端设备的网络能力，原先为终端设备的提供S1-U连接在S-GW中的隧道编号等，该初始上下文建立请求消息还用于触发eNB1为终端设备分配连接所需的资源。
在接收到消息之后，eNB1储存上述初始化上下文建立请求消息中携带的信息，例如MME与eNB1之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及MME与S-GW实体之间的S1-U连接在S-GW实体中的标识信息，为上述连接分别分配网络资源。
应理解，图12实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤1204a，向MME发送的初始化上下文建立回复消息，该初始化上下文建立回复消息携带了MME与eNB1之间的S1-MME连接在eNB1中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB1与S-GW实体之间的S1-U连接在eNB1中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，可以储存ENB-UE-S1AP-ID，至此，eNB1和MME的S1-MME连接建立完成。
步骤1205a，MME向S-GW实体发送承载修改请求消息，该承载修改请求消息中携带S1-U连接在S-GW实体中的标识信息gTP-TEID。
步骤1206a，S-GW实体向MME发送承载修改回复消息，该消息用于确认接收步骤604发送的承载修改请求消息，eNB1和S-GW实体之间的S1-U承载得以建立。
步骤1203b，MME向eNB2发送初始化上下文建立请求消息，该初始化上下文建立请求消息中携带eNB2与MME之间的S1-MME连接在MME中的标识信息，以及eNB2与S-GW实体之间的S1-U连接在S-GW实体标识信息。
具体地，该初始化上下文建立请求消息中包括用于指示不立即建立终端设备与eNB2之间的DRB的指示位。
在接收到消息之后，eNB2储存上述初始化上下文建立请求消息中携带的信息，例如MME与eNB2之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB2与S-GW实体之间的S1-U连接在S-GW实体中的标识信息，为上述连接分别分配网络资源。
应理解，图12实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤1204b，向MME发送的初始化上下文建立回复消息，该初始化上下文建立回复消息携带了MME与eNB2之间的S1-MME连接在eNB2中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB2与S-GW之间的S1-U连接在eNB2中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，可以储存ENB-UE-S1AP-ID，至此，eNB2和MME的S1-MME连接建立完成。
步骤1205a，MME向S-GW实体发送承载修改请求消息，该承载修改请求消息中携带S1-U连接在eNB2中的标识信息gTP-TEID。
步骤1206a，S-GW实体向MME发送承载修改回复消息。
其中，该消息可以用于确认接收步骤604发送的承载修改请求消息，确定eNB2和S-GW实体之间的S1-U连接建立完成。
如果当终端设备确定eNB1为实际转换为连接态时接入的接入网设备时，步骤1207，当终端设备需要进行上行数据传输时，建立与eNB1之间的无线连接。
其中，上无线连接可以包括终端设备与eNB1之间建立的RRC连接和DRB，此时终端设备可以向eNB1发送上行数据。
步骤1208，终端设备进行上行数据传输。
步骤1209，eNB1向MME发送通知消息，应理解，该通知消息即为图4实施例中的第三消息，用于告知MME当前终端设备所处的位置信息或接入的eNB1信息。
步骤1210，MME向SCEF实体发送反馈消息，该消息用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输，该反馈消息中包括当前终端设备所处的位置信息或接入的eNB1的信息。
应理解，图12示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图12中的各种操作的变形。此外，图12中的各个步骤可以分别按照与图12所呈现的不同的顺序来执行，并且有可能并非要执行图12中的全部操作。
图13示出了本申请一个方法的示意性流程图。在该实施例中，控制面功能实体为MME，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，eNB1和eNB2均为接入网设备，如图13所示，该方法包括：
步骤1301，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤1301之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
在发送上述消息之前，SCEF首先将终端设备在核心网外部的标识转换为终端设备在核心网内部的标识，步骤1301中的连接建立请求消息可以显式地指示MME为终端设备建立连接，也可以隐式地指示MME为终端设备建立连接。
应理解，该连接建立请求消息可以为图4实施例中示出的第一消息。
具体地，在显式的指示方式中，上述连接建立请求消息包括用于指示建立S1-MME连接和/或建立S1-U连接的标识位，以及终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI，应理解，该终端设备的标识信息可以为终端设备在核心网外部的标识，也可以为终端设备在核心网内部的标识。
MME在收到SCEF实体发送的连接建立请求消息后，若步骤1201发送的连接建立请求消息为显式的消息，则MME根据上述连接建立请求消息中的标识位，判断是否建立连接，例如用于指示建立连接的标识位值为1时，建立连接。具体地，在隐式的指示方式中，上述连接建立请求消息的名称可以用于指示建立第一网络连接和/或建立第二连接。该隐式的连接建立请求消息可以包括终端设备转换为连接态时的位置信息，例如ECGI，以及所述终端设备的标识信息等，例如IMSI。
此后，MME根据连接建立请求消息中的终端设备转换为连接态时的位置信息，在 MME本地存储的映射关系列表中找到对应的eNB1和eNB2，该eNB1和eNB2即图4实施例中的接入网设备，MME预测终端设备转换为连接态时将接入该eNB1或eNB2。
步骤1302，MME向S-GW实体发送映射识别请求。
其中，该映射识别请求与前述实施例中的描述一致，在此不再赘述。
步骤1303a，MME向eNB1发送初始化上下文建立请求消息，该初始化上下文建立请求消息中携带eNB1与MME之间的S1-MME连接在MME中标识信息，以及eNB1与S-GW实体之间的S1-U连接在S-GW实体中标识信息。
具体地，该初始化上下文建立请求消息中包括用于指示不立即建立终端设备与eNB1之间的DRB的指示位。
在接收到消息之后，eNB1储存MME与eNB1之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB1与S-GW实体之间的S1-U连接在S-GW实体中的标识信息，为上述S1-MME连接和S1-U连接分别分配网络资源。
应理解，图13实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤1304a，eNB1向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息携带了MME与eNB1之间的S1-MME连接在eNB1中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB1与S-GW之间的S1-U连接在eNB2中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB1和MME的S1-MME连接建立完成。
步骤1303b，MME向eNB2发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带eNB2与MME之间的S1-MME连接在MME中的标识信息，以及eNB2与S-GW实体之间的S1-U连接在S-GW实体中的标识信息。
具体地，该初始化上下文建立请求消息中包括不立即建立终端设备与eNB2之间的DRB的指示位。
在接收到消息之后，eNB2储存MME与eNB2之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB2与S-GW实体之间的S1-U连接在S-GW实体中的标识信息，为上述S1-MME连接和S1-U连接分别分配网络资源。
应理解，图13实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤1304b，eNB2向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息携带了MME与eNB2之间的S1-MME连接在eNB2中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB2与S-GW之间的S1-U连接在S-GW中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB2和MME的S1-MME连接建立完成。
步骤1305，MME向S-GW实体发送承载修改请求消息。
其中，该承载修改请求消息中携带S1-U连接在eNB2中的标识信息gTP-TEID，以及S1-U连接在eNB1中的标识信息gTP-TEID。
步骤1306，S-GW实体向MME发送承载修改回复消息。
其中，该消息可以用于确认接收步骤604发送的承载修改请求消息。eNB2和S-GW实体之间的S1-U连接，以及eNB1和S-GW实体之间的S1-U连接建立完成。
应理解，与图12所示出的实施例不同，在图13所示的实施例中，MME向S-GW实体发送的承载修改请求消息中，同时携带了eNB1与S-GW实体之间的S1-U连接的信息和eNB2与S-GW实体之间S1-U连接的信息。
如果当终端设备确定eNB1为终端设备实际转换为连接态时接入的接入网设备，当终端设备需要进行上行数据传输时，将执行步骤1307，建立与eNB1之间的无线连接。
其中，该无线连接可以包括终端设备与eNB1之间建立的RRC连接与DRB，此时终端设备可以向eNB1发送上行数据。
步骤1308，终端设备发送上行数据。
步骤1309，eNB1向MME发送通知消息。
其中，该通知消息可以为图4实施例中的第三消息，用于告知MME当前终端设备所处的位置信息或接入的eNB1的信息。
步骤1310，MME向SCEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的S1-MME和S1-U进行数据传输，该反馈消息中包括当前终端设备所处的位置信息或接入的eNB1信息。
应理解，图12和图13实施例示出了在4G系统中，终端设备具有上行数据传输需求时，终端设备转换为连接态的示意性流程图，而对于终端设备具有下行数据传输需求时，预先建立连接的过程可以与步骤1201至1206b相同，也可以与步骤1301至1306b相同，为了简洁起见，不再赘述。
应理解，图13示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图13中的各种操作的变形。此外，图13中的各个步骤可以分别按照与图13所呈现的不同的顺序来执行，并且有可能并非要执行图13中的全部操作。
图14示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF实体，如图14所示，该方法包括：
步骤1401，NEF实体向AMF实体发送终端设备连接建立请求消息。
应理解，在步骤1401之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。其中，该消息包括终端设备转换为连接态时的预测位置信息，以及终端设备的标识信息。
应理解，该建立请求消息可以为图4实施例中的第一消息，该连接建立请求消息可以显式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也可以隐式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也就是说，图 4示出的实施例中第一连接在图14实施例中具体为N2连接，第二连接在图14实施例中具体为N3连接。
还应理解，该连接建立消息可以显式或隐式的指示AMF实体为终端设备建立连接。
步骤1402，AMF实体向SMF实体发送N3连接通知消息。
其中，该N3连接通知消息可以为图4实施例中描述的第二消息，该N3连接通知消息中包括步骤1401中连接建立请求消息中携带的信息。
步骤1403，SMF实体收到步骤1402的消息之后，向AMF实体发送N3连接建立请求消息。
其中，该连接建立请求消息中携带N3连接在SMF实体中的上下文信息，具体地，可以包括N3连接在SMF实体中的标识信息。应理解，SMF实体或AMF实体根据该连接建立请求消息中携带的终端设备的上下文信息中，预测终端设备转换为连接态时接入的接入网设备为(R)AN1设备或(R)AN2设备。
步骤1404a，AMF实体将从SMF实体处接收的N3连接建立请求消息转发至(R)AN1设备，并向(R)AN1设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
应理解，终端设备的用户面上下文信息包括N3连接在SMF中的上下文信息；终端设备的控制面上下文信息包括N2连接在AMF实体中的上下文信息。
(R)AN1在收到步骤1404a发送的消息后，此时，(R)AN1设备保存了用于建立N3连接的信息，例如N3连接在NG-UP实体中的标识信息，以及用于建立N2连接的信息，例如，保存N2连接在AMF实体中的标识信息。
进一步地，在步骤1405a中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。N3连接建立响应消息包括与N3连接在(R)AN1设备中的上下文信息，包括N3连接在(R)AN1设备处的标识信息等；N2建立完成消息包含了N2连接在(R)AN1设备中的上下文信息，包括N3连接在(R)AN1处的标识信息等。AMF接收到步骤1405a发送的消息后，储存N2连接在(R)AN1设备中的上下文信息，至此，N2连接建立完成。
同理，在步骤1404b，AMF将从SMF处接收的N3连接建立请求消息转发至(R)AN2设备，AMF也向(R)AN2设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
(R)AN2设备在收到步骤1404a发送的消息后，此时，(R)AN2设备保存了用于建立N3连接的上下文信息，例如N3连接在NG-UP实体中的标识信息，以及用于建立N2连接的上下文信息，例如，保存N2连接在AMF实体中的标识信息。
进一步地，在步骤1405a中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。具体地，N3连接建立响应消息包括与N3连接在(R)AN2中的上下文信息，包括N3连接在(R)AN2设备中的标识信息等；N2建立完成消息包括N2连接在(R)AN2设备中的上下文信息，包括N3连接在(R)AN2中的标识信息等。
AMF接收到步骤1405a发送的消息后，储存N2连接在(R)AN2设备中的上下文信息，至此，N2连接建立完成。
进一步地，步骤1406，AMF实体将N3连接建立响应消息转发至SMF实体，该N3 连接建立响应消息中携带N3连接在(R)AN2设备和/或(R)AN1设备中的上下文信息。
应理解，UE的用户面上下文信息包括N3连接在(R)AN2设备和/或(R)AN1设备中的上下文信息。
步骤1407，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息。
其中，该用户面更新请求消息可以包括N3连接建立响应消息中N3连接在(R)AN2和/或(R)AN1中的上下文信息。
NG-UP在接收到消息后，储存N3连接在(R)AN1设备中的上下文信息和/或储存N3连接在(R)AN2设备中的上下文信息，至此，N3连接建立完成。
步骤1408，NG-UP实体向SMF实体发送用户面更新响应消息。
其中，用户面更新响应消息可以用于确认N3连接建立完成。
应理解，步骤1406可以分别细化为AMF实体向SMF实体发送的两条N3连接建立响应消息，该两条N3连接建立响应消息分别包括N3连接在(R)AN2设备处的标识信息等和N3连接在(R)AN1设备处的标识信息等，该两条N3建立响应消息在本申请实施例中的执行顺序不做限定。也就是说，实际上该两条N3连接响应消息分别用于建立(R)AN1设备与用户面功能实体之间的连接以及(R)AN2设备与用户面功能实体之间的连接。
还应理解，步骤1407可以分别细化为SMF实体向NG-UP实体发送的两条用户面更新请求消息，该两条用户面更新请求消息分别携带N3连接在(R)AN2设备中的标识信息等和N3连接在(R)AN1设备中的标识信息等，该两条用户面更新请求消息在本申请实施例中的执行顺序不做限定。
还应理解，步骤1408可以分别细化为NG-UP实体向SMF实体发送的两条用户面更新响应消息，该两条用户面更新响应消息分别用于确认(R)AN1设备与用户面功能实体之间的连接以及(R)AN2设备与用户面功能实体之间的连接建立完成，该两条用户面更新响应消息在本申请实施例中的执行顺序不做限定。
通过上述步骤，(R)AN1设备与第一控制面实体之间的连接建立完成，(R)AN1设备与用户面功能实体之间的连接建立完成；同理，(R)AN2设备与第一控制面实体之间的连接建立完成，(R)AN2设备与用户面功能实体之间的连接建立完成。
进一步地，当终端设备需要进行上行数据传输时，终端设备将与接入网设备之间建立无线连接，例如，当(R)AN1设备为终端设备转换为连接态时实际接入的接入网设备时，那么终端设备将与(R)AN1设备之间建立无线连接。
进一步地，由于为终端设备发送上行数据的连接已经建立完毕，因此终端设备可以发送上行数据，进行上行数据的传输。
应理解，如果(R)AN1设备为终端设备的终端设备转换为连接态时实际接入的接入网设备，那么(R)AN1设备可以向AMF实体发送通知消息，应理解，该通知消息为图4实施例中的第三消息，该通知消息用于告知AMF实体，(R)AN1设备已成功为终端设备提供服务，应理解，该通知消息中包括终端设备的标识信息。
进一步地，AMF实体向NEF实体发送反馈消息，该消息可以用于表征终端设备能够利用前述过程建立的N3和N2连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，当终端设备需要进行下行传输时，与接入网设备的传输过程与图9示出的 步骤909至步骤913相相似，或者与图11示出的1109至1115步骤相似，在此不再赘述。
应理解，图14示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图14中的各种操作的变形。此外，图14中的各个步骤可以分别按照与图14所呈现的不同的顺序来执行，并且有可能并非要执行图14中的全部操作。
上面结合图12至图14分别描述了在4G系统中和5G系统中预先向多个接入网设备发送终端设备上下文信息的示意性流程图。
图15示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF，并且进一步地，本申请实施例中示出了终端设备终端设备在处于空闲态或非激活态之前接入的源接入网(Source AN)设备，以及根据终端设备的接入网信息确定的终端设备转换为连接态时可能接入的目标接入网(Target AN)设备。如图15所示，方法包括：
步骤1501，NEF实体向AMF实体发送连接建立请求消息。
应理解，在步骤1501之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么AMF可以根据该接入网信息确定终端设备的目标接入网(Target AN)设备。
步骤1502a，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息可以用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤1503a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤1504a，目标接入网设备向AMF实体发送传输成功通知消息。
其中，传输成功通知消息可以用于告知AMF实体已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤1502b-1504b替代。
步骤1502b，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向AMF实体发送终端设备的上下文信息。
步骤1503b，源接入网设备向AMF实体发送上下文传输消息。
其中，该上下文传输消息中携带终端设备的上下文信息。
步骤1504b，AMF实体将从源接入网设备获得的终端设备的上下文信息转发至目标接入网设备。
其中，终端设备的上下文信息可以包含用于建立N3连接的信息，例如N3连接在NG-UP实体中的标识信息，以及用于建立N2连接的信息，例如，AMF实体中的标识信息。
Target RAN设备在收到步骤1506发送的消息后，此时，Target RAN设备保存了用 于建立N3连接的信息，例如N3连接在NG-UP实体中的标识信息，以及用于建立N2连接的信息，例如，保存N2连接在AMF实体中的标识信息。
进一步地，在步骤1505b中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。N3连接建立响应消息包括与N3连接在Target RAN设备中的信息，包括N3连接在Target RAN设备处的标识信息等；N2建立完成消息包含了与N2连接有关的Target RAN设备的信息，包括N3连接在Target RAN设备处的标识信息等。
AMF实体接收到步骤1505b发送的消息后，储存N2连接在Target RAN设备中的上下文信息，至此，N2连接建立完成。
并且，步骤1506，AMF实体将N3连接建立响应消息转发至SMF实体处。
步骤1507，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息。
其中，用户面更新请求消息包括N3连接建立响应消息中用于N3连接在Target RAN设备中的上下文信息。
NG-UP在接收到消息后，储存用于建立N3连接的有关Target RAN设备的信息，至此，N3连接建立完成。
步骤1508，NG-UP实体向SMF实体发送用户面更新响应消息，用于确认N3连接建立完成。
进一步地，终端设备需传输上行数据时，执行步骤1509，建立无线连接，并且进一步地，执行步骤1510，进行上行数据的传输。
步骤1511d，Target AN设备向Source AN设备发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source AN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
步骤1512d，Target AN设备向AMF实体发送通知消息。
应理解，该通知消息可以为图4实施例中的第三消息，该通知消息用于告知AMF实体，Target AN设备已成功为终端设备提供服务，应理解，该通知消息中包括终端设备的标识信息。
步骤1513d，AMF实体向NEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的N3和N2连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，步骤1511d-1513d还可以由步骤1511e-1513e代替。
步骤1511e，Target AN设备向AMF实体发送上下文释放请求消息。
其中，该上下文释放请求消息可以用于请求AMF实体转发上述上下文释放请求消息至Source AN设备，还应理解，该上下文释放请求消息的另外一个作用是告知AMF实体，Target AN设备已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，AMF实体将执行步骤1512e，AMF向Source AN设备发送上下文释放请求消息，该上下文释放请求消息用于指示Source AN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
步骤1513e，AMF实体向NEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的N3和N2连接进行数 据传输，该反馈消息中包括终端设备的上下文信息。
应理解，在步骤701之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。
图16示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为MME，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，并且进一步地，本申请实施例中示出了终端设备终端设备在处于空闲态或非激活态之前接入的源接入网设备(例如，Source eNB)，以及根据终端设备的接入网信息预测的终端设备转换为连接态时可能接入的目标接入网设备(例如，Target eNB)。如图16所示，方法包括：
步骤1601，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤1501之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。
其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么MME可以根据该接入网信息确定终端设备的目标接入网设备(Target eNB)。
步骤1602a，MME向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息可以用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤1603a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤1604a，目标接入网设备向MME发送传输成功通知消息。
其中，传输成功通知消息可以用于告知MME已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤1602b-1604b替代。
步骤1602b，MME向源接入网设备发送上下文传输通知消息，该上下文传输通知消息用于通知源接入网设备向MME发送终端设备的上下文信息。
步骤1603b，源接入网设备向MME发送上下文传输消息，该上下文传输消息中携带终端设备的上下文信息。
步骤1604b，MME向TargeteNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带TargeteNB与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MMW连接在MME中的标识信息，以及MME与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW端的标识信息。
具体地，该初始化上下文建立请求消息中包括不立即建立终端设备与TargeteNB之间的DRB的指示位，初始化上下文建立请求消息还用于告知TargeteNB关于终端设备的 上下文信息，比如终端设备的网络能力，原先为终端设备的提供S1-U连接在S-GW实体中的隧道编号等，该初始上下文建立请求消息还用于触发Target eNB为终端设备分配连接所需的资源。
在接收到消息之后，Target eNB储存上述初始化上下文建立请求消息中携带的信息，例如MME与Target eNB之间的S1-MME连接在MME中的标识信息MME-UE-S1AP-ID，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的的标识信息。
应理解，图16实施例中的初始化上下文建立请求消息中包括图4实施例中的第一标识信息或第二标识信息。
步骤1605b，向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息可以携带MME与Target eNB之间的S1-MME连接在Target eNB中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及eNB与S-GW之间的S1-U连接在Target eNB中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB和MME的S1-MME连接建立完成。
步骤1606，MME向S-GW实体发送承载修改请求消息。
其中，该承载修改请求消息中携带S1-U连接在eNB中的标识信息gTP-TEID。
步骤1607，S-GW实体向MME发送承载修改回复消息，该消息用于确认接收步骤604发送的承载修改请求消息，Target eNB和S-GW实体之间的S1-U连接建立完成。
进一步地，终端设备需传输上行数据时，执行步骤1608，建立无线连接，并且进一步地，执行步骤1609，进行上行数据的传输。
步骤1610d，TargeteNB向Source eNB发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
步骤1611d，TargeteNB向MME发送通知消息。
应理解，该通知消息可以为图4实施例中的第三消息，该通知消息用于告知MME，Target eNB已成功为终端设备提供服务，应理解，该通知消息中可以包括终端设备的标识信息。
步骤1612d，MME向SCEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，步骤1610d-1612d还可以由步骤1610e-1612e代替。
步骤1610e，Target eNB向MME发送上下文释放请求消息。
其中，该上下文释放请求消息可以用于请求MME转发上述上下文释放请求消息至Source eNB，还应理解，该上下文释放请求消息的另外一个作用是告知MME，Target eNB已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，MME将执行步骤1611e，MME向Source eNB发送上下文释放请求消息，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
步骤1612e，MME向SCEF实体发送反馈消息。
其中，该消息可以用于表征终端设备能够利用前述过程建立的S1-MME连接和S1-U连接进行数据传输，该反馈消息中包括终端设备的上下文信息。
应理解，图16示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图16中的各种操作的变形。此外，图16中的各个步骤可以分别按照与图16所呈现的不同的顺序来执行，并且有可能并非要执行图16中的全部操作。
图17示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF，第二控制面板功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF实体，并且进一步地，本申请实施例中示出了终端设备终端设备在处于空闲态或非激活态之前接入的源接入网(Source AN)设备，以及根据终端设备的接入网信息预测的终端设备转换为连接态时可能接入的目标接入网(Target AN)设备。如图17所示，方法包括：
步骤1701，NEF实体向AMF实体发送连接建立请求消息。
应理解，在步骤1701之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请求消息。
其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么AMF实体可以根据该接入网信息确定终端设备的目标接入网(Target AN)设备。
步骤1702a，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤1703a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤1704a，目标接入网设备向AMF实体发送传输成功通知消息。
其中，传输成功通知消息可以用于告知AMF实体已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤1702b-1704b替代。
步骤1702b，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息可以用于通知源接入网设备向AMF实体发送终端设备的上下文信息。
步骤1703b，源接入网设备向AM实体F发送上下文传输消息。
其中，该上下文传输消息中携带终端设备的上下文信息。
步骤1704b，AMF实体将从SMF实体处接收的N3连接建立请求消息转发至Target RAN设备，并向Target RAN设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
源接入网设备在收到步骤1704b发送的消息后，Target RAN设备保存用于建立N3连接的信息，例如N3连接在Target RAN设备中的标识信息，以及用于建立N2连接的 信息，例如，保存N2连接在AMF实体中的标识信息。
进一步地，在步骤1705b中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。
其中，N3连接建立响应消息包括与N3连接在Target RAN设备中的信息，包括N3连接在Target RAN设备处的标识信息等；N2建立完成消息包含了与N2连接有关的Target RAN设备的信息，包括N3连接在Target RAN设备处的标识信息等。
AMF接收到步骤1705b发送的消息后，储存N2连接在Target RAN设备中的上下文信息，至此，N2连接建立完成。
并且，步骤1706，AMF实体将N3连接建立响应消息转发至SMF实体处。
步骤1707，SMF实体接收到N3连接建立响应消息后，向NG-UP发送用户面更新请求消息。
其中，用户面更新请求消息可以包括N3连接建立响应消息中用于N3连接在NG-(R)AN中的上下文信息。
NG-UP实体在接收到消息后，储存用于建立N3连接的有关Target RAN设备的信息，至此，N3连接建立完成。
步骤1708，NG-UP实体向SMF实体发送用户面更新响应消息。
其中，用户面更新响应消息可以用于确认N3连接建立完成。
进一步地，当数据网络传输终端设备的下行数据时，执行步骤1708，DN向NG-UP实体传输下行传输。
步骤1709，NG-UP实体缓存终端设备的下行数据。
步骤1710，NG-UP经Target RAN设备向终端设备发送寻呼消息。
并且进一步地，执行步骤1711，终端设备建立与Target RAN设备之间的无线连接。
步骤1712，SMF实体向Target RAN设备发送终端设备的下行数据。
步骤1713，Target RAN设备向终端设备发送下行数据。
步骤1714d，Target RAN设备向Source RAN设备发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source RAN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，步骤1714d还可以由步骤1714e-1715e代替。
步骤1714e，Target RAN设备向AMF实体发送上下文释放请求消息。
其中，该上下文释放请求消息用于请求AMF实体转发上述上下文释放请求消息至Source RAN设备，还应理解，该上下文释放请求消息的另外一个作用是告知AMF实体，Target RAN设备已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，AMF实体将执行步骤1715e，AMF实体向Source RAN设备发送上下文释放请求消息，该上下文释放请求消息用于指示Source RAN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，图17示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图17中的各种操作的变形。此外，图17中的各个步骤可以分别按照与图17所呈现的不同的顺序来执行，并且有可能并非要执行图17中的全部操作。图18示出了本申请一个方法的示意性流程图。在该实施例中，第一控 制面功能实体为MME，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，并且进一步地，本申请实施例中示出了终端设备终端设备在处于空闲态或非激活态之前接入的源接入网设备(Source eNB)，以及根据终端设备的接入网信息预测的终端设备转换为连接态时可能接入的目标接入网设备(Target eNB)。如图18所示，方法包括：
步骤1801，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤1801之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么MME可以根据该接入网信息确定终端设备的目标接入网设备(Target eNB)。
步骤1802a，MME向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤1803a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤1804a，目标接入网设备向MME发送传输成功通知消息。
其中，传输成功通知消息可以用于告知MME已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤1802b-1804b替代。
步骤1802b，MME向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向MME发送终端设备的上下文信息。
步骤1803b，源接入网设备向MME发送上下文传输消息。
其中，该上下文传输消息中携带终端设备的上下文信息。
步骤1804b，MME向TargeteNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带TargeteNB与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MME连接在MME中的标识信息，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW实体中的标识信息。
在接收到消息之后，Target eNB储存上述初始化上下文建立请求消息中携带的信息，例如MME与Target eNB之间的S1-MME连接在MME中的标识信息MME-终端设备-S1AP-ID，以及eNB与S-GW实体之间的S1-U连接在S-GW实体中的的标识信息。
应理解，图18实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤1805b，向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息携带了MME与Target eNB之间的S1-MME连接在Target eNB中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及Target eNB与S-GW实体之间的S1-U连接在Target eNB中的的标识信息gTP-TEID， 即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB和MME的S1-MME连接建立完成。
步骤1806，MME向S-GW实体发送承载修改请求消息。
其中，该承载修改请求消息中携带S1-U连接在Target eNB中的标识信息gTP-TEID。
步骤1807，S-GW实体向MME发送承载修改回复消息。
其中，该消息可以用于确认接收步骤604发送的承载修改请求消息，Target eNB和S-GW实体之间的S1-U连接建立完成。
步骤1808，DN向S-GW实体发送下行数据。
步骤1809，S-GW实体缓存DN发送的下行数据。
步骤1810，S-GW实体通过下行数据通知消息(Downlink Data Notification，DNN)告知MME有终端设备的下行数据。
之后，由MME向终端设备发送寻呼消息。
进一步地，执行步骤1811，终端设备建立与Target eNB之间的无线连接，并且进一步地，执行步骤1812和1813，进行下行数据的传输。
步骤1814d，Target eNB向Source eNB发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，步骤1814d还可以由步骤1814e-1815e代替。
步骤1814e，Target eNB向MME发送上下文释放请求消息。
其中，该上下文释放请求消息用于请求MME转发上述上下文释放请求消息至Source eNB，还应理解，该上下文释放请求消息的另外一个作用是告知MME，Target eNB已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，MME将执行步骤1815e，MME向Source eNB发送上下文释放请求消息，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，图18示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图18中的各种操作的变形。此外，图18中的各个步骤可以分别按照与图18所呈现的不同的顺序来执行，并且有可能并非要执行图18中的全部操作。
图19示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF实体，第二控制面功能实体为AMF实体，用户面功能实体为NG-UP实体，网络能力开放功能实体为NEF，并且进一步地，本申请实施例中示出了终端设备在处于连接态时接入的源接入网(Source RAN)设备，以及根据终端设备的接入网信息预测的终端设备转换为连接态时可能目标接入网(Target RAN)设备。如图19所示，方法包括：
步骤1901，NEF实体向AMF实体发送连接建立请求消息。
应理解，在步骤1901之前，如图4实施例的描述，AMF实体根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，AMF实体能够通过预测网元向NEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，NEF实体根据上述信息，生成连接建立请 求消息。其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么AMF实体可以根据该接入网信息确定终端设备的目标接入网(Target RAN)设备。
步骤1902a，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤1903a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤1904a，目标接入网设备向AMF实体发送传输成功通知消息。
其中，传输成功通知消息可以用于告知AMF实体已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤1902b-1904b替代。
步骤1902b，AMF实体向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向AMF实体发送终端设备的上下文信息。
步骤1903b，源接入网设备向AMF实体发送上下文传输消息。
其中，该上下文传输消息中携带终端设备的上下文信息。
步骤1904b，AMF实体将从SMF实体处接收的N3连接建立请求消息转发至Target RAN设备，并向Target RAN设备发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
N3连接建立请求消息包括储存在SMF实体中的有关NG-UP实体的上下文信息，包括PDU Session标识信息，N3连接在NG-UP处的端点信息，PDU session质量服务等。
N2连接建立响应消息包括N2连接在AMF实体中的上下文信息，包括N2连接在AMF实体中的端点等。值得注意的是，消息中包含了“无需立即建立无线连接”的标识位。
Target RAN设备在收到步骤1904b发送的消息后，保存用于建立N3连接的信息，例如N3连接在Target RAN设备中的标识信息，以及用于建立N2连接的信息，例如，保存N2连接在AMF中的标识信息。
进一步地，在步骤1905b中，向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。
其中，N3连接建立响应消息包括与N3连接在Target RAN设备中的信息，包括N3连接在Target RAN设备中的标识信息等；N2建立完成消息包括N3连接在Target RAN设备中的标识信息等。
AMF实体接收到步骤1905b发送的消息后，储存N2连接在Target RAN设备中的上下文信息，至此，N2连接建立完成。
并且，步骤1906，AMF实体将N3连接建立响应消息转发至SMF实体处。
步骤1907，SMF实体接收到N3连接建立响应消息后，向NG-UP实体发送用户面更新请求消息。
其中，用户面更新请求消息包括N3连接建立响应消息中用于N3连接在Target RAN设备中的上下文信息。
NG-UP实体在接收到消息后，储存用于建立N3连接在Target RAN设备中的标识信 息，至此，N3连接建立完成。
步骤1908，NG-UP向SMF实体发送用户面更新响应消息，用于确认N3连接建立完成。
进一步地，数据网络有向终端设备发送下行数据的传输需求时，执行步骤1908，DN向NG-UP实体传输下行传输。
步骤1909，NG-UP向Target RAN设备传输终端设备的下行数据。
步骤1910，Target RAN设备缓存该终端设备的下行数据。
步骤1911，NG-UP实体向Source RAN设备传输该终端设备的下行数据。
步骤1912，Source RAN设备缓存该终端设备的下行数据。
应理解，在步骤1909至1912中，Source RAN设备和Target RAN设备都缓存数据目的是降低由于第一控制面功能实体对终端的Target RAN设备预测不准确，导致终端设备无法送该Target RAN设备处接收下行数据的情况。例如，终端设备仍处于Source RAN范围的情形下，可能仍然从Source RAN设备处接收该终端设备的下行数据。
步骤1913，终端设备建立与Target RAN设备之间的无线连接。
步骤1914，Target RAN设备向终端设备发送该终端设备的下行数据。
步骤1916d，Target RAN设备向Source RAN设备发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source RAN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，步骤1916d还可以由步骤1916e-1917e代替。
步骤1916e，Target RAN设备向AMF实体发送上下文释放请求消息，该上下文释放请求消息用于请求AMF转发上述上下文释放请求消息至Source RAN设备，还应理解，该上下文释放请求消息的另外一个作用是告知AMF实体，Target RAN设备已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，AMF实体将执行步骤1917e，AMF实体向Source RAN设备发送上下文释放请求消息，该上下文释放请求消息用于指示Source RAN设备删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，图19示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图19中的各种操作的变形。此外，图19中的各个步骤可以分别按照与图19所呈现的不同的顺序来执行，并且有可能并非要执行图19中的全部操作。
图20示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为MME，用户面功能实体为S-GW实体，网络能力开放功能实体为SCEF实体，并且进一步地，本申请实施例中示出了终端设备终端设备在处于空闲态或非激活态之前接入的源接入网设备(Source eNB)，以及根据终端设备的接入网信息预测的终端设备转换为连接态时可能接入的目标接入网设备(Target eNB)。如图20所示，方法包括：
步骤2001，SCEF实体向MME发送连接建立请求消息。
应理解，在步骤601之前，如图4实施例的描述，MME根据终端设备发送的上下文释放消息，确定终端设备从连接态转换为空闲态或非激活态，进一步地，MME能够通过预测网元向SCEF实体发送终端设备的预测信息，上述预测信息包括预测终端设备转换为连接态的位置和时刻，进一步地，SCEF实体根据上述信息，生成连接建立请求消息。
其中，该连接建立请求消息中携带终端设备的接入网信息，例如该连接建立请求消息中携带终端设备的ECGI，以及终端设备的标识信息或接入网设备的标识信息，那么MME可以根据该接入网信息确定终端设备的目标接入网设备(Target eNB)。
步骤2002a，MME向源接入网设备发送上下文传输通知消息。
其中，该上下文传输通知消息用于通知源接入网设备向目标接入网设备发送终端设备的上下文信息，可选地，该上下文通知消息中携带目标接入网设备的标识信息。
步骤2003a，源接入网设备向目标接入网设备发送终端设备的上下文信息。
步骤2004a，目标接入网设备向MME发送传输成功通知消息。
其中，传输成功通知消息可以用于告知MME已经接收到终端设备的上下文信息。
另外一种目标接入网设备获取终端设备的上下文信息的可选方式可以由步骤2002b-2004b替代。
步骤2002b，MME向源接入网设备发送上下文传输通知消息，该上下文传输通知消息用于通知源接入网设备向MME发送终端设备的上下文信息。
步骤2003b，源接入网设备向MME发送上下文传输消息，该上下文传输消息中携带终端设备的上下文信息。
步骤2004b，MME向TargeteNB发送初始化上下文建立请求消息。
其中，该初始化上下文建立请求消息中携带TargeteNB与MME之间的S1-MME连接在MME中的上下文信息，例如该S1-MME连接在MME中的标识信息，以及Target eNB与S-GW实体之间的S1-U连接在S-GW实体中的上下文信息，例如S1-U连接在S-GW实体中的标识信息。
应理解，图20实施例中的初始化上下文建立请求消息中包括为图4实施例中的第一标识信息或第二标识信息。
步骤2005b，向MME发送的初始化上下文建立回复消息。
其中，该初始化上下文建立回复消息携带了MME与Target eNB之间的S1-MME连接在Target eNB中的标识信息ENB-UE-S1AP-ID，即图4实施例中的第一标识信息，以及Target eNB与S-GW实体之间的S1-U连接在Target eNB中的的标识信息gTP-TEID，即图4实施例中的第二标识信息。
MME在接收到上述初始化上下文建立请求回复消息后，储存ENB-UE-S1AP-ID，至此，eNB和MME的S1-MME连接建立完成。
步骤2006，MME向S-GW实体发送承载修改请求消息，该承载修改请求消息中携带S1-U连接在Target eNB中的标识信息gTP-TEID。
步骤2007，S-GW实体向MME发送承载修改回复消息。
其中，该消息可以用于确认接收步骤604发送的承载修改请求消息，Target eNB和S-GW之间的S1-U承载得以建立。
步骤2008，DN向S-GW实体传输终端设备的下行数据。
步骤2009，S-GW实体向Target eNB发送终端设备的下行数据。
步骤2010，Target eNB缓存S-GW实体发送的该终端设备的下行数据。
步骤2011，S-GW向Source eNB发送该终端设备的下行数据。
步骤2012，Source eNB缓存S-GW实体发送的该终端设备的下行数据。
步骤2013，Target eNB向终端设备发起寻呼。
步骤2014，Source eNB向终端设备发起寻呼。
步骤2015，终端设备建立与Target eNB之间的无线连接。步骤2016，进行下行数据的传输。
步骤2017d，Target eNB向Source eNB发送上下文释放请求消息。
其中，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，步骤2017d还可以由步骤2017e-2018e代替。
步骤2017e，Target eNB向MME发送上下文释放请求消息。
其中，该上下文释放请求消息用于请求MME转发上述上下文释放请求消息至Source eNB，还应理解，该上下文释放请求消息的另外一个作用是告知MME，Target eNB已成功为终端设备提供服务，可选地，该通知消息中包括终端设备的标识信息。
进一步地，MME将执行步骤2018e，MME向Source eNB发送上下文释放请求消息，该上下文释放请求消息用于指示Source eNB删除存储的终端设备的上下文信息，有利于节省网络资源。
应理解，图20示出了本申请一实施例的详细步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图20中的各种操作的变形。此外，图20中的各个步骤可以分别按照与图20所呈现的不同的顺序来执行，并且有可能并非要执行图20中的全部操作。
应理解，上述图15至图20中实施例描述的目标接入网设备指的是终端设备转换为连接态时预测可能接入的接入网设备。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
图21示出了本申请一个方法的示意性流程图。在该实施例中，第一控制面功能实体为SMF2实体，第二控制面功能实体为AMF实体，用户面功能实体为NG-UP1实体、NG-UP2实体和下一代用户平面锚点(NG-UP anchor)实体，网络能力开放功能实体为NEF实体，如图21所示，该方法包括：
步骤2101，NEF实体向AMF实体发送终端设备终端设备连接建立请求消息，该连接建立请求消息包括终端设备恢复连接态时的位置信息，以及终端设备终端设备的标识信息，也就是该连接建立请求消息中包括终端设备的上下文信息。
应理解，该建立请求消息可以为图4实施例中的第一消息，该连接建立请求消息可以显式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也可以隐式地指示控制面功能实体启动建立N2连接和/或建立N3连接的建立过程，也就是说，图4示出的实施例中第一网络连接在图21实施例中具体为N2连接，第二网络连接在图21实施例中具体为N3连接。
还应理解，该连接建立消息可以显式或隐式地指示AMF实体为终端设备终端设备建立网络连接。
AMF实体接收到上述连接建立请求消息后，AMF实体根据本地策略，以及终端设备恢复连接态时的位置信息等，选择SMF1作为第一控制面功能实体。
步骤2102，AMF实体向SMF1发送N3连接通知消息，该N3连接通知消息即为图 4实施例中描述的第二消息，该N3连接通知消息中包括步骤2101连接建立请求消息中携带的信息。具体地，该通知消息可以为PDU会话建立请求消息，该消息中携带了用于指示连接预建立的标识信息，能够用于请求SMF2向NG-UP2发送N3连接建立请求消息。
步骤2103a，SMF1实体收到步骤2102的N3连接通知消息之后，终端设备获取终端设备的终端设备上下文信息。
步骤2103，SMF1根据本地策略以及终端设备恢复连接态时的位置信息，选择NG-UP2实体为终端设备的用户面功能实体，而NG-UP1为终端设备上一次处于连接态时的用户面功能实体。SMF1实体为终端设备创建N3连接的上下文信息。具体地，该N3连接的上下文信息中包括N3连接在NG-UP2中的标识信息，N9连接在NG-UP2处的标识信息。可选地，包括SMF1为终端设备分配的网际协议(Internet Protocol，IP)地址。
应理解，SMF1实体或AMF实体根据该连接建立请求消息中携带的终端设备的上下文信息中，预测终端设备恢复连接态时接入的接入网设备为(R)AN设备。
步骤2104a，SMF1实体向NG-UP2发送用户上下文请求消息，该用户上下文请求消息中携带N3连接在SMF1实体中的上下文信息。具体地，包括N3连接在NG-UP2中的标识信息，在SMF2中存储的N9连接在NG-UP anchor处的标识信息。
其中，N9连接为NG-UP实体与NG-UP anchor实体之间的连接，由于可能有多个NG-UP实体与NG-UP anchor实体相连，因此，该N9连接用于传输该多个NG-UP实体之间的数据。NG-UP2实体在收到步骤2104a发送的消息后，此时NG-UP2实体保存了用于建立N9连接的信息，例如N9连接在NG-UP anchor实体处的标识信息。以及用于建立N3连接的信息，例如，保存N3连接在NG-UP2实体中的标识信息。
步骤2104b，NG-UP2实体向SMF1实体发送用户上下文响应消息。
步骤2105，SMF1向NG-UP anchor实体发送N3连接更改请求，该连接更改请求消息包括N9连接在NG-UP2处的标识信息。
可选地，该N3连接更改请求还用于通知NG-UP anchor不删除的NG-UP1实体的信息，例如该N3连接更改请求中用于告知NG-UP anchor实体不删除的NG-UP1实体的信息的标识位值为1。
应理解，当N3连接更改请求包含告知NG-UP anchor实体不删除原来的NG-UP1实体的信息的标识位时，步骤2101中NEF实体向AMF实体发送的终端设备连接建立请求消息同时包含了终端设备在上一次处于连接态时的接入网设备信息。
还应理解，当NEF实体向AMF实体发送的终端设备连接建立请求消息同时包含了终端设备在上一次处于连接态时的接入网设备信息(例如(R)AN2设备信息)时，核心网设备为与(R)AN2设备设备建立用户上下文信息的交互过程的步骤同图7中的步骤702至708步骤相似，或者与图9中的步骤902至908步骤相似，或者与图11中的步骤1102至1108的步骤相似，在此不作赘述。
N3连接更改请求消息包括储存在SMF1实体中的有关NG-UP2的上下文信息，该上下文信息包括N3连接在NG-UP2实体处的端点信息，NG-UP2的IP地址等。
步骤2106，NG-UP anchor实体向SMF1实体发送N3连接更改响应消息。至此，N9连接建立完成。
步骤2107，SMF1实体向AMF实体发送N3连接建立请求消息，该消息包括SMF1实体为N3连接创建的上下文信息。具体地，N3连接建立请求消息包括SMF1实体向NG-(R)AN设备发送终端设备的PDU会话标识，PDU会话的服务质量描述，以及N3连接在NG-UP2实体中的标识信息。
步骤2108，AMF实体将从SMF1实体处接收的N3连接建立请求消息转发至NG-(R)AN设备，AMF实体也向NG-(R)AN实体发送N2连接建立响应消息。
应理解，N3连接建立请求消息和N2连接建立响应消息可能是一个消息，也可能是两个不同的消息。若为两个不同的消息，则对消息间发送的先后顺序本申请不做限定。
N3连接建立请求消息包括储存在SMF1实体中的有关NG-UP2实体的信息，该信息包括PDU会话标识信息，N3连接在NG-UP2实体处的端点信息，PDU会话质量服务等。
N2连接建立响应消息包括AMF实体的信息，该信息包括N2连接在AMF实体处的端点等。值得注意的是，消息中包含了“无需立即建立无线连接”的标识位。
NG-(R)AN在收到步骤2108发送的消息后，此时NG-(R)AN设备保存了用于建立N3连接的信息，例如N3连接在NG-UP2处的标识信息，以及用于建立N2连接的信息，例如，保存N2连接在AMF中的标识信息。
进一步地，在步骤2109中，NG-(R)AN设备向AMF实体发送N2连接建立完成消息以及N3连接建立响应消息。具体地，N3连接建立响应消息包括与N3连接在NG-(R)AN中的信息，包括N3连接在NG-(R)AN设备处的标识信息等；N2建立完成消息包含了与N2连接有关的NG-(R)AN设备的信息，包括N2连接在NG-(R)AN设备处的标识信息等。
AMF接收到步骤2109发送的消息后，储存N2连接在NG-(R)AN设备中的上下文信息，至此，N2连接建立完成。
进一步地，步骤2110，AMF实体将N3连接建立响应消息转发至SMF1实体，该N3连接建立响应消息中携带N3连接在NG-(R)AN设备中的上下文信息。
步骤2111，SMF1实体接收到N3连接建立响应消息后，向NG-UP2实体发送用户面更新请求消息。
其中，该用户面更新请求消息可以包括N3连接建立响应消息中用于N3连接在NG-(R)AN设备中为终端设备创建的的上下文信息。
NG-UP2实体在接收到消息后，储存用于建立N3连接的有关NG-(R)AN设备中的终端设备上下文信息，至此，N3连接建立完成。
步骤2112，NG-UP实体向SMF1实体发送用户面更新响应消息，该用户面更新响应消息可以用于确认N3连接建立完成。
通过上述步骤，NG-(R)AN设备与第一控制面实体之间的连接建立完成，NG-(R)AN与用户面功能实体之间的连接建立完成。
步骤2113，SMF2向AMF发送终端设备IP地址提示消息，消息包括SMF2为终端设备分配的IP地址。可选地，包含了告知AS不需要删除原终端设备的IP地址的标识信息。
步骤2114，AMF向NEF发送终端设备IP地址提示消息，消息包括SMF2为终端设备分配的IP地址。可选地，包含了告知AS不需要删除原终端设备的IP地址的标识信息。
进一步地，步骤2115，当终端设备需要进行上行数据传输时，终端设备将与目标接入网设备之间建立无线网络连接，例如，当(R)AN设备为目标接入网设备时，那么终端 设备将与(R)AN设备之间建立无线网络连接。
进一步地，由于为终端设备发送上行数据的连接已经建立完毕，因此终端设备可以发送上行数据，进行上行数据的传输。
步骤2116，应理解，如果(R)AN设备为终端设备的目标接入网，那么(R)AN设备可以向AMF实体发送通知消息，应理解，该通知消息为图4实施例中的第三消息，该通知消息用于告知AMF实体，(R)AN设备已成功为终端设备提供服务，应理解，该通知消息中包括终端设备的标识信息。
进一步地，AMF实体向SMF1实体发送通知消息，该消息用于(R)AN已成功为终端设备提供服务，该反馈消息中包括终端设备的标识信息。
步骤2117，SMF1实体向NG-UP1实体发送会话终止请求消息，用于通知NG-UP1实体删除其储存的终端设备的上下文信息。在NG-UP1实体删除储存的终端设备上下文信息之后，NG-UP1向SMF1实体发送会话终止响应消息。
应理解，当终端设备需要进行下行传输时，与目标接入网设备的传输过程与图9示出的步骤909至步骤913相似，或者与图11示出的1109至1115步骤相似，在此不再赘述。
上面结合图4至图21从方法的角度详细描述了本申请实施例的示意性流程图，下面结合图22至25从装置的角度描述本申请实施例的相关设备。
图22是本发明一个实施例的网络设备的示意性结构框图。图22是本发明实施例的核心网设备2200的示意性框图。应理解，核心网设备2200能够执行图4至图21的方法中由第一控制面功能实体执行的各个步骤，为了避免重复，此处不再详述。核心网设备2200包括：
获取单元2210，用于获取所述终端设备的接入网信息，其中，终端设备处于空闲态或非激活态。
发送单元2220，用于根据获取单元2210获取的接入网信息，向接入网设备发送所述终端设备的上下文信息。
应理解，该获取单元2210执行的动作可以由处理器实现，而发送单元2220执行的动作可以在处理器的控制下由收发器实现。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
图23是本发明一个实施例的接入网设备的示意性结构框图。图23是本发明实施例的接入网设备2300的示意性框图。应理解，接入网设备2300能够执行图4至图21的方法中由接入网设备执行的各个步骤，为了避免重复，此处不再详述。接入网设备2300包括：
接收单元2310，用于接收第一控制面功能实体发送的所述终端设备的上行文信息，其中，终端设备处于空闲态或非激活态。
通信单元2320，用于根据接收单元2310接收的所述终端设备的上下文信息，与所述终端设备进行通信。
应理解，该获取单元2310执行的动作可以由处理器实现，而发送单元2320执行的动作可以在处理器的控制下由收发器实现。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
图24是本发明一个实施例的装置的示意性结构框图。图24示出了本发明实施例提供的装置2400。应理解，装置2400能够执行图4至图21的方法中由第一控制面功能实体执行的各个步骤，为了避免重复，此处不再详述。装置2400包括：
存储器2410，用于存储程序；
收发器2420，用于和其他设备进行通信；
处理器2430，用于执行存储器2410中的程序，处理器2430与所述存储器2410和所述收发器2420分别相连，用于执行所述存储器2410存储的所述指令，以在执行所述指令时执行如下步骤：
所述处理器2430用于通过收发器2420获取所述终端设备的接入网信息，其中，终端设备处于空闲态或非激活态；根据所述接入网信息，向接入网设备发送所述终端设备的上下文信息。
应理解，装置2400可以具体为上述实施例中的第一控制面功能实体，并且可以用于执行上述方法实施例中与第一控制面功能实体对应的各个步骤和/或流程。
因此，当终端设备处于空闲态或非激活态时，本申请实施例中第一控制面功能实体通过获取终端设备的接入网信息，预先向该接入网信息对应的接入网设备发送该终端设备的上下文信息，当终端设备具有数据传输需求时，即终端设备需要从空闲态向连接态切换或者从非激活态向连接态切换时，无需等待终端设备的上下文信息传输过程，有利于减小时延。
图25是本发明一个实施例的装置的示意性结构框图。图25示出了本发明实施例提供的装置2500。应理解，装置2500能够执行图4至图20的方法中由接入网设备执行的各个步骤，为了避免重复，此处不再详述。装置2500包括：
存储器2510，用于存储程序；
收发器2520，用于和其他设备进行通信；
处理器2530，用于执行存储器2510中的程序，处理器2530与所述存储器2510和所述收发器2520分别相连，用于执行所述存储器2510存储的所述指令，以在执行所述指令时执行如下步骤：
所述处理器2530用于通过收发器2520接收第一控制面功能实体发送的所述终端设备的上下文信息，其中，终端设备处于空闲态或非激活态；根据所述终端设备的上下文信息，与所述终端设备进行通信。
应理解，装置2500可以具体为上述实施例4至21中的接入网设备，并且可以用于执行上述方法实施例中与接入网设备对应的各个步骤和/或流程。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究 竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (22)

  1. 一种通信方法，其特征在于，包括：
    第一控制面功能实体获取终端设备的接入网信息，其中，所述终端设备处于空闲态或非激活态；
    所述第一控制面功能实体根据所述接入网信息，向接入网设备发送所述终端设备的上下文信息。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备的上下文信息包括：
    所述终端设备的用户面上下文信息；以及
    所述终端设备的控制面上下文信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一控制面功能实体接收所述接入网设备发送的第一标识信息和第二标识信息；
    其中，所述第一标识信息用于标识所述接入网设备与所述第一控制面实体之间的连接；所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一控制面功能实体向所述用户面功能实体发送更新请求消息，所述更新请求消息包括所述第二标识信息；
    所述第一控制面功能实体接收所述用户面功能实体发送的更新响应消息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一控制面功能实体获取所述终端设备的接入网信息，包括：
    所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体接收所述终端设备的接入网信息；或者，
    所述第一控制面功能实体从网络能力开放功能实体或第二控制面功能实体接收所述终端设备的位置预测信息，并根据所述位置预测信息获取所述终端设备的接入网信息。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，当所述终端设备处于非激活态时，所述方法还包括：
    所述第一控制面功能实体从所述终端设备当前所驻留的接入网设备获取所述终端设备的上下文信息。
  7. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一控制面功能实体获取所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的的接入网设备的信息。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第一控制面功能实体向所述网络能力开放功能实体发送反馈消息，其中，所述反馈消息包括所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的接入网设备的信息。
  9. 一种通信方法，其特征在于，包括：
    接入网设备接收第一控制面功能实体发送的终端设备的上下文信息，其中，所述终端设备处于空闲态或非激活态；
    所述接入网设备根据所述终端设备的上下文信息，与所述终端设备进行数据传输。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述第一控制面功能实体发送的第一标识信息和第二标识信息，其中，所述第一标识信息包括所述接入网设备与所述第一控制面实体之间的连接的标识信息；所述第二标识信息包括所述接入网设备与用户面功能实体之间的连接的标识信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述第一控制面功能实体发送所述终端设备的当前位置信息或所述接入网设备的信息。
  12. 一种核心网设备，其特征在于，包括：
    获取单元，用于获取终端设备的接入网信息，其中，所述终端设备处于空闲态或非激活态；
    发送单元，用于根据所述接入网信息，向接入网设备发送所述终端设备的上下文信息。
  13. 根据权利要求12所述的核心网设备，其特征在于，所述终端设备的上下文信息包括：
    所述终端设备的用户面上下文信息；以及
    所述终端设备的控制面上下文信息。
  14. 根据权利要求12或13所述的核心网设备，其特征在于，所述核心网设备还包括：
    接收单元，用于接收所述接入网设备发送的第一标识信息和第二标识信息；
    其中，所述第一标识信息用于标识所述接入网设备与所述核心网设备之间的连接，所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接。
  15. 根据权利要求14所述的核心网设备，其特征在于：
    所述发送单元，还用于向所述用户面功能实体发送更新请求消息，所述更新请求消息包括所述第二标识信息；
    所述接收单元，还用于接收所述用户面功能实体发送的更新响应消息。
  16. 根据权利要求12至15中任一项所述的核心网设备，其特征在于，所述获取单元还用于：
    从网络能力开放功能实体或控制面功能实体接收所述终端设备的接入网信息；或者，
    从网络能力开放功能实体或控制面功能实体接收所述终端设备的位置预测信息，并根据所述位置预测信息获取所述终端设备的接入网信息。
  17. 根据权利要求15所述的核心网设备，其特征在于，当所述终端设备处于非激活态时，所述获取单元还用于：
    从所述终端设备当前所驻留的接入网设备获取所述终端设备的上下文信息。
  18. 根据权利要求17所述的核心网设备，其特征在于，所述获取单元还用于：
    获取所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的接入网设备的信息。
  19. 根据权利要求18所述的核心网设备，其特征在于，所述发送单元还用于：
    向所述网络能力开放功能实体发送反馈消息，其中，所述反馈消息包括所述终端设备的当前位置信息或所述终端设备转换为连接态时所述终端设备的接入网设备的信息。
  20. 一种接入网设备，其特征在于，包括：
    接收单元，用于接收控制面功能实体发送的终端设备的上行文信息，其中，所述终端设备处于空闲态或非激活态；
    通信单元，用于根据所述终端设备的上下文信息，与所述终端设备进行数据传输。
  21. 根据权利要求20所述的接入网设备，其特征在于，所述接入网设备还包括：
    发送单元，用于向所述控制面功能实体发送的第一标识信息和第二标识信息，其中，所述第一标识信息用于标识所述接入网设备与所述控制面实体之间的连接；所述第二标识信息用于标识所述接入网设备与用户面功能实体之间的连接。
  22. 根据权利要求20或21所述的接入网设备，其特征在于，所述发送单元还用于：
    向所述控制面功能实体发送所述终端设备的当前位置信息或所述接入网设备的信息。
PCT/CN2017/077388 2017-03-20 2017-03-20 通信方法及其设备 WO2018170706A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2017/077388 WO2018170706A1 (zh) 2017-03-20 2017-03-20 通信方法及其设备
CN201780084667.6A CN110214460B (zh) 2017-03-20 2017-03-20 通信方法及其设备
EP17901872.6A EP3585110B1 (en) 2017-03-20 2017-03-20 Communication method and device thereof
US16/569,735 US11202250B2 (en) 2017-03-20 2019-09-13 Communication method for reducing delay in an idle or inactive mode and device thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077388 WO2018170706A1 (zh) 2017-03-20 2017-03-20 通信方法及其设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/569,735 Continuation US11202250B2 (en) 2017-03-20 2019-09-13 Communication method for reducing delay in an idle or inactive mode and device thereof

Publications (1)

Publication Number Publication Date
WO2018170706A1 true WO2018170706A1 (zh) 2018-09-27

Family

ID=63584590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077388 WO2018170706A1 (zh) 2017-03-20 2017-03-20 通信方法及其设备

Country Status (4)

Country Link
US (1) US11202250B2 (zh)
EP (1) EP3585110B1 (zh)
CN (1) CN110214460B (zh)
WO (1) WO2018170706A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113170412A (zh) * 2018-11-21 2021-07-23 索尼集团公司 基于传播信道特性延迟网络中用户设备寻呼操作的系统、方法和计算机程序产品
US11729671B2 (en) 2018-10-05 2023-08-15 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113498221B (zh) * 2020-04-02 2024-04-26 大唐移动通信设备有限公司 非激活态ue进行状态转换方法和用户终端及网络侧设备
EP3968696A1 (en) * 2020-09-15 2022-03-16 Nokia Technologies Oy Ng based context release and data forwarding for multi-hop mobility
US20220295540A1 (en) * 2021-03-09 2022-09-15 FG Innovation Company Limited Monitoring physical downlink control channel for small data transmission

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101287169A (zh) * 2008-05-27 2008-10-15 中兴通讯股份有限公司 一种s1接口应用协议标识的传输方法
CN101815281A (zh) * 2009-02-20 2010-08-25 华为技术有限公司 一种处理本地疏导业务的方法、设备及通信系统
CN103634849A (zh) * 2012-08-27 2014-03-12 华为终端有限公司 用于传输数据的方法和设备
CN105592533A (zh) * 2014-11-07 2016-05-18 思科技术公司 用于提供网络环境中的省电模式增强的系统和方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1960567B (zh) * 2005-11-03 2010-04-21 华为技术有限公司 一种终端进入和退出空闲模式的通信方法
CN103687055B (zh) * 2012-09-25 2019-02-26 中兴通讯股份有限公司 一种承载分配和管理的方法及设备
US8923880B2 (en) 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
US20170251357A1 (en) * 2014-09-05 2017-08-31 Nec Corporation Method and device for transferring mobility management and bearer management
WO2016064141A1 (ko) 2014-10-23 2016-04-28 엘지전자 주식회사 무선 통신 시스템에서 연결된 상태의 단말을 위하여 개선된 drx 방식을 구성하는 방법 및 장치
US10470090B2 (en) * 2014-11-14 2019-11-05 Qualcomm Incorporated Data compression techniques for handover and radio link failure recovery
WO2017126928A1 (ko) * 2016-01-20 2017-07-27 엘지전자 주식회사 연결 모드 변경 방법 및 이동성 관리 개체

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101287169A (zh) * 2008-05-27 2008-10-15 中兴通讯股份有限公司 一种s1接口应用协议标识的传输方法
CN101815281A (zh) * 2009-02-20 2010-08-25 华为技术有限公司 一种处理本地疏导业务的方法、设备及通信系统
CN103634849A (zh) * 2012-08-27 2014-03-12 华为终端有限公司 用于传输数据的方法和设备
CN105592533A (zh) * 2014-11-07 2016-05-18 思科技术公司 用于提供网络环境中的省电模式增强的系统和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3585110A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11729671B2 (en) 2018-10-05 2023-08-15 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
CN113170412A (zh) * 2018-11-21 2021-07-23 索尼集团公司 基于传播信道特性延迟网络中用户设备寻呼操作的系统、方法和计算机程序产品

Also Published As

Publication number Publication date
EP3585110A1 (en) 2019-12-25
CN110214460A (zh) 2019-09-06
EP3585110A4 (en) 2020-01-22
US11202250B2 (en) 2021-12-14
US20200008137A1 (en) 2020-01-02
EP3585110B1 (en) 2022-04-20
CN110214460B (zh) 2021-01-29

Similar Documents

Publication Publication Date Title
WO2018170706A1 (zh) 通信方法及其设备
CN107548127B (zh) 支持数据传输的方法和设备
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
US10015718B2 (en) Method, apparatus, and system for routing user plane data in mobile network
KR101465847B1 (ko) 통신 시스템과 통신 제어 방법
EP3652993B1 (en) Method for supporting handover and corresponding apparatus.
JP6346288B2 (ja) Ｌｔｅネットワーク上でショートデータバーストサービスを最適化するための方法およびシステム
JP5021772B2 (ja) トラッキングエリアの更新或いは切替プロセスにおいてリソースが誤ってリリースされることを防ぐ方法
US8976717B2 (en) Method for data forwarding
WO2009049529A1 (fr) Procédé d'établissement de support de charge et dispositif associé
WO2014101571A1 (zh) 一种承载分配方法及用户设备、基站和服务网关
WO2011015147A1 (zh) 数据传输方法、装置和通信系统
WO2011026392A1 (zh) 一种路由策略的获取方法及系统
WO2021254353A1 (zh) 一种释放中继连接的方法、设备及系统
WO2015124104A1 (zh) 一种路径建立方法、设备及系统、核心网设备
WO2013170673A1 (zh) 一种接入方法、基站、接入点和用户设备
WO2018082070A1 (zh) 一种数据报文处理方法及控制面网元、用户面网元
WO2009132582A1 (zh) 一种删除承载的方法与装置
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
WO2011050663A1 (zh) 支持本地ip访问的通信系统中隧道更新方法与系统
WO2017173586A1 (zh) 一种用户终端的管理方法及相关设备
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
WO2014146578A1 (zh) 通过小小区传输数据的方法及宏演进基站
WO2011020230A1 (zh) 无线准入控制的方法及装置
WO2013185542A1 (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: 17901872

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017901872

Country of ref document: EP

Effective date: 20190918