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

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

Info

Publication number
WO2018006650A1
WO2018006650A1 PCT/CN2017/084009 CN2017084009W WO2018006650A1 WO 2018006650 A1 WO2018006650 A1 WO 2018006650A1 CN 2017084009 W CN2017084009 W CN 2017084009W WO 2018006650 A1 WO2018006650 A1 WO 2018006650A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
session
terminal
pdu
indication information
Prior art date
Application number
PCT/CN2017/084009
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 中兴通讯股份有限公司
Publication of WO2018006650A1 publication Critical patent/WO2018006650A1/zh

Links

Images

Classifications

    • 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

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 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.
  • TUPF terminating user-plane function
  • DN data network
  • SSC session and service continuity
  • 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 junction bound in the old PDU session. bundle.
  • the UE may migrate the old PDU session to the new PDU session.
  • 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 id and DN name.
  • the Control Plane CP is a Policy Function that establishes two Policy Control sessions (ie, Policy Control). Session1 and Policy Control Session2).
  • the UE accesses the application by using PDN session1, so that the AF establishes AF session1 to provide service information, and the CP associates AF session1 with 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).
  • the terminal cannot determine which PDU session is redirected by PDU session3.
  • the terminal cannot determine which PDU session is redirected by the newly established PDU session, and an effective solution has not been proposed.
  • the embodiment of the invention provides a method, a device and a system for implementing a session continuation to solve at least the problem that the terminal cannot determine which PDU session is redirected in the newly established PDU session in the related art.
  • a method for implementing session continuity including:
  • the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines, for the terminal, that the second When the PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the sending the indication information to the terminal includes: sending, to the terminal, indication information that carries the session identifier of the second PDU session, where the session identifier is used to uniquely identify the second PDU session.
  • the method before the sending, by the terminal, the indication information that carries the session identifier of the second PDU session, the method further includes:
  • the session identifier includes: a session identifier allocated for the second PDU session when the second PDU session is established; an Internet IP address or an IPv6 address prefix of the second PDU session; The session identifier assigned to the second PDU session when the second PDU session.
  • sending the indication information to the terminal including:
  • the indication information is sent to the terminal through an intermediate router user plane (User Plane, abbreviated as UP).
  • UP User Plane
  • a method for implementing a session continuity including:
  • the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines, for the terminal, that the currently established When the second PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the indication information includes at least one of the following: the terminal is establishing the second a session identifier of the second PDU session received by the PDU session, an IP address of the second PDU session or an IPv6 address prefix, and the second PDU session received by the terminal in a network sending redirect TUPF message Identification information.
  • a system for implementing a session including: a terminal, a network side device, where the network side device is configured to send indication information to the terminal, where The indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines, for the terminal, that the currently established second PDU session needs to be redirected to the end user plane function TUPF At the same time, the first PDU session established by the establishment request is initiated to the network side device.
  • the network side device is further configured to send, to the terminal, indication information that carries a session identifier of the second PDU session, where the session identifier is used to uniquely identify a second PDU session, and The network side device determines, according to the session identifier, that the first PDU session is a redirect session of the second PDU session.
  • a session continuous implementation apparatus including:
  • the sending module is configured to send the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to be established currently
  • the second PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the sending module is further configured to send, to the terminal, indication information that carries a session identifier of the second PDU session, where the session identifier is used to uniquely identify a second PDU session, and the network
  • the side device determines, according to the session identifier, that the first PDU session is a redirect session of the second PDU session.
  • a session continuous implementation apparatus including:
  • a receiving module configured to receive indication information sent by the network side device, where the indication The information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session is determined by the terminal to redirect the currently established second PDU session to the terminating user plane function TUPF.
  • the network side device initiates a first PDU session established by the setup request.
  • 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 indication information is sent to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session, and the foregoing technical solution is used to solve the related art. It is impossible to judge which PDU session is redirected by the newly established PDU session, and the terminal can determine, according to the indication information, which PDU session the newly established PDU session is switched over.
  • 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
  • Figure 6 is a schematic diagram (3) of the problems in the prior art
  • FIG. 7 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. 9 is a flowchart of a method for implementing session continuity according to Embodiment 2 of the present invention.
  • FIG. 10 is a structural block diagram (1) of a device for continuously implementing a session according to Embodiment 3 of the present invention.
  • FIG. 11 is a structural block diagram (2) of a device for continuously implementing a session according to Embodiment 3 of the present invention.
  • Figure 12 is a block diagram showing the structure of a session continuous implementation apparatus according to Embodiment 4 of the present invention.
  • FIG. 13 is a flowchart (1) of a method for implementing business continuity according to an embodiment of the present invention.
  • 15 is a flowchart (3) of a method for implementing business continuity according to an embodiment of the present invention.
  • 16 is a flowchart (4) of a method for implementing a service continuity according to an embodiment of the present invention
  • 17 is a flow chart (v) of a method for implementing business continuity in accordance with an embodiment of the present invention.
  • FIG. 7 is a hardware structural block diagram of a computer terminal in which a session is continuously implemented 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. 7, or have a different configuration than that shown in FIG.
  • the memory 104 can be configured as a software program and a module for storing 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 the software program and the module stored in the memory 104, thereby Perform various functional applications and data processing, that is, implement the vulnerability detection method of 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 arranged to receive or transmit 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.
  • the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • FIG. 8 is a flowchart of a method for implementing session continuity according to Embodiment 1 of the present invention, as shown in FIG. Includes the following steps:
  • Step S802 The network side device sends the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to establish the second currently established When the PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the indication information is sent to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session.
  • the terminal cannot determine that the terminal is newly established.
  • the PDU session is a problem of which PDU session is redirected, and the terminal can determine, according to the indication information, which PDU session the newly established PDU session is switched over.
  • the first PDU session in the embodiment of the present invention determines that the terminal needs to redirect the currently established second PDU session to the terminating user plane function TUPF, the first PDU session established by the network side device is initiated. .
  • Step S802 can be implemented in various manners.
  • the method may be implemented to: send, to the terminal, indication information that carries a session identifier of the second PDU session, where the session identifier is used for Uniquely identifies the second PDU session.
  • the method before the sending the indication information of the session identifier of the second PDU session to the terminal, the method further includes: determining, according to the session identifier, that the first PDU session is a redirect session of the second PDU session.
  • the indication information is sent to the terminal through the intermediate router UP, which will be specifically described in the following preferred embodiments, and details are not described herein again.
  • the performing step associates 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
  • the updated service information provided by the AF through the AF session may also be received.
  • the session identifier includes at least one of: a session identifier allocated for the second PDU session when the second PDU session is established; the second PDU session Internet IP address or IPv6 address prefix; a session identifier assigned to the second PDU session when the second PDU session is redirected.
  • FIG. 8 in the first embodiment is mainly described from the network side device.
  • a method for implementing session continuity is further provided, and FIG. 9 is a session according to Embodiment 2 of the present invention.
  • a flowchart of a continuous implementation method, as shown in FIG. 9, includes the following steps:
  • Step S902 Receive indication information sent by the network side device, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to establish the second currently established When the PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the terminal receives the indication information sent by the network side device, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session, and the foregoing technical solution solves the problem that the terminal cannot be used in the related art. It is determined that the newly established PDU session is a problem of which PDU session is redirected, and the terminal can determine, according to the indication information, which PDU session the newly established PDU session is switched over.
  • the first PDU session in the embodiment of the present invention determines that the terminal needs to redirect the currently established second PDU session to the terminating user plane function TUPF, the first PDU session established by the network side device is initiated. .
  • the method further includes:
  • the first PDU session and the application function AF session are associated according to the session identifier carried in the request message, where the application function AF session is a session established when the terminal accesses the specified application through the second PDU session.
  • the indication information includes at least one of: a session identifier of the second PDU session received by the terminal when establishing the second PDU session, an IP address of the second PDU session, or an IPv6 /address prefix, the terminal is connected in the network to send a redirect TUPF message The received second PDU session identification information.
  • the session identifier includes at least one of: a session identifier allocated for the second PDU session when the second PDU session is established; an Internet IP address or an IPv6 address of the second PDU session a prefix; a session identifier assigned to the second PDU session when the second PDU session is redirected.
  • a session continuous implementation system including: a terminal, a network side device, where
  • the network side device is configured to send the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to establish the second currently established When the PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the terminal receives the indication information sent by the network side device, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session, and the foregoing technical solution is adopted to solve the problem.
  • the terminal cannot determine which PDU session is redirected by the newly established PDU session, and the terminal can determine, according to the indication information, which PDU session is switched by the newly established PDU session.
  • the network side device is further configured to: send, to the terminal, the indication information that carries the session identifier of the second PDU session, where the session identifier is used to uniquely identify the second PDU session, and the network side device determines, according to the session identifier.
  • a PDU session is a redirect session for a second 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.
  • 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 which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform 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. 10 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. 10, the method includes:
  • the sending module 100 is configured to send the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to set the currently established second When the PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the function of the foregoing module is used to send the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session, and the foregoing technical solution solves the related art, the terminal cannot determine the new The PDU session established is a problem of which PDU session is redirected, and the terminal can determine, according to the indication information, which PDU session the newly established PDU session is switched over.
  • the sending module 100 is further configured to send, to the terminal, indication information that carries the session identifier of the second PDU session, where the session identifier is used to uniquely identify the second PDU session. And the network side device determines, according to the session identifier, that the first PDU session is a redirect session of the second PDU session.
  • the foregoing apparatus further includes: a determining module 102, configured to determine, according to the session identifier, that the first PDU session is a redirect session of a second PDU session.
  • 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. 12 is a structural block diagram of a device for continuously implementing a session according to Embodiment 4 of the present invention. As shown in FIG. 12, the method includes:
  • the receiving module 120 is configured to receive the indication information sent by the network side device, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to be established currently When the second PDU session is redirected to the terminating user plane function TUPF, the first PDU session established by the establishment request is initiated to the network side device.
  • the terminal receives the indication information sent by the network side device, where the indication information is used to indicate that the first protocol data unit PDU session is a redirection session of the second PDU session, and the foregoing technical solution is used to solve the related art.
  • the terminal cannot determine which PDU session is redirected by the newly established PDU session, and the terminal can determine, according to the indication information, which PDU session the newly established PDU session is switched over.
  • the indication information includes at least one of: a session identifier of the second PDU session received by the terminal when establishing the second PDU session, an IP address of the second PDU session, or an IPv6 An address prefix, the second PDU session identifier information received by the terminal in a network sending redirect TUPF message
  • each of the above modules can be implemented by software or hardware.
  • the latter can be implemented in the following manner, but is not limited thereto: the above modules are all located in the same processor; or, the above modules are respectively located in different processors in any combination.
  • FIG. 13 is a flowchart (1) of a method for implementing a service continuity according to an embodiment 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 SSC mode 3 for PDN session 1, and selects TUPF1, which is assigned IP address/Prefix1.
  • the UE accesses an application through the PDU session 1.
  • the AF session of the application establishes the AF session1 to provide the service information to the Policy Function, and the Policy Function associates the AF session1 with the PDU session 1 (ie, the AF Session1 and the Policy control session1 are associated);
  • 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 selected TUPF1 for PDN session 2 and assigned IP address/Prefix2.
  • 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 sends a TUPF redirect message to the UE.
  • Step S1306 After receiving the redirect message, 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, TUPF redirection indication information, and the like.
  • the network selects a new TUPF (ie TUPF2) for the UE, assigns a new IP address (IP address/Prefix 3) and notifies the UE.
  • the network determines that the new PDU session is for the redirection of the PDU session1, so the network will ip the IP of the session1 Address/Prefix1 is indicated to the UE.
  • the UE judges that the PDU session3 is the redirection of the PDU session1 according to the IP address/Prefix1.
  • 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 Address/Prefix3), the TUPF redirection indication (optional), and the old IP address. (IP Address/Prefix1), DN name.
  • the CP in step S1300/S1302 and the CP in step S1308 may be the same or different.
  • Step S1310 The Policy Function determines that the PDU session 1 is redirected according to the TUPF redirection indication or the old IP address/Prefix1, and associates the PDU session 3 with the AF session1 according to the IP Address/Prefix1 (ie, Policy Control session 3 and AF session 1) Associated).
  • IP Address/Prefix1 ie, Policy Control session 3 and AF session 1
  • Step S1312 The Policy Function sends a message to the AF to notify the TUPF redirection event.
  • Step S1314 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 S1316 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 S1318 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 associates AF session1 with PDU session 3 according to the IP address/Prefix1 reported by the UE.
  • the establishment of a new PDU session is performed in a manner that the UE requests to establish a new PDU session.
  • 14 is an implementation industry in accordance with an embodiment of the present invention.
  • Flow chart (2) of the continuity method as shown in FIG. 14, the process includes the following steps:
  • Step S1400 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 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.
  • 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 selects TUPF1 for PDN session 2, assigns IP address2, 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.
  • Step S1404 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 sends a TUPF redirect message to the UE.
  • Step S1406 After receiving the redirect message, 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, TUPF redirection indication information, and the like.
  • the network selects a new TUPF (ie TUPF2) for the UE, assigns a new IP address (IP address/Prefix 3) and notifies the UE.
  • the network determines that the new PDU session is for redirection of the PDU session1, so the network indicates the PDU session ID 1 of the PDU session1 to the UE.
  • the UE determines that the PDU session3 is the reconfiguration of the PDU session1 according to the IP address/Prefix1.
  • Step S1408 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 PDU session identifier 1, DN. Name.
  • the CP in step S1400/S1404 and the CP in step S1408 may be the same or different.
  • Step S1410 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 S1412 The Policy Function sends a message to the AF to notify the TUPF redirection event.
  • Step S1414 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 S1416 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 S1418 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. 15 is a flowchart (3) of a method for implementing a service continuity according to an embodiment of the present invention. As shown in FIG. 15, the process includes the following steps:
  • Step S1500 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 selected TUPF1 for PDN session 1, and assigned IP address/Prefix1.
  • the UE accesses an application through the PDU session 1, and the application corresponds to the AF. Establishing AF session1 to provide service information to the Policy Function, and the Policy Function associates AF session1 with Policy control session1.
  • Step S1502 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 address/Prefix2.
  • Step S1504 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 sends a TUPF redirection message to the UE, and carries the redirection PDU session identifier 1 in the message.
  • Step S1506 After receiving the redirect message, 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, TUPF redirection indication information, and the like.
  • the network selects a new TUPF (ie TUPF2) for the UE, assigns a new IP address (IP address/Prefix 3) and notifies the UE.
  • the network determines that the new PDU session is a redirection for PDU session1, so the network sub-direction redirects the PDU session ID 1 to the UE.
  • the UE judges that the PDU session3 is the redirection of the PDU session1 according to the redirect PDU session identifier 1.
  • Step S1508 The CP notifies the Policy Function through the policy control session 1, and the redirect PDU session identifier 1 corresponding to the PDU session 1.
  • Step S1510 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 Address/Prefix 3), the TUP redirect indication (optional), and the redirected PDU session. Identification 1, DN name.
  • the CP in step S1500/S1502 and the CP in step S1510 may be the same or different.
  • Step S1512 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 S1514 The Policy Function sends a message to the AF to notify the TUPF redirection event.
  • Step S1516 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 S1518 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 S1520 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 network after the network determines the redirection, the network establishes a new PDU connection by using the network to notify the UE after establishing a new TUPF connection.
  • This procedure is applicable to support Multi-Homed PDU sessions using IPv6.
  • 16 is a flowchart (4) of a method for implementing a service continuity according to an embodiment of the present invention. As shown in FIG. 16, the process includes the following steps:
  • Step S1600 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 address/Prefix1.
  • 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.
  • Step S1602 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 address/Prefix2.
  • Step S1604 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. The network therefore decides to establish a new leg to TUPF2 (ie PDU Session 3).
  • Step S1606 The CP configures an intermediate UP (different from TUPF) as a bifurcation point of the Multi-homed PDU session. This UP is used as the default router.
  • Step S1610 the network decides to redirect the PDU session 1 first, so the network notifies the UE that a new connection (leg) is available, and the message carries a new IP address/prefix3, redirection indication information, a timer, and the like.
  • the network also provides IP address/prefix1 to indicate that the connection is used for redirection of PDU Session 1.
  • Step S1612 UP (default IP router) sends a route advertisement message carrying the new IP Address/Prefix3. If S1006 is not executed, the route advertisement message further carries redirection indication information, a timer, and an IP address/prefix1 for indicating the connection for redirection of the PDU session 1.
  • Step S1614 The CP sends a policy control session modification message to the Policy Function through the policy control session 1, and sends a TUPF redirection event notification and a new IP Address/prefix3;
  • Step S1616 The Policy Function sends a message to the AF to notify the TUPF redirection event.
  • Step S1618 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 S1620 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 S1622 the network 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.
  • FIG. 17 is a flowchart (V) of a method for implementing a service continuity according to an embodiment of the present invention. As shown in FIG. 17, the process includes the following steps:
  • Step S1700 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 selected TUPF1 for PDN session 1, and assigned IP address/Prefix1.
  • 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.
  • Step S1702 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 address/Prefix2.
  • the network also assigns a PDU session identifier 2 to the PDU Session 2.
  • User Id, DN name, and PDU Session 2 can uniquely identify PDU Session 2.
  • Step S1704 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. The network therefore decides to establish a new leg to TUPF2 (ie PDU Session 3).
  • Step S1706 The CP configures an intermediate UP (different from TUPF) as a bifurcation point of the Multi-homed PDU session. This UP is used as the default router.
  • Step S1708 the network decides to redirect the PDU session 1 first, so the network notifies the UE that a new leg is available, and the message carries a new IP address/prefix3, redirection indication information, a timer, and the like.
  • the network also provides a PDU session identification 1 for indicating that the connection is for redirection of PDU Session 1.
  • Step S1710 UP (default IP router) sends a route advertisement message carrying a new IP Address/Prefix3. If the S1710 is not executed, the route advertisement message further carries redirection indication information, a timer, and a PDU session identifier 1 for indicating the connection for redirection of the PDU session 1.
  • Step S1712 The CP sends a policy control session modification message to the Policy Function through the policy control session 1, and sends a TUPF redirection event notification and a new IP Address/prefix3;
  • Step S1714 The Policy Function sends a message to the AF to notify the TUPF redirection event.
  • Step S1716 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 S1718 After the policy decision is made, the Policy Function provides policy information to TUPF2 and AN2, and TUPF2 and AN2 execute the policy.
  • step S1720 the network initiates a process to release the PDU session 1.
  • 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 thus determined.
  • 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, the terminal cannot determine which PDU session is redirected by the newly established PDU session, and the terminal can determine the newly established PDU session according to the indication information. Which PDU session was switched over.
  • 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 set to be stored for performing the following steps. code:
  • the indication information is sent to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is a redirect session of the second PDU session, and the first PDU session determines that the terminal needs to redirect the currently established second PDU session.
  • the user plane function TUPF is terminated, the first PDU session established by the establishment request is initiated to the network side device.
  • 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 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 in In a 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), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like. .
  • the foregoing technical solution provided by the embodiment of the present invention may be applied to the process of continuously implementing a session, by sending the indication information to the terminal, where the indication information is used to indicate that the first protocol data unit PDU session is the weight of the second PDU session.
  • the directional session is solved by the above technical solution, and the terminal can not determine which PDU session is redirected by the newly established PDU session, and the terminal can determine, according to the indication information, which PDU session is switched by the newly established PDU session. of.

Landscapes

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

Abstract

本发明提供了一种会话连续的实现方法、装置及系统，其中，所述方法包括：向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。

Description

会话连续的实现方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种会话连续的实现方法、装置及系统。
背景技术
图1是相关技术中4G网络的架构示意图，如图1所示，该网络架构中各网元包括：终端(User Equipment，简称为UE)，主要通过无线空口接入4G网络并获得服务，终端通过空口和基站交互信息，通过非接入层信令(Non Access Stratum，简称为NAS)和核心网的移动性管理单元交互信息。
目前业界正在研究下一代无线通信系统，并提出如图2所示的架构示意图。其中，用户面功能实体包括终结用户面(Terminating user-plane function，简称为TUPF)，用于UE接入数据网络(Data Network,简称为DN)入口点。在研究下一代无线通信系统过程中，提出了新的对业务连续性的需求和方案。其中，定义了会话和业务连续性(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 id,DN name.为了实现对PDU session的策略控制，控制面(Control Plane，简称为CP)分别是Policy Function建立了2个Policy Control session(即Policy Control session1和Policy Control Session2).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)进行关联，此外，即使CP能够将AF session1和PDU session3进行关系，但终端仍然无法判断PDU session3是哪个PDU session重定向的。
针对相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种会话连续的实现方法、装置及系统，以至少解决相关技术中终端无法判断新建立的PDU会话是哪个PDU session重定向的问题。
根据本发明的一个实施例，提供了一种会话连续的实现方法，包括：
向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
可选地，向终端发送指示信息，包括：向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话。
可选地，向所述终端发送携带有所述第二PDU会话的会话标识的指示信息之前，所述方法还包括：
根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
可选地，所述会话标识包括：在建立所述第二PDU会话时，为所述第二PDU会话分配的会话标识；所述第二PDU会话的互联网IP地址或IPv6地址前缀；在重定向所述第二PDU会话时，为所述第二PDU会话分配的会话标识。
可选地，向终端发送指示信息，包括：
通过中间路由器用户面(User Plane，简称为UP)向所述终端发送所述指示信息。
根据本发明的另一个实施例，还提供了一种会话连续的实现方法，包括：
接收网络侧设备发送的指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
可选地，所述指示信息包括以下至少之一：所述终端在建立所述第二 PDU会话时接收到的所述第二PDU会话的会话标识、所述第二PDU会话的IP地址或IPv6地址前缀、所述终端在网络发送重定向TUPF消息中接收到的所述第二PDU会话标识信息。
根据本发明的另一个实施例，还提供了一种会话连续的实现系统，包括：终端，网络侧设备，其中，所述网络侧设备，设置为向所述终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
可选地，所述网络侧设备，还用于向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话，且所述网络侧设备根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
发送模块，设置为向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
可选地，所述发送模块，还设置为向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话，且所述网络侧设备根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
根据本发明的另一个实施例，还提供了一种会话连续的实现装置，包括：
接收模块，设置为接收网络侧设备发送的指示信息，其中，所述指示 信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的会话连续的实现方法的实现。
通过本发明实施例，向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中4G网络的架构示意图；
图2是相关技术中下一代无线通信系统结构示意图；
图3是相关技术中SSC模式3的示意图；
图4是现有技术中存在问题的示意图(一)；
图5是现有技术中存在问题的示意图(二)；
图6是现有技术中存在问题的示意图(三)；
图7是本发明实施例的一种会话连续的实现的计算机终端的硬件结构框图；
图8是根据本发明实施例1的会话连续的实现方法的流程图；
图9是根据本发明实施例2的会话连续的实现方法的流程图；
图10是根据本发明实施例3的会话连续的实现装置的结构框图(一)；
图11是根据本发明实施例3的会话连续的实现装置的结构框图(二)；
图12是根据本发明实施例4的会话连续的实现装置的结构框图；
图13是根据本发明实施例的实现业务连续性方法的流程图(一)；
图14是根据本发明实施例的实现业务连续性方法的流程图(二)；
图15是根据本发明实施例的实现业务连续性方法的流程图(三)；
图16是根据本发明实施例的实现业务连续性方法的流程图(四)；
图17是根据本发明实施例的实现业务连续性方法的流程图(五)。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
实施例1
根据本发明实施例，还提供了一种会话连续的实现方法的实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在 某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请实施例1所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图7是本发明实施例的一种会话连续的实现的计算机终端的硬件结构框图。如图7所示，计算机终端10可以包括一个或多个(图中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器104、以及用于通信功能的传输模块106。本领域普通技术人员可以理解，图7所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，计算机终端10还可包括比图7中所示更多或者更少的组件，或者具有与图7所示不同的配置。
存储器104可设置为存储应用软件的软件程序以及模块，如本发明实施例中的页面内容的处理方法对应的程序指令/模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的应用程序的漏洞检测方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
在上述运行环境下，本申请提供了如图8所示的会话连续的实现方法。图8是根据本发明实施例1的会话连续的实现方法的流程图，如图8所示， 包括以下步骤：
步骤S802，网络侧设备向终端发送指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
通过上述步骤，向终端发送指示信息，该指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
需要说明的是，本发明实施例的第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
步骤S802可以有多种实现方式，在本发明实施例的一个可选示例中，可以通过以下方式实现：向终端发送携带有第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话。
可选地，向终端发送携带有第二PDU会话的会话标识的指示信息之前，上述方法还包括：根据会话标识确定第一PDU会话为第二PDU会话的重定向会话。
在实际应用过程中，还提供了一种向终端发送指示信息的实现方式：通过中间路由器UP向终端发送指示信息，以下优选实施例会具体说明，此处不再赘述。
当然，在执行步骤根据请求消息中携带的第一PDU会话的会话标识关联第二PDU会话和应用功能AF会话之后，还可以接收AF通过AF会话提供的更新业务信息。
在本发明实施例中，会话标识包括以下至少之一：在建立所述第二PDU会话时，为所述第二PDU会话分配的会话标识；所述第二PDU会话 的互联网IP地址或IPv6地址前缀；在重定向所述第二PDU会话时，为所述第二PDU会话分配的会话标识。
实施例2
实施例1中的图8主要从网络侧设备进行描述，为了完善上述技术方案，在本发明实施例中，还提供了一种会话连续的实现方法，图9是根据本发明实施例2的会话连续的实现方法的流程图，如图9所示，包括以下步骤：
步骤S902，接收网络侧设备发送的指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
通过上述步骤，终端接收网络侧设备发送的指示信息，该指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
需要说明的是，本发明实施例的第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
可选地，在建立请求中携带有用于唯一标识第二PDU会话的会话标识时，上述方法还包括：
根据请求消息中携带的会话标识关联第一PDU会话和应用功能AF会话，其中，应用功能AF会话为终端通过第二PDU会话访问指定应用时建立的会话。
可选地，所述指示信息包括以下至少之一：所述终端在建立所述第二PDU会话时接收到的所述第二PDU会话的会话标识、所述第二PDU会话的IP地址或IPv6/地址前缀、所述终端在网络发送重定向TUPF消息中接 收到的所述第二PDU会话标识信息。
在本发明实施例中，会话标识包括以下至少之一：在建立所述第二PDU会话时，为所述第二PDU会话分配的会话标识；所述第二PDU会话的互联网IP地址或IPv6地址前缀；在重定向所述第二PDU会话时，为所述第二PDU会话分配的会话标识。
为了更好的理解上述网络侧设备和终端之间的交互流程，在本发明实施例中，还提供了一种会话连续的实现系统，包括：终端，网络侧设备，其中，
网络侧设备，设置为向终端发送指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
通过上述网络侧设备与终端的交互流程，终端接收网络侧设备发送的指示信息，该指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
可选地，网络侧设备，还设置为向终端发送携带有第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话，且网络侧设备根据会话标识确定第一PDU会话为第二PDU会话的重定向会话。
可选地，网络侧设备，还设置为根据请求消息中携带的第一PDU会话的会话标识至少确定第二PDU会话为第一PDU会话的重定向会话。
在本发明实施例的一个可选实施例中，网络侧设备，还用于根据请求消息中携带的第一PDU会话的会话标识关联第二PDU会话和应用功能AF会话，其中，AF会话为终端通过第一PDU会话访问指定应用时建立的会话。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例的方法。
实施例3
在本实施例中还提供了一种会话连续的实现装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图10是根据本发明实施例3的会话连续的实现装置的结构框图(一)，如图10所示，包括：
发送模块100，设置为向终端发送指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
通过上述模块的作用，向终端发送指示信息，该指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
可选地，发送模块100，还设置为向终端发送携带有第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话， 且网络侧设备根据会话标识确定第一PDU会话为第二PDU会话的重定向会话。
可选地，如图11所示，上述装置还包括：确定模块102，设置为根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
实施例4
在本实施例中还提供了一种会话连续的实现装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图12是根据本发明实施例4的会话连续的实现装置的结构框图，如图12所示，包括：
接收模块120，设置为接收网络侧设备发送的指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
通过上述模块的作用，终端接收网络侧设备发送的指示信息，该指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
可选地，所述指示信息包括以下至少之一：所述终端在建立所述第二PDU会话时接收到的所述第二PDU会话的会话标识、所述第二PDU会话的IP地址或IPv6地址前缀、所述终端在网络发送重定向TUPF消息中接收到的所述第二PDU会话标识信息
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于 后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
为了更好的理解上述会话连续的实现过程，以下结合优选实施例对上述技术方案进行说明，但不用于对本发明实施例进行限定。
优选实施例1
在本实施例中，网络决定重定向后，采用UE请求建立新PDU会话的方式执行新PDU会话的建立。图13是根据本发明实施例的实现业务连续性方法的流程图(一)，如图13所示，该流程包括如下步骤：
步骤S1300：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了SSC模式3，并选择了TUPF1，分配了IP address/Prefix1。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进行关联)；
步骤S1302：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address/Prefix2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。
步骤S1304：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络向UE发送TUPF重定向消息。
步骤S1306：UE接收到重定向消息后，UE向网络发送请求建立新的PDU会话(PDN会话3)的消息，消息中携带User Id，DN name，TUPF重定向指示信息等。网络为UE选择新的TUPF(即TUPF2)，分配新的IP地址(IP address/Prefix 3)并通知UE。此外网络决定该新的PDU会话是用于PDU session1的重定向，因此网络将PDU session1的IP  address/Prefix1指示给UE。UE根据IP address/Prefix1判断PDU session3为PDU session1的重定向。
步骤S1308：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address/Prefix3)，TUPF重定向指示(可选)，旧的IP地址(IP Address/Prefix1)，DN name。
其中步骤S1300/S1302中CP和步骤S1308中的CP可以相同也可以不同。
步骤S1310：Policy Function根据TUPF重定向指示或旧的IP address/Prefix1判断PDU会话1发生了重定向，并根据IP Address/Prefix1将PDU会话3与AF session1进行关联(即Policy Control session3和AF session1进行关联)。
步骤S1312：Policy Function向AF发送消息，通知TUPF重定向事件。
步骤S1314：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1316，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1318，UE发起流程，释放PDU会话1。
在本发明实施例中，假定Policy Function和CP是独立的功能实体，在其他实施例中，Policy Function也集成在CP中。具体实现时CP与Policy Function的交互为内部交互，可以忽略，AF与Policy Function的交互为AF与CP的交互。即CP将根据UE上报的IP address/Prefix1将AF session1与PDU会话3进行关联。
优选实施例2
在本发明优选实施例中，网络决定重定向后，采用UE请求建立新PDU会话的方式执行新PDU会话的建立。图14是根据本发明实施例的实现业 务连续性方法的流程图(二)，如图14所示，该流程包括如下步骤：
步骤S1400：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进行关联；
步骤S1402：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address2，此外网络还为PDU会话1分配了PDU会话标识1。User Id、DN name和PDU会话1可以唯一标识PDU会话1。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。
步骤S1404：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络向UE发送TUPF重定向消息。
步骤S1406：UE接收到重定向消息后，UE向网络发送请求建立新的PDU会话(PDN会话3)的消息，消息中携带User Id，DN name，TUPF重定向指示信息等。网络为UE选择新的TUPF(即TUPF2)，分配新的IP地址(IP address/Prefix 3)并通知UE。此外网络决定该新的PDU会话是用于PDU session1的重定向，因此网络将PDU session1的PDU会话标识1指示给UE。UE根据IP address/Prefix1判断PDU session3为PDU session1的重定
步骤S1408：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address3)，TUPF重定向指示(可选)，PDU会话标识1，DN name。
其中步骤S1400/S1404中CP和步骤S1408中的CP可以相同也可以不同。
步骤S1410：Policy Function根据TUPF重定向指示或PDU会话标识1判断PDU会话1发生了重定向，并根据PDU会话标识1将PDU会话3与AF session1进行关联(即Policy Control session3和AF session1进行关联)。
步骤S1412：Policy Function向AF发送消息，通知TUPF重定向事件。
步骤S1414：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1416，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1418，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
在本发明优选实施例中，网络决定重定向后，采用UE请求建立新PDU会话的方式执行新PDU会话的建立。图15是根据本发明实施例的实现业务连续性方法的流程图(三)，如图15所示，该流程包括如下步骤：
步骤S1500：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了TUPF1，分配了IP address/Prefix1。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进行关联；
步骤S1502：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address/Prefix2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。
步骤S1504：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络向UE发送TUPF重定向消息，并在消息中携带重定向PDU会话标识1。
步骤S1506：UE接收到重定向消息后，UE向网络发送请求建立新的PDU会话(PDN会话3)的消息，消息中携带User Id，DN name，TUPF重定向指示信息等。网络为UE选择新的TUPF(即TUPF2)，分配新的IP地址(IP address/Prefix 3)并通知UE。此外网络决定该新的PDU会话是用于PDU session1的重定向，因此网络分指示重定向PDU会话标识1给UE。UE根据重定向PDU会话标识1判断PDU session3为PDU session1的重定向。
步骤S1508：CP通过策略控制会话1通知Policy Function，PDU会话1对应的重定向PDU会话标识1。
步骤S1510：CP向Policy Function发送请求新的策略控制会话(Policy Control session3)的消息，消息中携带新分配的IP地址(IP Address/Prefix3)，TUPF重定向指示(可选)，重定向PDU会话标识1，DN name。
其中步骤S1500/S1502中CP和步骤S1510中的CP可以相同也可以不同。
步骤S1512：Policy Function根据TUPF重定向指示或重定向PDU会话标识1判断PDU会话1发生了重定向，并根据重定向PDU会话标识1将PDU会话3和AF session 1进行关联(Policy Control session3和AF session1进行关联)。
步骤S1514：Policy Function向AF发送消息，通知TUPF重定向事件。
步骤S1516：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1518，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1520，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进行关联。
优选实施例4
在本发明实施例中，网络决定重定向后，采用网络为UE建立到新的TUPF连接后通知UE的方式建立新的PDU连接。本流程适用于支持采用IPv6的Multi-Homed PDU session。图16是根据本发明实施例的实现业务连续性方法的流程图(四)，如图16所示，该流程包括如下步骤：
步骤S1600：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了TUPF1，分配了IP address/Prefix1。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进行关联；
步骤S1602：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address/Prefix2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。
步骤S1604：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络决定建立新的连接(leg)到TUPF2(即PDU会话3)。
步骤S1606：CP配置一个中间UP(区别于TUPF)作为Multi-homed PDU会话的分叉点。这个UP作为默认路由器。
步骤S1610：可选的，网络决定先重定向PDU会话1，因此网络通知UE新的连接(leg)可用，消息中携带新的IP address/prefix3,重定向指示信息，定时器等参数。此外网络还提供IP address/prefix1用于指示该连接用于PDU会话1的重定向。
步骤S1612：UP(默认IP路由器)发送路由通告消息，携带新的IP Address/Prefix3。若S1006不执行，那么路由通告消息中还携带重定向指示信息，定时器以及用于指示该连接用于PDU会话1的重定向的IP address/prefix1。
步骤S1614：CP向通过策略控制会话1向Policy Function发送策略控制会话修改消息，发送TUPF重定向事件通知以及新的IP Address/prefix3；
步骤S1616：Policy Function向AF发送消息，通知TUPF重定向事件。
步骤S1618：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1620，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1622，网络发起流程，释放PDU会话1。
上述优选实施例中，假定Policy Function和CP是独立的功能实体，在其他实施例中，Policy Function也集成在CP中。具体实现时CP与Policy Function的交互为内部交互，，可以忽略。AF与Policy Function的交互为AF与CP的交互。
优选实施例5
在本发明优选实施例中，网络决定重定向后，采用网络为UE建立到新的TUPF连接后通知UE的方式建立新的PDU连接。本流程适用于支持采用IPv6的Multi-Homed PDU session。图17是根据本发明实施例的实现业务连续性方法的流程图(五)，如图17所示，该流程包括如下步骤：
步骤S1700：UE在AN1向网络请求建立PDU会话1，携带user id和DN name。网络为PDN会话1选择了TUPF1，分配了IP address/Prefix1。，此外网络还为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进行关联；
步骤S1702：UE在AN1下向网络请求建立PDU会话2，携带user id和DN name。网络为PDN会话2选择了TUPF1，分配了IP address/Prefix2。，此外网络还为PDU会话2分配了PDU会话标识2。User Id、DN name和PDU会话2可以唯一标识PDU会话2。TUPF1和CP之间存在Sx会话2，CP和Policy Function之间存在Policy Control session2。
步骤S1704：UE移动到了AN2，网络决策TUPF1对于PDU会话1和PDU会话2不是最优，需要重新选择TUPF。因此网络决定建立新的连接(leg)到TUPF2(即PDU会话3)。
步骤S1706：CP配置一个中间UP(区别于TUPF)作为Multi-homed PDU会话的分叉点。这个UP作为默认路由器。
步骤S1708：可选的，网络决定先重定向PDU会话1，因此网络通知UE新的连接(leg)可用，消息中携带新的IP address/prefix3,重定向指示信息，定时器等参数。此外网络还提供PDU会话标识1用于指示该连接用于PDU会话1的重定向。
步骤S1710：UP(默认IP路由器)发送路由通告消息，携带新的IP  Address/Prefix3。若S1710不执行，那么路由通告消息中还携带重定向指示信息，定时器以及用于指示该连接用于PDU会话1的重定向的PDU会话标识1。
步骤S1712：CP向通过策略控制会话1向Policy Function发送策略控制会话修改消息，发送TUPF重定向事件通知以及新的IP Address/prefix3；
步骤S1714：Policy Function向AF发送消息，通知TUPF重定向事件。
步骤S1716：UE和应用服务器进行应用层交互后，AF通过AF session1向Policy Function提供更新的业务信息；
步骤S1718，Policy Function进行策略决策后，向TUPF2和AN2提供策略信息，TUPF2和AN2执行策略。
步骤S1720，网络发起流程，释放PDU会话1。
在上述所有实施例中，UE和网络之间协商了新建立的PDU会话所重定向的原有PDU会话，并由此确定对应的AF会话。
同样，网络还可以将实施于原有PDU会话的一些策略施加于新建立的PDU会话。
综上所述，本发明实施例达到了以下技术效果：解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以用于保存上述实施例一所提供的页面内容的处理方法所执行的程序代码。
可选地，在本实施例中，上述存储介质可以位于计算机网络中计算机终端群中的任意一个计算机终端中，或者位于移动终端群中的任意一个移动终端中。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的 程序代码：
S1，向终端发送指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收网络侧设备发送的指示信息，其中，指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
在本发明的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在 一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
本发明实施例提供的上述技术方案，可以应用于会话连续的实现过程中，通过向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，采用上述技术方案，解决了相关技术中，终端无法判断新建立的PDU会话是哪个PDU session重定向的问题，进而终端能够根据指示信息确定新建立的PDU会话是由哪个PDU会话切换过来的。

Claims (12)

  1. 一种会话连续的实现方法，包括：
    向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
  2. 根据权利要求1所述的方法，其中，向终端发送指示信息，包括：
    向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
  4. 根据权利要求2或3所述的方法，其中，所述会话标识包括以下至少之一：在建立所述第二PDU会话时，为所述第二PDU会话分配的会话标识；所述第二PDU会话的互联网IP地址或IPv6地址前缀；在重定向所述第二PDU会话时，为所述第二PDU会话分配的会话标识。
  5. 一种会话连续的实现方法，包括：
    接收网络侧设备发送的指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一 PDU会话。
  6. 根据权利要求5所述的方法，其中，所述指示信息包括以下至少之一：所述终端在建立所述第二PDU会话时接收到的所述第二PDU会话的会话标识、所述第二PDU会话的IP地址或IPv6地址前缀、所述终端在网络发送重定向TUPF消息中接收到的所述第二PDU会话标识信息。
  7. 一种会话连续的实现系统，包括：终端，网络侧设备，其中，
    所述网络侧设备，设置为向所述终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
  8. 根据权利要求7所述的系统，其中，所述网络侧设备，还用于向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话，且所述网络侧设备根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
  9. 一种会话连续的实现装置，包括：
    发送模块，设置为向终端发送指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为所述终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
  10. 根据权利要求9所述的装置，其中，所述发送模块，还用于 向所述终端发送携带有所述第二PDU会话的会话标识的指示信息，其中，该会话标识用于唯一标识第二PDU会话，且所述网络侧设备根据所述会话标识确定所述第一PDU会话为第二PDU会话的重定向会话。
  11. 一种会话连续的实现装置，包括：
    接收模块，设置为接收网络侧设备发送的指示信息，其中，所述指示信息用于指示第一协议数据单元PDU会话为第二PDU会话的重定向会话，第一PDU会话为终端确定需要将当前建立的所述第二PDU会话重定向到终结用户面功能TUPF时，向网络侧设备发起建立请求所建立的第一PDU会话。
  12. 根据权利要求11所述的装置，其中，所述指示信息包括以下至少之一：所述终端在建立所述第二PDU会话时接收到的所述第二PDU会话的会话标识、所述第二PDU会话的IP地址或IPv6地址前缀、所述终端在网络发送重定向TUPF消息中接收到的所述第二PDU会话标识信息。
PCT/CN2017/084009 2016-07-08 2017-05-11 会话连续的实现方法、装置及系统 WO2018006650A1 (zh)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=60901694

Family Applications (1)

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

Country Status (2)

Country Link
CN (1) CN107592328A (zh)
WO (1) WO2018006650A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020011173A1 (zh) * 2018-07-10 2020-01-16 华为技术有限公司 搬迁管理方法及装置
US11974355B2 (en) 2018-08-10 2024-04-30 Zte Corporation Indication information sending method, apparatus and system, and storage medium

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108271229B (zh) * 2018-01-31 2020-08-14 中国联合网络通信集团有限公司 一种用户面选择方法及装置
CN116709593A (zh) * 2018-02-14 2023-09-05 华为技术有限公司 确定协议数据单元会话服务网元的方法和装置
KR102479660B1 (ko) * 2018-03-12 2022-12-20 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 Ue 정책의 업데이트 방법 및 장치, 컴퓨터 저장매체
CN110557791B (zh) 2018-05-31 2021-07-20 华为技术有限公司 会话管理方法、设备及系统
CN110582126B (zh) * 2018-06-11 2021-08-13 华为技术有限公司 一种通信方法及装置
CN110662276B (zh) * 2018-06-30 2021-01-01 华为技术有限公司 动态组网方法、设备及系统
CN110784432B (zh) * 2018-07-31 2021-11-19 华为技术有限公司 一种会话创建方法及装置
CN113439486B (zh) * 2019-02-14 2023-10-27 Lg电子株式会社 用于显示用于使用ma pdu会话的信息的方法和终端
CN112015566A (zh) * 2019-05-30 2020-12-01 中国电信股份有限公司 用户面功能切换方法、装置和系统
CN112243300B (zh) * 2019-07-19 2022-11-08 中国移动通信有限公司研究院 连接建立方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101351032A (zh) * 2007-07-20 2009-01-21 华为技术有限公司 域切换方法、服务器与控制装置
CN101917429A (zh) * 2007-07-20 2010-12-15 华为技术有限公司 域切换方法、服务器与控制装置
US20110145419A1 (en) * 2009-12-15 2011-06-16 Interdigital Patent Holdings, Inc. Inter-device mobility session release
CN103748840A (zh) * 2011-05-09 2014-04-23 橙公司 用于处理针对在两个接入网络之间切换呼叫的请求的方法
CN104094666A (zh) * 2012-01-31 2014-10-08 诺基亚公司 用于促进通信会话连续性的方法和设备
WO2015137631A1 (ko) * 2014-03-10 2015-09-17 엘지전자 주식회사 근접 서비스 수행 방법 및 사용자 장치

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101351032A (zh) * 2007-07-20 2009-01-21 华为技术有限公司 域切换方法、服务器与控制装置
CN101917429A (zh) * 2007-07-20 2010-12-15 华为技术有限公司 域切换方法、服务器与控制装置
US20110145419A1 (en) * 2009-12-15 2011-06-16 Interdigital Patent Holdings, Inc. Inter-device mobility session release
CN103748840A (zh) * 2011-05-09 2014-04-23 橙公司 用于处理针对在两个接入网络之间切换呼叫的请求的方法
CN104094666A (zh) * 2012-01-31 2014-10-08 诺基亚公司 用于促进通信会话连续性的方法和设备
WO2015137631A1 (ko) * 2014-03-10 2015-09-17 엘지전자 주식회사 근접 서비스 수행 방법 및 사용자 장치

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020011173A1 (zh) * 2018-07-10 2020-01-16 华为技术有限公司 搬迁管理方法及装置
US11974355B2 (en) 2018-08-10 2024-04-30 Zte Corporation Indication information sending method, apparatus and system, and storage medium

Also Published As

Publication number Publication date
CN107592328A (zh) 2018-01-16

Similar Documents

Publication Publication Date Title
WO2018006650A1 (zh) 会话连续的实现方法、装置及系统
EP4087367B1 (en) Method, device, and system for implementing continuous session
CN110933623B (zh) 一种通信方法和装置
US20210112486A1 (en) Processing method, terminal, and network element
WO2019214300A1 (zh) 数据传输方法、装置和可读存储介质
EP2561708B1 (en) Method and apparatus for determining access point service capabilities
US20140237125A1 (en) Method, apparatus, and system for establishing device-to-device connection
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
WO2015051701A1 (zh) Wifi同步apn网络多通道并发上网并自动优选wifi联网的方法
WO2014005330A1 (zh) 一种服务注册与发现的方法，设备和系统
EP2966895A1 (en) Method and system for transmitting data packet, terminal device and network device
US10716159B2 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
US20220264690A1 (en) Method for influencing data traffic routing in a core network
EP3871453B1 (en) Paging of idle state wireless communication devices
CN105850183A (zh) 无线网络接入控制方法及设备、系统
CN111182657A (zh) 一种隧道协商建立方法及装置
CA3189164A1 (en) Application relocation method and apparatus
WO2019238060A1 (zh) 一种数据传输方法及装置
CN101784027A (zh) 紧急会话切换方法及系统
EP2899950B1 (en) Method and device for obtaining internet protocol address
WO2014121599A1 (zh) 传递蜂窝网络负荷信息的方法和相关设备
JP2022540390A (ja) サービスデータ適応プロトコル層エンティティの管理方法、送信端末及び受信端末
WO2014177022A1 (zh) 流移动性支持能力处理方法、装置、pdn gw
WO2020197454A1 (en) Paging of idle state wireless communication devices
WO2018010442A1 (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: 17823462

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17823462

Country of ref document: EP

Kind code of ref document: A1