CN110099010B

CN110099010B - Service distribution method and device

Info

Publication number: CN110099010B
Application number: CN201810098667.8A
Authority: CN
Inventors: 韦安妮; 吴义壮; 熊春山
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-01-31
Filing date: 2018-01-31
Publication date: 2021-08-03
Anticipated expiration: 2038-01-31
Also published as: CN110099010A; WO2019149177A1

Abstract

The application provides a method and a device for service distribution, relates to the technical field of communication, and aims to solve the problem that a session is interrupted due to the mobility of UE (user equipment) in the traditional technical scheme. The scheme comprises the following steps: under the condition that a first session between a terminal device and a first Data Network (DN) needs a second functional entity, the first functional entity determines the second functional entity for the first session, and the first session comprises at least one first service; the method comprises the steps that a first functional entity sends first mapping rule information to a second functional entity, the first mapping rule information is used for indicating the second functional entity to send a first service to a third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of a first server to the address of a second server.

Description

Service distribution method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for service offloading.

Background

A Protocol Data Unit (PDU) session is a connection between a User Equipment (UE) and a Data Network (DN) defined in a fifth generation (5th generation, 5G) mobile communication system, and is used to provide a PDU connectivity service. The PDU connection service supported by a 5G Core Network (CN) is a service for providing PDU exchange between a UE and a Data Network (DN) determined by a Data Network Name (DNN). The UE may establish a PDU session served by different User Plane Function (UPF) entities to connect to the same DN.

In a conventional technical solution, as the UE moves, a Session Management Function (SMF) entity may insert an "uplink classifier (ULCL)" for a PDU session of the UE, where the ULCL is used for filtering conditions provided by the SMF entity on a UPF entity supporting the ULCL function, so that the UPF entity shunts a plurality of services of the PDU session to different UPF anchor points (anchors), and each UPF corresponds to one anchor point DN to perform service transmission with the UE through a target DN (e.g., a DN closest to the UE). As shown in fig. 1, service 1 of one PDU session will be shunted from the UPF anchor1 shown in fig. 1 to UPF anchor2 by a UPF containing a ULCL function.

However, usually, the change of the anchor causes the PDU session established between the UE and the DN corresponding to the anchor to be interrupted, and the conventional technical solution does not solve the problem of the PDU session interruption caused in the service offloading scenario.

Disclosure of Invention

The embodiment of the invention provides a method and a device for service distribution, which are used for solving the problem of PDU session interruption caused in a service distribution scene.

In a first aspect, the present application provides a method for service offloading, including: under the condition that a first session between a terminal device and a first Data Network (DN) needs a second functional entity, the first functional entity determines the second functional entity for the first session, and the second functional entity is used for shunting at least one first service included in the first session; the first functional entity sends first mapping rule information to the second functional entity, the first mapping rule information is used for indicating the second functional entity to send the first service to the third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of the first server to the address of the second server.

The application provides a method for service distribution, under the condition that a first session between a terminal device and a first data network DN needs a second functional entity, the first functional entity determines the second functional entity for the first session, and sends first mapping rule information for instructing the second functional entity to send a first service to a third functional entity, so that the second functional entity can send data in the first service to the third functional entity according to the first mapping rule information after receiving the first service, and the third functional entity realizes the conversion of the address of the first service from the address of a first server to the address of a second server, thereby not only distributing the data in the first service when a better data network which can be provided for the first service exists, but also not changing the target IP of the first service because the terminal device does not need to change the first service in the process of distributing the first service in the application, therefore, the first PDU session can be prevented from being interrupted when the first service is shunted.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the method provided by the present application further includes: the first functional entity receives a first request message for instructing the first functional entity to determine a second functional entity for a first session between the terminal and the first data network DN. Optionally, the determining, by the first functional entity, of the second functional entity needed to be determined for the first session between the terminal and the first data network DN includes: the first functional entity determines that a second functional entity needs to be determined for a first session between the terminal device and the first data network DN upon triggering of the first request message, so that the first functional entity can determine that a second functional entity needs to be determined for a first session between the terminal device and the first data network DN by receiving the first request message. Of course, the first functional entity may also determine the second functional entity for the first session according to other trigger conditions.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the first request message includes any one of: the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, information of a second DN, information of a third functional entity, an address of the first server and an address of the second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN corresponds to the third functional entity, so that the first functional entity can determine the second functional entity needed to be determined for the first session.

With reference to any one of the first aspect to any one of the second possible implementation manners of the first aspect, in a third possible implementation manner of the first aspect, the method provided by the present application further includes: the first functional entity determines the first mapping rule information according to the mapping relation between the address of the first server and the address of the second server, and determines the first mapping rule information according to the mapping relation between the address of the first server and the address of the second server, so that the second functional entity can conveniently realize the forwarding of data in the first service, namely, the first service is accurately sent to the third functional entity. It can be understood that, the first server is a source address where the first service is located, and the second server is a server that provides a service for the first service in one of the destination data networks corresponding to the third functional entity.

With reference to the first aspect to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the first mapping rule information includes: information of the first service and information of a third functional entity associated with the first service. By configuring the association relationship between the information of the first service and the information of the third functional entity to the second functional entity, when the second functional entity receives the first service, the first service can be accurately forwarded to the third functional entity indicated by the information of the third functional entity associated with the information of the first service according to the first mapping rule information.

With reference to the first aspect to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method provided by the present application further includes: the first functional entity sends a mapping relation between the address of the first server and the address of the second server to the third functional entity, wherein the mapping relation is used 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 used 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. By sending the mapping relationship to the third functional entity, 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, acquire the first service from the data network corresponding to the second server, and map the requested address of the first service from the address of the second server to the address of the first server after acquiring the first service, so that the terminal device can accurately identify the first service.

In a second aspect, the present application provides a service offloading method, including: the fourth functional entity acquires the position information of the terminal device; and the fourth functional entity sends a first request message for indicating that a second functional entity is determined for a first session between the terminal device and the first data network DN under the condition that the fourth functional entity determines that a second data network DN serving the first service of the terminal device exists according to the position information of the terminal device, and the second functional entity is used for shunting at least one first service associated with the first session.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the first request message includes any one of the following: the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, information of a second DN, information of a third functional entity, an address of the first server and an address of the second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN is associated with the third functional entity.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the method provided by the present application further includes: and the fourth functional entity sends a second request message for indicating the position information of the reported terminal device to the terminal device.

With reference to any one of the second aspect to any one of the second possible implementation manners of the second aspect, in a third possible implementation manner of the second aspect, the method provided by the present application further includes: the fourth functional entity transmits first indication information for instructing 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 to the terminal device.

With reference to any one of the second aspect to any one of the third possible implementation manners of the second aspect, in a fourth possible implementation manner of the second aspect, the method provided by the present application further includes: and the fourth functional entity sends a mapping relation between the address of the first server and the address of the second server to the terminal device, wherein the mapping relation is used for 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, the address of the first server is a source address of the terminal device for requesting the first service, and the address of the second server is a target address of the terminal device for requesting the first service.

In a third aspect, the present application provides a method for service offloading, including: the terminal device sends the position information of the terminal device to the fourth functional entity; the terminal device receives a mapping relation which is sent by a fourth functional entity and used for indicating the address of a first server and the address of a second server, wherein the address of the first server is a source address of data in a 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; and the terminal device maps the address of the first service from the address of the first server to the address of the second server according to the first indication information.

With reference to the third aspect, in a first possible implementation manner of the third aspect, before the terminal device sends the location information of the terminal device to the fourth functional entity, the method provided by the present application further includes: and the terminal device receives a second request message which is sent by the fourth functional entity and used for indicating the terminal device to report the position information of the terminal device.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the method provided by the present application further includes: the terminal device maps the address of the first service from the address of the first server to the address of the second server, and then requests the first service based on the address of the second server.

With reference to any one of the third aspect to the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the first indication information includes: and mapping relation between the address of the first server and the address of the second server, wherein the mapping relation is used 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.

In a fourth aspect, the present application provides a method for service offloading, including: the second functional entity receives first mapping rule information which is sent by the first functional entity and used for indicating the second functional entity to send the first service to a third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of the first server to the address of the second server; and after receiving the first service, the second functional entity sends the first service to the third functional entity.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first mapping rule information includes: information of the first service and information of a third functional entity associated with the first service.

In a fifth aspect, the present application provides a method for service offloading, including: the third functional entity receives first indication information sent by the first functional entity, wherein the first indication information is used for indicating the third functional entity to realize the conversion of the address of the first service from the address of the first server to the address of the second server; and after receiving the first service, the third functional entity realizes the conversion of the address of the first service from the address of the first server to the address of the second server, wherein the first server requests the source address of the first service for the terminal device, and the second server requests the target address of the first service for the terminal device.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, 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 by the third functional entity to map an address of the first service from the address of the first server to the address of the second server, or used by the third functional entity to map an address of the first service from the address of the second server to the address of the first server.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, after receiving the first service, the third functional entity performs conversion between an address of the first service and an address of the second server, where the conversion includes: the third functional entity receives the first service sent by the terminal device, maps the address of the first service from the address of the first server to the address of the second server, or receives the first service sent by the second DN, and maps the address of the first service from the address of the second server to the address of the first server.

Correspondingly, in a sixth aspect, the present application provides a service offloading device, which may implement the service offloading method described in any one of the first aspect to the fourth possible implementation manners of the first aspect. For example, the traffic splitting apparatus may be a first functional entity, and the first functional entity may be an SMF, or a chip disposed in an SMF. Which may be implemented by software, hardware, or by hardware executing the corresponding software.

A sixth aspect of the present application, which is designed by taking the apparatus for traffic offloading as an example herein as an SMF, provides an apparatus for traffic offloading, including: a determining unit, configured to determine, when a first session between a terminal device and a first data network DN requires a second functional entity, that the first functional entity determines, for the first session, the second functional entity for offloading at least one first service included in the first session when the second functional entity needs to be determined for the first session between the terminal device and the first data network DN; a sending unit, configured to send, to a second functional entity, first mapping rule information used to instruct the second functional entity to send a first service to a third functional entity, where the third functional entity is configured to implement conversion between an address of the first service and an address of a second server from an address of the first server.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the apparatus for splitting a service provided by the present application further includes: a receiving unit, configured to receive a first request message for instructing a first functional entity to determine a second functional entity for a first session between a terminal device and a first data network DN. Optionally, the determining unit is specifically configured to determine that the first session between the terminal device and the first data network DN needs to determine the second functional entity under the trigger of the first request message.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the first request message includes any one of: the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, information of a second DN, information of a third functional entity, an address of the first server and an address of the second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN is associated with the third functional entity.

With reference to the sixth aspect to the second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the determining unit is further configured to determine the first mapping rule information according to a mapping relationship between an address of the first server and an address of the second server.

With reference to any one of the sixth aspect to the third possible implementation manner of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the first mapping rule information includes: information of the first service and information of a third functional entity associated with the first service.

With reference to any one of the sixth aspect to the fourth possible implementation manner of the sixth aspect, in a fifth possible implementation manner of the sixth aspect, the sending unit is further configured to send, to the third functional entity, a mapping relationship between an address of the first server and an address of the second server, where the mapping relationship is used by the third functional entity to map an address of the first service from the address of the first server to the address of the second server, or used by the third functional entity to map an address of the first service from the address of the second server to the address of the first server.

In addition, the present application also provides a device for service offloading, where the device for service offloading includes: the device comprises a processor and a transmitter, wherein the processor is used for determining a second functional entity for shunting at least one first service included in a first session under the condition that the first session between a terminal device and a first data network DN needs to determine the second functional entity, and the transmitter is used for sending first mapping rule information for instructing the second functional entity to send the first service to a third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of a first server to the address of a second server.

Optionally, the device for traffic offload further includes a receiver, where the receiver is configured to implement the relevant operation of message/data reception at the device side of traffic offload described in any of the first aspect to the first aspect, the transmitter is further configured to implement the relevant operation of message/data transmission at the device side of traffic offload described in any of the first aspect to the first aspect, and the processor is further configured to perform the operation of message/data processing at the device side of traffic offload described in any of the first aspect to the first aspect. Optionally, the device for service offloading in this application further includes: a bus and a memory for storing code and data, the processor, the receiver, the transmitter and the memory being connected by the bus.

In the seventh aspect, in a possible design, the traffic offloading device may be an SMF or a chip applied in the SMF, and the traffic offloading device may include at least one processor. The at least one processor is configured to execute the instructions to support the device for traffic offload to perform operations related to message processing or control performed on the device side of the traffic offload in the method described in any one of the first aspect to the fifth possible implementation manner of the first aspect. Optionally, the apparatus may further comprise a memory, coupled to the at least one processor, that stores programs (instructions) and data necessary for the apparatus. Optionally, the traffic splitting apparatus may further include a communication interface, configured to support communication between the traffic splitting apparatus and other network elements (e.g., the second functional entity and the third functional entity). The communication interface may be a transceiving circuit, where the transceiving circuit is configured to enable the device supporting the traffic offload to perform operations related to message reception and transmission on the device side of the traffic offload in the method described in any one of the first aspect to the fifth possible implementation manner of the first aspect. Optionally, the traffic splitting apparatus may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected through the bus.

In an eighth aspect, the present application provides a device for traffic offload, where the device for traffic offload may implement the method for traffic offload described in any one of the fourth possible implementation manners of the second aspect to the second aspect. For example, the device for traffic offloading may be a third functional entity, such as an AF, or a chip disposed in the AF. Which may be implemented by software, hardware, or by hardware executing the corresponding software.

Taking the service offloading device as an example, in an eighth aspect, the service offloading device includes: an acquisition unit configured to acquire position information of a terminal apparatus; a determining unit, configured to determine, according to the location information of the terminal device, that there is a second data network DN serving the first service of the terminal device; and a sending unit, configured to send, in a case where the determining unit determines that the second data network DN exists, a first request message indicating that a second functional entity is determined for a first session between the terminal device and the first data network DN, where the second functional entity is configured to offload at least one first service included in the first session.

With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, the first request message includes any one of: the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, information of a second DN, information of a third functional entity, an address of the first server and an address of the second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN is associated with the third functional entity.

With reference to the eighth aspect or the first possible implementation manner of the eighth aspect, in a second possible implementation manner of the eighth aspect, the sending unit is further configured to send, to the terminal device, a second request message for indicating to report the location information of the terminal device.

With reference to any one of the eighth aspect to the second possible implementation manner of the eighth aspect, in a third possible implementation manner of the eighth aspect, the sending unit is further configured to send, to the terminal device, first indication information used for indicating that the terminal device maps the address of the first service from the address of the first server to the address of the second server.

With reference to any one of the eighth aspect to the third possible implementation manner of the eighth aspect, in a fourth possible implementation manner of the eighth aspect, the sending unit is further configured to send, to the terminal device, a mapping relationship between an address of the first server and an address of the second server, where the mapping relationship is used for the terminal device to map an address of the first service from the address of the first server to an address of the second server, the address of the first server is a source address of the terminal device requesting the first service, and the address of the second server is a destination address of the terminal device requesting the first service.

In addition, the present application also provides a device for service offloading, where the device for service offloading includes: the processor is used for acquiring the position information of the terminal device, and the transmitter is used for sending a first request message used for indicating that a second functional entity is determined for a first session between the terminal device and the first data network DN under the condition that the determination unit determines that the second data network DN exists, wherein the second functional entity is used for shunting at least one first service associated with the first session.

Optionally, the device for traffic offload further includes a receiver, where the receiver is configured to implement the operation related to message/data reception at the device side of traffic offload described in any of the second aspect to the second aspect, the transmitter is further configured to implement the operation related to message/data transmission at the device side of traffic offload described in any of the second aspect to the second aspect, and the processor is further configured to perform the operation related to message/data processing at the device side of traffic offload described in any of the second aspect to the second aspect. Optionally, the device for service offloading in this application further includes: a bus and a memory for storing code and data, the processor, the receiver, the transmitter and the memory being connected by the bus.

In a possible design of the ninth aspect, the traffic offload device may be an AF or a chip applied in the AF, and the traffic offload device may include at least one processor. The at least one processor is configured to execute the instructions to support the device for traffic offload to perform operations related to message processing or control performed on the device side of the traffic offload in the method described in any one of the second aspect to the fourth possible implementation manner of the second aspect. Optionally, the apparatus may further comprise a memory, coupled to the at least one processor, that stores programs (instructions) and data necessary for the apparatus. Optionally, the traffic splitting apparatus may further include a communication interface, configured to support communication between the traffic splitting apparatus and other network elements (e.g., terminal apparatuses). The communication interface may be a transceiving circuit, where the transceiving circuit is configured to enable the device supporting the traffic offload to perform operations related to message reception and transmission on the device side of the traffic offload in the method described in any one of the second aspect to the fourth possible implementation manner of the second aspect. Optionally, the traffic splitting apparatus may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected through the bus.

In a tenth aspect, the present application provides a device for traffic offload, where the device for traffic offload may implement the method for traffic offload described in any one of the third to the second possible implementation manners of the third aspect. For example, the device for traffic splitting may be a terminal device or a chip disposed in the terminal device. Which may be implemented by software, hardware, or by hardware executing the corresponding software.

Taking the service offloading device as an example of a terminal, in a tenth aspect, the service offloading device includes: a transmitting unit configured to transmit position information of the terminal apparatus to the fourth functional entity; a receiving unit, configured to receive first indication information sent by the fourth functional entity, where the first indication information is used to indicate a mapping relationship between an address of a first server and an address of a second server, where the address of the first server is a source address of the terminal device requesting a first service, and the address of the second server is a destination address of the terminal device requesting the first service; and the processing unit is used for mapping 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.

With reference to the tenth aspect, in a first possible implementation manner of the tenth aspect, the receiving unit is further configured to receive a second request message, which is sent by the fourth functional entity and used for instructing the terminal device to report the location information of the terminal device.

With reference to the tenth aspect or the first possible implementation manner of the tenth aspect, in a second possible implementation manner of the tenth aspect, the processing unit provided by the present application is further configured to request the first service according to an address of the second server.

With reference to any one of the tenth aspect to the second possible implementation manner of the tenth aspect, in a third possible implementation manner of the tenth aspect, the first indication information includes: and mapping relation between the address of the first server and the address of the second server, wherein the mapping relation is used 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.

In addition, the present application also provides a device for service offloading, where the device for service offloading includes: the system comprises a transmitter and a receiver, wherein the transmitter is used for sending the position information of the terminal device to a fourth functional entity, the receiver is used for receiving first indication information which is sent by the fourth functional entity and used for indicating the mapping relation between the address of a first server and the address of a second server, the address of the first server is the source address of the terminal device for requesting the first service, the address of the second server is the target address of the terminal device for requesting the first service, and the processor is further used for mapping the address of 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.

Optionally, the processor in the traffic offload device is further configured to perform the operation of performing message/data processing on the traffic offload device side as described in any of the third to third aspects. Optionally, the transmitter is further configured to implement the device supporting traffic offloading to perform the relevant operation of message/data transmission on the device side of traffic offloading as described in any of the third aspect to the third aspect, and the receiver is further configured to implement the device supporting traffic offloading to perform the relevant operation of message/data reception on the device side of traffic offloading as described in any of the third aspect to the third aspect. Optionally, the device for service offloading in this application further includes: a bus and a memory for storing code and data, the processor, the receiver, the transmitter and the memory being connected by the bus.

In the eleventh aspect, in a possible design, the traffic splitting apparatus may be a terminal or a chip applied in the terminal, and the traffic splitting apparatus may include at least one processor. The at least one processor is configured to execute the instructions to support the device for traffic offload to perform operations related to message processing or control performed on the device side of the traffic offload in the method described in any one of the third possible implementations of the third aspect to the third aspect. Optionally, the apparatus may further comprise a memory, coupled to the at least one processor, that stores programs (instructions) and data necessary for the apparatus. Optionally, the apparatus for traffic offload may further include a communication interface, configured to support communication between the apparatus for traffic offload and another network element (e.g., a fourth functional entity). The communication interface may be a transceiving circuit, where the transceiving circuit is configured to enable the device supporting the traffic offload to perform operations related to message reception and transmission on the device side of the traffic offload in the method described in any one of the third possible implementation manners of the third aspect to the third aspect. Optionally, the traffic splitting apparatus may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected through the bus.

In a twelfth aspect, the present application provides a device for traffic offload, where the device for traffic offload may implement the method for traffic offload described in any one of the first possible implementation manners of the fourth aspect to the fourth aspect. For example, the device for traffic splitting may be a second functional entity, such as an uplink classifier, or a chip disposed in the uplink classifier. Which may be implemented by software, hardware, or by hardware executing the corresponding software.

Taking the service offloading device as the second functional entity as an example, in a twelfth aspect, the service offloading device includes: a receiving unit, configured to receive first mapping rule information, which is sent by a first functional entity and used to instruct a second functional entity to send a first service to a third functional entity, where the third functional entity is used to implement conversion between an address of the first service and an address of a second server from an address of the first server; and after receiving the first service, the second functional entity sends the first service to the third functional entity.

With reference to the twelfth aspect, in a first possible implementation manner of the twelfth aspect, the first mapping rule information includes: information of the first service and information of a third functional entity associated with the first service.

In addition, the present application also provides a device for service offloading, where the device for service offloading includes: the device comprises a transmitter and a receiver, wherein the receiver is used for receiving first mapping rule information which is sent by a first functional entity and used for indicating a second functional entity to send a first service to a third functional entity, the third functional entity is used for realizing the conversion of the address of the first service from the address of a first server to the address of a second server, and the transmitter is used for sending the first service to the third functional entity after receiving the first service.

Optionally, the traffic offload device further includes a processor configured to perform the operation of performing message/data processing on the traffic offload device side as described in any of the fourth to fourth aspects. Optionally, the transmitter is further configured to implement the device supporting traffic offload to perform the relevant operation of message/data transmission on the device side of traffic offload as described in any of the above fourth to fourth aspects, and the receiver is further configured to implement the device supporting traffic offload to perform the relevant operation of message/data reception on the device side of traffic offload as described in any of the fourth to fourth aspects. Optionally, the device for service offloading in this application further includes: a bus and a memory for storing code and data, the processor, the receiver, the transmitter and the memory being connected by the bus.

In a possible design of the thirteenth aspect, the traffic splitting apparatus may be the second functional entity or a chip applied in the second functional entity, and the traffic splitting apparatus may include at least one processor. The at least one processor is configured to execute the instructions to support the device for traffic offload to perform operations related to message processing or control performed on the device side of the traffic offload in the method described in any one of the above-mentioned fourth to fourth possible implementations. Optionally, the apparatus may further comprise a memory, coupled to the at least one processor, that stores programs (instructions) and data necessary for the apparatus. Optionally, the traffic offload apparatus may further include a communication interface for supporting communication between the traffic offload apparatus and other network elements (e.g., the first functional entity). The communication interface may be a transceiving circuit, where the transceiving circuit is configured to enable the device supporting the traffic offload to perform operations related to message reception and transmission on the device side of the traffic offload in the method described in any one of the fourth aspect to the first possible implementation manner of the fourth aspect. Optionally, the traffic splitting apparatus may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected through the bus.

In a fourteenth aspect, the present application provides a device for traffic offload, where the device for traffic offload may implement the method for traffic offload described in any one of the second possible implementation manners of the fifth aspect to the fifth aspect. For example, the traffic splitting apparatus may be a third functional entity, for example, a UPF achor, or a chip disposed in the UPF achor. Which may be implemented by software, hardware, or by hardware executing the corresponding software.

Taking the third functional entity as UPF achor as an example, the method includes: a receiving unit, configured to receive first indication information, sent by a first functional entity, for indicating a third functional entity to implement conversion between an address of a first service from an address of a first server to an address of a second server; and the processing unit is used for realizing the conversion of the address of the first service from the address of the first server to the address of the second server after receiving the first service.

With reference to the fourteenth aspect, in a first possible implementation manner of the fourteenth aspect, 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 by the third functional entity to map an address of the first service from the address of the first server to the address of the second server, or used by the third functional entity to map an address of the first service from the address of the second server to the address of the first server.

With reference to the fourteenth aspect or the first possible implementation manner of the fourteenth aspect, in a second possible implementation manner of the fourteenth aspect, the processing unit is specifically configured to receive a first service sent by the terminal device, and the third functional entity maps an address of the first service from an address of the first server to an address of the second server, or the processing unit is specifically configured to receive the first service sent by the second DN, and the third functional entity maps an address of the first service from an address of the second server to an address of the first server.

In a fifteenth aspect, in a possible design, the traffic offload device may be a third functional entity or a chip applied in the third functional entity, and the traffic offload device may include at least one processor. The at least one processor is configured to execute instructions to support the device for traffic offload to perform operations related to message processing or control performed on the device side of the traffic offload in the method described in any one of the fifth to fifth possible implementation manners of the above-mentioned aspect. Optionally, the apparatus may further comprise a memory, coupled to the at least one processor, that stores programs (instructions) and data necessary for the apparatus. Optionally, the traffic offload apparatus may further include a communication interface for supporting communication between the traffic offload apparatus and other network elements (e.g., the first functional entity). The communication interface may be a transceiving circuit, where the transceiving circuit is configured to enable the device supporting the traffic offload to perform operations related to message reception and transmission on the device side of the traffic offload in the method described in any one of the fifth aspect to the first possible implementation manner of the fifth aspect. Optionally, the traffic splitting apparatus may further include a bus, wherein the memory, the communication interface, and the at least one processor may be interconnected through the bus.

In a sixteenth aspect, the present application provides a computer-readable storage medium, which, when applied to a device for traffic offloading, has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for traffic offloading described in any one of the first aspect to the first aspect.

In a seventeenth aspect, the present application provides a computer-readable storage medium, which, when applied to a device for traffic offloading, has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for traffic offloading described in any one of the second aspect to the second aspect.

In an eighteenth aspect, the present application provides a computer-readable storage medium, which, when applied to a device for traffic offloading, has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for traffic offloading described in any one of the third to the third aspects.

In a nineteenth aspect, the present application provides a computer-readable storage medium, which when applied to a device for traffic offloading, has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for traffic offloading described in any one of the above fourth to fourth aspects.

In a twentieth aspect, the present application provides a computer-readable storage medium, which when applied to a device for traffic offloading, has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for traffic offloading described in any one of the fifth aspect to the fifth aspect.

In a twenty-first aspect, the present application provides a computer program product containing instructions, where the instructions are stored in the computer program product, and when the instructions are executed, the instructions cause a first functional entity to perform the method for traffic offload described in any one of the foregoing first aspect to the fourth possible implementation manner of the first aspect.

In a twenty-second aspect, the present application provides a computer program product containing instructions stored therein, where the instructions, when executed, cause a fourth functional entity to perform the method for traffic offload described in any one of the second to fourth possible implementation manners of the second aspect.

In a twenty-third aspect, the present application provides a computer program product containing instructions, where the instructions are stored in the computer program product, and when the instructions are executed, the terminal apparatus is caused to execute the method for traffic offloading described in any one of the fourth possible implementation manners of the third aspect to the third aspect.

In a twenty-fourth aspect, the present application provides a computer program product containing instructions stored therein, where the instructions, when executed, cause a second functional entity to perform the method for traffic offload described in any one of the fourth aspect to the first possible implementation manner of the fourth aspect.

In a twenty-fifth aspect, the present application provides a computer program product containing instructions, where the instructions are stored in the computer program product, and when the instructions are executed, the third functional entity is caused to execute the method for traffic offload described in any one of the first possible implementation manners of the fifth aspect to the fifth aspect.

In a twenty-sixth aspect, the present application provides a chip system, which is applied in a first functional entity, where 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 execute an instruction stored in the chip system, so as to execute the method for traffic splitting described in any one of the first aspect to the first aspect.

In a twenty-seventh aspect, the present application provides a chip system, which is applied in a fourth functional entity, where 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 execute an instruction to execute the method for traffic splitting according to any one of the second aspect to the second aspect.

In a twenty-eighth aspect, the present application provides a chip system, which is applied in a terminal device, where 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 execute an instruction to execute the method for traffic offloading described in any of the third aspects.

In a twenty-ninth aspect, the present application provides a chip system, which is applied in a second functional entity, where 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 execute an instruction to execute the method for service offloading described in any one of the fourth aspects.

In a thirtieth aspect, the present application provides a chip system, which is applied to a third functional entity, where 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 execute an instruction to execute the method for service offloading described in any one of the fifth aspects.

Optionally, the chip system described above in this application further includes at least one memory, where the at least one memory stores instructions.

The present application provides a communication system comprising a first functional entity as described in the sixth aspect or the sixth aspect above, a fourth functional entity as described in any of the ninth aspect or the ninth aspect, and a second functional entity as described in the twelfth aspect, and a third functional entity as described in the fourteenth aspect.

In a possible design, the system may further include another device that interacts with the fourth functional entity, the first functional entity, or the second functional entity or the third functional entity in the solution provided in the embodiment of the present invention.

Drawings

Fig. 1 is a schematic diagram of a method for traffic offloading provided in the prior art;

fig. 2 is an architecture diagram of a service offloading system provided in the present application;

fig. 3 is an architecture diagram of another service distribution system provided in the present application;

fig. 4 is a first flowchart of a service offloading method provided in the present application;

fig. 5 is a flowchart illustrating a second method for service offloading according to the present application;

fig. 6 is a schematic diagram of first mapping rule information provided in the present application;

fig. 7 is a third schematic flowchart of a service offloading method provided in the present application;

fig. 8 is a fourth schematic flowchart of a service offloading method provided in the present application;

fig. 9 is a schematic diagram of another first mapping rule information provided in the present application;

fig. 10 is a fifth flowchart of a service offloading method provided in the present application;

fig. 11 is a sixth schematic flowchart of a service offloading method provided in the present application;

FIG. 12 is a first diagram illustrating a first functional entity according to the present application;

FIG. 13 is a second schematic structural diagram of a first functional entity according to the present application;

fig. 14 is a third schematic structural diagram of a first functional entity provided in the present application;

FIG. 15 is a first diagram illustrating a fourth functional entity according to the present application;

FIG. 16 is a second schematic structural diagram of a fourth functional entity according to the present application;

fig. 17 is a third schematic structural diagram of a fourth functional entity provided in the present application;

fig. 18 is a first schematic structural diagram of a terminal device provided in the present application;

fig. 19 is a second schematic structural diagram of a terminal device according to the present application;

fig. 20 is a third schematic structural diagram of a terminal device provided in the present application;

FIG. 21 is a first schematic structural diagram of a second functional entity according to the present application;

FIG. 22 is a second block diagram of a second functional entity according to the present application;

FIG. 23 is a third schematic structural diagram of a second functional entity according to the present application;

FIG. 24 is a first diagram illustrating a third functional entity according to the present application;

FIG. 25 is a second block diagram illustrating a third functional entity according to the present application;

FIG. 26 is a third diagram illustrating a third functional entity according to the present application;

fig. 27 is a schematic structural diagram of a chip system provided in the present application.

Detailed Description

The application provides a method and a device for service distribution, which are used for solving the problem of PDU session interruption caused in a service distribution scene. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The terms "first", "second", and the like in the present application are only for distinguishing different objects, and do not limit the order thereof. For example, the first functional entity and the second functional entity are only used for distinguishing different functional entities, and the sequence order thereof is not limited.

The term "and/or" in this application is only one kind of association relationship describing the associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this application generally indicates that the former and latter related objects are in an "or" relationship.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

As shown in fig. 2, fig. 2 is a schematic diagram of an architecture of a service offloading system applied by a service offloading method provided in the present application, and as shown in fig. 2, the method includes: a first functional entity 101, a second functional entity 102, a third functional entity 103, a fourth functional entity 104 and a fifth functional entity 105.

The fourth functional entity 104 and the first functional entity 101 may communicate directly or indirectly, for example, the communication is forwarded by other functional entities, for example, the communication is forwarded by the sixth functional entity 106 shown in fig. 2 between the fourth functional entity 104 and the first functional entity 101.

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 therebetween, and the first session may be established for the first functional entity 101, so that the terminal 107 can perform traffic transmission between the data networks corresponding to the fifth functional entity 105 through the first session, for example, the first session may be a Protocol Data Unit (PDU) session.

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 send a part of the traffic in the first session to the third functional entity 103 according to the first mapping rule.

The first functional entity 101 is further configured to send the 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 for acquiring 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 a server for acquiring the first service when the first service of the terminal communicates with the destination data network, that is, the second server belongs to one server in the destination data network.

The third functional entity 103 is configured to, when receiving an uplink service sent by the terminal, convert an address of the uplink service from an address of the first server to an address of the second server and send the address, and, when receiving a downlink service sent to the terminal, convert an address of the downlink service from an address of the second server to an address of the first server and send the address.

The fourth functional entity 104 is configured to obtain the location information of the terminal 107, and determine whether a destination data network exists that better provides a service for a certain service of the terminal according to the location information of the terminal 107.

It is understood that information of at least one data network exists in the fourth functional entity 104, and the information of the data network includes information of an access address, a name, a deployed geographic location, and the like of the data network. The Data Network (DN) is an external network for providing data services.

In embodiments of the present invention, the terminals may be distributed throughout the wireless network, and each terminal may be static or mobile.

If the service offloading system is applied to a 5G network, as shown in fig. 3, a network element or an entity corresponding to the first functional entity 101 may be a Session Management Function (SMF) entity; the network element or the entity corresponding to the second functional entity 102 may be a network element that has a function of shunting a service of one session, for example, an uplink classifier (UL CL) or a branch 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 (AF), and the network element or entity corresponding to the fifth functional entity 105 may be a second UPF achor.

Wherein the third functional entity 103 is connected to the second data network via an N6 interface, and the fifth functional entity 105 is connected to the first data network via an N6 interface.

In addition, as shown in fig. 3, the 5G network may further include AN access device (e.g., AN Access Network (AN)), AN access and mobility management function (AMF) entity, a Unified Data Management (UDM) entity, AN authentication server function (AUSF) entity, a Policy Control Function (PCF) entity, and the like, which are not specifically limited in this embodiment.

The terminal communicates with the AMF entity through an N1 interface (N1 for short); the AMF entity communicates with the SMF entity over an N11 interface (N11), the SMF entity communicates with a first UPF achor and a second UPF achor over an N4 interface (N4), the first UPF achor communicates with the first DN over an N6 interface (N6), and the second UPF achor communicates with the second DN over an N6 interface (N6). The terminal accesses the network through the access device, the access device communicates with the AMF entity through an N2 interface (N2 for short), the access device communicates with the UL CL through an N3 interface (N3 for short), and the UL CL communicates with the first UPF achor and the second UPF achor through an N9 interface (N9 for short), respectively. The SMF entity communicates with the PCF entity over an N7 interface (abbreviated N7), and the PCF entity communicates with the AF over an N5 interface.

Wherein, the PCF is used to forward signaling or data of the AF to the SMF entity.

It should be noted that the interface name between each network element in fig. 3 is only an example, and the interface name may be other names in a specific implementation, which is not specifically limited in this embodiment of the present application.

It should be noted that the access device, the AMF entity, the SMF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity in fig. 3 are only names, and the names do not limit the device itself. In the 5G network and other networks in the future, the network elements or entities 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, which is not specifically limited in this embodiment of the present application. For example, the UDM entity may also be replaced by a user home server (HSS) or a User Subscription Database (USD) or a database entity, and the like, which are described herein in a unified manner and will not be described in detail below.

It should be noted that, in this application, the first session refers to a communication link established by the SMF entity and connecting between the terminal and the data network, where the communication link includes the terminal, the access device, the UPF achor, and the data network corresponding to the UPF achor. The first session may be a protocol data unit session (PDU) PDU, which is used to provide a PDU packet.

The first service or service in this application refers to at least one service flow included in the first session, where the service flow may be identified by a five-tuple, and the service flow is a PDU packet provided by the first session.

Alternatively, the terminal 107 in this application may also be referred to as a terminal equipment, User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. 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, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in a fifth-generation (5G) communication network or a terminal device in a future-evolution Public Land Mobile Network (PLMN) network, and the like.

As an example, in the embodiment of the present invention, the terminal may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

Optionally, the access device referred to in this embodiment refers to a device accessing a core network, and may be, for example, a base station, a broadband network service gateway (BNG), an aggregation switch, a non-third generation partnership project (3rd generation partnership project, 3GPP) access device, and the like. The base stations 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, etc.

Optionally, the AMF entity involved in the embodiment of the present application may also be responsible for functions such as registration management, mobility management, and lawful interception, which is not specifically limited in the embodiment of the present application.

Optionally, the SMF entity involved in this embodiment of the present application is configured to perform session management, and includes: session establishment, session modification, session release, Internet Protocol (IP) address allocation and management between networks of the terminal, selection and control of the UPF entity, lawful interception and other control functions related to the session.

Optionally, the UPF entity in this embodiment of the present application, in addition to having the function of the user plane function entity shown in fig. 3, may also implement a user plane function of a Serving Gateway (SGW) and a packet data network gateway (PGW). In addition, the UPF entity may also be a Software Defined Network (SDN) switch (switch), which is not specifically limited in this embodiment of the present application.

Optionally, the AUSF entity involved in the embodiment of the present application is configured to perform authentication and verification on the terminal based on subscription data of the terminal.

Optionally, the UDM entity referred to in the embodiments of the present application is configured to store user subscription data. In addition, the UDM entity further includes functions such as authentication, processing a user identifier, subscription management, and the like, which is not specifically limited in this embodiment of the present application.

Optionally, the PCF entity involved in the embodiment of the present application provides policy rules, and supports functions related to policies, such as unified policy framework management network behavior.

Optionally, the user plane function entity in fig. 3 may be implemented by one entity device, may also be implemented by multiple entity devices together, and may also be a logic function module in one entity device, which is not specifically limited in this embodiment of the present application.

The SMF entity is used for reallocating the UPF for the terminal according to the position information of the terminal or the characteristics of data sent by the terminal or the position between the UPF and the terminal, and the service quality of the UPF is used for reallocating the UPF for the terminal so as to reestablish the session between the terminal and the newly-allocated UPF, thereby improving the reestablished session and optimizing the user plane.

The access device is used for providing data service 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 in an actual use process. In the embodiment of the present invention, a Base Station (BS) may be a device that communicates with a User Equipment (UE) or other communication stations, such as a relay station, and the base station may provide communication coverage in a specific physical area.

PCF entity for interfacing between the radio part and the packet network (IP network).

And the AF entity is used for playing a role of influencing the route by the application.

It can be understood that, as shown in fig. 3, 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 can be sent to the second functional entity according to the association relationship between the configuration information and the first session, 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. Optionally, the second functional entity further has a second mapping rule, the second functional entity may forward the other services in the first session to a fifth functional entity according to the second mapping rule, where the configuration information is used to identify the second functional entity, and the configuration information may be an access address or an access identifier of the second functional entity, which is not limited in this application.

Since the terminal is distributed throughout the wireless network and can dynamically move throughout the wireless network, the terminal can generally perform data interaction with the source data network, for example, request a service from the source data network, through the first session after the first session between the terminal and the source data network is established. However, if the terminal moves to the range of another data network, and the data network can better provide a service for a certain service of the terminal, or when the source data network cannot meet the requirement of the certain service of the terminal, and the terminal can obtain the service from another data network, the first functional entity may determine a second functional entity for the first session, and the second functional entity is used for forwarding (also referred to as offloading) the service of the terminal, so that a certain service requested by the terminal may be forwarded to the destination data network through the second functional entity, so as to request the certain service from the destination data network. The established first session can be left uninterrupted as no IP needs to be exchanged for the terminal in the whole process.

As shown in fig. 4, a method for service offloading provided by the present application includes:

s101, in case that a first session between the terminal device and the first data network DN needs to determine a second functional entity, the first functional entity determines the second functional entity for the first session, where the first session includes at least one first service.

Optionally, the second functional entity is configured to offload at least one first service included in the first session.

Optionally, the terminal device in this application may be the terminal 107 shown in fig. 3, the first functional entity may be an SMF entity, and the second functional entity may be an uplink classifier.

Specifically, on one hand, the first functional entity in the present application may determine whether the second functional entity needs to be determined for the first session between the terminal device and the first DN according to the preset mapping rule information, and the specific mapping rule information may refer to the prior art, which is not limited in the present application. On the other hand, the first functional entity of the present application may also determine that the second functional entity needs to be determined for the first session under the trigger of the first request message sent by the fourth functional entity.

As a possible embodiment provided by the present application, as shown in fig. 5, before step S101, the method provided by the present application further includes:

s105, the fourth functional entity acquires the position information of the terminal device.

Specifically, the fourth functional entity in the present application may be an AF entity in the architecture shown in fig. 3.

S106, the fourth functional entity determines a second DN which is used for serving the first service of the terminal device according to the position information of the terminal device and the service information corresponding to the terminal device.

It is to be understood that the second DN in this application may include at least one DN from which the terminal device may request data included in the first service.

The presence of a second DN serving a first service of a terminal device in this application may be understood as meaning that the terminal device may obtain data included in the first service from the second DN.

S107, the fourth functional entity sends a first request message, where the first request message is used to instruct the first functional entity to determine a second functional entity for a first session between the terminal device and the first data network DN, and the second functional entity is used to offload at least one first service included in the first session. In an actual process, the terminal device is in a mobile state, and the first functional entity does not usually know the specific position of the terminal device, so that the first functional entity can timely shunt at least one first service in the first session by sending a first request message to the first functional entity when the fourth functional entity obtains the position information of the terminal device and determines that a second DN which can provide better service for the first service of the terminal device exists.

As a possible implementation manner, step S101 in the present application may specifically be implemented by: the first functional entity determines that a first session between the terminal device and the first data network DN requires a determination of the second functional entity upon triggering of the first request message.

Optionally, the first request message includes at least one of: the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, information of a second DN, information of a third functional entity, an address of the first server and an address of the second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the third functional entity is associated with the second DN.

The third functional entity may be the first user plane functional entity in the architecture shown in fig. 3.

The first server is one of at least one server corresponding to the first data network, a first session exists between the first data network and the terminal device, the second server is one of at least one server corresponding to the second data network, and the second data network is one data network determined by the fourth functional entity according to the position information of the terminal device.

The information of the second DN includes a data network name (DN name, DNN) and a Data Network Access Identifier (DNAI).

Optionally, in this application, determining, by the first functional entity, the second functional entity for the first session may be implemented by: the first functional entity determines the second functional entity according to the preset rule information, for example, when a second functional entity is located in the first session, the second functional entity is directly determined as the second functional entity of the first session, or the first functional entity receives a first policy sent by the PCF entity, the first policy is used to indicate information of the second functional entity, and the first functional entity determines the second functional entity according to the first policy.

It should be noted that, in this application, the second functional entity 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, in this case, 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, and based on this case, when receiving the first service of the terminal device forwarded by the access device, the second functional entity directly forwards the first service to the fifth functional entity.

Wherein, the fifth functional entity may be a second UPF achor in the architecture shown in fig. 3.

On the other hand, in the case that a first session between the terminal device and the first data network DN requires a determination of a second functional entity, the first functional entity may introduce the second functional entity into the first session, that is, the second functional entity does not exist in the first session when the first session between the terminal device and the first data network DN requires a determination of the second 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 a fifth functional entity, and a third functional entity, to establish a second functional entity and an access device, and a connection between the fifth functional entity and the third functional entity, such that upon receiving the request message for the first service from the terminal device, a request message for the first service may be sent to the second functional entity, for forwarding, 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 converts the address of the first service from the address of the first server into the address of the second server according to the mapping relation between the address of the first server and the address of the second server, and sends the address of the first service to a second DN corresponding to the third functional entity.

Specifically, the first mapping rule information in the present application may also be referred to as route forwarding rule information.

S102, the first functional entity sends first mapping rule information to the second functional entity, the first mapping rule information is used for indicating the second functional entity to send the first service to the third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of the first server to the address of the second server.

Optionally, before step S102, the method provided by the present application further includes: and the first functional entity determines first mapping rule information according to the mapping relation between the address of the first server and the address of the second server.

Specifically, the first mapping rule information in the present application may be determined by the first functional entity according to a mapping relationship between an address of the first server and an address of the second server, and on the other hand, the first mapping rule information may also be sent to the first functional entity by another device, and compared with the case where the first functional entity determines 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 functional entity directly receives the first mapping rule information, and the processing efficiency of the first functional entity may be improved.

S103, the second functional entity receives the first mapping rule information sent by the first functional entity.

And S104, after receiving the first service, the second functional entity sends the first service to the third functional entity according to the first mapping rule information.

It should be noted that, before the first functional entity does not send the first mapping rule information to the second functional entity, when the second functional entity exists in the first session, the second functional entity sends the data in the first service to the fifth functional entity after receiving the data in the first service, and after the first functional entity sends the first mapping rule information to the second functional entity, the second functional entity forwards the first service to the third functional entity after receiving the data in the first service.

Specifically, as shown in fig. 6, the first mapping rule information includes: and after receiving the first service, the second functional entity sends the first service to the third functional entity indicated by the information of the third functional entity according to the first mapping rule information.

Specifically, the information of the first service may be IP five-tuple information of the first service, for example, information of a source IP address, a source port, a destination IP address, and the like. The information of the first service included in the first mapping rule information may be an address of the second server of the first service.

The information of the third functional entity may be an identification (e.g., address, access identification, etc.) of the third functional entity, a tunnel address (tunnel ID), an access identification of the data network, etc.

In addition, optionally, the first functional entity in the present application may further send second mapping rule information to the second functional entity, where the second mapping rule information is used to instruct the second functional entity to forward the second service in the first session to a fifth functional entity, where the fifth functional entity has the first session with the terminal device.

Specifically, the second mapping rule information may be information of an origin server of the second service and information of a UPF achor corresponding to the origin server.

It should be noted that, after the first functional entity determines the second functional entity for the first session, the second functional entity, the third functional entity, and the fifth functional entity all have connections therebetween, so that the second functional entity can distribute the traffic in the first session to the fifth functional entity or the third functional entity according to the first mapping rule information.

Of course, in the present application, the first functional entity may also not send the second mapping rule information to the second functional entity, so that when the second functional entity determines that the second service sent by the terminal device is received, if it is determined that the third functional entity corresponding to the information of the second service does not exist in the first mapping rule information, the second service is forwarded to the fifth functional entity.

The application provides a method for service distribution, under the condition that a first session between a terminal device and a first data network DN needs a second functional entity, the first functional entity determines the second functional entity for the first session, and sends first mapping rule information for indicating the second functional entity to send a first service to a third functional entity, so that the second functional entity can send the first service to the third functional entity according to the first mapping rule information after receiving the first service, the third functional entity realizes the conversion of the address of the first service from the address of a first server to the address of a second server, thus the first service can be distributed when a data network which can provide better for the first service exists, and the terminal device does not need to change the target IP of the first service in the process of distributing the first service in the application, therefore, the first PDU session can be prevented from being interrupted when the first service is shunted.

Optionally, as shown in fig. 7, the method provided by the present application further includes:

s108, the first functional entity sends a mapping relation between the address of the first server and the address of the second server to the third functional entity, wherein the mapping relation is used 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 used 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.

It should be noted that, in the present application, a process in which the first functional entity sends the mapping relationship between the address of the first server and the address of the second server to the third functional entity and a process in which the first functional entity sends the first mapping rule to the second functional entity may be executed simultaneously, that is, the two processes are executed without a sequential order.

Specifically, 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 an address of the first server and an address of the second server.

S109, the third functional entity receives the mapping relation between the address of the first server and the address of the second server.

S110, when receiving a first service sent by a second functional entity, a third functional entity converts the address of the first service from the address of a first server into the address of a second server, sends the first service after the address conversion to a second data network corresponding to the second server so as to obtain the first service from the second data network corresponding to the second server, and after receiving the first service sent by the second data network corresponding to the second server, the third functional entity maps the address of the first service from the address of the second server into the address of the first server and sends the address of the first service to the second functional entity.

Illustratively, the address of the first server where the data 1 in the first service is located is IP1, 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 and sends the data 1 to the second data network, so as to obtain the data 1 from the second data network; after the third functional entity acquires data 1 from the second data network according to the IP2, the third functional entity converts the address of the data 1 from the IP2 to the IP1, and then transmits the data 1 with the address converted from the IP2 to the IP1 to the second functional entity.

As another possible embodiment of the present application, as shown in fig. 8, the method provided by the present application further includes, before step S105:

and S111, the fourth functional entity sends a second request message for indicating the position information of the reported 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 information for reporting the location information of the terminal device, and the second request message may also be a signaling message already existing between the terminal device and the fourth functional entity, and the signaling message has a field for carrying and indicating the location information of the terminal device to be reported, which is not limited in this application.

Of course, the fourth functional entity in the present application may also obtain the location information of the terminal device from other places, which is not limited in the present application.

Specifically, 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 determine the first DN for the first service of the terminal device from the at least one DN according to the location information of the terminal device and the service information of the terminal device.

S112, the terminal device receives the second request message.

S113, the terminal device transmits the location information of the terminal device to the fourth functional entity.

Alternatively, the location information of the terminal device may be information such as longitude and latitude of the terminal device, which is not limited in the present application.

As another embodiment of the present application, after data in the first service is split, in order to enable the terminal device to determine that the first service is split, in an aspect, the method provided by the present application further includes:

s114, the fourth functional entity sends first indication information to the terminal device, wherein the first indication information is used for indicating the mapping relation between the address of the first server and the address of the second server.

S115, the terminal device receives the first instruction information.

S116, the terminal device maps the address of the first service from the address of the first server to the address of the second server according to the first indication information, and requests the first service according to the address of the second server.

Specifically, 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.

In this case, the first mapping rule information sent by the second functional entity by the first functional entity may be an association between the information updated by the first service (i.e. the address of the second server) and the third functional entity, so that the second functional entity may forward the first service to the third functional entity after receiving the information updated by the first service.

Optionally, in another aspect, the present application further includes: and the fourth functional entity sends a mapping relation between the address of the first server and the address of the second server to the terminal device, wherein the mapping relation is used for 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, the address of the first server is a source address of the terminal device for requesting the first service, and the address of the second server is a target address of the terminal device for requesting the first service.

The destination address is an address of the terminal device actually requesting the first service, and the source address is an address of the terminal device originally requesting the first service.

As shown in fig. 9, when the fourth functional entity sends, to the terminal device, a message instructing 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, the first mapping rule information sent by the first functional entity to the second functional entity includes: the address of the first server of the first service is associated with the fifth functional entity, and the address of the second server of the first service is associated with the third functional entity.

It should be noted that, when steps S114 to S116 are executed, steps S108, S109 and S110 may be omitted.

In summary, as shown in fig. 10, the following detailed description describes a specific process of the service offloading method by taking the first functional entity as an SMF entity, the second functional entity as an UL CL, the third functional entity as a second UPF achor, the fourth functional entity as an AF entity, and the fifth functional entity as a first UPF achor, and taking the SMF to determine the UL CL under the trigger of the AF through the PCF, the specific process includes:

s201, the UE reports the position information of the UE to AF.

The location information of the UE may be information for determining a location of the UE, which is not limited in this application.

S202, the AF determines a second DN serving the first business of the UE according to the position information of the UE.

S203, the AF sends a first request message to the PCF.

The content of the first request message may refer to the description in the above embodiment, which is not described herein again, and in addition, the first request message may further include information of the UE and application information, where the information of the UE is used to identify the UE. The application information is used for PCF to generate corresponding rules for the type of application.

The UE information provided by the AF may be used by the PCF to generate corresponding rules for a certain UE or for a (group of) UEs.

Specifically, if there is no direct interface between the AF and the PCF, the AF interacts with the PCF through a Network Exposure Function (NEF).

S204, PCF sends a second request message to SMF.

The content of the second request message may be the same as the content of the first request message, or the PCF may process the first request message and then generate the second request message, which is not limited in the present application.

S205, determining ULCF by SMF.

S206, after determining the ULCF, the SMF sends first mapping rule information to the ULCL, and sends the association relation between the address of the first server and the address of the second server to the second UPF achor.

Specifically, the first mapping rule message is information of the first service and second UPF achor information associated with the first service.

Specifically, after step S206, the ULCL further forwards the received first service to the second UPF achor according to the first mapping rule information, and after receiving the first service sent by the second UPF achor and requested according to the address of the second server, and changing the address of the received first service from the address of the second server to the address of the first server by the second UPF achor, sending the first service with the address changed to the address of the first server to the ULCL, so as to send the ULCL to the UE through the access device.

As shown in fig. 11, fig. 11 shows a specific flow of another service offloading method provided in the present application, and as a difference between fig. 11 and fig. 10, steps S207 and S208 are added in fig. 11, and a process of sending, by the SMF, an association relationship between an address of the first server and an address of the second server to the second UPF achor in step S205 is omitted. However, the first mapping rule information sent by the SMF to the ULCL in step S205 is the IP five-tuple 1 and the first UPF achor information associated with the first service, and the IP five-tuple 2 and the second UPF achor information associated with the first service, so that the ULCL entity can forward the service of the IP five-tuple 1 to the first UPF achor after receiving the service of the IP five-tuple 1, and can forward the service of the IP five-tuple 2 to the second UPF achor after receiving the service of the IP five-tuple 2.

S207, the AF sends, to the UE, a mapping relationship between an address of the first server and an address of the second server, or sends first indication information, where the first indication information is used to indicate the UE to map an address of data in the first service from the address of the first server to the address of the second server.

S208, the UE maps the address of the first service from the address of the first server to the address of the second server and requests the first service according to the address of the second server.

The application provides a method for traffic offloading, in case a first session between a terminal device and a first data network DN needs to determine a second functional entity, the first functional entity determines the second functional entity for the first session, and transmitting first mapping rule information for instructing the second functional entity to transmit the first service to the third functional entity to the second functional entity, thus, after the second functional entity receives the first service, the first service can be sent to the third functional entity according to the first mapping rule information, the third functional entity realizes the conversion of the address of the first service from the address of the first server to the address of the second server, therefore, the first service can be shunted when a data network which can provide better for the first service exists, and the first PDU session can be prevented from being interrupted when the first service is shunted.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that 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, includes a hardware structure and/or a software module corresponding to each function for implementing the above functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, according to the above method, the first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the terminal device may be divided into functional modules, for example, the functional modules may be divided corresponding to the functions, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. The following description will be given by taking the division of each function module corresponding to each function as an example:

in case of integrated units, fig. 12 shows a possible schematic structural diagram of the first functional entity involved in the above embodiment. The first functional entity comprises: determining unit 101 and transmitting unit 102. Wherein, the determining unit 101 is configured to support the first functional entity to perform steps S101 and S205 in the foregoing embodiment; the sending unit 102 is configured to support the first functional entity to perform steps S102, S108 and S206 in the foregoing embodiment. Furthermore, the first functional entity may further comprise a receiving unit 103, and the receiving unit 103 is configured to support the first functional entity to execute step S109 in the foregoing embodiment. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Based on the hardware implementation, the sending unit 102 in this 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 to function as a transceiver, a specific transceiver may also be referred to as a communication interface or a transceiver circuit, and the determining unit 101 may be integrated on a processor of the first functional entity.

In case of integrated units, fig. 13 shows a schematic diagram of a possible logical structure of the first functional entity involved in the above embodiments. The first functional entity comprises: a processing module 112 and a communication module 113. The processing module 112 is used for controlling and managing actions of the first functional entity, for example, the processing module 112 is used for executing steps of message or data processing on the first functional entity side, for example, supporting the first functional entity to execute steps S101 and S205 in the above embodiments; the communication module 113 is configured to support the first functional entity to perform steps S102, S108, S206, and S109 in the foregoing embodiments. And/or other processes performed by the first functional entity for the techniques described herein. Optionally, the first functional entity may further comprise a storage module 111 for storing program codes and data of the first functional entity.

The processing module 112 may be a processor or 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, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module 113 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 111 may be a memory.

When the processing module 112 is the processor 120, the communication module 113 is the communication interface 130 or the transceiver, and the storage module 111 is the memory 140, the first functional entity referred to in this application may be the device shown in fig. 14.

Wherein the communication interface 130, the at least one processor 120, and the memory 140 are connected to each other through the bus 110; the bus 110 may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 14, but this is not intended to represent only one bus or type of bus. Wherein the memory 140 is used for storing program codes and data of the first functional entity. The communication interface 130 is used to support the first functional entity to communicate with other devices (e.g., a second functional entity), and the processor 120 is used to support the first functional entity to execute the program codes and data stored in the memory 140 to implement a method of traffic offload provided by the present application.

In case of integrated units, fig. 15 shows a possible schematic structure of the fourth functional entity involved in the above embodiments. The fourth functional entity comprises: an acquisition unit 201, a determination unit 202, and a transmission unit 203. The obtaining unit 201 is configured to support a fourth functional entity to execute step S105 in the foregoing embodiment; the determining unit 202 is configured to support the fourth functional entity to perform steps S106 and S202 in the foregoing embodiment, wherein the sending unit 203 is configured to support the fourth functional entity to perform steps S107, S111, S114, S203 and S207 in the foregoing embodiment. Additionally, and/or other processes for the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Based on the hardware implementation, the acquiring unit 201 in this application may be a receiver of a fourth functional entity, the sending unit 203 may be a transmitter of the fourth functional entity, the transmitter may be generally integrated with the receiver of the fourth functional entity to serve as a transceiver, a specific transceiver may also be referred to as a communication interface, or a transceiver circuit, and the determining unit 202 may be integrated on a processor of the fourth functional entity.

In case of integrated units, fig. 16 shows a schematic diagram of a possible logical structure of the fourth functional entity involved in the above embodiments. A fourth functional entity comprising: a processing module 212 and a communication module 213. The processing module 212 is configured to control and manage actions of the fourth functional entity, for example, the processing module 212 is configured to support the fourth functional entity to perform operations of performing message or data processing on the fourth functional entity side in the foregoing embodiments, for example, to perform steps S106 and S202 in the foregoing embodiments; the communication module 213 is used to support the fourth functional entity to perform the operations of receiving and sending messages or data on the fourth functional entity side in the above embodiments, for example, steps S105, S107, S111, S114, S203 and S207 in the above embodiments. And/or other processes performed by a fourth functional entity for the techniques described herein.

Optionally, 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 may be a processor or 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, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module 213 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 211 may be a memory.

When the processing module 212 is the processor 220, the communication module 213 is the communication interface 230 or the transceiver, and the storage module 211 is the memory 210, the fourth functional entity involved in the present application may be the device shown in fig. 17.

Wherein the communication interface 230, the at least one processor 220, and the memory 210 are connected to each other through the bus 200; the bus 200 may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 17, but this does not mean only one bus or one type of bus. Wherein the memory 210 is used for storing program codes and data of the fourth functional entity. The communication interface 230 is used for supporting the fourth functional entity to communicate with other devices (e.g., terminal apparatuses), and the processor 220 is used for supporting the fourth functional entity to execute the program codes and data stored in the memory 210 to implement a method of traffic offloading provided by the present application.

Fig. 18 shows a schematic diagram of a possible structure of the terminal device according to the above-described embodiment, in the case of an integrated unit. The terminal device includes: a transmitting unit 301, a receiving unit 302, and a processing unit 303. Wherein, the receiving unit 302 is configured to support the terminal device to perform steps S112 and S115 in the foregoing embodiment; the transmitting unit 301 is configured to support the terminal device to execute steps S113 and S201 in the foregoing embodiments, and the processing unit 303 is configured to support the terminal device to execute steps S116 and S208 in the foregoing embodiments. And/or other processes for the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Based on the hardware implementation, the receiving unit 302 in this application may be a receiver of the terminal device, and the transmitting unit 301 may be a transmitter of the terminal device, and the receiver may be integrated with the transmitter of the terminal device to be used as a transceiver, and the transceiver may also be referred to as a communication interface or a transceiver circuit.

In the case of an integrated unit, fig. 19 shows a schematic diagram of a possible logical structure of the terminal device according to the above-described embodiment. The terminal device includes: a processing module 312 and a communication module 313. The processing module 312 is configured to control and manage the actions of the terminal device, for example, the processing module 312 is configured to support the terminal device to perform operations of performing message or data processing on the terminal device side in the foregoing embodiments, for example, steps S116 and S208 in the foregoing embodiments; the communication module 313 is used to support the terminal device to perform operations of receiving or transmitting messages or data on the terminal device side in the above embodiments, for example, steps S112, S115, S113, and S201 in the above embodiments. And/or other processes performed by a terminal device for the techniques described herein.

Optionally, the terminal device may further include a storage module 311 for storing program codes and data of the terminal device.

The processing module 312 may be a processor or 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, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module 313 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 311 may be a memory.

When the processing module 312 is the processor 320, the communication module 313 is the communication interface 330 or the transceiver, and the storage module 311 is the memory 310, the terminal device according to the present application may be the apparatus shown in fig. 20.

Wherein 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, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 20, but this is not intended to represent only one bus or type of bus. The memory 310 is used for storing program codes and data of the terminal device, among others. The communication interface 330 is used for supporting the terminal device to communicate with other devices (e.g., a fourth functional entity), and the processor 320 is used for supporting the terminal device to execute the program codes and data stored in the memory 310 to implement a method of traffic offload provided by the present application.

In case of integrated units, fig. 21 shows a possible schematic structural diagram of the second functional entity involved in the above embodiment. The second functional entity comprises: a receiving unit 401 and a transmitting unit 402. Wherein, the receiving unit 401 is configured to support the second functional entity to execute step S103 in the foregoing embodiment; the sending unit 402 is configured to support the second functional entity to execute step S104 in the foregoing embodiment. And/or other processes for the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Based on the hardware implementation, the receiving unit 401 in this application may be a receiver of the second functional entity, and the transmitting unit 402 may be a transmitter of the second functional entity, and the receiver may be generally integrated with the transmitter of the second functional entity to be used as a transceiver, and a specific transceiver may also be referred to as a communication interface or a transceiver circuit.

In case of integrated units, fig. 22 shows a schematic diagram of a possible logical structure of the second functional entity involved in the above embodiments. The second functional entity comprises: a processing module 412 and a communication module 413. The processing module 412 is configured to control and manage an action of the second functional entity, for example, the processing module 412 is configured to support the second functional entity to perform an operation of performing message or data processing on the second functional entity side in the foregoing embodiment; the communication module 413 is configured to support the second functional entity to perform operations of receiving or sending messages or data on the side of the second functional entity in the foregoing embodiments, for example, steps S103 and S104 in the foregoing embodiments. And/or other processes performed by a second functional entity for the techniques described herein.

Optionally, the second functional entity may further include a storage module 411 for storing program codes and data of the second functional entity.

The processing module 412 may be a processor or 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, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module 413 may be a transceiver, a transceiving circuit, a communication interface, or the like. The storage module 411 may be a memory.

When the processing module 412 is the processor 420, the communication module 413 is the communication interface 430 or the transceiver, and the storage module 411 is the memory 410, the second functional entity referred to in this application may be the device shown in fig. 23.

Wherein 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, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 23, but it is not intended that there be only one bus or one type of bus. Wherein the memory 410 is used for storing program codes and data of the second functional entity. The communication interface 430 is used to support the second functional entity to communicate with other devices (e.g., the first functional entity and the third functional entity), and the processor 420 is used to support the second functional entity to execute the program codes and data stored in the memory 410 to implement a service offloading method provided by the present application.

In the case of integrated units, fig. 24 shows a possible schematic structural diagram of the third functional entity involved in the above-described embodiment. The third functional entity comprises: a receiving unit 501 and a processing unit 502. Wherein, the receiving unit 501 is configured to support the third functional entity to execute step S109 in the foregoing embodiment; the processing unit 502 is configured to support the third functional entity to execute step S110 in the foregoing embodiment. And/or other processes for the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Based on the hardware implementation, the receiving unit 501 in this application may be a receiver of the third functional entity, and the receiver may be integrated with a transmitter of the third functional entity to be used as a transceiver, and the transceiver may also be referred to as a communication interface or a transceiver circuit.

In case of integrated units, fig. 25 shows a schematic diagram of a possible logical structure of the third functional entity involved in the above embodiments. The third functional entity comprises: a processing module 512 and a communication module 513. The processing module 512 is configured to control and manage actions of the third functional entity, for example, the processing module 512 is configured to support the third functional entity to perform operations of performing message or data processing on the third functional entity side in the foregoing embodiments; the communication module 513 is configured to support the third functional entity to perform operations of receiving or sending messages or data on the third functional entity side in the foregoing embodiments, for example, steps S109 and S110 in the foregoing embodiments. And/or other processes performed by a third functional entity for the techniques described herein.

Optionally, the third functional entity may further include a storage module 511, configured to store program codes and data of the third functional entity.

The processing module 512 may be a processor or 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, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module 513 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 511 may be a memory.

When the processing module 512 is a processor 520, the communication module 513 is a communication interface 530 or a transceiver, and the storage module 511 is a memory 510, the third functional entity involved in the present application may be the device shown in fig. 26.

Wherein the communication interface 530, the at least one processor 520, and the memory 510 are connected to each other through the bus 500; the bus 500 may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 26, but this does not indicate only one bus or one type of bus. Wherein the memory 510 is used for storing program codes and data of the third functional entity. The communication interface 530 is used for supporting the third functional entity to communicate with other devices (e.g., the first functional entity), and the processor 520 is used for supporting the third functional entity to execute the program codes and data stored in the memory 510 to implement a method of traffic offload provided by the present application.

The above receiving unit (or unit for receiving) is an interface circuit of the apparatus for receiving signals from other apparatuses. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The above transmitting unit (or a unit for transmitting) is an interface circuit of the apparatus for transmitting a signal to other apparatuses. For example, when the device is implemented in the form of a chip, the transmitting unit is an interface circuit for the chip to transmit 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.

Optionally, the system-on-chip 150 also includes a memory 1540, which may include both read-only memory and random access memory, and provides operating instructions and data to the processor 1510. A portion of memory 1540 may also include non-volatile random access memory (NVRAM).

In some embodiments, memory 1540 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:

in the embodiment of the present invention, by calling an operation instruction stored in the memory 1540 (the operation instruction may be stored in an operating system), a corresponding operation is performed.

One possible implementation is: the 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 realize respective functions.

The processor 1510 controls operations of the first functional entity, the second functional entity, the third functional entity, the fourth functional entity, and the terminal, and the processor 1510 may also be referred to as a Central Processing Unit (CPU). Memory 1540 can include both 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). In a particular implementation, memory 1540, interface circuit 1530, and memory 1540 are coupled together by a bus system 1520, where bus system 1520 may include a power bus, a control bus, a status signal bus, and so forth, in addition to a data bus. For clarity of illustration, however, the various buses are labeled in FIG. 27 as the bus system 1520.

The method disclosed in the above 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 having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1510. The processor 1510 may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. 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 the hardware thereof.

Optionally, the interface circuit 1530 is configured to perform the steps of receiving and transmitting of the first functional entity, the second functional entity, the third functional entity, the fourth functional entity and the terminal device in the embodiments shown in fig. 4, fig. 5, fig. 7, fig. 8, fig. 10 and fig. 11.

The processor 1510 is configured to perform the steps of the processing of the first functional entity, the second functional entity, the third functional entity, the fourth functional entity and the terminal device in the embodiments shown in fig. 4, fig. 5, fig. 7, fig. 8, fig. 10 and fig. 11.

In the above embodiments, 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 the form of software and installed in the memory.

The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, e.g., the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. A computer-readable storage medium may be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

In one aspect, a computer storage medium is provided, in which instructions are stored, which 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.

In a further aspect, there is provided a computer storage medium having stored therein instructions that, when executed, cause a fourth functional entity to perform steps S106 and S202, S105, S107, S111, S114, S203 and S207 in embodiments. And/or other processes performed by a fourth functional entity for the techniques described herein.

On the other hand, there is provided a computer storage medium having stored therein instructions that, when executed, cause a terminal apparatus to execute S116 and S208, S112, S115, S113, and S201 in the embodiment. And/or other terminal-performed processes for the techniques described herein.

In yet another aspect, a computer storage medium is provided, in which instructions are stored, and when executed, the instructions cause a second functional entity to perform S103 and S104 in the embodiment. And/or other processes performed by a second functional entity for the techniques described herein.

On the other hand, a computer storage medium is provided, in which instructions are stored, and when executed, the instructions cause a third functional entity to execute S109 and S110 in the embodiment. And/or other processes performed by a third functional entity for the techniques described herein.

In one aspect, a computer program product is provided that includes instructions stored therein, which 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.

In yet another aspect, a computer program product is provided, which comprises instructions stored therein, which when executed, cause a fourth functional entity to perform steps S106 and S202, S105, S107, S111, S114, S203 and S207 in the embodiments. And/or other processes performed by a fourth functional entity for the techniques described herein.

On the other hand, a computer program product is provided, which comprises instructions stored therein, which when executed, cause the terminal to perform steps S116 and S208, S112, S115, S113 and S201 in the embodiments. And/or other processes performed by a terminal device for the techniques described herein.

In yet another aspect, a computer program product is provided, comprising instructions stored therein, which when executed, cause a second functional entity to perform S103 and S104 in an embodiment. And/or other processes performed by a second functional entity for the techniques described herein.

On the other hand, a computer program product containing instructions is provided, and the instructions stored in the computer program product, when executed, cause the third functional entity to execute S109 and S110 in the embodiment. And/or other processes performed by a third functional entity for the techniques described herein.

In one aspect, a chip system applied in a first functional entity is provided, where 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 execute instructions to perform S101, S205, S102, S108, S206, and S109 in the embodiments. And/or other processes performed by the first functional entity for the techniques described herein.

In another aspect, a chip system applied in the fourth functional entity is provided, where 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 execute instructions to perform steps S106, S202, S105, S107, S111, S114, S203, and S207 in the embodiments. And/or other processes performed by a fourth functional entity for the techniques described herein.

In another aspect, a chip system is provided, where the chip system is applied in a terminal, and the chip system includes at least one processor and an interface circuit, where the interface circuit and the at least one processor are interconnected by a line, and the processor is configured to execute instructions to perform S116, S208, S112, S115, S113, and S201 in the embodiment. And/or other processes performed by a terminal device for the techniques described herein.

In another aspect, a chip system applied in the second functional entity is provided, where 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 execute instructions to perform S103 and S104 in the embodiment. And/or other processes performed by a second functional entity for the techniques described herein.

In another aspect, a chip system applied in the third functional entity is provided, where 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 execute instructions to perform S109 and S110 in the embodiment. And/or other processes performed by a third functional entity for the techniques described herein.

In addition, the present application also provides a system for traffic offload, where the system for traffic offload includes a first functional entity shown in fig. 12 to 14, a fourth functional entity shown in fig. 15 to 17, a terminal device shown in fig. 18 to 20, a second functional entity shown in fig. 21 to 23, and a third functional entity shown in fig. 24 to 26.

The application provides a service shunting system, under the condition that a first session between a terminal device and a first data network DN needs to determine a second functional entity, the first functional entity determines the second functional entity for the first session, and sends first mapping rule information for instructing the second functional entity to send data in the first service to a third functional entity, so that the second functional entity can send the data in the first service to the third functional entity according to the first mapping rule information after receiving the data in the first service, and the third functional entity realizes the conversion of the address of the data in the first service from the address of a first server to the address of a second server, thereby shunting the data in the first service when a better data network exists for providing the data in the first service, and the first PDU session can be prevented from being interrupted when the data in the first service is shunted.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for traffic offload, comprising:

under the condition that a first session between a terminal device and a first Data Network (DN) needs a second functional entity, the first functional entity determines the second functional entity for the first session, and the first session comprises at least one first service;

the first functional entity sends first mapping rule information to the second functional entity, the first mapping rule information is used for indicating the second functional entity to send the first service to a third functional entity, and the third functional entity is used for realizing the conversion of the address of the first service from the address of a first server to the address of a second server.

2. The method of claim 1, comprising:

the first functional entity receives a first request message indicating that the first functional entity needs to determine the second functional entity for the first session between the terminal device and the first data network DN.

3. The method of claim 2, wherein the first request message comprises at least one of:

the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, the information of the second DN, the information of the third functional entity, an address of a first server and an address of a second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN is associated with the third functional entity.

4. The method of claim 3, further comprising:

and the first functional entity determines the first mapping rule information according to the mapping relation between the address of the first server and the address of the second server.

5. The method of claim 4, wherein the first mapping rule information comprises: information of the first service and information of the third functional entity associated with the first service.

6. The method according to any one of claims 1-5, further comprising:

the first functional entity sends a mapping relation between an address of a first server and an address of a second server to the third functional entity, wherein the mapping relation is used 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 used 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.

7. The method according to claim 1, wherein before the first functional entity sends the first mapping rule information to the second functional entity, the second functional entity sends the received data in the first service to a fifth functional entity.

8. The method of claim 1, wherein the first functional entity is a session management functional entity, the second functional entity is an uplink classifier, and the third functional entity is a first user plane function anchor.

9. The method of claim 7, wherein the first functional entity is a session management functional entity, the second functional entity is an uplink classifier, the third functional entity is a first user plane function anchor, and the fifth functional entity is a second user plane function anchor.

10. A service offloading method, comprising:

the fourth functional entity acquires the position information of the terminal device;

the fourth functional entity sends a first request message when determining that a second data network DN serving a first service of the terminal device exists according to the position information of the terminal device, wherein the first request message is used for indicating that a second functional entity is determined for a first session between the terminal device and the first data network DN, and the second functional entity is used for shunting at least one first service included in the first session;

wherein the method further comprises:

the fourth functional entity sends a mapping relationship between an address of a first server and an address of a second server to the terminal device, where the mapping relationship is used for 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, the address of the first server is a source address of the terminal device requesting the first service, and the address of the second server is a destination address of the terminal device requesting the first service.

11. The method of claim 10, wherein the first request message comprises any one of:

the first server is used for indicating that a mapping relation exists among information of a second data network DN serving the first service, the information of the second DN, information of a third functional entity, an address of a first server and an address of a second server, wherein the address of the first server is a source address of the terminal device requesting the first service, the address of the second server is a target address of the terminal device requesting the first service, and the second DN is associated with the third functional entity.

12. The method according to claim 10 or 11, characterized in that the method further comprises:

and the fourth functional entity sends a second request message for indicating the reporting of the position information of the terminal device to the terminal device.

13. The method of claim 11, further comprising:

and the fourth functional entity sends first indication information to the terminal device, wherein the first indication information is used for indicating 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.

14. An apparatus for traffic offloading, comprising:

a determining unit, configured to determine a second functional entity for a first session between a terminal device and a first data network DN, the first session including at least one first service, in case the first session requires the second functional entity;

a sending unit, configured to send first mapping rule information to the second functional entity, where the first mapping rule information is used to instruct the second functional entity to send the first service to a third functional entity, and the third functional entity is used to implement conversion between an address of the first service and an address of a second server from an address of the first server.

15. The apparatus of claim 14, further comprising:

a receiving unit, configured to receive a first request message, where the first request message is used to indicate that a first functional entity needs to determine a second functional entity for the first session between the terminal device and the first data network DN.

16. The apparatus of claim 15, wherein the first request message comprises at least one of:

17. The apparatus according to claim 16, wherein the determining unit is further configured to determine the first mapping rule information according to a mapping relationship between an address of the first server and an address of a second server.

18. The apparatus of claim 17, wherein the first mapping rule information comprises: information of the first service and information of the third functional entity associated with the first service.

19. The apparatus according to any one of claims 14 to 17, wherein the sending unit is further configured to send, to the third functional entity, a mapping relationship between an address of a first server and an address of a second server, where the mapping relationship 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 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.

20. A traffic splitting apparatus, comprising:

an acquisition unit configured to acquire position information of a terminal apparatus;

a determining unit, configured to determine, according to the location information of the terminal device, that there is a second data network DN serving a first service of the terminal device;

a sending unit, configured to send a first request message when the determining unit determines that the second data network DN exists, where the first request message is used to indicate that a second functional entity is determined for a first session between the terminal device and a first data network DN, and the second functional entity is used to offload at least one first service included in the first session;

the sending unit is further configured to send, to the terminal device, a mapping relationship between an address of a first server and an address of a second server, where the mapping relationship is used for 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, the address of the first server is a source address of the terminal device requesting the first service, and the address of the second server is a destination address of the terminal device requesting the first service.

21. The apparatus of claim 20, wherein the first request message comprises any one of:

22. The apparatus according to claim 20 or 21, wherein the sending unit is further configured to send a second request message to the terminal apparatus, where the second request message is used to instruct reporting of the location information of the terminal apparatus.

23. The apparatus of claim 20, wherein the sending unit is further configured to send, to the terminal apparatus, first indication information, where the first indication information is used to instruct the terminal apparatus to map an address of the first service from an address of the first server to an address of the second server.

24. A computer-readable storage medium applied to a traffic offload device, wherein the computer-readable storage medium stores instructions that, when executed, cause the traffic offload method according to any of claims 1-9 or any of claims 10-13 to be performed.

25. A chip system, for use in a device for traffic offload, 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, and the processor being configured to execute instructions to perform the method for traffic offload according to any one of claims 1 to 9 or any one of claims 10 to 13.