WO2018112897A1 - 一种会话激活方法及装置和系统 - Google Patents

一种会话激活方法及装置和系统 Download PDF

Info

Publication number
WO2018112897A1
WO2018112897A1 PCT/CN2016/111753 CN2016111753W WO2018112897A1 WO 2018112897 A1 WO2018112897 A1 WO 2018112897A1 CN 2016111753 W CN2016111753 W CN 2016111753W WO 2018112897 A1 WO2018112897 A1 WO 2018112897A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
function entity
management function
terminal
session
Prior art date
Application number
PCT/CN2016/111753
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 EP16924589.1A priority Critical patent/EP3550867A4/en
Priority to PCT/CN2016/111753 priority patent/WO2018112897A1/zh
Priority to CN201680091560.XA priority patent/CN110073686B/zh
Publication of WO2018112897A1 publication Critical patent/WO2018112897A1/zh
Priority to US16/447,551 priority patent/US11206537B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a session activation method, apparatus, and system.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • the NE such as MME or S-GW
  • the core network architecture is split according to the type of function (such as authentication and security functions, session management functions, mobility management functions, and access control functions).
  • function such as authentication and security functions, session management functions, mobility management functions, and access control functions.
  • For different NF components different functions are implemented by the corresponding NF components. Functional decoupling between different NF components, and for a certain NF component, it can interact with other NF components through the supported interfaces to complete related network services.
  • the NE in the core network architecture can implement the separation of the Mobility Management (MM) function and the Session Management (SM) function.
  • the MM function is implemented by the MM function entity, and the SM function is performed by the SM function. Entity completed.
  • a protocol data unit (PDU) session may be established for one terminal, and these PDU sessions are simultaneously activated. This causes a lot of signaling interaction between the terminal and the network, resulting in a higher network load and faster power consumption of the terminal.
  • PDU protocol data unit
  • the embodiment of the present invention provides a method for session activation, a mobility management function entity, a session management function entity, a terminal, and a system, so as to alleviate the problem of excessive signaling interaction between the terminal and the network in the existing solution.
  • an embodiment of the present invention provides a session activation method, where the method includes: a mobility management function entity acquires a protocol data unit PDU session activation request of a terminal, where the PDU session activation request includes an identifier of a PDU session and an identifier of the terminal, where The PDU session activation request is for requesting activation of the PDU session; the mobility management function entity sends the PDU session activation request to the session management function entity; the session management function entity activates the PDU session according to the PDU session activation request.
  • the mobility management function entity can acquire a PDU session activation request including an identifier of the PDU session and an identifier of the terminal, and send the PDU session activation request to the session management function entity, thereby activating the PDU session. Therefore, the solution of the embodiment of the present invention can activate the PDU session on demand without activating all PDU sessions with established connections, thereby reducing signaling interaction between the terminal and the network, thereby reducing network load and saving power of the terminal. .
  • the mobility management function entity may obtain the PDU session activation request of the terminal in one of the following manners: In the first manner, the mobility management function entity may receive a control plane connection activation request from the terminal, and the control plane connection is activated. The request includes the PDU session activation request; in the second manner, the mobility management function entity can receive the PDU session activation request from the terminal.
  • the terminal may further generate the PDU session activation request.
  • the mobility management function entity may hold a binding relationship between the identifier of the terminal, the identifier of the PDU session, and the identifier of the session management function entity; the mobility management function entity sends the PDU to the session management function entity.
  • the session management function entity identified by the identifier of the session management function entity may be selected according to the identifier of the PDU session, the identifier of the terminal, and the binding relationship.
  • the mobility management function entity may further receive a handover request from the target access node, where the handover request carries the identifier of the terminal and the identifier of the target access node, where the handover request is used to request to access the terminal from the source.
  • the node switches to the target access node; then, the mobility management function entity can send a mobile event of the terminal to the session management function entity, the mobile event including the identity of the terminal and the identity of the target access node.
  • the session management function entity receives the movement of the terminal from the mobility management function entity. After the event, the at least one PDU session corresponding to the identifier of the terminal may be determined; when the at least one PDU session is an idle state PDU session, the session management function entity may determine whether the context of the at least one PDU session needs to be updated; or, when the at least When a PDU session is an active PDU session, the session management function entity can notify the terminal and the target access node to update the context of the at least one PDU session.
  • the at least one PDU session is an idle state PDU session
  • the context of the at least one PDU session includes an identifier of the first user plane function entity
  • the session management function entity may be according to the service of the target access node.
  • a list of service areas of the area and the first user plane functional entity determines whether the context of the at least one PDU session needs to be updated.
  • the session management function entity may determine that the context of the at least one PDU session needs to be updated; or if the service area of the target access node In the list of service areas of the first user plane functional entity, the session management function entity may determine that the context of the at least one PDU session does not need to be updated.
  • the session management function entity may further send a release message to the first user plane function entity, and release the message for the configuration that only the first user plane function releases the at least one PDU session. Resources; and select a second user plane functional entity for the terminal. And/or, the session management function entity may further send a PDU session update message to the mobility management function entity, where the PDU session update message is used to update the context of the at least one PDU session.
  • the mobility management function entity may further send the PDU session update message to the terminal. After receiving the PDU session update message from the mobility management function entity, the terminal may update the context of the at least one PDU session according to the PDU session update message.
  • an embodiment of the present invention provides a session processing method, where the method includes: a mobility management function entity receives a handover request from a target access node, and the handover request carries an identifier of the terminal and an identifier of the target access node, where the handover The request is for requesting to switch the terminal from the source access node to the target access node; the mobility management function entity sends the mobile event of the terminal to the session management function entity, where the mobile event includes the identifier of the terminal and the identifier of the target access node; session management Determining, by the functional entity, at least one PDU session corresponding to the identifier of the terminal, when the at least one PDU session is an idle state PDU session, the session management function entity determines whether the context of the at least one PDU session needs to be updated; or when the at least one PDU session The session management function entity notifies the terminal and target when the PDU session is activated The access node updates the context of the at least one PDU session.
  • the at least one PDU session is an idle state PDU session
  • the context of the at least one PDU session may include an identifier of the first user plane function entity
  • the session management function entity may be according to the service area of the target access node. And determining, by the service area list of the first user plane function entity, whether the context of the at least one PDU session needs to be updated.
  • the session management function entity determines that the context of the at least one PDU session needs to be updated; or if the service area of the target access node is In the service area list of the first user plane functional entity, the session management function entity determines that the context of the at least one PDU session does not need to be updated.
  • the session management function entity may further send a release message to the first user plane function entity, and the release message is used to indicate the first user plane function entity. Release a configuration resource of at least one PDU session; and select a second user plane functional entity for the terminal. And/or, the session management function entity may further send a PDU session update message to the mobility management function entity, where the PDU session update message is used to update the context of the at least one PDU session.
  • the mobility management function entity may further send the PDU session update message to the terminal.
  • the terminal may update the context of the at least one PDU session according to the PDU session update message.
  • an embodiment of the present invention provides a mobility management function entity, which has a function of implementing a behavior of a mobility management function entity in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the mobility management function entity includes a processor configured to support the mobility management function entity to perform corresponding functions in the above methods. Further, the mobility management function entity may further include a communication interface for supporting communication between the mobility management function entity and the session management function entity, the terminal, or other network elements. Further, the mobility management function entity may further include a memory for coupling with the processor, which stores program instructions and data necessary for the mobility management function entity.
  • an embodiment of the present invention provides a session management function entity, where the session management function is implemented.
  • the body has the function of realizing the behavior of the session management function entity in the above method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the session management function entity includes a processor configured to support the session management function entity to perform corresponding functions in the above methods. Further, the session management function entity may further include a communication interface for supporting communication between the session management function entity and the mobility management function entity or other network elements. Further, the session management function entity may further include a memory for coupling with the processor, which stores program instructions and data necessary for the session management function entity.
  • the embodiment of the present invention provides a terminal, which can implement the functions performed by the terminal in the foregoing method design, and the functions can be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the terminal includes a processor and a transceiver configured to support the terminal to perform corresponding functions in the above methods.
  • the transceiver is configured to support communication between the terminal and a mobility management function entity, an access node, or other network element.
  • the terminal can also include a memory for coupling with the processor that retains the program instructions and data necessary for the terminal.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the foregoing mobility management function entity, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing the computer software instructions used for the session management function entity, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing the above-mentioned computer software instructions for a terminal, which includes a program designed to execute the above aspects.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a mobility management function entity in the method design described above.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a session management function entity in the method design described above.
  • embodiments of the present invention provide a computer program product comprising instructions that, when executed by a computer, cause a computer to perform functions performed by a terminal in the method design described above.
  • an embodiment of the present invention provides a communication system, where the system includes the mobility management function entity and the session management function entity, or the system includes the mobility management function entity, Session management functional entities and terminals.
  • the mobility management function entity can obtain the PDU session activation request including the identifier of the PDU session and the identifier of the terminal, and send the PDU session activation request to the session management function entity. Thereby the PDU session is activated. Therefore, the solution of the embodiment of the present invention can activate the PDU session on demand without activating all PDU sessions with established connections, thereby reducing signaling interaction between the terminal and the network, thereby reducing network load and saving power of the terminal. .
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a session activation method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of a session registration method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication of another session activation method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of another session activation method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of a session processing method according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of communication of another session processing method according to an embodiment of the present invention.
  • FIG. 8a is a schematic structural diagram of a mobility management function entity according to an embodiment of the present invention.
  • FIG. 8b is a schematic structural diagram of another mobility management function entity according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a session management function entity according to an embodiment of the present disclosure.
  • FIG. 9b is a schematic structural diagram of another session management function entity according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 10b is a schematic structural diagram of another terminal according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention.
  • the network architecture includes: a core network control plane function entity 101, a terminal 102, an access node 103, a user plane function entity 104, and a data network 105.
  • the core network control plane function entity 101 includes: an MM function.
  • the entity 101a, the SM function entity 101b, the policy management function entity 101c, and the user data management function entity 101d is first described below with reference to FIG.
  • the network architecture includes: a core network control plane function entity 101, a terminal 102, an access node 103, a user plane function entity 104, and a data network 105.
  • the core network control plane function entity 101 includes: an MM function.
  • the entity 101a, the SM function entity 101b, the policy management function entity 101c, and the user data management function entity 101d includes: an MM function.
  • the MM function entity is responsible for the connection between the terminal and the control plane of the core network, and the maintenance and control of the connection between the access node (AN) and the control plane of the core network, and the network access control of the terminal, and the terminal.
  • Network location management and terminal reachability management is responsible for the connection between the terminal and the control plane of the core network, and the maintenance and control of the connection between the access node (AN) and the control plane of the core network, and the network access control of the terminal, and the terminal.
  • the SM function entity is responsible for notifying the MM function entity of the requirement of the control plane connection of the terminal, so that the MM function entity controls the control plane connection of the terminal according to the requirements of the SM function entity.
  • the SM functional entity is also responsible for managing and maintaining the PDU data connection of the terminal, and establishing context information of the data connection for the terminal.
  • the SM signaling sent by the SM function entity to the terminal and the AN is delivered to the terminal and the access node through the MM functional entity.
  • Subscriber Data Management (SDM) functional entity responsible for saving and managing subscription data of contracted users.
  • the subscription data of the subscription user may include the identifier of the subscription user, the key used by the subscription user to authenticate the terminal when the terminal accesses the network, and the information of the network service that the subscription user can use.
  • the user data management function entity provides the subscription data of the subscription user to the MM function entity when the terminal accesses the network, so that the MM function entity can perform terminal authentication, access control, and the like on the terminal according to the subscription data of the user.
  • the policy management function entity which may also be referred to as a policy control function entity, is used to determine a quality of service (QoS) policy and a charging rule policy of the PDU session connection when establishing a PDU session connection for the terminal.
  • QoS quality of service
  • the policies are provided to the SM functional entities, so that the SM functional entities further manage the PDU session connections according to the policies.
  • the terminal involved in the embodiments of the present invention may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment, UE), Mobile Station (MS), Terminal (Terminal), Terminal Equipment (Terminal Equipment) and so on.
  • UE User Equipment
  • MS Mobile Station
  • Terminal Terminal
  • Terminal Equipment Terminal Equipment
  • the embodiments of the present invention are Detailed instructions in one step.
  • an embodiment of the present invention provides a session activation method, and a mobility management function entity, a session management function entity, a terminal, and a system based on the method.
  • the method includes: the mobility management function entity acquires a PDU session activation request of the terminal, the PDU session activation request includes an identifier of the PDU session and an identifier of the terminal, the PDU session activation request is used to request activation of the PDU session; and the mobility management function entity is in the session
  • the management function entity sends a PDU session activation request; after receiving the PDU session activation request, the session management function entity activates the PDU session according to the PDU session activation request.
  • the mobility management function entity can obtain a PDU session activation request including an identifier of the PDU session and an identifier of the terminal, and send the PDU session activation request to the session management function entity, thereby activating the PDU session. Therefore, the solution of the embodiment of the present invention can activate the PDU session on demand without activating all PDU sessions with established connections, thereby reducing signaling interaction between the terminal and the network, thereby reducing network load and saving power of the terminal. .
  • FIG. 2 is a schematic diagram of communication of a session activation method according to an embodiment of the present invention. As shown in FIG. 2, the method includes sections S201 to S203.
  • the mobility management function entity acquires a PDU session activation request of the terminal, where the PDU session activation request includes an identifier of the PDU session and an identifier of the terminal.
  • the PDU session activation request is used to activate the PDU session.
  • the mobility management function entity may obtain the PDU session activation request of the terminal in one of the following ways:
  • the first mode the mobility management function entity may receive a control plane connection activation request from the terminal, and the control plane connection activation request includes the PDU session activation request.
  • the control plane connection is in an idle state, and the terminal needs to activate the control plane connection when the PDU session needs to be activated.
  • the control plane connection activation request carries the activation request of the PDU session, which saves control signaling. s expenses.
  • the mobility management function entity can receive the PDU session activation request from the terminal.
  • the S406 portion of Figure 4 below uses this approach.
  • the control plane is already connected.
  • the PDU session activation request may be directly sent to the mobility management function entity to save control signaling overhead.
  • the mobility management function entity may obtain the PDU session activation request of the terminal by using other methods, which is not limited in the embodiment of the present invention.
  • the identifier of the foregoing terminal is used to identify the terminal, and the identifier of the PDU session is used to identify the PDU session.
  • the mobility management function entity sends the PDU session activation request to the session management function entity.
  • the mobility management function entity maintains a binding relationship between the identity of the terminal, the identity of the PDU session, and the identity of the session management function entity.
  • the session management function entity identified by the identifier of the session management function entity may be selected according to the identifier of the PDU session, the identifier of the terminal, and the binding relationship.
  • the embodiment of the present invention may first implement the PDU session registration method shown in FIG. 3 below, and the mobility management function entity may save the foregoing binding in the PDU session registration method. The relationship can be seen in detail in FIG.
  • the session management function entity activates the PDU session according to the PDU session activation request.
  • the mobility management function entity may also receive a handover request from the target access node, the handover request carrying an identity of the terminal and an identity of the target access node.
  • the handover request is used to request that the terminal be handed over from the source access node to the target access node.
  • the mobility management function entity may send a mobility event of the terminal to the session management function entity, where the mobility event includes an identifier of the terminal and an identifier of the target access node.
  • the session management function entity may determine at least one PDU session corresponding to the identifier of the terminal; when the at least one PDU session is an idle state PDU session, the session management function entity may determine whether it is required Updating the context of the at least one PDU session; or, when the at least one PDU session is an active PDU session, the session management function entity may notify the terminal and the target access node to update the context of the at least one PDU session.
  • the at least one PDU session corresponding to the identifier of the terminal may be in an idle state or an active state.
  • the solution in this example may be different according to the state of the at least one PDU session. deal with.
  • the at least one PDU session is an idle PDU session
  • the context of the at least one PDU session includes an identifier of the first user plane function entity
  • the session management function entity may determine whether the Updating the context of the at least one PDU session: The session management function entity may determine whether to update the context of the at least one PDU session according to the service area of the target access node and the service area list of the first user plane function entity.
  • the session management function entity determines that the context of the at least one PDU session needs to be updated; or if the service area of the target access node is In the service area list of the first user plane functional entity, the session management function entity determines that the context of the at least one PDU session does not need to be updated.
  • the session management function entity may further send a release message to the first user plane function entity, where the release message is used to indicate that the first user plane function entity releases at least A configuration resource of a PDU session; and selecting a second user plane functional entity for the terminal. And/or, the session management function entity may further send a PDU session update message to the mobility management function entity, where the PDU session update message is used to update the context of the at least one PDU session.
  • the mobility management function entity is represented by MM
  • the session management function entity is represented by the SM
  • the user plane function entity is represented by the UP
  • the access node is represented by the AN.
  • the solution of the embodiment of the present invention is described.
  • FIG. 3 is a schematic diagram of communication of a session registration method according to an embodiment of the present invention.
  • the method shown in Figure 3 can be performed prior to the method shown in Figure 2.
  • the session registration method as shown in FIG. 3 includes the S301-S304 part.
  • the establishment process of the PDU session is performed between the terminal, the AN, the MM, the SM, and the UP.
  • the SM sends a PDU session registration request of the terminal to the MM.
  • the foregoing PDU session registration request carries the identifier of the terminal, the identifier of the PDU session, and the identifier of the SM.
  • the identifier of the PDU session is used to distinguish different PDU sessions.
  • the PDU session of one service type uniquely corresponds to the identifier of one PDU session.
  • the identifier of the SM is used to identify the session management function entity serving the terminal.
  • the MM saves the binding relationship between the identifier of the terminal, the identifier of the PDU session, and the identifier of the SM.
  • the MM sends a response message to the PDU session registration request to the SM.
  • each PDU session uniquely corresponds to the identifier of one PDU session, and the MM function entity can save the identity of the terminal, the identifier of the PDU session, and the binding relationship between the SM functional entities, thereby facilitating the MM function and the SM.
  • a terminal establishes a data connection with a network side through a Packet Date Network (PDN) connection.
  • PDN Packet Date Network
  • the state of the PDN connection of the terminal is synchronized with the state of the control plane connection, and the states of the two are represented by the same connection state machine, for example, an Evolved packet system connection management (ECM) connection state representation.
  • ECM Evolved packet system connection management
  • the idle state may be represented as an ECM Idle state
  • the connected state may be represented as an ECM Connected state.
  • the terminal in the ECM_Idle state triggers the activation of the PDN connection while activating the control plane connection through the service request.
  • the terminal After the mobility management function and the session management function are separated, the terminal establishes a data connection with the network side through the PDU session.
  • the state of the control plane connection is maintained by the MM, where the state of the control plane connection includes the control plane idle state and the control plane connection state.
  • the state of the PDU session is maintained by the SM, where the state of the PDU session includes an idle state and an active state.
  • the control plane idle state can be represented as CM_Idle state
  • the control plane connection state can be represented as CM_Connected state
  • the idle state of the PDU session can be represented as SM_Idle state
  • the active state of the PDU session can be represented as SM_Active state.
  • FIG. 4 is a schematic diagram of communication of another session activation method according to an embodiment of the present invention. As shown in FIG. 4, the method includes parts S401-S408.
  • the terminal establishes a Radio Resource Control (RRC) connection with the AN.
  • RRC Radio Resource Control
  • the terminal After the terminal decides to activate the PDU session, the terminal establishes an RRC connection with the AN.
  • the terminal sends a CP connection activate request to the MM.
  • the MM sends a configuration control plane connection message to the AN, carrying the parameters of the configuration AN and the control plane connection activation response.
  • the AN sends a control plane connection activation response to the terminal.
  • the AN sends an acknowledgment control plane connection configuration completion response to the MM.
  • the terminal sends a PDU session activation request to the MM, the PDU session activation request carrying the identity of the terminal and the identity of the PDU session.
  • the MM sends the above PDU session activation request to the SM.
  • the MM finds the identifier of the terminal and the identifier of the SM corresponding to the identifier of the PDU session according to the identifier of the saved terminal, the identifier of the SM, and the identifier of the PDU session, and sends the PDU session activation request.
  • the SM corresponding to the identifier of the SM.
  • the SM sends a PDU Session Activation Response to the MM.
  • the SM sends a PDU session activation response to the MM.
  • the MM sends a PDU session activation response to the terminal.
  • the terminal can learn that the PDU session is activated.
  • FIG. 5 is a schematic diagram of communication of another session activation method according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 4 can be referred to the detailed description in FIG. 4, and details are not described herein.
  • the method includes portions S501-S508.
  • the S501 part is the same as or similar to the S401 part
  • the S503-S505 parts are the same or similar to the S403-S405 parts
  • the S506-S508 parts are the same or similar to the S407-S409 parts respectively.
  • 5 is different from FIG. 4 in that, in the S502 part, the control plane connection activation request sent by the terminal to the MM carries the PDU session activation request; the behavior of the S406 part of FIG. 4 is not performed in the method shown in FIG. 5.
  • the PDU session activation request in addition to the identifier of the carrying terminal, the PDU session activation request carries the identifier of the PDU session, and can distinguish different PDU sessions of the terminal. Therefore, when the PDU session is activated, the solution of the embodiment of the present invention can activate the corresponding PDU session as needed according to the identifier of the PDU session. For example, the PDU session of a specific service type can be activated as needed.
  • the terminal may switch between different ANs.
  • the terminal switches, it is now Some solutions require processing all data connections to the terminal.
  • the PDU session corresponding to the terminal may be in an idle state or an active state, and may also include an idle state and an active state PDU session.
  • the existing solution cannot implement an idle state PDU session or activation. Differentiated processing of PDU sessions.
  • the embodiments of the present invention provide a session processing method, and a mobility management function entity, a session management function entity, a terminal, and a system based on the method.
  • the method includes: a mobility management function entity receiving a handover request from a target access node, the handover request carrying an identifier of the terminal and an identifier of the target access node, wherein the handover request is used to request to switch the terminal from the source access node to the target interface An ingress node; the mobility management function entity sends a mobility event of the terminal to the session management function entity, where the mobility event includes an identifier of the terminal and an identifier of the target access node; the session management function entity determines at least one PDU session corresponding to the identifier of the terminal; When the at least one PDU session is an idle state PDU session, the session management function entity determines whether it is necessary to update the context of the at least one PDU session; or, when the at least one PDU session is an active state PDU session, the session
  • the at least one PDU session is an idle state PDU session
  • the context of the at least one PDU session may include an identifier of the first user plane function entity
  • the session management function entity may be according to the service area of the target access node and the A list of service areas of a user plane functional entity determining whether the context of the at least one PDU session needs to be updated.
  • the session management function entity determines that the context of the at least one PDU session needs to be updated; or if the service area of the target access node is In the service area list of the first user plane functional entity, the session management function entity determines that the context of the at least one PDU session does not need to be updated.
  • the session management function entity may further send a release message to the first user plane function entity, where the release message is used to indicate that the first user plane function entity releases at least A configuration resource of a PDU session; and selecting a second user plane functional entity for the terminal. And/or, the session management function entity may further send a PDU session update message to the mobility management function entity, where the PDU session update message is used to update the context of the at least one PDU session.
  • the mobility management function entity may also send the PDU session update message to the terminal.
  • the terminal from the mobility tube
  • the function entity may update the context of the at least one PDU session according to the PDU session update message.
  • the at least one PDU session is an idle state PDU session.
  • the session processing method may be executed after the method shown in FIG. 2 is executed, or the session processing method may be directly executed without executing the method shown in FIG. 2 .
  • the mobility management function entity is represented by MM
  • the session management function entity is represented by SM
  • the first user plane function entity is represented by UP1
  • the second user plane function entity is represented by UP2
  • the source access node is represented by the source AN.
  • the AN represents a target access node, and the solution of the embodiment of the present invention is described.
  • FIG. 6 shows a session processing method in which the PDU session is in an idle state in the case where the terminal is to be changed, and the PDU session is in an idle state;
  • FIG. 7 shows a type in which the terminal moves, and in the case where the AN is to be changed, the PDU session is in an active state. Session processing method.
  • FIG. 6 is a schematic diagram of communication of a session processing method according to an embodiment of the present invention. As shown in FIG. 6, the flow includes sections S601 to S608.
  • the target AN sends a handover request of the terminal to the MM, and the handover request of the terminal carries the identifier of the terminal and the identifier of the target AN.
  • the handover request may be a path switch request or the like.
  • the terminal moves and will switch from the source AN to the target AN.
  • the identifier of the terminal is used to identify the terminal, and the identifier of the target AN is used to identify the target AN.
  • the MM sends a mobile event of the terminal to the SM, the mobile event including the identifier of the terminal and the identifier of the target AN.
  • the SM determines whether the PDU session in the idle state needs to be updated.
  • the SM sends a context update message of the idle state PDU session to the MM; the MM sends a context update message of the PDU session to the terminal.
  • the terminal updates the PDU session context according to the PDU session context update message.
  • the PDU session context may include an identifier of the terminal, an identifier of the PDU session, an identifier of the SM corresponding to the PDU session, or a network address allocated by the UP for the terminal, and a connection status of the PDU session, where the PDU session is The connection status includes an idle state or an active state.
  • the terminal sends a context update confirmation of the PDU session to the MM, and the MM sends a context update confirmation of the PDU session to the SM.
  • the SM sends a configuration UP instruction to UP1.
  • the UP command is configured to release UP1 as the resource configured by the terminal, and the identifier of the terminal is deleted from the list of the UP1 service.
  • the SM sends a configuration UP command to UP2.
  • the SM selects UP2, which provides services for the terminal.
  • the configuration command sent to the UP2 includes information such as the identifier of the terminal, the identifier of the PDU session, the QoS corresponding to the PDU session, and the charging configuration.
  • the SM or UP corresponding to the PDU session may be reallocated for the network address of the terminal.
  • the network address is a network address used by the terminal to receive and send data.
  • the network address type may be Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6, IPv6.
  • the SM sends a terminal mobile event response to the MM.
  • the MM sends a terminal handover confirmation to the target AN.
  • the processing of the PDU session in the idle state is avoided; while the terminal moves in the prior art, the AN will participate in the processing of all the PDU sessions in the terminal, thereby saving network resources and improving.
  • FIG. 7 is a schematic diagram of communication of another session processing method according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 6 can refer to the detailed description in FIG. 6 , and details are not described herein.
  • the method includes portions S701-S705.
  • the parts of S701-S702 are the same or similar to the parts of S601-S302, respectively, and the parts of S704-S705 are the same or similar to the parts of S607-S608 respectively.
  • each network element such as a mobility management function entity, a session management function entity, a terminal, etc.
  • each network element such as a mobility management function entity, a session management function entity, a terminal, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the functional unit of the mobility management function entity, the session management function entity, the terminal, and the like according to the foregoing method example.
  • each functional unit may be divided according to each function, or two or more functions may be used.
  • the functions are integrated in one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8a shows a possible structural diagram of the mobility management function entity involved in the above embodiment.
  • the mobility management function entity includes a processing unit 802 and a communication unit 803.
  • the processing unit 802 is configured to control and manage the actions of the mobility management function entity.
  • the processing unit 802 is configured to support the mobility management function entity to perform processes S201 and S202 in FIG. 2, processes S301, S303, and S304 in FIG. Processes S403, S407, and S409 in FIG. 4, processes S503, S506, and S508 in FIG. 5, processes S602, S604, S605, and S608 in FIG. 6, processes S702, S703, and S705 in FIG. 7, and/or Other processes for the techniques described herein.
  • the communication unit 803 is configured to support communication between the mobility management function entity and other network entities, for example, with the terminal, the access node, the session management function entity, the user data management function entity, the policy management function entity, etc. shown in FIG. Communication.
  • the mobility management function entity may further include a storage unit 801 for storing program codes and data of the mobility management function entity.
  • the processing unit 802 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be real A combination of computing functions, for example, includes one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 803 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage unit 801 can be a memory.
  • the mobility management function entity involved in the embodiment of the present invention may be the mobility management function entity shown in FIG. 8b.
  • the mobility management function entity 810 includes a processor 812, a communication interface 811, and a memory 813.
  • the mobility management function entity 810 may also include a bus 814.
  • the processor 812, the communication interface 811, and the memory 813 may be connected to each other through a bus 814.
  • the bus 814 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 814 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8b, but it does not mean that there is only one bus or one type of bus.
  • FIG. 9a shows a possible structural diagram of the session management function entity involved in the above embodiment.
  • the session management function entity includes a processing unit 902 and a communication unit 903.
  • the processing unit 902 is configured to control and manage the action of the session management function entity.
  • the processing unit 902 is configured to support the session management function entity to perform the process S203 in FIG. 2, the processes S301 and S302 in FIG. 3, and the process in FIG. S408, process S507 in FIG. 5, processes S603, S604, S606a, S606b, and S607 in FIG. 6, processes S703 and S704 in FIG. 7, and/or other processes for the techniques described herein.
  • the communication unit 903 is configured to support communication between the session management function entity and other network entities, for example, with the mobility management function entity, the user data management function entity, the policy management function entity, the user plane function entity, etc. shown in FIG. Communication.
  • the session management function entity may further include a storage unit 901 for storing program codes and data of the session management function entity.
  • the processing unit 902 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 903 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the storage unit 901 can be a memory.
  • the session management function entity involved in the embodiment of the present invention may be the session management function entity shown in FIG. 9b.
  • the session management function entity 910 includes a processor 912, a communication interface 911, and a memory 913.
  • the session management function entity 910 may further include a bus 914.
  • the processor 912, the communication interface 911, and the memory 913 may be connected to each other through a bus 914; the bus 914 may be a PCI bus or an EISA bus or the like.
  • the bus 914 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9b, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10a shows a possible structural diagram of the terminal involved in the above embodiment.
  • the terminal includes a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is configured to perform control management on the action of the terminal.
  • the processing unit 1002 is configured to support the terminal to perform the process S301 in FIG. 3, the processes S401, S402, and S406 in FIG. 4, and the processes S501 and S502 in FIG. Process S605 in FIG. 6, process S703 in FIG. 7, and/or other processes for the techniques described herein.
  • the communication unit 1003 is configured to support communication between the terminal and other network entities, such as communication with the access node, mobility management function entity, etc., shown in FIG.
  • the terminal may further include a storage unit 1001 for storing program codes and data of the terminal.
  • the processing unit 1002 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1003 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces.
  • the storage unit 1001 may be a memory.
  • the terminal involved in the embodiment of the present invention may be the terminal shown in FIG. 10b.
  • FIG. 10b shows a simplified schematic diagram of one possible design structure of a terminal involved in an embodiment of the present invention.
  • the terminal 1000 includes a transmitter 1011, a receiver 1012, and a processor 1013.
  • the processor 1013 may also be a controller, and is represented as "controller/processor 1013" in FIG. 10b.
  • the terminal 1010 may further include a modem processor 1015, where the modem processor 1015 An encoder 1016, a modulator 1017, a decoder 1018, and a demodulator 1019 can be included.
  • the transmitter 1011 conditions (eg, analog transforms, filters, amplifies, upconverts, etc.) the output samples and generates an uplink signal that is transmitted via an antenna to the AN described in the above embodiments. .
  • the antenna receives the downlink signal transmitted by the base station in the above embodiment.
  • Receiver 1012 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples.
  • encoder 1018 receives traffic data and signaling messages to be transmitted on the uplink and processes (e.g., formats, codes, and interleaves) the traffic data and signaling messages.
  • Modulator 1018 further processes (e.g., symbol maps and modulates) the encoded traffic data and signaling messages and provides output samples.
  • Demodulator 1019 processes (e.g., demodulates) the input samples and provides symbol estimates.
  • the decoder 1018 processes (e.g., deinterleaves and decodes) the symbol estimates and provides decoded data and signaling messages that are sent to the terminal 1010.
  • Encoder 1016, modulator 1017, demodulator 1019, and decoder 1018 may be implemented by a composite modem processor 1015. These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems). It should be noted that, when the terminal 1010 does not include the modem processor 1015, the above functions of the modem processor 1015 may also be completed by the processor 1013.
  • the terminal 1010 may further include a memory 1014 for storing program codes and data for the terminal 1010.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a mobility management functional entity, a session management functional entity, or a terminal.
  • the processor and the storage medium may also exist as discrete components in a mobility management function entity, a session management function entity, or a terminal.
  • the present invention is implemented
  • the functions described in the examples can be implemented in hardware, software, firmware or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

本发明实施例提供一种会话激活方法及移动性管理功能实体、会话管理功能实体、终端和系统。该方法包括：移动性管理功能实体获取终端的协议数据单元PDU会话激活请求，该PDU会话激活请求包括PDU会话的标识和该终端的标识，该PDU会话激活请求用于请求激活该PDU会话；该移动性管理功能实体向会话管理功能实体发送该PDU会话激活请求；会话管理功能实体根据该PDU会话激活请求激活该PDU会话。本发明实施例能够通过在PDU会话激活请求中增加PDU会话的标识，使得终端能够按需激活PDU会话，从而能够减少终端与网络之间的信令交互，有利于降低网络负荷和节约终端的电量。

Description

一种会话激活方法及装置和系统 技术领域
本发明实施例涉及通信技术领域，尤其涉及一种会话激活方法及装置和系统。
背景技术
目前，演进分组核心网络(Evolved Packet Core，EPC)采用基于网元(Network Element，NE)的架构，其中，典型的NE包括：移动性管理实体(Mobility Management Entity，MME)、服务网关(Serving Gateway，S-GW)及分组数据网络网关(Packet Data Network Gateway，P-GW)等。然而，随着商业模式的拓展以及技术的发展，用户对于业务的需求随之发生变化。EPC所提供的网络功能(Network Function，NF)是固化并分散在各个NE中的，当需要引入新的NF来支持用户的需求时，EPC需要重新定义和设计NE的处理逻辑和流程交互。对设备商来说，这种重新设计的方式开发周期长且成本高；对于网络运营商来说，这种重新设计的方式使得网络运营商不能及时发布新的网络服务。
在这种情况下，核心网架构中的NE(例如MME或S-GW)按照功能的类别(如：认证和安全功能、会话管理功能、移动性管理功能及接入控制功能等)被拆分为不同的NF组件，不同功能由对应的NF组件实现。不同NF组件之间功能解耦，且对于某一NF组件而言，其可以通过所支持的接口和其它NF组件进行交互以完成有关网络服务。
在实践中，核心网架构中的NE可以实现移动性管理(Mobility Management，MM)功能和会话管理(Session Management，SM)功能的分离，其中，MM功能由MM功能实体完成，SM功能由SM功能实体完成。然而，MM功能和SM分离后，对于一个终端而言，可能会建立多个协议数据单元(Protocol Date Unit，PDU)会话，且这些PDU会话会被同时激活。这使得终端与网络之间的信令交互很多，从而导致网络负荷较高以及终端的电量消耗较快。
发明内容
为了解决上述问题，本发明实施例提供一种会话激活的方法及移动性管理功能实体、会话管理功能实体、终端和系统，以期缓解现有方案中终端与网络之间信令交互过多的问题。
一方面，本发明实施例提供一种会话激活方法，该方法包括：移动性管理功能实体获取终端的协议数据单元PDU会话激活请求，该PDU会话激活请求包括PDU会话的标识和终端的标识，该PDU会话激活请求用于请求激活该PDU会话；移动性管理功能实体向会话管理功能实体发送该PDU会话激活请求；会话管理功能实体根据该PDU会话激活请求激活该PDU会话。
本发明实施例中，移动性管理功能实体能够获取包括PDU会话的标识和终端的标识的PDU会话激活请求，并向会话管理功能实体发送该PDU会话激活请求，从而激活该PDU会话。因此，本发明实施例的方案能够按需激活PDU会话，而不需要激活所有已建立连接的PDU会话，从而能够减少终端与网络之间的信令交互，有利于降低网络负荷和节约终端的电量。
在一个可能的设计中，移动性管理功能实体可以通过以下方式之一获取终端的PDU会话激活请求：第一种方式，移动性管理功能实体可以从终端接收控制面连接激活请求，控制面连接激活请求包括该PDU会话激活请求；第二种方式，移动性管理功能实体可以从终端接收该PDU会话激活请求。
在一种可能的实施方式中，终端向移动性管理功能实体发送上述控制面连接激活请求或PDU会话激活请求之前，终端还可以生成该PDU会话激活请求。
在一个可能的设计中，移动性管理功能实体中可以保存有终端的标识、PDU会话的标识和会话管理功能实体的标识之间的绑定关系；移动性管理功能实体向会话管理功能实体发送PDU会话激活请求之前，还可以根据PDU会话的标识、终端的标识以及上述绑定关系，选择上述会话管理功能实体的标识所标识的会话管理功能实体。
在一个可能的设计中，移动性管理功能实体还可以从目标接入节点接收切换请求，切换请求携带终端的标识和目标接入节点的标识，其中，切换请求用于请求将终端从源接入节点切换到目标接入节点；然后，移动性管理功能实体可以向会话管理功能实体发送终端的移动事件，该移动事件包括终端的标识和目标接入节点的标识。
在这个设计中，会话管理功能实体从移动性管理功能实体接收终端的移动 事件后，可以确定终端的标识对应的至少一个PDU会话；当该至少一个PDU会话为空闲态PDU会话时，会话管理功能实体可以确定是否需要更新该至少一个PDU会话的上下文；或者，当该至少一个PDU会话为激活态PDU会话时，会话管理功能实体可以通知终端和目标接入节点更新该至少一个PDU会话的上下文。
在一种可能的实施方式中，上述至少一个PDU会话为空闲态PDU会话，上述至少一个PDU会话的上下文中包括第一用户面功能实体的标识，会话管理功能实体可以根据目标接入节点的服务区域和第一用户面功能实体的服务区域列表，确定是否需要更新该至少一个PDU会话的上下文。例如，若目标接入节点的服务区域不在第一用户面功能实体的服务区域列表中，则会话管理功能实体可以确定需要更新该至少一个PDU会话的上下文；或者，若目标接入节点的服务区域在第一用户面功能实体的服务区域列表中，则会话管理功能实体可以确定不需要更新该至少一个PDU会话的上下文。
进一步的，会话管理功能实体在确定需要更新至少一个PDU会话的上下文之后，还可以向第一用户面功能实体发送释放消息，释放消息用于只是第一用户面功能释放该至少一个PDU会话的配置资源；并为终端选择第二用户面功能实体。和/或，会话管理功能实体还可以向移动性管理功能实体发送PDU会话更新消息，PDU会话更新消息用于更新该至少一个PDU会话的上下文。对应的，移动性管理功能实体从会话管理功能实体接收PDU会话更新消息后，还可以向终端发送该PDU会话更新消息。终端从移动性管理功能实体接收该PDU会话更新消息后，可以根据该PDU会话更新消息，更新该至少一个PDU会话的上下文。
另一方面，本发明实施例提供一种会话处理方法，该方法包括：移动性管理功能实体从目标接入节点接收切换请求，切换请求携带终端的标识和目标接入节点的标识，其中，切换请求用于请求将终端从源接入节点切换到目标接入节点；移动性管理功能实体向会话管理功能实体发送终端的移动事件，移动事件包括终端的标识和目标接入节点的标识；会话管理功能实体确定终端的标识对应的至少一个PDU会话，当该至少一个PDU会话为空闲态PDU会话时，会话管理功能实体确定是否需要更新该至少一个PDU会话的上下文；或者，当该至少一个PDU会话为激活态PDU会话时，会话管理功能实体通知终端和目标 接入节点更新该至少一个PDU会话的上下文。
在一个可能的设计中，上述至少一个PDU会话为空闲态PDU会话，该至少一个PDU会话的上下文中可以包括第一用户面功能实体的标识，会话管理功能实体可以根据目标接入节点的服务区域和第一用户面功能实体的服务区域列表，确定是否需要更新该至少一个PDU会话的上下文。例如，若目标接入节点的服务区域不在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定需要更新该至少一个PDU会话的上下文；或者，若目标接入节点的服务区域在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定不需要更新该至少一个PDU会话的上下文。
在一个可能的设计中，会话管理功能实体确定需要更新至少一个PDU会话的上下文之后，会话管理功能实体还可以向第一用户面功能实体发送释放消息，释放消息用于指示第一用户面功能实体释放至少一个PDU会话的配置资源；并为终端选择第二用户面功能实体。和/或，会话管理功能实体还可以向移动性管理功能实体发送PDU会话更新消息，PDU会话更新消息用于更新该至少一个PDU会话的上下文。
在一种可能的实施方式中，移动性管理功能实体从会话管理功能实体接收PDU会话更新消息后，还可以向终端发送该PDU会话更新消息。对应的，终端从移动性管理功能实体接收该PDU会话更新消息后，可以根据该PDU会话更新消息，更新所述至少一个PDU会话的上下文。
又一方面，本发明实施例提供一种移动性管理功能实体，该移动性管理功能实体具有实现上述方法设计中移动性管理功能实体行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，移动性管理功能实体包括处理器，所述处理器被配置为支持移动性管理功能实体执行上述方法中相应的功能。进一步的，移动性管理功能实体还可以包括通信接口，所述通信接口用于支持移动性管理功能实体与会话管理功能实体、终端或其他网元之间的通信。进一步的，移动性管理功能实体还可以包括存储器，所述存储器用于与处理器耦合，其保存移动性管理功能实体必要的程序指令和数据。
又一方面，本发明实施例提供一种会话管理功能实体，该会话管理功能实 体具有实现上述方法设计中会话管理功能实体行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，会话管理功能实体包括处理器，所述处理器被配置为支持会话管理功能实体执行上述方法中相应的功能。进一步的，会话管理功能实体还可以包括通信接口，所述通信接口用于支持会话管理功能实体与移动性管理功能实体或其他网元之间的通信。进一步的，会话管理功能实体还可以包括存储器，所述存储器用于与处理器耦合，其保存会话管理功能实体必要的程序指令和数据。
又一方面，本发明实施例提供了一种终端，该终端可以实现上述方法设计中终端所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该终端的结构中包括处理器和收发器，该处理器被配置为支持该终端执行上述方法中相应的功能。该收发器用于支持该终端与移动性管理功能实体、接入节点或其他网元之间的通信。该终端还可以包括存储器，该存储器用于与处理器耦合，其保存该终端必要的程序指令和数据。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于移动性管理功能实体所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于会话管理功能实体所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述用于终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中移动性管理功能实体所执行的功能。
再一方面，本发明实施例提供一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中会话管理功能实体所执行的功能。
再一方面，本发明实施例提供一种计算机程序产品，其包含指令，当所述程序被计算机所执行时，该指令使得计算机执行上述方法设计中终端所执行的功能。
再一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的移动性管理功能实体和会话管理功能实体；或者，该系统包括上述方面所述的移动性管理功能实体、会话管理功能实体和终端。
相较于现有技术，本发明实施例的方案中，移动性管理功能实体能够获取包括PDU会话的标识和终端的标识的PDU会话激活请求，并向会话管理功能实体发送该PDU会话激活请求，从而激活该PDU会话。因此，本发明实施例的方案能够按需激活PDU会话，而不需要激活所有已建立连接的PDU会话，从而能够减少终端与网络之间的信令交互，有利于降低网络负荷和节约终端的电量。
附图说明
图1为本发明实施例提供的一种可能的网络架构的示意图；
图2为本发明实施例提供的一种会话激活方法的通信示意图；
图3为本发明实施例提供的一种会话注册方法的通信示意图；
图4为本发明实施例提供的另一种会话激活方法的通信示意图；
图5为本发明实施例提供的又一种会话激活方法的通信示意图；
图6为本发明实施例提供的一种会话处理方法的通信示意图；
图7为本发明实施例提供的另一种会话处理方法的通信示意图；
图8a为本发明实施例提供的一种移动性管理功能实体的结构示意图；
图8b为本发明实施例提供的另一种移动性管理功能实体的结构示意图；
图9a为本发明实施例提供的一种会话管理功能实体结构示意图；
图9b为本发明实施例提供的另一种会话管理功能实体的结构示意图；
图10a为本发明实施例提供的一种终端的结构示意图；
图10b为本发明实施例提供的另一种终端的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描 述。
下面首先结合图1对本发明实施例可能适用的网络架构进行介绍。图1为本发明实施例提供的一种可能的网络架构的示意图。如图1所示，该网络架构包括：核心网控制面功能实体101、终端102、接入节点103、用户面功能实体104以及数据网络105，其中，核心网控制面功能实体101包括：MM功能实体101a、SM功能实体101b、策略管理功能实体101c和用户数据管理功能实体101d。
MM功能实体负责终端和核心网控制面之间的连接，以及接入节点(Access Node，AN)和核心网控制面之间的连接的维护和控制，以及支持终端的网络接入控制、终端的网络位置管理以及终端的可达性管理等。
SM功能实体负责将该终端的控制面连接的需求通知给MM功能实体，从而MM功能实体按照SM功能实体的需求对终端的控制面连接进行控制。SM功能实体还负责终端的PDU数据连接的管理和维护，为终端建立数据连接的上下文信息。此外，SM功能实体发送给终端和AN的SM信令通过MM功能实体传递给终端和接入节点。
用户数据管理(Subscriber Data Management，SDM)功能实体，负责保存和管理签约用户的签约数据。其中，签约用户的签约数据可以包括签约用户的标识、签约用户使用终端接入网络时对终端进行认证的密钥和签约用户可以使用的网络业务的信息等。用户数据管理功能实体在终端接入网络时将签约用户的签约数据提供给MM功能实体，使MM功能实体可以根据用户的签约数据对终端进行终端认证、接入控制等。
策略管理功能实体，也可以称为策略控制(policy control)功能实体，用于在为终端建立PDU会话连接时确定该PDU会话连接的服务质量(Quality of Service，QoS)策略和计费规则策略等策略，并将这些策略提供给SM功能实体，使得SM功能实体进一步根据这些策略对上述PDU会话连接进行管理。
本发明实施例中所涉及到的终端可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile Station，MS)，终端(Terminal)，终端设备(Terminal Equipment)等等。为方便描述，上面提到的设备统称为终端。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进 一步详细说明。
现有方案中，MM功能和SM功能分离后，对于一个终端而言，可能会建立多个PDU会话，这些PDU会话会被同时激活。这使得终端与网络之间的信令交互很多，从而导致网络负荷较高以及终端的电量消耗较快。
有鉴于此，本发明实施例提供一种会话激活方法，和基于这个方法的移动性管理功能实体、会话管理功能实体、终端及系统。该方法包括：移动性管理功能实体获取终端的PDU会话激活请求，PDU会话激活请求包括PDU会话的标识和终端的标识，PDU会话激活请求用于请求激活该PDU会话；移动性管理功能实体向会话管理功能实体发送PDU会话激活请求；会话管理功能实体接收该PDU会话激活请求后，根据该PDU会话激活请求激活上述PDU会话。本发明实施例的方案中，移动性管理功能实体能够获取包括PDU会话的标识和终端的标识的PDU会话激活请求，并向会话管理功能实体发送该PDU会话激活请求，从而激活该PDU会话。因此，本发明实施例的方案能够按需激活PDU会话，而不需要激活所有已建立连接的PDU会话，从而能够减少终端与网络之间的信令交互，有利于降低网络负荷和节约终端的电量。
下面结合附图2对本发明实施例的方案进行说明。图2为本发明实施例提供的一种会话激活方法的通信示意图。如图2所示，该方法包括S201～S203部分。
在S201部分，移动性管理功能实体获取终端的PDU会话激活请求，PDU会话激活请求包括PDU会话的标识和终端的标识。
其中，该PDU会话激活请求用于激活上述PDU会话。
在一个示例中，移动性管理功能实体可以通过以下方式之一获取终端的PDU会话激活请求：
第一种方式：移动性管理功能实体可以从终端接收控制面连接激活请求，控制面连接激活请求包括该PDU会话激活请求。例如，下面图5中的S502部分采用了这种方式。这种情况下，控制面连接处于空闲态，终端需要激活该PDU会话时，会先激活控制面连接；此时，在控制面连接激活请求中携带该PDU会话的激活请求，节省了控制信令的开销。
第二种方式：移动性管理功能实体可以从终端接收PDU会话激活请求。例如，下面图4中的S406部分采用了这种方式。这种情况下，控制面连接已经处 于激活状态，终端需要激活该PDU会话时，可以直接向移动性管理功能实体发送该PDU会话激活请求，以节省控制信令的开销。
当然，移动性管理功能实体还可以通过其他方式获取终端的PDU会话激活请求，本发明实施例并不限定。
需要说明的是，上述终端的标识用于标识该终端，上述PDU会话的标识用于标识该PDU会话。
在S202部分，移动性管理功能实体向会话管理功能实体发送该PDU会话激活请求。
在一个示例中，移动性管理功能实体中保存有该终端的标识、该PDU会话的标识以及该会话管理功能实体的标识之间的绑定关系。移动性管理功能实体向会话管理功能实体发送上述PDU会话激活请求之前，可以根据上述PDU会话的标识、上述终端的标识以及该绑定关系，选择会话管理功能实体的标识所标识的会话管理功能实体。示例性的，在实施图2所示的会话激活方法之前，本发明实施例可以先实施下面图3所示的PDU会话注册方法，移动性管理功能实体可以在PDU会话注册方法中保存上述绑定关系，具体可见图3中的描述。
在S203部分，会话管理功能实体根据PDU会话激活请求，激活上述PDU会话。
在一个示例中，移动性管理功能实体还可以从目标接入节点接收切换请求，该切换请求携带该终端的标识和该目标接入节点的标识。其中，该切换请求用于请求将该终端从源接入节点切换到该目标接入节点。然后，移动性管理功能实体可以向会话管理功能实体发送终端的移动事件，该移动事件包括该终端的标识和该目标接入节点的标识。会话管理功能实体从移动性管理功能实体接收终端的移动事件后，可以确定终端的标识对应的至少一个PDU会话；当该至少一个PDU会话为空闲态PDU会话时，会话管理功能实体可以确定是否需要更新该至少一个PDU会话的上下文；或者，当该至少一个PDU会话为激活态PDU会话时，会话管理功能实体可以通知上述终端和上述目标接入节点更新该至少一个PDU会话的上下文。
本示例中，该终端的标识对应的至少一个PDU会话可能为空闲态，也可能为激活态，本示例的方案可以根据该至少一个PDU会话的状态来对该至少一个PDU会话的上下文进行不同的处理。
在一种可能的实施方式中，上述至少一个PDU会话为空闲态PDU会话，该至少一个PDU会话的上下文中包括第一用户面功能实体的标识，会话管理功能实体可以通过以下方式来确定是否需要更新该至少一个PDU会话的上下文：会话管理功能实体可以根据目标接入节点的服务区域和第一用户面功能实体的服务区域列表，来确定是否需要更新该至少一个PDU会话的上下文。例如，若目标接入节点的服务区域不在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定需要更新该至少一个PDU会话的上下文；或者，若目标接入节点的服务区域在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定不需要更新该至少一个PDU会话的上下文。
在一个示例中，会话管理功能实体确定需要更新至少一个PDU会话的上下文之后，会话管理功能实体还可以向第一用户面功能实体发送释放消息，释放消息用于指示第一用户面功能实体释放至少一个PDU会话的配置资源；并为终端选择第二用户面功能实体。和/或，会话管理功能实体还可以向移动性管理功能实体发送PDU会话更新消息，PDU会话更新消息用于更新该至少一个PDU会话的上下文。
下面将结合图3～图5，对本发明实施例的方案做进一步说明。图3～图5中，以MM表示移动性管理功能实体，SM表示会话管理功能实体，UP表示用户面功能实体，AN表示接入节点，对本发明实施例的方案进行描述。
图3为本发明实施例提供的一种会话注册方法的通信示意图。图3所示的方法可以在图2所示的方法之前执行。如图3所示的会话注册方法包括S301-S304部分。
在S301部分，在终端、AN、MM、SM和UP之间执行PDU会话的建立过程。
在S302部分，SM向MM发送终端的PDU会话注册请求。
上述PDU会话注册请求携带终端的标识，PDU会话的标识以及SM的标识。其中，PDU会话的标识用于对不同的PDU会话进行区分，例如一种业务类型的PDU会话唯一对应一个PDU会话的标识。SM的标识用于标识出服务于该终端的会话管理功能实体。
在S303部分，MM保存终端的标识、PDU会话的标识以及SM的标识之间的绑定关系。
在S304部分，MM向SM发送PDU会话注册请求的响应消息。
现有方案中，当MM功能和SM功能分离后，对于一个终端而言，可能会建立多个PDU会话。这些PDU会话由于类型不同等原因，可能由不同的SM功能实体进行处理，而不同的SM功能实体可能部署在不同的网络位置。这使得MM功能实体和SM功能实体之间、终端和网络之间的信令交互相当复杂。图3所示的方案中，每一个PDU会话唯一对应一个PDU会话的标识，MM功能实体能够保存终端的标识、PDU会话的标识和SM功能实体之间的绑定关系，从而便于MM功能和SM功能分离后，上述各个网元之间的信令交互。
目前，在EPC中，终端通过分组数据网络(Packet Date Network，PDN)连接与网络侧建立数据连接。终端的PDN连接的状态和控制面连接的状态同步，这二者的状态采用同一个连接状态机表示，例如采用演进分组系统连接管理(Evolved packet system Connection Management，ECM)连接状态表示。当ECM连接状态为空闲态时，PDN连接和控制面连接都处于空闲态；当ECM连接状态为连接态时，PDN连接和控制面连接都处于连接状态。其中，上述空闲态可以表示为ECM Idle态，上述连接态可以表示为ECM Connected态。处于ECM_Idle态的终端，在通过服务请求激活控制面连接的同时触发PDN连接的激活。
而移动性管理功能和会话管理功能分离后，终端通过PDU会话与网络侧建立数据连接。此时，控制面连接的状态由MM维护，这里控制面连接的状态包括控制面空闲态和控制面连接态。PDU会话的状态由SM维护，这里PDU会话的状态包括空闲态和激活态。其中，控制面空闲态可以表示为CM_Idle态，控制面连接态可以表示为CM_Connected态，PDU会话的空闲态可以表示为SM_Idle态，PDU会话的激活态可以表示为SM_Active态。
在图2所示方法的基础上，下面结合图4和图5，对本发明实施例的方案做进一步说明。其中，图4所示的方法中，当控制面连接处于CM_Idle态时，需要先激活控制面连接，然后激活PDU会话。图5所示的方法中，当控制面连接处于CM_Connected态时，可以直接激活PDU会话。
图4为本发明实施例提供的另一种会话激活方法的通信示意图，如图4所示，该方法包括S401-S408部分。
在S401部分，终端和AN建立无线资源控制(Radio Resource Control，RRC)连接。
终端决定激活PDU会话后，终端和AN建立RRC连接。
在S402部分，终端向MM发送控制面连接激活请求(CP connection activate request)。
在S403部分，MM向AN发送配置控制面连接消息，携带配置AN的参数和控制面连接激活响应。
在S404部分，AN向终端发送控制面连接激活响应。
在S405部分，AN向MM发送确认控制面连接配置完成响应。
在S406部分，终端向MM发送PDU会话激活请求，该PDU会话激活请求携带终端的标识和PDU会话的标识。
在S407部分，MM向SM发送上述PDU会话激活请求。
在一个示例中，MM根据保存的终端的标识、SM的标识以及PDU会话的标识的绑定关系，找到该终端的标识和PDU会话的标识所对应的SM的标识，并将PDU会话激活请求发送给该SM的标识对应的SM。
在S408部分，SM向MM发送PDU会话激活响应。
具体的，SM对该PDU会话的标识对应的PDU会话进行激活后，向MM发送PDU会话激活响应。
在S409部分，MM向终端发送PDU会话激活响应。
具体的，终端接收PDU会话激活响应后，能够获知上述PDU会话已激活。
图5为本发明实施例提供的又一种会话激活方法的通信示意图。图5中，与图4所示方法相同或相似的内容，可以参考图4中的详细描述，此处不做赘述。如图5所示，该方法包括S501-S508部分。其中，S501部分与S401部分相同或类似，S503～S505部分分别与S403～S405部分相同或类似，S506～S508部分分别与S407～S409部分相同或类似。图5与图4的不同之处在于：S502部分中，终端向MM发送的控制面连接激活请求中，携带PDU会话激活请求；图5所示方法中不用执行图4的S406部分的行为。
本发明实施例中，PDU会话激活请求中除携带终端的标识外，还携带PDU会话的标识，能够对终端的不同PDU会话进行区分。因此，本发明实施例的方案在进行PDU会话激活时，能够根据PDU会话的标识，按需激活对应的PDU会话，例如可以按照需要激活特定业务类型的PDU会话。
实践中，终端可能会在不同的AN之间进行切换。当终端发生切换时，现 有的方案需要对终端的所有数据连接进行处理。而移动性管理功能和会话管理功能分离后，终端对应的PDU会话可能处于空闲态或激活态，也可能同时包括空闲态和激活态的PDU会话，现有方案无法实现对空闲态PDU会话或激活态PDU会话的区别处理。
有鉴于此，本发明实施例提供一种会话处理方法，和基于这个方法的移动性管理功能实体、会话管理功能实体、终端和系统。该方法包括：移动性管理功能实体从目标接入节点接收切换请求，切换请求携带终端的标识和目标接入节点的标识，其中，切换请求用于请求将终端从源接入节点切换到目标接入节点；移动性管理功能实体向会话管理功能实体发送终端的移动事件，移动事件包括终端的标识和目标接入节点的标识；会话管理功能实体确定终端的标识对应的至少一个PDU会话；当该至少一个PDU会话为空闲态PDU会话时，会话管理功能实体确定是否需要更新该至少一个PDU会话的上下文；或者，当该至少一个PDU会话为激活态PDU会话时，会话管理功能实体通知终端和目标接入节点更新该至少一个PDU会话的上下文。
在一个示例中，上述至少一个PDU会话为空闲态PDU会话，该至少一个PDU会话的上下文中可以包括第一用户面功能实体的标识，会话管理功能实体可以根据目标接入节点的服务区域和第一用户面功能实体的服务区域列表，确定是否需要更新该至少一个PDU会话的上下文。例如，若目标接入节点的服务区域不在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定需要更新该至少一个PDU会话的上下文；或者，若目标接入节点的服务区域在第一用户面功能实体的服务区域列表中，则会话管理功能实体确定不需要更新该至少一个PDU会话的上下文。
在一个示例中，会话管理功能实体确定需要更新至少一个PDU会话的上下文之后，会话管理功能实体还可以向第一用户面功能实体发送释放消息，释放消息用于指示第一用户面功能实体释放至少一个PDU会话的配置资源；并为终端选择第二用户面功能实体。和/或，会话管理功能实体还可以向移动性管理功能实体发送PDU会话更新消息，PDU会话更新消息用于更新该至少一个PDU会话的上下文。
在这个示例中，移动性管理功能实体从会话管理功能实体接收PDU会话更新消息后，还可以向终端发送该PDU会话更新消息。对应的，终端从移动性管 理功能实体接收该PDU会话更新消息后，可以根据该PDU会话更新消息，更新所述至少一个PDU会话的上下文。其中，该至少一个PDU会话为空闲态PDU会话。
需要说明的是，本发明实施例中，可以在执行图2所示方法之后再执行上述会话处理方法，也可以在不执行图2所示方法的情况下，直接执行上述会话处理方法。
下面结合图6和图7，对上述会话处理方法做进一步说明。图6和图7中，以MM表示移动性管理功能实体，SM表示会话管理功能实体，UP1表示第一用户面功能实体，UP2表示第二用户面功能实体，源AN表示源接入节点，目标AN表示目标接入节点，对本发明实施例的方案进行描述。
图6示出了终端移动，将要变更AN的情况下，PDU会话处于空闲态的一种会话处理方法；图7示出了终端移动，将要变更AN的情况下，PDU会话处于激活态的一种会话处理方法。
图6为本发明实施例提供的一种会话处理方法的通信示意图。如图6所示，该流程包括S601～S608部分。
在S601部分，目标AN向MM发送终端的切换请求，该终端的切换请求携带终端的标识和目标AN的标识。例如，该切换请求可以是path switch request等。
在该步骤之前，终端移动，将要从源AN切换到目标AN。终端的标识用于标识终端，目标AN的标识用来标识该目标AN。
在S602部分，MM向SM发送终端的移动事件，该移动事件包括终端的标识和目标AN的标识。
在S603部分，SM判断该空闲态的PDU会话是否需要更新。
关于终端的PDU会话是否需要更新，详见图2及其相关文字所述，在此不再赘述。
在S604部分，SM向MM发送该空闲态PDU会话的上下文更新消息；MM向终端发送PDU会话的上下文更新消息。
对应的，终端根据PDU会话上下文更新消息更新PDU会话上下文。该PDU会话上下文可以包括该终端的标识、PDU会话的标识、PDU会话对应的SM的标识或UP为终端分配的网络地址、以及PDU会话的连接状态，该PDU会话的 连接状态包括空闲态或激活态。
在S605部分，终端向MM发送该PDU会话的上下文更新确认，MM向SM发送该PDU会话的上下文更新确认。
需要说明的是，空闲态PDU会话的上下文更新后，该PDU会话仍旧处于空闲态。
在S606a部分，SM向UP1发送配置UP指令。
该步骤中，配置UP指令为释放UP1为终端配置的资源，并将终端的标识从UP1服务的列表中删除。
在S606b部分，SM向UP2发送配置UP指令。
该步骤中，SM选择UP2，该UP2为该终端提供服务。发送给UP2的配置指令中包括终端的标识、PDU会话的标识、PDU会话对应的QoS和计费配置等信息。
此外，在SM为该PDU会话选择UP2时，该PDU会话对应的SM或UP可以为终端的网络地址进行重新分配。该网络地址是终端接收和发送数据时使用的网络地址，网络地址类型可以为互联网协议第四版(Internet Protocol Version4，IPv4)和互联网协议第六版(Internet Protocol Version 6，IPv6)等。
在S607部分，SM向MM发送终端移动事件响应。
在S608部分，MM向目标AN发送终端切换确认。
本发明实施例中，在终端移动时，对于处于空闲态态PDU会话的处理；同时避免了现有技术中终端移动时，AN会参与终端中的所有PDU会话的处理，节省了网络资源，提高了终端移动时的处理效率。
图7为本发明实施例提供的又一种会话处理方法的通信示意图。图7中，与图6所示方法相同或相似的内容，可以参考图6中的详细描述，此处不做赘述。如图7所示，该方法包括S701-S705部分。其中，S701-S702部分分别与S601-S302部分相同或相似，S704-S705部分分别与S607-S608部分相同或相似。而S703部分中SM控制PDU会话的流程可以参考现有流程，此处不做赘述。
本发明实施例，能够实现在终端移动时，只对处于激活态的PDU会话的处理，避免了现有技术中终端移动时，接入网会参与终端中的所有PDU会话的处理，节省了网络资源，提高了终端移动时的处理效率。
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。 可以理解的是，各个网元，例如移动性管理功能实体、会话管理功能实体、终端等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对移动性管理功能实体、会话管理功能实体、终端等进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图8a示出了上述实施例中所涉及的移动性管理功能实体的一种可能的结构示意图。移动性管理功能实体包括：处理单元802和通信单元803。处理单元802用于对移动性管理功能实体的动作进行控制管理，例如，处理单元802用于支持移动性管理功能实体执行图2中的过程S201和S202，图3中的过程S301、S303和S304，图4中的过程S403、S407和S409，图5中的过程S503、S506和S508，图6中的过程S602、S604、S605和S608，图7中的过程S702、S703和S705，和/或用于本文所描述的技术的其它过程。通信单元803用于支持移动性管理功能实体与其他网络实体的通信，例如与图1中示出的终端、接入节点、会话管理功能实体、用户数据管理功能实体、策略管理功能实体等之间的通信。移动性管理功能实体还可以包括存储单元801，用于存储移动性管理功能实体的程序代码和数据。
其中，处理单元802可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实 现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元803可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元801可以是存储器。
当处理单元802为处理器，通信单元803为通信接口，存储单元801为存储器时，本发明实施例所涉及的移动性管理功能实体可以为图8b所示的移动性管理功能实体。
参阅图8b所示，该移动性管理功能实体810包括：处理器812、通信接口811、存储器813。可选的，移动性管理功能实体810还可以包括总线814。其中，处理器812、通信接口811、存储器813可以通过总线814相互连接；总线814可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线814可以分为地址总线、数据总线、控制总线等。为便于表示，图8b中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的单元的情况下，图9a示出了上述实施例中所涉及的会话管理功能实体的一种可能的结构示意图。会话管理功能实体包括：处理单元902和通信单元903。处理单元902用于对会话管理功能实体的动作进行控制管理，例如，处理单元902用于支持会话管理功能实体执行图2中的过程S203，图3中的过程S301和S302，图4中的过程S408，图5中的过程S507，图6中的过程S603、S604、S606a、S606b和S607，图7中的过程S703和S704，和/或用于本文所描述的技术的其它过程。通信单元903用于支持会话管理功能实体与其他网络实体的通信，例如与图1中示出的移动性管理功能实体、用户数据管理功能实体、策略管理功能实体、用户面功能实体等之间的通信。会话管理功能实体还可以包括存储单元901，用于存储会话管理功能实体的程序代码和数据。
其中，处理单元902可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元903可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元901可以是存储器。
当处理单元902为处理器，通信单元903为通信接口，存储单元901为存储器时，本发明实施例所涉及的会话管理功能实体可以为图9b所示的会话管理功能实体。
参阅图9b所示，该会话管理功能实体910包括：处理器912、通信接口911、存储器913。可选的，会话管理功能实体910还可以包括总线914。其中，处理器912、通信接口911、存储器913可以通过总线914相互连接；总线914可以是PCI总线或EISA总线等。所述总线914可以分为地址总线、数据总线、控制总线等。为便于表示，图9b中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的单元的情况下，图10a示出了上述实施例中所涉及的终端的一种可能的结构示意图。终端包括：处理单元1002和通信单元1003。处理单元1002用于对终端的动作进行控制管理，例如，处理单元1002用于支持终端执行图3中的过程S301，图4中的过程S401、S402和S406，图5中的过程S501和S502，图6中的过程S605，图7中的过程S703，和/或用于本文所描述的技术的其它过程。通信单元1003用于支持终端与其他网络实体的通信，例如与图1中示出的接入节点、移动性管理功能实体等之间的通信。终端还可以包括存储单元1001，用于存储终端的程序代码和数据。
其中，处理单元1002可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1003可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口。存储单元1001可以是存储器。
当处理单元1002为处理器，通信单元1003为收发器，存储单元1001为存储器时，本发明实施例所涉及的终端可以为图10b所示的终端。
图10b示出了本发明实施例中所涉及的终端的一种可能的设计结构的简化示意图。所述终端1000包括发射器1011，接收器1012和处理器1013。其中，处理器1013也可以为控制器，图10b中表示为“控制器/处理器1013”。可选的，所述终端1010还可以包括调制解调处理器1015，其中，调制解调处理器1015 可以包括编码器1016、调制器1017、解码器1018和解调器1019。
在一个示例中，发射器1011调节(例如，模拟转换、滤波、放大和上变频等)该输出采样并生成上行链路信号，该上行链路信号经由天线发射给上述实施例中所述的AN。在下行链路上，天线接收上述实施例中基站发射的下行链路信号。接收器1012调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。在调制解调处理器1015中，编码器1018接收要在上行链路上发送的业务数据和信令消息，并对业务数据和信令消息进行处理(例如，格式化、编码和交织)。调制器1018进一步处理(例如，符号映射和调制)编码后的业务数据和信令消息并提供输出采样。解调器1019处理(例如，解调)该输入采样并提供符号估计。解码器1018处理(例如，解交织和解码)该符号估计并提供发送给终端1010的已解码的数据和信令消息。编码器1016、调制器1017、解调器1019和解码器1018可以由合成的调制解调处理器1015来实现。这些单元根据无线接入网采用的无线接入技术(例如，LTE及其他演进系统的接入技术)来进行处理。需要说明的是，当终端1010不包括调制解调处理器1015时，调制解调处理器1015的上述功能也可以由处理器1013完成。
进一步的，终端1010还可以包括存储器1014，存储器1014用于存储用于终端1010的程序代码和数据。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于移动性管理功能实体、会话管理功能实体或终端中。当然，处理器和存储介质也可以作为分立组件存在于移动性管理功能实体、会话管理功能实体或终端中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施 例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (23)

  1. 一种会话激活方法，其特征在于，所述方法包括：
    移动性管理功能实体获取终端的协议数据单元PDU会话激活请求，所述PDU会话激活请求包括PDU会话的标识和所述终端的标识，所述PDU会话激活请求用于请求激活所述PDU会话；
    所述移动性管理功能实体向会话管理功能实体发送所述PDU会话激活请求。
  2. 根据权利要求1所述的方法，其特征在于，所述移动性管理功能实体获取终端的PDU会话激活请求，包括：
    所述移动性管理功能实体从所述终端接收控制面连接激活请求，所述控制面连接激活请求包括所述PDU会话激活请求；或者，
    所述移动性管理功能实体从所述终端接收所述PDU会话激活请求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述移动性管理功能实体中保存有所述终端的标识、所述PDU会话的标识以及所述会话管理功能实体的标识之间的绑定关系；所述移动性管理功能实体向会话管理功能实体发送所述PDU会话激活请求之前，所述方法还包括：
    所述移动性管理功能实体根据所述PDU会话的标识、所述终端的标识以及所述绑定关系，选择所述会话管理功能实体的标识所标识的会话管理功能实体。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动性管理功能实体从目标接入节点接收切换请求，所述切换请求携带所述终端的标识和所述目标接入节点的标识，其中，所述切换请求用于请求将所述终端从源接入节点切换到所述目标接入节点；
    所述移动性管理功能实体向所述会话管理功能实体发送所述终端的移动事件，所述移动事件包括所述终端的标识和所述目标接入节点的标识。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述移动性管理功能实体从所述会话功能管理实体接收PDU会话更新消息，所述PDU会话更新消息用于更新所述终端的标识对应的至少一个PDU会话的上下文，其中，所述至少一个PDU会话为空闲态PDU会话；
    所述移动性管理功能实体向所述终端发送所述PDU会话更新消息。
  6. 一种会话激活方法，其特征在于，所述方法包括：
    会话管理功能实体从移动性管理功能实体接收终端的协议数据单元PDU会话激活请求，所述PDU会话激活请求包括PDU会话的标识和所述终端的标识，所述PDU会话激活请求用于请求激活所述PDU会话；
    所述会话管理功能实体根据所述PDU会话激活请求激活所述PDU会话。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能实体从所述移动性管理功能实体接收所述终端的移动事件，所述移动事件包括所述终端的标识和目标接入节点的标识，其中，所述目标接入节点为所述终端将切换到的接入节点；
    所述会话管理功能实体确定所述终端的标识对应的至少一个PDU会话；
    当所述至少一个PDU会话为空闲态PDU会话时，所述会话管理功能实体确定是否需要更新所述至少一个PDU会话的上下文；或者，
    当所述至少一个PDU会话为激活态PDU会话时，所述会话管理功能实体通知所述终端和所述目标接入节点更新所述至少一个PDU会话的上下文。
  8. 根据权利要求7所述的方法，其特征在于，所述至少一个PDU会话为空闲态PDU会话，所述至少一个PDU会话的上下文中包括第一用户面功能实体的标识，所述会话管理功能实体确定是否需要更新所述至少一个PDU会话的上下文，包括：
    所述会话管理功能实体根据所述目标接入节点的服务区域和所述第一用户面功能实体的服务区域列表，确定是否需要更新所述至少一个PDU会话的上下文。
  9. 根据权利要求8所述的方法，其特征在于，所述会话管理功能实体根据所述目标接入节点的服务区域和所述第一用户面功能实体的服务区域列表，确定是否需要更新所述至少一个PDU会话的上下文，包括：
    若所述目标接入节点的服务区域不在所述第一用户面功能实体的服务区域列表中，则所述会话管理功能实体确定需要更新所述至少一个PDU会话的上下文；或者，
    若所述目标接入节点的服务区域在所述第一用户面功能实体的服务区域列表中，则所述会话管理功能实体确定不需要更新所述至少一个PDU会话的上下文。
  10. 根据权利要求9所述的方法，其特征在于，所述会话管理功能实体确 定需要更新所述至少一个PDU会话的上下文之后，所述方法还包括：
    所述会话管理功能实体向所述第一用户面功能实体发送释放消息，所述释放消息用于指示所述第一用户面功能实体释放所述至少一个PDU会话的配置资源；
    所述会话管理功能实体为所述终端选择第二用户面功能实体。
  11. 根据权利要求9或10所述的方法，其特征在于，所述会话管理功能实体确定需要更新所述至少一个PDU会话的上下文之后，所述方法还包括：
    所述会话管理功能实体向所述移动性管理功能实体发送PDU会话更新消息，所述PDU会话更新消息用于更新所述至少一个PDU会话的上下文。
  12. 一种移动性管理功能实体，其特征在于，包括处理单元和通信单元，
    所述处理单元用于获取终端的协议数据单元PDU会话激活请求，所述PDU会话激活请求包括PDU会话的标识和所述终端的标识，所述PDU会话激活请求用于请求激活所述PDU会话；以及用于通过所述通信单元向会话管理功能实体发送所述PDU会话激活请求。
  13. 根据权利要求12所述的移动性管理功能实体，其特征在于，所述处理单元具体用于通过所述通信单元从所述终端接收控制面连接激活请求，所述控制面连接激活请求包括所述PDU会话激活请求；或者，所述处理单元具体用于通过所述通信单元从所述终端接收所述PDU会话激活请求。
  14. 根据权利要求12或13所述的移动性管理功能实体，其特征在于，所述移动性管理功能实体中保存有所述终端的标识、所述PDU会话的标识以及所述会话管理功能实体的标识之间的绑定关系；所述处理单元还用于根据所述PDU会话的标识、所述终端的标识以及所述绑定关系，选择所述会话管理功能实体的标识所标识的会话管理功能实体。
  15. 根据权利要求12至14中任一项所述的移动性管理功能实体，其特征在于，所述处理单元还用于通过所述通信单元从目标接入节点接收切换请求，所述切换请求携带所述终端的标识和所述目标接入节点的标识，其中，所述切换请求用于请求将所述终端从源接入节点切换到所述目标接入节点；以及用于通过所述通信单元向所述会话管理功能实体发送所述终端的移动事件，所述移动事件包括所述终端的标识和所述目标接入节点的标识。
  16. 根据权利要求15所述的移动性管理功能实体，其特征在于，所述处理 单元还用于通过所述通信单元从所述会话管理功能实体接收PDU会话更新消息，所述PDU会话更新消息用于更新所述终端的标识对应的至少一个PDU会话的上下文，其中，所述至少一个PDU会话为空闲态PDU会话；以及用于通过所述通信单元向所述终端发送所述PDU会话更新消息。
  17. 一种会话管理功能实体，其特征在于，包括处理单元和通信单元，
    所述处理单元用于通过所述通信单元从移动性管理功能实体接收终端的协议数据单元PDU会话激活请求，所述PDU会话激活请求包括PDU会话的标识和所述终端的标识，所述PDU会话激活请求用于请求激活所述PDU会话；以及用于根据所述PDU会话激活请求激活所述PDU会话。
  18. 根据权利要求17所述的会话管理功能实体，其特征在于，所述处理单元还用于通过所述通信单元从所述移动性管理功能实体接收所述终端的移动事件，所述移动事件包括所述终端的标识和目标接入节点的标识，其中，所述目标接入节点为所述终端将切换到的接入节点；以及用于确定所述终端的标识对应的至少一个PDU会话；还用于当所述至少一个PDU会话为空闲态PDU会话时，确定是否需要更新所述至少一个PDU会话的上下文；或者，还用于当所述至少一个PDU会话为激活态PDU会话时，通知所述终端和所述目标接入节点更新所述至少一个PDU会话的上下文。
  19. 根据权利要求18所述的会话管理功能实体，其特征在于，所述至少一个PDU会话为空闲态PDU会话，所述至少一个PDU会话的上下文中包括第一用户面功能实体的标识；所述处理单元具体用于根据所述目标接入节点的服务区域和所述第一用户面功能实体的服务区域列表，确定是否需要更新所述至少一个PDU会话的上下文。
  20. 根据权利要求19所述的会话管理功能实体，其特征在于，所述处理单元具体用于若所述目标接入节点的服务区域不在所述第一用户面功能实体的服务区域列表中，则确定需要更新所述至少一个PDU会话的上下文；或者，所述处理单元具体用于若所述目标接入节点的服务区域在所述第一用户面功能实体的服务区域列表中，则确定不需要更新所述至少一个PDU会话的上下文。
  21. 根据权利要求20所述的会话管理功能实体，其特征在于，所述处理单元还用于通过所述通信单元向所述第一用户面功能实体发送释放消息，所述释放消息用于指示所述第一用户面功能实体释放所述至少一个PDU会话的配置资 源；以及用于为所述终端选择第二用户面功能实体。
  22. 根据权利要求20或21所述的会话管理功能实体，其特征在于，所述处理单元还用于通过所述通信单元向所述移动性管理功能实体发送PDU会话更新消息，所述PDU会话更新消息用于更新所述至少一个PDU会话的上下文。
  23. 一种通信系统，其特征在于，包括如权利要求12至16中任一项所述的移动性管理功能实体和如权利要求17至22中任一项所述的会话管理功能实体。
PCT/CN2016/111753 2016-12-23 2016-12-23 一种会话激活方法及装置和系统 WO2018112897A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16924589.1A EP3550867A4 (en) 2016-12-23 2016-12-23 METHOD AND DEVICE FOR SESSION ACTIVATION AND SYSTEM
PCT/CN2016/111753 WO2018112897A1 (zh) 2016-12-23 2016-12-23 一种会话激活方法及装置和系统
CN201680091560.XA CN110073686B (zh) 2016-12-23 2016-12-23 一种会话激活方法及装置和系统
US16/447,551 US11206537B2 (en) 2016-12-23 2019-06-20 Session activation method, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/111753 WO2018112897A1 (zh) 2016-12-23 2016-12-23 一种会话激活方法及装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/447,551 Continuation US11206537B2 (en) 2016-12-23 2019-06-20 Session activation method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2018112897A1 true WO2018112897A1 (zh) 2018-06-28

Family

ID=62624646

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/111753 WO2018112897A1 (zh) 2016-12-23 2016-12-23 一种会话激活方法及装置和系统

Country Status (4)

Country Link
US (1) US11206537B2 (zh)
EP (1) EP3550867A4 (zh)
CN (1) CN110073686B (zh)
WO (1) WO2018112897A1 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102449475B1 (ko) * 2016-10-21 2022-09-30 삼성전자 주식회사 무선 통신 시스템에서 단말이 지원 가능한 네트워크 정보에 기반한 단말의 네트워크 접속 방법 및 장치
CN108617012B (zh) * 2017-01-03 2020-04-17 电信科学技术研究院 一种建立连接的方法及装置
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
US10917927B2 (en) 2017-05-12 2021-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Local identifier locator network protocol (ILNP) breakout
CN109429329B (zh) * 2017-06-20 2020-10-23 华为技术有限公司 一种会话上下文删除方法及装置
CA3020118A1 (en) * 2017-10-09 2019-04-09 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
EP3841729A1 (en) 2018-08-24 2021-06-30 Koninklijke KPN N.V. Information-centric networking over 5g or later networks
US11558491B2 (en) * 2018-08-24 2023-01-17 Koninklijke Kpn N.V. Information-centric networking over 5G or later networks
US11129061B1 (en) 2018-11-07 2021-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Local identifier locator network protocol (ILNP) breakout
CN111278139B (zh) * 2020-02-13 2023-04-28 展讯通信（上海）有限公司 管理pdu会话的方法、装置及存储介质
CN111526553A (zh) * 2020-05-13 2020-08-11 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
CN112188579B (zh) * 2020-10-21 2023-03-10 中国联合网络通信集团有限公司 呼叫方法及终端、认证管理功能实体设备
AR126424A1 (es) * 2021-07-12 2023-10-11 Ericsson Telefon Ab L M Método y aparato para servicio de multidifusión / transmisión

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102123487A (zh) * 2010-01-07 2011-07-13 中国移动通信集团公司 一种载波激活方法、装置和系统
CN102428736A (zh) * 2009-05-22 2012-04-25 高通股份有限公司 在无线通信系统内寻呼用户设备(ue)
CN104469691A (zh) * 2013-09-25 2015-03-25 电信科学技术研究院 一种组通信方法、设备及系统
US9203549B2 (en) * 2012-06-06 2015-12-01 Ciena Corporation Systems and methods for operational simplification of carrier ethernet networks
CN105813079A (zh) * 2016-05-17 2016-07-27 工业和信息化部电信研究院 一种终端接入方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8352316B2 (en) * 2006-07-27 2013-01-08 Fatwallet, Inc. Method of using a subdomain portion of a domain name to pass a unique tracking code
CN101242645B (zh) * 2007-02-09 2011-02-09 华为技术有限公司 移动终端从空闲态进入激活态的方法及系统
CN102625285B (zh) * 2011-02-01 2017-04-26 中兴通讯股份有限公司 一种获取终端的身份标识的方法及系统
EP3419351A4 (en) * 2016-02-17 2019-08-14 LG Electronics Inc. -1- METHOD FOR SENDING / RECEIVING POSITION REGISTRATION-RELATED MESSAGES IN A WIRELESS COMMUNICATION SYSTEM AND DEVICE THEREFOR
CN109644516B (zh) * 2016-08-22 2023-09-01 三星电子株式会社 用于无线通信网络中的区域数据网络配置的方法和系统
KR102379860B1 (ko) * 2016-08-22 2022-03-29 삼성전자 주식회사 이동성 관리와 세션 관리가 분리된 무선 통신 시스템 운영 방법 및 장치
US10652784B2 (en) * 2016-09-30 2020-05-12 Huawei Technologies Co., Ltd. Method and apparatus for serving mobile communication devices using tunneling protocols
US10972552B2 (en) * 2016-09-30 2021-04-06 Huawei Technologies Co., Ltd. Method and system for user plane path selection
WO2018075828A1 (en) * 2016-10-19 2018-04-26 Convida Wireless, Llc Apparatus
CN108702724B (zh) * 2016-11-27 2021-06-15 Lg 电子株式会社 无线通信系统中的注销方法及其装置
US20200059989A1 (en) * 2017-08-16 2020-02-20 Lenovo (Singapore) Pte. Ltd. Indicating a packet data unit session as unavailable

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102428736A (zh) * 2009-05-22 2012-04-25 高通股份有限公司 在无线通信系统内寻呼用户设备(ue)
CN102123487A (zh) * 2010-01-07 2011-07-13 中国移动通信集团公司 一种载波激活方法、装置和系统
US9203549B2 (en) * 2012-06-06 2015-12-01 Ciena Corporation Systems and methods for operational simplification of carrier ethernet networks
CN104469691A (zh) * 2013-09-25 2015-03-25 电信科学技术研究院 一种组通信方法、设备及系统
CN105813079A (zh) * 2016-05-17 2016-07-27 工业和信息化部电信研究院 一种终端接入方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US11206537B2 (en) 2021-12-21
US20190306758A1 (en) 2019-10-03
CN110073686A (zh) 2019-07-30
CN110073686B (zh) 2021-01-29
EP3550867A4 (en) 2019-12-04
EP3550867A1 (en) 2019-10-09

Similar Documents

Publication Publication Date Title
WO2018112897A1 (zh) 一种会话激活方法及装置和系统
JP7187580B2 (ja) セッション管理の方法、装置、およびシステム
CN111436087B (zh) 一种pdu会话切换方法及其装置
KR102394891B1 (ko) 무선 통신 방법 및 장치
EP3764696A1 (en) Method and apparatus for transmitting data
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
WO2019033796A1 (zh) 会话处理方法及相关设备
WO2018202138A1 (zh) 通信方法及相关设备
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
CN105874830A (zh) 一种移动性管理的方法、装置及系统
WO2018126342A1 (zh) 一种通信方法及设备
US20190260811A1 (en) Packet data unit session establishment method and network entity performing the same
CN109429213B (zh) 一种信息处理方法、装置、设备及计算机可读存储介质
CN113438695B (zh) 一种会话建立的方法及装置
KR102536020B1 (ko) 다중 액세스에 걸쳐 트래픽을 분할하기 위한 방법 및 컴퓨팅 디바이스
WO2009117879A1 (zh) 一种指示服务网关承载管理的方法
EP3739918B1 (en) Method and apparatus for transmitting downlink data
JP2019515576A (ja) データ伝送方法、装置及びコンピュータ記憶媒体
WO2018137152A1 (zh) 短消息传输方法、设备和系统
JP2023534597A (ja) リロケーション時にエッジアプリケーションサーバへのシームレスなサービス継続性を調整するためのメカニズム
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
WO2020034802A1 (zh) 一种激活pdu会话的方法及设备
WO2018170707A1 (zh) 控制面连接管理方法和装置
JP7206390B2 (ja) データの送信方法およびデバイス
JP7357798B2 (ja) データリンク上の動的ステータス情報のための報告サービス

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: 16924589

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: 2016924589

Country of ref document: EP

Effective date: 20190701