WO2018119595A1 - Method, device and system for shunting between fixed network device and mobile network device - Google Patents

Abstract

Disclosed in the present invention are a method and device for shunting between a fixed network device and a mobile network device, the method and the device are applied to a system supporting the non-3rd generation partnership project (non-3GPP) access technology to access a core network. By means of the method of the present invention, a data stream to be sent to the mobile network device is sent to the fixed network device from a core network, thereby avoiding the instability of transmitting the data stream by means of a direct connection (such as Bluetooth technology) between the mobile network device and the fixed network device, and improving the quality of service.

Description

Method, device and system for shunting between fixed network equipment and mobile network equipment Technical field

The present invention relates to the field of communications technologies, and in particular, to a method, device, and system for offloading between a fixed network device and a mobile network device.

Background technique

In order to meet the challenges of wireless broadband technology, the communication field has developed and developed a next-generation mobile communication system (next generation system) network architecture, called the fifth generation (5rd generation, 5G) network architecture. The architecture not only supports wireless technology access to the 5G core network, but also supports the non-3rd generation partnership project (non-3GPP) access technology to access the 5G core network. The core network function of the 5G core network is divided into a user plane (UP) function and a control plane (CP) function. The UP function entity is mainly responsible for packet data packet forwarding, quality of service (QoS) control, accounting information statistics, and reporting to the CP. The CP function entity is mainly responsible for sending a packet forwarding policy and a QoS control policy to the UP.

In the prior art, a mobile network device (such as a user equipment, a UE) can directly establish a connection with a fixed network device through an application layer and a Bluetooth technology, and implement a traffic distribution between the fixed network device and the UE through a connection with the fixed network device. For example, the UE detects available fixed network devices based on the Bluetooth technology, such as a TV TV, an audio device, etc., and establishes a connection between the UE and the fixed network device. The data stream is then first sent to the UE and the user clicks on the available fixed network device. The UE sends the data stream to the fixed network device selected by the user based on the fixed network device selected by the user, so as to implement the movement of the data stream between the UE and the fixed network device.

However, due to network problems, the shunting of the connection between the mobile network device and the fixed network device cannot ensure the quality of the shunt transmission and transmission is stable, resulting in low service quality.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a system for offloading between a fixed network device and a mobile network device, so as to at least solve the technical problem that the service quality caused by the offloading of the mobile network device and the fixed network device is not high.

To achieve the above objective, the embodiments of the present invention provide a system solution for supporting a non-3rd generation partnership plan non-3GPP access technology to access a core network. Specifically, the control plane CP function entity receives the identifier of the mobile network device and the identifier of the fixed network device sent by the non-3rd generation partnership plan non-3GPP access gateway. Wherein the mobile network device and the fixed network device have the same access point. Then, the CP function entity obtains the description information of the service that allows the traffic distribution according to the identifier of the mobile network device, and sends a traffic distribution request to the traffic distribution device, where the traffic distribution request includes the description information of the service that allows the traffic distribution, the identifier of the mobile network device, and the The identifier of the network device. Then, the offloading device receives a downlink data stream that is sent to the mobile network device, and the downlink data stream belongs to the data stream of the service described by the description information of the traffic that allows the offloading. The offloading device then sends the downlink data stream to the fixed network device according to the identifier of the fixed network device. Through the above method, the data stream sent to the mobile network device can be sent from the core network to the fixed network device, thereby avoiding instability of the data stream transmitted between the mobile network device and the fixed network device through direct connection (such as Bluetooth technology). Sex, improve the quality of business.

In a possible design, the CP function entity may further send a subscription request to the offloading device before sending the offloading request to the offloading device, where the subscription request includes the identifier of the mobile network device and the mobile network device subscription Description of the business. Then, the traffic distribution device determines, according to the description information of the service that is subscribed to by the mobile network device, that the service corresponding to the data flow that is being sent to the mobile network device belongs to the service description information of the service that is signed by the mobile network device; The offloading device returns a subscription response to the CP functional entity. The subscription response includes the identifier of the mobile network device and the description information of the service corresponding to the data flow that is being sent to the mobile network device, where the description information of the service that allows the offloading is sent to the mobile Description information of the service corresponding to the data flow of the network device. Therefore, the CP function can determine that the service corresponding to the data stream sent to the mobile network device is a traffic that allows the traffic to be offloaded, and then triggers the traffic distribution by using the traffic distribution request. Make the shunt method more flexible.

In a possible design, the offloading device may be the non-3GPP access gateway or the user plane UP functional entity, thereby providing a flexible and technical solution to facilitate different network layouts.

In a possible design, the control plane CP functional entity receives the identity of the mobile network device and the identity of the fixed network device sent by the non-3rd generation partnership plan non-3GPP access gateway, the non-3GPP interface The ingress gateway obtains the identifier of the fixed network device and the identifier of the mobile network device, so as to ensure that the CP functional entity successfully triggers the offloading.

In a possible design, before the non-3GPP access gateway acquires the identifier of the fixed network device and the identifier of the mobile network device, establishing a connection between the fixed network device and the non-3GPP access gateway. After the non-3GPP access gateway acquires the identifier of the fixed network device and the identifier of the access point of the fixed network device, the non-3GPP access gateway stores the identifier of the fixed network device and Correspondence relationship with the identifier of the access point of the fixed network device. Therefore, when the user uses the service, the later user can use the information according to the stored information.

In a possible design, after the non-3GPP access gateway stores the identifier of the fixed network device and the identifier of the access point of the fixed network device, the non-3GPP access gateway The obtaining the identifier of the fixed network device and the identifier of the mobile network device is specifically: the non-3GPP access gateway receives a session request sent by the mobile network device. Then, the non-3GPP access gateway acquires an identifier of the mobile network device and an identifier of an access point of the mobile network device according to the session request. Then, the non-3GPP access gateway obtains the correspondence between the identifier of the stored fixed network device and the identifier of the access point of the fixed network device according to the identifier of the access point of the mobile network device. The mobile network device has the identity of the fixed network device of the same access point. Thereby, the identification of the fixed network device and the identification of the mobile network device can be obtained by different methods.

In a possible design, the non-3GPP access gateway obtains the identifier of the fixed network device, and the identifier of the mobile network device is: the non-3GPP access gateway receives the session request sent by the mobile network device. The session request includes an identifier of the mobile network device and an identifier of the fixed network device. Thereby, the identification of the fixed network device and the identification of the mobile network device can be obtained by different methods.

In a possible design, the non-3GPP access gateway further obtains the type of the fixed network device according to the identifier of the fixed network device, and stores the correspondence between the identifier and the type of the fixed network device.

In a possible design, the session request further includes an identifier of an access point of the mobile network device; the non-3GPP access gateway further receives an establishment session sent by the CP function entity The request to establish a session includes an identifier of a fixed network device included in the session request and an identifier of an access point of the mobile network device; and then the non-3GPP access gateway performs the function to the CP The entity sends a response to establish a session, where the response to the establishment of the session includes an identifier of the fixed network device that is successfully registered in the access point corresponding to the access point identifier included in the session request.

In a possible design, before the CP function entity acquires the service description information of the service that allows the offloading, the CP function entity further sends a policy request to the policy entity, where the policy request includes the identifier of the mobile network device; Receiving a policy response sent by the policy entity, where the policy response includes the offloading policy information subscribed by the mobile network device, where the offloading policy information includes description information of the service subscribed by the mobile network device.

In a possible design, before the CP function entity sends the policy request to the policy function entity, the CP function entity further receives a session modification request sent by the mobile network device, where the session modification request includes the The identifier of the mobile network device, the identifier of the fixed network, and the description information of the service corresponding to the data stream being sent to the mobile network device;

The description information of the service that the CP function entity obtains the traffic that is allowed to be offloaded is specifically: the policy request includes the description information of the service corresponding to the data flow of the mobile network device, and the service that the CP function entity subscribes according to the mobile network device The description information determines that the description information of the corresponding service of the data stream that is being sent to the mobile network device is the description information of the service that allows the offloading.

In a possible design, the CP function entity further acquires the type of the fixed network device, where the offload request further includes a type of the fixed network device, and the offload policy information further includes a type corresponding to the solid device type. a quality of service QoS parameter; or the CP function entity acquires the type of the fixed network device, where the policy response includes a QoS parameter corresponding to each fixed network device type subscribed by the mobile network device, and the CP functional entity is configured according to And the QoS parameters corresponding to the type of the fixed network device included in the session are obtained by the QoS parameters corresponding to the type of the fixed network device that are subscribed by the mobile network device. Through the QoS parameters, the offloading device can be controlled based on the QoS parameters in the process of offloading, further ensuring the quality of data transmission.

In a possible design, the CP function entity obtains a quality of service QoS parameter corresponding to the type of the fixed network device, where the policy request further includes the type of the fixed network device, where the policy The response further includes a QoS parameter corresponding to the type of the fixed network device; or

The policy response includes each of the mobile network device subscriptions corresponding to the fixed network device type. a QoS parameter, the CP function entity acquiring a QoS parameter corresponding to the type of the fixed network device included in the session according to each QoS parameter corresponding to the fixed network device type subscribed by the mobile network device. The solution is flexible and flexible by providing different QoS parameter acquisition methods.

In a possible design, the offloading device also acquires a quality of service QoS parameter of a data stream sent to the fixed network device; the offloading device is based on the process of transmitting the downlink data stream to the fixed network device The QoS parameter performs QoS control on a data stream sent to the fixed network device. Through the QoS parameters, the offloading device can control based on the QoS parameters in the process of offloading, and then further ensure the quality of the data transmission.

In a possible design, the service quality QoS parameter of the data stream sent by the traffic distribution device to the fixed network device is specifically: the traffic distribution device acquires a quality of service QoS parameter of a default data stream sent to the fixed network device; or The offloading device obtains a quality of service QoS parameter of the data stream sent to the fixed network device from the offloading request, and the QoS parameter of the data stream sent to the fixed network device is a QoS corresponding to the type of the fixed network device parameter. Through the QoS parameters, the offloading device can control based on the QoS parameters in the process of offloading, and then further ensure the quality of the data transmission.

In a possible design, the CP functional entity further receives an identifier of an access point of the mobile network device from the non-3GPP access gateway; further, the CP functional entity further connects to the non-3GPP The ingress gateway sends a request for establishing a session, where the request for establishing a session includes an identifier of the fixed network device included in the session request, and an identifier of the access point; and the CP functional entity accesses the non-3GPP interface a response to the establishment of the session returned by the gateway, the response of the establishment session includes an identifier of the fixed network device successfully registered in the access point corresponding to the access point identifier included in the session request; the CP functional entity And deleting the stored identifier of the fixed network device and the type of the fixed network device that are not successfully registered according to the response to establish the session. The fixed network device registered at the access point is further determined by a process of establishing a session with the non-3GPP access gateway. Therefore, it is ensured that the data stream sent to the fixed network device in the splitting can be successfully received, and the splitting is ensured smoothly.

In a second aspect, the method provided by the embodiment of the present invention is applied to a system that supports a non-3rd generation partnership program non-3GPP access technology to access a fifth generation 5G core network. The mobile network device receives a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, and the fixed network device indicated by the identifier of the fixed network device has the same connection with the mobile network device. Pointing in; then storing an identifier of the fixed network device; receiving a data packet of the service at the mobile network device And sending, to the CP function entity, a session modification request, where the session modification request carries an identifier of the mobile network device, an identifier of the fixed network device, and service description information of the service; the session modification request And a fixed network device for triggering sending, by the service description information of the service, the data stream sent to the mobile network device to the identifier of the fixed network device. Through the above method, the mobile network device can trigger the data stream sent to the mobile network device to be sent from the core network to the fixed network device in the process of providing the service, thereby avoiding direct connection between the mobile network device and the fixed network device (for example, Bluetooth technology, etc.) transmit data stream instability and improve service quality.

In a possible device, after the mobile network device establishes a connection with the fixed network device, it also identifies an identifier of the fixed network device that establishes a connection with the mobile network device; and then, the session request sent by the mobile network device The session request carries the identifier of the mobile network device and the identifier of the identified fixed network device that establishes a connection with the mobile network device, and the identifier of the fixed network device in the session establishment call is included in the identifier In the identification of the fixed network device that establishes a connection with the mobile network device.

In a third aspect, an embodiment of the present invention provides a traffic distribution device. The device has the function of implementing the shunt device in the design of the above method. These functions can be implemented in hardware or in software by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

In a fourth aspect, an embodiment of the present invention provides a non-3 third generation partnership plan non-3GPP access gateway. The access gateway has the function of implementing the access gateway in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

In a fifth aspect, an embodiment of the present invention provides a control plane CP functional entity. The CP functional entity has the function of implementing the execution of the CP functional entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

In a sixth aspect, an embodiment of the present invention provides a mobile network device. The mobile network device has the function of implementing the CP functional entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software. The hardware or software includes one or more units corresponding to the functions described above.

According to a seventh aspect of the present invention, a flow distribution device includes a processor, a memory, and a total a line and communication interface; the memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the shunt device is in operation, the processor executes the computer execution instruction stored in the memory to enable the shunt device A method of offloading between a fixed network device and a mobile network device according to any of the above first aspects.

In an eighth aspect, an embodiment of the present invention provides a CP functional entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when When the CP function entity is running, the processor executes the computer-executed instruction stored in the memory to cause the CP function entity to perform a method of offloading between the fixed network device and the mobile network device according to any one of the above first aspects.

In a ninth aspect, an embodiment of the present invention provides a non-3rd generation partnership plan non-3GPP access gateway, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, the process And the memory is connected to the memory, and when the access gateway is running, the processor executes the computer-executed instruction stored in the memory, so that the access gateway performs the fixed network device according to any one of the foregoing first aspects A method of offloading between mobile network devices.

A ninth aspect, an embodiment of the present invention provides a mobile network device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when When the mobile network device is in operation, the processor executes the computer-executed instructions stored by the memory to cause the access gateway to perform a method of offloading between the fixed network device and the mobile network device according to any of the above aspects.

In a tenth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the CP functional entity, which includes a program designed to execute the foregoing aspects as a CP functional entity.

In an eleventh aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the foregoing shunt device, including a program designed to implement the above-described aspects for a shunt device.

In an eleventh aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the non-3rd Generation Partnership Project non-3GPP access gateway, where Access to the program designed by the gateway.

According to a twelfth aspect, an embodiment of the present invention provides a computer storage medium for storing the foregoing Computer software instructions for use in a mobile network device that include a program designed to perform the above aspects for a mobile network device.

In addition, the technical effects brought by the design mode of any one of the second aspect to the fourth aspect can be referred to the technical effects brought by different design modes in the first aspect, and details are not described herein again.

These and other aspects of the invention will be more apparent from the following description of the embodiments.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below.

FIG. 1 is a schematic diagram of a 5G network architecture according to an embodiment of the present invention;

2 is a schematic diagram of a computer device according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart of a method for splitting a fixed network device and a mobile network device according to an embodiment of the present disclosure;

4 is a schematic flowchart of a method for splitting a fixed network device and a mobile network device according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a power distribution device according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a non-3GPP access gateway according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a CP functional entity according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of another mobile network device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

In the description of the present invention, "a plurality" means two or more unless otherwise stated.

As shown in FIG. 1 , it is a 5G network architecture provided by an embodiment of the present invention. The architecture not only supports the wireless technology defined by the 3GPP standards organization to access the 5G core network, but also supports the non-3GPP access technology to access the 5G core network.

As shown in Figure 1, the UE or Customer Premises Equipment (CPE), such as a fixed network terminal device, uses a non-3GPP access method (such as through non-3GPP). Incoming) and accessing the core network side through a non-3GPP access gateway (N-3G-GW).

The non-3GPP access point may be a WiFi access point (AP) or a WiFi access controller (AC), and the non-3GPP access mode may implement a WLAN air interface connection for the WLAN mode. The WLAN mode can be a WLAN AP (Access point) or a WALN AC (Access control), and both the WLAN AP and the WALN AC support the Y1 interface.

The N3G-GW implements the WLAN access network aggregation function, supports user plane data forwarding and control plane signaling processing, and supports Y2, NWx and NG (next generation network interface, next generation) 2 and NG3 interfaces. The NWx interface is an interface between the UE and the N3G-GW and is carried on the Y1 and Y2 interfaces. The NWx interface is used to establish a secure channel based on the Y1 interface between the UE and the non-GPP access point, and establish a secure channel based on the Y2 interface between the non-3GPP access point and the N3G-GW, and transmit the secure channel in the secure channel. Signaling or user plane data.

The N3G-GW includes an N3G-GW Control Plane (N3G-GW-C) functional entity and an N3G-GW User Plane (N3G-GW-U) work-through entity. The N3G-GW communicates with the Control Plane Function (CP) functional entity of the 5G core network through the NG2, and communicates with the UP functional entity of the 5G core network through the NG3 interface. Specifically, the N3G-GW-C functional entity communicates with the Control Plane Function (CP) functional entity of the 5G core network through the NG2 interface, and the N3G-GW-U functional entity passes through the NG3 interface and the user plane of the 5G core network (User Plane function, UP) functional entity communication. Further, in the embodiment of the present invention, the N3G-GW may store the identifier of the fixed network device and the identifier of the mobile network device that have the same access point access network as the mobile network device, and may be sent as the offloading device to the mobile network device. The data stream is forwarded to the fixed network device. The above N3G-GW is only a name, and the name itself does not limit the device. For example, the N3G-GW may be replaced with an ngPDG (Next Generation Packet Data Gateway), or an N3IWF (Non-3GPP Interworking Function) entity or the like.

The CP function entity communicates with the application function (AF) entity of the 5G core network through the NG5 interface, and sends a packet forwarding policy and a QoS control policy to the UP function entity through the NG4; in addition, the CP functional entity is also associated with the policy function entity. Communicate. In the embodiment of the present invention, the CP function entity acquires a traffic off policy, a QoS parameter, and the like for the UE to use the service to the policy function entity. Further, the CP function entity may also implement binding of the UE to the fixed network device, generate a traffic off policy based on the user subscription data, and send the traffic off policy to the UP function entity.

The UP function entity communicates with the data network (DN) entity of the 5G core network through the NG6, and is responsible for packet data packet forwarding, QoS control, accounting information statistics, and reporting to the CP functional entity. Further, the UP function entity may also be configured as a offloading device to send the data stream sent to the mobile network device to the fixed network device having the same access point as the mobile network device.

It should be noted that the mobile network device involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms. User equipment UE, mobile station (MS), terminal, terminal equipment, soft terminal, and the like. For convenience of description, the mobile network device in this application takes the UE as an example. As a customer front-end device, the CPE can also be any fixed network device (ie, a fixed network device), such as a set-top box. The fixed network devices described above may include fixed non-mobile devices, as well as devices that move within a limited range, such as devices that move within a corporate or home environment.

It should be noted that the above-mentioned "CP functional entity" and "UP functional entity" are only one name, and the name itself does not limit the device. For example, the "CP functional entity" may also be replaced by "CP function", and the "UP functional entity" may also be replaced with "UP function"; or, the "CP functional entity" may be replaced with "CP", the "UP functional entity" may also be replaced with "UP", etc., which are uniformly described herein, and will not be described below.

In addition, any one of the above-mentioned 5G network architectures, such as a CP functional entity or an UP functional entity, may be implemented by one physical device or multiple physical devices; The functional nodes or network elements, such as the CP functional entity and the UP functional entity, may be implemented by different physical devices, or may be implemented by the same physical device, which is not specifically limited in this embodiment of the present invention. That is, it can be understood that any one of the above-mentioned 5G network architectures, such as a CP function entity or an UP function entity, may be a logical function module or a plurality of entities in the entity device. A logical function module of the device is not specifically limited in this embodiment of the present invention.

For example, as shown in FIG. 2, the CP function entity, the UP function entity, the non-3gpp access gateway, and the mobile network device in FIG. 1 can be implemented by the computer device (or system) in FIG.

FIG. 2 is a schematic structural diagram of each network element provided by an embodiment of the present invention. The network element is used in the system shown in FIG. 1. Network element 200 can include one or more ports 208 coupled to a transceiver 206. The transceiver 206 can be a transmitter, a receiver, or a combination thereof, from His network node sends or receives data packets over port 212. Processor 202 is coupled to transceiver 206 for processing data packets. Processor 202 can include one or more multi-core processors and/or memory 204. The processor 202 can be a general purpose processor, an application specific integrated circuit (ASIC), or a digital signal processor (DSP).

Memory 204 can be a non-transitory storage medium coupled to processor 202 for storing different types of data. The memory 204 may include a read only memory (ROM), a random access memory (RAM), or other types of dynamic storage devices that can store information and instructions, and may also be a disk storage. Memory 204 can be used to hold instructions that implement an NFV system or related methods. It will be appreciated that at least one of the cache and long term storage is programmed or loaded by the processor 202 to the processor 202 of the network element 200.

Network element 200 may implement a method of performing one or more instructions to perform a split between a fixed network device and a mobile network device in accordance with an embodiment of the present invention. These instructions may be stored in the memory 204 or integrated into the kernel of the operating system of the network element or a plug-in of the kernel.

In one particular embodiment, network element 200 acts as a streaming device, including memory 204, processor 202 and transceiver 206, and one or more ports 208 coupled to the transceiver. a memory 204 for storing computer executable program code; a processor 202 coupled to the memory 204 and the transceiver 206;

Wherein the program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:

Receiving a shunt request sent by the control plane CP function entity, where the offload request includes description information of the service that allows the offload, an identifier of the mobile device, and an identifier of the fixed network device; and a downlink data stream that is sent to the mobile device; The fixed network device indicated by the mobile device and the fixed network device identifier has a common access point;

Determining, by the traffic distribution device, that the downlink data flow is a data flow of the traffic offloaded service according to the description information of the traffic offloaded service;

And sending the downlink data stream to the fixed network device according to the identifier of the fixed network device.

The specific implementation manner of the operation performed by the processor included in the network element of the offloading device may refer to the corresponding step performed by the N3G-GW or the UP functional entity in performing the offloading process in the embodiment of FIG. 3 or 4, and the present invention is implemented. The examples will not be described again.

In another specific embodiment, network element 200 acts as a non-3GPP access gateway, including a memory. 204, processor 202 and transceiver 206 and one or more ports 208 coupled to the transceiver. a memory 204 for storing computer executable program code; a processor 202 coupled to the memory 204 and the transceiver 206;

Wherein the program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:

Obtaining an identifier of the fixed network device and an identifier of the mobile network device, where the fixed network device and the mobile network device have the same access point;

Sending the identifier of the fixed network device and the identifier of the mobile network device to a control CP function entity, where the identifier of the fixed network device and the identifier of the mobile network device are used to indicate that the offload device is to be sent to the mobile network device The downstream data stream is sent to the fixed network device.

For a specific implementation of the operation performed by the processor included in the network element of the non-3GPP access gateway, reference may be made to the corresponding step performed by the access gateway in the embodiment of FIG. 3 or FIG. 4, which is not described in detail in the embodiment of the present invention.

In another embodiment, network element 200 acts as a CP functional entity, including memory 204, processor 202 and transceiver 206, and one or more ports 208 coupled to the transceiver. a memory 204 for storing computer executable program code; a processor 202 coupled to the memory 204 and the transceiver 206;

Wherein the program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:

Receiving an identifier of the mobile network device and an identifier of the fixed network device sent by the non-3rd Generation Partnership Project non-3GPP access gateway;

Obtaining service description information of the mobile network device that is allowed to be offloaded by the identifier of the mobile network device;

Sending a offloading request to the offloading device, where the offloading request includes description information of the service that allows the offloading, an identifier of the mobile network device, and an identifier of the fixed network device; the offloading request is used to indicate according to the solid The identifier of the network device sends the downlink data stream of the mobile network device indicated by the identifier sent to the mobile network device to the fixed network device.

For the specific implementation of the operation performed by the processor included in the network element of the CP functional entity, refer to the corresponding step performed by the CP functional entity in the embodiment of FIG. 3 or 4, which is an embodiment of the present invention. No longer.

In another embodiment, network element 200 acts as a mobile network device, including memory 204, processor 202 and transceiver 206, and one or more ports 208 coupled to the transceiver. a memory 204 for storing computer executable program code; a processor 202 coupled to the memory 204 and the transceiver 206;

Wherein the program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:

Receiving a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, where the fixed network device indicated by the identifier of the fixed network device has the same access point as the mobile network device;

Storing an identifier of the fixed network device;

Transmitting, in the process of receiving the data packet of the service, the session modification request to the CP function entity, where the session modification request carries the identifier of the mobile network device, the identifier of the fixed network device, and the The service description information of the service; the session modification request is used to trigger the fixed network device that sends the data flow sent to the mobile network device to the identifier of the fixed network device according to the service description information of the service.

For the specific implementation of the operations performed by the processor included in the network element of the mobile network device, reference may be made to the corresponding steps performed by the mobile network device in the embodiment of FIG. 3 or 4, which is not described in the embodiment of the present invention.

FIG. 3 is a schematic flowchart of a method for offloading between a fixed network device and a mobile network device according to an embodiment of the present invention. The UE is a mobile network device, and the CPE is a fixed network device. This embodiment includes two phases, a shunt preparation phase and a shunt phase. In the offload preparation phase (refer to S301-307 in FIG. 3), the CP function entity completes the perception of the fixed network device and establishes a binding relationship between the fixed network device and the UE having the same access point as the UE. In the splitting phase (refer to S308 and subsequent steps in FIG. 3), the user is triggered to perform the offloading by the user who is using the UE to receive the data stream, and the network offloads part or all of the traffic to the fixed network device.

Specifically, the method for offloading between the fixed network device and the mobile network device provided by the embodiment of the present invention includes the following steps:

The S300 and the fixed network device (such as CPE) establish a connection with the N3G-GW.

Specifically, the fixed network device (such as the CPE) can establish a connection with the non-3GPP access gateway N3G-GW (specifically, the N3G-GW-U functional entity of the N3G-GW) through the non-3GPP access point. For example, the wind-fixing device may send a connection request to the access point of the UE (such as a non-3GPP access point) by using the Y1 interface, and then the access point sends a connection request to the N3G-GW-U functional entity by using the Y2 interface, in the connection request. Contains the identity of the fixed network device. The fixed network device can establish a connection with the N3G-GW after the authentication succeeds by using the Point to Point Protocol over Ethernet (PPPOE) or the IP over Ethernet (IPOE) on the Ethernet.

After the fixed network device establishes a connection with the N3G-GW (specifically, the N3G-GW-U functional entity) through the access point (such as a non-3GPP access point) of the fixed network device, the N3G-GW acquires the fixed network device. The identifier and the identifier of the access point of the fixed network device, and the correspondence between the identifier of the fixed network device and the identifier of the access point of the fixed network device. The identifier of the fixed network device may be an inherent identifier of the fixed network device (such as the identifier of the fixed network device), or may be a temporary identifier assigned by the N3G-GW to the fixed network device. The embodiments of the present invention are not limited herein. The identifier of the access point of the fixed network device may be the location where the access point is deployed in the network, such as the circuit ID of the access point in the network line, or the physical location identifier actually deployed by the access point. The embodiment of the invention is not limited.

Further, the N3G-GW can also identify the device type for the fixed network device, and store the correspondence between the type of the fixed network device and the identifier of the fixed network device. Specifically, the type of the fixed network device may be: a display device, a video device, an audio device, a voice device, a television (TV), a desktop computer (PC), a printer, a fax machine, a refrigerator, an air conditioner, a monitor, and the like.

Step 301: The UE sends a session request to the N3G-GW-U functional entity of the N3G-GW through the access point. The session request may be a packet data unit (PDU) session establishment request, an attach request, or another NAS (Non-Access-Stratum) request, etc., in the embodiment of the present invention, for a session request The form is a NAS (Non-Access-Stratum) request as an example.

Specifically, the UE may send a NAS request to the access point of the UE (such as a non-3GPP access point) by using the Y1 interface, and then the non-3GPP access point sends the NAS request to the N3G-GW-U functional entity by using the Y2 interface, and the NAS The request contains the UE ID. The UE identifier may be one or two of a UE temporary identifier (for example, a Globally Unique Temporary Identity (GUTI), a UE permanent identifier, or a UE's network access identifier (NAI). Or three. The UE permanent identifier may be an international mobile subscriber identification number (IMSI).

S302: The N3G-GW user plane function entity sends the received session request and the identifier of the access point of the UE to the N3G-GW-C (N3G-GW control plane function entity).

Specifically, after receiving the session request sent by the UE through the non-3GPP access point, the N3G-GW-U functional entity acquires the identifier of the access point of the UE. The identifier of the access point of the UE embodies the location where the access point is deployed in the network, such as the circuit ID (the circuit ID) of the access point in the network line, or the physical location identifier actually deployed by the access point, etc. The embodiment is not limited; then the session request and the access point identifier of the UE are sent to the N3G-GW-C.

S303. The N3G-GW-C sends the session request and the identifier of the access point of the UE to the CP function entity.

Specifically, the session request sent by the N3G-GW-C to the CP function entity may be an Uplink NAS transprot message, a session establishment request message, or an Initial UE message. After receiving the session request sent by the N3G-GW-U functional entity, the N3G-GW-C functional entity identifies the fixed network device from the N3G-GW-U and the fixed network device according to the identifier of the access point of the UE. Obtaining, in a correspondence between the identifiers of the access points, an identifier of the fixed network device having the same access point as the mobile network device. Then, the N3G-GW-C functional entity sends the determined identifier of the fixed network device with the same access point identifier as the UE and the session request (NAS request) sent by the UE to the CP functional entity in the form of the NG2 request. That is to say, the fixed network device indicated by the identifier of the fixed network device sent by the N3G-GW to the CP functional entity and the mobile network device indicated by the identifier of the mobile network device have the same access point.

That is, the NG2 request includes the identifier of the fixed network device having the same access point as the UE and the session request sent by the UE (ie, the NAS request); further, the NG2 request may further include the identifier of the mobile network device access point. The access point of the mobile network device is also an access point of the fixed network device.

Further, the N3G-GW-C can also obtain the type of the fixed network device according to the identifier of the fixed network device, and send the type of the fixed network device to the CP functional entity.

S304: The CP function entity sends a session establishment request to the UP function entity, so that the UP function entity establishes a session with the CP function entity after receiving the session establishment request.

Specifically, the session establishment request sent by the CP function entity to the UP function entity may be a packet data unit (PDU) session establishment request (which may be referred to as a first session establishment request). After receiving the NG2 request sent by the N3G-GW-C, the CP function entity authenticates the UE, and after the UE authentication is successful, allocates the UE's IP address and determines the accessed UP function entity. The CP functional entity then assigns a fully qualified tunnel endpoint identifier (F-TEID) to the determined UP functional entity. After the F-TEID is assigned to the UP function entity, a session establishment request is sent to the determined UP function entity, and the session establishment request includes an F-TEID allocated for the UP.

In addition, after the UE authentication and authentication succeeds, the CP functional entity also allocates an F-TEID to the N3G-GW. Further, the session establishment request sent by the CP function entity to the UP function entity may further include an F-TEID and a UE IP address allocated for the N3G-GW, or an F-TEID and a user identifier allocated for the N3G-GW.

As an optional manner, the CP function entity allocates an F-TEID to the N3G-GW. After the CP function entity sends a session establishment request to the UP function entity, the session establishment request sent by the CP function entity to the UP function entity is not included in the N3G. - GW assigned F-TEID. Therefore, the CP function entity may further send a session establishment modification request to the UP function entity after sending the session establishment request to the UP function entity, and send the F-TEID allocated for the N3G-GW to the UP function entity in the session establishment modification request.

It is to be noted that the method for determining the access of the UP function entity by the CP function entity belongs to the prior art, and is not limited herein.

Further, after receiving the session request sent by the UE, the CP function entity acquires the UE identifier included in the session request, and stores the correspondence between the UE identifier and the identifier of the fixed network device sent by the CP utility entity. If the NG2 request includes the identifier of the access point of the fixed network device, the CP further stores a correspondence between the identifier of the UE, the identifier of the fixed network device, and the identifier of the access point of the fixed network device and the type of the fixed network device. That is, the CP functional entity stores the correspondence between the type of the fixed network device, the identifier of the UE and the identifier of the fixed network device, or the type of the fixed network device, the identity of the UE, the identity of the fixed network device, and the storage mobile network. The correspondence between the identifiers of the access points of the device and the fixed network device, or the correspondence between the UE identifier, the identity binding of the fixed network device, and the identifier of the access point of the mobile network device and the fixed network device.

S305. The CP function entity sends a session establishment request to the N3G-GW-C functional entity, so that the N3G-GW-C functional entity receives the session establishment request and establishes a session with the CP function entity.

Specifically, the session establishment request sent by the CP function entity to the N3G-GW-C functional entity may be a packet data unit (PDU) session establishment request (which may be referred to as a second session establishment request). The session establishment request includes: a user identifier, an F-TEID assigned by the CP functional entity to the N3G-GW (abbreviation: N3G-GW F-TEID), and an F-TEID assigned to the UP functional entity (abbreviation: UP F-TEID) ).

It is worth noting that there is no strict chronological order between step S304 and step S305.

S306. After the CP functional entity establishes a session with the UP functional entity and the N3G-GW, respectively, return a session response to the N3G-GW-C.

Specifically, since the session request is in the form of a NAS request, the session response in this step includes the NAS response. The NAS response may include the UE IP address allocated by the CP for the UE, and the identifier of the fixed network device that has the same access point as the UE determined by the N3G-GW-C functional entity in step 303.

Optionally, the NAS response may establish a reply message, an attach success message, or other NAS reply message for the PDU session. Further, the NAS response is sent through the interface NG2 message between the CP function and the N3G-GW.

As an alternative, if the NG2 request in S303 further includes the type of the fixed network device (ie, the type corresponding to the identifier of the fixed network device), the session response may further include a fixed network having the same access point as the UE. The type of device.

S307. The N3G-G-C obtains a session response from the NG2 message, and sends the session response to the UE.

After receiving the session response, the UE stores the fixed network device identifier carried in the session response, and displays the fixed network device identifier to the terminal user. If the session response further includes the type of the fixed network device, the UE stores the correspondence between the identifier of the fixed network device and the type of the fixed network device, and displays the correspondence between the identifier of the fixed network device and the type of the fixed network device to the terminal user. .

The UE encapsulates and sends related service data packets by using the UE IP address to provide service services for users of the UE.

S308: The UE sends a session modification request to the CP functional entity. The session modification request includes an identifier of the UE, an identifier of the fixed network device, and a description of the corresponding service of the data stream being sent to the mobile network device. Information.

The session modification request may be a PDU session modification request or other form of a request for modifying the current session. The example of the present invention is described by taking a session modification request as a PDU session modification request as an example.

Specifically, after receiving the session response in step 307, the UE receives the data stream sent by the N2G-GW and provides a service service for the user of the UE. Then, the UE displays the fixed network device identifier included in the session response or the correspondence between the identifier of the fixed network device and the type of the fixed network device to the user, so that the user selects the fixed network device as the device that receives the data packet after the offloading. The UE may display the information included in the session response to the user according to the trigger of the user, or may be automatically displayed after the UE receives the session response, which is not limited herein. Further, in the embodiment of the present invention, the operation of the user to select the fixed network device as the device for offloading the data packet is not limited. For example, the user can select (long press) the video service being played on the mobile phone and move it to the fixed network device (such as TV, TV).

The UE sends a PDU session modification request to the N3G-GW-C functional entity based on the user's operation. Optionally, the PDU session modification request may also be replaced with other forms of requests for modifying the current session. A PDU session modification request or other form of request for modifying the current session is carried in the NAS request.

Further, the description information of the service corresponding to the data stream that is being sent to the mobile network device may be obtained by the UE according to the service used by the user, and may be a source IP address and a destination IP address including the traffic to be offloaded, and a port number of the service source to be offloaded. And one or two or three of the destination port number and the type of protocol used by the offloaded service. The description of the service may also be an identifier for describing the service, such as a service identifier or a service identifier, or a flow identifier of the data flow of the traffic to be offloaded, which is not limited in the embodiment of the present invention. In addition, the description information of the service may be obtained by the UE according to the service to be offloaded, and the specific acquisition method belongs to the prior art, which is not limited in the embodiment of the present invention. Optionally, the PDU session modification request may further include an operation indication, such as an indication of traffic switching, to indicate that the CP function entity triggers the offloading operation after receiving the session modification request.

S309. After receiving the session modification request sent by the UE, the CP function entity sends a policy request to the policy function entity to obtain the quality of service (QOS) parameter used in the offloading from the policy function entity.

Specifically, the policy request includes an identifier of the UE (such as an IMSI of the UE).

As an optional manner, the policy request may further include a type of the fixed network device and/or description information of the corresponding service of the data flow that is being sent to the mobile network device.

After receiving the session modification request, the CP function entity acquires the type of the fixed network device. If the session modification request includes the type of the fixed network device, the CP functional entity may obtain the type of the fixed network device according to the session modification request. If the session modification request includes the type of the fixed network device, the CP function entity may obtain the type of the fixed network device according to the identifier of the inherent device in the session modification request. If the identifier of the fixed network device carried in the session modification request is inherent to the fixed network device The identifier, the CP functional entity can obtain the type of the fixed network device according to the identifier of the fixed network device. If the identifier of the fixed network device carried in the session modification request is the temporary identifier of the fixed network device, the CP function entity may obtain the type of the fixed network device according to the identifier of the stored fixed network device and the type of the fixed network device.

S310. After receiving the policy request sent by the CP function entity, the policy function entity returns a policy response to the CP function entity.

The policy function entity stores the traffic offloading policy information signed by each mobile network device (such as a UE). The offloading policy information includes description information of the service subscribed by the mobile network device (that is, description information of the service that the mobile network device subscribes to allow the offloading).

Further, if the policy request includes the type of the fixed network device, the offload policy information further includes a quality of service QoS parameter corresponding to the fixed device type. The QoS parameters include Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), QoS Class Identifier (QCI), and Allocation and Retention Priority (ARP). ), Differentiated Services Code Point (DSCP), one of delay, bandwidth, any two, any three, or any number.

If the type of the fixed network device is not included in the policy request, the offloading policy information may further include a QoS parameter that is signed by the mobile network device and corresponding to each fixed network device type, and then the CP functional entity signs the contract according to the mobile network device. And a QoS parameter corresponding to the type of the fixed network device, and acquiring a QoS parameter corresponding to the type of the fixed network device included in the session. Specifically, after receiving the policy request sent by the CP function entity, the policy function entity obtains the traffic policy corresponding to the UE based on the identifier of the UE, and then obtains the QoS parameter corresponding to the type of the fixed network device according to the traffic policy information corresponding to the UE. And determining, according to the service description information, whether the service is allowed to be offloaded. And if the service allows the offloading, returning a policy response to the CP function entity, where the policy response includes service description information, a type of the fixed network device, and a QoS parameter corresponding to the type of the fixed network device.

Optionally, if the obtained QoS parameter corresponding to the type of the fixed network device in the policy request is not included in the acquired UE offloading policy information, the policy function entity uses the default QoS parameter as the type corresponding to the type of the fixed network device. The QoS parameter, and further determining, according to the service description information in the offload request, whether the service allows offloading, and returning a policy response to the CP functional entity after determining to allow the offloading. The policy response includes service description information, a type of the fixed network device, and a QoS parameter corresponding to the type of the fixed network device.

It is to be noted that, if the policy function entity determines that the service is not allowed to be offloaded according to the description information of the service, the policy response in S310 carries the failure information, and does not perform S311 and S312, and performs subsequent offloading.

As another alternative, if the policy request sent by the CP function entity does not include the service description information of the offloaded service, the policy response includes description information of the service subscribed by the mobile network device. Then, the CP function entity further determines, according to the description information of the service in the session modification request and the description information of the service in the policy response, whether the service indicated by the service description information in the session modification request allows the traffic to be offloaded. . And after determining that the shunting is allowed, the subsequent shunts after S311 and S312 are performed.

As another possible option, the CP function entity may also acquire the offloading policy information of the UE in advance (for example, any time before S308, or may obtain the shunting policy information of all UEs from the policy function entity in advance), and then receive the information. After the session modification request to S308, the offloading policy information of the UE is obtained according to the identifier of the UE included in the session modification request. The CP function entity then determines the QoS parameters corresponding to the type of the fixed network device carried in the session modification request according to the information about the offloading policy of the UE.

S311: After receiving the policy response of S310, the CP function entity sends a split request to the N3G-GW-C functional entity through the NG2 interface. The offload request may be a PDU session modification request message. The offload request includes description information of the service that allows the offload, an identifier of the mobile network device, and an identifier of the fixed network device.

Specifically, the offloading policy may be sent by the policy function entity to the CP function entity, as shown in step 310.

The S312 and the N3G-GW-C function entity send a offload response to the CP function entity through the NG2 interface.

Further, after receiving the offloading request sent by the CP function entity, the N3G-GW-C functional entity sends the downlink data stream to the fixed network device according to the identifier of the fixed network device. Further, the N3G-GW-C functional entity may further obtain a quality of service QoS parameter of the data stream sent to the fixed network device; and in the process of transmitting the downlink data stream to the fixed network device, based on the QoS The parameters perform QoS control on the data stream sent to the fixed network device.

The quality of service QoS parameter of the data stream that is sent by the N3G-GW-C to the fixed network device is specifically: the traffic distribution device obtains a quality of service QoS parameter of a data stream that is sent by default to the fixed network device; or The offloading device obtains a quality of service QoS parameter of the data stream sent to the fixed network device from the offloading request, and the QoS parameter of the data stream sent to the fixed network device is a QoS parameter corresponding to the type of the fixed network device.

Further, the method for the N3G-GW-C functional entity to send the downlink data stream to the fixed network device is as follows: the N3G-GW-C functional entity receives the downlink data packet sent by the UP function entity, and parses the downlink data packet header information, And matching with the description information of the service in the offload request. After the packet header information of the downlink data packet is successfully matched with the flow description in the traffic distribution request, the identifier of the fixed network device in the traffic distribution request is obtained. The N3G-GW-U functional entity then sends the data packet to the fixed network equipment (CPE).

It is worth noting that this patent does not limit how the shunted packets are sent to the fixed network device. For example, the N3G-GW-C functional entity may change the destination IP address in the offloaded data packet to the IP address corresponding to the fixed network device, and send the offloaded data packet to the fixed network device from the port corresponding to the fixed network device. .

In the foregoing process, after the mobile network device (such as the UE) initiates a session request, the CP function binds the identifier of the fixed network device with the same access point to the UE, and the fixed network device with the same access point as the UE The identity and/or type are sent to the UE. Therefore, the UE selects the fixed network device that receives the data stream in the process of receiving the data stream and providing the service service for the user. The CP acquires the QoS parameter of the fixed network device according to the identifier of the fixed network device with the same access point bound to the mobile network device, and notifies the traffic off device, such as the N3G-GW, to send the downlink data stream based on the QoS parameter. To the fixed network device. Therefore, the network side can perform QoS control on the data stream sent to the fixed network device, and improve the service quality after the offloading.

FIG. 4 is a schematic flowchart of a method for offloading between a fixed network device and a mobile network device according to an embodiment of the present invention. Accessing the 3GPP network in the 5G network architecture shown in Figure 1 by UE and CPE The case is described as an example, involving the interaction between the UE, the N3G-GW, the CP functional entity, and the Policy Function (PF) entity and the UP functional entity. This embodiment includes two phases, a shunt preparation phase and a shunt phase. In the offload preparation phase (refer to S400-409 in FIG. 4), the CP function entity completes the perception of the fixed network device and establishes a binding relationship between the fixed network device and the UE having the same access point as the UE. In the offloading phase (refer to S410 and subsequent steps in FIG. 3), the user triggers the network to perform offloading, and the network offloads part or all of the traffic to the fixed network device.

S400: The UE establishes a connection with the fixed network device, and identifies the identifier of the fixed network device.

Specifically, the UE can establish a connection with the fixed network device in multiple manners. For example, a fixed network device (such as a CPE) that opens a Bluetooth through a Bluetooth search, and the like, is not limited herein. After establishing a connection with the fixed network device, the UE obtains the identifier of the fixed network device (such as the inherent identifier of the fixed network device), and stores the correspondence between the identifier of the fixed network device and the device type. Then, the UE displays the correspondence between the identifier of the fixed network device and the device type to the user.

Steps 401-402: The UE sends a session request to the N3G-GW-C via the N3G-GW-U functional entity of the N3G-GW.

The session request may be a PDU session connection establishment request, an attach request, or another NAS (Non-Access-Stratum) request, and the like. The embodiment of the present invention describes a case where the session request is in the form of a NAS (Non-Access-Stratum) request.

The NAS request includes the identifier of the UE and the identifier of the fixed network device. The UE identifier may be one, two or three of the UE temporary identifier, the UE permanent identifier, or the UE's network access identifier.

Further, referring to the descriptions of S301 and S302, after receiving the session request sent by the UE in S401, the N3G-GW-U may also acquire the identifier of the access point of the UE, and add the identifier of the access point of the UE to the session. The request is sent to the N3G-GW-C in S402. It is worth noting that the identifier of the fixed network device in the session request is identified by the UE after the UE establishes a connection with the fixed network device. Therefore, the fixed network device and the UE indicated by the identifier of the fixed network device in the session request have the same access point. Therefore, the identifier of the access point of the UE acquired by the N3G-GW-U is both the identifier of the access point of the UE and the identifier of the access point of the fixed network device. That is to say, the fixed network device indicated by the UE in the session request and the identifier of the fixed network device uses the same access point to access the 3GPP core network.

S403. The N3G-GW-C sends a session request to the CP function entity, where the session request further includes an identifier of the UE access point.

Referring to S303, the N3G-GW-C can request a CP session entity to send a session request through the interface NG2. The NG2 request includes a session request (ie, a NAS request) sent with the UE.

Further, after receiving the session request, the CP function entity stores the correspondence between the identifier of the UE and the identifier of the fixed network device.

Further, if the session further includes the type of the fixed network device, the CP functional entity further stores the correspondence between the identifier of the fixed network device and the type of the fixed network device.

S404-405: The CP function entity establishes a session between the N3G-GW and the UP functional entity for the UE.

Specifically, the CP function entity separately sends a session establishment request to the UP function entity and the N3G-GW (such as the N3G-GW-C function entity), and the CP function entity receives the UP function entity and the N3G-GW respectively. The session establishment response establishes a session between the N3G-GW and the UP functional entity for the UE. Specifically, the CP function entity establishes a N3G-GW for the UE to establish a session with the UP function entity. For reference, the descriptions of S304 and S305 are not limited herein.

S406-407. The CP functional entity establishes a session between the N3G-GW and the UP functional entity for the fixed network device.

Specifically, the CP functional entity separately sends a session establishment request to the UP functional entity and the N3G-GW (such as the N3G-GW-C functional entity) (and the CP functional entity separately receives and receives the N3G-GW-C function). The session establishment response returned by the entity and the UP function entity establishes a session between the N3G-GW and the UP function entity for the fixed network device, wherein the IP session establishment request sent to the N3G-GW includes the identifier of the fixed network device and the CP is N3G- The GW-assigned tunnel identity IP session establishment request may further include an identifier of the access point of the UE and the fixed network device. The session establishment request sent to the UP function entity includes the identifier of the intrinsic device, and the tunnel identifier assigned by the CP to the N3G-GW. And the tunnel identifier assigned by the CP to the UP, and the identifier of the fixed network device and the access point of the UE.

Then, after receiving the session establishment request sent by the CP function entity, the N3G-GW determines the registration status of the fixed network device based on the identifier of the access point and the identifier of the fixed network device included in the session establishment request. Then, the N3G-GW sends the correspondence between the IP address of the successfully registered fixed network device and the identifier of the fixed network device to the CP functional entity in the session establishment response.

Further, after receiving the session establishment response for the fixed network device returned by the N3G-GW, the CP function entity determines the identifier of the fixed network device that has been successfully registered according to the identifier of the successfully registered fixed network device included in the session establishment response. And deleting the UE identifier, the identifier of the fixed network device, and the type of the fixed network device. The identity of the fixed device and the type of the fixed network device that are not successfully registered in the correspondence relationship.

Further, after establishing a session between the N3G-GW and the UP functional entity for the fixed network device, the CP functional entity also records the access point identifier and the CP functional entity establishes a session for the fixed network device as the N3G-GW and the UP functional entity. The corresponding relationship of the assigned tunnel identifiers.

Further, before performing S406-407, the CP function entity determines whether the corresponding relationship including the access point identifier is recorded according to the access point identifier of the UE and the fixed network device in S403. If the CP function entity determines that the corresponding relationship including the access point identifier is recorded, the session between the N3G-GW and the UP functional entity established by the fixed network device is obtained according to the tunnel identifier in the corresponding relationship. S406-407 is no longer executed.

S408. After the CP function entity establishes a session between the N3G-GW and the UP functional entity for the UE and the fixed network device, the N3G-GW-C functional entity returns a session response to the N3G-GW-U functional entity.

Specifically, since the session request is in the form of a NAS request, the session response in this step includes the NAS response. The NAS response may include the UE IP address assigned by the CP to the UE. Optionally, the NAS response may further include an identifier of the successfully registered fixed network device determined in S406.

Optionally, the NAS response may establish a reply message, an attach success message, or other NAS reply message for the PDU session. Further, the NAS response is sent through the interface NG2 message between the CP function and the N3G-GW. The NG2 message in this step may be and the NG2 response message may be any one of an NG2 reply message, a Downlink NG2 NAS transport message, or an NG2 session establishment reply message.

S409. The N3G-G-C functional entity obtains the NAS response from the NG2 response, and continues to send the NAS response to the UE through the N3G-G-U functional entity.

After receiving the NAS response, the UE stores the fixed network device identifier carried in the NAS response, and displays the fixed network device identifier to the terminal user. If the NAS response further includes the type of the fixed network device, the UE stores the correspondence between the identifier of the fixed network device and the type of the fixed network device, and displays the correspondence between the identifier of the fixed network device and the type of the fixed network device to the terminal user. .

The UE uses the UE IP address to receive data packets of related services, and provides service services for users of the UE.

S410: The UE sends a session modification request to the CP functional entity. The session modification request may be a PDU session modification request, a traffic off request, or the like.

For details, refer to the description of S308, and the embodiments of the present invention are not described in detail.

S411-412, with reference to the related description of S309-310, the embodiments of the present invention are not described in detail.

S413: After receiving the policy response of S412, the CP function entity sends a split request to the UP function entity through NG4. The information carried in the IP session modification request refers to the description of the NG2 modification request in S311.

Further, the operations performed by the CP function entity after receiving the policy response of S412 can also refer to the related description in S311, and the embodiments of the present invention are not described in detail.

S414. The UP function entity sends a offload response to the CP function entity through the NG4 interface.

Further, after receiving the offloading request sent by the CP function entity, the UP function entity sends the downlink data stream to the fixed network device according to the identifier of the fixed network device in the offloading request. Specifically, the CP function entity receives the downlink data packet sent to the UE, parses the downlink data packet header information, and matches the service description information in the traffic distribution request. After the packet header information of the downlink data packet is successfully matched with the traffic description in the traffic distribution request, the IP address of the fixed network device corresponding to the traffic distribution policy is obtained. Then, the CP function entity modifies the destination IP address of the data packet to the IP address of the fixed network device, and sends the data packet modified with the destination IP address to the N3G-GW through the session link corresponding to the tunnel identifier of the N3G-GW. The received data packet is then sent by the N3G-GW to the fixed network device according to the IP address of the fixed network device.

Further, after the processing of the offloading request by the UP function entity, refer to the description of S312, and the implementation of the present invention is not described in detail herein.

In the foregoing process, after the UE establishes a connection with the fixed network device, the identifier of the fixed network device is identified. A session request is then sent to the N3G-GW through the access point. After the CP network entity initiates a session request by the mobile network device (such as the UE), the UE is bound with the identity of the fixed network device having the same access point and/or the type of the fixed network device, and will have the same access point as the UE. And the identity and/or type of the successfully registered fixed network device is sent to the UE. Therefore, in the process of receiving the data flow and providing the service service for the user, the UE selects the fixed network device to perform data offloading. The CP acquires the QoS parameters of the fixed network device according to the identifier of the fixed network device with the same access point bound to the mobile network device, and notifies the traffic distribution device, such as the N3G-GW, to send the data flow sent to the UE based on the QoS parameter. Give fixed network equipment. Therefore, the network side can perform QoS control on the data stream sent to the fixed network device, and improve the service quality after the offloading.

It should be noted that the S300-S307 can also be interchanged with the S400 and S409 to complete the offloading on the UP functional entity or the N3G-GW.

As another implementation manner, in conjunction with the description for FIG. 3 or FIG. 4, the CP functional entity may also perform S309 at any time between S303 and S306, and send a policy request to the policy function entity without executing 308; or The CP function entity may also execute S411 at any time between S407 and S409 to send a policy request to the policy function entity without executing S410. The policy request includes the identifier of the UE, so as to obtain the offload policy information of the UE from the policy function entity. Then, the policy response in S311 or S412 includes the offload policy information of the UE. The offload policy information of the UE refers to the description of S310.

After receiving the policy response, the CP function entity determines the identifier of the fixed network device and the type of the fixed network device according to the identifier of the fixed network device and the type of the fixed network device stored in S304 or S403, and according to the determined fixed network device. The type obtains a QoS parameter corresponding to the type of the fixed network device.

Then, S311 or S413 is executed, and the offload request in S311 or S413 includes the UE identifier, the identifier of the fixed network device, the QoS parameter corresponding to the type of the fixed network device corresponding to the fixed network device identifier, and the service description information of the service that allows the offloaded service. . After receiving the offloading request sent by the CP function entity, the offloading device (such as the N3G-GW or the UP function entity) monitors the data stream sent to the UE based on the UE identifier carried in the offloading request, and monitors the data sent to the UE. After the flow, the service description information of the data flow sent to the UE is obtained. Then, according to the service description information of the data stream sent to the UE and the description information of the service in the offloading request, it is determined whether the service corresponding to the data stream sent to the UE is allowed to be offloaded. And determining YES, performing data offloading between the fixed network device and the UE based on the identifier of the fixed network device carried in the offload request, and performing QoS control on the data flow offloaded to the fixed network device based on the QoS parameter in the offload request .

As an alternative manner, after receiving the policy response, the CP function entity determines the solid corresponding to the identifier of the UE according to the identifier of the UE and the identifier of the fixed network device and the fixed network device type stored in S304 or S403. If the identifier of the fixed network device corresponding to the identifier of the UE is two or more, the identifier of the fixed network device and the fixed network may be selected by the CP functional entity. The type of the device, and the identifier of the selected fixed network device and the type of the fixed network device are included in the offload request.

By describing, the CP function is initiated after a session request is initiated by a mobile network device (such as a UE). The UE binds the identity of the fixed network device with the same access point and the type of the fixed network device. In addition, the CP function entity obtains the QoS parameters of the fixed network device and the service description information of the service that is allowed to be offloaded according to the identifier of the fixed network device and the type of the fixed network device that are bound to the mobile network device. And notifying the offloading device, such as the N3G-GW or the UP function entity, to monitor the data stream sent to the UE, and after the N3G-GW or the UP function entity determines that the data stream sent to the UE is a data stream of the service that allows the offloading, based on the QoS parameter The data stream sent to the UE is sent to the fixed network device. Therefore, the network side can perform QoS control on the data stream sent to the fixed network device, and improve the service quality after the offloading.

As another implementation manner, in conjunction with the description for FIG. 3 or FIG. 4, the CP functional entity may also perform S309 at any time between S303 and S306, and send a policy request to the policy function entity without executing 308; or The CP function entity may also execute S411 at any time between S407 and S409 to send a policy request to the policy function entity without executing S410. The policy request includes the identifier of the UE, so as to obtain the offload policy information of the UE from the policy function entity. Then, the policy response in S311 or S412 includes the offload policy information of the UE. The offload policy information of the UE refers to the description of S310.

Then, the CP function entity sends a subscription request to the offloading device (such as the N3G-GW or the UP function entity) to subscribe to the traffic that is allowed to be offloaded to the UE. The foregoing subscription request includes the identifier of the UE and the service description information of the service that allows the traffic to be offloaded. After receiving the subscription request sent by the CP function entity, the traffic distribution device monitors the data stream sent to the UE based on the UE identifier carried in the subscription request, and acquires and sends data to the UE after monitoring the data stream sent to the UE. The business description information of the flow of the business. Then, the traffic distribution device determines whether the service corresponding to the data flow sent to the UE is allowed to be offloaded according to the service description information of the data flow that is sent to the UE and the service description information of the service that is allowed to be offloaded in the subscription request. And when it is determined to be YES, the subscription response is returned to the CP function entity, and the subscription response includes description information of the service that allows the traffic to be offloaded. Then, the CP function entity determines the identifier of the fixed network device corresponding to the identifier of the UE and the type of the fixed network device according to the correspondence between the identifier of the UE and the identifier of the fixed network device and the type of the fixed network device stored in S304 or S403, and determines according to the determined The type of fixed network device obtains a QoS parameter corresponding to the type of the fixed network device. Then, the CP function entity performs S311 or S413 to send a offload request to the offloading device (such as the N3G-GW or the UP function entity), and the offloading request refers to the description of S311. Then, the offloading device (such as an N3G-GW or UP functional entity) performs S312 or S414.

By describing, the CP function binds the identifier of the fixed network device and the type of the fixed network device with the same access point to the UE after the mobile network device (such as the UE) initiates the session request. In addition, the CP function entity obtains the QoS parameters of the fixed network device and the service description information of the service that is allowed to be offloaded according to the identifier of the fixed network device and the type of the fixed network device that are bound to the mobile network device. And the traffic offloading device, such as the N3G-GW or the UP function entity, is subscribed to the data stream of the service that allows the traffic offloading to the UE. After receiving the subscription request, the traffic distribution device monitors the data flow sent to the UE, and sends a subscription response to the CP function entity after the N3G-GW or the UP function entity determines that the data stream sent to the UE is a data flow of the traffic that is allowed to be offloaded. The offloading request is then sent by the CP function entity to the offloading device, so that the offloading device sends the data stream sent to the UE to the fixed network device based on the QoS parameter. Therefore, the network side can perform QoS control on the data stream sent to the fixed network device, and improve the service quality after the offloading.

The solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the network elements. It can be understood that the above-mentioned implementation of the CP functional entity, the N3G-GW, the UP functional entity, and the mobile network device, in order to implement the above functions, include hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiments of the present invention may perform the division of functional units on the foregoing devices or entities according to the foregoing method examples. For example, each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software function module. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module by using corresponding functions, FIG. 5 shows a possible structural diagram of a shunting device (such as an N3G-GW or an UP functional entity) involved in the foregoing embodiment, and the shunting device 500 includes: a receiving unit 501, a determining unit 502, and a transmitting unit 503. Further, the offloading device may further include an obtaining unit 504.

Specifically, the receiving unit 501 is configured to receive a split request sent by the control plane CP function entity, where the offload request includes description information of the service that allows the offload, an identifier of the mobile device, and an identifier of the fixed network device, and is configured to receive and send. a downlink data stream to the mobile device; the mobile device and the fixed network device indicated by the fixed network device identifier have a common access point; and the determining unit 502 is configured to use, according to the description information of the traffic split service Determining, by the transmitting unit 503, the downlink data stream to be sent to the fixed network device according to the identifier of the fixed network device.

Further, the obtaining unit 504 is configured to obtain the QoS parameter, and the sending unit 503 sends the downlink data stream to the fixed network device according to the identifier of the fixed network device, where the sending unit is based on the The QoS parameters will send the downstream data stream to the fixed network device.

Further, the acquiring unit 504 obtains the QoS parameter of the QoS as follows:

The offloading request includes the QoS parameter subscribed by the mobile network device, the acquiring unit 504 acquires the type of the fixed network device, and obtains the QoS parameter signed by the mobile network device from the QoS parameter signed by the mobile network device. Type corresponding QoS parameter; or

The offloading request includes a QoS parameter corresponding to the type of the fixed network device, and the obtaining unit 504 obtains a QoS parameter corresponding to the type of the fixed network device from the offloading request; or

The obtaining unit 504 will obtain the default quality of service QoS parameters of the data stream sent to the fixed network device.

Further, the receiving unit 501 is further used for a subscription request sent by the CP function entity, where the subscription request includes an identifier of the UE and service description information of the service that allows the offloading;

The determining unit 502 monitors the data stream sent to the UE based on the UE identifier carried in the subscription request, and determines, according to the service description information included in the subscription request, that the service corresponding to the data stream sent to the mobile network device is allowed to be offloaded. business;

The sending unit 503 is further configured to: return a subscription response to the CP function entity, where the subscription response includes the identifier of the mobile network device and the description information of the service corresponding to the data stream that is being sent to the mobile network device, where The description information of the service that allows the offloading is the description information of the service corresponding to the data flow that is being sent to the mobile network device.

FIG. 6 is a diagram of supporting a non-3rd generation partnership program non-3GPP access network according to an embodiment of the present invention; turn off. The access gateway includes: an obtaining unit 601 and a sending unit 602. Further, the access gateway may further include a receiving unit 603, a storage unit 604, and a determining unit 605.

Specifically, the obtaining unit 601 is configured to acquire an identifier of the fixed network device and an identifier of the mobile network device, where the fixed network device and the mobile network device have the same access point;

The sending unit 602 is configured to send the identifier of the fixed network device and the identifier of the mobile network device to a control CP function entity, where the identifier of the fixed network device and the identifier of the mobile network device are used to indicate that the offload device is to be sent to The downlink data stream of the mobile network device is sent to the fixed network device.

Optionally, after the gateway establishes a connection with the fixed network device by using a connection point of the fixed network device, the acquiring unit 601 is further configured to use an identifier of the access point of the fixed network device;

The storage unit 604 is configured to store a correspondence between an identifier of the fixed network device and an identifier of an access point of the fixed network device;

The receiving unit 603 is configured to receive a session request sent by the mobile network device.

The obtaining unit 601 is further configured to acquire, according to the session request, an identifier of the mobile network device and an identifier of an access point of the mobile network device;

The obtaining unit 601 obtains the identifier of the fixed network device and the identifier of the mobile network device, which is specifically: according to the identifier of the access point of the mobile network device, the identifier of the stored fixed network device and the access of the fixed network device Obtaining, in a correspondence between the identifiers of the points, an identifier of the fixed network device having the same access point as the mobile network device, and acquiring an identifier of the mobile network device from the session request.

Optionally, the receiving unit 603 is further configured to receive a session request sent by the mobile network device, where the session request includes an identifier of the mobile network device and an identifier of the fixed network device.

Optionally, the session request further includes an access point identifier of the mobile network device, and the sending unit 602 further sends the access point identifier of the mobile network device to the CP function entity.

Optionally, the receiving unit 603 is further configured to: receive a request for establishing a session sent by the CP function entity, where the request for establishing a session includes an identifier of the fixed network device included in the session request, and the access The identifier of the point;

The determining unit 605 is further configured to determine a label of the fixed network device included in the session request. Whether the fixed network device indicated by the identifier of the fixed network device is registered at an access point indicated by the identifier of the access point;

The sending unit 602 is further configured to send a response to establish a session to the CP function entity, where the response to the establishment session includes the successful registration in the access point corresponding to the access point identifier included in the session request. The identity of the fixed network device.

Optionally, the determining unit 605 is further configured to: determine whether the fixed network device indicated by the identifier of the fixed network device included in the session request is registered at an access point indicated by the identifier of the access point;

The sending unit 602 sends the identifier of the fixed network device and the identifier of the mobile network device to the control CP function entity, where the identifier of the mobile network device is corresponding to the identifier of the access point. The identifier of the fixed network device successfully registered in the access point is sent to the CP functional entity.

It should be noted that the access gateway in FIG. 6 can also be used to perform any steps performed by the N3G-GW of FIG. 3 and FIG. 4, and the embodiments of the present invention are not described in detail herein.

FIG. 7 is a CP functional entity according to an embodiment of the present invention. The CP functional entity includes: a receiving unit 701, an obtaining unit 702, and a transmitting unit 703. Further, the CP functional entity may further include a storage unit 705 and a determining unit 704.

Specifically, the receiving unit 701 receives the identifier of the mobile network device and the identifier of the fixed network device that are sent by the non-3rd generation partnership plan non-3GPP access gateway;

The obtaining unit 702 is configured to obtain service description information of a service that allows the offloading of the mobile network device indicated by the identifier of the mobile network device;

The sending unit 703 is configured to send a offloading request to the offloading device, where the offloading request includes description information of the service that allows the offloading, an identifier of the mobile network device, and an identifier of the fixed network device; the offloading request is used to indicate And sending, according to the identifier of the fixed network device, the downlink data stream of the mobile network device indicated by the identifier sent to the mobile network device to the fixed network device.

Optionally, the sending unit 703 is further configured to: send a policy request to the policy entity, where the policy request includes an identifier of the mobile network device;

The receiving unit 701 is further configured to: receive a policy response sent by the policy entity, where the policy response includes the offloading policy information that is signed by the mobile network device, where the offloading policy information includes the service that is subscribed by the mobile network device. The service description information of the service that is subscribed by the mobile network device includes the service description information of the service that allows the offloading.

Optionally, the receiving unit 701 is further configured to receive a session modification request sent by the mobile network device, where the session modification request includes an identifier of the mobile network device, an identifier of the fixed network device, and a service description of the service to be offloaded. information;

The CP function entity further includes a determining unit 704, configured to determine, according to the service description information of the service that is allowed to be offloaded by the mobile network device that is included in the traffic policy information, the service that needs to be offloaded in the session modification request The description information is the service description information that allows the traffic to be offloaded, and the service description information of the traffic that is allowed to be offloaded is the service description information of the service to be offloaded in the session modification request.

Optionally, the sending unit 703 is further configured to: send a subscription request to the offloading device, where the subscription request includes an identifier of the mobile network device and description information of a service subscribed by the mobile network device;

The receiving unit 701 is further configured to receive a subscription response returned by the offloading device, where the subscription response includes an identifier of the mobile network device and description information of a service corresponding to a data flow that is being sent to the mobile network device And the description information of the service that allows the offloading is the description information of the service corresponding to the data flow that is being sent to the mobile network device.

Optionally, the receiving unit 701 is further configured to receive the type of the fixed network device, where the policy request includes a type of the fixed network device, where the offload policy information further includes a type of the fixed network device. Corresponding QoS parameters; the offload request further includes a QoS parameter corresponding to the type of the fixed network device, where the QoS parameter is used to control when the downlink data stream is sent to the fixed network device.

Optionally, the receiving unit 701 is further configured to receive the type of the fixed network device; the offload policy information further includes a QoS parameter subscribed by the mobile network device;

The determining unit 704 is further configured to determine, in the QoS parameters subscribed by the mobile network device, a QoS parameter corresponding to the type of the fixed network device;

The offload request further includes a QoS parameter corresponding to the type of the fixed network device, and the QoS parameter is used to control when the downlink data stream is sent to the fixed network device.

Optionally, the receiving unit 701 further receives, by the CP function entity, a session request sent by the non-3GPP access gateway, where the session request carries an identifier of the fixed network device, and an identifier of the mobile network device. a fixed network indication indicated by the identifier of the fixed network device carried in the session request The mobile network device indicated by the identifier of the mobile network device has the same access point;

The CP function entity further includes a storage unit 705, configured to store a correspondence between the identifier of the fixed network device and the identifier of the network device;

The determining unit 704 is further configured to determine a type of the fixed network device according to the identifier of the fixed network device, and store a correspondence between the type of the fixed network device and the identifier of the fixed network device.

Optionally, the session request further includes an identifier of the access point of the mobile network device, and the method further includes: the sending unit 703 is further configured to send a session establishing session to the non-3GPP access gateway. The request for establishing a session includes an identifier of the fixed network device included in the session request, and an identifier of the access point;

The receiving unit 701 is further configured to: a response to establish a session returned by the non-3GPP access gateway, where the response to the establishment session includes an access point corresponding to the access point identifier included in the session request The identifier of the fixed network device successfully registered;

The CP function entity further includes a deleting unit 706, configured to delete the stored identifier of the fixed network device and the type of the fixed network device that are not successfully registered according to the response to the establishment of the session.

It should be noted that the CP function entity in FIG. 7 can also be used to perform any steps performed by the CP function entity of FIG. 3 and FIG. 4, and the embodiments of the present invention are not described in detail herein.

FIG. 8 is a mobile network device according to an embodiment of the present invention. The mobile network device includes a receiving unit 801, a storage unit 802, and a transmitting unit 803. Further, the mobile network device may further include an identification unit 804.

Specifically, the receiving unit 801 is configured to receive a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, and the fixed network device indicated by the identifier of the fixed network device and the mobile network device Have the same access point;

a storage unit 802, configured to store an identifier of the fixed network device;

The sending unit 803 is configured to send a session modification request to the CP function entity, where the mobile network device receives the data packet of the service, where the session modification request carries the identifier of the mobile network device, and the fixed network The identifier of the device and the service description information of the service; the session modification request is used to trigger an identifier indication that the data stream sent to the mobile network device is sent to the fixed network device according to the service description information of the service Fixed network equipment.

Optionally, the mobile network device further includes an identifying unit 804 for the mobile network After the device establishes a connection with the fixed network device, identifying an identifier of the fixed network device that establishes a connection with the mobile network device;

The sending unit 803 is further configured to send a session request, where the session request carries an identifier of the mobile network device and an identifier of the identified fixed network device that establishes a connection with the mobile network device, where the session establishment is ringing The identity of the fixed network device in the middle is included in the identified identity of the fixed network device that establishes a connection with the mobile network device.

It should be noted that the mobile network device of FIG. 7 can also be used to perform any steps performed by the mobile network device of FIG. 3 and FIG. 4, and the embodiments of the present invention are not described in detail herein.

The embodiment of the present invention further provides a computer storage medium for storing computer software instructions used by the CP function entity, the mobile network device, the non-3GPP access gateway, and the UP function entity, respectively, for executing the foregoing method. The program designed by the embodiment. By executing the stored program, the flow between the fixed network device and the mobile network device can be realized.

Although the present invention has been described herein in connection with the embodiments of the present invention, it will be understood by those skilled in the <RTIgt; Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code. The computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of the methods, apparatus, and computer program products of the embodiments of the invention. It will be understood that each flow and/or block of the flowcharts and/or block diagrams, and the flow and/or block of the flowcharts and/or block diagrams can be implemented by computer program instructions. Hehe. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the invention has been described with respect to the specific embodiments and embodiments thereof, various modifications and combinations may be made without departing from the spirit and scope of the invention. Accordingly, the specification and drawings are to be construed as the It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims (43)

A method for offloading between a fixed network device and a mobile network device is applied to a system for supporting a non-3rd generation partnership program non-3GPP access technology to access a core network, wherein the method includes: The control plane CP function entity receives the identifier of the mobile network device and the identifier of the fixed network device sent by the non-3rd generation partnership plan non-3GPP access gateway, the mobile network device and the fixed network device having the same access point; The CP function entity obtains the description information of the service that is allowed to be offloaded, and sends a traffic distribution request to the traffic distribution device, where the traffic distribution request includes the description information of the service that allows the traffic distribution, the identifier of the mobile network device, and the identifier of the fixed network device; The offloading device receives a downlink data stream that is sent to the mobile network device, where the downlink data stream belongs to a data stream of the service described by the description information of the service that allows the offloading; The offloading device sends the downlink data stream to the fixed network device according to the identifier of the fixed network device. The method according to claim 1, wherein before the sending of the offloading request by the CP function entity to the offloading device, the method further comprises: a subscription request sent by the CP function entity to the offloading device, where the subscription request includes an identifier of the mobile network device and description information of a service subscribed by the mobile network device; Determining, according to the description information of the service subscribed by the mobile network device, that the service corresponding to the data flow that is being sent to the mobile network device belongs to the service description information of the service subscribed by the mobile network device; The offloading device returns a subscription response to the CP functional entity, where the subscription response includes an identifier of the mobile network device and description information of a service corresponding to a data flow that is being sent to the mobile network device, where the traffic is allowed to be offloaded The description information is description information of the service corresponding to the data stream being sent to the mobile network device. The method according to claim 1 or 2, wherein the offloading device is the non-3GPP access gateway or user plane UP functional entity. The method according to any one of claims 1-3, wherein the control plane CP function entity receives the label of the mobile network device sent by the non-3rd generation partnership plan non-3GPP access gateway Before identifying the identification of the fixed network device, the method further includes: The non-3GPP access gateway acquires an identifier of the fixed network device and an identifier of the mobile network device. The method according to claim 4, wherein before the non-3GPP access gateway acquires the identifier of the fixed network device and the identifier of the mobile network device, the method further includes: After the fixed network device establishes a connection with the non-3GPP access gateway, the non-3GPP access gateway acquires an identifier of the fixed network device and an identifier of an access point of the fixed network device; The non-3GPP access gateway stores a correspondence between an identifier of the fixed network device and an identifier of an access point of the fixed network device. The method according to claim 5, wherein after the non-3GPP access gateway stores the identifier of the fixed network device and the identifier of the access point of the fixed network device, the The identifier of the fixed network device and the identifier of the mobile network device obtained by the non-3GPP access gateway are specifically: Receiving, by the non-3GPP access gateway, a session request sent by the mobile network device; Obtaining, by the non-3GPP access gateway, an identifier of the mobile network device and an identifier of an access point of the mobile network device according to the session request; And obtaining, by the non-3GPP access gateway, the mobile device from the corresponding relationship between the identifier of the fixed network device and the identifier of the access point of the fixed network device according to the identifier of the access point of the mobile network device The network device has the identity of the fixed network device of the same access point. The method according to claim 4, wherein the identifier of the fixed network device and the identifier of the mobile network device are obtained by the non-3GPP access gateway: The non-3GPP access gateway receives a session request sent by the mobile network device, where the session request includes an identifier of the mobile network device and an identifier of the fixed network device. The method of any of claims 4-7, wherein the method further comprises: The non-3GPP access gateway obtains the type of the fixed network device according to the identifier of the fixed network device, and stores the correspondence between the identifier and the type of the fixed network device. The method according to claim 7, wherein the session request further includes an identifier of an access point of the mobile network device; The method further includes: Receiving, by the non-3GPP access gateway, a request for establishing a session sent by the CP function entity, where the request for establishing a session includes an identifier of a fixed network device included in the session request and an access point of the mobile network device Identification The non-3GPP access gateway sends a response to establish a session to the CP function entity, where the response to the establishment session includes the successful registration in the access point corresponding to the access point identifier included in the session request. The identification of the fixed network equipment. The method according to any one of claims 1-9, wherein before the CP function entity acquires service description information of a service that allows the offloading, the method further includes: Sending, by the CP function entity, a policy request to a policy entity, where the policy request includes an identifier of the mobile network device; Receiving a policy response sent by the policy entity, where the policy response includes the offloading policy information subscribed by the mobile network device, where the offloading policy information includes description information of the service subscribed by the mobile network device. The method according to claim 10, wherein before the sending of the policy request by the CP function entity to the policy function entity, the method further comprises: Receiving, by the CP function entity, a session modification request sent by the mobile network device, where the session modification request includes an identifier of the mobile network device, an identifier of the fixed network, and a data flow that is being sent to the mobile network device. Corresponding information of the corresponding service; The description information of the service that the CP function entity obtains the traffic that is allowed to be offloaded is specifically: the policy request includes the description information of the service corresponding to the data flow of the mobile network device, and the service that the CP function entity subscribes according to the mobile network device The description information determines that the description information of the corresponding service of the data stream that is being sent to the mobile network device is the description information of the service that allows the offloading. The method according to claim 10 or 11, wherein the method further comprises: The CP function entity acquires the type of the fixed network device, where the offload request further includes the type of the fixed network device, and the offload policy information further includes a quality of service QoS parameter corresponding to the solid device type; or The CP function entity acquires the type of the fixed network device, where the policy response includes a QoS parameter corresponding to each fixed network device type subscribed by the mobile network device, and the CP function entity is contracted according to the mobile network device. The QoS parameters corresponding to the fixed network device type are obtained. And taking a QoS parameter corresponding to the type of the fixed network device included in the session. The method according to claim 12, wherein the CP function entity obtains a quality of service QoS parameter corresponding to the type of the fixed network device, specifically: The policy request further includes the type of the fixed network device, where the policy response further includes a QoS parameter corresponding to a type of the fixed network device; or The policy response includes a QoS parameter corresponding to the type of the fixed network device that is subscribed by the mobile network device, and the CP function entity acquires the QoS parameter corresponding to each fixed network device type that the mobile network device subscribes to. a QoS parameter corresponding to the type of the fixed network device included in the session. The method of any of claims 1-13, wherein the method further comprises: The offloading device acquires a quality of service QoS parameter of a data stream sent to the fixed network device; The offloading device performs QoS control on the data stream sent to the fixed network device based on the QoS parameter in the process of transmitting the downlink data stream to the fixed network device. The method according to claim 14, wherein the service quality QoS parameter of the data stream sent by the traffic distribution device to the fixed network device is specifically: the traffic distribution device acquires a default data stream sent to the fixed network device. a quality of service QoS parameter; or the offloading device obtains a quality of service QoS parameter of the data stream sent to the fixed network device from the offloading request, and the QoS parameter of the data stream sent to the fixed network device is the fixed network The QoS parameter corresponding to the type of device. The method according to claim 6 or 7, wherein the CP function entity further receives an identifier of an access point of the mobile network device from the non-3GPP access gateway; the method further comprising: The CP function entity sends a request for establishing a session to the non-3GPP access gateway, where the request for establishing a session includes an identifier of the fixed network device included in the session request, and an identifier of the access point; The CP function entity accesses the response of the non-3GPP access gateway to establish a session, and the response to the establishment session includes the success of the access point corresponding to the access point identifier included in the session request. The identity of the registered fixed network device; The CP functional entity deletes the stored unsuccessful registration according to the response to the establishment of the session The identification of the fixed network equipment and the type of fixed network equipment. A method for offloading between a fixed network device and a mobile network device, which is applied to a system for supporting a non-3rd generation partnership program non-3GPP access technology to access a fifth generation 5G core network, wherein the method includes : Receiving, by the mobile network device, a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, where the fixed network device indicated by the identifier of the fixed network device has the same access point as the mobile network device ; Storing an identifier of the fixed network device; Transmitting, in the process of receiving the data packet of the service, the session modification request to the CP function entity, where the session modification request carries the identifier of the mobile network device, the identifier of the fixed network device, and the The service description information of the service; the session modification request is used to trigger the fixed network device that sends the data flow sent to the mobile network device to the identifier of the fixed network device according to the service description information of the service. The method of claim 17, wherein the method further comprises: After the mobile network device establishes a connection with the fixed network device, identifying an identifier of the fixed network device that establishes a connection with the mobile network device; a session request sent by the mobile network device, where the session request carries an identifier of the mobile network device and an identifier of the identified fixed network device that establishes a connection with the mobile network device, where the session establishment is ringing The identifier of the fixed network device is included in the identified identifier of the fixed network device that establishes a connection with the mobile network device. A power distribution device is applied to a system for supporting a non-3rd generation partnership program non-3GPP access technology to access a core network, wherein the power distribution device includes: a receiving unit, configured to receive a split request sent by a control plane CP function entity, where the offload request includes description information of a service that allows offloading, an identifier of the mobile device, and an identifier of the fixed network device; and is configured to receive and send to the mobile device a downlink data stream; the mobile device and the fixed network device indicated by the fixed network device identifier have a common access point; a determining unit, configured to determine, according to the description information of the offloaded service, the downlink data flow as a data flow of the traffic offloaded service; a sending unit, configured to send the downlink data stream to the solid according to an identifier of the fixed network device Network equipment. The flow dividing device according to claim 19, further comprising an acquiring unit, The obtaining unit is configured to: obtain a quality of service QoS parameter; And sending, by the sending unit, the downlink data stream to the fixed network device according to the identifier of the fixed network device, where the sending unit sends the downlink data stream to the fixed network based on the QoS parameter device. The offloading device according to claim 20, wherein the acquiring unit obtains the quality of service QoS parameter specifically: The offloading request includes the QoS parameter signed by the mobile network device, the acquiring unit acquires the type of the fixed network device, and obtains the type of the fixed network device from the QoS parameter signed by the mobile network device. Corresponding QoS parameters; or The offloading request includes a QoS parameter corresponding to the type of the fixed network device, and the obtaining unit acquires a QoS parameter corresponding to the type of the fixed network device from the offloading request; or The obtaining unit will obtain a default quality of service QoS parameter of the data stream sent to the fixed network device. The flow dividing device according to claims 19-21, characterized in that: The receiving unit is further used for a subscription request sent by the CP function entity, where the subscription request includes an identifier of the UE and service description information of a service that allows the offloading; The determining unit monitors the data stream sent to the UE based on the UE identifier carried in the subscription request, and determines, according to the service description information included in the subscription request, the service corresponding to the data stream sent to the mobile network device as a service that allows the offloading ; The sending unit is further configured to: return a subscription response to the CP function entity, where the subscription response includes the identifier of the mobile network device and description information of a service corresponding to the data stream being sent to the mobile network device, The description information of the traffic that is allowed to be offloaded is the description information of the service corresponding to the data flow that is being sent to the mobile network device. A non-3 third generation partnership program supporting a non-3GPP access gateway, wherein the gateway includes: An acquiring unit, configured to acquire an identifier of the fixed network device and an identifier of the mobile network device, where the fixed network device and the mobile network device have the same access point; a sending unit, configured to send the identifier of the fixed network device and the identifier of the mobile network device to a control CP function entity, where the identifier of the fixed network device and the identifier of the mobile network device are used to indicate that the offload device sends The downlink data stream to the mobile network device is sent to the fixed network device. The access gateway according to claim 23, wherein after the gateway establishes a connection with the fixed network device through a connection point of the fixed network device, the acquiring unit is further used for the fixed network device The identity of the access point; The gateway further includes a storage unit, configured to store a correspondence between an identifier of the fixed network device and an identifier of an access point of the fixed network device; a receiving unit, configured to receive a session request sent by the mobile network device; The obtaining unit is further configured to acquire, according to the session request, an identifier of the mobile network device and an identifier of an access point of the mobile network device; Obtaining, by the acquiring unit, the identifier of the fixed network device and the identifier of the mobile network device, according to the identifier of the access point of the mobile network device, from the identifier of the stored fixed network device and the access point of the fixed network device Obtaining, in a correspondence between the identifiers, an identifier of the fixed network device having the same access point as the mobile network device, and acquiring an identifier of the mobile network device from the session request. The access gateway of claim 23, wherein: The receiving unit is further configured to receive a session request sent by the mobile network device, where the session request includes an identifier of the mobile network device and an identifier of the fixed network device. The access gateway according to claim 24 or 25, characterized in that: The session request further includes an access point identifier of the mobile network device, and the sending unit further sends an access point identifier of the mobile network device to the CP functional entity. The access gateway of claim 26, wherein: The receiving unit is further configured to: receive a request for establishing a session sent by the CP function entity, where the request for establishing a session includes an identifier of the fixed network device included in the session request and an identifier of the access point; The determining unit is further configured to: determine whether the fixed network device of the fixed network device included in the session request that identifies the identifier of the fixed network device is registered at an access point indicated by the identifier of the access point; The sending unit is further configured to send a response to establish a session to the CP function entity, where The response to the establishment of the session includes the identifier of the fixed network device successfully registered in the access point corresponding to the access point identifier included in the session request. The access gateway according to claim 26, wherein the determining unit is further configured to: determine whether the fixed network device indicated by the identifier of the fixed network device included in the session request is at the identifier of the access point Indicating access point registration; The sending unit sends the identifier of the fixed network device and the identifier of the mobile network device to the control CP function entity, where the identifier of the mobile network device is corresponding to the identifier of the access point The identifier of the fixed network device successfully registered in the ingress is sent to the CP functional entity. A control plane CP functional entity, comprising: a receiving unit, configured to receive an identifier of the mobile network device and an identifier of the fixed network device sent by the non-3rd generation partnership plan non-3GPP access gateway; An obtaining unit, configured to acquire service description information of a service that allows the offloading of the mobile network device indicated by the identifier of the mobile network device; a sending unit, configured to send a offloading request to the offloading device, where the offloading request includes description information of the service that allows the offloading, an identifier of the mobile network device, and an identifier of the fixed network device; And indicating to send, according to the identifier of the fixed network device, the downlink data stream of the mobile network device indicated by the identifier sent to the mobile network device to the fixed network device. The CP functional entity according to claim 29, characterized in that: The sending unit is further configured to send a policy request to the policy entity, where the policy request includes an identifier of the mobile network device; The receiving unit is further configured to: receive a policy response sent by the policy entity, where the policy response includes the offloading policy information subscribed by the mobile network device, where the offloading policy information includes a service of the service subscribed by the mobile network device Description; The service description information of the service subscribed by the mobile network device includes the service description information of the service that allows the offloading. The CP functional entity according to claim 30, characterized in that: The receiving unit is further configured to receive a session modification request sent by the mobile network device, where the session modification request includes an identifier of the mobile network device, an identifier of the fixed network device, and service description information of the service to be offloaded; The CP function entity further includes a determining unit, configured to determine, according to the service description information of the service that is allowed to be offloaded by the mobile network device that is included in the traffic distribution information, to determine the traffic to be split included in the session modification request. The service description information of the service is service description information that allows the traffic to be offloaded, and the service description information of the service that is allowed to be offloaded is the service description information of the service to be offloaded in the session modification request. The CP functional entity according to claim 30, characterized in that: The description information of the service that allows the offloading is the service description information of the service subscribed by the mobile network device; The service description information of the service that is signed by the mobile network device, is used to indicate that the traffic distribution device determines whether the description information of the service corresponding to the data flow that is being sent to the mobile network device is included in the service of the service signed by the mobile network device. Description. The CP functional entity according to claim 30, characterized in that: The sending unit is further configured to: send a subscription request to the offloading device, where the subscription request includes an identifier of the mobile network device and description information of a service subscribed by the mobile network device; The receiving unit is further configured to receive a subscription response returned by the offloading device, where the subscription response includes an identifier of the mobile network device and description information of a service corresponding to a data flow that is being sent to the mobile network device, where The description information of the traffic that is allowed to be offloaded is description information of a service corresponding to the data flow that is being sent to the mobile network device. A CP functional entity according to any of claims 30-33, characterized in that: The receiving unit is further configured to receive the type of the fixed network device, where the policy request includes a type of the fixed network device, where the offload policy information further includes a QoS parameter corresponding to a type of the fixed network device; The offload request further includes a QoS parameter corresponding to the type of the fixed network device, and the QoS parameter is used to control when the downlink data stream is sent to the fixed network device. A CP functional entity according to any of claims 31-33, characterized in that: The receiving unit is further configured to receive the type of the fixed network device; the offloading policy information further includes a QoS parameter subscribed by the mobile network device; The determining unit is further configured to determine, in the QoS parameter signed by the mobile network device, The QoS parameters corresponding to the type of the fixed network device; The offload request further includes a QoS parameter corresponding to the type of the fixed network device, and the QoS parameter is used to control when the downlink data stream is sent to the fixed network device. A CP functional entity according to any of claims 29-35, characterized in that The receiving unit further receives, by the CP function entity, a session request sent by the non-3GPP access gateway, where the session request carries an identifier of the fixed network device, an identifier of the mobile network device, and the session request The fixed network device carried in the identifier of the fixed network device and the mobile network device indicated by the identifier of the mobile network device have the same access point; The CP function entity further includes a storage unit, configured to store a correspondence between the identifier of the fixed network device and the identifier of the network device; The determining unit is further configured to determine a type of the fixed network device according to the identifier of the fixed network device, and store a correspondence between the type of the fixed network device and the identifier of the fixed network device. The CP function entity according to claim 36, wherein the session request further includes an identifier of an access point of the mobile network device; the method further comprising: The sending unit is further configured to send a request for establishing a session to the non-3GPP access gateway, where the request for establishing a session includes an identifier of a fixed network device included in the session request, and the access point Identification The receiving unit is further configured to: a response to establish a session returned by the non-3GPP access gateway, where the response to the establishment session includes the access point corresponding to the access point identifier included in the session request The identity of the successfully registered fixed network device; The CP function entity further includes a deleting unit, configured to delete the stored identifier of the fixed network device and the type of the fixed network device that are not successfully registered according to the response to the establishment of the session. A mobile network device, which is applied to a system that supports a non-3rd generation partnership program non-3GPP access technology to access a fifth generation 5G core network, wherein the mobile network device includes: a receiving unit, configured to receive a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, where the fixed network device indicated by the identifier of the fixed network device has the same connection as the mobile network device Entry point a storage unit, configured to store an identifier of the fixed network device; a sending unit, configured to: when the mobile network device receives a data packet of a service, The CP function entity sends a session modification request, where the session modification request carries an identifier of the mobile network device, an identifier of the fixed network device, and service description information of the service; the session modification request is used to trigger according to the service The service description information is sent to the fixed network device indicated by the identifier of the fixed network device by the data stream sent to the mobile network device. The mobile network device according to claim 38, wherein the mobile network device further comprises an identification unit, configured to identify that the mobile network device establishes a connection with the mobile network device after establishing a connection with the fixed network device Identification of fixed network equipment; The sending unit is further configured to send a session request, where the session request carries an identifier of the mobile network device and an identifier of the identified fixed network device that establishes a connection with the mobile network device, where the session establishment is ringing The identifier of the fixed network device in the identifier is included in the identified identifier of the fixed network device that establishes a connection with the mobile network device. A shunt device, including the following features, comprising: a memory for storing computer executable program code; Transceiver, and a processor coupled to the memory and the transceiver; Wherein the program code includes instructions that, when executed by the processor, cause the shunt device to perform the following operations: Receiving a shunt request sent by the control plane CP function entity, where the offload request includes description information of the service that allows the offload, an identifier of the mobile device, and an identifier of the fixed network device; and a downlink data stream that is sent to the mobile device; The fixed network device indicated by the mobile device and the fixed network device identifier has a common access point; Determining, by the traffic distribution device, that the downlink data flow is a data flow of the traffic offloaded service according to the description information of the traffic offloaded service; And sending the downlink data stream to the fixed network device according to the identifier of the fixed network device. A non-3 third generation partnership program supporting a non-3GPP access gateway, including: a memory for storing computer executable program code; Transceiver, and a processor coupled to the memory and the transceiver; Wherein the program code includes instructions that, when executed by the processor, cause the access gateway to perform the following operations: Obtaining an identifier of the fixed network device and an identifier of the mobile network device, where the fixed network device and the mobile network device have the same access point; Sending the identifier of the fixed network device and the identifier of the mobile network device to a control CP function entity, where the identifier of the fixed network device and the identifier of the mobile network device are used to indicate that the offload device is to be sent to the mobile network device The downstream data stream is sent to the fixed network device. A control plane CP functional entity, comprising: a memory for storing computer executable program code; Transceiver, and a processor coupled to the memory and the transceiver; Wherein the program code includes instructions that, when executed by the processor, cause the CP functional entity to perform the following operations: Receiving an identifier of the mobile network device and an identifier of the fixed network device sent by the non-3rd Generation Partnership Project non-3GPP access gateway; Obtaining service description information of the mobile network device that is allowed to be offloaded by the identifier of the mobile network device; Sending a offloading request to the offloading device, where the offloading request includes description information of the service that allows the offloading, an identifier of the mobile network device, and an identifier of the fixed network device; the offloading request is used to indicate according to the solid The identifier of the network device sends the downlink data stream of the mobile network device indicated by the identifier sent to the mobile network device to the fixed network device. A control plane CP functional entity, comprising: a memory for storing computer executable program code; Transceiver, and a processor coupled to the memory and the transceiver; Wherein the program code includes instructions that, when executed by the processor, cause the CP functional entity to perform the following operations: Receiving a session establishment response sent by the CP function entity, where the session establishment response includes an identifier of the fixed network device, where the fixed network device indicated by the identifier of the fixed network device is the same as the mobile network device Access point Storing an identifier of the fixed network device; Transmitting, in the process of receiving the data packet of the service, the session modification request to the CP function entity, where the session modification request carries the identifier of the mobile network device, the identifier of the fixed network device, and the The service description information of the service; the session modification request is used to trigger the fixed network device that sends the data flow sent to the mobile network device to the identifier of the fixed network device according to the service description information of the service.

Images