WO2019149177A1 - 一种业务分流的方法和装置 - Google Patents

一种业务分流的方法和装置 Download PDF

Info

Publication number
WO2019149177A1
WO2019149177A1 PCT/CN2019/073523 CN2019073523W WO2019149177A1 WO 2019149177 A1 WO2019149177 A1 WO 2019149177A1 CN 2019073523 W CN2019073523 W CN 2019073523W WO 2019149177 A1 WO2019149177 A1 WO 2019149177A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
server
service
functional entity
terminal device
Prior art date
Application number
PCT/CN2019/073523
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 WO2019149177A1 publication Critical patent/WO2019149177A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2557—Translation policies or rules
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and apparatus for service offloading.
  • a protocol data unit (PDU) session is between a user equipment (UE) and a data network (DN) defined in a fifth generation (5th generation, 5G) mobile communication system. Connection to provide PDU connectivity services.
  • the PDU connection service supported by the 5G core network (CN) refers to a service that provides PDU exchange between the UE and a data network (DN) determined by a data network name (DNN).
  • the UE may establish a PDU session that is served by different user plane function (UPF) entities to connect to the same DN.
  • UPF user plane function
  • a session management function (SMF) entity may insert an “uplink classifier (ULCL)” for one PDU session of the UE, and the ULCL is used in one
  • the filtering condition provided by the SMF entity on the UPF entity supporting the ULCL function so that the UPF entity offloads multiple services of one PDU session to different UPF anchors, and each UPF anchor corresponds to one DN to pass the target DN.
  • the DN closest to the UE performs traffic transmission with the UE.
  • the service 1 of one PDU session is offloaded from the UPF anchor 1 shown in FIG. 1 to the UPF anchor 2 by the UPF containing the ULCL function.
  • the change of the anchor usually causes the PDU session established between the UE and the DN corresponding to the anchor to be interrupted.
  • the problem of the PDU session interruption caused by the service offloading scenario is not solved in the conventional technical solution.
  • the embodiment of the invention provides a method and a device for service offloading, which are used to solve the problem of PDU session interruption caused in a service offload scenario.
  • the present application provides a method for service offloading, where: when a first session between a terminal device and a first data network DN requires a second functional entity, the first functional entity determines a second session for the first session. a function entity, the second function entity is configured to offload the at least one first service included in the first session; the first function entity sends the first mapping rule information to the second function entity, where the first mapping rule information is used to indicate the second function entity The first service is sent to the third functional entity, and the third functional entity is configured to implement a conversion between the address of the first service from the address of the first server to the address of the second server.
  • the present application provides a method for service offloading.
  • the first functional entity determines a second functional entity for the first session, and The second function entity sends first mapping rule information for instructing the second function entity to send the first service to the third function entity, so that after receiving the first service, the second function entity may
  • the data in the first service is sent to the third functional entity, and the third functional entity realizes the conversion between the address of the first service from the address of the first server to the address of the second server, so that the presence may be first
  • the service provides a better data network
  • the data in the first service is offloaded, and since the terminal device does not need to change the destination IP of the first service in the process of offloading the first service in this application, the first When the service is offloaded, the first PDU session is not interrupted.
  • the method provided by the application further includes: receiving, by the first functional entity, the first functional entity is between the terminal and the first data network DN
  • the first session determines a first request message for the second functional entity.
  • the first function entity determines that the second function entity needs to be determined for the first session between the terminal and the first data network DN, and the first function entity determines that the terminal device is required to be triggered by the first request message.
  • Determining, by the first session between the first data network DN, the second functional entity by receiving the first request message, such that the first functional entity can determine that the first session between the terminal and the first data network DN needs to be determined
  • Two functional entities may also determine the second functional entity for the first session according to other triggering conditions.
  • the first request message includes any one of the following: a mapping relationship between the information of the second data network DN, the information of the second DN, the information of the third functional entity, the address of the first server, and the address of the second server, wherein the address of the first server is a request of the terminal device
  • the source address of the first service, the address of the second server is the target address of the first service requested by the terminal device, and the second DN corresponds to the third functional entity, so that the first functional entity determines that the second functional entity needs to be determined for the first session.
  • the method provided by the application further includes: the first functional entity according to the first Determining the first mapping rule information by using a mapping relationship between the address of the server and the address of the second server, and determining the first mapping rule information according to the mapping relationship between the address of the first server and the address of the second server, which may be convenient
  • the second functional entity implements forwarding of data in the first service, that is, the first service is accurately sent to the third functional entity.
  • the first server is a source address where the first service is located
  • the second server is a server that serves the first service in the destination data network corresponding to the third functional entity.
  • the first mapping rule information includes: information about the first service and associated with the first service The third functional entity's information.
  • the second function entity may be accurate according to the first mapping rule information when receiving the first service The first service is forwarded to the third functional entity indicated by the information of the third functional entity associated with the information of the first service.
  • the method provided by the application further includes: sending, by the first functional entity, to the third functional entity a mapping relationship between the address of the first server and the address of the second server, where the mapping function is used by the third functional entity to map the address of the first service from the address of the first server to the address of the second server, or
  • the tri-function entity maps the address of the first service from the address of the second server to the address of the first server.
  • the third functional entity can accurately map the address of the first server to the address of the second server when receiving the request of the terminal device for the first service, and Obtaining the first service at the data network corresponding to the second server, and after obtaining the first service, in order to enable the terminal device to accurately identify the first service, mapping the address of the requested first service from the address of the second server Is the address of the first server.
  • the present application provides a service offloading method, including: acquiring, by a fourth functional entity, location information of a terminal device; and determining, by the fourth functional entity, that the second service entity exists as a second service of the terminal device according to the location information of the terminal device.
  • the fourth functional entity sends a first request message for indicating a second functional entity for the first session between the terminal device and the first data network DN, the second functional entity is for the first At least one first service offload associated with the session.
  • the first request message includes any one of: information indicating that the second data network DN serving the first service exists, the second DN The information, the information of the third functional entity, the mapping between the address of the first server and the address of the second server, wherein the address of the first server is the source address of the first service requested by the terminal device, and the address of the second server The target device is requested for the destination address of the first service, and the second DN is associated with the third functional entity.
  • the method provided by the application further includes: the fourth functional entity sends the indication to the terminal device A second request message for reporting location information of the terminal device.
  • the method provided by the application further includes: the fourth functional entity to the terminal device Sending first indication information for instructing the terminal device to map an address of the first service from an address of the first server to an address of the second server.
  • the method provided by the application further includes: the fourth functional entity to the terminal device Transmitting a mapping relationship between the address of the first server and the address of the second server, where the mapping relationship is used by the terminal device to map the address of the first service from the address of the first server to the address of the second server, where the address of the first server is The terminal device requests the source address of the first service, and the address of the second server is the target address of the first service requested by the terminal device.
  • the application provides a method for service offloading, comprising: sending, by a terminal device, location information of a terminal device to a fourth functional entity; the terminal device receiving, by the fourth functional entity, an address indicating the first server and the second a mapping relationship between the addresses of the server, where the address of the first server is the source address of the data in the first service, and the address of the second server is the target address of the first service requested by the terminal device; An indication information that maps an address of the first service from an address of the first server to an address of the second server.
  • the method provided by the application further includes: the terminal device receives the fourth function entity to send a second request message for instructing the terminal device to report location information of the terminal device.
  • the method provided by the application further includes: the terminal device sends the address of the first service from the first After the address of the server is mapped to the address of the second server, the first service is requested according to the address of the second server.
  • the first indication information includes: an address of the first server, and a second A mapping relationship between addresses of the server for the terminal device to map the address of the first service from the address of the second server to the address of the first server.
  • the present application provides a method for service offloading, including: receiving, by a second function entity, first mapping rule information that is sent by a first function entity to instruct a second function entity to send a first service to a third function entity a third functional entity is configured to implement a conversion between an address of the first service from an address of the first server to an address of the second server; after receiving the first service, the second functional entity sends the first service to the first Three functional entities.
  • the first mapping rule information includes: information of a first service and information of a third function entity associated with the first service.
  • the present application provides a method for service offloading, including: receiving, by a third function entity, first indication information sent by a first function entity, where the first indication information is used to indicate that the third function entity implements an address of the first service Converting from the address of the first server to the address of the second server; after receiving the first service, the third functional entity realizes the address of the first service from the address of the first server to the address of the second server The conversion, wherein the first server requests the terminal device for the source address of the first service, and the second server requests the terminal device for the target address of the first service.
  • the first indication information is a mapping relationship between an address of the first server and an address of the second service, where the mapping relationship is used for the third functional entity
  • the address of the first service is mapped from the address of the first server to the address of the second server, or is used by the third functional entity to map the address of the first service from the address of the second server to the address of the first server.
  • the third functional entity implements the address of the first service after receiving the first service
  • the conversion between the address of the first server and the address of the second server includes: the third function entity receives the first service sent by the terminal device, and the third function entity maps the address of the first service from the address of the first server to the first The address of the second server, or the third function entity receives the first service sent by the second DN, and the third function entity maps the address of the first service from the address of the second server to the address of the first server.
  • the application provides a service offloading device, where the service offloading device can implement the method for diverting traffic described in any one of the first aspect to the fourth possible implementation manner of the first aspect .
  • the device for offloading the service may be a first functional entity, and the first functional entity may be an SMF or a chip disposed in the SMF.
  • the above method can be implemented by software, hardware, or by executing corresponding software through hardware.
  • the application provides a service offloading device, where the first session between the terminal device and the first data network DN needs to be second.
  • the determining unit is configured to determine that the second functional entity needs to be determined for the first session between the terminal and the first data network DN, the first functional entity determining for the first session a second functional entity of the at least one first service split that is included in the session; the sending unit, configured to send, to the second functional entity, the first mapping rule information used to instruct the second functional entity to send the first service to the third functional entity
  • the third functional entity is configured to implement a conversion between an address of the first service from an address of the first server to an address of the second server.
  • the device for the service offloading provided by the application further includes: a receiving unit, configured to receive, by the first functional entity, a terminal device and a first The first session between the data networks DN determines a first request message for the second functional entity.
  • the determining unit is configured to determine, according to the triggering of the first request message, that the first session between the terminal device and the first data network DN needs to determine the second functional entity.
  • the first request message includes any one of the following: a mapping relationship between the information of the second data network DN, the information of the second DN, the information of the third functional entity, the address of the first server, and the address of the second server, wherein the address of the first server is a request of the terminal device
  • the source address of the first service, the address of the second server is the target address of the first service requested by the terminal device, and the second DN is associated with the third functional entity.
  • the determining unit is further configured to: according to the address of the first server and the address of the second server The mapping relationship between the first mapping rule information is determined.
  • the first mapping rule information includes: information and information of the first service Information about a third functional entity associated with a service.
  • the sending unit is further configured to send the first server to the third functional entity.
  • a mapping relationship between the address and the address of the second server, the mapping function for the third functional entity to map the address of the first service from the address of the first server to the address of the second server, or for the third functional entity The address of the first service is mapped from the address of the second server to the address of the first server.
  • the present application further provides an apparatus for traffic offloading, where the apparatus for offloading includes: a processor and a transmitter, wherein the processor determines that the first session between the terminal device and the first data network DN needs to determine the second function.
  • the apparatus for offloading includes: a processor and a transmitter, wherein the processor determines that the first session between the terminal device and the first data network DN needs to determine the second function.
  • a second functional entity for determining, for the first session, the at least one first service split included in the first session
  • the transmitter configured to send, to the second functional entity, the second functional entity
  • the first mapping rule information sent by the service to the third functional entity is used to implement the conversion between the address of the first service from the address of the first server to the address of the second server.
  • the device for offloading the service further includes a receiver, where the device for supporting the service offloading implements the message/data receiving on the device side of the service offloading described in any one of the foregoing first aspect to the first aspect.
  • the transmitter is further configured to support the service offloading device to implement the related operation of the message/data transmission on the device side of the service offloading described in any one of the first aspect to the first aspect
  • the processor is further configured to perform The operation of message/data processing is performed on the device side of the service offload described in any of the above first aspect to the first aspect.
  • the device for offloading services in the application further includes: a bus and a memory, the memory is used to store code and data, and the processor, the receiver, the transmitter, and the memory are connected by using a bus.
  • the device for offloading the service may be an SMF or a chip applied in the SMF, and the device for offloading the service may include at least one processor.
  • the at least one processor is configured to perform the offloading of the service in the method described in any one of the first aspect to the fifth possible implementation of the first aspect by executing the instruction to support the apparatus for the service offloading Related operations of message processing or control performed on the device side.
  • the apparatus may further comprise a memory for coupling with the at least one processor, which stores programs (instructions) and data necessary for the device.
  • the device for offloading the service may further include a communication interface for supporting communication between the device for the service offload and other network elements (for example, the second functional entity and the third functional entity).
  • the communication interface may be a transceiver circuit or an interface circuit, wherein the transceiver circuit for supporting the service offloading device performs the method described in any one of the first aspect to the fifth possible implementation of the first aspect
  • the device side of the service offload performs related operations of message reception and transmission.
  • the device for offloading the service may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected by a bus.
  • the present application provides an apparatus for service offloading, where the apparatus for offloading the service may implement the method of service offloading described in any one of the second aspect to the fourth possible implementation manner of the second aspect.
  • the device for offloading the service may be a third functional entity, such as AF, or a chip disposed in the AF.
  • the above method can be implemented by software, hardware, or by executing corresponding software through hardware.
  • the device for offloading the service includes: an acquiring unit, configured to acquire location information of the terminal device; and a determining unit, configured to determine, according to the location information of the terminal device, the existence a second data network DN of the first service service of the terminal device; and a sending unit, configured to send, after the determining unit determines that the second data network DN exists, the indication between the terminal device and the first data network DN
  • a session determines a first request message of the second function entity, and the second function entity is configured to offload the at least one first service included in the first session.
  • the first request message includes any one of: information indicating that the second data network DN serving the first service exists, the second DN The information, the information of the third functional entity, the mapping between the address of the first server and the address of the second server, wherein the address of the first server is the source address of the first service requested by the terminal device, and the address of the second server The target device is requested for the destination address of the first service, and the second DN is associated with the third functional entity.
  • the sending unit is further configured to send, to the terminal device, location information for indicating the reporting of the terminal device Second request message.
  • the sending unit is further configured to send, to the terminal device, the terminal device Mapping the address of the first service from the address of the first server to the first indication of the address of the second server.
  • the sending unit is further configured to send the address of the first server to the terminal device a mapping relationship between the address of the first server and the address of the second server, the address of the first server is the address of the second server, and the address of the first server is the first request of the terminal device The source address of the service, and the address of the second server is the target address of the first service requested by the terminal device.
  • the present application further provides an apparatus for offloading services, where the apparatus for offloading includes: a processor and a transmitter, wherein the processor is configured to acquire location information of the terminal device, and the transmitter is configured to determine, in the determining unit, that the second In the case of the data network DN, transmitting a first request message for indicating a second functional entity for the first session between the terminal device and the first data network DN, the second functional entity for associating the first session At least one first service is offloaded.
  • the apparatus for offloading includes: a processor and a transmitter, wherein the processor is configured to acquire location information of the terminal device, and the transmitter is configured to determine, in the determining unit, that the second In the case of the data network DN, transmitting a first request message for indicating a second functional entity for the first session between the terminal device and the first data network DN, the second functional entity for associating the first session At least one first service is offloaded.
  • the device for offloading the service further includes a receiver, where the device for supporting the service offloading implements the message/data receiving on the device side of the service offloading described in any one of the foregoing second aspect to the second aspect.
  • the transmitter is further configured to support the service offloading device to implement the related operations of the message/data transmission on the device side of the service offloading described in any one of the second aspect to the second aspect
  • the processor is further configured to perform The operation of the message/data processing on the device side of the service offload described in any of the above second aspect to the second aspect.
  • the device for offloading services in the application further includes: a bus and a memory, the memory is used to store code and data, and the processor, the receiver, the transmitter, and the memory are connected by using a bus.
  • the device for offloading the service may be AF or applied to a chip in the AF, and the device for splitting the service may include at least one processor.
  • the at least one processor is configured to perform the shunting of the service in the method described in any one of the second aspect to the second possible implementation of the second aspect to the second aspect of the apparatus Related operations of message processing or control performed on the device side.
  • the apparatus may further comprise a memory for coupling with the at least one processor, which stores programs (instructions) and data necessary for the device.
  • the device for offloading the service may further include a communication interface for supporting communication between the device for the service offload and other network elements (for example, the terminal device).
  • the communication interface may be a transceiver circuit or an interface circuit, wherein the transceiver circuit for supporting the service offloading device performs the method described in any one of the second aspect to the second possible implementation of the second aspect
  • the device side of the service offload performs related operations of message reception and transmission.
  • the device for offloading the service may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected by a bus.
  • the present application provides an apparatus for service offloading, where the apparatus for offloading the service may implement the method of service offloading described in any one of the second possible implementation manners of the third aspect to the third aspect.
  • the device for offloading the service may be a terminal device or a chip disposed in the terminal device.
  • the above method can be implemented by software, hardware, or by executing corresponding software through hardware.
  • the device for offloading the service includes: a sending unit, configured to send location information of the terminal device to the fourth functional entity, and a receiving unit, configured to receive the fourth a first indication information sent by the function entity, where the first indication information is used to indicate a mapping relationship between an address of the first server and an address of the second server, where the address of the first server is the terminal device request a source address of the first service, where the address of the second server is a target address of the first service, and a processing unit, configured to: use the data in the first service according to the first indication information The address is mapped from the address of the first server to the address of the second server.
  • the receiving unit is further configured to receive a second request message that is sent by the fourth functional entity and is used to indicate that the terminal device reports the location information of the terminal device.
  • the processing unit provided by the application is further configured to request the first address according to the address of the second server. business.
  • the first indication information includes: an address of the first server and a second server A mapping relationship between addresses for the terminal device to map an address of the first service from an address of the second server to an address of the first server.
  • the present application further provides a device for traffic offloading, where the device for offloading includes: a transmitter and a receiver, wherein the transmitter is configured to send location information of the terminal device to the fourth functional entity, and the receiver is configured to receive the first a first indication information sent by the four-function entity for indicating a mapping relationship between an address of the first server and an address of the second server, where the address of the first server is a source address of the first service requested by the terminal device, The address of the second server is that the terminal device requests the target address of the first service, and the processor is further configured to: map the address of the data in the first service from the address of the first server to the address of the second server according to the first indication information. .
  • the processor in the device for offloading the service is further configured to perform the operation of the message/data processing on the device side of the service offloading described in any one of the foregoing third to third aspects.
  • the device that is used by the transmitter to support the service offloading implements the related operation of the message/data transmission on the device side of the service offloading described in any one of the foregoing third to third aspects
  • the receiver is further used for The apparatus for supporting service offloading implements the related operation of message/data reception on the device side of the service offload described in any one of the third aspect to the third aspect.
  • the device for offloading services in the application further includes: a bus and a memory, the memory is used to store code and data, and the processor, the receiver, the transmitter, and the memory are connected by using a bus.
  • the device for offloading the service may be a terminal or a chip applied to the terminal, and the device for offloading the service may include at least one processor.
  • the at least one processor is configured to perform the offloading of the service in the method described in any one of the third aspect to the third aspect of the third aspect, by performing an instruction to support the device for the service offloading Related operations of message processing or control performed on the device side.
  • the apparatus may further comprise a memory for coupling with the at least one processor, which stores programs (instructions) and data necessary for the device.
  • the device for offloading the service may further include a communication interface for supporting communication between the device for offloading the service and other network elements (for example, the fourth functional entity).
  • the communication interface may be a transceiver circuit or an interface circuit, wherein the transceiver circuit for supporting the service offloading device performs the method described in any one of the third aspect to the third possible implementation of the third aspect
  • the device side of the service offload performs related operations of message reception and transmission.
  • the device for offloading the service may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected by a bus.
  • the present application provides an apparatus for service offloading, where the apparatus for offloading the service can implement the method of service offloading described in any one of the first possible implementation manners of the fourth aspect to the fourth aspect.
  • the device for offloading the service may be a second functional entity, such as an uplink classifier, or a chip disposed in an uplink classifier.
  • the above method can be implemented by software, hardware, or by executing corresponding software through hardware.
  • the apparatus for offloading the service is the second function entity
  • the device for offloading the service includes: a receiving unit, configured to receive, by the first function entity, the second function entity to indicate the first service Sending to the first mapping rule information of the third function entity, the third function entity is configured to implement conversion between the address of the first service from the address of the first server to the address of the second server; the second functional entity receives the first After a service, the first service is sent to the third functional entity.
  • the first mapping rule information includes: information of a first service and information of a third function entity associated with the first service.
  • the present application further provides an apparatus for service offloading, where the apparatus for offloading includes: a transmitter and a receiver, where the receiver is configured to receive, by the first functional entity, the second function entity to send the first service. a first mapping rule information to the third functional entity, the third functional entity is configured to implement a conversion between an address of the first service from an address of the first server to an address of the second server, and the transmitter is configured to receive the first After a service, the first service is sent to the third functional entity.
  • the device for offloading the service further includes a processor, configured to perform the operation of the message/data processing on the device side of the service offloading described in any one of the foregoing fourth to fourth aspects.
  • the device that is used by the transmitter to support the service offloading implements the related operation of the message/data transmission on the device side of the service offloading described in any one of the foregoing fourth to fourth aspects
  • the receiver is further used for The apparatus for supporting service offloading implements the related operation of message/data reception on the device side of the service offload described in any one of the fourth aspect to the fourth aspect.
  • the device for offloading services in the application further includes: a bus and a memory, the memory is used to store code and data, and the processor, the receiver, the transmitter, and the memory are connected by using a bus.
  • the device for offloading the service may be a second functional entity or a chip applied to the second functional entity, and the device for splitting the service may include at least one processor.
  • the at least one processor is configured to perform the shunting of the service in the method described in any one of the fourth to fourth aspects of the fourth aspect to the fourth aspect Related operations of message processing or control performed on the device side.
  • the apparatus may further comprise a memory for coupling with the at least one processor, which stores programs (instructions) and data necessary for the device.
  • the device for offloading the service may further include a communication interface for supporting communication between the device for offloading the service and other network elements (for example, the first functional entity).
  • the communication interface may be a transceiver circuit or an interface circuit, wherein the transceiver circuit for supporting the service offloading device performs the method described in any one of the fourth aspect to the fourth possible implementation of the fourth aspect
  • the device side of the service offload performs related operations of message reception and transmission.
  • the device for offloading the service may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected by a bus.
  • the present application provides an apparatus for service offloading, where the apparatus for offloading the service may implement the method of service offloading described in any one of the second possible implementation manners of the fifth aspect to the fifth aspect.
  • the device for offloading the service may be a third functional entity, for example, UPF achor, or a chip set in the UPF achor.
  • the above method can be implemented by software, hardware, or by executing corresponding software through hardware.
  • the third functional entity is the UPF achor
  • the receiving unit is configured to receive, by the first functional entity, an address that is used by the first functional entity to indicate that the third functional entity implements the first service from the address of the first server to the second server.
  • the first indication information of the conversion between the addresses the processing unit, configured to implement, after receiving the first service, a conversion between an address of the first service from an address of the first server to an address of the second server.
  • the first indication information is a mapping relationship between an address of the first server and an address of the second service, where the mapping relationship is used for the third
  • the functional entity maps the address of the first service from the address of the first server to the address of the second server, or is used by the third functional entity to map the address of the first service from the address of the second server to the address of the first server.
  • the processing unit is configured to receive the first service sent by the terminal device,
  • the third functional entity maps the address of the first service from the address of the first server to the address of the second server, or the processing unit is specifically configured to receive the first service sent by the second DN, where the third functional entity will be the first service
  • the address is mapped from the address of the second server to the address of the first server.
  • the device for offloading the service may be a third functional entity or a chip applied to the third functional entity, and the device for splitting the service may include at least one processor.
  • the at least one processor is configured to perform the offloading of the service in the method described in any one of the fifth aspect to the fifth aspect of the fifth aspect to the fifth aspect Related operations of message processing or control performed on the device side.
  • the apparatus may further comprise a memory for coupling with the at least one processor, which stores programs (instructions) and data necessary for the device.
  • the device for offloading the service may further include a communication interface for supporting communication between the device for offloading the service and other network elements (for example, the first functional entity).
  • the communication interface may be a transceiver circuit or an interface circuit, wherein the transceiver circuit for supporting the service offloading device performs the method described in any one of the first possible implementation manners of the fifth aspect to the fifth aspect
  • the device side of the service offload performs related operations of message reception and transmission.
  • the device for offloading the service may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected by a bus.
  • the present application provides a computer readable storage medium, wherein when the computer readable storage medium is applied to a service shunt, the computer readable storage medium stores instructions, and when the instructions are run on the computer, causes the computer A method of performing traffic offloading as described in any one of the above first aspect to the first aspect.
  • the present application provides a computer readable storage medium, wherein when the computer readable storage medium is applied to a service shunt, the computer readable storage medium stores instructions, and when the instructions are run on the computer, causes the computer A method of performing traffic offloading as described in any one of the above second aspect to the second aspect.
  • the present application provides a computer readable storage medium, wherein when the computer readable storage medium is applied to a service shunt, the computer readable storage medium stores instructions, and when the instructions are run on the computer, causes the computer A method of performing traffic offloading as described in any one of the above third to third aspects.
  • the present application provides a computer readable storage medium, wherein when the computer readable storage medium is applied to a service shunt, the computer readable storage medium stores instructions, and when the instructions are run on the computer, causes the computer A method of traffic offloading as described in any one of the fourth to fourth aspects above.
  • the present application provides a computer readable storage medium, wherein when the computer readable storage medium is applied to a service offloading device, the computer readable storage medium stores instructions for causing the computer to operate when the computer is run on the computer A method of traffic offloading as described in any one of the fifth to fifth aspects above.
  • the present application provides a computer program product comprising instructions, wherein a computer program product stores instructions, when the instruction is executed, causing the first functional entity to perform the first aspect to the fourth aspect of the first aspect A method of traffic offloading as described in any of the possible implementations.
  • the application provides a computer program product comprising instructions, wherein the computer program product stores instructions, when the instruction is executed, causing the fourth functional entity to perform the fourth aspect to the fourth aspect of the second aspect A method of traffic offloading as described in any of the possible implementations.
  • the application provides a computer program product comprising instructions, wherein the computer program product stores instructions, when the instruction is executed, causing the terminal device to perform the fourth possibility of the third aspect to the third aspect A method of traffic offloading as described in any of the implementations.
  • the application provides a computer program product comprising instructions, wherein the computer program product stores instructions, when the instruction is executed, causing the second functional entity to perform the first to fourth aspects of the fourth aspect A method of traffic offloading as described in any of the possible implementations.
  • the present application provides a computer program product comprising instructions, wherein an instruction is stored in a computer program product, and when the instruction is executed, causing a third functional entity to perform the first aspect of the fifth aspect to the fifth aspect A method of traffic offloading as described in any of the possible implementations.
  • the present application provides a chip system, which is applied to a first functional entity, the chip system includes at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to be stored and stored in An instruction in the chip system to perform the method of traffic offloading as described in any one of the first aspect to the first aspect.
  • the present application provides a chip system, which is applied to a fourth functional entity, the chip system includes at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is used to run the instruction.
  • the present application provides a chip system for use in a terminal device, the chip system including at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to execute an instruction to execute A method of service offloading as described in any of the third aspects.
  • the present application provides a chip system, which is applied to a second functional entity, the chip system includes at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction.
  • the chip system includes at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction.
  • the present application provides a chip system, which is applied to a third functional entity, the chip system includes at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction to A method of performing traffic offloading as described in any of the fifth aspects.
  • the chip system described above in the application further includes at least one memory, where the at least one memory stores an instruction.
  • the present application provides a communication system comprising a first functional entity as described in the sixth or sixth aspect above, a fourth functional entity described in any one of the ninth or ninth aspects, and a tenth The second functional entity described in the two aspects, and the third functional entity described in the fourteenth aspect.
  • system may further include other devices in the solution provided by the embodiment of the present invention that interact with the fourth functional entity, the first functional entity, or the second functional entity or the third functional entity.
  • FIG. 1 is a schematic diagram of a method for service offloading provided in the prior art
  • FIG. 2 is a structural diagram of a service offloading system provided by the present application.
  • FIG. 3 is a structural diagram of another service offloading system provided by the present application.
  • FIG. 4 is a schematic flowchart 1 of a method for service offloading provided by the present application.
  • FIG. 5 is a schematic flowchart 2 of a method for service offloading provided by the present application.
  • FIG. 6 is a schematic diagram of a first mapping rule information provided by the present application.
  • FIG. 7 is a schematic flowchart 3 of a method for service offloading provided by the present application.
  • FIG. 8 is a schematic flowchart 4 of a method for service offloading provided by the present application.
  • FIG. 9 is a schematic diagram of another first mapping rule information provided by the present application.
  • FIG. 10 is a schematic flowchart 5 of a method for service offloading provided by the present application.
  • FIG. 11 is a schematic flowchart 6 of a method for service offloading provided by the present application.
  • FIG. 12 is a schematic structural diagram 1 of a first functional entity according to the present application.
  • FIG. 13 is a schematic structural diagram 2 of a first functional entity according to the present application.
  • FIG. 14 is a schematic structural diagram 3 of a first functional entity according to the present application.
  • FIG. 15 is a schematic structural diagram 1 of a fourth functional entity according to the present application.
  • 16 is a schematic structural diagram 2 of a fourth functional entity according to the present application.
  • FIG. 17 is a schematic structural diagram 3 of a fourth functional entity according to the present application.
  • FIG. 18 is a schematic structural diagram 1 of a terminal device according to the present application.
  • FIG. 19 is a schematic structural diagram 2 of a terminal device according to the present application.
  • 20 is a schematic structural diagram 3 of a terminal device according to the present application.
  • FIG. 21 is a schematic structural diagram 1 of a second functional entity according to the present application.
  • FIG. 22 is a schematic structural diagram 2 of a second functional entity according to the present application.
  • FIG. 23 is a schematic structural diagram 3 of a second functional entity according to the present application.
  • FIG. 24 is a schematic structural diagram 1 of a third functional entity according to the present application.
  • FIG. 25 is a schematic structural diagram 2 of a third functional entity according to the present application.
  • FIG. 26 is a schematic structural diagram 3 of a third functional entity according to the present application.
  • FIG. 27 is a schematic structural diagram of a chip system provided by the present application.
  • the present application provides a method and an apparatus for service offloading to solve the problem of PDU session interruption caused in a service offload scenario.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • first, second, and the like in this application are only used to distinguish different objects, and the order is not limited.
  • first functional entity and the second functional entity are merely for distinguishing different functional entities, and are not limited in their order.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 2 is a schematic structural diagram of a service offloading system applied to a method for service offloading provided by the present application.
  • the method includes: a first functional entity 101, and a second function.
  • the fourth functional entity 104 and the first functional entity 101 may communicate directly or indirectly, for example, by other functional entity forwarding, for example, between the fourth functional entity 104 and the first functional entity 101.
  • the sixth functional entity 106 as shown in FIG. 2 forwards the communication.
  • the fourth functional entity 104 is in communication with at least one terminal 107, wherein the terminal 107 and the fifth functional entity 105 have a first session, the first session can be established for the first functional entity 101, so that the terminal 107 can pass
  • the first session is a service transmission between the data network corresponding to the fifth functional entity 105.
  • the first session may be a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the first functional entity 101 is configured to determine a second functional entity 102 for the first session, and then send the first mapping rule to the second functional entity 102, so that the second functional entity can be in the first session according to the first mapping rule.
  • a part of the service is sent to the third functional entity 103.
  • the first functional entity 101 is further configured to send a mapping relationship between the address of the first server and the address of the second server to the third functional entity 103.
  • the first server is a server that obtains the first service when the first service of the terminal communicates with the source data network, that is, the first server belongs to one server in the source data network, and the second server is the first service and destination data of the terminal.
  • the third function entity 103 is configured to: when receiving the uplink service sent by the terminal, convert the address of the uplink service from the address of the first server to the address of the second server, and send it out, and serve to receive the sent to the terminal.
  • the address of the downlink service is converted from the address of the second server to the address of the first server, and is sent out.
  • the fourth functional entity 104 is configured to acquire location information of the terminal 107, and determine, according to the location information of the terminal 107, whether there is a destination data network that provides better service for a certain service of the terminal.
  • the information of the data network includes information such as an access address of the data network, a name, a geographical location of the deployment, and the like.
  • a data network is used to provide an external network for data services.
  • terminals may be distributed throughout the wireless network, and each terminal may be static or mobile.
  • the network element or entity corresponding to the first functional entity 101 may be a session management function (SMF) entity; the second functional entity 102
  • the corresponding network element or entity may be a network element that has a service for offloading a session, for example, an uplink classifier (UL CL) or a branching point network element (branching point).
  • the network element or entity corresponding to the third functional entity 103 may be a user plane function (UPF) anchor (achor); the network element or entity corresponding to the fourth functional entity 104 may be an application function (application) Function, AF), the network element or entity corresponding to the fifth functional entity 105 may be the second UPF achor.
  • UPF user plane function
  • the third functional entity 103 is connected to the second data network through the N6 interface, and the fifth functional entity 105 is connected to the first data network through the N6 interface.
  • the 5G network may further include an access device (for example, an access network (AN)), an access and mobility management function (AMF) entity, and unified data.
  • an access device for example, an access network (AN)
  • AMF access and mobility management function
  • UDM unified data management
  • AUSF authentication server function
  • PCF policy control function
  • the terminal communicates with the AMF entity through the N1 interface (N1 for short); the AMF entity communicates with the SMF entity through the N11 interface (N11 for short), and the SMF entity communicates with the first UPF achor and the second UPF achor through the N4 interface (N4 for short).
  • the first UPF achor communicates with the first DN through an N6 interface (N6 for short), and the second UPF achor communicates with the second DN through an N6 interface (N6 for short).
  • the terminal accesses the network through the access device, and the access device communicates with the AMF entity through the N2 interface (N2).
  • the access device communicates with the UL CL through the N3 interface (N3), and the UL CL passes through the N9 interface.
  • N9 it communicates with the first UPF achor and the second UPF achor.
  • the SMF entity communicates with the PCF entity through an N7 interface (N7 for short), and the PCF entity communicates with the AF through the N5 interface.
  • the PCF is used to forward the signaling or data of the AF to the SMF entity.
  • the name of the interface between the network elements in FIG. 3 is only an example. In the specific implementation, the interface name may be other names, which is not specifically limited in this embodiment of the present application.
  • the access device, the AMF entity, the SMF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity of FIG. 3 are only one name, and the name does not limit the device itself.
  • the network element or the entity corresponding to the access device, the AMF entity, the SMF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity may also be other names.
  • the UDM entity may be replaced by a home subscriber server (HSS) or a user subscription database (USD) or a database entity, etc., and is hereby described in a unified manner, and details are not described herein.
  • the first session refers to a communication link between the connected terminal established by the SMF entity and the data network, and the communication link includes a terminal, an access device, a UPF achor, and a data network corresponding to the UPF achor.
  • the first session may be a protocol data unit session (PDU session). This PDU session is used to provide PDU packets.
  • the first service or service in the present application refers to at least one service flow included in the first session, and the service flow may be identified by a quintuple, and the service flow is a PDU data packet provided by the first session.
  • the terminal 107 in this application may also be referred to as a terminal device, a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a mobile device.
  • UE user equipment
  • an access terminal a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a mobile device.
  • user terminal, terminal, wireless communication device, user agent or user device may also be referred to as a terminal device, a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a mobile device.
  • user terminal terminal, terminal, wireless communication device, user agent or user device.
  • the terminal device may be a station (STA) in a wireless local area network (WLAN), and may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, or a wireless local loop (wireless local Loop, WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system, For example, a terminal device in a fifth-generation (5G) communication network or a terminal device in a public land mobile network (PLMN) network that is evolving in the future.
  • 5G fifth-generation
  • PLMN public land mobile network
  • the terminal may also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are more than just a hardware device, but they also implement powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-size, non-reliable smartphones for full or partial functions, such as smart watches or smart glasses, and focus on only one type of application, and need to work with other devices such as smartphones. Use, such as various smart bracelets for smart signs monitoring, smart jewelry, etc.
  • the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, and a non-third generation. 3rd generation partnership project (3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the AMF entity involved in the embodiment of the present application may also be responsible for the functions of the registration management, the mobility management, the lawful monitoring, and the like, which is not specifically limited in this embodiment.
  • the SMF entity involved in the embodiment of the present application is used for session management, including: session establishment, session modification, session release, and internet protocol (IP) address allocation between the terminals of the network.
  • IP internet protocol
  • the UPF entity involved in the embodiment of the present application has the functions of the user plane function entity shown in FIG. 3, and can also implement a serving gateway (SGW) and a packet data network gateway. , PGW) user plane function.
  • SGW serving gateway
  • PGW packet data network gateway
  • the UPF entity may also be a software-defined network (SDN) switch, which is not specifically limited in this embodiment of the present application.
  • SDN software-defined network
  • the AUSF entity involved in the embodiment of the present application is used to authenticate the terminal based on the subscription data of the terminal.
  • the UDM entity involved in the embodiment of the present application is used to store user subscription data.
  • the UDM entity further includes the functions of the authentication, the processing of the user identifier, the contract management, and the like, which are not specifically limited in this embodiment of the present application.
  • the PCF entity involved in the embodiment of the present application provides a policy rule, and supports a policy-related function such as a unified policy architecture management network behavior.
  • the user plane function entity in FIG. 3 may be implemented by one entity device, or may be implemented by multiple entity devices, or may be a logical function module in a physical device. limited.
  • the SMF entity is configured to re-allocate the UPF according to the location information of the terminal or the feature of the data sent by the terminal or the location between the UPF and the terminal, and re-establish the session between the terminal and the newly allocated UPF. To improve the re-established session to optimize the user face.
  • the access device is configured to provide data services for the terminal, for example, receiving data sent by the terminal, or sending data to the terminal, and the access device may be a base station during actual use.
  • a base station may be a device that communicates with a user equipment (UE) or other communication station, such as a relay station, and the base station may provide communication coverage of a specific physical area.
  • UE user equipment
  • a PCF entity used as an interface between a radio frequency part and a packet network (IP network).
  • IP network packet network
  • the AF entity is used to play the role of the application affecting the route.
  • the SMF after the SMF determines the second functional entity for the first session, the SMF sends the association relationship between the configuration information of the second functional entity and the first session to the access device, The third functional entity and the fifth functional entity, so that when the access device receives the service sent by the terminal through the first session, the service in the first session may be sent according to the association relationship between the configuration information and the first session.
  • the second functional entity so that the second functional entity can forward part of the service in the first session to the third functional entity according to the first mapping rule.
  • the second function entity further includes a second mapping rule, where the second function entity may forward the other service in the first session to the fifth function entity according to the second mapping rule, where the configuration information is used to identify the first
  • the second functional entity may be the access address of the second functional entity or the access identifier, which is not limited in this application.
  • the terminal can generally perform data interaction with the source data network through the first session. For example, requesting a service from a source data network. However, if the terminal moves to a range of another data network, and the data network can better serve a certain service of the terminal, or if the source data network cannot meet the requirements of a certain service of the terminal, and the terminal can When the service is obtained in another data network, the first functional entity may determine a second functional entity for the first session, and the second functional entity is configured to forward the service of the terminal (also referred to as offloading). The second functional entity can forward a certain service requested by the terminal to the destination data network to request the certain service from the destination data network. Since the destination IP is not required to be replaced for the terminal throughout the process, the established first session can be made uninterrupted.
  • a method for service offloading provided by the application includes:
  • the first functional entity determines the second functional entity for the first session, where the first session includes at least one first service.
  • the second functional entity is configured to offload at least one first service included in the first session.
  • the terminal device in this application may be the terminal 107 as shown in FIG. 3, the first functional entity may be an SMF entity, and the second functional entity may be an uplink classifier.
  • the first function entity in the present application may determine, according to the preset mapping rule information, whether the second function entity needs to be determined for the first session between the terminal device and the first DN, and the specific mapping rule information may be referred to. In the prior art, this application does not limit this.
  • the first functional entity of the present application may further determine that the second functional entity needs to be determined for the first session, triggered by the first request message sent by the fourth functional entity.
  • the method provided by the present application before S101 further includes:
  • the fourth functional entity acquires location information of the terminal device.
  • the fourth functional entity in this application may be an AF entity in the architecture as shown in FIG. 3.
  • the fourth functional entity determines that there is a second DN serving the first service of the terminal device according to the location information of the terminal device and the service information corresponding to the terminal device.
  • the second DN in the present application can include at least one DN, and the terminal device can request data included in the first service from the at least one DN.
  • the second DN in the present application serving the first service of the terminal device can be understood as the terminal device can obtain the data included in the first service from the second DN.
  • the fourth function entity sends a first request message, where the first request message is used to indicate that the first functional entity determines a second functional entity for the first session between the terminal device and the first data network DN, where the second functional entity is And configured to offload at least one first service included in the first session. Since the terminal device is in a moving state in the actual process, and the first functional entity does not know the specific location of the terminal device, the location information of the terminal device is acquired by the fourth functional entity, and the presence of the terminal device is determined to be present. When the service can provide the second DN of the better service, the first function message is sent to the first function entity, so that the first function entity can offload the at least one first service in the first session in time.
  • S101 in this application may be specifically implemented by: after triggering by the first request message, the first functional entity determines that the first session between the terminal device and the first data network DN needs to be determined. The second functional entity.
  • the first request message includes at least one of: information indicating that there is a second data network DN serving the first service, information of the second DN, information of the third functional entity, and the first server a mapping relationship between the address and the address of the second server, wherein the address of the first server is a source address of the first service requested by the terminal device, and the address of the second server is a target address of the first service requested by the terminal device,
  • the tri-function entity is associated with the second DN.
  • the third functional entity may be a first user plane functional entity in the architecture as shown in FIG. 3.
  • the first server is one of the at least one server corresponding to the first data network, wherein the first data network has a first session with the terminal device, and the second server is at least one server corresponding to the second data network.
  • a server, the second data network is a data network determined by the fourth functional entity according to the location information of the terminal device, and the second data network can better serve the data of the terminal device compared to the first data network.
  • the information of the second DN includes a data network name (DN name, DNN) and a data network access identifier (DNA access identifier, DNAI).
  • determining, by the first functional entity in the present application, that the second functional entity is the first session entity may be implemented by: determining, by the first functional entity, the second functional entity according to the preset rule information, for example, when a second functional entity is located.
  • the second functional entity is directly determined as the second functional entity of the first session, or the first functional entity receives the first policy sent by the PCF entity, where the first policy is used to indicate the second functional entity.
  • Information the first functional entity determines the second functional entity according to the first policy.
  • the second functional entity in the present application exists in the first session before the first functional entity determines that the second functional entity needs to be determined for the first session between the terminal device and the first data network DN.
  • the second functional entity has established a connection with the access device and the fifth functional entity corresponding to the first session, but the second functional entity may not have the first mapping rule information.
  • the second function entity When receiving the first service of the terminal device forwarded by the access device, the second function entity directly forwards the first service to the fifth function entity.
  • the fifth functional entity may be a second UPF achor in the architecture as shown in FIG. 3.
  • the first functional entity introduces the second functional entity into the first session, that is, the terminal When the first session between the device and the first data network DN needs to determine the second functional entity, the second functional entity does not exist in the first session.
  • the first functional entity When the first functional entity determines the second functional entity for the first session, the first functional entity needs to send the configuration information of the second functional entity to the access device, and the fifth functional entity and the third functional entity to establish the first a connection between the second functional entity and the access device, and the fifth functional entity, and the third functional entity, so that the access device may request the first service when receiving the request message of the terminal device for the first service Transmitting the message to the second functional entity, to forward, by the second functional entity, the first service to the third functional entity according to the first mapping rule, and then the third functional entity is configured according to the address of the first server and the address of the second server
  • the mapping relationship is: sending the address of the first service from the address of the first server to the address of the second server and sending the second DN corresponding to the third functional entity.
  • the first mapping rule information in this application may also be referred to as route forwarding rule information.
  • the first function entity sends, to the second function entity, the first mapping rule information, where the first mapping rule message is used to instruct the second function entity to send the first service to the third function entity, where the third function entity is used to implement The translation of the address of the first service from the address of the first server to the address of the second server.
  • the method provided by the application further includes: determining, by the first functional entity, the first mapping rule information according to a mapping relationship between an address of the first server and an address of the second server.
  • the first mapping rule information in the application may be determined by the first functional entity according to the mapping relationship between the address of the first server and the address of the second server, and the first mapping rule information may also be The first function entity directly receives the first mapping rule information and the first function entity determines the first mapping rule information according to the mapping relationship between the address of the first server and the address of the second server. In comparison, the processing efficiency of the first functional entity can be improved.
  • the second functional entity receives the first mapping rule information sent by the first functional entity.
  • the second function entity After receiving the first service, the second function entity sends the first service to the third function entity according to the first mapping rule information.
  • the second function entity receives the data in the first service. After the data in the first service is sent to the fifth function entity, after the first function entity sends the first mapping rule information to the second function entity, the second function entity receives the data in the first service, and then The first service is forwarded to the third functional entity.
  • the first mapping rule information includes: information of the first service and information of a third function entity associated with the first service, where the second function entity receives the first service, according to the The first mapping rule information sends the first service to the third functional entity indicated by the information of the third functional entity.
  • the information of the first service may be the IP quintuple information of the first service, for example, the source IP address, the source port, the destination IP address, and the like.
  • the information of the first service included in the first mapping rule information may be the address of the second server of the first service.
  • the information of the third functional entity may be an identifier of the third functional entity (eg, address, access identifier, etc.), a tunnel address (tunnel ID), an access identifier of the data network, and the like.
  • the first functional entity in the application may further send, to the second functional entity, second mapping rule information, where the second mapping rule information is used to indicate that the second functional entity is to use the second service in the first session. Forwarding to a fifth functional entity, wherein the fifth functional entity has a first session with the terminal device.
  • the second mapping rule information may be information of a source server of the second service and information of an UPF achor corresponding to the source server.
  • the first functional entity in the application has a connection between the second functional entity and the third functional entity and the fifth functional entity, such that the second function
  • the entity may offload the service in the first session to the fifth functional entity or the third functional entity according to the first mapping rule information.
  • the first functional entity in the present application may also not send the second mapping rule information to the second functional entity, so that the second functional entity determines the first mapping rule information when determining that the second service sent by the terminal device is received.
  • the second service is forwarded to the fifth functional entity.
  • the present application provides a method for service offloading.
  • the first functional entity determines a second functional entity for the first session, and The second function entity sends first mapping rule information for instructing the second function entity to send the first service to the third function entity, so that after receiving the first service, the second function entity may
  • the first service is sent to the third functional entity, and the third functional entity implements a conversion between the address of the first service from the address of the first server to the address of the second server, so that not only can the first service be provided in the presence of the first service
  • the first service is offloaded, and the terminal device does not need to change the destination IP of the first service in the process of offloading the first service in the application, so that when the first service is offloaded, A PDU session is not interrupted.
  • the method provided by the application further includes:
  • the first functional entity sends a mapping relationship between the address of the first server and the address of the second server to the third functional entity, where the mapping function is used by the third functional entity to address the address of the first service from the address of the first server. Mapping to the address of the second server, or for the third functional entity to map the address of the first service from the address of the second server to the address of the first server.
  • the first functional entity sends a mapping relationship between the address of the first server and the address of the second server to the third functional entity, and the first functional entity sends the first mapping to the second functional entity.
  • the process of rules can be performed simultaneously, that is, the execution of the two processes is not in order.
  • the first functional entity may send a network address translation (NAT) rule to the third functional entity, where the NAT rule includes a mapping relationship between the address of the first server and the address of the second server.
  • NAT network address translation
  • the third functional entity receives a mapping relationship between an address of the first server and an address of the second server.
  • the third function entity converts the address of the first service from the address of the first server to the address of the second server, and sends the first service after the translated address.
  • a second data network corresponding to the second server the first service is obtained from the second data network corresponding to the second server, and the third function entity receives the first service sent by the second data network corresponding to the second server, The address of the first service is mapped from the address of the second server to the address of the first server, and sent to the second functional entity.
  • the address of the first server where the data 1 in the first service is located is IP1, and after receiving the data 1, the third functional entity converts the address of the data 1 from IP1 to IP2, and converts the address from IP1 to Data 1 of IP2 is sent to the second data network to obtain data 1 from the second data network; after the third functional entity acquires data 1 from the second data network according to IP2, the third functional entity addresses the data 1 After converting from IP2 to IP1, data 1 that converts the address from IP2 to IP1 is sent to the second functional entity.
  • the method provided by the present application further includes: before S105:
  • the fourth functional entity sends a second request message for indicating location information of the reporting terminal device to the terminal device.
  • the second request message may be a newly defined signaling message between the terminal device and the fourth functional entity, where the newly defined signaling message is used to indicate the information of the location information of the terminal device, and the second request message may also pass.
  • a signaling message that has been received between the terminal device and the fourth functional entity, and has a field in the signaling message that indicates location information of the terminal device which is not limited in this application.
  • the fourth functional entity in the present application can also obtain the location information of the terminal device from other places, which is not limited in this application.
  • the fourth functional entity has information of at least one DN, and an association relationship between the service and the at least one DN, so that the fourth functional entity can be based on the location information of the terminal device and the service information of the terminal device from the at least one
  • the first DN is determined in the DN for the first service of the terminal device.
  • the terminal device receives the second request message.
  • the terminal device sends the location information of the terminal device to the fourth functional entity.
  • the location information of the terminal device may be information such as the longitude and latitude of the terminal device, which is not limited in this application.
  • the method provided by the present application further includes:
  • the fourth function entity sends first indication information to the terminal device, where the first indication information device is used to indicate a mapping relationship between an address of the first server and an address of the second server.
  • the terminal device receives the first indication information.
  • the terminal device maps, according to the first indication information, an address of the first service from an address of the first server to an address of the second server, and requests the first service according to the address of the second server.
  • the terminal device changes the IP quintuple information of the first service from the address of the first server to the address of the second server, and then the terminal device requests the first service according to the address of the second server.
  • the first mapping rule information sent by the first function entity to the second function entity may be the relationship between the information of the first service update (ie, the address of the second server) and the third functional entity.
  • the second functional entity can forward the first service to the third functional entity after receiving the information of the first service update.
  • the method further includes: the fourth function entity sends a mapping relationship between the address of the first server and the address of the second server to the terminal device, where the mapping relationship is used by the terminal device to use the first service
  • the address is mapped from the address of the first server to the address of the second server, the address of the first server is the source address of the first service requested by the terminal device, and the address of the second server is the target address of the first service requested by the terminal device.
  • the target address is an address that the terminal device actually requests the first service
  • the source address is an address that the terminal device originally requests the first service
  • the first mapping rule information that is sent includes: an association between an address of the first server of the first service and a fifth functional entity, and an association between an address of the second server of the first service and the third functional entity.
  • the first functional entity is an SMF entity
  • the second functional entity is a UL CL
  • the third functional entity is a second UPF achor
  • the fourth functional entity is an AF entity.
  • the function entity is the first UPF achor
  • the SMF determines the UL CL as an example under the trigger of the AF through the PCF, and details the specific process of the service offloading method of the present application, including:
  • the UE reports the location information of the UE to the AF.
  • the location information of the UE may be information for determining the location of the UE, which is not limited in this application.
  • the AF determines, according to the location information of the UE, that there is a second DN serving as the first service of the UE.
  • the AF sends a first request message to the PCF.
  • the first request message may further include information about the UE, and application information, where the information of the UE is used for identification.
  • the application information is used by the PCF to generate corresponding rules for the application of the type.
  • the UE information provided by the AF may be used by the PCF to generate a corresponding rule for a certain UE or multiple UEs (groups).
  • the AF interacts with the PCF through a network exposure function (NEF).
  • NEF network exposure function
  • the PCF sends a second request message to the SMF.
  • the content of the second request message may be the same as the content of the first request message, and may be processed by the PCF to generate the second request message, which is not limited by the application.
  • the SMF determines the ULCF.
  • the SMF sends the first mapping rule information to the ULCL after determining the ULCF, and sends an association relationship between the address of the first server and the address of the second server to the second UPF achor.
  • the first mapping rule message is the information of the first service and the second UPF achor information associated with the first service.
  • the method further includes: the ULCL forwarding, according to the first mapping rule information, the received first service to the second UPF achor, and receiving the request by the second UPF achor according to the address request of the second server.
  • the first service that changes the address to the address of the first server is sent to the ULCL. To be sent to the UE by the ULCL through the access device.
  • FIG. 11 shows a specific process of another method for service offloading provided by the present application.
  • the difference between FIG. 11 and FIG. 10 is that S207 and S208 are added in FIG. 11, and S205 is omitted.
  • the SMF sends a process of association between the address of the first server and the address of the second server to the second UPF achor.
  • the first mapping rule information sent by the SMF to the ULCL in S205 is the IP quintuple 1 of the first service and the first UPF achor information associated with the first service, and the IP quintuple 2 of the first service and the first service.
  • the associated second UPF achor information so that the ULCL entity can forward the service of the IP quintuple 1 to the first UPF achor and receive the IP after receiving the IP quintuple as the service of the IP quintuple 1.
  • the IP quintuple 2 service can be forwarded to the second UPF achor.
  • the AF sends a mapping relationship between the address of the first server and the address of the second server to the UE, or sends the first indication information, where the first indication information is used to indicate that the UE sends the address of the data in the first service from the first
  • the address of a server is mapped to the address of the second server.
  • the UE maps an address of the first service from an address of the first server to an address of the second server, and requests the first service according to the address of the second server.
  • the present application provides a method for service offloading.
  • the first functional entity determines a second functional entity for the first session, and
  • the second function entity sends first mapping rule information for instructing the second function entity to send the first service to the third function entity, so that the second function entity can receive the first service rule according to the first mapping rule information.
  • the third function entity implements a conversion between the address of the first service from the address of the first server to the address of the second server, so that the first service can be provided not only in the presence In a better data network, the first service is offloaded, and the first PDU session is not interrupted when the first service is offloaded.
  • each network element for example, the first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the terminal device, in order to implement the foregoing functions, includes a hardware structure corresponding to performing each function and/or Or software module.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform functional module division on the first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the terminal device according to the foregoing method example.
  • each functional module may be divided according to each function.
  • Two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner. The following is an example of dividing each functional module by using corresponding functions:
  • FIG. 12 shows a possible structural diagram of the first functional entity involved in the above embodiment.
  • the first functional entity includes: a determining unit 101 and a transmitting unit 102.
  • the determining unit 101 is configured to support the first functional entity to execute S101 and S205 in the foregoing embodiment.
  • the sending unit 102 is configured to support the first functional entity to execute S102, S108, and S206 in the foregoing embodiment.
  • the first functional entity may further comprise a receiving unit 103 for supporting the first functional entity to perform S109 in the above-described embodiment. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the sending unit 102 in the present application may be a transmitter of the first functional entity
  • the receiving unit 103 may be a receiver of the first functional entity
  • the transmitter may be integrated with the receiver.
  • a transceiver a specific transceiver may also be referred to as a communication interface or a transceiver circuit or an interface circuit, and the determining unit 101 may be integrated on a processor of the first functional entity.
  • FIG. 13 shows a possible logical structure diagram of the first functional entity involved in the above embodiment.
  • the first functional entity includes a processing module 112 and a communication module 113.
  • the processing module 112 is configured to perform control management on the action of the first functional entity.
  • the processing module 112 is configured to perform a step of performing message or data processing on the first functional entity side, for example, supporting the first functional entity to execute in the foregoing embodiment.
  • S101 and S205 The communication module 113 is configured to support the first functional entity to execute S102, S108, S206, and S109 in the above embodiment. And/or other processes performed by the first functional entity for the techniques described herein.
  • the first functional entity may further include a storage module 111, configured to store program codes and data of the first functional entity.
  • the processing module 112 may be a processor or a controller, such as a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication module 113 may be a transceiver, a transceiver circuit or a communication interface or an interface circuit or the like.
  • the storage module 111 can be a memory.
  • the processing module 112 is the processor 120
  • the communication module 113 is the communication interface 130 or the transceiver
  • the storage module 111 is the memory 140
  • the first functional entity involved in the present application may be the device shown in FIG.
  • the communication interface 130, the at least one processor 120, and the memory 140 are mutually connected by a bus 110; the bus 110 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 14, but it does not mean that there is only one bus or one type of bus.
  • the memory 140 is configured to store program codes and data of the first functional entity.
  • the communication interface 130 is configured to support the first functional entity to communicate with other devices (eg, the second functional entity), and the processor 120 is configured to support the first functional entity to execute the program code and data stored in the memory 140 to implement one provided by the present application. A method of business diversion.
  • FIG. 15 shows a possible structural diagram of the fourth functional entity involved in the above embodiment.
  • the fourth functional entity includes: an obtaining unit 201, a determining unit 202, and a transmitting unit 203.
  • the obtaining unit 201 is configured to support the fourth functional entity to execute S105 in the foregoing embodiment.
  • the determining unit 202 is configured to support the fourth functional entity to execute S106 and S202 in the foregoing embodiment, wherein the sending unit 203 is configured to support the fourth functional entity to execute S107, S111, S114, S203, and S207 in the foregoing embodiment.
  • All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the obtaining unit 201 in the present application may be a receiver of the fourth functional entity
  • the sending unit 203 may be a fourth functional entity transmitter
  • the transmitter may generally be the receiver of the fourth functional entity.
  • a specific transceiver may also be referred to as a communication interface, or a transceiver circuit or an interface circuit, and further the determining unit 202 may be integrated on a processor of the fourth functional entity.
  • FIG. 16 shows a possible logical structure diagram of the fourth functional entity involved in the above embodiment.
  • the fourth functional entity includes: a processing module 212 and a communication module 213.
  • the processing module 212 is configured to perform control and management on the action of the fourth functional entity.
  • the processing module 212 is configured to support the fourth functional entity to perform the operation of performing message or data processing on the fourth functional entity side in the foregoing embodiment, for example, performing S106 and S202 in the foregoing embodiment
  • the communication module 213 is configured to support the fourth function entity to perform the operation of receiving the message or the data on the fourth functional entity side in the foregoing embodiment, for example, S105 and S107 in the foregoing embodiment. , S111, S114, S203, and S207. And/or other processes performed by the fourth functional entity for the techniques described herein.
  • the fourth functional entity may further include a storage module 211, configured to store program codes and data of the fourth functional entity.
  • the processing module 212 can be a processor or a controller, for example, a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication module 213 can be a transceiver, a transceiver circuit or a communication interface or an interface circuit or the like.
  • the storage module 211 can be a memory.
  • the fourth functional entity involved in the present application may be the device shown in FIG.
  • the communication interface 230, the at least one processor 220, and the memory 210 are connected to each other through a bus 200.
  • the bus 200 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 17, but it does not mean that there is only one bus or one type of bus.
  • the memory 210 is configured to store program codes and data of the fourth functional entity.
  • the communication interface 230 is configured to support the fourth functional entity to communicate with other devices (eg, terminal devices), and the processor 220 is configured to support the fourth functional entity to execute the program code and data stored in the memory 210 to implement a service provided by the present application. The method of shunting.
  • FIG. 18 shows a possible structural diagram of the terminal device involved in the above embodiment.
  • the terminal device includes a transmitting unit 301, a receiving unit 302, and a processing unit 303.
  • the receiving unit 302 is configured to support the terminal device to execute S112 and S115 in the foregoing embodiment;
  • the sending unit 301 is configured to support the terminal device to execute S113 and S201 in the foregoing embodiment, and the processing unit 303 is configured to support the terminal device to execute the foregoing embodiment.
  • S116 and S208 And/or other processes for the techniques described herein. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the receiving unit 302 in the present application may be a receiver of the terminal device, and the sending unit 301 may be a transmitter of the terminal device, and the receiver may be generally integrated with the transmitter of the terminal device.
  • the transceiver, the specific transceiver may also be referred to as a communication interface or a transceiver circuit or an interface circuit.
  • FIG. 19 shows a possible logical structure diagram of the terminal device involved in the above embodiment.
  • the terminal device includes a processing module 312 and a communication module 313.
  • the processing module 312 is configured to perform control and management on the action of the terminal device.
  • the processing module 312 is configured to support the terminal device to perform the operation of performing message or data processing on the terminal device side in the foregoing embodiment, for example, S116 in the foregoing embodiment, and S208;
  • the communication module 313 is configured to support the terminal device to perform an operation of receiving or transmitting a message or data on the terminal device side in the above embodiment, for example, S112, S115, S113, and S201 in the above embodiment. And/or other processes performed by the terminal device for the techniques described herein.
  • the terminal device may further include a storage module 311, configured to store program codes and data of the terminal device.
  • the processing module 312 can be a processor or a controller, such as a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication module 313 can be a transceiver, a transceiver circuit or a communication interface or an interface circuit or the like.
  • the storage module 311 can be a memory.
  • the terminal device involved in the present application may be the device shown in FIG.
  • the communication interface 330, the at least one processor 320, and the memory 310 are connected to each other through a bus 300.
  • the bus 300 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 20, but it does not mean that there is only one bus or one type of bus.
  • the memory 310 is used to store program codes and data of the terminal device.
  • the communication interface 330 is configured to support the terminal device to communicate with other devices (for example, a fourth functional entity), and the processor 320 is configured to support the terminal device to execute the program code and data stored in the memory 310 to implement a service distribution provided by the present application. method.
  • FIG. 21 shows a possible structural diagram of the second functional entity involved in the above embodiment.
  • the second functional entity includes a receiving unit 401 and a transmitting unit 402.
  • the receiving unit 401 is configured to support the second functional entity to execute S103 in the foregoing embodiment.
  • the sending unit 402 is configured to support the second functional entity to execute S104 in the above embodiment. And/or other processes for the techniques described herein. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the receiving unit 401 in the present application may be a receiver of the second functional entity
  • the sending unit 402 may be a transmitter of the second functional entity, and the receiver may be generally sent with the second functional entity.
  • the devices are integrated for use as a transceiver, and the specific transceiver may also be referred to as a communication interface or a transceiver circuit or an interface circuit.
  • FIG. 22 shows a possible logical structure diagram of the second functional entity involved in the above embodiment.
  • the second functional entity includes a processing module 412 and a communication module 413.
  • the processing module 412 is configured to control and control the action of the second functional entity.
  • the processing module 412 is configured to support the second functional entity to perform the operation of performing message or data processing on the second functional entity side in the foregoing embodiment;
  • the module 413 is configured to support the second function entity to perform an operation of receiving or transmitting a message or data on the second functional entity side in the above embodiment, for example, S103 and S104 in the above embodiment. And/or other processes performed by the second functional entity for the techniques described herein.
  • the second functional entity may further include a storage module 411, configured to store program codes and data of the second functional entity.
  • the processing module 412 can be a processor or a controller, such as a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication module 413 can be a transceiver, a transceiver circuit or a communication interface or an interface circuit or the like.
  • the storage module 411 can be a memory.
  • the processing module 412 is the processor 420
  • the communication module 413 is the communication interface 430 or the transceiver
  • the storage module 411 is the memory 410
  • the second functional entity involved in the present application may be the device shown in FIG.
  • the communication interface 430, the at least one processor 420, and the memory 410 are connected to each other through a bus 400.
  • the bus 400 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 23, but it does not mean that there is only one bus or one type of bus.
  • the memory 410 is configured to store program codes and data of the second functional entity.
  • the communication interface 430 is configured to support the second functional entity to communicate with other devices (eg, the first functional entity and the third functional entity), and the processor 420 is configured to support the second functional entity to execute the program code and data stored in the memory 410 to implement The method for service offloading provided by the application.
  • FIG. 24 shows a possible structural diagram of the third functional entity involved in the above embodiment.
  • the third functional entity includes: a receiving unit 501 and a processing unit 502.
  • the receiving unit 501 is configured to support the third functional entity to execute S109 in the foregoing embodiment.
  • the processing unit 502 is configured to support the third functional entity to execute S110 in the foregoing embodiment. And/or other processes for the techniques described herein. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the receiving unit 501 in the present application may be a receiver of a third functional entity, and the receiver may be integrated with a transmitter of the third functional entity as a transceiver, and the specific transceiver. It can also be called a communication interface or a transceiver circuit or an interface circuit.
  • FIG. 25 shows a possible logical structure diagram of the third functional entity involved in the above embodiment.
  • the third functional entity includes a processing module 512 and a communication module 513.
  • the processing module 512 is configured to control and control the action of the third functional entity.
  • the processing module 512 is configured to support the third functional entity to perform the operation of performing message or data processing on the third functional entity side in the foregoing embodiment;
  • the module 513 is configured to support the third function entity to perform the operation of receiving or transmitting a message or data on the third functional entity side in the foregoing embodiment, for example, S109 and S110 in the above embodiment. And/or other processes performed by the third functional entity for the techniques described herein.
  • the third functional entity may further include a storage module 511, configured to store program code and data of the third functional entity.
  • the processing module 512 can be a processor or a controller, for example, a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication module 513 can be a transceiver, a transceiver circuit, an interface circuit, or a communication interface.
  • the storage module 511 can be a memory.
  • the processing module 512 is the processor 520
  • the communication module 513 is the communication interface 530 or the transceiver
  • the storage module 511 is the memory 510
  • the third functional entity involved in the present application may be the device shown in FIG.
  • the communication interface 530, the at least one processor 520, and the memory 510 are connected to each other through a bus 500.
  • the bus 500 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 26, but it does not mean that there is only one bus or one type of bus.
  • the memory 510 is configured to store program codes and data of the third functional entity.
  • the communication interface 530 is configured to support the third functional entity to communicate with other devices (eg, the first functional entity), and the processor 520 is configured to support the third functional entity to execute the program code and data stored in the memory 510 to implement one provided by the present application. A method of business diversion.
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit for the chip to receive signals from other chips or devices.
  • the above transmitting unit is an interface circuit of the device for transmitting signals to other devices.
  • the transmitting unit is an interface circuit for transmitting signals to other chips or devices.
  • FIG. 27 is a schematic structural diagram of a chip system 150 according to an embodiment of the present invention.
  • the chip system 150 includes at least one processor 1510 and interface circuitry 1530.
  • the chip system 150 further includes a memory 1540, which may include a read only memory and a random access memory, and provides operating instructions and data to the processor 1510.
  • a portion of the memory 1540 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
  • the corresponding operation is performed by calling an operation instruction stored in the memory 1540 (which can be stored in the operating system).
  • first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the chip system used by the terminal device have similar structures, and different devices can use different chip systems to implement the respective The function.
  • the processor 1510 controls the operations of the first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the terminal.
  • the processor 1510 may also be referred to as a CPU (central processing unit).
  • Memory 1540 can include read only memory and random access memory and provides instructions and data to processor 1510.
  • a portion of memory 1540 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540, the interface circuit 1530, and the memory 1540 are coupled together by a bus system 1520.
  • the bus system 1520 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 1520 in FIG.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1510 or implemented by the processor 1510.
  • the processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1510 or an instruction in a form of software.
  • the processor 1510 may be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or Other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540 and performs the steps of the above method in combination with its hardware.
  • the interface circuit 1530 is configured to execute the first functional entity, the second functional entity, and the third functional entity in the embodiment shown in FIG. 4, FIG. 5, FIG. 7, FIG. 8, FIG. 10, FIG. The steps of the four functional entities and the receiving and transmitting of the terminal device.
  • the processor 1510 is configured to execute the first functional entity, the second functional entity, the third functional entity, and the fourth functional entity in the embodiments shown in FIG. 4, FIG. 5, FIG. 7, FIG. 8, FIG. 10, FIG. The step of processing the terminal device.
  • the instructions stored by the memory for execution by the processor may be implemented in the form of a computer program product.
  • the computer program product may be written in the memory in advance, or may be downloaded in software and installed in the memory.
  • a computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, computer instructions can be wired from a website site, computer, server or data center (eg, Coax, fiber, digital subscriber line (DSL) or wireless (eg, infrared, wireless, microwave, etc.) is transmitted to another website, computer, server, or data center.
  • a website site eg, computer, server or data center
  • DSL digital subscriber line
  • wireless eg, infrared, wireless, microwave, etc.
  • the computer readable storage medium can be any available media that can be stored by the computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • Useful media can be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk, SSD), and the like.
  • a computer storage medium having stored therein instructions that, when executed, cause a first functional entity to perform S101, S205, S102, S108, S206, and S109 in an embodiment. And/or other processes performed by the first functional entity for the techniques described herein.
  • a computer storage medium wherein instructions are stored in a computer readable storage medium, and when the instructions are executed, causing the fourth functional entity to execute S106 and S202, S105, S107, S111, S114, S203 in the embodiment And S207. And/or other processes performed by the fourth functional entity for the techniques described herein.
  • a computer storage medium in which instructions are stored, and when the instructions are executed, cause the terminal device to execute S116 and S208, S112, S115, S113, and S201 in the embodiment. And/or other processes performed by the terminal for the techniques described herein.
  • a computer storage medium is provided, the instructions being stored in the computer readable storage medium, when the instructions are executed, causing the second functional entity to execute S103 and S104 in the embodiment. And/or other processes performed by the second functional entity for the techniques described herein.
  • a computer storage medium having stored therein instructions that, when executed, cause a third functional entity to perform S109 and S110 in an embodiment. And/or other processes performed by the third functional entity for the techniques described herein.
  • a computer program product includes instructions that store instructions in a computer program product that, when executed, cause a first functional entity to execute S101, S205, S102, S108, S206, and S109 in an embodiment. And/or other processes performed by the first functional entity for the techniques described herein.
  • a computer program product in another aspect, storing instructions, when the instructions are executed, causing the fourth functional entity to execute S106 and S202, S105, S107, S111, S114 in the embodiment, S203 and S207. And/or other processes performed by the fourth functional entity for the techniques described herein.
  • a computer program product includes instructions that, when executed, cause a terminal to execute S116 and S208, S112, S115, S113, and S201 in an embodiment when the instructions are executed. And/or other processes performed by the terminal device for the techniques described herein.
  • a computer program product includes instructions that store instructions in a computer program product that, when executed, cause a second functional entity to perform S103 and S104 in an embodiment. And/or other processes performed by the second functional entity for the techniques described herein.
  • a computer program product includes instructions that store instructions in a computer program product that, when executed, cause a third functional entity to perform S109 and S110 in an embodiment. And/or other processes performed by the third functional entity for the techniques described herein.
  • a chip system is provided, the chip system being applied to a first functional entity, the chip system comprising at least one processor and an interface circuit, the interface circuit and the at least one processor being interconnected by a line, the processor being configured to execute an instruction to execute S101, S205, S102, S108, S206, and S109 in the embodiment. And/or other processes performed by the first functional entity for the techniques described herein.
  • a chip system is provided, the chip system being applied to a fourth functional entity, the chip system comprising at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction to S106 and S202, S105, S107, S111, S114, S203, and S207 in the embodiment of the embodiment are executed. And/or other processes performed by the fourth functional entity for the techniques described herein.
  • a chip system is provided, the chip system being applied to a terminal, the chip system comprising at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to execute an instruction to execute the embodiment S116 and S208, S112, S115, S113, and S201. And/or other processes performed by the terminal device for the techniques described herein.
  • a chip system is provided, the chip system being applied to a second functional entity, the chip system comprising at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction to S103 and S104 in the embodiment are executed. And/or other processes performed by the second functional entity for the techniques described herein.
  • a chip system is provided, the chip system being applied to a third functional entity, the chip system comprising at least one processor and an interface circuit, the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to run the instruction to S109 and S110 in the embodiment are executed. And/or other processes performed by the third functional entity for the techniques described herein.
  • the present application further provides a system for service offloading, the system for splitting the service includes a first functional entity as shown in FIG. 12-14, and a fourth functional entity shown in FIG. 15-17, FIG. 18- The terminal device shown at 20, the second functional entity shown in Figs. 21-23, and the third functional entity shown in Figs. 24-26.
  • the present application provides a system for service offloading.
  • the first functional entity determines a second functional entity for the first session, and
  • the second function entity sends first mapping rule information for instructing the second function entity to send data in the first service to the third function entity, so that the second function entity can receive the data in the first service after receiving the data in the first service entity.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种业务分流的方法和装置，涉及通信技术领域，用以解决传统技术方案中存在的由于UE的移动性使得会话中断的问题。该方案包括：终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，第一功能实体为所述第一会话确定第二功能实体，第一会话包括至少一个第一业务；第一功能实体向所述第二功能实体发送第一映射规则信息，所述第一映射规则信息用于指示第二功能实体将第一业务发送至第三功能实体，所述第三功能实体用于实现所述第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。

Description

一种业务分流的方法和装置
本申请要求于2018年01月31日提交中国专利局、申请号为201810098667.8、申请名称为“一种业务分流的方法和装置”中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种业务分流的方法和装置。
背景技术
协议数据单元(protocol data unit，PDU)会话(session)是第五代(5th generation，5G)移动通信系统中定义的用户设备(user equipment，UE)和数据网络(data network，DN)之间的连接，用于提供PDU连接性服务。其中，5G核心网(core network，CN)支持的PDU连接服务，是指提供UE和由数据网络名称(data network name，DNN)确定的数据网络(data network，DN)之间PDU交换的服务。UE可以建立由不同的用户面功能(user plane function，UPF)实体提供服务(service)的PDU会话，来连接到相同的DN。
传统技术方案中，随着UE的移动，会话管理功能(session management function，SMF)实体可以为该UE的一个PDU会话插入一个“上行分类器(uplink classifier，ULCL)”，该ULCL用于在一个支持ULCL功能的UPF实体上通过SMF实体提供的过滤条件，使得UPF实体将一个PDU会话的多个业务分流给不同的UPF锚点(anchor)，每个UPF锚点对应一个DN，以通过目标DN(例如，与UE距离最近的DN)与UE进行业务传输。如图1所示，一个PDU会话的业务1会被含有ULCL功能的UPF从图1中所示的UPF anchor1分流至UPF anchor2。
但是，通常anchor的改变，会使得UE与该anchor对应的DN之间建立的PDU会话中断，而传统技术方案中并未解决业务分流场景中引起的PDU会话中断的问题。
发明内容
本发明实施例提供一种业务分流的方法和装置，用于解决业务分流场景中引起的PDU会话中断的问题。
为了解决上述技术问题，本申请实施例提供如下技术方案：
第一方面，本申请提供一种业务分流的方法，包括：终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，第二功能实体用于对第一会话包括的至少一个第一业务分流；第一功能实体向第二功能实体发送第一映射规则信息，第一映射规则信息用于指示第二功能实体将第一业务发送至第三功能实体，第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
本申请提供一种业务分流的方法，终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，并向第二功能实体发送用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，这样第二功能实体在接收到第一业务之后，便可以根据第一映射规则信息将第 一业务中的数据发送至第三功能实体，由第三功能实体实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，这样不仅可以在存在可以为第一业务提供更好的数据网络时，将第一业务中的数据分流，且由于本申请中在对第一业务分流的过程中终端装置无需改变第一业务的目的IP，因此可以避免在对第一业务进行分流时，第一PDU会话不中断。
结合第一方面，在第一方面的第一种可能的实现方式中，本申请提供的方法还包括：第一功能实体接收用于指示第一功能实体为终端和第一数据网络DN之间的第一会话确定第二功能实体的第一请求消息。可选的，第一功能实体确定需要为终端和第一数据网络DN之间的第一会话确定第二功能实体，包括：在第一请求消息的触发下，第一功能实体确定需要为终端装置和第一数据网络DN之间的第一会话确定第二功能实体，通过接收第一请求消息，这样第一功能实体便可以确定需要为终端和第一数据网络DN之间的第一会话确定第二功能实体。当然，第一功能实体还可以根据其他触发条件为第一会话确定第二功能实体。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，第一请求消息包括以下任一项：用于表明存在为第一业务服务的第二数据网络DN的信息、第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址，第二DN与第三功能实体对应，这样便于第一功能实体确定需要为第一会话确定第二功能实体。
结合第一方面至第一方面的第二种可能的实现方式中任一项，在第一方面的第三种可能的实现方式中，本申请提供的方法还包括：第一功能实体根据第一服务器的地址和第二服务器的地址之间的映射关系，确定第一映射规则信息，通过根据第一服务器的地址和第二服务器的地址之间的映射关系，确定第一映射规则信息，可以便于第二功能实体实现第一业务中数据的转发，即将第一业务准确地发送到第三功能实体。可以理解的是，其中，第一服务器为第一业务所在的源地址，第二服务器为第三功能实体对应的目的数据网络中的一个为第一业务提供服务的服务器。
结合第一方面至第一方面的第三种可能的实现方式中，在第一方面的第四种可能的实现方式中，第一映射规则信息包括：第一业务的信息和与第一业务关联的第三功能实体的信息。通过将第一业务的信息和第三功能实体的信息之间的关联关系配置给第二功能实体，这样第二功能实体在接收到第一业务的时候，便可以根据第一映射规则信息，准确地将第一业务转发至与第一业务的信息关联的第三功能实体的信息所指示的第三功能实体。
结合第一方面至第一方面的第四种可能的实现方式中，在第一方面的第五种可能的实现方式中，本申请提供的方法还包括：第一功能实体向第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者用于第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。通过将映射关系发送给第三功能实体，这样便于第三功能实体在接收到终端装置对第一业务的请求时，可以准确的将第一服务器的地址映射为第二服务器的地址，并从第二服务器对应的数 据网络处获取第一业务，以及在获取到第一业务后，为了使得终端装置可以准确地识别该第一业务，将请求到的第一业务的地址从第二服务器的地址映射为第一服务器的地址。
第二方面，本申请提供一种业务分流方法，包括：第四功能实体获取终端装置的位置信息；第四功能实体根据终端装置的位置信息，确定存在为终端装置的第一业务服务的第二数据网络DN的情况下，第四功能实体发送用于指示为终端装置和第一数据网络DN之间的第一会话确定第二功能实体的第一请求消息，第二功能实体用于对第一会话关联的至少一个第一业务分流。
结合第二方面，在第二方面的第一种可能的实现方式中，第一请求消息包括以下任一项：用于表明存在为第一业务服务的第二数据网络DN的信息、第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址，第二DN与第三功能实体关联。
结合第二方面或第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，本申请提供的方法还包括：第四功能实体向终端装置发送用于指示上报终端装置的位置信息的第二请求消息。
结合第二方面至第二方面的第二种可能的实现方式中任一项，在第二方面的第三种可能的实现方式中，本申请提供的方法还包括：第四功能实体向终端装置发送用于指示终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址的第一指示信息。
结合第二方面至第二方面的第三种可能的实现方式中任一项，在第二方面的第四种可能的实现方式中，本申请提供的方法还包括：第四功能实体向终端装置发送第一服务器的地址和第二服务器的地址之间的映射关系，映射关系用于终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址。
第三方面，本申请提供一种业务分流的方法，包括：终端装置向第四功能实体发送终端装置的位置信息；终端装置接收第四功能实体发送的用于表明第一服务器的地址和第二服务器的地址之间的映射关系，其中，第一服务器的地址为终端装置请求第一业务中的数据的源地址，第二服务器的地址为终端装置请求第一业务的目标地址；终端装置根据第一指示信息，将第一业务的地址从第一服务器的地址映射为所述第二服务器的地址。
结合第三方面，在第三方面的第一种可能的实现方式中，终端装置向第四功能实体发送终端装置的位置信息之前，本申请提供的方法还包括：终端装置接收第四功能实体发送的用于指示终端装置上报终端装置的位置信息的第二请求消息。
结合第三方面或第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，本申请提供的方法还包括：终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址之后，根据第二服务器的地址请求第一业务。
结合第三方面至第三方面的第二种可能的实现方式中任一项，在第三方面的第三种可能的实现方式中，第一指示信息，包括：第一服务器的地址和第二服务器的地址 之间的映射关系，映射关系用于终端装置将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
第四方面，本申请提供一种业务分流的方法，包括：第二功能实体接收第一功能实体发送的用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换；第二功能实体在接收到第一业务后，将该第一业务发送至第三功能实体。
结合第四方面，在第四方面的第一种可能的实现方式中，该第一映射规则信息包括：第一业务的信息和与第一业务关联的第三功能实体的信息。
第五方面，本申请提供一种业务分流的方法，包括：第三功能实体接收第一功能实体发送的第一指示信息，该第一指示信息用于指示第三功能实体实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换；第三功能实体在接收到第一业务之后，实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，其中，第一服务器为终端装置请求第一业务的源地址，第二服务器为终端装置请求第一业务的目标地址。
结合第五方面，在第五方面的第一种可能的实现方式中，第一指示信息为第一服务器的地址和第二服务的地址之间的映射关系，该映射关系用于第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者用于第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
结合第五方面或第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，第三功能实体在接收到第一业务之后，实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，包括：第三功能实体接收终端装置发送的第一业务，第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者，第三功能实体接收第二DN发送的第一业务，第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
相应的，第六方面，本申请提供一种业务分流的装置，该业务分流的装置可以实现第一方面至第一方面的第四种可能的实现方式中任一项所描述的业务分流的方法。例如，该业务分流的装置可以为第一功能实体，该第一功能实体可以为SMF，或者为设置在SMF中的芯片。其可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种设计为，此处以业务分流的装置为SMF为例，该第六方面，本申请提供一种业务分流的装置，包括：终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，确定单元，用于确定需要为终端和第一数据网络DN之间的第一会话确定第二功能实体的情况下，该第一功能实体为第一会话确定用于对第一会话包括的至少一个第一业务分流的第二功能实体；发送单元，用于向第二功能实体发送用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，该第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
结合第六方面，在第六方面的第一种可能的实现方式中，本申请提供的业务分流的装置，还包括：接收单元，用于接收用于指示第一功能实体为终端装置和第一数据网络DN之间的第一会话确定第二功能实体的第一请求消息。可选的，确定单元，具 体用于在第一请求消息的触发下确定终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体。
结合第六方面或第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，第一请求消息包括以下任一项：用于表明存在为第一业务服务的第二数据网络DN的信息、第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址，第二DN与第三功能实体关联。
结合第六方面至第六方面的第二种可能的实现方式，在第六方面的第三种可能的实现方式中，确定单元，还用于根据第一服务器的地址和第二服务器的地址之间的映射关系，确定第一映射规则信息。
结合第六方面至第六方面的第三种可能的实现方式中任一项，在第六方面的第四种可能的实现方式中，第一映射规则信息包括：第一业务的信息和与第一业务关联的第三功能实体的信息。
结合第六方面至第六方面的第四种可能的实现方式中任一项，在第六方面的第五种可能的实现方式中，发送单元，还用于向第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者用于第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
此外，本申请还提供一种业务分流的装置，该业务分流的装置包括：处理器和发射器，其中，处理器确定终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体的情况下，用于为第一会话确定对第一会话包括的至少一个第一业务分流的第二功能实体，发射器，用于向第二功能实体发送用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，该第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
可选的，该业务分流的装置还包括接收器，该接收器用于支持业务分流的装置实现上述第一方面至第一方面的任一项所描述的在业务分流的装置侧进行消息/数据接收的相关操作，发射器还用于支持业务分流的装置实现第一方面至第一方面的任一项所描述的在业务分流的装置侧进行消息/数据发送的相关操作，处理器还用于执行上述第一方面至第一方面任一项所描述的在业务分流的装置侧进行消息/数据处理的操作。可选的，本申请中的业务分流的装置还包括：总线和存储器，存储器用于存储代码和数据，处理器、接收器、发射器和存储器通过总线连接。
第七方面，一种可能的设计中，该业务分流的装置可以为SMF或者应用于SMF中的芯片，该业务分流的装置可以包括至少一个处理器。该至少一个处理器被配置为通过执行指令，以支持该业务分流的装置执行上述第一方面至第一方面的第五种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行的消息处理或控制的相关操作。可选的，该装置还可以包括存储器，用于与至少一个处理器耦合，其保存该装置必要的程序(指令)和数据。此外可选的，该业务分流的装置还可以包括通信接口，用于支持该业务分流的装置与其他网元(例如，第二功能实体和第三功能实体) 之间的通信。该通信接口可以是收发电路或者接口电路，其中，收发电路用于支持该业务分流的装置执行上述第一方面至第一方面的第五种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行消息接收和发送的相关操作。可选的，业务分流的装置还可以包括总线，其中，存储器、通信接口和至少一个处理器可以通过总线互联。
第八方面，本申请提供一种业务分流的装置，该业务分流的装置可以实现第二方面至第二方面的第四种可能的实现方式中任一项所描述的业务分流的方法。例如，该业务分流的装置可以为第三功能实体，例如，AF，或者为设置在AF中的芯片。其可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
此处以业务分流的装置为AF为例，第八方面，该业务分流的装置，包括：获取单元，用于获取终端装置的位置信息；确定单元，用于根据终端装置的位置信息，确定存在为终端装置的第一业务服务的第二数据网络DN；发送单元，用于在确定单元确定存在第二数据网络DN的情况下，发送用于指示为终端装置和第一数据网络DN之间的第一会话确定第二功能实体的第一请求消息，该第二功能实体用于对第一会话包括的至少一个第一业务分流。
结合第八方面，在第八方面的第一种可能的实现方式中，第一请求消息包括以下任一项：用于表明存在为第一业务服务的第二数据网络DN的信息、第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址，第二DN与第三功能实体关联。
结合第八方面或第八方面的第一种可能的实现方式，在第八方面的第二种可能的实现方式中，发送单元，还用于向终端装置发送用于指示上报终端装置的位置信息的第二请求消息。
结合第八方面至第八方面的第二种可能的实现方式中任一项，在第八方面的第三种可能的实现方式中，发送单元，还用于向终端装置发送用于指示终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址的第一指示信息。
结合第八方面至第八方面的第三种可能的实现方式中任一项，在第八方面的第四种可能的实现方式中，发送单元，还用于向终端装置发送第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址，第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址。
此外，本申请还提供一种业务分流的装置，该业务分流的装置包括：处理器和发射器，其中，处理器用于获取终端装置的位置信息，发射器，用于在确定单元确定存在第二数据网络DN的情况下，发送用于指示为终端装置和第一数据网络DN之间的第一会话确定第二功能实体的第一请求消息，该第二功能实体用于对第一会话关联的至少一个第一业务分流。
可选的，该业务分流的装置还包括接收器，该接收器用于支持业务分流的装置实现上述第二方面至第二方面的任一项所描述的在业务分流的装置侧进行消息/数据接收的相关操作，发射器还用于支持业务分流的装置实现第二方面至第二方面的任一项 所描述的在业务分流的装置侧进行消息/数据发射的相关操作，处理器还用于执行上述第二方面至第二方面任一项所描述的在业务分流的装置侧进行消息/数据处理的操作。可选的，本申请中的业务分流的装置还包括：总线和存储器，存储器用于存储代码和数据，处理器、接收器、发射器和存储器通过总线连接。
第九方面，一种可能的设计中，该业务分流的装置可以为AF或者应用于AF中的芯片，该业务分流的装置可以包括至少一个处理器。该至少一个处理器被配置为通过执行指令，以支持该业务分流的装置执行上述第二方面至第二方面的第四种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行的消息处理或控制的相关操作。可选的，该装置还可以包括存储器，用于与至少一个处理器耦合，其保存该装置必要的程序(指令)和数据。此外可选的，该业务分流的装置还可以包括通信接口，用于支持该业务分流的装置与其他网元(例如，终端装置)之间的通信。该通信接口可以是收发电路或者接口电路，其中，收发电路用于支持该业务分流的装置执行上述第二方面至第二方面的第四种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行消息接收和发送的相关操作。可选的，业务分流的装置还可以包括总线，其中，存储器、通信接口和至少一个处理器可以通过总线互联。
第十方面，本申请提供一种业务分流的装置，该业务分流的装置可以实现第三方面至第三方面的第二种可能的实现方式中任一项所描述的业务分流的方法。例如，该业务分流的装置可以为终端装置或者为设置在终端装置中的芯片。其可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
此处以业务分流的装置为终端为例，第十方面，该业务分流的装置，包括：发送单元，用于向第四功能实体发送终端装置的位置信息；接收单元，用于接收所述第四功能实体发送的第一指示信息，所述第一指示信息用于表明第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址；处理单元，用于根据所述第一指示信息，将所述第一业务中数据的地址从所述第一服务器的地址映射为所述第二服务器的地址。
结合第十方面，在第十方面的第一种可能的实现方式中，接收单元，还用于接收第四功能实体发送的用于指示终端装置上报终端装置的位置信息的第二请求消息。
结合第十方面或第十方面的第一种可能的实现方式，在第十方面的第二种可能的实现方式中，本申请提供的处理单元，还用于根据第二服务器的地址请求第一业务。
结合第十方面至第十方面的第二种可能的实现方式中任一项，在第十方面的第三种可能的实现方式中，第一指示信息包括：第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于终端装置将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
此外，本申请还提供一种业务分流的装置，该业务分流的装置包括：发射器和接收器，其中，发射器用于向第四功能实体发送终端装置的位置信息，接收器，用于接收第四功能实体发送的用于表明第一服务器的地址和第二服务器的地址之间的映射关系的第一指示信息，其中，该第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址，处理器，还用于根据第一指 示信息，将第一业务中数据的地址从第一服务器的地址映射为所述第二服务器的地址。
可选的，该业务分流的装置中的处理器还用于执行上述第三方面至第三方面任一项所描述的在业务分流的装置侧进行消息/数据处理的操作。可选的，发射器还用于支持业务分流的装置实现上述第三方面至第三方面的任一项所描述的在业务分流的装置侧进行消息/数据发送的相关操作，接收器还用于支持业务分流的装置实现第三方面至第三方面的任一项所描述的在业务分流的装置侧进行消息/数据接收的相关操作。可选的，本申请中的业务分流的装置还包括：总线和存储器，存储器用于存储代码和数据，处理器、接收器、发射器和存储器通过总线连接。
第十一方面，一种可能的设计中，该业务分流的装置可以为终端或者应用于终端中的芯片，该业务分流的装置可以包括至少一个处理器。该至少一个处理器被配置为通过执行指令，以支持该业务分流的装置执行上述第三方面至第三方面的第三种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行的消息处理或控制的相关操作。可选的，该装置还可以包括存储器，用于与至少一个处理器耦合，其保存该装置必要的程序(指令)和数据。此外可选的，该业务分流的装置还可以包括通信接口，用于支持该业务分流的装置与其他网元(例如，第四功能实体)之间的通信。该通信接口可以是收发电路或者接口电路，其中，收发电路用于支持该业务分流的装置执行上述第三方面至第三方面的第三种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行消息接收和发送的相关操作。可选的，业务分流的装置还可以包括总线，其中，存储器、通信接口和至少一个处理器可以通过总线互联。
第十二方面，本申请提供一种业务分流的装置，该业务分流的装置可以实现第四方面至第四方面的第一种可能的实现方式中任一项所描述的业务分流的方法。例如，该业务分流的装置可以为第二功能实体，例如，上行分类器，或者为设置在上行分类器中的芯片。其可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
此处以业务分流的装置为第二功能实体为例，第十二方面，该业务分流的装置，包括：接收单元，用于接收第一功能实体发送的用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换；第二功能实体在接收到第一业务后，将该第一业务发送至第三功能实体。
结合第十二方面，在第十二方面的第一种可能的实现方式中，该第一映射规则信息包括：第一业务的信息和与第一业务关联的第三功能实体的信息。
此外，本申请还提供一种业务分流的装置，该业务分流的装置包括：发射器和接收器，其中，接收器用于接收第一功能实体发送的用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，发射器，用于在接收到第一业务后，将该第一业务发送至第三功能实体。
可选的，该业务分流的装置还包括处理器用于执行上述第四方面至第四方面任一项所描述的在业务分流的装置侧进行消息/数据处理的操作。可选的，发射器还用于支持业务分流的装置实现上述第四方面至第四方面的任一项所描述的在业务分流的装置侧进行消息/数据发送的相关操作，接收器还用于支持业务分流的装置实现第四方面至 第四方面的任一项所描述的在业务分流的装置侧进行消息/数据接收的相关操作。可选的，本申请中的业务分流的装置还包括：总线和存储器，存储器用于存储代码和数据，处理器、接收器、发射器和存储器通过总线连接。
第十三方面，一种可能的设计中，该业务分流的装置可以为第二功能实体或者应用于第二功能实体中的芯片，该业务分流的装置可以包括至少一个处理器。该至少一个处理器被配置为通过执行指令，以支持该业务分流的装置执行上述第四方面至第四方面的第一种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行的消息处理或控制的相关操作。可选的，该装置还可以包括存储器，用于与至少一个处理器耦合，其保存该装置必要的程序(指令)和数据。此外可选的，该业务分流的装置还可以包括通信接口，用于支持该业务分流的装置与其他网元(例如，第一功能实体)之间的通信。该通信接口可以是收发电路或者接口电路，其中，收发电路用于支持该业务分流的装置执行上述第四方面至第四方面的第一种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行消息接收和发送的相关操作。可选的，业务分流的装置还可以包括总线，其中，存储器、通信接口和至少一个处理器可以通过总线互联。
第十四方面，本申请提供一种业务分流的装置，该业务分流的装置可以实现第五方面至第五方面的第二种可能的实现方式中任一项所描述的业务分流的方法。例如，该业务分流的装置可以为第三功能实体，例如，UPF achor，或者为设置在UPF achor中的芯片。其可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
此处以第三功能实体为UPF achor为例，包括：接收单元，用于接收第一功能实体发送的用于指示第三功能实体实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换的第一指示信息；处理单元，用于在接收到第一业务之后，实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
结合第十四方面，在第十四方面的第一种可能的实现方式中，第一指示信息为第一服务器的地址和第二服务的地址之间的映射关系，该映射关系用于第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者用于第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
结合第十四方面或第十四方面的第一种可能的实现方式，在第十四方面的第二种可能的实现方式中，处理单元，具体用于接收终端装置发送的第一业务，第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者，处理单元，具体用于接收第二DN发送的第一业务，第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
第十五方面，一种可能的设计中，该业务分流的装置可以为第三功能实体或者应用于第三功能实体中的芯片，该业务分流的装置可以包括至少一个处理器。该至少一个处理器被配置为通过执行指令，以支持该业务分流的装置执行上述第五方面至第五方面的第一种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行的消息处理或控制的相关操作。可选的，该装置还可以包括存储器，用于与至少一个处理器耦合，其保存该装置必要的程序(指令)和数据。此外可选的，该业务分流的装置还可以包括通信接口，用于支持该业务分流的装置与其他网元(例如，第一功能实 体)之间的通信。该通信接口可以是收发电路或者接口电路，其中，收发电路用于支持该业务分流的装置执行上述第五方面至第五方面的第一种可能的实现方式中任一项所描述的方法中在该业务分流的装置侧进行消息接收和发送的相关操作。可选的，业务分流的装置还可以包括总线，其中，存储器、通信接口和至少一个处理器可以通过总线互联。
第十六方面，本申请提供一种计算机可读存储介质，当计算机可读存储介质应用于业务分流的装置中，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第一方面至第一方面的任一项所描述的业务分流的方法。
第十七方面，本申请提供一种计算机可读存储介质，当计算机可读存储介质应用于业务分流的装置中，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第二方面至第二方面的任一项所描述的业务分流的方法。
第十八方面，本申请提供一种计算机可读存储介质，当计算机可读存储介质应用于业务分流的装置中，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第三方面至第三方面的任一项所描述的业务分流的方法。
第十九方面，本申请提供一种计算机可读存储介质，当计算机可读存储介质应用于业务分流的装置中，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第四方面至第四方面的任一项所描述的业务分流的方法。
第二十方面，本申请提供一种计算机可读存储介质，当计算机可读存储介质应用于业务分流的装置中，计算机可读存储介质中存储有指令，当指令在计算机上运行时，使得计算机执行上述第五方面至第五方面的任一项所描述的业务分流的方法。
第二十一方面，本申请提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当该指令被运行时，使得第一功能实体执行上述第一方面至第一方面的第四种可能的实现方式中任一项所描述的业务分流的方法。
第二十二方面，本申请提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当该指令被运行时，使得第四功能实体执行上述第二方面至第二方面的第四种可能的实现方式中任一项所描述的业务分流的方法。
第二十三方面，本申请提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当该指令被运行时，使得终端装置执行上述第三方面至第三方面的第四种可能的实现方式中任一项所描述的业务分流的方法。
第二十四方面，本申请提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当该指令被运行时，使得第二功能实体执行上述第四方面至第四方面的第一种可能的实现方式中任一项所描述的业务分流的方法。
第二十五方面，本申请提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当该指令被运行时，使得第三功能实体执行上述第五方面至第五方面的第一种可能的实现方式中任一项所描述的业务分流的方法。
第二十六方面，本申请提供一种芯片系统，应用于第一功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行存储在芯片系统中的指令，以执行第一方面至第一方面的任一项所描述的业务分流的方法。
第二十七方面，本申请提供一种芯片系统，应用于第四功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行第二方面至第二方面的任一项的业务分流的方法。
第二十八方面，本申请提供一种芯片系统，应用于终端装置中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行第三方面任一项所描述的业务分流的方法。
第二十九方面，本申请提供一种芯片系统，应用于第二功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行第四方面任一项所描述的业务分流的方法。
第三十方面，本申请提供一种芯片系统，应用于第三功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行第五方面任一项所描述的业务分流的方法。
可选的，本申请中上述描述的芯片系统还包括至少一个存储器，该至少一个存储器中存储有指令。
本申请提供一种通信系统，该通信系统包括如上述第六方面或第六方面所描述的第一功能实体，第九方面或第九方面任一方面所描述的第四功能实体，以及第十二方面所描述的第二功能实体，以及第十四方面所描述的第三功能实体。
在一个可能的设计中，该系统还可以包括本发明实施例提供的方案中与第四功能实体，第一功能实体或者第二功能实体或第三功能实体进行交互的其他设备。
附图说明
图1为现有技术中提供的一种业务分流的方法的示意图；
图2为本申请提供的一种业务分流系统的架构图；
图3为本申请提供的另一种业务分流系统的架构图；
图4为本申请提供的一种业务分流的方法的流程示意图一；
图5为本申请提供的一种业务分流的方法的流程示意图二；
图6为本申请提供的一种第一映射规则信息的示意图；
图7为本申请提供的一种业务分流的方法的流程示意图三；
图8为本申请提供的一种业务分流的方法的流程示意图四；
图9为本申请提供的另一种第一映射规则信息的示意图；
图10为本申请提供的一种业务分流的方法的流程示意图五；
图11为本申请提供的一种业务分流的方法的流程示意图六；
图12为本申请提供一种第一功能实体的结构示意图一；
图13为本申请提供一种第一功能实体的结构示意图二；
图14为本申请提供一种第一功能实体的结构示意图三；
图15为本申请提供一种第四功能实体的结构示意图一；
图16为本申请提供一种第四功能实体的结构示意图二；
图17为本申请提供一种第四功能实体的结构示意图三；
图18为本申请提供一种终端装置的结构示意图一；
图19为本申请提供一种终端装置的结构示意图二；
图20为本申请提供一种终端装置的结构示意图三；
图21为本申请提供一种第二功能实体的结构示意图一；
图22为本申请提供一种第二功能实体的结构示意图二；
图23为本申请提供一种第二功能实体的结构示意图三；
图24为本申请提供一种第三功能实体的结构示意图一；
图25为本申请提供一种第三功能实体的结构示意图二；
图26为本申请提供一种第三功能实体的结构示意图三；
图27为本申请提供的一种芯片系统的结构示意图。
具体实施方式
本申请提供一种业务分流的方法和装置，用以解决业务分流场景中引起的PDU会话中断的问题。其中，方法和装置是基于同一发明构思的，由于方法及设备解决问题的原理相似，因此设备与方法的实施可以相互参见，重复之处不再赘述。
本申请中的术语“第一”、“第二”等仅是为了区分不同的对象，并不对其顺序进行限定。例如，第一功能实体和第二功能实体仅仅是为了区分不同的功能实体，并不对其先后顺序进行限定。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本申请中字符“/”，一般表示前后关联对象是一种“或”的关系。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图2所示，图2示出了本申请提供的一种业务分流的方法所应用的一种业务分流系统的架构示意图，如图2所示，包括：第一功能实体101、第二功能实体102、第三功能实体103、第四功能实体104以及第五功能实体105。
其中，第四功能实体104和第一功能实体101之间可以直接通信，也可以间接通信，例如，通过其他功能实体转发进行通信，例如，第四功能实体104和第一功能实体101之间通过如图2所示的第六功能实体106转发进行通信。
该第四功能实体104与至少一个终端107通信，其中，终端107和第五功能实体105之间具有第一会话，该第一会话可以为第一功能实体101建立的，这样终端107便可以通过第一会话与第五功能实体105对应的数据网络之间进行业务传输，例如，该第一会话可以为协议数据单元(protocol data unit，PDU)会话。
第一功能实体101用于为第一会话确定一个第二功能实体102，然后向该第二功能实体102发送第一映射规则，以使得第二功能实体可以根据第一映射规则将第一会话中的一部分业务发送至第三功能实体103。
第一功能实体101还用于向第三功能实体103发送第一服务器的地址和第二服务器的地址之间的映射关系。其中，第一服务器为终端的第一业务与源数据网络通信时获取第一业务的服务器，也即第一服务器属于源数据网络中的一个服务器，第二服务器为终端的第一业务与目的数据网络通信时获取第一业务的服务器，也即第二服务器属于目的数据网络中的一个服务器。
第三功能实体103用于在接收到终端发送的上行业务时，将上行业务的地址从第一服务器的地址转换为第二服务器的地址，并发送出去，以及用于在接收到发送给终端的下行业务时，将下行业务的地址从第二服务器的地址转换为第一服务器的地址，并发送出去。
第四功能实体104用于获取终端107的位置信息，以及根据终端107的位置信息确定是否存在为终端的某一个业务更好提供服务的目的数据网络。
可以理解的是，第四功能实体104中存在至少一个数据网络的信息，该数据网络的信息包括数据网络的接入地址，名称，部署的地理位置等信息。其中，数据网络(data network，DN)，用于提供数据服务的外部网络。
在本发明实施例中，终端可以分布于整个无线网络中，每个终端可以是静态的或移动的。
其中，若上述业务分流系统应用于5G网络，则如图3所示，第一功能实体101所对应的网元或者实体可以为会话功能管理(session management function，SMF)实体；第二功能实体102所对应的网元或者实体可以为具有对一个会话的业务进行分流的网元，例如，上行分类器(uplink classifier，UL CL)或者分支点网元(branching point)。第三功能实体103所对应的网元或者实体可以为第一用户面功能(user plan function，UPF)锚点(achor)；第四功能实体104所对应的网元或者实体可以为应用功能(application function，AF)，第五功能实体105所对应的网元或者实体可以为第二UPF achor。
其中，第三功能实体103通过N6接口与第二数据网络连接，第五功能实体105通过N6接口与第一数据网络连接。
此外，如图3所示，该5G网络还可以包括接入设备(例如，接入网络(access network，AN))、接入与移动管理功能(access and mobility management function，AMF)实体、统一数据管理(unified data management，UDM)实体、鉴权服务器功能(authentication server function，AUSF)实体、策略控制功能(policy control function，PCF)实体等，本申请实施例对此不作具体限定。
其中，终端通过N1接口(简称N1)与AMF实体通信；AMF实体通过N11接口(简称N11)与SMF实体通信，SMF实体通过N4接口(简称N4)与第一UPF achor和第二UPF achor通信，第一UPF achor通过N6接口(简称N6)与第一DN通信，第二UPF achor通过N6接口(简称N6)与第二DN通信。终端通过接入设备接入网络，接入设备与AMF实体之间通过N2接口(简称N2)通信，接入设备与UL CL之间通过N3接口(简称N3)通信，UL CL分别通过N9接口(简称N9)与第一UPF achor和第二UPF achor通信。SMF实体通过N7接口(简称N7)与PCF实体通信，PCF实体通过N5接口与AF通信。
其中，PCF用于转发AF的信令或者数据到SMF实体。
需要说明的是，图3中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图3的接入设备、AMF实体、SMF实体、AUSF实体、UDM实体、UPF实体和PCF实体等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入设备、AMF实体、SMF实体、AUSF实体、UDM实体、UPF实体和PCF实体所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM实体还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，以下不再赘述。
需要说明的是，本申请中第一会话即指SMF实体建立的连通终端和数据网络之间的通信链路，该通信链中包括终端，接入设备，UPF achor以及UPF achor对应的数据网络。第一会话可以为协议数据单元会话(protocol data unit session，PDU session)。该PDU session用于提供PDU数据包。
本申请中的第一业务或者业务，是指第一会话所包含的至少一个业务流，该业务流可用五元组来标识，该业务流为第一会话所提供的PDU数据包。
可选的，本申请中的终端107也可以称为终端设备，用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是无线局域网(wireless local area networks，WLAN)中的站点(station，STA)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，第五代(fifth-generation，5G)通信网络中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端设备等。
作为示例，在本发明实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
可选的，本申请实施例中所涉及到的接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，3GPP)接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例中所涉及到的AMF实体还可以负责注册管理，移动性管 理，合法监听等功能，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的SMF实体用于进行会话管理，包括：会话建立，会话修改，会话释放，终端的网络之间互连的协议(internet protocol，IP)地址分配和管理，UPF实体的选择和控制，合法监听等与会话相关的控制功能。
可选的，本申请实施例中所涉及到的UPF实体除了具备图3所示的用户面功能实体的功能，还可实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能。此外，UPF实体还可以是软件定义网络(software defined network，SDN)交换机(switch)，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的AUSF实体用于基于终端的签约数据对终端进行鉴权认证。
可选的，本申请实施例中所涉及到的UDM实体用于储存用户签约数据。此外，UDM实体还包括鉴权认证，处理用户标识，签约管理等功能，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的PCF实体提供策略规则，支持统一的策略架构管理网络行为等与策略相关的功能。
可选的，图3中的用户面功能实体可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
其中，SMF实体用于根据终端的位置信息或者终端发送的数据的特征或者UPF与终端之间的位置，UPF的服务质量为终端重新分配UPF，以重新建立终端和新分配的UPF之间的会话，从而提高重建后的会话能够优化用户面。
接入设备用于为终端提供数据服务，例如，接收终端发送的数据，或者向终端发送数据，在实际使用过程中接入设备可以为基站。其中，在本发明实施例中，基站(base station，BS)可以是与用户设备(user equipment，UE)或其它通信站点如中继站点，进行通信的设备，基站可以提供特定物理区域的通信覆盖。
PCF实体，用于作为射频部分与分组网络(IP网络)间的接口。
AF实体，用于起到应用影响路由的作用。
可以理解的是，如图3所示，当SMF为第一会话确定第二功能实体之后，该SMF将第二功能实体的配置信息与第一会话之间的关联关系发送给接入设备、第三功能实体和第五功能实体，这样当接入设备通过第一会话接收到终端发送的业务时，便可以根据配置信息与第一会话之间的关联关系将第一会话中的业务发送给第二功能实体，这样第二功能实体便可以根据第一映射规则将第一会话中的部分业务转发至第三功能实体。可选的，该第二功能实体中还具有第二映射规则，第二功能实体可以根据该第二映射规则将第一会话中的其他业务转发至第五功能实体，该配置信息用于识别第二功能实体，该配置信息可以为第二功能实体的接入地址，或者接入标识等信息，本申请对此不进行限定。
由于终端分布于整个无线网络中，且可以在整个无线网络中动态移动，因此，当终端和源数据网络之间的第一会话建立之后，终端通常可以通过第一会话与源数据网 络进行数据交互，例如，从源数据网络中请求业务。但是，若终端移动至另一个数据网络的范围，且该数据网络可以更好地为终端的某个业务提供服务时，或者存在源数据网络无法满足终端某个业务的需求时，且终端可以从另一个数据网络中获取该业务时，第一功能实体便可以为第一会话确定一个第二功能实体，该第二功能实体用于对终端的业务进行转发(也可以称之为分流)，这样便可以通过第二功能实体将终端所请求的某一个业务转发至目的数据网络，以从目的数据网络中请求到该某一个业务。在整个过程中由于不需要为终端更换目的IP，所以可以使得已建立的第一会话不中断。
如图4所示，本申请提供的一种业务分流的方法，包括：
S101、终端装置和第一DN之间的第一会话需要确定第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，其中，第一会话包括至少一个第一业务。
可选的，该第二功能实体用于对第一会话包括的至少一个第一业务分流。
可选的，本申请中的终端装置可以为如图3所示的终端107，第一功能实体可以为SMF实体，第二功能实体可以为上行分类器。
具体的，一方面，本申请中的第一功能实体可以根据预设映射规则信息判断是否需要为终端装置和第一DN之间的第一会话确定第二功能实体，具体的映射规则信息可以参见现有技术，本申请对此不进行限定。另一方面，本申请的第一功能实体还可以在第四功能实体发送的第一请求消息的触发下，确定需要为第一会话确定第二功能实体。
作为本申请提供的一种可能的实施例，如图5所示，本申请提供的方法在S101之前，还包括：
S105、第四功能实体获取终端装置的位置信息。
具体的，本申请中的第四功能实体可以为如图3所示的架构中的AF实体。
S106、第四功能实体根据终端装置的位置信息以及终端装置对应的业务信息，确定存在为终端装置的第一业务服务的第二DN。
可以理解的是，本申请中的第二DN可以包括至少一个DN，该终端装置可以从该至少一个DN中请求到第一业务包括的数据。
本申请中存在为终端装置的第一业务服务的第二DN可以理解为终端装置可以从该第二DN处获取该第一业务包括的数据。
S107、第四功能实体发送第一请求消息，该第一请求消息用于指示第一功能实体为终端装置和第一数据网络DN之间的第一会话确定第二功能实体，该第二功能实体用于对第一会话包括的至少一个第一业务分流。由于在实际过程中，终端装置处于移动状态，而第一功能实体往往并不知道终端装置的具体位置，因此，通过第四功能实体获取终端装置的位置信息，以及确定存在为终端装置的第一业务可以提供更好服务的第二DN时，向第一功能实体发送第一请求消息，可以使得第一功能实体及时对第一会话中的至少一个第一业务进行分流。
作为一种可能的实现方式，本申请中的S101具体可以通过以下方式实现：在第一请求消息的触发下，第一功能实体确定终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体。
可选的，该第一请求消息包括以下至少一项：用于表明存在为第一业务服务的第 二数据网络DN的信息、第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，该第一服务器的地址为终端装置请求第一业务的源地址，该第二服务器的地址为终端装置请求第一业务的目标地址，第三功能实体与第二DN关联。
其中，第三功能实体可以为如图3所示的架构中的第一用户面功能实体。
其中，第一服务器为第一数据网络对应的至少一个服务器中的一个服务器，其中，第一数据网络与终端装置之间具有第一会话，第二服务器为第二数据网络对应的至少一个服务器中的一个服务器，第二数据网络为第四功能实体根据终端装置的位置信息确定的一个数据网络，与第一数据网络相比，该第二数据网络可以更好地为终端装置的数据提供服务。
其中，第二DN的信息包括数据网络名称(DN name，DNN)，数据网络接入标识(DN access identifier，DNAI)。
可选的，本申请中第一功能实体为第一会话确定第二功能实体可以通过如下方式实现：第一功能实体根据预设规则信息确定第二功能实体，例如，当一个第二功能实体位于第一会话中时，直接将该第二功能实体确定为第一会话的第二功能实体，或者第一功能实体接收PCF实体发送的第一策略，该第一策略用于指示第二功能实体的信息，第一功能实体根据第一策略，确定第二功能实体。
需要说明的是，本申请中的第二功能实体在第一功能实体确定需要为终端装置和第一数据网络DN之间的第一会话确定第二功能实体之前就存在于第一会话中，在这种情况下，第二功能实体与接入设备、第一会话对应的第五功能实体之间已建立了连接，但是第二功能实体中可能不具有第一映射规则信息，基于此种情况，第二功能实体在接收到接入设备转发的终端装置的第一业务时，直接将该第一业务转发至第五功能实体。
其中，第五功能实体可以为如图3所示的架构中的第二UPF achor。
另一方面，可以在终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体的情况下，第一功能实体将该第二功能实体引入该第一会话中，也即终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体时，第二功能实体不存在于第一会话中。当第一功能实体为第一会话确定第二功能实体时，第一功能实体需要将第二功能实体的配置信息发送给接入设备，以及第五功能实体、以及第三功能实体，以建立第二功能实体和接入设备，以及第五功能实体、以及第三功能实体之间的连接，这样接入设备在接收到终端装置对第一业务的请求消息时，可以将对第一业务的请求消息发送给第二功能实体，以由第二功能实体根据第一映射规则，将第一业务转发至第三功能实体，然后第三功能实体根据第一服务器的地址和第二服务器的地址之间的映射关系，将第一业务的地址从第一服务器的地址转化为第二服务器的地址之间发送给第三功能实体对应的第二DN。
具体的，本申请中的第一映射规则信息也可以称之为路由转发规则信息。
S102、第一功能实体向第二功能实体发送第一映射规则信息，该第一映射规则消息用于指示第二功能实体将第一业务发送至第三功能实体，该第三功能实体用于实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
可选的，在S102之前，本申请提供的方法还包括：第一功能实体根据第一服务器的地址和第二服务器的地址之间的映射关系，确定第一映射规则信息。
具体的，本申请中的第一映射规则信息可以为第一功能实体根据第一服务器的地址和第二服务器的地址之间的映射关系确定的，另一方面，该第一映射规则信息还可以为其他设备发送给第一功能实体的，第一功能实体直接接收第一映射规则信息与第一功能实体根据第一服务器的地址和第二服务器的地址之间的映射关系确定第一映射规则信息相比，可以提高第一功能实体的处理效率。
S103、第二功能实体接收第一功能实体发送的第一映射规则信息。
S104、第二功能实体在接收到第一业务后，根据第一映射规则信息将第一业务发送至第三功能实体。
需要说明的是，当第一功能实体未向第二功能实体发送第一映射规则信息之前，当第一会话中存在第二功能实体时，该第二功能实体在接收到第一业务中的数据后，将第一业务中的数据发送至第五功能实体，而在第一功能实体向第二功能实体发送第一映射规则信息之后，第二功能实体收到第一业务中的数据后，将第一业务转发到第三功能实体上。
具体的，如图6所示，该第一映射规则信息包括：第一业务的信息和与第一业务关联的第三功能实体的信息，第二功能实体在接收到第一业务后，根据该第一映射规则信息将第一业务发送至第三功能实体的信息所指示的第三功能实体。
具体的，第一业务的信息可以为第一业务的IP五元组信息，例如，源IP地址，源端口，目的IP地址等信息。第一映射规则信息包括的第一业务的信息可以为第一业务的第二服务器的地址。
第三功能实体的信息可以为第三功能实体的标识(例如，地址，接入标识等)、通道地址(tunnel ID)、数据网络的接入标识等。
此外，可选的，本申请中的第一功能实体还可以向第二功能实体发送第二映射规则信息，该第二映射规则信息用于指示第二功能实体将第一会话中的第二业务转发至第五功能实体，其中，第五功能实体与终端装置之间具有第一会话。
具体的，该第二映射规则信息可以为第二业务的源服务器的信息和与源服务器对应的UPF achor的信息。
需要说明的是，本申请中的第一功能实体在为第一会话确定第二功能实体之后，该第二功能实体和第三功能实体和第五功能实体之间均具有连接，这样第二功能实体便可以对第一会话中的业务按照第一映射规则信息分流至第五功能实体或第三功能实体。
当然，本申请中第一功能实体还可以向第二功能实体不发送第二映射规则信息，这样第二功能实体在确定接收到终端装置发送的第二业务时，若确定第一映射规则信息中不存在与该第二业务的信息对应的第三功能实体时，便将该第二业务转发至第五功能实体。
本申请提供一种业务分流的方法，终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，并向第二功能实体发送用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则 信息，这样第二功能实体在接收到第一业务之后，便可以根据第一映射规则信息将第一业务发送至第三功能实体，由第三功能实体实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，这样不仅可以在存在可以为第一业务提供更好的数据网络时，将第一业务分流，且由于本申请中在对第一业务分流的过程中终端装置无需改变第一业务的目的IP，因此可以避免在对第一业务进行分流时，第一PDU会话不中断。
可选的，如图7所示，本申请提供的方法还包括：
S108、第一功能实体向第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于第三功能实体将第一业务的地址从第一服务器的地址映射为第二服务器的地址，或者用于第三功能实体将第一业务的地址从第二服务器的地址映射为第一服务器的地址。
需要说明的是，本申请中第一功能实体向第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系的过程和第一功能实体向第二功能实体发送第一映射规则的过程可以同时执行，也即该两个过程的执行并无先后顺序。
具体的，第一功能实体可以向第三功能实体发送网络地址转换(network address translation，NAT)规则，该NAT规则中包括第一服务器的地址和第二服务器的地址之间的映射关系。
S109、第三功能实体接收第一服务器的地址和第二服务器的地址之间的映射关系。
S110、第三功能实体在接收到第二功能实体发送的第一业务时，将第一业务的地址从第一服务器的地址转换为第二服务器的地址，并将转换地址后的第一业务发送至第二服务器对应的第二数据网络，以从第二服务器对应的第二数据网络获取第一业务，第三功能实体在接收到第二服务器对应的第二数据网络发送的第一业务后，将第一业务的地址从第二服务器的地址映射为第一服务器的地址，并发送至第二功能实体。
示例性的，第一业务中的数据1所在的第一服务器的地址为IP1，第三功能实体接收到数据1之后，将数据1的地址从IP1变换为IP2之后，并将地址从IP1变换为IP2的数据1发送至第二数据网络，以从第二数据网络处获取数据1；当第三功能实体根据IP2从第二数据网络处获取数据1之后，第三功能实体将该数据1的地址从IP2变换为IP1之后，将地址从IP2变换为IP1的数据1发送给第二功能实体。
作为本申请的另一种可能的实施例，如图8所示，本申请提供的方法，在S105之前还包括：
S111、第四功能实体向终端装置发送用于指示上报终端装置的位置信息的第二请求消息。
其中，第二请求消息可以为终端装置和第四功能实体之间新定义的信令消息，该新定义的信令消息用于指示上报终端装置的位置信息的信息，第二请求消息也可以通过终端装置和第四功能实体之间已具有的一个信令消息，在该信令消息中具有承载指示上报终端装置的位置信息的字段，本申请对此不作限定。
当然，本申请中第四功能实体还可以从其他地方获取终端装置的位置信息，本申请对此不进行限定。
具体的，第四功能实体中具有至少一个DN的信息，以及业务和至少一个DN之 间的关联关系，这样第四功能实体便可以根据终端装置的位置信息，以及终端装置的业务信息从至少一个DN中为终端装置的第一业务确定第一DN。
S112、终端装置接收第二请求消息。
S113、终端装置向第四功能实体发送终端装置的位置信息。
可选的，终端装置的位置信息可以为终端装置的经度、纬度等信息，本申请对此不进行限定。
作为本申请的另一个实施例，在第一业务中的数据被分流之后，为了使得终端装置可以确定第一业务被分流，因此，一方面，本申请提供的方法还包括：
S114、第四功能实体向终端装置发送第一指示信息，该第一指示信息装置用于表明第一服务器的地址和第二服务器的地址之间的映射关系。
S115、终端装置接收第一指示信息。
S116、终端装置根据第一指示信息，将第一业务的地址从第一服务器的地址映射为所述第二服务器的地址，以及按照第二服务器的地址请求第一业务。
具体的，终端装置将第一业务的IP五元组信息从第一服务器的地址变更为第二服务器的地址，然后，终端装置按照第二服务器的地址请求第一业务。
在这种情况下，第一功能实体将第二功能实体发送的第一映射规则信息便可以为第一业务更新的信息(即第二服务器的地址)与第三功能实体之间的关联关系，这样第二功能实体在接收到第一业务更新的信息之后便可以将第一业务转发至第三功能实体。
可选的，另一方面，本申请中还包括：第四功能实体向终端装置发送第一服务器的地址和第二服务器的地址之间的映射关系，该映射关系用于终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址，该第一服务器的地址为终端装置请求第一业务的源地址，第二服务器的地址为终端装置请求第一业务的目标地址。
其中，目标地址为终端装置实际请求第一业务的地址，源地址为终端装置原本请求第一业务的地址。
如图9所示，当第四功能实体向终端装置发送用于指示终端装置将第一业务的地址从第一服务器的地址映射为第二服务器的地址时，第一功能实体向第二功能实体发送的第一映射规则信息包括：第一业务的第一服务器的地址和第五功能实体之间的关联关系，以及第一业务的第二服务器的地址和第三功能实体之间的关联关系。
需要说明的是，当S114-S116执行时，上述S108、S109以及S110便可以省略。
综上所述，如图10所示，下述以第一功能实体为SMF实体，第二功能实体为UL CL，第三功能实体为第二UPF achor，第四功能实体为AF实体，第五功能实体为第一UPF achor，以SMF在AF通过PCF的触发下，确定UL CL为例，详细介绍本申请的业务分流的方法的具体流程，包括：
S201、UE向AF上报UE的位置信息。
其中，UE的位置信息可以为用于确定UE位置的信息，本申请对此不限定。
S202、AF根据UE的位置信息，确定存在为UE的第一业务服务的第二DN。
S203、AF向PCF发送第一请求消息。
其中，该第一请求消息的内容可以参见上述实施例中的描述，本申请在此不再赘 述，此外，第一请求消息中还可以包括UE的信息，应用信息，该UE的信息用于识别该UE。其中，应用信息用于PCF对该类型的应用生成相应的规则。
AF提供的UE信息可以用于PCF对某个UE或者多个UE(群组)生成相应的规则。
具体的，如果AF和PCF之间没有直接接口，则AF通过能力开放网元(network exposure function，NEF)与PCF交互。
S204、PCF向SMF发送第二请求消息。
该第二请求消息的内容与第一请求消息的内容可以相同，也可以由PCF将第一请求消息处理之后生成第二请求消息，本申请对此不进行限定。
S205、SMF确定ULCF。
S206、SMF确定ULCF之后向ULCL发送第一映射规则信息，以及向第二UPF achor发送第一服务器的地址和第二服务器的地址之间的关联关系。
具体的，第一映射规则消息为第一业务的信息和与第一业务关联的第二UPF achor信息。
具体的，在S206之后，还包括ULCL根据第一映射规则信息将接收到的第一业务转发至第二UPF achor，以及在接收到第二UPF achor发送的按照第二服务器的地址请求到的第一业务，并由第二UPF achor将接收到的第一业务的地址从第二服务器的地址变更为第一服务器的地址之后，将地址变更为第一服务器的地址的第一业务发送给ULCL，以由ULCL通过接入设备发送给UE。
如图11所示，图11示出了本申请提供的另一种业务分流的方法的具体流程，如图11与图10的区别在于，图11中增加了S207和S208，且省略了S205中SMF向第二UPF achor发送第一服务器的地址和第二服务器的地址之间的关联关系的过程。但是S205中SMF向ULCL发送的第一映射规则信息为第一业务的IP五元组1和与第一业务关联的第一UPF achor信息以及第一业务的IP五元组2和与第一业务关联的第二UPF achor信息，这样ULCL实体在接收到IP五元组为IP五元组1的业务之后，便可以将IP五元组1的业务转发至第一UPF achor，以及在接收到IP五元组为IP五元组2的业务之后，便可以将IP五元组2的业务转发至第二UPF achor。
S207、AF向UE发送第一服务器的地址和第二服务器的地址之间的映射关系，或者发送第一指示信息，该第一指示信息用于指示UE将第一业务中的数据的地址从第一服务器的地址映射为第二服务器的地址。
S208、UE将第一业务的地址从第一服务器的地址映射为第二服务器的地址，并按照第二服务器的地址请求第一业务。
本申请提供一种业务分流的方法，终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，并向第二功能实体发送用于指示第二功能实体将第一业务发送至第三功能实体的第一映射规则信息，这样第二功能实体在接收到第一业务之后，便可以根据第一映射规则信息将第一业务发送至第三功能实体，由第三功能实体实现第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换，这样不仅可以在存在可以为第一业务提供更好的数据网络时，将第一业务分流，还可以避免在对第一业务进行分流的时候，第一 PDU会话不中断。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如第一功能实体、第二功能实体、第三功能实体、第四功能实体和终端装置，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一功能实体、第二功能实体、第三功能实体、第四功能实体和终端装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明：
在采用集成的单元的情况下，图12示出了上述实施例中所涉及的第一功能实体的一种可能的结构示意图。第一功能实体包括：确定单元101、发送单元102。其中，确定单元101用于支持第一功能实体执行上述实施例中的S101以及S205。发送单元102用于支持第一功能实体执行上述实施例中的S102、S108以及S206。此外，第一功能实体还可以包括接收单元103，该接收单元103用于支持第一功能实体执行上述实施例中的S109。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用硬件实现的基础上，本申请中的发送单元102可以为第一功能实体的发送器，接收单元103可以为第一功能实体的接收器，该发送器通常可以和接收器集成在一起用作收发器，具体的收发器还可以称为通信接口或收发电路或者接口电路，确定单元101可以集成在第一功能实体的处理器上。
在采用集成的单元的情况下，图13示出了上述实施例中所涉及的第一功能实体的一种可能的逻辑结构示意图。第一功能实体包括：处理模块112和通信模块113。处理模块112用于对第一功能实体的动作进行控制管理，例如，处理模块112用于执行在第一功能实体侧进行消息或数据处理的步骤，例如，支持第一功能实体执行上述实施例中的S101以及S205。通信模块113用于支持第一功能实体执行上述实施例中的S102、S108、S206以及S109。和/或用于本文所描述的技术的其他由第一功能实体执行的过程。可选的，第一功能实体还可以包括存储模块111，用于存储第一功能实体的程序代码和数据。
其中，处理模块112可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。 通信模块113可以是收发器、收发电路或通信接口或者接口电路等。存储模块111可以是存储器。
当处理模块112为处理器120，通信模块113为通信接口130或收发器时，存储模块111为存储器140时，本申请所涉及的第一功能实体可以为图14所示的设备。
其中，通信接口130、至少一个处理器120以及存储器140通过总线110相互连接；总线110可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器140用于存储第一功能实体的程序代码和数据。通信接口130用于支持第一功能实体与其他设备(例如，第二功能实体)通信，处理器120用于支持第一功能实体执行存储器140中存储的程序代码和数据以实现本申请提供的一种业务分流的方法。
在采用集成的单元的情况下，图15示出了上述实施例中所涉及的第四功能实体的一种可能的结构示意图。第四功能实体包括：获取单元201、确定单元202以及发送单元203。其中，获取单元201用于支持第四功能实体执行上述实施例中的S105。确定单元202用于支持第四功能实体执行上述实施例中的S106以及S202，其中，发送单元203用于支持第四功能实体执行上述实施例中的S107、S111、S114、S203以及S207。此外，和/或用于本文所描述的技术的其它过程。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用硬件实现的基础上，本申请中的获取单元201可以为第四功能实体的接收器，发送单元203可以为第四功能实体发送器，该发送器通常可以和第四功能实体的接收器集成在一起用作收发器，具体的收发器还可以称为通信接口，或收发电路或者接口电路，此外确定单元202可以集成在第四功能实体的处理器上。
在采用集成的单元的情况下，图16示出了上述实施例中所涉及的第四功能实体的一种可能的逻辑结构示意图。第四功能实体，包括：处理模块212和通信模块213。处理模块212用于对第四功能实体的动作进行控制管理，例如，处理模块212用于支持第四功能实体执行上述实施例中在第四功能实体侧进行消息或数据处理的操作，例如，执行上述实施例中的S106以及S202；通信模块213用于支持第四功能实体执行上述实施例中在第四功能实体侧进行消息或数据接收和发送的操作，例如，上述实施例中的S105、S107、S111、S114、S203以及S207。和/或用于本文所描述的技术的其他由第四功能实体执行的过程。
可选的，第四功能实体还可以包括存储模块211，用于存储第四功能实体的程序代码和数据。
其中，处理模块212可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块213可以是收发器、收发电路或通信接口或者接口电路等。存储模块211可以是存储器。
当处理模块212为处理器220，通信模块213为通信接口230或收发器时，存储模块211为存储器210时，本申请所涉及的第四功能实体可以为图17所示的设备。
其中，通信接口230、至少一个处理器220以及存储器210通过总线200相互连接；总线200可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器210用于存储第四功能实体的程序代码和数据。通信接口230用于支持第四功能实体与其他设备(例如，终端装置)通信，处理器220用于支持第四功能实体执行存储器210中存储的程序代码和数据以实现本申请提供的一种业务分流的方法。
在采用集成的单元的情况下，图18示出了上述实施例中所涉及的终端装置的一种可能的结构示意图。终端装置包括：发送单元301、接收单元302以及处理单元303。其中，接收单元302用于支持终端装置执行上述实施例中的S112以及S115；发送单元301用于支持终端装置执行上述实施例中的S113以及S201，处理单元303用于支持终端装置执行上述实施例中的S116以及S208。和/或用于本文所描述的技术的其它过程。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用硬件实现的基础上，本申请中的接收单元302可以为终端装置的接收器，发送单元301可以为终端装置的发送器，该接收器通常可以和终端装置的发送器集成在一起用作收发器，具体的收发器还可以称为通信接口或收发电路或者接口电路。
在采用集成的单元的情况下，图19示出了上述实施例中所涉及的终端装置的一种可能的逻辑结构示意图。终端装置包括：处理模块312和通信模块313。处理模块312用于对终端装置的动作进行控制管理，例如，处理模块312用于支持终端装置执行上述实施例中在终端装置侧进行消息或数据处理的操作，例如，上述实施例中的S116以及S208；通信模块313用于支持终端装置执行上述实施例中在终端装置侧进行消息或数据接收或发送的操作，例如，上述实施例中的S112、S115、S113以及S201。和/或用于本文所描述的技术的其他由终端装置执行的过程。
可选的，终端装置还可以包括存储模块311，用于存储终端装置的程序代码和数据。
其中，处理模块312可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块313可以是收发器、收发电路或通信接口或者接口电路等。存储模块311可以是存储器。
当处理模块312为处理器320，通信模块313为通信接口330或收发器时，存储模块311为存储器310时，本申请所涉及的终端装置可以为图20所示的设备。
其中，通信接口330、至少一个处理器320以及存储器310通过总线300相互连接；总线300可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、 控制总线等。为便于表示，图20中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器310用于存储终端装置的程序代码和数据。通信接口330用于支持终端装置与其他设备(例如，第四功能实体)通信，处理器320用于支持终端装置执行存储器310中存储的程序代码和数据以实现本申请提供的一种业务分流的方法。
在采用集成的单元的情况下，图21示出了上述实施例中所涉及的第二功能实体的一种可能的结构示意图。第二功能实体包括：接收单元401和发送单元402。其中，接收单元401用于支持第二功能实体执行上述实施例中的S103。发送单元402用于支持第二功能实体执行上述实施例中的S104。和/或用于本文所描述的技术的其它过程。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用硬件实现的基础上，本申请中的接收单元401可以为第二功能实体的接收器，发送单元402可以为第二功能实体的发送器，该接收器通常可以和第二功能实体的发送器集成在一起用作收发器，具体的收发器还可以称为通信接口或收发电路或者接口电路。
在采用集成的单元的情况下，图22示出了上述实施例中所涉及的第二功能实体的一种可能的逻辑结构示意图。第二功能实体包括：处理模块412和通信模块413。其中，处理模块412用于对第二功能实体的动作进行控制管理，例如，处理模块412用于支持第二功能实体执行上述实施例中在第二功能实体侧进行消息或数据处理的操作；通信模块413用于支持第二功能实体执行上述实施例中在第二功能实体侧进行消息或数据接收或发送的操作，例如，上述实施例中的S103和S104。和/或用于本文所描述的技术的其他由第二功能实体执行的过程。
可选的，第二功能实体还可以包括存储模块411，用于存储第二功能实体的程序代码和数据。
其中，处理模块412可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块413可以是收发器、收发电路或通信接口或者接口电路等。存储模块411可以是存储器。
当处理模块412为处理器420，通信模块413为通信接口430或收发器时，存储模块411为存储器410时，本申请所涉及的第二功能实体可以为图23所示的设备。
其中，通信接口430、至少一个处理器420以及存储器410通过总线400相互连接；总线400可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图23中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器410用于存储第二功能实体的程序代码和数据。通信接口430用于支持第二功能实体与其他设备(例如，第一功能实体和第三功能实体)通信，处理器420用于支持第二功能实体执行存储器410中存储的程序代码和数据以实 现本申请提供的一种业务分流的方法。
在采用集成的单元的情况下，图24示出了上述实施例中所涉及的第三功能实体的一种可能的结构示意图。第三功能实体包括：接收单元501和处理单元502。其中，接收单元501用于支持第三功能实体执行上述实施例中的S109。处理单元502用于支持第三功能实体执行上述实施例中的S110。和/或用于本文所描述的技术的其它过程。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在采用硬件实现的基础上，本申请中的接收单元501可以为第三功能实体的接收器，该接收器通常可以和第三功能实体的发送器集成在一起用作收发器，具体的收发器还可以称为通信接口或收发电路或者接口电路。
在采用集成的单元的情况下，图25示出了上述实施例中所涉及的第三功能实体的一种可能的逻辑结构示意图。第三功能实体包括：处理模块512和通信模块513。其中，处理模块512用于对第三功能实体的动作进行控制管理，例如，处理模块512用于支持第三功能实体执行上述实施例中在第三功能实体侧进行消息或数据处理的操作；通信模块513用于支持第三功能实体执行上述实施例中在第三功能实体侧进行消息或数据接收或发送的操作，例如，上述实施例中的S109以及S110。和/或用于本文所描述的技术的其他由第三功能实体执行的过程。
可选的，第三功能实体还可以包括存储模块511，用于存储第三功能实体的程序代码和数据。
其中，处理模块512可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块513可以是收发器、收发电路、接口电路或通信接口等。存储模块511可以是存储器。
当处理模块512为处理器520，通信模块513为通信接口530或收发器时，存储模块511为存储器510时，本申请所涉及的第三功能实体可以为图26所示的设备。
其中，通信接口530、至少一个处理器520以及存储器510通过总线500相互连接；总线500可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图26中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器510用于存储第三功能实体的程序代码和数据。通信接口530用于支持第三功能实体与其他设备(例如，第一功能实体)通信，处理器520用于支持第三功能实体执行存储器510中存储的程序代码和数据以实现本申请提供的一种业务分流的方法。
以上接收单元(或用于接收的单元)是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上发送单元(或用于发送的单元)是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送 单元是该芯片用于向其它芯片或装置发送信号的接口电路。
图27是本发明实施例提供的芯片系统150的结构示意图。芯片系统150包括至少一个处理器1510和接口电路1530。
可选的，该芯片系统150还包括存储器1540，存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供操作指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。
在一些实施方式中，存储器1540存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
在本发明实施例中，通过调用存储器1540存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
一种可能的实现方式为：第一功能实体，第二功能实体，第三功能实体，第四功能实体以及终端装置所用的芯片系统的结构类似，不同的装置可以使用不同的芯片系统以实现各自的功能。
处理器1510控制第一功能实体，第二功能实体，第三功能实体，第四功能实体以及终端的操作，处理器1510还可以称为CPU(central processing unit，中央处理单元)。存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(NVRAM)。具体的应用中存储器1540、接口电路1530以及存储器1540通过总线系统1520耦合在一起，其中总线系统1520除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图27中将各种总线都标为总线系统1520。
上述本发明实施例揭示的方法可以应用于处理器1510中，或者由处理器1510实现。处理器1510可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1510可以是通用处理器、数字信号处理器(digital signal processing，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1540，处理器1510读取存储器1540中的信息，结合其硬件完成上述方法的步骤。
可选地，接口电路1530用于执行图4、图5、图7、图8、图10、图11所示的实施例中的第一功能实体，第二功能实体，第三功能实体，第四功能实体以及终端装置的接收和发送的步骤。
处理器1510用于执行图4、图5、图7、图8、图10、图11所示的实施例中的第一功能实体，第二功能实体，第三功能实体，第四功能实体以及终端装置的处理的步骤。
在上述实施例中，存储器存储的供处理器执行的指令可以以计算机程序产品的形式实现。计算机程序产品可以是事先写入在存储器中，也可以是以软件形式下载并安装在存储器中。
计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk，SSD)等。
一方面，提供一种计算机存储介质，计算机可读存储介质中存储有指令，当指令被运行时，使得第一功能实体执行实施例中的S101、S205、S102、S108、S206以及S109。和/或用于本文所描述的技术的其他由第一功能实体执行的过程。
又一方面，提供一种计算机存储介质，计算机可读存储介质中存储有指令，当指令被运行时，使得第四功能实体执行实施例中的S106以及S202、S105、S107、S111、S114、S203以及S207。和/或用于本文所描述的技术的其他由第四功能实体执行的过程。
另一方面，提供一种计算机存储介质，计算机可读存储介质中存储有指令，当指令被运行时，使得终端装置执行实施例中的S116以及S208、S112、S115、S113以及S201。和/或用于本文所描述的技术的其他由终端执行的过程。
再一方面，又一方面，提供一种计算机存储介质，计算机可读存储介质中存储有指令，当指令被运行时，使得第二功能实体执行实施例中的S103和S104。和/或用于本文所描述的技术的其他由第二功能实体执行的过程。
另一方面，提供一种计算机存储介质，计算机可读存储介质中存储有指令，当指令被运行时，使得第三功能实体执行实施例中的S109以及S110。和/或用于本文所描述的技术的其他由第三功能实体执行的过程。
一方面，提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当指令被运行时，使得第一功能实体执行实施例中的S101、S205、S102、S108、S206以及S109。和/或用于本文所描述的技术的其他由第一功能实体执行的过程。
又一方面，提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当指令被运行时，使得第四功能实体执行实施例中的S106以及S202、S105、S107、S111、S114、S203以及S207。和/或用于本文所描述的技术的其他由第四功能实体执行的过程。
另一方面，提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当指令被运行时，使得终端执行实施例中的S116以及S208、S112、S115、S113以及S201。和/或用于本文所描述的技术的其他由终端装置执行的过程。
又一方面，提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当指令被运行时，使得第二功能实体执行实施例中的S103和S104。和/或用于本文所描述的技术的其他由第二功能实体执行的过程。
另一方面，提供一种包含指令的计算机程序产品，计算机程序产品中存储有指令，当指令被运行时，使得第三功能实体执行实施例中的S109以及S110。和/或用于本文所描述的技术的其他由第三功能实体执行的过程。
一方面，提供一种芯片系统，该芯片系统应用于第一功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中的S101、S205、S102、S108、S206以及S109。和/或用于本文所描述的技术的其他由第一功能实体执行的过程。
又一方面，提供一种芯片系统，该芯片系统应用于第四功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中实施例中的S106以及S202、S105、S107、S111、S114、S203以及S207。和/或用于本文所描述的技术的其他由第四功能实体执行的过程。
另一方面，提供一种芯片系统，该芯片系统应用于终端中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中的S116以及S208、S112、S115、S113以及S201。和/或用于本文所描述的技术的其他由终端装置执行的过程。
又一方面，提供一种芯片系统，该芯片系统应用于第二功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中的S103和S104。和/或用于本文所描述的技术的其他由第二功能实体执行的过程。
另一方面，提供一种芯片系统，该芯片系统应用于第三功能实体中，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中的S109以及S110。和/或用于本文所描述的技术的其他由第三功能实体执行的过程。
此外，本申请还提供一种业务分流的系统，该业务分流的系统包括如图12-图14所示的第一功能实体，图15-图17所示的第四功能实体，图18-图20所示的终端装置，图21-图23所示的第二功能实体以及图24-图26所示的第三功能实体。
本申请提供一种业务分流的系统，终端装置和第一数据网络DN之间的第一会话需要确定第二功能实体的情况下，第一功能实体为第一会话确定第二功能实体，并向第二功能实体发送用于指示第二功能实体将第一业务中的数据发送至第三功能实体的第一映射规则信息，这样第二功能实体在接收到第一业务中的数据之后，便可以根据第一映射规则信息将第一业务中的数据发送至第三功能实体，由第三功能实体实现第一业务中的数据的地址从第一服务器的地址到第二服务器的地址之间的转换，这样不仅可以在存在可以为第一业务中的数据提供更好的数据网络时，将第一业务中的数据分流，还可以避免在对第一业务中的数据进行分流的时候，第一PDU会话不中断。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功 能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (30)

  1. 一种业务分流的方法，其特征在于，包括：
    终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，第一功能实体为所述第一会话确定所述第二功能实体，所述第一会话包括至少一个第一业务；
    所述第一功能实体向所述第二功能实体发送第一映射规则信息，所述第一映射规则信息用于指示所述第二功能实体将所述第一业务发送至第三功能实体，所述第三功能实体用于实现所述第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
  2. 根据权利要求1所述的方法，其特征在于，包括：
    所述第一功能实体接收第一请求消息，所述第一请求消息用于指示所述第一功能实体需要为所述终端装置和所述第一数据网络DN之间的所述第一会话确定所述第二功能实体。
  3. 根据权利要求2所述的方法，其特征在于，所述第一请求消息包括以下至少一项：
    用于表明存在为所述第一业务服务的第二数据网络DN的信息、所述第二DN的信息、所述第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址，所述第二DN与所述第三功能实体关联。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一功能实体根据所述第一服务器的地址和第二服务器的地址之间的映射关系，确定所述第一映射规则信息。
  5. 根据权利要求4所述的方法，其特征在于，所述第一映射规则信息包括：所述第一业务的信息和与所述第一业务关联的所述第三功能实体的信息。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第一功能实体向所述第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系，所述映射关系用于所述第三功能实体将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址，或者用于所述第三功能实体将所述第一业务地址从所述第二服务器的地址映射为所述第一服务器的地址。
  7. 一种业务分流方法，其特征在于，包括：
    第四功能实体获取终端装置的位置信息；
    所述第四功能实体根据所述终端装置的位置信息确定存在为所述终端装置的第一业务服务的第二数据网络DN的情况下，所述第四功能实体发送第一请求消息，所述第一请求消息用于指示为所述终端装置和第一数据网络DN之间的第一会话确定第二功能实体，所述第二功能实体用于对所述第一会话包括的至少一个第一业务分流。
  8. 根据权利要求7所述的方法，其特征在于，所述第一请求消息包括以下任一项：
    用于表明存在为所述第一业务服务的第二数据网络DN的信息、所述第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系， 其中，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址，所述第二DN与所述第三功能实体关联。
  9. 根据权利要求7或8所述的方法，其特征在于，所述方法还包括：
    所述第四功能实体向所述终端装置发送用于指示上报所述终端装置的位置信息的第二请求消息。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述方法还包括：
    所述第四功能实体向所述终端装置发送第一指示信息，所述第一指示信息用于指示所述终端装置将所述第一业务的地址从第一服务器的地址映射为第二服务器的地址。
  11. 根据权利要求7-9任一项所述的方法，其特征在于，所述方法还包括：
    所述第四功能实体向所述终端装置发送第一服务器的地址和第二服务器的地址之间的映射关系，所述映射关系用于所述终端装置将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址。
  12. 一种业务分流的方法，其特征在于，包括：
    终端装置向第四功能实体发送所述终端装置的位置信息；
    所述终端装置接收所述第四功能实体发送的第一指示信息，所述第一指示信息用于表明第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址；
    所述终端装置根据所述第一指示信息，将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述终端装置接收所述第四功能实体发送的第二请求消息，所述第二请求消息用于指示所述终端装置上报所述终端装置的位置信息。
  14. 一种业务分流的装置，其特征在于，包括：
    终端装置和第一数据网络DN之间的第一会话需要第二功能实体的情况下，确定单元，用于为所述第一会话确定所述第二功能实体，所述第一会话包括至少一个第一业务；
    发送单元，用于向所述第二功能实体发送第一映射规则信息，所述第一映射规则信息用于指示所述第二功能实体将所述第一业务发送至第三功能实体，所述第三功能实体用于实现所述第一业务的地址从第一服务器的地址到第二服务器的地址之间的转换。
  15. 根据权利要求14所述的装置，其特征在于，所述装置，还包括：
    接收单元，用于接收第一请求消息，所述第一请求消息用于指示第一功能实体需要为所述终端装置和所述第一数据网络DN之间的所述第一会话确定所述第二功能实体。
  16. 根据权利要求15所述的装置，其特征在于，所述第一请求消息包括以下至少 一项：
    用于表明存在为所述第一业务服务的第二数据网络DN的信息、所述第二DN的信息、所述第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址，所述第二DN与所述第三功能实体关联。
  17. 根据权利要求16所述的装置，其特征在于，所述确定单元，还用于根据所述第一服务器的地址和第二服务器的地址之间的映射关系，确定所述第一映射规则信息。
  18. 根据权利要求17所述的装置，其特征在于，所述第一映射规则信息包括：所述第一业务的信息和与所述第一业务关联的所述第三功能实体的信息。
  19. 根据权利要求14-18任一项所述的装置，其特征在于，所述发送单元，还用于向所述第三功能实体发送第一服务器的地址和第二服务器的地址之间的映射关系，所述映射关系用于所述第三功能实体将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址，或者用于所述第三功能实体将所述第一业务的地址从所述第二服务器的地址映射为所述第一服务器的地址。
  20. 根据权利要求14-19任一项所述的装置，其特征在于，所述装置还包括：
    接收单元，用于接收第一请求消息，所述第一请求消息用于指示所述第一功能实体为终端装置和第一数据网络DN之间的所述第一会话确定第二功能实体。
  21. 一种业务分流装置，其特征在于，包括：
    获取单元，用于获取终端装置的位置信息；
    确定单元，用于根据所述终端装置的位置信息，确定存在为所述终端装置的第一业务服务的第二数据网络DN；
    发送单元，用于在确定单元确定存在所述第二数据网络DN的情况下，发送第一请求消息，所述第一请求消息用于指示为所述终端装置和第一数据网络DN之间的第一会话确定第二功能实体，所述第二功能实体用于对所述第一会话包括的至少一个第一业务分流。
  22. 根据权利要求21所述的装置，其特征在于，所述第一请求消息包括以下任一项：
    用于表明存在为所述第一业务服务的第二数据网络DN的信息、所述第二DN的信息、第三功能实体的信息、第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址，所述第二DN与所述第三功能实体关联。
  23. 根据权利要求21或22所述的装置，其特征在于，所述发送单元，还用于向所述终端装置发送用于指示上报所述终端装置的位置信息的第二请求消息。
  24. 根据权利要求21-23任一项所述的装置，其特征在于，所述发送单元，还用于向所述终端装置发送第一指示信息，所述第一指示信息用于指示所述终端装置将所述第一业务的地址从第一服务器的地址映射为第二服务器的地址。
  25. 根据权利要求21-24任一项所述的装置，其特征在于，所述发送单元，还用 于向所述终端装置发送第一服务器的地址和第二服务器的地址之间的映射关系，所述映射关系用于所述终端装置将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址，所述第一服务器的地址为所述终端装置请求所述第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务的目标地址。
  26. 一种业务分流的装置，其特征在于，包括：
    发送单元，用于向第四功能实体发送终端装置的位置信息；
    接收单元，用于接收所述第四功能实体发送的第一指示信息，所述第一指示信息用于表明第一服务器的地址和第二服务器的地址之间的映射关系，其中，所述第一服务器的地址为所述终端装置请求第一业务的源地址，所述第二服务器的地址为所述终端装置请求所述第一业务中的目标地址；
    处理单元，用于根据所述第一指示信息，将所述第一业务的地址从所述第一服务器的地址映射为所述第二服务器的地址。
  27. 根据权利要求26所述的装置，其特征在于，所述接收单元，还用于接收所述第四功能实体发送的第二请求消息，所述第二请求消息用于指示所述终端装置上报所述终端装置的位置信息。
  28. 根据权利要求26或27所述的装置，其特征在于，所述第一指示信息包括：第一服务器的地址和第二服务器的地址之间的映射关系，所述映射关系用于所述终端装置将所述第一业务的地址从所述第二服务器的地址映射为所述第一服务器的地址。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质应用于业务分流装置中，所述计算机可读存储介质中存储有指令，当所述指令被运行时，使得上述权利要求1-6任一项或7-11任一项或12或13任一项所述的业务分流方法被执行。
  30. 一种芯片系统，其特征在于，应用于业务分流的装置中，所述芯片系统包括至少一个处理器和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器用于运行指令，以进行权利要求1-6任一项或权利要求7-11任一项或权利要求12或13所述的业务分流的方法。
PCT/CN2019/073523 2018-01-31 2019-01-28 一种业务分流的方法和装置 WO2019149177A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810098667.8A CN110099010B (zh) 2018-01-31 2018-01-31 一种业务分流的方法和装置
CN201810098667.8 2018-01-31

Publications (1)

Publication Number Publication Date
WO2019149177A1 true WO2019149177A1 (zh) 2019-08-08

Family

ID=67443374

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/073523 WO2019149177A1 (zh) 2018-01-31 2019-01-28 一种业务分流的方法和装置

Country Status (2)

Country Link
CN (1) CN110099010B (zh)
WO (1) WO2019149177A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220038378A1 (en) * 2019-11-08 2022-02-03 Tencent Technology (Shenzhen) Company Limited Service offloading method, apparatus, and system, electronic device, and storage medium
CN114125995A (zh) * 2021-11-23 2022-03-01 新华三技术有限公司成都分公司 数据传输方法及装置
EP4024922A4 (en) * 2020-04-30 2022-12-07 Tencent Technology (Shenzhen) Company Limited PROCEDURES FOR ACHIEVEMENT OF CONTINUITY OF SERVICE AND RELATED EQUIPMENT

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113993118B (zh) * 2021-10-15 2023-07-25 中国联合网络通信集团有限公司 数据分流方法、装置、设备、功能实体及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
US9198209B2 (en) * 2012-08-21 2015-11-24 Cisco Technology, Inc. Providing integrated end-to-end architecture that includes quality of service transport for tunneled traffic
CN105554176A (zh) * 2015-12-29 2016-05-04 华为技术有限公司 发送报文的方法、装置和通信系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103460653A (zh) * 2011-03-31 2013-12-18 日本电气株式会社 计算机系统和通信方法
CN107911844B (zh) * 2013-01-24 2021-10-01 华为技术有限公司 控制分流的方法、ue、网络设备及服务器
CN104641679B (zh) * 2013-04-03 2019-03-19 华为技术有限公司 一种无线网络的分流方法及设备、系统
CN105491617A (zh) * 2015-12-03 2016-04-13 北京北方烽火科技有限公司 一种支持业务本地分流的方法及基站子系统
CN106982443B (zh) * 2016-01-18 2020-10-30 中国移动通信集团河北有限公司 业务分流方法及装置
US10362511B2 (en) * 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
US9198209B2 (en) * 2012-08-21 2015-11-24 Cisco Technology, Inc. Providing integrated end-to-end architecture that includes quality of service transport for tunneled traffic
CN105554176A (zh) * 2015-12-29 2016-05-04 华为技术有限公司 发送报文的方法、装置和通信系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220038378A1 (en) * 2019-11-08 2022-02-03 Tencent Technology (Shenzhen) Company Limited Service offloading method, apparatus, and system, electronic device, and storage medium
EP4024922A4 (en) * 2020-04-30 2022-12-07 Tencent Technology (Shenzhen) Company Limited PROCEDURES FOR ACHIEVEMENT OF CONTINUITY OF SERVICE AND RELATED EQUIPMENT
CN114125995A (zh) * 2021-11-23 2022-03-01 新华三技术有限公司成都分公司 数据传输方法及装置
CN114125995B (zh) * 2021-11-23 2023-06-27 新华三技术有限公司成都分公司 数据传输方法及装置

Also Published As

Publication number Publication date
CN110099010B (zh) 2021-08-03
CN110099010A (zh) 2019-08-06

Similar Documents

Publication Publication Date Title
US11588741B2 (en) Service flow processing method, communication method, and apparatus
EP3614730B1 (en) Parameter determination method and communication entity
CN111031080B (zh) 报文传输方法及装置
EP3944665B1 (en) Session management method, apparatus, and system, and device
CN110830429B (zh) 一种业务流的传输方法、通信方法及装置
EP3793240A1 (en) Configuration method, data transmission method and apparatus
WO2019149177A1 (zh) 一种业务分流的方法和装置
CN110072297B (zh) 一种信息交互方法、装置及计算机可读存储介质
WO2017214975A1 (zh) 获取终端无线能力信息的方法、核心网实体、基站和终端
CN110557846B (zh) 一种数据传输方法、终端设备及网络设备
US11503667B2 (en) Enhancement for multi-access PDU session release
WO2019071900A1 (zh) 网络切换之后返回的方法、接入网设备和核心网设备
WO2018201999A1 (zh) 用户面链路建立方法、基站及移动性管理设备
JP2021530171A (ja) 経路選択方法、端末デバイス及びネットワークデバイス
CN109314893B (zh) 一种切换方法及装置
WO2018170746A1 (zh) 通信方法、辅网络节点和终端
CN112738855B (zh) 一种应用在quic的基于多链路的传输方法和装置
JP6281192B2 (ja) 基地局装置、ハンドオーバー制御方法および無線通信システム
WO2020034869A1 (zh) 一种业务流的传输方法、通信方法及装置
US20220264356A1 (en) Traffic routing method, apparatus, and system
US20220353941A1 (en) Ma pdu reactivation requested handling
CN112789896A (zh) 切换传输路径的方法及装置
WO2024027299A1 (zh) 消息路由方法和装置
WO2023143270A1 (zh) 一种通信方法及装置
CN115915196A (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: 19747956

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

Country of ref document: EP

Kind code of ref document: A1