WO2018006878A1 - 会话连续的实现方法、装置及系 - Google Patents

会话连续的实现方法、装置及系 Download PDF

Info

Publication number
WO2018006878A1
WO2018006878A1 PCT/CN2017/092282 CN2017092282W WO2018006878A1 WO 2018006878 A1 WO2018006878 A1 WO 2018006878A1 CN 2017092282 W CN2017092282 W CN 2017092282W WO 2018006878 A1 WO2018006878 A1 WO 2018006878A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pdu session
pdu
terminal
identifier
Prior art date
Application number
PCT/CN2017/092282
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 EP17823690.7A priority Critical patent/EP3506598B1/en
Priority to EP22154601.3A priority patent/EP4087367B1/en
Priority to ES17823690T priority patent/ES2954999T3/es
Publication of WO2018006878A1 publication Critical patent/WO2018006878A1/zh
Priority to US16/242,993 priority patent/US11006326B2/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/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for implementing a session continuity.
  • each network element in the network architecture includes: a user equipment (UE), which accesses a 4G network through a wireless air interface and obtains a service.
  • UE user equipment
  • the information is exchanged between the air interface and the base station, and the non-access stratum signaling (Non Access Stratum, abbreviated as NAS) and the mobility management unit of the core network exchange information.
  • NAS non-access stratum signaling
  • the radio access network (Radio Access Network, hereinafter referred to as RAN) is responsible for the air interface resource scheduling and the air interface connection management of the terminal access network, and is also responsible for detecting the uplink and downlink rate of the user, so as to ensure that the maximum uplink and downlink rates allowed by the user cannot be exceeded.
  • RAN Radio Access Network
  • MME Mobile Management Entity
  • the core network control plane unit which is mainly responsible for authentication, authorization, and subscription checking of users to ensure that users are legitimate users; user mobility management, including location registration and temporary identification. Assignment; maintain IDLE (idle) and CONNECT (connection) status and state transition; switch in CONNECT state; packet data network (Packet Data Network, PDN for short) connection and bearer maintenance, including session management such as creation, modification and deletion The function; triggering paging and other functions in the IDLE state.
  • IDLE Idle
  • CONNECT connection
  • PDN Packet Data Network
  • the Service Gateway Serving GW The core network user plane function unit, which is mainly responsible for the interaction between the packet data network (Packet Data Network, PDN) GW in the case of roaming; the downlink data packet is received in the IDLE state for buffering and the MME is notified.
  • PDN Packet Data Network
  • User user plane anchors across base stations and user plane anchors across 2G/3G/4G mobility.
  • Packet data gateway PDN GW core network user plane functional unit, which is the terminal access PDN
  • the access point of the network is responsible for allocating user IP addresses, establishing, modifying, and deleting bearers triggered by the network. It also has the functions of controlling quality of the network (Quality of Server, QoS for short), and is the third-generation cooperative organization of users. (Third Generation Partnership Project, abbreviated as 3GPP)
  • the packet data gateway is also responsible for detecting the session uplink and downlink rate to ensure that the maximum uplink and downlink rate allowed by the user session cannot be exceeded.
  • the industry is currently researching next-generation wireless communication systems and proposes a schematic diagram of the architecture shown in Figure 2.
  • the user plane function entity includes a terminating user-plane function (TUPF) for the UE to access the data network (Data Network, DN for short) entry point.
  • the control plane function entity includes Access and Mobility Management Function (AMF), which is responsible for UE access control and mobility management, and Session Management Function (SMF), which is responsible for the session. management.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • Mode 1 TUPF remains unchanged regardless of how the access network used by the UE changes;
  • Mode 2 The UE moves only in a subset of the access point of the access network (TUPF remains unchanged. When the UE leaves the service area of the TUPF, a different TUPF suitable for the current access point of the UE will be used for the service. UE.
  • Mode 3 As shown in FIG. 3, the UE is allowed to create a new PDU session to the same DN before the final protocol data unit (PDU) session is finally terminated, when the UE requests to establish a new one.
  • the network selects a TUPF that is suitable for the UE's new network attachment point.
  • the UE migrates the application from the old PDU session to the new PDU session, or the UE waits for the application bound to the old PDU session to end.
  • the UE may migrate the old PDU session to the new PDU session. But the following problem. First, as shown in FIG. 4, the UE establishes two PDN sessions to the same DN through AN1 (the allocation is PDU session1 and PDU session2), and the network selects the same TUPF for the two PDU sessions (ie, TUPF). The two PDU sessions have the same user with the DN name.
  • the Control Plane CP is the Policy Function, which establishes two Policy Control sessions (ie, Policy Control session1). And the Policy Contro1Session2).
  • the UE accesses the application by using the PDN session1, so that the AF establishes the AF session1 to provide service information, and the CP associates the AF session1 with the PDU session 1.
  • the UE accesses an application through the PDU session1.
  • the AF session of the application establishes the AF session1 to provide service information to the Policy Function, and the Policy Function associates the AF session1 with the Policy control session1.
  • the network instructs the UE to redirect PDU session1 and PDN session 2 to the new TUPF.
  • the UE establishes a new PDU session3.
  • the UE carries the user id and the DN name, but the Policy Function cannot determine which PDU session of the PDU session3 is switched over. Therefore, it is impossible to determine whether to associate AF session1 with PDU session3 (ie, Policy Control session3).
  • SMF network function entities
  • SMF may not be able to select the same Policy Function.
  • the AMF may not be able to select the same SMF, and thus cannot select the same Policy Function.
  • some of the original contexts on the SMF cannot be reused, which reduces the processing efficiency and increases the signaling overhead.
  • Embodiments of the present invention provide a method, an apparatus, and a system for implementing a session continuity, to at least When the terminal is redirected to the new TUPF in the related art, it is impossible to determine from which PDU session the newly established PDU session is switched.
  • a method for implementing a session continuity including:
  • the first PDU receives a request message for establishing the second PDU session that is initiated by the terminal after receiving the indication information, where the request message carries a session identifier of a first PDU session, the first PDU The session identifier of the session is used to uniquely identify the first PDU session.
  • a method for implementing session continuity is further provided.
  • request message for establishing the second PDU session, where the request message carries a session identifier of the first PDU session, and the session identifier of the first PDU session is used to uniquely identify the a PDU session;
  • a method for implementing a session continuity including:
  • a method for implementing a session continuity including:
  • the terminal receives the indication information of the network, where the indication information is used to notify the terminal that the current first protocol data unit PDU session is to be released, and the terminal establishes a second PDU session to the same data network;
  • a session continuous implementation apparatus including:
  • the first sending module is configured to send the indication information to the terminal, where the indication information is used to notify the terminal that the current first protocol data unit PDU session is to be released, and the terminal establishes the first data network to the same Two PDU sessions;
  • a first receiving module configured to receive a request message for establishing the second PDU session initiated by the terminal after receiving the indication information, where the request message carries a session of the first PDU session And identifying, the session identifier of the first PDU session is used to uniquely identify the first PDU session.
  • a session continuous implementation apparatus including:
  • a second receiving module configured to receive a request message for establishing the second PDU session initiated by the terminal, where the request message carries a session identifier of the first PDU session, and the session of the first PDU session The identifier is used to uniquely identify the first PDU session;
  • a selection module configured to select a session management function SMF of the first PDU session for the second PDU session according to the session identifier of the first PDU session.
  • a session continuous implementation apparatus including:
  • the third receiving module is configured to receive a request message of the second policy control session corresponding to the second PDU session that the terminal requests to establish, where the request message carries the session identifier of the first PDU session, and the first PDU The session identifier of the session is used to uniquely identify the first PDU session;
  • the association module is configured to associate the second policy control session and the application function AF session according to the session identifier of the first PDU session carried in the request message, where the AF session is the terminal traversing the first PDU A session established when a session accesses a specified application.
  • a session continuous implementation apparatus which is applied to a terminal, and includes:
  • a fourth receiving module configured to receive indication information of the network, where the indication information is used to notify the terminal that the current first protocol data unit PDU session is to be released, and the terminal establishes the same data network Two PDU sessions;
  • a second sending module configured to send a request message for establishing the second PDU session to the network, where the request message carries a session identifier of a first PDU session, where the first PDU session is The session identifier is used to uniquely identify the first PDU session.
  • a computer storage medium is further provided, and the computer storage medium may store an execution instruction for performing the implementation of the session continuous implementation method in the foregoing embodiment.
  • the request information for establishing the second PDU session sent by the terminal is received, where the request information carries the session identifier of the first PDU session, and the session identifier of the first PDU session can be used to uniquely identify
  • the session identifier of the first PDU session is solved by the above technical solution.
  • the problem that the newly established PDU session is switched from which PDU session cannot be determined, and the network side can confirm Which PDU session is redirected by the newly established PDU session.
  • FIG. 1 is a schematic structural diagram of a 4G network in the related art
  • FIG. 2 is a schematic structural diagram of a next generation wireless communication system in the related art
  • Figure 5 is a schematic diagram (2) of the problems in the prior art
  • FIG. 6 is a block diagram showing the hardware structure of a computer terminal in which a session is continuously implemented according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a method for implementing session continuity according to Embodiment 1 of the present invention.
  • FIG. 8 is a flowchart of a method for implementing session continuity according to Embodiment 2 of the present invention.
  • FIG. 9 is a structural block diagram (1) of a device for continuously implementing a session according to Embodiment 3 of the present invention.
  • FIG. 10 is a structural block diagram (2) of a device for continuously implementing a session according to Embodiment 3 of the present invention.
  • FIG. 11 is a block diagram showing the structure of a session continuous implementation apparatus according to Embodiment 3 of the present invention.
  • FIG. 12 is a flowchart of a method for implementing session continuity according to a preferred embodiment 1 of the present invention.
  • FIG. 13 is a flowchart of a method for implementing session continuity according to a preferred embodiment 2 of the present invention.
  • FIG. 14 is a flow chart of a method of implementing session continuity in accordance with a preferred embodiment 3 of the present invention.
  • a method embodiment of processing of page content is also provided, it being noted that the steps illustrated in the flowchart of the figures may be performed in a computer system such as a set of computer executable instructions. Also, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.
  • FIG. 6 is a block diagram showing the hardware structure of a computer terminal which is continuously implemented by a session according to an embodiment of the present invention.
  • computer terminal 10 may include one or more (only one shown) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • a memory 104 for storing data
  • a transmission module 106 for communication functions.
  • computer terminal 10 may also include more or fewer components than shown in FIG. 6, or have a different configuration than that shown in FIG.
  • the memory 104 can be used to store software programs and modules of the application software, such as program instructions/modules corresponding to the processing method of the page content in the embodiment of the present invention, and the processor 102 executes by executing the software programs and modules stored in the memory 104.
  • Various functional applications and data processing that is, the vulnerability detection method for implementing the above application.
  • Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 104 may further include memory remotely located relative to processor 102, which may be coupled to computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 106 is for receiving or transmitting data via a network.
  • the network specific examples described above may include a wireless network provided by a communication provider of the computer terminal 10.
  • the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • NIC Network Interface Controller
  • the transmission device 106 can be a radio frequency (RF) module for communicating with the Internet by wireless.
  • RF radio frequency
  • FIG. 7 is a flowchart of a method for implementing session continuity according to Embodiment 1 of the present invention. As shown in FIG. 7, the method includes the following steps:
  • Step S702 sending indication information to the terminal, where the indication information is used to instruct the terminal to redirect the currently established first protocol data unit PDU session to the TUPF;
  • Step S704 the receiving terminal sends a request message for establishing a second PDU session after receiving the indication information, where the request message carries the session identifier of the first PDU session, and the session identifier of the first PDU session is used for unique Identifies the first PDU session.
  • the request information for establishing the second PDU session sent by the terminal is The request information carries the session identifier of the first PDU session, and the session identifier of the first PDU session can be used to uniquely identify the session identifier of the first PDU session, and the foregoing technical solution solves the related art, the terminal redirects to the new In the TUPF, it is impossible to determine from which PDU session the newly established PDU session is switched, and the network side can confirm which PDU session the newly established PDU session is redirected from.
  • step S704 after performing step S704, determining, according to the session identifier of the first PDU session carried in the request message, that the second PDU session is a redirect session of the first PDU session; and/or according to the request message
  • the session identifier of the carried first PDU session is associated with a second PDU session and an application function AF session, where the AF session is a session established when the terminal accesses the specified application through the first PDU session.
  • the event notification of the TUPF redirection may also be sent to the AF, and Receiving updated service information provided by the AF through the AF session.
  • the session identifier of the first PDU session includes at least one of the following: a user identifier, a data network name, an Internet IP address of the first PDU session, or an IPv6 prefix.
  • the session identifier of the first PDU session may further include at least one of: a session identifier allocated for the first PDU session when the first PDU session is established; an Internet IP of the first PDU session Address or IPv6 prefix; a session identifier assigned to the first PDU session when the first PDU session is redirected.
  • FIG. 7 in the first embodiment is mainly described from the network side device.
  • a method for implementing a continuous session is also provided, and FIG. 8 is a session according to Embodiment 2 of the present invention.
  • a flowchart of a continuous implementation method, as shown in FIG. 8, includes the following steps:
  • Step S802 the session identifier of the first PDU session established by the terminal is obtained, where the session identifier of the first PDU session is used to uniquely identify the first PDU session.
  • Step S804 when the terminal determines that the currently established first PDU session needs to be redirected to the terminating user plane function TUPF, the request message for establishing the second PDU session is initiated to the network side device, where the request message carries the first PDU.
  • the session ID of the session is the information that the terminal determines that the currently established first PDU session needs to be redirected to the terminating user plane function TUPF.
  • the request message for establishing the second PDU session is initiated to the network side device, and the request information carries the session identifier of the first PDU session, and the foregoing technical solution is adopted.
  • the terminal is redirected to the new TUPF, it is impossible to determine from which PDU session the newly established PDU session is switched, and then the network side can confirm which PDU session is redirected by the newly established PDU session. Come over.
  • the session identifier of the first PDU session includes at least one of the following: a user identifier, a data network name, an Internet IP address of the first PDU session, or an IPv6 prefix.
  • the session identifier of the first PDU session may further include at least one of the following: a session identifier assigned to the first PDU session when the first PDU session is established; an Internet IP address or an IPv6 prefix of the first PDU session; and when the first PDU session is redirected, The session ID assigned to a PDU session.
  • a session continuous implementation system including: a terminal, a network side device, where
  • the terminal is configured to receive the indication information, where the indication information is used to indicate that the terminal needs to redirect the currently established first protocol data unit PDU session to the final user plane function TUPF;
  • the network side device is configured to receive, by the terminal, a request message for establishing a second PDU session, after the receiving the indication information, where the request message carries the session identifier of the first PDU session, and the session identifier of the first PDU session Used to uniquely identify the first PDU session.
  • the receiving terminal After the network side device sends the indication information for instructing the terminal to redirect the currently established first protocol data unit PDU session to the TUPF, the receiving terminal sends the The request information of the second PDU session, where the request information carries the session identifier of the first PDU session, and the session identifier of the first PDU session can be used to uniquely identify the session identifier of the first PDU session, which is solved by using the foregoing technical solution.
  • the network side can confirm which PDU session is redirected by the newly established PDU session.
  • the network side device is further configured to determine, according to the session identifier of the first PDU session carried in the request message, that the second PDU session is a redirect session of the first PDU session.
  • the network side device is further configured to associate the second PDU session and the application function AF session according to the session identifier of the first PDU session carried in the request message, where the AF session is a terminal. The session established when the specified application is accessed through the first PDU session.
  • a method for implementing a session continuity including:
  • the first PDU receives a request message for establishing the second PDU session that is initiated by the terminal after receiving the indication information, where the request message carries a session identifier of a first PDU session, the first PDU The session identifier of the session is used to uniquely identify the first PDU session.
  • the method further includes:
  • the method further includes:
  • the session identifier of the first PDU session includes at least one of: a session identifier allocated for the first PDU session when the first PDU session is established; an Internet IP of the first PDU session Address or IPv6 prefix; a session identifier assigned to the first PDU session when the first PDU session is redirected.
  • a method for implementing session continuity is further provided.
  • request message for establishing the second PDU session, where the request message carries a session identifier of the first PDU session, and the session identifier of the first PDU session is used to uniquely identify the a PDU session;
  • the method before receiving the request message for establishing the second PDU session initiated by the terminal, the method further includes:
  • the SMF is selected for the first PDU session, and the correspondence between the session identifier of the first PDU session and the SMF is saved;
  • the SMF is selected for the first PDU session, and the SMF is notified to the terminal that the current first protocol data unit PDU session is to be released, and the terminal establishes the During the process of the second PDU session, the correspondence between the session identifier of the first PDU session and the SMF is saved.
  • the method further includes:
  • the session identifier of the first PDU session includes at least one of: a session identifier allocated for the first PDU session when the first PDU session is established; an Internet IP of the first PDU session Address or IPv6 prefix; a session identifier assigned to the first PDU session when the first PDU session is redirected.
  • a method for implementing a session continuity including:
  • the session identifier of the first PDU session includes at least one of: a session identifier allocated for the first PDU session when the first PDU session is established; an Internet IP of the first PDU session Address or IPv6 prefix; when redirecting the first PDU session, The session identifier assigned to the first PDU session.
  • the method further includes:
  • a method for implementing a session continuity including:
  • the terminal receives the indication information of the network, where the indication information is used to notify the terminal that the current first protocol data unit PDU session is to be released, and the terminal establishes a second PDU session to the same data network;
  • the method before the terminal receives the indication information of the network, the method further includes:
  • the terminal acquires a session identifier of the first PDU session in the indication information.
  • the session identifier of the first PDU session includes at least one of: a session identifier allocated for the first PDU session when the first PDU session is established; an Internet IP of the first PDU session Address or IPv6 prefix; a session identifier assigned to the first PDU session when the first PDU session is redirected.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention may be soft in nature or in part contributing to the prior art.
  • the form of the product is stored in a storage medium (such as ROM / RAM, disk, CD), including a number of instructions to make a terminal device (can be a mobile phone, computer, server, or network) A device or the like) performs the methods of various embodiments of the present invention.
  • a device for implementing a session is provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 9 is a structural block diagram (1) of a device for continuously implementing a session according to Embodiment 3 of the present invention. As shown in FIG. 9, the method includes:
  • the sending module 90 is configured to send the indication information to the terminal, where the indication information is used to indicate that the terminal needs to redirect the currently established first protocol data unit PDU session to the final user plane function TUPF;
  • the receiving module 92 is configured to receive a request message for establishing a second PDU session initiated by the terminal after receiving the indication information, where the request message carries the session identifier of the first PDU session, and the session identifier of the first PDU session Used to uniquely identify the first PDU session.
  • the request information used by the terminal to establish the second PDU session is sent by the integrated function of the foregoing modules.
  • the session identifier of the first PDU session is carried, and the session identifier of the first PDU session can be used to uniquely identify the session identifier of the first PDU session.
  • FIG. 10 is a structural block diagram (2) of a device for continuously implementing a session according to Embodiment 3 of the present invention, As shown in FIG. 10, the foregoing apparatus further includes: a determining module 96, configured to determine, according to the session identifier carried in the request message, that the first PDU session is redirected to the second PDU session.
  • a determining module 96 configured to determine, according to the session identifier carried in the request message, that the first PDU session is redirected to the second PDU session.
  • the foregoing apparatus further includes: an association module, configured to associate the second PDU session and the application function AF session according to the session identifier carried in the request message, where the application function AF session is to access the specified application by the terminal through the first PDU session.
  • an association module configured to associate the second PDU session and the application function AF session according to the session identifier carried in the request message, where the application function AF session is to access the specified application by the terminal through the first PDU session. The session that was established.
  • a device for implementing a session is provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 11 is a structural block diagram of a device for continuously implementing a session according to Embodiment 3 of the present invention. As shown in FIG. 11, the method includes:
  • the obtaining module 110 is configured to obtain a session identifier of a first protocol data unit PDU session established by the terminal, where the session identifier is used to uniquely identify the first PDU session;
  • the initiating module 112 is configured to: when the terminal determines that the currently established first PDU session needs to be redirected to the terminating user plane function TUPF, initiate a request message for establishing a second PDU session to the network side device, where the request message carries The session ID of the first PDU session.
  • the request message for establishing the second PDU session is initiated by the network side device, and the request information carries the session identifier of the first PDU session.
  • a session continuous implementation apparatus including:
  • the first sending module (corresponding to the sending module 90 of the above embodiment) is configured to send to the terminal Instructing information, wherein the indication information is used to notify the terminal that a current first protocol data unit PDU session is to be released, and the terminal establishes a second PDU session to the same data network;
  • a first receiving module (corresponding to the receiving module 92 of the above embodiment), configured to receive a request message for establishing the second PDU session initiated by the terminal after receiving the indication information, where
  • the request message carries a session identifier of the first PDU session, and the session identifier of the first PDU session is used to uniquely identify the first PDU session.
  • a session continuous implementation apparatus including:
  • the second receiving module (corresponding to the receiving module 92 of the previous embodiment) is configured to receive a request message initiated by the terminal for establishing the second PDU session, where the request message carries the first PDU session. a session identifier, where the session identifier of the first PDU session is used to uniquely identify the first PDU session;
  • a selection module configured to select a session management function SMF of the first PDU session for the second PDU session according to the session identifier of the first PDU session.
  • a session continuous implementation apparatus including:
  • the third receiving module (corresponding to the receiving module 92 of the previous embodiment) is configured to receive a request message of the second policy control session corresponding to the second PDU session that the terminal requests to establish, where the request message carries the first a session identifier of the PDU session, where the session identifier of the first PDU session is used to uniquely identify the first PDU session;
  • the association module is configured to associate the second policy control session and the application function AF session according to the session identifier of the first PDU session carried in the request message, where the AF session is the terminal traversing the first PDU A session established when a session accesses a specified application.
  • a session continuous implementation apparatus which is applied to a terminal, and includes:
  • the fourth receiving module (corresponding to the receiving module 92 of the above embodiment) is configured to receive the network Instructing information, wherein the indication information is used to notify the terminal that a current first protocol data unit PDU session is to be released, and the terminal establishes a second PDU session to the same data network;
  • a second sending module (corresponding to the sending module 90 of the above embodiment), configured to send a request message for establishing the second PDU session to the network, where the request message carries a first PDU session
  • the session identifier, the session identifier of the first PDU session is used to uniquely identify the first PDU session.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • FIG. 12 is a flowchart of a method for implementing session continuity according to a preferred embodiment 1 of the present invention. As shown in FIG. 12, the process includes the following steps:
  • Step S1200 The UE requests the network to establish a PDU session 1 at the AN1, carrying the user id and the DN name.
  • the network selects SSC mode 3 for PDN session 1, selects TUPF1, and assigns IP address1.
  • the UE accesses an application through the PDU session 1.
  • the AF session of the application establishes the AF session1 to provide service information to the Policy Function, and the Policy Function associates the AF session1 with the PDU session 1 (ie, AF Session1 and Policy control session1 are associated).
  • the AMF in the CP selects an SMF and sends a message to the SMF requesting to establish PDU session 1.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF carrying the IP address1.
  • the AMF further returns a confirmation message to the AN.
  • the AMF can save the correspondence between IPAddress1 and SMF;
  • Step S1202 The UE requests to establish a PDU session 2 to the network under AN1, carrying the user id And DN name.
  • the network selected TUPF1 for PDN session 2 and assigned IP address2.
  • the AMF in the CP selects an SMF and sends a message to the SMF requesting to establish PDU session 2.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF carrying the IP address2.
  • the AMF further returns a confirmation message to the AN.
  • AMF can save the correspondence between IPAddress2 and SMF.
  • Step S 1204 The UE moves to AN2, and the network decision TUPF1 is not optimal for PDU Session 1 and PDU Session 2, and TUPF needs to be reselected. Therefore the network (usually SMF) sends a TUPF Redirection message to the UE. That is, the network informs the UE that PDU Session 1 and PDU Session 2 will be released after a period of time, and the UE establishes a new PDU session to the same DN.
  • SMF Service Management Function
  • Step S1206 After the UE receives the redirect message (ie, the network notifies the UE that the PDU session 1 and the PDU session 2 are to be released, and the UE establishes a message to the same DN new PDU session), the UE first decides to redirect the PDU session 1. Therefore, the UE sends a message requesting to establish a new PDU session (PDU session 3) to the network, where the message carries User Id, DN name, IP address of PDU session 1 (IP address 1), TUPF redirection indication information, and the like.
  • the network ie CP selects the IP address (IP address 3) of the new TUPF (ie TUPF2) allocation information for the UE.
  • Step S1208 The CP sends a message requesting a new policy control session (Policy Control session 3) to the Policy Function, where the message carries the newly assigned IP address (IP Address3), the TUPF redirection indication (optional), and the old IP address (IP). Address1), DN name.
  • the CP in step S1200/S 1202 and the CP in step S1208 may be the same or different.
  • the AMF can select the original SMF according to the IP address1 and the saved correspondence.
  • the SMF returns an acknowledgment message to the AMF, the AMF saves the correspondence between IPAddress3 and SMF.
  • the SMF can also select the original Policy Function according to IP address1.
  • Step S1210 The Policy Function is based on the TUPF redirection indication or the old IP address1. It is judged that the PDU session 1 is redirected (the establishment of the PDU session 3 is triggered by the message of step S1204), and the PDU session 3 is associated with the AF session1 according to the IP Address1 (ie, Policy Control session 3 and AF session 1 are associated).
  • Step S1212 The Policy Function sends a message to the AF to notify the TUPF redirection event (user plane reselection event).
  • Step S1214 After the UE and the application server perform application layer interaction, the AF provides updated service information to the Policy Function through the AF session1.
  • Step S1216 After the Policy Function makes a policy decision, the policy information is provided to TUPF2 and AN2, and TUPF2 and AN2 execute the policy.
  • step S1218 the UE initiates a process to release the PDU session 1.
  • the Policy Function and the CP are independent functional entities.
  • the Policy Function is also integrated in the CP.
  • the interaction between the CP and the Policy Function is internal interaction and can be ignored.
  • the interaction between the AF and the Policy Function is the interaction between the AF and the CP. That is, the CP will associate AF session1 with PDU session 3 according to the IP address1 reported by the UE.
  • FIG. 13 is a flowchart of a method for implementing session continuity according to a preferred embodiment 2 of the present invention. As shown in FIG. 13, the process includes the following steps:
  • Step S1300 The UE requests the establishment of the PDU session 1 from the network at AN1, carrying the user id and the DN name.
  • the network selects TUPF1 for PDN session 1, assigns IP address1, and the network also assigns PDU session ID 1 to PDU session 1.
  • User Id, DN name, and PDU Session 1 can uniquely identify PDU Session 1.
  • the UE accesses an application through the PDU session 1.
  • the AF session of the application establishes the AF session1 to provide service information to the Policy Function, and the Policy Function associates the AF session1 with the Policy control session1.
  • the AMF in the CP selects an SMF and sends a request to the SMF to establish a PDU session. Message.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF, which carries the PDU session identifier 1.
  • the AMF further returns a confirmation message to the AN.
  • the AMF can save the correspondence between the PDU session identifier 1 and the SMF.
  • the PDU session identifier 1 may also be allocated by the UE and sent to the AMF, SMF and Policy Function in the message requesting the establishment of the PDU session 2.
  • Step S1302 The UE requests to establish a PDU session 2 to the network under AN1, carrying the user id and the DN name.
  • the network selects TUPF1 for PDN session 2, assigns IP address2, and the network also assigns PDU session ID 2 to PDU session 2.
  • User Id, DN name, and PDU session 2 can uniquely identify the PDU session 2.
  • the AMF in the CP receives the request to establish a PDU Session 2 message sent by AN1.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF, which carries the PDU session identifier 2.
  • the AMF further returns a confirmation message to the AN.
  • the AMF can save the correspondence between the PDU session identifier 2 and the SMF.
  • the PDU session identifier 1 may also be allocated by the UE and sent to the AMF, SMF and Policy Function in the message requesting the establishment of the PDU session 2.
  • Step S1304 The UE moves to AN2, and the network decision TUPF1 is not optimal for PDU Session 1 and PDU Session 2, and TUPF needs to be reselected. Therefore the network (usually SMF) sends a TUPF Redirection message to the UE. That is, the network informs the UE that PDU Session 1 and PDU Session 2 will be released, and the UE establishes a new PDU session to the same DN.
  • SMF the network informs the UE that PDU Session 1 and PDU Session 2 will be released, and the UE establishes a new PDU session to the same DN.
  • Step S1306 After the UE receives the redirect message (ie, the network notifies the UE that the PDU session 1 and the PDU session 2 are to be released, and the UE establishes a message to the same DN new PDU session), the UE first decides to redirect the PDU session 1. Therefore, the UE sends a message requesting to establish a new PDU session (PDN session 3) to the network, where the message carries User Id, DN name, PDU session identifier 1, TUPF redirection indication information, and the like. The network selects the IP address (IP address 3) of the new TUPF (ie TUPF2) allocation information for the UE.
  • IP address 3 IP address of the new TUPF (ie TUPF2) allocation information for the UE.
  • Step S1308 The CP sends a message requesting a new policy control session (Policy Control session 3) to the Policy Function, where the message carries the newly assigned IP address (IP Address3).
  • Policy Control session 3 Policy Control session 3
  • IP Address3 IP Address 3
  • TUPF redirection indication optionally
  • PDU session ID 1 DN name.
  • the CP in step S1300/S 1302 and the CP in step S1308 may be the same or different.
  • the AMF may select the original SMF according to the PDU session identifier 1 and the saved correspondence.
  • the SMF returns an acknowledgment message to the AMF, the AMF saves the correspondence between the PDU session identifier 3 and the SMF.
  • the SMF can also select the original Policy Function according to the PDU session identifier 3.
  • Step S1310 The Policy Function determines that the PDU session 1 is redirected according to the TUPF redirection indication or the PDU session identifier 1, and associates the PDU session 3 with the AF session1 according to the PDU session identifier 1 (ie, the Policy Control session 3 and the AF session 1 are associated). .
  • Step S1310 The Policy Function sends a message to the AF to notify the TUPF redirection event (user plane reselection event).
  • Step S1312 After the application layer interaction between the UE and the application server, the AF provides updated service information to the Policy Function through the AF session1.
  • Step S1314 After the Policy Function makes a policy decision, the policy information is provided to TUPF2 and AN2, and TUPF2 and AN2 execute the policy.
  • step S1316 the UE initiates a process to release the PDU session 1.
  • the Policy Function and the CP are independent functional entities.
  • the Policy Function is also integrated in the CP.
  • the interaction between the CP and the Policy Function is internal interaction and can be ignored.
  • the interaction between AF and Policy Function is the interaction between AF and CP. That is, the CP associates AF session1 with PDU session 3 according to the PDU session identifier 1 reported by the UE.
  • FIG. 14 is a flow chart of a method for implementing session continuity in accordance with a preferred embodiment 3 of the present invention. As shown in FIG. 14, the process includes the following steps:
  • Step S 1400 The UE requests the network to establish a PDU session 1 at the AN1, carrying the user id and the DN name.
  • the network selected TUPF1 for PDN session 1, and assigned IP address1.
  • the UE accesses an application through the PDU session 1.
  • the AF session of the application establishes the AF session1 to provide service information to the Policy Function, and the Policy Function associates the AF session1 with the Policy control session1.
  • the AMF in the CP selects an SMF and sends a message to the SMF requesting to establish PDU session 1.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF, and the AMF will further return a confirmation message to the AN.
  • Step S1402 The UE requests to establish a PDU session 2 to the network under AN1, carrying the user id and the DN name.
  • the network selected TUPF1 for PDN session 2 and assigned IP address2.
  • the AMF in the CP selects an SMF and sends a message to the SMF requesting to establish PDU session 2.
  • the SMF further selects a Policy Function.
  • the SMF will return an acknowledgement message to the AMF, and the AMF will further return a confirmation message to the AN.
  • Step S 1404 The UE moves to AN2, and the network decision TUPF1 is not optimal for PDU Session 1 and PDU Session 2, and TUPF needs to be reselected. Therefore, the network (usually the SMF) sends a TUPF redirection message to the UE (ie, the network informs the UE that the PDU session 1 is to be released, and the UE establishes a new PDU session to the same DN), and the message carries the redirected PDU corresponding to the PDU1 session 1. Session ID 1. In this process, the TUPF redirection message is sent by the SMF to the UE through the AMF, and the AMF saves the correspondence between the redirection PDU session identifier 1 and the SMF.
  • Step S1406 After the UE receives the redirect message (ie, the network notifies the UE that the PDU session 1 is to be released, and the UE establishes a message to the same DN new PDU session), the UE decides to redirect the PDU session 1, so the UE sends the message to the network.
  • Request to establish a new PDU session (PDN session 3) message carrying User Id, DN name, redirect PDU session ID 1, TUPF Redirect instructions, etc.
  • the network selects the IP address (IP address 3) of the new TUPF (ie TUPF2) allocation information for the UE.
  • Step S1408 The CP notifies the Policy Function, and the redirect PDU session identifier 1 corresponding to the PDU session 1.
  • Step S1410 The CP sends a message requesting a new policy control session (Policy Control session 3) to the Policy Function, the message carries the newly assigned IP address (IP Address3), the TUPF redirection indication (optional), and the redirected PDU session identifier 1 , DN name.
  • Policy Control session 3 Policy Control session 3
  • IP Address3 IP Address 3
  • TUPF redirection indication optionally
  • PDU session identifier 1 DN name
  • the CP in step S1400/S1402 and the CP in step S1410 may be the same or different.
  • the AMF may select the original SMF according to the redirected PDU session identifier 1 and the saved correspondence.
  • the SMF can also select the original Policy Function according to the PDU session identifier 3.
  • Step S1412 The Policy Function determines that the PDU session 1 is redirected according to the TUPF redirection indication or the redirect PDU session identifier 1, and associates the PDU session 3 with the AF session 1 according to the redirect PDU session identifier 1 (Policy Control session 3 and AF) Session1 is associated).
  • Step S1414 The Policy Function sends a message to the AF to notify the TUPF redirection event (user plane reselection event).
  • Step S1416 After the application layer interaction between the UE and the application server, the AF provides the updated service information to the Policy Function through the AF session1.
  • Step S1418 After the Policy Function makes a policy decision, the policy information is provided to TUPF2 and AN2, and TUPF2 and AN2 execute the policy.
  • step S1420 the UE initiates a process to release the PDU session 1.
  • the Policy Function and the CP are independent functional entities.
  • the Policy Function is also integrated in the CP.
  • the interaction between the CP and the Policy Function is internal interaction and can be ignored.
  • the interaction between AF and Policy Function is the interaction between AF and CP. That is, the CP associates AF session1 with PDU session 3 according to the PDU session identifier 1 reported by the UE.
  • the original PDU session redirected by the newly established PDU session is negotiated between the UE and the network, and the corresponding AF session is determined accordingly.
  • the network can also apply some of the policies implemented in the original PDU session to the newly established PDU session.
  • the embodiment of the present invention achieves the following technical effects: in the related art, when the terminal is redirected to the new TUPF, the problem that the newly established PDU session is switched from which PDU session cannot be determined, and then the network side It is possible to confirm which PDU session was redirected by the newly established PDU session.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be used to save the program code executed by the processing method of the page content provided in the first embodiment.
  • the foregoing storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.
  • the storage medium is arranged to store program code for performing the following steps:
  • the indication information is sent to the terminal, where the indication information is used to indicate that the terminal redirects the currently established first protocol data unit PDU session to the final user plane function TUPF;
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the session identifier of the first protocol data unit PDU session established by the terminal is obtained, where the session identifier of the first PDU session is used to uniquely identify the first PDU session.
  • the disclosed technical contents 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.
  • multiple units or components may be combined or may be Integrate 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, unit or module, and may be electrical or otherwise.
  • 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 above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included 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 read only memory (ROM, Read-Only Memory), Random Access Memory (RAM), removable hard disk, disk or optical disk, etc., which can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)

Abstract

本发明提供了一种会话连续的实现方法、装置，其中，所述方法包括：向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；接收所述终端在接收到所述指示信息后发起的用于建立第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。

Description

会话连续的实现方法、装置及系 技术领域
本发明涉及通信领域，具体而言，涉及一种会话连续的实现方法、装置及系统。
背景技术
图1是相关技术中4G网络的架构示意图，如图1所示，该网络架构中各网元包括：终端(User Equipment，简称为UE)，主要通过无线空口接入4G网络并获得服务，终端通过空口和基站交互信息，通过非接入层信令(Non Access Stratum，简称为NAS)和核心网的移动性管理单元交互信息。
基站(Radio Access Network，简称为RAN)，负责终端接入网络的空口资源调度和以及空口的连接管理，还负责检测用户上下行速率，以保证不能超过该用户允许的最大上下行速率。
移动管理实体(Mobile Management Entity，简称为MME)：核心网控制面单元，主要负责对用户的鉴权、授权以及签约检查，以保证用户是合法用户；用户移动性管理，包括位置注册和临时标识分配；维护IDLE(空闲)和CONNECT(连接)状态以及状态迁移；在CONNECT状态下的切换；分组数据网(Packet DataNetwork，简称为PDN)连接以及承载的维护，包括创建、修改和删除等会话管理的功能；用户IDLE状态下触发寻呼等功能。
服务网关Serving GW：核心网用户面功能单元，主要负责漫游情况下和分组数据网(Packet Data Network，简称为PDN)GW的交互；用户IDLE状态下收到下行数据包进行缓存并通知MME寻呼用户；跨基站的用户面锚点以及跨2G/3G/4G移动性的用户面锚点等功能。
分组数据网关PDN GW：核心网用户面功能单元，是终端接入PDN 网络的接入点，负责分配用户IP地址，网络触发的承载建立、修改和删除，还具有网络服务质量(Quality of Server，简称为QoS)控制计费等功能，是用户在第三代合作组织(Third Generation Partnership Project，简称为3GPP)系统内以及和非3GPP系统之间切换的锚点，从而保证IP地址不变，保证业务连续性。分组数据网关还负责检测会话上下行速率，以保证不能超过该用户会话所允许的最大上下行速率。
目前业界正在研究下一代无线通信系统，并提出如图2所示的架构示意图。其中，用户面功能实体包括终结用户面(Terminating user-plane function，简称为TUPF)，用于UE接入数据网络(Data Network，简称为DN)入口点。控制面功能实体包括接入和移动性管理功能(Access and Mobility Management Function，简称为AMF)，负责UE的接入控制和移动性管理，以及会话管理功能(Session Management Function，简称SMF)，负责会话管理。在研究下一代无线通信系统过程中，提出了新的对业务连续性的需求和方案。其中，定义了会话和业务连续性(Session and service continuity，简称为SSC)的3种模式。
模式1：无论UE使用的接入网的如何变化，TUPF保持不变；
模式2：UE只在接入网附着点的一组子集中移动时(TUPF保持不变。当UE离开TUPF的服务区域，一个适合于UE当前接入网附着点的不同的TUPF将用于服务UE。
模式3：如图3所示，UE被允许在之前的协议数据单元(Protocol Data Unit，简称为PDU)会话被最终终结前，新建一个到同一个DN的PDU会话，当UE请求建立一个新的PDU会话时，网络选择一个适合UE新的网络附着点的TUPF。当两个PDU同时激活时，UE将应用从旧的PDU会话迁移到新的PDU会话，或是UE等待绑定在旧的PDU会话的应用结束。
为了保证业务连续性，在模式3中，在应用支持业务连续性的情况下，UE可以将绑定在旧的PDU会话的迁移到新的PDU会话。但存在如下的 问题。首先，如图4所示，UE通过AN1建立了2个到同一个DN建立了2个PDN session(分配是PDU session1和PDU session2)，网络为这两个PDU session选择了同一个TUPF(即TUPF)，这两个PDU session具有相同的user以DN name.为了实现对PDU session的策略控制，控制面(Control Plane，简称为CP)分别是Policy Function建立了2个Policy Control session(即Policy Control session1和Policy Contro1Session2).UE采用PDN session1访问应用，从而AF建立AF session1提供业务信息，CP将AF session1和PDU session 1进行关联。其中UE通过PDU session1访问了某种应用，该应用对应的AF建立AF session1向Policy Function提供业务信息，Policy Function将AF session1和Policy control session1进行关联。
随后，如图5所示，当UE移动到AN2后，网络指示UE将PDU session1和PDN session 2需要被重定向到新的TUPF。根据网路指示，UE建立了新的PDU session3，建立PDU session3的过程中UE携带user id和DN name，但是Policy Function无法确定PDU session3是哪个PDU session切换过来的。因此无法判断是否将AF session1和PDU session3(即Policy Control session3)进行关联。
同样，若是网络其他网络功能实体(如SMF)无法判断PDU session 3是哪个PDU session切换过来的，那么SMF有可能无法选到同一个Policy Function。进一步地，若AMF无法判断PDU session 3是哪个PDU session切换过来的，那么AMF有可能无法选到同一个SMF，进而无法选到同一个Policy Function。此外，若无法选到同一个SMF，那么原来在SMF上的一些上下文也无法重用，降低了处理的效率和增加了信令开销。
针对相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种会话连续的实现方法、装置及系统，以至少 解决相关技术中终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题。
根据本发明的一个实施例，还提供了一种会话连续的实现方法，包括：
向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，
端发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，包括：
接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，包括：
终端接收网络的指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
所述终端向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第一发送模块，设置为向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
第一接收模块，设置为接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第二接收模块，设置为接收终端发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
选择模块，设置为根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第三接收模块，设置为接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一 PDU会话；
关联模块，设置为根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，应用于终端，包括：
第四接收模块，设置为接收网络的指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
第二发送模块，设置为向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的会话连续的实现方法的实现。
通过本发明实施例，接收到终端发送的用于建立第二PDU会话的请求信息，在该请求信息中携带有第一PDU会话的会话标识，而第一PDU会话的会话标识能够用来唯一标识第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中4G网络的架构示意图；
图2是相关技术中下一代无线通信系统结构示意图；
图3是相关技术中SSC模式3的示意图；
图4是现有技术中存在问题的示意图(一)；
图5是现有技术中存在问题的示意图(二)；
图6是本发明实施例的一种会话连续的实现的计算机终端的硬件结构框图；
图7是根据本发明实施例1的会话连续的实现方法的流程图；
图8是根据本发明实施例2的会话连续的实现方法的流程图；
图9是根据本发明实施例3的会话连续的实现装置的结构框图(一)；
图10是根据本发明实施例3的会话连续的实现装置的结构框图(二)；
图11是根据本发明实施例3的会话连续的实现装置的结构框图；
图12为根据本发明优选实施例1的实现会话连续性的方法的流程图；
图13为根据本发明优选实施例2的实现会话连续性的方法的流程图；
图14为根据本发明优选实施例3的实现会话连续性的方法的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
实施例1
根据本发明实施例，还提供了一种页面内容的处理的方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请实施例1所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图6是本发明实施例的一种会话连续的实现的计算机终端的硬件结构框图。如图6所示，计算机终端10可以包括一个或多个(图中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器104、以及用于通信功能的传输模块106。本领域普通技术人员可以理解，图6所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，计算机终端10还可包括比图6中所示更多或者更少的组件，或者具有与图6所示不同的配置。
存储器104可用于存储应用软件的软件程序以及模块，如本发明实施例中的页面内容的处理方法对应的程序指令/模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的应用程序的漏洞检测方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例 中，传输装置106可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
在上述运行环境下，本申请提供了如图7所示的会话连续的实现方法。图7是根据本发明实施例1的会话连续的实现方法的流程图，如图7所示，包括以下步骤：
步骤S702，向终端发送指示信息，其中，该指示信息用于指示终端将当前建立的第一协议数据单元PDU会话重定向到TUPF；
步骤S704，接收终端在接收到指示信息后发起的用于建立第二PDU会话的请求消息，其中，在请求消息中携带有第一PDU会话的会话标识，第一PDU会话的会话标识用于唯一标识第一PDU会话。
通过上述各个步骤，在向终端发送用于指示终端将当前建立的第一协议数据单元PDU会话重定向到TUPF的指示信息后，接收终端发送的用于建立第二PDU会话的请求信息，在该请求信息中携带有第一PDU会话的会话标识，而第一PDU会话的会话标识能够用来唯一标识第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
在一个可选实施例中，在执行步骤S704之后，可以根据请求消息中携带的第一PDU会话的会话标识确定第二PDU会话为第一PDU会话的重定向会话；和/或根据请求消息中携带的第一PDU会话的会话标识关联第二PDU会话和应用功能AF会话，其中，AF会话为终端通过第一PDU会话访问指定应用时建立的会话。
当然，在实际应用过程中，在执行步骤根据请求消息中携带的第一PDU会话的会话标识关联第二PDU会话和应用功能AF会话之后，还可以向AF发送TUPF重定向的事件通知，还可以接收AF通过AF会话提供的更新业务信息。
在本发明实施例中，第一PDU会话的会话标识包括以下至少之一：用户标识User ID，数据网络名，第一PDU会话的互联网IP地址或IPv6前缀。
可选地，第一PDU会话的会话标识还可以包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
实施例2
实施例1中的图7主要从网络侧设备进行描述，为了完善上述技术方案，在本发明实施例中，还提供了一种会话连续的实现方法，图8是根据本发明实施例2的会话连续的实现方法的流程图，如图8所示，包括以下步骤：
步骤S802，获取终端建立的第一PDU会话的会话标识，其中，第一PDU会话的会话标识用于唯一标识第一PDU会话；
步骤S804，在终端确定需要将当前建立的第一PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立第二PDU会话的请求消息，其中，在请求消息中携带有第一PDU会话的会话标识。
通过上述各个步骤，在获取到第一PDU会话的会话标识之后，向网络侧设备发起建立第二PDU会话的请求消息，且该请求信息中携带有第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
在本发明实施例中，第一PDU会话的会话标识包括以下至少之一：用户标识User ID，数据网络名，第一PDU会话的互联网IP地址或IPv6前缀。
可选地，第一PDU会话的会话标识还可以包括以下至少之一：在建 立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
为了更好的理解上述网络侧设备和终端之间的交互流程，在本发明实施例中，还提供了一种会话连续的实现系统，包括：终端，网络侧设备，其中，
终端，用于接收指示信息，其中，该指示信息用于指示终端需要将当前建立的第一协议数据单元PDU会话重定向到终结用户面功能TUPF；
网络侧设备，用于接收终端在收到指示信息后发起的用于建立第二PDU会话的请求消息，其中，在请求消息中携带有第一PDU会话的会话标识，第一PDU会话的会话标识用于唯一标识第一PDU会话。
通过上述终端和网络侧设备的交互过程，在网络侧设备向终端发送用于指示终端将当前建立的第一协议数据单元PDU会话重定向到TUPF的指示信息后，接收终端发送的用于建立第二PDU会话的请求信息，在该请求信息中携带有第一PDU会话的会话标识，而第一PDU会话的会话标识能够用来唯一标识第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
可选地，网络侧设备，还用于根据请求消息中携带的第一PDU会话的会话标识至少确定第二PDU会话为第一PDU会话的重定向会话。
在本发明实施例的一个可选实施例中，网络侧设备，还用于根据请求消息中携带的第一PDU会话的会话标识关联第二PDU会话和应用功能AF会话，其中，AF会话为终端通过第一PDU会话访问指定应用时建立的会话。
根据本发明的一个实施例，还提供了一种会话连续的实现方法，包括：
向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的 第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
可选地，接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
根据所述请求消息中携带的第一PDU会话的会话标识确定所述第二PDU会话为所述第一PDU会话的重定向会话或为所述指示信息触发。
可选地，接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
根据第一PDU会话的会话标识选择为所述第二PDU会话选择所述第一PDU会话选择的策略功能实体。
可选地，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，
端发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
可选地，在接收终端发起的用于建立所述第二PDU会话的请求消息之前，所述方法还包括：
在所述第一PDU会话建立过程中，为所述第一PDU会话选择所述SMF，并保存所述第一PDU会话的会话标识和所述SMF的对应关系；或者，
在所述第一PDU会话建立过程中，为所述第一PDU会话选择所述SMF，并在所述SMF通知终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立所述第二PDU会话的过程中，保存所述第一PDU会话的会话标识和所述SMF的对应关系。
可选地，接收所述终端发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二PDU会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
可选地，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，包括：
接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
可选地，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时， 为所述第一PDU会话分配的会话标识。
可选地，根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话之后，所述方法还包括：
向AF发送用户面功能重选的事件通知。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，包括：
终端接收网络的指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
所述终端向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
可选地，终端接收网络的指示信息之前，所述方法还包括：
所述终端在建立所述第一PDU会话的过程中分配所述第一PDU会话的会话标识；或者，
所述终端在建立所述第一PDU会话的过程中接收所述第一PDU会话的会话标识；或者，
所述终端在所述指示信息中获取所述第一PDU会话的会话标识。
可选地，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软 件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例的方法。
实施例3
在本实施例中还提供了一种会话连续的实现装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图9是根据本发明实施例3的会话连续的实现装置的结构框图(一)，如图9所示，包括：
发送模块90，设置为向终端发送指示信息，其中，该指示信息用于指示终端需要将当前建立的第一协议数据单元PDU会话重定向到终结用户面功能TUPF；
接收模块92，设置为接收终端在接收到指示信息后发起的用于建立第二PDU会话的请求消息，其中，在请求消息中携带有第一PDU会话的会话标识，第一PDU会话的会话标识用于唯一标识第一PDU会话。
通过上述各个模块的综合作用，在向终端发送用于指示终端将当前建立的第一协议数据单元PDU会话重定向到TUPF的指示信息后，接收终端发送的用于建立第二PDU会话的请求信息，在该请求信息中携带有第一PDU会话的会话标识，而第一PDU会话的会话标识能够用来唯一标识第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
图10是根据本发明实施例3的会话连续的实现装置的结构框图(二)， 如图10所示，上述装置还包括：确定模块96，设置为根据请求消息中携带的会话标识确定第一PDU会话重定向至第二PDU会话。
可选地，上述装置还包括：关联模块98，设置为根据请求消息中携带的会话标识关联第二PDU会话和应用功能AF会话，其中，应用功能AF会话为终端通过第一PDU会话访问指定应用时建立的会话。
实施例4
在本实施例中还提供了一种会话连续的实现装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图11是根据本发明实施例3的会话连续的实现装置的结构框图，如图11所示，包括：
获取模块110，设置为获取终端建立的第一协议数据单元PDU会话的会话标识，其中，该会话标识用于唯一标识第一PDU会话；
发起模块112，设置为在终端确定需要将当前建立的第一PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立第二PDU会话的请求消息，其中，在请求消息中携带有第一PDU会话的会话标识。
通过上述各个模块的作用，在获取到第一PDU会话的会话标识之后，向网络侧设备发起建立第二PDU会话的请求消息，且该请求信息中携带有第一PDU会话的会话标识，采用上述技术方案，解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第一发送模块(相当于上实施例的发送模块90)，设置为向终端发送 指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
第一接收模块(相当于上实施例的接收模块92)，设置为接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第二接收模块(相当于上实施例的接收模块92)，设置为接收终端发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
选择模块，设置为根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
第三接收模块(相当于上实施例的接收模块92)，设置为接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
关联模块，设置为根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，应用于终端，包括：
第四接收模块(相当于上实施例的接收模块92)，设置为接收网络的 指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
第二发送模块(相当于上实施例的发送模块90)，设置为向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
为了更好的理解上述会话连续的实现过程，以下结合优选实施例对上述技术方案进行说明，但不用于对本发明实施例进行限定。
优选实施例1
图12为根据本发明优选实施例1的实现会话连续性的方法的流程图，如图12所示，该流程包括如下步骤：
步骤S 1200：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了SSC模式3，并选择了TUPF1，分配了IP address1。TUPF1和CP之间存在Sx会话1，CP和Policy Function之间存在Policy Control session1。UE通过PDU会话1访问了某种应用，该应用对应的AF建立AF session1向Policy Function提供业务信息，Policy Function将AF session1与PDU会话1关联(即AF Session1和Policy control session1进行关联)。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话1的消息后，会选择一个SMF，并向SMF发送请求建立PDU会话1的消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，消息中携带IP address1。AMF进一步向AN返回确认消息。而AMF可保存IPAddress1和SMF的对应关系；
步骤S 1202：UE在AN1下向网络请求建立PDU会话2，携带user id 和DN name。网络为PDN会话2选择了TUPF1，分配了IP address2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话2的消息后，会选择一个SMF，并向SMF发送请求建立PDU会话2的消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，消息中携带IP address2。AMF进一步向AN返回确认消息。而AMF可保存IPAddress2和SMF的对应关系。
步骤S 1204：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络(通常为SMF)向UE发送TUPF重定向消息。即网络通知UE PDU会话1和PDU会话2在一段时间后将被释放，且UE建立到同一个DN新的PDU会话。
步骤S1206：UE接收到重定向消息(即网络通知UE PDU会话1和PDU会话2将被释放，且UE建立到同一个DN新的PDU会话的消息)后，UE首先决定重定向PDU会话1，因此UE向网络发送请求建立新的PDU会话(PDU会话3)的消息，消息中携带User Id，DN name，PDU会话1的IP地址(IP address1)、TUPF重定向指示信息等。网络(即CP)为UE选择新的TUPF(即TUPF2)分配信息的IP地址(IP address 3)。步骤S1208：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address3)，TUPF重定向指示(可选)，旧的IP地址(IP Address1)，DN name。
其中步骤S1200/S 1202中CP和步骤S1208中的CP可以相同也可以不同。当需要选择相同的SMF时，当AMF接收到AN2发送的请求建立PDU会话3的消息后，AMF可以根据IP address1和保存的对应关系选择原来的SMF。在SMF向AMF返回确认消息时，AMF保存IPAddress3和SMF的对应关系。而SMF也可以根据IP address1选择原来的Policy Function。
步骤S1210：Policy Function根据TUPF重定向指示或旧的IPaddress1 判断PDU会话1发生了重定向(PDU会话3的建立是由步骤S1204的消息触发的)，并根据IP Address1将PDU会话3与AF session1进行关联(即Policy Control session3和AF session1进行关联)。
步骤S1212：Policy Function向AF发送消息，通知TUPF重定向事件(用户面重选事件)。
步骤S1214：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1216，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1218，UE发起流程，释放PDU会话1。
上述实施例中，假定Policy Function和CP是独立的功能实体，在其他实施例中，Policy Function也集成在CP中。具体实现时CP与Policy Function的交互为内部交互，可以忽略，AF与Policy Function的交互为AF与CP的交互。即CP将根据UE上报的IP address1将AF session1与PDU会话3进行关联。
优选实施例2
图13为根据本发明优选实施例2的实现会话连续性的方法的流程图，如图13所示，该流程包括如下步骤：
步骤S1300：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了TUPF1，分配了IP address1，此外网络还为PDU会话1分配了PDU会话标识1。User Id、DN name和PDU会话1可以唯一标识PDU会话1。TUPF1和CP之间存在Sx会话1，CP和Policy Function之间存在Policy Control session1。UE通过PDU会话1访问了某种应用，该应用对应的AF建立AF session1向Policy Function提供业务信息，Policy Function将AF session1和Policy control session1进行关联。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话1的消息后，会选择一个SMF，并向SMF发送请求建立PDU会话1 的消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，消息中携带PDU会话标识1。AMF进一步向AN返回确认消息。而AMF可保存PDU会话标识1和SMF的对应关系。可选地，PDU会话标识1也可以由UE分配，并在请求建立PDU会话2的消息中，发送给AMF，SMF和Policy Function。
步骤S 1302：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address2，此外网络还为PDU会话2分配了PDU会话标识2。User Id、DN name和PDU会话2可以唯一标识PDU会话2，TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话2消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，消息中携带PDU会话标识2。AMF进一步向AN返回确认消息。而AMF可保存PDU会话标识2和SMF的对应关系。可选地，PDU会话标识1也可以由UE分配，并在请求建立PDU会话2的消息中，发送给AMF，SMF和Policy Function。
步骤S1304：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络(通常为SMF)向UE发送TUPF重定向消息。即网络通知UE PDU会话1和PDU会话2将被释放，且UE建立到同一个DN新的PDU会话。
步骤S1306：UE接收到重定向消息(即网络通知UE PDU会话1和PDU会话2将被释放，且UE建立到同一个DN新的PDU会话的消息)后，UE首先决定重定向PDU会话1，因此UE向网络发送请求建立新的PDU会话(PDN会话3)的消息，消息中携带User Id，DN name，PDU会话标识1、TUPF重定向指示信息等。网络为UE选择新的TUPF(即TUPF2)分配信息的IP地址(IP address 3)。
步骤S1308：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address3)， TUPF重定向指示(可选)，PDU会话标识1，DN name。
其中步骤S1300/S 1302中CP和步骤S1308中的CP可以相同也可以不同。当需要选择相同的SMF时，当AMF接收到AN2发送的请求建立PDU会话3的消息后，AMF可以根据PDU会话标识1和保存的对应关系选择原来的SMF。在SMF向AMF返回确认消息时，AMF保存PDU会话标识3和SMF的对应关系。而SMF也可以根据PDU会话标识3选择原来的Policy Function。
步骤S1310：Policy Function根据TUPF重定向指示或PDU会话标识1判断PDU会话1发生了重定向，并根据PDU会话标识1将PDU会话3与AF session1进行关联(即Policy Control session3和AF session1进行关联)。
步骤S1310：Policy Function向AF发送消息，通知TUPF重定向事件(用户面重选事件)。
步骤S1312：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1314，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S 1316，UE发起流程，释放PDU会话1。
上述实施例中，假定Policy Function和CP是独立的功能实体，在其他实施例中，Policy Function也集成在CP中。具体实现时CP与Policy Function的交互为内部交互，，可以忽略。AF与Policy Function的交互为AF与CP的交互。即CP将根据UE上报的PDU会话标识1将AF session1与PDU会话3进行关联。
优选实施例3
图14为根据本发明优选实施例3的实现会话连续性的方法的流程图， 如图14所示，该流程包括如下步骤：
步骤S 1400：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了TUPF1，分配了IP address1。TUPF1和CP之间存在Sx会话1，CP和Policy Function之间存在Policy Control session1。UE通过PDU会话1访问了某种应用，该应用对应的AF建立AF session1向Policy Function提供业务信息，Policy Function将AF session1和Policy control session1进行关联。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话1的消息后，会选择一个SMF，并向SMF发送请求建立PDU会话1的消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，AMF进一步向AN返回确认消息。
步骤S1402：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。。在这个过程中，CP中的AMF接收到AN1发送的请求建立PDU会话2的消息后，会选择一个SMF，并向SMF发送请求建立PDU会话2的消息。SMF进一步选择一个Policy Function。SMF会向AMF返回确认消息，AMF进一步向AN返回确认消息。
步骤S 1404：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络(通常为SMF)向UE发送TUPF重定向消息(即网络通知UE PDU会话1将被释放，且UE建立到同一个DN新的PDU会话)，消息中携带PDU1会话1对应的重定向PDU会话标识1。在这个过程中，TUPF重定向消息由SMF通过AMF发送给UE，AMF保存重定向PDU会话标识1和SMF的对应关系。
步骤S1406：UE接收到重定向消息(即网络通知UE PDU会话1将被释放，且UE建立到同一个DN新的PDU会话的消息)后，UE决定重定向PDU会话1，因此UE向网络发送请求建立新的PDU会话(PDN会话3)的消息，消息中携带User Id，DN name，重定向PDU会话标识1、TUPF 重定向指示信息等。网络为UE选择新的TUPF(即TUPF2)分配信息的IP地址(IP address 3)。
步骤S1408：CP通知Policy Function，PDU会话1对应的重定向PDU会话标识1。
步骤S1410：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address3)，TUPF重定向指示(可选)，重定向PDU会话标识1，DN name。
其中步骤S1400/S1402中CP和步骤S1410中的CP可以相同也可以不同。当需要选择相同的SMF时，当AMF接收到AN2发送的请求建立PDU会话3的消息后，AMF可以根据重定向PDU会话标识1和保存的对应关系选择原来的SMF。而SMF也可以根据PDU会话标识3选择原来的Policy Function。步骤S1412：Policy Function根据TUPF重定向指示或重定向PDU会话标识1判断PDU会话1发生了重定向，并根据重定向PDU会话标识1将PDU会话3和AF session 1进行关联(Policy Control session3和AF session1进行关联)。
步骤S1414：Policy Function向AF发送消息，通知TUPF重定向事件(用户面重选事件)。
步骤S1416：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1418，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1420，UE发起流程，释放PDU会话1。
需要说明的是，在本发明实施例中，假定Policy Function和CP是独立的功能实体，在其他实施例中，Policy Function也集成在CP中。具体实现时CP与Policy Function的交互为内部交互，，可以忽略。AF与Policy Function的交互为AF与CP的交互。即CP将根据UE上报的PDU会话标识1将AF session1与PDU会话3进行关联。
在本发明实施例中，UE和网络之间协商了新建立的PDU会话所重定向的原有PDU会话，并由此确定对应的AF会话。
同样，网络还可以将实施于原有PDU会话的一些策略施加于新建立的PDU会话。
综上所述，本发明实施例达到了以下技术效果：解决了相关技术中，终端重定向到新的TUPF时，无法确定新建立的PDU会话是从哪个PDU会话切换过来的问题，进而网络侧能够确认新建立的PDU会话是由哪个PDU会话重定向过来的。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以用于保存上述实施例一所提供的页面内容的处理方法所执行的程序代码。
可选地，在本实施例中，上述存储介质可以位于计算机网络中计算机终端群中的任意一个计算机终端中，或者位于移动终端群中的任意一个移动终端中。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：
S1，向终端发送指示信息，其中，该指示信息用于指示所述终端将当前建立的第一协议数据单元PDU会话重定向到终结用户面功能TUPF；
S2，接收所述终端在接收到所述指示信息后发起的用于建立第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，获取终端建立的第一协议数据单元PDU会话的会话标识，其中，所述第一PDU会话的会话标识用于唯一标识第一PDU会话；
S2，在所述终端确定需要将当前建立的所述第一PDU会话重定向到 终结用户面功能TUPF时，向网络侧设备发起建立第二PDU会话的请求消息，其中，在所述请求消息中携带有所述第一PDU会话的会话标识。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
在本发明的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM， Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (18)

  1. 一种会话连续的实现方法，其中，包括：
    向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
    接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
  2. 根据权利要求1所述的方法，其中，接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
    根据所述请求消息中携带的第一PDU会话的会话标识确定所述第二PDU会话为所述第一PDU会话的重定向会话或为所述指示信息触发。
  3. 根据权利要求1所述的方法，其中，接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
    根据第一PDU会话的会话标识选择为所述第二PDU会话选择所述第一PDU会话选择的策略功能实体。
  4. 根据权利要求1-3任一项所述的方法，其中，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
  5. 一种会话连续的实现方法，其中，包括：
    接收终端发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
    根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
  6. 根据权利要求5所述的方法，其中，在接收终端发起的用于建立所述第二PDU会话的请求消息之前，所述方法还包括：
    在所述第一PDU会话建立过程中，为所述第一PDU会话选择所述SMF，并保存所述第一PDU会话的会话标识和所述SMF的对应关系；或者，
    在所述第一PDU会话建立过程中，为所述第一PDU会话选择所述SMF，并在所述SMF通知终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立所述第二PDU会话的过程中，保存所述第一PDU会话的会话标识和所述SMF的对应关系。
  7. 根据权利要求5所述的方法，其中，接收所述终端发起的用于建立所述第二PDU会话的请求消息之后，所述方法还包括：
    根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二PDU会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
  8. 根据权利要求5-7任一项所述的方法，其中，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一 PDU会话分配的会话标识。
  9. 一种会话连续的实现方法，其中，包括：
    接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
    根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
  10. 根据权利要求9所述的方法，其中，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
  11. 根据权利要求9所述的方法，其中，根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话之后，所述方法还包括：
    向AF发送用户面功能重选的事件通知。
  12. 一种会话连续的实现方法，其中，包括：
    终端接收网络的指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
    所述终端向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所 述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
  13. 根据权利要求12所述的方法，其中，终端接收网络的指示信息之前，所述方法还包括：
    所述终端在建立所述第一PDU会话的过程中分配所述第一PDU会话的会话标识；或者，
    所述终端在建立所述第一PDU会话的过程中接收所述第一PDU会话的会话标识；或者，
    所述终端在所述指示信息中获取所述第一PDU会话的会话标识。
  14. 根据权利要求12或13所述的方法，其中，所述第一PDU会话的会话标识包括以下至少之一：在建立所述第一PDU会话时，为所述第一PDU会话分配的会话标识；所述第一PDU会话的互联网IP地址或IPv6前缀；在重定向所述第一PDU会话时，为所述第一PDU会话分配的会话标识。
  15. 一种会话连续的实现装置，其中，包括：
    第一发送模块，设置为向终端发送指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
    第一接收模块，设置为接收所述终端在接收到所述指示信息后发起的用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
  16. 一种会话连续的实现装置，其中，包括：
    第二接收模块，设置为接收终端发起的用于建立所述第二PDU 会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
    选择模块，设置为根据所述第一PDU会话的会话标识为第二PDU会话选择所述第一PDU会话的会话管理功能SMF。
  17. 一种会话连续的实现装置，其中，包括：
    第三接收模块，设置为接收终端请求建立的第二PDU会话对应的第二策略控制会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话；
    关联模块，设置为根据所述请求消息中携带的第一PDU会话的会话标识关联所述第二策略控制会话和应用功能AF会话，其中，所述AF会话为所述终端通过所述第一PDU会话访问指定应用时建立的会话。
  18. 一种会话连续的实现装置，应用于终端，其中，包括：
    第四接收模块，设置为接收网络的指示信息，其中，所述指示信息用于通知所述终端当前的第一协议数据单元PDU会话将被释放，且所述终端建立到同一个数据网络的第二PDU会话；
    第二发送模块，设置为向所述网络发送用于建立所述第二PDU会话的请求消息，其中，在所述请求消息中携带有第一PDU会话的会话标识，所述第一PDU会话的会话标识用于唯一标识所述第一PDU会话。
PCT/CN2017/092282 2016-07-08 2017-07-07 会话连续的实现方法、装置及系 WO2018006878A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17823690.7A EP3506598B1 (en) 2016-07-08 2017-07-07 Method, device, and computer-readable storage medium for implementing continuous session
EP22154601.3A EP4087367B1 (en) 2016-07-08 2017-07-07 Method, device, and system for implementing continuous session
ES17823690T ES2954999T3 (es) 2016-07-08 2017-07-07 Método, dispositivo y medio de almacenamiento legible por ordenador para implementar una sesión continua
US16/242,993 US11006326B2 (en) 2016-07-08 2019-01-08 Method, device, and system for implementing session continuity

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610543593.5A CN107592331B (zh) 2016-07-08 2016-07-08 会话连续的实现方法、装置及系统
CN201610543593.5 2016-07-08

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/242,993 Continuation US11006326B2 (en) 2016-07-08 2019-01-08 Method, device, and system for implementing session continuity

Publications (1)

Publication Number Publication Date
WO2018006878A1 true WO2018006878A1 (zh) 2018-01-11

Family

ID=60912019

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/092282 WO2018006878A1 (zh) 2016-07-08 2017-07-07 会话连续的实现方法、装置及系

Country Status (5)

Country Link
US (1) US11006326B2 (zh)
EP (2) EP3506598B1 (zh)
CN (1) CN107592331B (zh)
ES (1) ES2954999T3 (zh)
WO (1) WO2018006878A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246813A (zh) * 2018-07-16 2019-01-18 中兴通讯股份有限公司 一种网络切片互斥关系处理方法、设备及系统
WO2019223784A1 (en) * 2018-05-25 2019-11-28 Mediatek Inc. Apparatus and method for pdu session establishment restriction in emergency registration
US10887799B2 (en) 2019-01-10 2021-01-05 Cisco Technology, Inc. SRv6 user-plane-based triggering methods and apparatus for session or flow migration in mobile networks
CN113068237A (zh) * 2021-03-29 2021-07-02 Oppo广东移动通信有限公司 一种会话管理方法、用户设备、计算机存储介质及系统
US11240198B2 (en) * 2018-01-15 2022-02-01 Huawei Technologies Co., Ltd. Session management method and apparatus
US20220286514A1 (en) * 2018-09-29 2022-09-08 Huawei Technologies Co., Ltd. Communications method and apparatus

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2552845A (en) * 2016-08-12 2018-02-14 Nec Corp Communication system
WO2018035722A1 (zh) * 2016-08-23 2018-03-01 华为技术有限公司 会话管理方法及装置
EP4271114A3 (en) * 2017-02-01 2024-01-10 Huawei Technologies Co., Ltd. Session type manager entity, control plane function entity, method and computer program for session management in nextgen mobile core networks
CN108401273B (zh) * 2017-02-06 2020-04-17 电信科学技术研究院 一种路由方法和装置
CN109691150B (zh) * 2017-03-07 2021-09-14 华为技术有限公司 一种会话迁移方法及设备
WO2018199649A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for registration type addition for service negotiation
US20190313311A1 (en) * 2018-04-09 2019-10-10 Mediatek Inc. Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover
CN112055959B (zh) * 2018-05-02 2023-08-25 诺基亚技术有限公司 用于通信的方法、装置和介质
CN110557846B (zh) * 2018-05-31 2021-06-29 华为技术有限公司 一种数据传输方法、终端设备及网络设备
CN110650504B (zh) * 2018-06-26 2021-11-19 华为技术有限公司 一种会话处理方法及装置
US11039369B2 (en) * 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors
KR20200039529A (ko) 2018-10-05 2020-04-16 삼성전자주식회사 무선 통신 시스템에서 모바일 엣지 컴퓨팅의 이전을 지원하는 방법 및 장치
US20200113009A1 (en) * 2018-10-06 2020-04-09 Mediatek Inc. Handling Of Invalid Mandatory Information In Mobile Communications
CN112655244B (zh) * 2018-10-30 2023-06-27 Oppo广东移动通信有限公司 一种业务处理方法、设备及存储介质
US11412375B2 (en) 2019-10-16 2022-08-09 Cisco Technology, Inc. Establishing untrusted non-3GPP sessions without compromising security
KR20210144205A (ko) * 2020-05-21 2021-11-30 삼성전자주식회사 네트워크 슬라이싱을 지원하는 무선 통신 시스템에서 세션 수립 방법 및 장치
US20240306043A1 (en) * 2021-01-26 2024-09-12 Beijing Xiaomi Mobile Software Co., Ltd. Method and device for processing application function session
WO2022183497A1 (zh) * 2021-03-05 2022-09-09 华为技术有限公司 一种通信方法和通信装置
CN115714970A (zh) * 2022-11-21 2023-02-24 中国人民解放军战略支援部队信息工程大学 5g终端移动中应用层无感的业务连续性传输方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247637A (zh) * 2007-02-15 2008-08-20 华为技术有限公司 一种在多接入方式下提供会话切换的方法及系统
US20110145419A1 (en) * 2009-12-15 2011-06-16 Interdigital Patent Holdings, Inc. Inter-device mobility session release
WO2015096012A1 (zh) * 2013-12-23 2015-07-02 华为终端有限公司 一种会话处理方法及设备

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3842661B2 (ja) * 2002-02-06 2006-11-08 株式会社エヌ・ティ・ティ・ドコモ 通信システム、通信制御方法、通信ノード、通信媒介ノード、通信媒介プログラム、セッション移動方法及びセッション移動プログラム
US20030177437A1 (en) * 2002-03-18 2003-09-18 Wu Frank Chih-Hsiang Erroneous packet data convergence protocol data unit handling scheme in a wireless communication system
CN101299879B (zh) * 2007-04-30 2013-08-07 华为技术有限公司 重定位方法、通信系统及无线网络控制器
CN103607793B (zh) * 2007-10-25 2017-08-25 思达伦特网络有限责任公司 用于移动节点的互通网关
CN101753963B (zh) * 2008-11-27 2012-10-03 北京中星微电子有限公司 视频监控系统的权限控制方法和系统
CN101938801B (zh) * 2009-06-30 2013-08-07 中兴通讯股份有限公司 一种实现网络间重定位的方法及系统
CN102413493A (zh) * 2010-09-21 2012-04-11 北京三星通信技术研究有限公司 决定重定位过程的方法和决定切换过程的方法
US8825054B2 (en) * 2011-12-06 2014-09-02 Qualcomm Incorporated Apparatus and methods for performing handover of user equipment between different radio access networks
KR101341303B1 (ko) * 2012-04-26 2013-12-12 주식회사 팬택 무선 접속 기술 간의 전환을 위한 단말의 통신 방법 및 그 단말
US20140169330A1 (en) * 2012-12-14 2014-06-19 Telefonaktiebolaget L M Ericsson (Publ) Network Gateway Selection at Multipath Communication
CN103945461A (zh) * 2013-01-23 2014-07-23 中兴通讯股份有限公司 数据多流传输方法及装置
DK2760240T3 (en) * 2013-01-25 2016-08-29 Telia Co Ab A method, network node and system for determining a brugerapparats capability to support network sharing
WO2014187875A1 (en) * 2013-05-24 2014-11-27 Telefonaktiebolaget L M Ericsson (Publ) Methods for providing a plmn identifier of a packet data network gateway to a node of a ran
US10667181B2 (en) * 2016-04-04 2020-05-26 Motorola Mobility Llc PDU sessions with various types of session continuity
CN109673174B (zh) * 2016-07-01 2021-08-10 Idac控股公司 以逐个会话为基础支持会话连续性的方法
WO2018006936A1 (en) * 2016-07-04 2018-01-11 Telefonaktiebolaget Lm Ericsson (Publ) Technique for internet protocol anchor relocation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247637A (zh) * 2007-02-15 2008-08-20 华为技术有限公司 一种在多接入方式下提供会话切换的方法及系统
US20110145419A1 (en) * 2009-12-15 2011-06-16 Interdigital Patent Holdings, Inc. Inter-device mobility session release
WO2015096012A1 (zh) * 2013-12-23 2015-07-02 华为终端有限公司 一种会话处理方法及设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CISCO SYSTEMS, INC. ET AL.: "SA WG2 MEETING#114 S2-161979", SYSTEM ENABLERS FOR SESSION AND SERVICE CONTINUITY, 14 April 2016 (2016-04-14), XP051091937 *
See also references of EP3506598A4 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11240198B2 (en) * 2018-01-15 2022-02-01 Huawei Technologies Co., Ltd. Session management method and apparatus
WO2019223784A1 (en) * 2018-05-25 2019-11-28 Mediatek Inc. Apparatus and method for pdu session establishment restriction in emergency registration
CN110785983A (zh) * 2018-05-25 2020-02-11 联发科技股份有限公司 紧急注册中用于pdu会话建立限制的装置及方法
CN109246813A (zh) * 2018-07-16 2019-01-18 中兴通讯股份有限公司 一种网络切片互斥关系处理方法、设备及系统
WO2020015649A1 (zh) * 2018-07-16 2020-01-23 南京中兴新软件有限责任公司 网络切片互斥关系处理方法、设备、介质及系统
US20220286514A1 (en) * 2018-09-29 2022-09-08 Huawei Technologies Co., Ltd. Communications method and apparatus
US11799968B2 (en) * 2018-09-29 2023-10-24 Huawei Technologies Co., Ltd. Communications method and apparatus
US10887799B2 (en) 2019-01-10 2021-01-05 Cisco Technology, Inc. SRv6 user-plane-based triggering methods and apparatus for session or flow migration in mobile networks
US11202236B2 (en) 2019-01-10 2021-12-14 Cisco Technology, Inc. SRV6 user-plane-based triggering methods and apparatus for session or flow migration in mobile networks
US11678228B2 (en) 2019-01-10 2023-06-13 Cisco Technology, Inc. SRV6 user-plane-based triggering methods and apparatus for session or flow migration in mobile networks
CN113068237A (zh) * 2021-03-29 2021-07-02 Oppo广东移动通信有限公司 一种会话管理方法、用户设备、计算机存储介质及系统

Also Published As

Publication number Publication date
EP4087367A1 (en) 2022-11-09
US11006326B2 (en) 2021-05-11
EP3506598A4 (en) 2020-06-24
ES2954999T3 (es) 2023-11-28
EP3506598B1 (en) 2023-07-19
CN107592331A (zh) 2018-01-16
US20190223060A1 (en) 2019-07-18
EP4087367B1 (en) 2024-07-17
CN107592331B (zh) 2021-11-02
EP3506598A1 (en) 2019-07-03

Similar Documents

Publication Publication Date Title
WO2018006878A1 (zh) 会话连续的实现方法、装置及系
RU2764259C1 (ru) Способ для активизации или деактивизации соединения плоскости пользователя в каждом сеансе
JP7366356B2 (ja) ワイヤレスネットワークによるワイヤレスデバイスのページング
CN111165014B (zh) 用于在无线通信系统中发送和接收与从5gs到eps的切换有关的信号的方法及其装置
JP6918937B2 (ja) 無線通信システムにおいて同一のｐｌｍｎに属するネットワークアクセスを通じた登録方法及びそのための装置
US11425593B2 (en) Method for implementing traffic splitting
WO2020034791A1 (zh) 一种持续在线pdu会话的管理方法及装置
US20220240131A1 (en) Data transmission method, communications device, and communications system
WO2019158132A1 (zh) 网络的切换方法、装置及系统，切换确定方法及装置
WO2018006650A1 (zh) 会话连续的实现方法、装置及系统
US20100056147A1 (en) Bearer suspension method, bearer resumption method, and gateway agent
TWI697247B (zh) 處理無線通訊系統中的連結的裝置及方法
KR101207467B1 (ko) 이동 통신 시스템에서 세션 정보 관리 방법 및 시스템과 그장치
WO2017215656A1 (zh) 会话建立的方法、装置及系统
WO2021083353A1 (zh) 连接处理方法及通信设备
US20130128816A1 (en) Method, Apparatus, and System for Setting Maximum Bandwidth
WO2012122910A1 (zh) 一种双通道通信方法和系统
WO2009117879A1 (zh) 一种指示服务网关承载管理的方法
WO2010031353A1 (zh) 服务请求的处理方法、装置及系统
WO2017167153A1 (zh) 移动通讯系统及寻呼方法
WO2012041073A1 (zh) 一种实现流迁移的方法及系统
WO2011140888A1 (zh) 一种增强单接入语音业务连续性的通信系统及方法
WO2012152130A1 (zh) 承载处理方法及装置
WO2019029228A1 (zh) 语音业务的处理方法及装置、存储介质
WO2018010583A1 (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: 17823690

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

Country of ref document: EP

Effective date: 20190208