CN112469077B

CN112469077B - Method and device for forwarding service data packet

Info

Publication number: CN112469077B
Application number: CN201910848792.0A
Authority: CN
Inventors: 银宇; 戚彩霞
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-09-09
Filing date: 2019-09-09
Publication date: 2022-07-29
Anticipated expiration: 2039-09-09
Also published as: WO2021047443A1; CN112469077A

Abstract

A method and a device for forwarding a service data packet are used for ensuring normal operation of a service when a 4G network is accessed through a 5G technology. The method comprises the following steps: the service gateway receives a first downlink data packet sent by the data gateway, and determines a QoS flow identifier and a second IP address and a second TEID of a PDU session distributed by the access equipment according to a first IP address and a first TEID contained in the first downlink data packet; sending a second downlink data packet to the access equipment, wherein the second downlink data packet comprises the QoS flow identifier, a second IP address and a second TEID; or, the service gateway receives a first uplink data packet sent by the access device, and determines a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to a third IP address and a third TEID contained in the first uplink data packet and the QoS flow identifier; and sending a second uplink data packet to the data gateway, wherein the second uplink data packet comprises a fourth IP address and a fourth TEID.

Description

Method and device for forwarding service data packet

Technical Field

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

Background

Currently, in a fifth generation (5th generation, 5G) network, AN Access Network (AN) accesses AN access and mobility management function (AMF) through AN N2 interface, and a core network is implemented based on a Service Based Architecture (SBA).

The 5G network forwards a service data packet between the terminal device and the external data network through a User Plane Function (UPF) device and an access device, a tunnel is established between the access device and the user plane function device based on a Packet Data Unit (PDU) session, and service data packets related to all PDU sessions are transmitted in the tunnel.

The 5G network employs a large number of new technologies, such as a service framework, a hyperText transfer protocol (HTTP) or a transport security protocol (TLS), which are not used in the mobile communication network and are not mature at present. In addition, operators need to invest in building new infrastructure for 5G networks, and the investment cost is high. Therefore, the applications of 5G networks are also relatively limited.

Disclosure of Invention

The application provides a method and a device for forwarding a service data packet, which are used for ensuring normal operation of a service when a 4G network is accessed through a 5G technology.

In a first aspect, the present application provides a method for forwarding a service data packet, where the method may include: the method comprises the steps that a service gateway receives a first downlink data packet sent by a data gateway, wherein the first downlink data packet comprises a first Internet Protocol (IP) address and a first Tunnel Endpoint Identifier (TEID); the service gateway determines a QoS flow identifier and a second IP address and a second TEID of a Packet Data Unit (PDU) session distributed by access equipment according to the first IP address and the first TEID; the service gateway sends a second downlink data packet to the access device, wherein the second downlink data packet comprises the QoS flow identifier, the second IP address and the second TEID; or, the serving gateway receives a first uplink data packet sent by the access device, where the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier; the service gateway determines a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identification; and the service gateway sends a second uplink data packet to the data gateway, wherein the second uplink data packet comprises the fourth IP address and the fourth TEID.

By the method, when the 5G terminal equipment and the access equipment are accessed to the evolved packet core network, the service data packet of the terminal equipment can be forwarded normally, the normal operation of the service is ensured, and the service experience of a user is prevented from being influenced. That is, the method can ensure normal operation of the service when the 4G network is accessed by the 5G technology.

In one possible design, the serving gateway receives a session establishment request message sent by a mobility management device, where the session establishment request message includes an access type of a terminal device, and the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network; the service gateway allocates the third IP address and the third TEID of the packet data network PDN connection according to the access type; and the service gateway sends a session establishment response message to the mobile management equipment, wherein the session establishment response message comprises the third IP address and the third TEID. This completes the establishment of the session.

In one possible design, the serving gateway sends a setup bearer request message to the mobility management device, where the setup bearer request message includes the third IP address and the third TEID. So that the bearer establishment can be performed subsequently.

In one possible design, the serving gateway receives an update bearer request message or a first setup bearer response message sent by a mobility management device, where the update bearer request message or the first setup bearer response message includes the second IP address and the second TEID and the QoS flow identifier; the service gateway sends an update bearing response message to the mobile management equipment based on the update bearing request message; or, the service gateway sends a second bearer establishment response message to the data gateway based on the first bearer establishment response message. Thus, the bearer update can be carried out subsequently or the bearer establishment can be completed.

In a second aspect, the present application provides a method for forwarding a service data packet, where the method may include: the method comprises the steps that access equipment receives a first downlink data packet sent by a service gateway, wherein the first downlink data packet comprises a first Internet Protocol (IP) address and a first Tunnel Endpoint Identifier (TEID); the access equipment acquires a quality of service parameter in a quality of service (QoS) flow context corresponding to the first IP address and the first TEID; the access equipment sends a second downlink data packet to the terminal equipment according to the service quality parameter; or, the access device receives a first uplink data packet sent by the terminal device; the access equipment acquires a second IP address and a second TEID of the QoS flow distributed by the service gateway in the QoS flow context of the first uplink data packet; and the access equipment sends a second uplink data packet to the service gateway, wherein the second uplink data packet comprises the second IP address and the second TEID.

In one possible design, the access device receives a PDU session resource update request message or a PDU session resource establishment request message or a handover request message sent by a mobility management device, where the PDU session resource update request message or the PDU session resource establishment request message or the handover request message includes the QoS flow identifier, the second IP address, and the second TEID.

In one possible design, the access device sends a PDU session resource update response message or a PDU session resource establishment response message or a handover request response message to the mobility management device, where the PDU session resource update response message or the PDU session resource establishment response message or the handover request response message includes the first IP address and the first TEID of the QoS flow allocated to the downlink data packet by the access device.

In a third aspect, the present application provides a method for forwarding a service data packet, where the method may include: the method comprises the steps that mobile management equipment receives a first message, wherein the first message is used for establishing a PDU session or a bearer; the mobile management equipment sends a second message to a service gateway, wherein the second message comprises a bearing identifier; the mobile management equipment sends a third message to access equipment, wherein the third message comprises a QoS flow identifier; the bearer identification and the QoS flow identification are used for identifying one bearer of the terminal equipment; the first message is a PDU session establishment request message sent by the terminal equipment, the second message is a session establishment request message, and the third message is a PDU session resource establishment request message; or, the first message is a bearer establishment request message sent by the serving gateway, the second message is a bearer establishment response message, and the third message is a PDU session resource update request message; or the first message is a forwarding switching request message sent by the source-side mobile management device, the second message is a session establishment request message, and the third message is a switching request message; the first message, the second message and the third message are used for establishing a channel for forwarding a service data packet.

By the method, when the 5G terminal equipment and the access equipment are accessed to the evolved packet core network, the service data packet of the terminal equipment can be forwarded normally, the normal operation of the service is ensured, and the service experience of a user is prevented from being influenced. That is, the method can ensure normal operation of the service when the 5G technology is used for accessing the 4G network.

In a possible design, when the second message is a session establishment request message, the second message further includes an access type of the terminal device, where the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network.

In one possible design, the mobility management device receives a session establishment response message sent by the serving gateway, where the session establishment response message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing; the mobile management equipment sends a PDU session resource establishment request message or a switching request message to the access equipment, wherein the PDU session resource establishment request message or the switching request message comprises the first IP address and the first TEID; the mobile management equipment receives a PDU session resource establishment response message or a switching request response message sent by access equipment, wherein the PDU session resource establishment response message or the switching request response message comprises a second IP address and a second TEID allocated by the access equipment; wherein the second IP address and the second TEID are an IP address and a TEID of a PDU session or an IP address and a TEID of a QoS flow; and the mobile management equipment sends an update bearing request message to the service gateway, wherein the update bearing request message comprises the second IP address and the second TEID.

In one possible design, the update bearer request message further includes a QoS flow identifier.

In one possible design, the setup bearer request message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing; the mobile management equipment sends a PDU session resource updating request message to the access equipment; wherein, when the first address and the first TEID are an IP address and a TEID of a bearer, the PDU session resource update request message includes the first IP address and the first TEID, or when the first address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update request message does not include the first IP address and the first TEID; the mobile management equipment receives a PDU session resource updating response message sent by the access equipment; wherein, the PDU session resource update response message includes a second IP address and a second TEID allocated by the access device, and the second IP address and the second TEID are an IP address and a TEID of a QoS flow; or when the first IP address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update response message does not include an IP address and a TEID allocated by an access device; the mobile management equipment sends a response message for establishing the load bearing to the service gateway; the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID are an IP address and a TEID of a PDU session, the bearer establishment response message does not include an IP address and a TEID allocated by the access device; or, the bearer establishment response message includes the second IP address and the second TEID, where the second IP address and the second TEID are obtained by the mobility management device from a PDU session resource establishment response message or a handover request response message.

In one possible design, the setup bearer response message further includes the QoS flow identification.

In a fourth aspect, the present application further provides a service gateway, where the service gateway has a function of implementing the service gateway in the example of the first aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

In a possible design, the structure of the service gateway includes a processing unit and a communication unit, and these units may perform corresponding functions in the method example of the first aspect, for which specific reference is made to the detailed description in the method example, which is not described herein again.

In a possible design, the service gateway includes a communication interface and a processor, and optionally may further include a memory, where the communication interface is used for transceiving data (information or signals, etc.) and performing communication interaction with other devices in the communication system, and the processor is configured to support the service gateway to perform a corresponding function of the service gateway in the method according to the first aspect. The memory is coupled to the processor and holds the necessary program instructions and data for the service gateway.

In a fifth aspect, the present application further provides an access device, where the access device has a function of implementing the access device in the method example of the second aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

In a possible design, the structure of the access device includes a processing unit and a communication unit, and these units may perform corresponding functions in the method example of the second aspect, for which specific reference is made to the detailed description in the method example, which is not described herein again.

In a possible design, the structure of the access device includes a communication interface and a processor, and optionally may further include a memory, the communication interface is used for transceiving data (information or signals, etc.) and performing communication interaction with other devices in the communication system, and the processor is configured to support the access device to perform corresponding functions of the access device in the method of the second aspect. The memory is coupled to the processor and holds the necessary program instructions and data for the access device.

In a sixth aspect, the present application further provides a mobility management device, where the mobility management device has a function of implementing the mobility management device in the example of the method in the third aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

In a possible design, the structure of the mobility management device includes a processing unit and a communication unit, and these units may perform corresponding functions in the method example of the third aspect, for which specific reference is made to the detailed description in the method example, and details are not described herein.

In a possible design, the structure of the mobility management device includes a communication interface and a processor, and optionally may further include a memory, where the communication interface is used for transceiving data (information or signals, etc.) and performing communication interaction with other devices in the communication system, and the processor is configured to support the mobility management device to perform corresponding functions of the mobility management device in the method according to the third aspect. The memory is coupled to the processor and holds program instructions and data necessary for the mobility management device.

In a seventh aspect, the present application further provides a communication system, where the communication system at least includes the serving gateway, the access device, and the mobility management device mentioned in the above design. Further, the serving gateway in the communication system may perform any one of the methods performed by the serving gateway, and the access device in the communication system may perform any one of the methods performed by the access device and the mobility management device in the communication system may perform any one of the methods performed by the mobility management device.

In an eighth aspect, the present application provides a computer-readable storage medium having stored thereon computer-executable instructions, which, when invoked by the computer, are operable to cause the computer to perform any one of the above first aspect or any one of the possible designs of the first aspect, any one of the methods in any one of the possible designs of the second aspect or the second aspect, any one of the methods in any one of the possible designs of the third aspect or the third aspect.

In a ninth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the possible designs of the first aspect or the first aspect, any one of the methods of the second aspect or the any one of the possible designs of the second aspect, or any one of the methods of the third aspect or the any one of the possible designs of the third aspect as described above.

In a tenth aspect, the present application provides a chip, coupled to a memory, for reading and executing program instructions stored in the memory to implement the above first aspect or any one of the possible designs of the first aspect, any one method of the second aspect or any one of the possible designs of the second aspect, or any one method of the third aspect or any one of the possible designs of the third aspect.

Drawings

Fig. 1 is a schematic diagram of a 5G network in the prior art;

fig. 2a is a schematic architecture diagram of a communication system provided in the present application;

FIG. 2b is a diagram of a 4G NSA architecture provided herein;

fig. 3 is a flowchart of a method for forwarding a service data packet according to the present application;

fig. 4 is a flowchart of another method for forwarding service data packets according to the present application;

fig. 5 is a flowchart of another method for forwarding service data packets according to the present application;

fig. 6 is a flowchart of another method for forwarding service data packets according to the present application;

fig. 7 is a flowchart of another method for forwarding service data packets according to the present application;

fig. 8 is a flowchart of an example of a method for forwarding a service data packet according to the present application;

fig. 9 is a flowchart of an example of another method for forwarding service data packets provided in the present application;

fig. 10 is a flowchart of an example of another method for forwarding service data packets provided in the present application;

fig. 11 is a flowchart of an example of another method for forwarding service data packets provided in the present application;

fig. 12 is a flowchart of an example of another method for forwarding service data packets provided in the present application;

Fig. 13 is a schematic structural diagram of a service gateway provided in the present application;

fig. 14 is a schematic structural diagram of an access device provided in the present application;

fig. 15 is a schematic structural diagram of a mobility management device provided in the present application;

fig. 16 is a block diagram of a service gateway provided in the present application;

fig. 17 is a block diagram of an access device provided in the present application;

fig. 18 is a block diagram of a mobility management device according to the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings.

The embodiment of the application provides a method and a device for forwarding a service data packet, which are used for ensuring normal operation of a service when a 4G network is accessed through a 5G technology. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

Data packets referred to in this application (including upstream and downstream data packets) are all referred to as service data packets.

In the description of the present application, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, nor order.

In order to more clearly describe the technical solution of the embodiment of the present application, the following describes in detail a method and an apparatus for forwarding a service data packet provided in the embodiment of the present application with reference to the accompanying drawings.

Fig. 1 illustrates an architecture of a 5G network in the prior art, where the architecture of the 5G network includes a Network Slice Selection Function (NSSF) device, a network open function (NEF) device, a network function library function (NF) device, a policy control function (policy control function) device, a Unified Data Management (UDM) device, an Application Function (AF) device, an authentication server function (AUSF) device, an access and mobility management function (access and mobility management function, AMF) device, a session management function (session management function, SMF) device, a service Proxy (PCF) device, a user equipment (PCF), a user equipment (radio access network, PCF), and a user equipment (radio access network, PCF), UPF) and Data Networks (DNs).

In the existing 5G network, a terminal device accesses an access and mobility management function device through an N1 interface and an access network accesses the access and mobility management function device through an N2 interface, and a core network is realized based on a service architecture.

Since 5G networks employ a large number of new technologies, such as a service framework, a hyperText transfer protocol (HTTP) or a transport security protocol (TLS), these technologies are not used in mobile communication networks, and are not mature at present. In addition, operators need to invest in building new infrastructure for 5G networks, and the investment cost is high, so that the application of the 5G networks is limited. Based on the compatibility between the 5G network and the fourth generation (4G) network, the present application proposes that the terminal device and the access network can access an Evolved Packet Core (EPC) through an N1 or N2 interface, and support 5G native access in the case of reusing an EPC network infrastructure. However, in the conventional EPC network, the service data packet between the terminal device and the external data network is forwarded through the access device, the service gateway, and the data gateway, which is different from the method for forwarding the 5G service data packet, so that when the access to the 4G network is realized through the 5G technology, the normal operation of the service can be ensured.

Based on the above description, the present application provides a possible communication system architecture, which is a possible communication system architecture to which the method for forwarding service data packets provided in the embodiment of the present application is applied, as shown in fig. 2a, the communication system architecture may include a terminal device, an access network, a mobility management device, a serving gateway, a data gateway, and a packet data network, where:

a terminal device, which may also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user. For example, the terminal device may include a handheld device, a vehicle-mounted device, and the like having a wireless connection function. Currently, the terminal device may be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like.

The terminal equipment is accessed through a local wireless access network.

The mobile management device is responsible for the functions of position management, connection management, security authentication, gateway selection and the like of the mobile user equipment.

The service gateway is a local access gateway of the terminal equipment and is responsible for connection management and data forwarding related to the access technology.

A data gateway is a gateway for a terminal device to access an external data network.

The EPC network may also be a network in which a control plane and a user plane are separated, that is, the control plane and the user plane of the serving gateway and the data gateway are separated and are divided into a serving gateway of the user plane, a serving gateway of the control plane, a data gateway of the user plane, and a data gateway of the control plane. The service gateway of the control plane is responsible for connection management and data forwarding control related to the access technology, and the service gateway of the user plane is responsible for data forwarding. The data gateway of the control plane is responsible for data forwarding control, and the data gateway of the user plane is responsible for data forwarding. The service gateway of the control plane can be deployed together with the data gateway of the control plane, and the service gateway of the user plane can also be deployed together with the data gateway of the user plane.

In practice, the terminal device may be a 5G terminal; for an evolved universal terrestrial radio access network (evolved E-UTRAN) and a New Radio (NR) access network, an access device may be a next generation evolved NodeB (ng-eNB) or a next generation NodeB (gNB) in a 5G mobile communication system, a core network is a network element of an EPC network, a mobile management device may be a Mobility Management Entity (MME), a serving gateway may be a serving gateway (S-GW), and a data gateway may be a packet data network gateway (PDN-GW). For a network with a separated control plane and user plane, the service gateway may be a serving gateway (SGW-U) of the user plane and a serving gateway (SGW-C) of the control plane, and the data gateway may be a data gateway (PGW-U) of the user plane and a data gateway (PGW-C) of the control plane. The mobile management device and the service gateway can be enhanced to a certain extent on the basis of the existing EPC network to support the native access of the 5G terminal device.

It should be noted that, when the mobility management device and the serving gateway are enhanced, the mobility management device may be referred to as an enhanced mobility management device, and the serving gateway may be referred to as an enhanced serving gateway.

As shown in fig. 2b, a terminal device in a 4G dependent networking architecture (NSA) is a 4G terminal device, and accesses a mobility management device through a 4G NAS, and a main access network accesses the mobility management device through a 4G S1 interface. The user plane data packet of the terminal device may be forwarded through a main access network and a second access network at the same time, where the main access network is an evolved NodeB (eNodeB) for E-UTRAN, and the corresponding access device is an ng-eNB or a gNB for E-UTRAN or an NR access network. The high bandwidth provided by the second access network allows the 4G terminal device to enjoy a service experience comparable to that of a 5G network. However, the NSA architecture requires deployment of a main access network and a second access network, and is suitable for local hotspot deployment, and the overall network deployment cost is high. Therefore, the network shown in fig. 2a provided by the present application can avoid the above problems, and flexibly implement access to a 4G network through a 5G technology.

It should be noted that the architectures of the communication systems shown in fig. 2a and fig. 2b are not limited to include only the devices shown in the figures, and may also include other devices not shown in the figures, and specific details of the present application are not listed here.

The method for forwarding the service data packet provided by the embodiment of the application is suitable for the communication system shown in fig. 2 a. Referring to fig. 3, a specific process of the method may include:

step 301, the service gateway receives a first downlink data packet sent by the data gateway, where the first downlink data packet includes a first Internet Protocol (IP) address and a first Tunnel Endpoint Identifier (TEID).

In this embodiment, the service gateway is an enhanced service gateway that enhances an existing service gateway.

Step 302, the serving gateway determines a quality of service (QoS) flow identifier and a second IP address and a second TEID of a Packet Data Unit (PDU) session allocated by an access device according to the first IP address and the first TEID.

Specifically, the serving gateway obtains the bearer context corresponding to the first IP address and the first TEID, so as to obtain the QoS flow identifier, the second IP address, and the second TEID according to the bearer context.

Step 303, the serving gateway sends a second downlink data packet to the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID.

It should be noted that the first downlink data packet and the second downlink data packet are data packets for the same service, and the second data packet is a data packet obtained by removing the first IP address and the first TEID in the first downlink data packet and encapsulating the QoS flow identifier, the second IP address, and the second TEID by the serving gateway.

Further, after receiving the second downlink data packet, the access device determines the PDU session context corresponding to the second IP address and the second TEID according to the second IP address and the second TEID, determines the corresponding QoS flow according to the QoS flow identifier, and then sends a third downlink data packet to the terminal device according to the QoS parameter associated with the QoS flow.

It should be noted that the third downlink data packet sent by the access device to the terminal is a data packet obtained by removing the second IP address and the second TEID in the second downlink data packet.

In an optional implementation manner, in a PDU session establishment scenario, before the serving gateway receives a first downlink data packet sent by a data gateway, the serving gateway receives a session establishment request message sent by a mobility management device, where the session establishment request message includes an access type of a terminal device, and the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network; the service gateway allocates a third IP address and a third TEID of the PDN connection according to the access type; and the service gateway sends a session establishment response message to the mobile management equipment, wherein the session establishment response message comprises the third IP address and the third TEID.

In this embodiment, the mobility management device is an enhanced mobility management device that is enhanced to an existing mobility management device.

Illustratively, the access type may be a type of an access device accessed by the terminal device, or a type of a radio access network, or a type of the terminal device; the type of the access equipment is an evolved node B (ng-eNB) type or a next generation base station gNB type; the type of the wireless access network is a new wireless NR type or an Evolved universal terrestrial radio access network Evolved E-UTRAN type; the type of the terminal equipment is 5G type.

In a specific embodiment, the session establishment request message received by the serving gateway further includes an associated bearer identifier allocated by the mobile management device for a default bearer of the PDN connection. The associated bearer identifier is both a PDN connection identifier and a bearer identifier of a currently established bearer, and the currently established bearer is a default bearer. It should be noted that the mobility management device may allocate a PDN connection identifier according to a PDU session identifier obtained from the terminal device, where a value of the PDN connection identifier is the same as a value of the PDU session identifier, and for example, the PDN connection identifier is calculated from the PDU session identifier through a certain algorithm. The mobility management device may also allocate a PDN connection identifier according to an existing method, and locally store a correspondence between the PDU session identifier and the PDN connection identifier, which is not limited in the present application.

In an exemplary embodiment, the serving gateway sends an establish session request message 2 to the data gateway after receiving the establish session request message (here, the establish session request message 2 is written to distinguish from the establish session request message received by the serving gateway and has no other meaning); the serving gateway receives the establish session response message 2 sent by the data gateway (here, the establish session response message 2 is written to distinguish from the establish session request message sent by the serving gateway, and has no other meaning). The setup session request message 2 may include the associated bearer identifier, the access type, and the first IP address and the first TEID. The session establishment response message 2 may include the associated bearer identifier and the fourth IP address and the fourth TEID of the bearer allocated by the data gateway.

In an optional embodiment, after the PDU session establishment is completed, the serving gateway receives an update bearer request message sent by the mobility management device, where the update bearer request message includes the second IP address and the second TEID and the QoS flow identifier; and the service gateway sends an update bearing response message to the mobile management equipment based on the update bearing request message.

In another optional implementation manner, in a scenario of PDU session update triggered by a bearer establishment procedure, before the serving gateway receives a first downlink data packet sent by a data gateway, the serving gateway sends a bearer establishment request message to the mobility management device, where the bearer establishment request message includes the third IP address and the third TEID.

For example, before sending the bearer establishment request message to the mobility management device, the serving gateway receives a bearer establishment request message 2 sent by the data gateway (here, the bearer establishment request message 2 is written to be distinguished from the bearer establishment request message sent by the serving gateway and has no other meaning), and the bearer establishment request message 2 includes the fourth IP address and the fourth TEID of the bearer allocated by the data gateway.

In a specific embodiment, after the PDU session update is completed, the serving gateway receives a first setup bearer response message sent by the mobility management device, where the first setup bearer response message includes the second IP address, the second TEID, and the QoS flow identifier; and the service gateway sends a second bearer establishment response message to the data gateway based on the first bearer establishment response message, wherein the second bearer establishment response message comprises a bearer identifier, the first IP and the first TEID. Wherein, the first bearer establishment response message is used for responding to the bearer establishment request message, and the second bearer establishment response message is used for responding to the bearer establishment request message 2.

By adopting the method for forwarding the service data packet provided by the embodiment of the application, when the 5G terminal equipment and the access equipment are accessed to the evolved packet core network, the service data packet of the terminal equipment can be forwarded normally, the normal operation of the service is ensured, and the influence on the service experience of a user is avoided. That is, the method can ensure normal operation of the service when the 4G network is accessed by the 5G technology.

Another method for forwarding a service data packet provided in this embodiment is applicable to the communication system shown in fig. 2 a. Referring to fig. 4, a specific process of the method may include:

Step 401, the serving gateway receives a first uplink data packet sent by the access device, where the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier.

In this embodiment, the serving gateway is an enhanced serving gateway that enhances an existing serving gateway.

Specifically, after receiving a third uplink data packet sent by the terminal device, the access device sends the first uplink data packet to the serving gateway. The access device determines a QoS flow corresponding to the third uplink data packet according to the air interface bearer, and obtains a QoS flow identifier in a QoS flow context, and a third IP address and a third TEID in a PDU session context corresponding to the QoS flow; the third IP address and third TEID are assigned by the serving gateway.

Step 402, the service gateway determines a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identifier.

Specifically, the serving gateway determines a PDN connection context corresponding to the third IP address and the third TEID, then determines a bearer context in the PDN connection context according to the QoS flow identifier, and obtains the fourth IP address and the fourth TEID according to the bearer context.

Step 403, the serving gateway sends a second uplink data packet to a data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

In an optional implementation manner, in a scenario of PDU session establishment, before the serving gateway receives the first uplink data packet sent by the access device, operations performed by the serving gateway are similar to operations performed by the serving gateway before the serving gateway receives the first downlink data packet sent by the data gateway in the embodiment shown in fig. 3, which may be specifically referred to each other, and details are not repeated here.

In another optional implementation manner, in a PDU session update scenario triggered by a bearer establishment procedure, operations performed by the serving gateway before the serving gateway receives the first uplink data packet sent by the access device are similar to operations performed by the serving gateway before the serving gateway receives the first downlink data packet sent by the data gateway in the embodiment shown in fig. 3, which may be specifically referred to each other, and details are not described here again.

It should be noted that, in the embodiments shown in fig. 3 and fig. 4, the enhanced serving gateway supports the tunnel of the PDN connection, so that the service packet of the terminal device can be forwarded normally, and the service experience of the user is not affected. The embodiment shown in fig. 3 implements forwarding of a downlink service data packet, and the embodiment shown in fig. 4 implements forwarding of an uplink service data packet, where the two embodiments are different in forwarding flow, and other flows are basically the same.

The following two embodiments shown in fig. 5 and fig. 6 are different from the embodiments shown in fig. 3 and fig. 4, in the embodiments shown in fig. 5 and fig. 6, a tunnel supporting QoS flows is used to enhance an access device, so that a service data packet of a terminal device can be forwarded normally, and service experience of a user is not affected. The embodiment shown in fig. 5 implements forwarding of a downlink service data packet, and the embodiment shown in fig. 6 implements forwarding of an uplink service data packet, where the two embodiments are different in forwarding flow, and other flows are basically the same.

Another method for forwarding a service data packet provided in this embodiment is applicable to the communication system shown in fig. 2 a. Referring to fig. 5, a specific process of the method may include:

Step 501, an access device receives a first downlink data packet sent by a service gateway, where the first downlink data packet includes a first IP address and a first TEID.

In this embodiment, the access device is an enhanced access device that enhances an existing access device.

Specifically, the service gateway receives the third downlink data packet sent by the data gateway, and then sends the first downlink data packet to the access device. The third downlink data packet includes an IP address and a TEID forwarded and allocated by the serving gateway to the downlink data packet carried by the serving gateway, and the serving gateway determines the first IP address and the first TEID of the QoS flow allocated by the access device according to the IP address and the TEID forwarded and allocated by the serving gateway to the downlink data packet carried by the serving gateway.

Step 502, the access device obtains the QoS parameters in the QoS flow context corresponding to the first IP address and the first TEID.

Specifically, the access device determines the QoS flow context corresponding to the first IP address and the first TEID, so as to obtain the QoS parameter.

Step 503, the access device sends a second downlink data packet to the terminal device according to the quality of service parameter.

In an optional implementation manner, in a PDU session establishment scenario, before the access device receives a first downlink data packet sent by a serving gateway, the access device receives a PDU session resource establishment request message sent by a mobility management device, where the PDU session resource establishment request message includes a QoS flow identifier and a second IP address and a second TEID of a QoS flow allocated by the serving gateway; then, the PDU session resource establishment request message also includes a PDU session establishment acceptance message sent to the terminal device, and the access device forwards the PDU session establishment acceptance message to the terminal device based on the PDU session resource establishment request message.

Illustratively, the PDU session resource establishment request message may further include a PDU session identification.

Optionally, the PDU session setup accept message may include the PDU session identifier and the QoS flow identifier.

And then, the access device sends a PDU session resource establishment response message to the mobility management device, wherein the PDU session resource establishment response message comprises the first IP address and the first TEID of the QoS flow allocated to the downlink data packet by the access device.

Illustratively, the PDU session resource setup response message may further include the PDU session identifier and the QoS flow identifier.

In another optional implementation manner, in a PDU session update scenario triggered by a bearer establishment procedure, before the access device receives a first downlink data packet sent by a serving gateway, the access device receives a PDU session resource update request message sent by the mobility management device, where the PDU session resource update request message includes a QoS flow identifier, the second IP address, and the second TEID; the PDU session resource updating request message also comprises a PDU session updating request message sent to the terminal equipment, and the access equipment forwards the PDU session updating request message to the terminal equipment based on the PDU session resource updating request message. Wherein the PDU session update request message includes the QoS flow identification.

And then, the access device sends a PDU session resource update response message to the mobility management device, wherein the PDU session resource update response message comprises a first IP address and a first TEID of a QoS flow allocated to a downlink data packet by the access device. Wherein, the PDU session resource update response message also includes the QoS flow identification.

For example, before the access device sends a PDU session resource update response message to the mobility management device, the access device receives a PDU session update complete message sent by the terminal device, and forwards the PDU session update complete message to the mobility management device, where the PDU session update complete message includes the QoS flow identifier and is used to indicate that the QoS flow establishment is complete.

In yet another optional implementation manner, in a handover procedure in which the access device, the mobility management device, and the serving gateway are handed over, the access device is a new-side access device, that is, a handed-over access device. In this scenario, before the access device receives the first downlink data packet sent by the serving gateway, the access device receives a handover request message sent by the mobility management device (where the mobility management device is a new-side mobility management device, that is, a post-handover mobility management device), where the handover request message includes the QoS flow identifier, the second IP address, and the second TEID.

Then, the access device sends a handover request response message to the mobility management device, where the handover request response message includes the first IP address and the first TEID of the QoS flow allocated by the access device for the downlink packet.

Another method for forwarding a service data packet provided in this embodiment is applicable to the communication system shown in fig. 2 a. Referring to fig. 6, a specific process of the method may include:

step 601, the access device receives a first uplink data packet sent by the terminal device.

Step 602, the access device obtains a second IP address and a second TEID of the QoS flow allocated by the serving gateway in the QoS flow context of the first uplink data packet.

Step 603, the access device sends a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

Specifically, after receiving the second uplink data packet, the service gateway sends a third uplink data packet to the data gateway. The service gateway determines the IP address and the TEID of the bearer distributed by the data gateway according to the second IP address and the second TEID; and the third uplink data packet comprises the IP address and the TEID of the bearer allocated by the data gateway.

In an optional implementation manner, in a scenario of PDU session establishment, before the access device receives a first uplink data packet sent by a terminal device, operations performed by the access device are similar to operations performed before the access device receives a first downlink data packet sent by a serving gateway in the embodiment shown in fig. 5, which may be specifically referred to each other, and details are not repeated here.

In another optional implementation manner, in a scenario of PDU session update triggered by a bearer establishment procedure, operations performed by the access device before the access device receives a first uplink data packet sent by a terminal device are similar to operations performed before the access device receives a first downlink data packet sent by a serving gateway in the embodiment shown in fig. 5, which may be specifically referred to each other, and details are not described here again.

In yet another optional implementation manner, in a handover procedure in which the access device, the mobility management device, and the serving gateway are handed over, the access device is a new-side access device, that is, an access device after handover. In this scenario, before the access device receives the first uplink data packet sent by the terminal device, operations performed by the access device are similar to operations performed before the access device receives the first downlink data packet sent by the serving gateway in the embodiment shown in fig. 5, which may be specifically referred to each other, and details are not described here again.

Fig. 7 shows an embodiment, which is another method for forwarding a service data packet according to the embodiment of the present application, and is applicable to the communication system shown in fig. 2 a. Referring to fig. 7, a specific process of the method may include:

step 701, the mobility management device receives a first message, where the first message is used to establish a PDU session or bearer.

In this embodiment, the mobility management device is an enhanced mobility management device that is enhanced with respect to an existing mobility management device.

Step 702, the mobility management device sends a second message to the service gateway, where the second message includes a bearer identifier.

Step 703, the mobility management device sends a third message to the access device, where the third message includes the QoS flow identifier.

Wherein, the bearer identification and the QoS flow identification are used for identifying one bearer of the terminal equipment.

In a scenario of PDU session establishment, the first message is a PDU session establishment request message sent by the terminal device, the second message is a session establishment request message, and the third message is a PDU session resource establishment request message; in a scenario of PDU session update triggered by a bearer establishment procedure, the first message is a bearer establishment request message sent by the serving gateway, the second message is a bearer establishment response message, and the third message is a PDU session resource update request message; in a handover process in which an access device, a mobility management device and a serving gateway are handed over, the mobility management device is a new-side mobility management device, the first message is a forward handover request message sent by a source mobility management device, the second message is a session establishment request message, and the third message is a handover request message.

Specifically, the first message, the second message, and the third message are used to establish a channel for forwarding a service data packet.

In an optional implementation manner, when the second message is a session establishment request message in a PDU session establishment scenario, the second message further includes an access type of a terminal device, where the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network.

In a specific implementation manner, the mobility management device receives a session establishment response message sent by the serving gateway, where the session establishment response message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

the mobile management equipment sends a PDU session resource establishment request message or a switching request message to the access equipment, wherein the PDU session resource establishment request message or the switching request message comprises the first IP address and the first TEID;

the mobile management equipment receives a PDU session resource establishment response message or a switching request response message sent by access equipment, wherein the PDU session resource establishment response message or the switching request response message comprises a second IP address and a second TEID allocated by the access equipment; wherein the second IP address and the second TEID are an IP address and a TEID of a PDU session or an IP address and a TEID of a QoS flow;

and the mobile management equipment sends an update bearing request message to the service gateway, wherein the update bearing request message comprises the second IP address and the second TEID.

In an optional implementation manner, the update bearer request message further includes a QoS flow identifier.

In another specific embodiment, the bearer establishment request message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

the mobile management equipment sends a PDU session resource updating request message to the access equipment; wherein, when the first address and the first TEID are an IP address and a TEID of a bearer, the PDU session resource update request message includes the first IP address and the first TEID, or when the first address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update request message does not include the first IP address and the first TEID;

the mobile management equipment receives a PDU session resource updating response message sent by the access equipment; the PDU session resource updating response message comprises a second IP address and a second TEID allocated by the access equipment, wherein the second IP address and the second TEID are the IP address and the TEID of the PDU session or the IP address and the TEID of the QoS flow; or when the first address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update response message does not contain the IP address and the TEID allocated by the access equipment;

The mobile management equipment sends a response message for establishing the load bearing to the service gateway; wherein the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID are an IP address and a TEID of a PDU session, the bearer establishment response message does not include an IP address and a TEID allocated by the access device; or, the bearer establishment response message includes the second IP address and the second TEID, where the second IP address and the second TEID are obtained by the mobility management device from a PDU session resource establishment response message or a handover request response message.

In an optional implementation manner, the setup bearer response message further includes a QoS flow identifier.

Based on the above embodiments, the embodiments of the present application provide an example of a method for forwarding a service data packet, where the example is that in a scenario of PDU session establishment, a tunnel supporting PDN connection through an enhanced serving gateway enables the service data packet of a terminal device to be forwarded normally. In this example, the serving gateway is an enhanced serving gateway and the mobility management device is an enhanced mobility management device, shown in this example as an enhanced serving gateway and an enhanced mobility management device. Referring to fig. 8, a specific process of this example may include:

Step 801, the terminal device sends a PDU session establishment request message to the enhanced mobility management device, where the PDU session establishment request message includes a PDU session identifier allocated to the PDU session by the terminal device.

And triggering a PDU session establishment flow when the terminal equipment needs to perform service.

Illustratively, when the terminal device sends a PDU session establishment request message to the enhanced mobility management device, the terminal device sends the PDU session establishment request message to the enhanced mobility management device through the access device. Specifically, the terminal device first sends the PDU session establishment request message to the access device, and then the access device forwards the PDU session establishment request message to the enhanced mobility management device.

Step 802, the enhanced mobility management device selects an enhanced service gateway and a data gateway.

Step 803, the enhanced mobility management device sends a session establishment request message to the enhanced service gateway.

The session establishment request message includes an access type of the terminal device, and the access type is used for indicating that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network.

In particular, the description of the access type may refer to the description of the access type involved in the embodiment shown in fig. 3, and is not described in detail here.

Similarly, the description of the setup session request message may refer to the description of the setup session request message in the embodiment shown in fig. 3, and will not be described in detail here.

And step 804, the enhanced service gateway sends a session establishment request message 2 to the data gateway for establishing the PDN connection.

The session establishment request message 2 may include the associated bearer identifier, the access type, and an IP address and a TEID allocated by the enhanced serving gateway for forwarding downlink packets of a default bearer of the PDN connection, that is, the first IP address and the first TEID involved in the embodiment shown in fig. 3.

Step 805, establishing a connection access network (IP-CAN) session of the PDN connection between the data gateway and a Policy and Charging Rules Function (PCRF) to obtain corresponding policies such as charging and quality of service.

Step 806, the data gateway sends a session establishment response message 2 to the enhanced service gateway.

The session establishment response message 2 may include the associated bearer identifier, and the IP address and the TEID allocated by the data gateway for forwarding the uplink data packet of the default bearer of the PDN connection, that is, the fourth IP address and the fourth TEID involved in the embodiment shown in fig. 3.

Step 807, the enhanced service gateway sends a setup session response message to the enhanced mobility management device.

The enhanced serving gateway learns that the terminal device accesses from the Evolved E-UTRAN or NR according to the access type received in step 803, and adds the enhanced serving gateway to forward and allocate an IP address and a TEID to an uplink packet connected to the PDN, where the IP address and the TEID are the IP address and the TEID of the PDN connection, and the enhanced serving gateway includes the IP address and the TEID in the session establishment response message, that is, the third IP address and the third TEID involved in the embodiment shown in fig. 3.

Optionally, the session establishment response message further includes an associated bearer identifier.

Step 808, the enhanced mobility management device sends a PDU session resource establishment request message to the access device.

The PDU session resource establishment request message comprises a PDU session identifier, a QoS flow identifier, an IP address and a TEID which are distributed by the enhanced service gateway. The PDU session resource establishment request message further includes a PDU session establishment accept message sent to the terminal device.

Specifically, the enhanced mobility management device allocates a QoS flow identifier, where the QoS flow identifier may be the same as the bearer identifier, or the QoS flow identifier is calculated from the bearer identifier through a certain algorithm, or the allocation of the QoS flow identifier and the bearer identifier are unrelated, but the enhanced mobility management device locally stores the corresponding relationship between the QoS flow identifier and the bearer identifier. The QoS flow identifier or bearer identifier is used to identify a bearer.

Step 809, the access device forwards the PDU session setup accept message to the terminal device. The PDU session establishment receiving message comprises a PDU session identification and a QoS flow identification.

Step 810, the access device sends a PDU session resource setup response message to the enhanced mobility management device.

The PDU session resource establishment response message includes a PDU session identifier, a QoS flow identifier, and an IP address and a TEID allocated to the access device for forwarding the downlink packet of the PDU session, that is, the second IP address and the second TEID in the embodiment shown in fig. 3.

Step 811, said enhanced mobility management element sends an update bearer request message to said enhanced service gateway.

Wherein, the update bearer request message includes the IP address and TEID allocated by the access device received by the enhanced mobility management device in step 810, and the update bearer request message further includes a QoS flow identifier and a bearer identifier, where the bearer identifier in this flow is an associated bearer identifier.

Specifically, the mme determines the bearer identifier according to the QoS flow identifier (the QoS flow identifier uniquely identifies one bearer in the terminal device), or further, the mme determines the PDN connection identifier according to the PDU session identifier, and determines the bearer identifier in the PDN connection according to the QoS flow identifier (the QoS flow identifier uniquely identifies one bearer in the PDN connection).

Step 812, the enhanced service gateway sends an update bearer response message to the enhanced mobility management device to indicate that the bearer update is successful.

And step 813, the enhanced service gateway receives the first downlink data packet sent by the data gateway. The first downlink data packet comprises a first IP address and a first TEID.

Step 814, the enhanced serving gateway determines a QoS flow id and a second IP address and a second TEID of the PDU session allocated by the access device according to the first IP address and the first TEID.

Specifically, the enhanced serving gateway obtains the bearer context corresponding to the first IP address and the first TEID, so as to obtain the QoS flow identifier, the second IP address, and the second TEID according to the bearer context.

Step 815, the enhanced serving gateway sends a second downlink data packet to the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID.

Step 816, the access device sends a third downlink data packet to the terminal device.

Specifically, the access device determines the PDU session context corresponding to the second IP address and the second TEID according to the second IP address and the second TEID, determines the corresponding QoS flow according to the QoS flow identifier, and then forwards the third downlink data packet to the terminal device according to the QoS parameter associated with the QoS flow.

817, the access device receives a third uplink data packet sent by the terminal device, where the third uplink data packet is sent on a corresponding air interface bearer, the access device determines, according to the air interface bearer, a QoS flow corresponding to the third uplink data packet, and the access device obtains a QoS flow identifier in a QoS flow context, and a third IP address and a third TEID in a PDU session context corresponding to the QoS flow.

Step 818, the access device sends the first uplink data packet to the enhanced serving gateway.

The first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier.

The third IP address and third TEID are assigned by the enhanced services gateway.

Step 819, the enhanced serving gateway determines a fourth IP address and a fourth TEID of the bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identifier.

Specifically, the enhanced serving gateway determines a PDN connection context corresponding to the third IP address and the third TEID, then determines a bearer context in the PDN connection context according to the QoS flow identifier, and obtains the fourth IP address and the fourth TEID according to the bearer context.

Step 820, the enhanced serving gateway sends a second uplink data packet to the data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

Based on the foregoing embodiments, the present application provides another example of a method for forwarding a service data packet, where the example is that in a scenario of PDU session update triggered by a bearer establishment procedure, a tunnel of a PDN connection is supported by an enhanced serving gateway, so that the service data packet of a terminal device can be forwarded normally. In this example, the serving gateway is an enhanced serving gateway and the mobility management device is an enhanced mobility management device, shown in this example as an enhanced serving gateway and an enhanced mobility management device. Referring to fig. 9, a specific process of this example may include:

Step 901, the policy and charging rule function entity triggers the IP-CAN session update and sends an IP-CAN session update request to the data gateway to send updated rules such as charging and service quality to the data gateway.

Step 902, the data gateway decides to trigger the bearer establishment procedure, and sends a bearer establishment request message 2 to the enhanced service gateway, where the bearer establishment request message 2 includes an IP address and a TEID allocated by the data gateway for forwarding an uplink data packet corresponding to the bearer, that is, a fourth IP address and a fourth TEID involved in the embodiment shown in fig. 3.

Step 903, the enhanced service gateway sends a bearer establishment request message to the enhanced mobility management device.

The bearer establishment request message includes a third IP address and a third TEID of the PDN connection allocated by the serving gateway according to the access type, that is, the third IP address and the third TEID are an IP address and a TEID of the PDN connection, that is, an IP address and a TEID of the PDU session allocated in step 807 in the example shown in fig. 8.

Step 904, the enhanced mobility management device sends a PDU session resource update request message to the access device.

The enhanced mobility management device assigns a QoS flow identifier (flow identifier) to the QoS flow carrying the corresponding QoS, the PDU session resource update request message includes the QoS flow identifier, and the QoS flow identifier assignment method refers to the method in the above embodiment and will not be described in detail here. The PDU session resource updating request message also comprises a PDU session updating request message sent to the terminal equipment.

Step 905, the access device forwards a PDU session update request message to a terminal device, where the PDU session update request message includes the QoS flow identifier.

Step 906, the terminal device sends a PDU session update complete message to the access device, where the PDU session update complete message includes a QoS flow identifier for indicating that the QoS flow establishment is complete.

Step 907, the access device forwards the PDU session update complete message to the enhanced mobility management device.

Step 908, the access device sends a PDU session resource update response message to the mme device, where the PDU session resource update response message includes a QoS flow id for indicating that the QoS flow establishment is completed.

Step 909, the enhanced mobility management device sends a first setup bearer response message to the enhanced service gateway.

The enhanced mobility management device allocates a bearer identifier for the bearer, the QoS flow identifier may be the same as the bearer identifier, or the bearer identifier is calculated from the QoS flow identifier by a certain algorithm, or the allocation of the bearer identifier is unrelated to the QoS flow identifier, but the enhanced mobility management device locally stores the corresponding relationship between the QoS flow identifier and the bearer identifier. The QoS flow identifier or bearer identifier is used to identify a bearer, which is a dedicated bearer in this flow. The first bearer establishment response message includes the bearer identification.

The first bearer establishment response message further includes the IP address and the TEID allocated by the access device (that is, the second IP address and the second TEID of the PDU session allocated by the access device, that is, the IP address and the TEID involved in step 810 in the example shown in fig. 8), or the first bearer establishment response message does not include the IP address and the TEID allocated by the access device, and after receiving the message, the enhanced serving gateway sends, to the terminal device accessed by the Evolved E-UTRAN or NR, all downlink service data packets corresponding to the PDN connection to the IP address and the TEID received in step 811 in the embodiment shown in fig. 8.

Step 910, the enhanced serving gateway sends a second bearer establishment response message to the data gateway, where the second bearer establishment response message includes a bearer identifier and an IP address and a TEID (i.e. the first IP address and the first TEID in the embodiment shown in fig. 3) allocated by the enhanced serving gateway and used for forwarding the downlink data packet corresponding to the bearer.

Step 911, the data gateway sends an IP-CAN session update response message to the policy and charging rules function entity.

Step 912, the enhanced service gateway receives the first downlink data packet sent by the data gateway. The first downlink data packet comprises a first IP address and a first TEID.

And 913, the enhanced serving gateway determines a QoS flow identifier and a second IP address and a second TEID of the PDU session allocated by the access device according to the first IP address and the first TEID.

Step 914, the enhanced serving gateway sends a second downlink data packet to the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID.

Step 915, the access device sends the third downlink data packet to the terminal device.

Specifically, the access device determines the PDU session context corresponding to the second IP address and the second TEID according to the second IP address and the second TEID, determines the corresponding QoS flow according to the QoS flow identifier, and then sends the third downlink data packet to the terminal device according to the QoS parameter associated with the QoS flow.

Step 916, the access device receives a third uplink data packet sent by the terminal device, where the third uplink data packet is sent on a corresponding air interface bearer, the access device determines a QoS flow corresponding to the third uplink data packet according to the air interface bearer, and the access device obtains a QoS flow identifier in a QoS flow context, and a third IP address and a third TEID in a PDU session context corresponding to the QoS flow.

Step 917, the access device sends the first uplink data packet to the enhanced serving gateway.

The first uplink data packet includes a third IP address and a third TEID and the QoS flow identifier.

Step 918, the enhanced serving gateway determines a fourth IP address and a fourth TEID of the bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identifier.

Step 919, the enhanced service gateway sends a second uplink data packet to the data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

It should be noted that, in the example shown in fig. 8 or the example shown in fig. 9, the occurrence sequence of the downlink packet forwarding process and the uplink packet forwarding process is not limited, and the figure is merely an example of a sequence, and it should be understood that the uplink packet forwarding may be performed before the downlink packet forwarding, and the application is not limited thereto.

Based on the above embodiments, the embodiments of the present application further provide another example of a method for forwarding a service data packet, where the example is that in a scenario of PDU session establishment, a tunnel supporting QoS flow is supported by an enhanced access device, so that a service data packet of a terminal device can be forwarded normally. In this example, the access device is an enhanced access device and the mobility management device is an enhanced mobility management device, which are shown in this example as an enhanced access device and an enhanced mobility management device. Referring to fig. 10, a specific process of this example may include:

step 1001, the terminal device sends a PDU session establishment request message to the enhanced mobility management device, where the PDU session establishment request message includes a PDU session identifier allocated to the PDU session by the terminal device.

Illustratively, when the terminal device sends a PDU session establishment request message to the enhanced mobility management device, the terminal device sends the PDU session establishment request message to the enhanced mobility management device through the enhanced access device. Specifically, the terminal device first sends the PDU session establishment request message to an enhanced access device, and then the enhanced access device forwards the PDU session establishment request message to the enhanced mobility management device.

Step 1002, the enhanced mobile management device selects a service gateway and a data gateway.

Step 1003, the enhanced mobile management device sends a session establishment request message to the service gateway.

Step 1004, the service gateway sends a session establishment request message 2 to the data gateway, for establishing PDN connection.

The session establishment request message 2 may include the associated bearer identifier, the access type, and an IP address and TEID allocated by the serving gateway for forwarding downlink packets of a default bearer of the PDN connection.

Step 1005, establishing the IP-CAN session of the PDN connection between the data gateway and the policy and charging rule function entity, so as to obtain the corresponding policies such as charging and quality of service.

Step 1006, the data gateway sends a session establishment response message 2 to the serving gateway.

The session establishment response message 2 may include the associated bearer identifier, and the IP address and TEID allocated by the data gateway for forwarding the uplink data packet of the default bearer of the PDN connection.

Step 1007, the service gateway sends a session establishment response message to the enhanced mobility management device.

The session establishment response message includes an IP address and a TEID (i.e., the second IP address and the second TEID involved in the embodiment shown in fig. 6) allocated by the serving gateway for forwarding the uplink packet of the default bearer of the PDN connection, where the second IP address and the second TEID are of the bearer or the QoS flow. The session establishment response message also contains an associated bearer identifier.

Step 1008, the enhanced mobility management device sends a PDU session resource establishment request message to the enhanced access device.

The PDU session resource establishment request message includes a PDU session identifier, a QoS flow identifier, an IP address of a QoS flow and a TEID (i.e., the IP address and the TEID allocated by the serving gateway in step 1007). The PDU session resource establishment request message further includes a PDU session establishment accept message sent to the terminal device.

Step 1009, the enhanced access device sends a PDU session setup accept message to the terminal device. The PDU conversation establishing receiving message comprises a PDU conversation mark and a QoS flow mark.

Step 1010, the enhanced access device sends a PDU session resource establishment response message to the enhanced mobility management device.

The PDU session resource establishment response message includes a PDU session identifier, a QoS flow identifier, and an IP address and a TEID allocated to the enhanced access device for forwarding a downlink packet of a QoS flow of the PDU session, that is, the first IP address and the first TEID in the embodiment shown in fig. 4.

Step 1011, the enhanced mobility management device sends an update bearer request message to the serving gateway.

Wherein, the update bearer request message includes the IP address and the TEID of the bearer, the IP address and the TEID received by the enhanced mobility management network element in step 1010, and the bearer identifier, which is the associated bearer identifier in this process.

Step 1012, the service gateway sends an update bearer response message to the enhanced mobility management device to indicate that the bearer update is successful.

Step 1013: and the service gateway receives a third downlink data packet sent by the data gateway, wherein the third downlink data packet comprises an IP address and a TEID (terminal identity) forwarded and allocated by the service gateway to a downlink data packet of a default bearer connected with the PDN.

And the service gateway determines a first IP address and a first TEID of the QoS flow allocated by the enhanced access equipment according to the IP address and the TEID which are transmitted and allocated by the service gateway for the downlink data packet of the default bearer of the PDN connection.

Step 1014, the service gateway sends a first downlink data packet to the enhanced access device, where the first downlink data packet includes the first IP address and the first TEID.

Step 1015, the enhanced access device obtains the QoS parameters in the QoS flow context corresponding to the first IP address and the first TEID.

Specifically, the enhanced access device determines the QoS flow context corresponding to the first IP address and the first TEID, so as to obtain the QoS parameter.

Step 1016, the enhanced access device sends a second downlink data packet to the terminal device according to the qos parameter.

Step 1017, the enhanced access device receives the first uplink data packet sent by the terminal device.

Step 1018, obtaining, by the enhanced access device, a second IP address and a second TEID of the QoS flow allocated by the serving gateway in the QoS flow context of the first uplink data packet.

Step 1019, the enhanced access device sends a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

Step 1020, the serving gateway sends a third uplink data packet to the data gateway.

Specifically, the service gateway determines the IP address and the TEID of the bearer allocated by the data gateway according to the second IP address and the second TEID; and the third uplink data packet comprises the IP address and the TEID of the bearer allocated by the data gateway.

Based on the above embodiments, the embodiments of the present application further provide another example of a method for forwarding a service data packet, where the example is that in a scenario of PDU session update, in a bearer establishment procedure, a service data packet of a terminal device can be normally forwarded by enhancing a tunnel that an access device supports QoS flows. In this example, the access device is an enhanced access device and the mobility management device is an enhanced mobility management device, which are shown in this example as an enhanced access device and an enhanced mobility management device. Referring to fig. 11, a specific process of this example may include:

step 1101, the policy and charging rule function entity triggers the update of the IP-CAN session, and sends an update request of the IP-CAN session to the data gateway so as to send the updated rules of charging, service quality and the like to the data gateway.

Step 1102, the data gateway decides to trigger a bearer establishment procedure, and sends a bearer establishment request message 2 to the serving gateway, where the bearer establishment request message 2 includes an IP address and a TEID allocated by the data gateway and used for forwarding an uplink data packet corresponding to the bearer.

Step 1103, the serving gateway sends a bearer establishment request message to the enhanced mobility management device, where the bearer establishment request message includes an IP address and a TEID allocated by the serving gateway and used for forwarding an uplink data packet corresponding to the bearer, that is, the IP address and the TEID are an IP address and a TEID of the bearer, that is, the second IP address and the second TEID involved in the embodiment shown in fig. 6.

Step 1104, the enhanced mobility management device sends a PDU session resource update request message to the enhanced access device.

The enhanced mobility management device assigns a QoS flow identifier (flow identifier) to the QoS flow carrying the corresponding QoS, the PDU session resource update request message includes the QoS flow identifier, and the QoS flow identifier assignment method refers to the method in the above embodiment and will not be described in detail here.

The PDU session resource update request message also carries an IP address and a TEID of the QoS flow, that is, the IP address and the TEID allocated by the serving gateway in step 1103 are used for forwarding the uplink data packet corresponding to the bearer.

The PDU session resource updating request message also comprises a PDU session updating request message sent to the terminal equipment.

Step 1105, the enhanced access device sends a PDU session update request message to a terminal device, where the PDU session update request message includes the QoS flow identifier.

Step 1106, the terminal device sends a PDU session update complete message to the enhanced access device, where the PDU session update complete message includes a QoS flow identifier, which is used to indicate that the QoS flow establishment is complete.

Step 1107, the enhanced access device forwards the PDU session update complete message to the enhanced mobility management device.

Step 1108, the access device sends a PDU session resource update response message to the enhanced mobility management device, where the PDU session resource update response message includes a QoS flow identifier for indicating that the QoS flow establishment is completed.

The PDU session resource update response message further includes an IP address and a TEID of the QoS flow, that is, an IP address and a TEID allocated by the enhanced access device and used for forwarding a downlink data packet corresponding to the QoS flow, that is, the IP address and the TEID are the IP address and the TEID of the QoS flow, that is, the first IP address and the first TEID in the embodiment shown in fig. 4.

Step 1109, the enhanced mobility management device sends a first bearer establishment response message to the service gateway.

Specifically, the first bearer establishment response message further includes an IP address and a TEID of the bearer, that is, the IP address and the TEID allocated by the enhanced access device and received by the enhanced mobility management network element in step 1108.

Step 1110, the serving gateway sends a second bearer establishment response message to the data gateway, where the second bearer establishment response message includes a bearer identifier and an IP address and a TEID allocated by the serving gateway for forwarding a downlink data packet corresponding to the bearer.

Step 1111, the data gateway sends an IP-CAN session update response message to the policy and charging rules function entity.

Step 1112: and the service gateway receives a third downlink data packet sent by the data gateway, wherein the third downlink data packet comprises an IP address and a TEID (terminal identity) which are distributed by the service gateway and used for forwarding the downlink data packet corresponding to the bearer.

And the service gateway determines a first IP address and a first TEID of the QoS flow distributed by the enhanced access equipment according to the IP address and the TEID which are distributed by the service gateway and used for forwarding the downlink data packet corresponding to the bearer.

Step 1113, the service gateway sends a first downlink data packet to the access device, where the first downlink data packet includes the first IP address and the first TEID.

Step 1114, the enhanced access device obtains a quality of service parameter in a QoS flow context corresponding to the first IP address and the first TEID.

Step 1115, the enhanced access device sends a second downlink data packet to the terminal device according to the service quality parameter.

Step 1116, the enhanced access device receives the first uplink data packet sent by the terminal device.

Step 1117, the enhanced access device obtains the second IP address and the second TEID of the QoS flow allocated by the service gateway in the QoS flow context of the first uplink data packet.

Step 1118, the enhanced access device sends a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

Step 1119, the service gateway sends a third uplink data packet to the data gateway.

It should be noted that, in the example shown in fig. 10 or the example shown in fig. 11, the occurrence sequence of the downstream packet forwarding process and the upstream packet forwarding process is not limited, and the figure is merely an example of a sequence, and it should be understood that the upstream packet forwarding may be performed first and the downstream packet forwarding is performed later, and the application is not limited thereto.

Based on the above embodiments, the embodiments of the present application provide an example of a method for forwarding a service data packet, where the example is an example of forwarding a service data packet in a handover procedure in which an access device, a mobility management device, and a serving gateway are switched. Wherein, in this example, the handover procedure may be a procedure of a 4G to 5G mobility management device change, a serving gateway change; in the process, the source access equipment is a 4G base station eNodeB, and the new access equipment is ng-eNB or gNB. Or, in this example, the handover procedure may be a 5G to 5G mobility management device change, serving gateway change procedure; in the process, the source side access device is ng-eNB or gNB, and the new side access device (target access device) is ng-eNB or gNB. Referring to fig. 12, a specific process of this example may include:

Step 1201, the source side access device triggers a handover procedure and sends a handover request message to the source side mobility management device.

Specifically, the source side access device triggers the terminal device to switch to the new side access device when detecting that the signal strength of the terminal device under the new side access device exceeds a certain threshold.

The handover request message includes an access type, and the access type is used to indicate an access type of the terminal device in a new access device. Illustratively, the access type may be a type of an access device accessed by the terminal device, or a type of a radio access network, or a type of the terminal device.

The type of the access device in the handover procedure from 4G to 5G, or from 5G to 5G may be a next generation evolved node b ng-eNB type or a next generation base station gNB type; the type of the wireless access network is a new wireless NR type or an Evolved universal terrestrial radio access network Evolved E-UTRAN type; the type of the terminal equipment is 5G type.

Optionally, the first handover request message further includes an identifier of a target access device (i.e., a new-side access device).

Step 1202, the source-side mobility management device sends a forward handover request message to a new-side mobility management device (target mobility management device).

Wherein, the forwarding handover request message includes the access type.

The forward handover request message further includes an identifier of the target access device (i.e., a new-side access device), and a context of the terminal device, including contexts of one or more established PDN connections of the terminal device, where each PDN connection context includes one or more bearer contexts, and each bearer context includes a bearer identifier, a QoS flow identifier, and an IP address and a TEID allocated by the data gateway.

Step 1203, the new-side mobility management device sends a session establishment request message to a new-side service gateway (target service gateway).

The session establishment request message includes the access type, the bearer identifier of each bearer, and the IP address and TEID allocated by the data gateway.

Step 1204, the new-side service gateway sends a session establishment response message to the new-side mobility management device.

In one example, for a tunnel of PDN connection granularity: the new-side serving gateway allocates an IP address and the TEID of the packet data network PDN connection according to the access type (i.e., a third IP address and a third TEID related to the embodiment shown in fig. 3); and the session establishing response message comprises the IP address of the message data network PDN connection distributed by the new-side service gateway according to the access type and the TEID.

In another example, for a tunnel carrying granularity (as with existing 4G network technologies): and the new side service gateway allocates the IP address and the TEID of the bearer, and the session establishment response message comprises the IP address and the TEID of the bearer allocated by the new side service gateway.

Step 1205, the new-side mobility management device sends a handover request message to the new-side access device, where the handover request message is used to request the new-side access device to establish a service data packet forwarding channel of the terminal device.

Wherein, the handover request message includes the IP address and the TEID allocated by the new-side serving gateway in step 1204.

The handover request message further includes the QoS flow id received in step 1202.

Step 1206, the new-side access device sends a handover request response message to the new-side mobility management device, where the handover request response message includes an IP address and a TEID allocated by the new-side access device for forwarding the downlink data packet, and a QoS flow identifier.

In one example, for a tunnel of PDN connection granularity: the IP address and the TEID allocated by the new-side access device for forwarding the downlink data packet are the second IP address and the second TEID involved in the embodiment shown in fig. 3;

In another example, for a tunnel with bearer granularity, the IP address and the TEID allocated by the new-side access device for forwarding the downlink data packet are the first IP address and the first TEID involved in the embodiment shown in fig. 5.

Step 1207, the new-side mobility management device sends a forward handover request response message to the source-side mobility management device, indicating that the new side establishes a successful bearer context.

Step 1208, the source-side mme sends a handover command to the source-side ap, so as to indicate that the ue may handover to the target side (i.e. the new side).

Step 1209, the source side access device forwards the handover command to the terminal device, so as to indicate that the terminal device may be handed over to the target side.

Step 1210, the terminal device switches to the target side and sends a switch completion message to the new side access device.

Step 1211, the new-side access device forwards the handover complete message to the new-side mobility management device.

Step 1212, the new-side mme sends a handover complete notification message to the source-side mme so that the source-side mme releases the source-side resource.

Step 1213, the new-side mme sends a first update bearer request message to the new-side sgsn, where the first update bearer request message includes the IP address and TEID allocated by the access device in step 1206.

Illustratively, for a tunnel with PDN connection granularity, the first update bearer request message further includes a QoS flow identifier.

Step 1214, the new-side serving gateway sends a second update bearer request message to the data gateway, where the second update bearer request message includes an IP address and a TEID of a bearer allocated by the new-side serving gateway for forwarding the downlink data packet.

Step 1215, the data gateway sends a first update bearer response message to the new-side service gateway.

Step 1216, the new-side serving gateway sends a second update bearer response message to the new-side mobility management device.

Step 1217, the new-side serving gateway receives the first downlink data packet sent by the data gateway. The first downlink data packet comprises the IP address and the TEID distributed by the new side service gateway.

Step 1218, the new side service gateway determines the IP address and the TEID of the PDU session allocated by the new side access device according to the IP address and the TEID allocated by the new side service gateway.

Specifically, the new-side serving gateway obtains the IP address and the bearer context corresponding to the TEID allocated to the new-side serving gateway, so as to obtain the QoS flow identifier and the IP address and the TEID of the PDU session allocated to the new-side access device according to the bearer context.

Or, the new side service gateway determines the IP address and the TEID of the QoS flow allocated by the new side access device according to the IP address and the TEID allocated by the new side service gateway.

Specifically, the new-side serving gateway obtains a bearer context corresponding to the IP address and the TEID allocated by the new-side serving gateway, so as to obtain the IP address and the TEID of the QoS flow allocated by the new-side access device according to the bearer context.

Step 1219, the new-side serving gateway sends a second downlink data packet to the new-side access device, where the second downlink data packet includes the QoS flow identifier and the IP address and TEID of the PDU session allocated by the new-side access device. Or, the new-side service gateway sends a second downlink data packet to the new-side access device, where the second downlink data packet includes an IP address and a TEID of a PDU session allocated by the new-side access device.

Step 1220, the new-side access device sends a third downlink data packet to the terminal device.

Specifically, the new-side access device determines the IP address of the PDU session allocated by the new-side access device and the PDU session context corresponding to the TEID according to the IP address and the TEID of the PDU session allocated by the new-side access device, determines the corresponding QoS flow according to the QoS flow identifier, and then the new-side access device sends the third downlink data packet to the terminal device according to the QoS parameter associated with the QoS flow.

Or, the new-side access device determines the IP address of the QoS flow allocated by the new-side access device and the QoS flow context corresponding to the TEID according to the IP address and the TEID of the QoS flow allocated by the new-side access device, and then the new-side access device sends the third downlink data packet to the terminal device according to the QoS parameter associated with the QoS flow.

Step 1221, the new-side access device receives a third uplink data packet sent by the terminal device, where the third uplink data packet is sent on a corresponding air interface bearer, the new-side access device determines, according to the air interface bearer, a QoS flow corresponding to the third uplink data packet, and the new-side access device obtains a QoS flow identifier in a QoS flow context, and an IP address and a TEID allocated by the new-side service gateway in a PDU session context corresponding to the QoS flow.

Or, the new-side access device obtains the IP address and the TEID of the QoS flow allocated by the new-side service gateway in the QoS flow context.

Step 1222, the new-side access device sends a first uplink data packet to the new-side serving gateway.

The first uplink data packet includes the IP address and TEID of the PDN connection allocated by the new-side serving gateway, and the QoS flow identifier.

Or, the first uplink data packet includes an IP address and a TEID of the QoS flow allocated by the new-side serving gateway.

And 1223, the new-side service gateway determines the IP address and the TEID of the bearer allocated by the data gateway according to the IP address and the TEID allocated by the new-side service gateway.

Specifically, the new-side serving gateway determines an IP address and a PDN connection context corresponding to the TEID allocated by the new-side serving gateway, then determines a bearer context in the PDN connection context according to the QoS flow identifier, and obtains the IP address and the TEID of the bearer allocated by the data gateway according to the bearer context.

Or, the new-side service gateway determines the IP address and the bearer context corresponding to the TEID allocated by the new-side service gateway, and obtains the IP address and the TEID of the bearer allocated by the data gateway according to the bearer context.

Step 1224, the new-side serving gateway sends a second uplink data packet to the data gateway, where the second uplink data packet includes the IP address and the TEID of the bearer allocated by the data gateway.

Based on the above embodiments, the present application further provides a service gateway, which is applied to the communication system shown in fig. 2a, and is used to implement the functions of the service gateway (or enhanced service gateway) in the above embodiments or examples. Referring to fig. 13, the service gateway 1300 includes: a communication unit 1301 and a processing unit 1302, wherein:

The communication unit 1301 is configured to receive a first downlink data packet sent by a data gateway, where the first downlink data packet includes a first internet protocol IP address and a first tunnel endpoint identifier TEID; the processing unit 1302 is configured to determine, according to the first IP address and the first TEID, a quality of service QoS flow identifier and a second IP address and a second TEID of a packet data unit, PDU, session allocated by an access device; the communication unit 1301 is further configured to send a second downlink data packet to the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID;

alternatively, the first and second electrodes may be,

the communication unit 1301 is configured to receive a first uplink data packet sent by the access device, where the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier; the processing unit 1302 is configured to determine a fourth IP address and a fourth TEID of a bearer allocated by a data gateway according to the third IP address and the third TEID and the QoS flow identifier; the communication unit 1301 is further configured to send a second uplink data packet to the data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

In an optional implementation manner, the communication unit 1301 is further configured to receive a session establishment request message sent by a mobility management device, where the session establishment request message includes an access type of a terminal device, and the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network; the processing unit 1302 is further configured to allocate the third IP address and the third TEID of the packet data network PDN connection according to the access type; the communication unit 1301 is further configured to send a session establishment response message to the mobility management apparatus, where the session establishment response message includes the third IP address and the third TEID.

Exemplarily, the communication unit 1301 is further configured to send a bearer setup request message to the mobility management apparatus, where the bearer setup request message includes the third IP address and the third TEID.

Specifically, the communication unit 1301 is further configured to receive an update bearer request message or a first bearer setup response message sent by the mobility management apparatus, where the update bearer request message or the first bearer setup response message includes the second IP address, the second TEID, and the QoS flow identifier; sending an update bearer response message to the mobility management device based on the update bearer request message; or sending a second bearer establishment response message to the data gateway based on the first bearer establishment response message.

By adopting the service gateway provided by the embodiment of the application, when the service gateway is accessed to the 4G network through the 5G technology, the normal operation of the service can be ensured, and the influence on the service experience of the user can be avoided.

Based on the foregoing embodiments, an embodiment of the present application further provides an access device, which is applied to a communication system as shown in fig. 2a, and is used to implement the functions of the access device in the foregoing embodiments or examples. Referring to fig. 14, the access device 1400 includes: a communication unit 1401 and a processing unit 1402, wherein:

the communication unit 1401 is configured to receive a first downlink data packet sent by a service gateway, where the first downlink data packet includes a first internet protocol IP address and a first tunnel endpoint identifier TEID; the processing unit 1402 is configured to obtain a quality of service parameter in a quality of service QoS flow context corresponding to the first IP address and the first TEID; the communication unit 1401 is further configured to send a second downlink data packet to the terminal device according to the quality of service parameter;

alternatively, the first and second electrodes may be,

the communication unit 1401 is configured to receive a first uplink data packet sent by a terminal device; the processing unit 1402, configured to obtain a second IP address and a second TEID of a QoS flow allocated by a serving gateway in a QoS flow context in which the first uplink data packet is located; the communication unit 1401 is further configured to send a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

In an optional implementation manner, the communication unit 1401 is further configured to receive a PDU session resource update request message or a PDU session resource establishment request message or a handover request message sent by the mobility management device, where the PDU session resource update request message or the PDU session resource establishment request message or the handover request message includes the QoS flow identifier and the second IP address and the second TEID.

Illustratively, the communication unit 1401 is further configured to send a PDU session resource update response message or a PDU session resource establishment response message or a handover request response message to the mobility management device, where the PDU session resource update response message or the PDU session resource establishment response message or the handover request response message includes the first IP address and the first TEID of the QoS flow allocated by the access device for the downlink data packet.

By adopting the access equipment provided by the embodiment of the application, when the 4G network is accessed through the 5G technology, the normal operation of the service can be ensured, and the influence on the service experience of the user can be avoided.

Based on the above embodiments, the present application further provides a mobility management device, which is applied to the communication system shown in fig. 2a, and is used to implement the functions of the mobility management device (or enhanced mobility management network element) in the above embodiments or examples. Referring to fig. 15, the mobility management device 1500 includes: a communication unit 1501 and a processing unit 1502, in which:

The communication unit 1501 is configured to send and receive information;

the processing unit 1502 is configured to control the communication unit 1501 to receive a first message, where the first message is used to establish a PDU session or bearer; controlling the communication unit 1501 to send a second message to a serving gateway, where the second message includes a bearer identifier; controlling the communication unit 1501 to send a third message to the access device, where the third message includes a QoS flow identifier; wherein, the bearer identification and the QoS flow identification are used for identifying one bearer of the terminal equipment; the first message is a PDU session establishment request message sent by the terminal equipment, the second message is a session establishment request message, and the third message is a PDU session resource establishment request message; or, the first message is a bearer establishment request message sent by the serving gateway, the second message is a bearer establishment response message, and the third message is a PDU session resource update request message; or the first message is a forwarding switching request message sent by the source-side mobile management device, the second message is a session establishment request message, and the third message is a switching request message; the first message, the second message and the third message are used for establishing a channel for forwarding a service data packet.

In an optional implementation manner, when the second message is a session establishment request message, the second message further includes an access type of a terminal device, where the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network.

Illustratively, the processing unit 1502 is further configured to:

controlling the communication unit 1501 to receive a session establishment response message sent by the serving gateway, where the session establishment response message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

controlling the communication unit 1501 to send a PDU session resource establishment request message or a handover request message to the access device, where the PDU session resource establishment request message or the handover request message includes the first IP address and the first TEID;

the communication unit 1501 is controlled to receive a PDU session resource establishment response message or a handover request response message sent by an access device, where the PDU session resource establishment response message or the handover request response message includes a second IP address and a second TEID allocated by the access device; the second IP address and the second TEID are the IP address and the TEID of a PDU session or the IP address and the TEID of a QoS flow;

Control the communication unit 1501 to transmit an update bearer request message including the second IP address and the second TEID to the serving gateway.

Specifically, the update bearer request message further includes a QoS flow identifier.

In a possible implementation manner, the bearer establishment request message includes the first IP address and the first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

the processing unit 1502 is further configured to: controlling the communication unit 1501 to transmit a PDU session resource update request message to the access device; wherein, when the first address and the first TEID are an IP address and a TEID of a bearer, the PDU session resource update request message includes the first IP address and the first TEID, or when the first address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update request message does not include the first IP address and the first TEID;

controlling the communication unit 1501 to receive a PDU session resource update response message sent by the access device; wherein, the PDU session resource update response message includes a second IP address and a second TEID allocated by the access device, and the second IP address and the second TEID are an IP address and a TEID of a QoS flow; or when the first IP address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update response message does not include an IP address and a TEID allocated by an access device;

Controlling the communication unit 1501 to transmit a setup bearer response message to the serving gateway; the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID are an IP address and a TEID of a PDU session, the bearer establishment response message does not include an IP address and a TEID allocated by the access device; or, the bearer establishment response message includes the second IP address and the second TEID, where the second IP address and the second TEID are obtained by the mobility management device from a PDU session resource establishment response message or a handover request response message.

Specifically, the bearer establishment response message further includes the QoS flow identifier.

By adopting the mobile management equipment provided by the embodiment of the application, when the mobile management equipment is accessed to a 4G network through a 5G technology, normal operation of services can be ensured, and influence on service experience of users can be avoided.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Based on the above embodiments, the present application further provides a service gateway, which is applied to the communication system shown in fig. 2a, and is used to implement the functions of the service gateway (or enhanced service gateway) in the above embodiments or examples. Referring to fig. 16, the mobility management device 1600 may include: a communication interface 1601, and a processor 1602, optionally may also include a memory 1603. The processor 1602 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of the CPU and the NP. The processor 1602 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. When the processor 1602 implements the above functions, it may be implemented by hardware, or may be implemented by hardware executing corresponding software.

The communication interface 1601 and the processor 1602 are connected to each other. Optionally, the communication interface 1601 and the processor 1602 are connected to each other via a bus 1604; the bus 1604 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 16, but this is not intended to represent only one bus or type of bus.

The memory 1603 is coupled to the processor 1602 and is used for storing programs and the like necessary for the SRS transmission apparatus 1600. For example, the program may include program code including computer operating instructions. The memory 1603 may include RAM and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 1602 executes the application program stored in the memory 1603 to implement the function of the service gateway 1600.

Specifically, when implementing the functions of the service gateway (or enhanced service gateway) in the foregoing embodiments or examples, the service gateway 1600:

The communication interface 1601 is configured to receive a first downlink data packet sent by a data gateway, where the first downlink data packet includes a first internet protocol IP address and a first tunnel endpoint identifier TEID; the processor 1602 is configured to determine a quality of service (QoS) flow identifier and a second IP address and a second TEID of a Packet Data Unit (PDU) session allocated by an access device according to the first IP address and the first TEID; the communication interface 1601 is further configured to send a second downlink packet to the access device, where the second downlink packet includes the QoS flow identifier, the second IP address, and the second TEID;

alternatively, the first and second electrodes may be,

the communication interface 1601 is configured to receive a first uplink packet sent by the access device, where the first uplink packet includes a third IP address, a third TEID, and the QoS flow identifier; the processor 1602 is configured to determine a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identifier; the communication interface 1601 is further configured to send a second uplink data packet to the data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

In an optional implementation manner, the communication interface 1601 is further configured to receive a session establishment request message sent by the mobility management device, where the session establishment request message includes an access type of the terminal device, and the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network; the processor 1602 is further configured to allocate the third IP address and the third TEID of the packet data network PDN connection according to the access type; the communication interface 1601 is further configured to send a session setup response message to the mobile management device, where the session setup response message includes the third IP address and the third TEID.

Illustratively, the communication interface 1601 is further configured to send a bearer setup request message to the mobility management device, where the bearer setup request message includes the third IP address and the third TEID.

Specifically, the communication interface 1601 is further configured to receive an update bearer request message or a first bearer setup response message sent by the mobility management apparatus, where the update bearer request message or the first bearer setup response message includes the second IP address, the second TEID, and the QoS flow identifier; sending an update bearer response message to the mobility management device based on the update bearer request message; or sending a second bearer establishment response message to the data gateway based on the first bearer establishment response message.

Based on the foregoing embodiments, an embodiment of the present application further provides an access device, where the access device is applied to a communication system as shown in fig. 2a, and is used to implement the functions of the access device in the foregoing embodiments or examples. Referring to fig. 17, the mobility management apparatus 1700 may include: a communication interface 1701, and a processor 1702, optionally including a memory 1703. The processor 1702 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of the CPU and the NP. The processor 1702 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. The processor 1702 may be implemented by hardware when implementing the above functions, or may be implemented by hardware executing corresponding software.

The communication interface 1701 and the processor 1702 are interconnected. Optionally, the communication interface 1701 and the processor 1702 are interconnected via a bus 1704; the bus 1704 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 17, but this does not mean only one bus or one type of bus.

The memory 1703 is coupled to the processor 1702, and is configured to store programs and the like necessary for the SRS transmission apparatus 1700. For example, the program may include program code including computer operating instructions. The memory 1703 may include a RAM, and may further include a non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 1702 executes the application program stored in the memory 1703 to implement the functions of the access device 1700.

Specifically, when implementing the functions of the access device in the foregoing embodiments or examples, the mobility management device 1700:

The communication interface 1701 is configured to receive a first downlink data packet sent by a service gateway, where the first downlink data packet includes a first internet protocol IP address and a first tunnel endpoint identifier TEID; the processor 1702 is configured to obtain a quality of service parameter in a quality of service, QoS, flow context corresponding to the first IP address and the first TEID; the communication interface 1701 is further configured to send a second downlink data packet to the terminal device according to the qos parameter;

alternatively, the first and second electrodes may be,

the communication interface 1701 is configured to receive a first uplink data packet sent by a terminal device; the processor 1702, configured to obtain a second IP address and a second TEID of the QoS flow allocated by the serving gateway in the QoS flow context of the first uplink data packet; the communication interface 1701 is further configured to send a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

In an optional implementation, the communication interface 1701 is further configured to receive a PDU session resource update request message or a PDU session resource establishment request message or a handover request message sent by the mobility management device, where the PDU session resource update request message or the PDU session resource establishment request message or the handover request message includes the QoS flow identifier and the second IP address and the second TEID.

Illustratively, the communication interface 1701 is further configured to send a PDU session resource update response message or a PDU session resource establishment response message or a handover request response message to the mobility management device, where the PDU session resource update response message or the PDU session resource establishment response message or the handover request response message includes the first IP address and the first TEID of the QoS flow allocated by the access device for the downlink data packet.

Based on the foregoing embodiments, the present application further provides a mobility management device, which is applied to the communication system shown in fig. 2a, and is configured to implement the functions of the mobility management device (or enhanced mobility management network element) in the foregoing embodiments or examples. Referring to fig. 18, the mobility management device 1800 may include: a communication interface 1801 and a processor 1802, and optionally, a memory 1803. The processor 1802 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of the CPU and the NP. The processor 1802 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. When the processor 1802 implements the above functions, the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.

The communication interface 1801 and the processor 1802 are interconnected. Optionally, the communication interface 1801 and the processor 1802 are connected to each other through a bus 1804; the bus 1804 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 18, but this does not mean only one bus or one type of bus.

The memory 1803 is coupled to the processor 1802 and is used for storing programs and the like necessary for the SRS transmission apparatus 1800. For example, the program may include program code including computer operating instructions. The memory 1803 may include RAM, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 1802 executes the application program stored in the memory 1803 to implement the functions of the mobility management device 1800.

Specifically, when implementing the functions of the mobility management device (or the enhanced mobility management network element) in the foregoing embodiments or examples, the mobility management device 1800:

The communication interface 1801 is used for sending and receiving information;

the processor 1802, configured to control the communication interface 1801 to receive a first message, where the first message is used to establish a PDU session or bearer; controlling the communication interface 1801 to send a second message to a service gateway, where the second message includes a bearer identifier; controlling the communication interface 1801 to send a third message to the access device, where the third message includes a QoS flow identifier; wherein, the bearer identification and the QoS flow identification are used for identifying one bearer of the terminal equipment; the first message is a PDU session establishment request message sent by the terminal equipment, the second message is a session establishment request message, and the third message is a PDU session resource establishment request message; or, the first message is a bearer establishment request message sent by the serving gateway, the second message is a bearer establishment response message, and the third message is a PDU session resource update request message; or the first message is a forwarding switching request message sent by the source-side mobile management device, the second message is a session establishment request message, and the third message is a switching request message; the first message, the second message and the third message are used for establishing a channel for forwarding a service data packet.

Illustratively, the processor 1802 is further configured to:

controlling the communication interface 1801 to receive a session establishment response message sent by the service gateway, where the session establishment response message includes a first IP address and a first TEID allocated by the service gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

controlling the communication interface 1801 to send a PDU session resource establishment request message or a handover request message to the access device, where the PDU session resource establishment request message or the handover request message includes the first IP address and the first TEID;

controlling the communication interface 1801 to receive a PDU session resource establishment response message or a handover request response message sent by the access device, where the PDU session resource establishment response message or the handover request response message includes a second IP address and a second TEID allocated by the access device; wherein the second IP address and the second TEID are an IP address and a TEID of a PDU session or an IP address and a TEID of a QoS flow;

Controlling the communication interface 1801 to send an update bearer request message to the service gateway, where the update bearer request message includes the second IP address and the second TEID.

In a possible implementation manner, the bearer establishment request message includes a first IP address and a first TEID allocated by the serving gateway; the first address and the first TEID are IP addresses and TEIDs of PDN connection or IP addresses and TEIDs of load bearing;

the processor 1802 is further configured to: controlling the communication interface 1801 to send a PDU session resource update request message to the access device; wherein, when the first address and the first TEID are an IP address and a TEID of a bearer, the PDU session resource update request message includes the first IP address and the first TEID, or when the first address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update request message does not include the first IP address and the first TEID;

controlling the communication interface 1801 to receive a PDU session resource update response message sent by the access device; the PDU session resource updating response message comprises a second IP address and a second TEID which are allocated by the access equipment, wherein the second IP address and the second TEID are the IP address and the TEID of the QoS flow; or when the first IP address and the first TEID are an IP address and a TEID of a PDN connection, the PDU session resource update response message does not include an IP address and a TEID allocated by an access device;

Controlling the communication interface 1801 to send a bearer establishment response message to the service gateway; the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID are an IP address and a TEID of a PDU session, the bearer establishment response message does not include an IP address and a TEID allocated by the access device; or the bearer establishment response message includes the second IP address and the second TEID, where the second IP address and the second TEID are obtained by the mobility management device from a PDU session resource establishment response message or a handover request response message.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A method for forwarding a service data packet, comprising:

the method comprises the steps that a service gateway receives a first downlink data packet sent by a data gateway, wherein the first downlink data packet comprises a first Internet Protocol (IP) address and a first Tunnel Endpoint Identifier (TEID);

the service gateway determines a QoS flow identifier and a second IP address and a second TEID of a Packet Data Unit (PDU) session distributed by access equipment according to the first IP address and the first TEID;

The service gateway sends a second downlink data packet to the access device, wherein the second downlink data packet comprises the QoS flow identifier, the second IP address and the second TEID;

or

The service gateway receives a first uplink data packet sent by the access device, wherein the first uplink data packet comprises a third IP address, a third TEID and the QoS flow identification;

the service gateway determines a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identification;

and the service gateway sends a second uplink data packet to the data gateway, wherein the second uplink data packet comprises the fourth IP address and the fourth TEID.

2. The method of claim 1, wherein the method further comprises:

the service gateway receives a session establishment request message sent by mobile management equipment, wherein the session establishment request message comprises an access type of terminal equipment, and the access type is used for indicating the terminal equipment to access from a new wireless network or an evolved universal terrestrial radio access network;

the service gateway allocates the third IP address and the third TEID of the packet data network PDN connection according to the access type;

And the service gateway sends a session establishment response message to the mobile management equipment, wherein the session establishment response message comprises the third IP address and the third TEID.

3. The method of claim 2, wherein the method further comprises:

and the service gateway sends a bearer establishment request message to the mobile management equipment, wherein the bearer establishment request message comprises the third IP address and the third TEID.

4. The method of any one of claims 1-3, further comprising:

the service gateway receives an update bearer request message or a first bearer establishment response message sent by a mobile management device, wherein the update bearer request message or the first bearer establishment response message contains the second IP address, the second TEID and the QoS flow identification;

the service gateway sends an update bearing response message to the mobile management equipment based on the update bearing request message; or, the service gateway sends a second bearer establishment response message to the data gateway based on the first bearer establishment response message.

5. A method for forwarding a service data packet, comprising:

The method comprises the steps that access equipment receives a first downlink data packet sent by a service gateway, wherein the first downlink data packet comprises a first Internet Protocol (IP) address and a first Tunnel Endpoint Identifier (TEID);

the access equipment acquires a quality of service parameter in a quality of service (QoS) flow context corresponding to the first IP address and the first TEID;

the access equipment sends a second downlink data packet to the terminal equipment according to the service quality parameter;

or alternatively

The access equipment receives a first uplink data packet sent by the terminal equipment;

the access equipment acquires a second IP address and a second TEID of the QoS flow distributed by the service gateway in the QoS flow context of the first uplink data packet;

and the access equipment sends a second uplink data packet to the service gateway, wherein the second uplink data packet comprises the second IP address and the second TEID.

6. The method of claim 5, wherein the method further comprises:

the access device receives a PDU session resource update request message or a PDU session resource establishment request message or a handover request message sent by a mobility management device, where the PDU session resource update request message or the PDU session resource establishment request message or the handover request message includes a QoS flow identifier, the second IP address, and the second TEID.

7. The method of claim 5 or 6, further comprising:

the access device sends a PDU session resource update response message or a PDU session resource establishment response message or a switching request response message to a mobile management device, wherein the PDU session resource update response message or the PDU session resource establishment response message or the switching request response message contains the first IP address and the first TEID of the QoS flow allocated for the downlink data packet by the access device.

8. A serving gateway, comprising:

the system comprises a communication interface, a first tunnel endpoint identifier TEID and a second Internet protocol IP address, wherein the communication interface is used for receiving a first downlink data packet sent by a data gateway, and the first downlink data packet comprises a first Internet protocol IP address and the first tunnel endpoint identifier TEID;

a processor, configured to determine, according to the first IP address and the first TEID, a quality of service QoS flow identifier and a second IP address and a second TEID of a packet data unit, PDU, session allocated by an access device;

the communication interface is further configured to send a second downlink data packet to the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID;

Or

The communication interface is configured to receive a first uplink data packet sent by the access device, where the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier;

the processor is configured to determine a fourth IP address and a fourth TEID of a bearer allocated by the data gateway according to the third IP address and the third TEID and the QoS flow identifier;

the communication interface is further configured to send a second uplink data packet to the data gateway, where the second uplink data packet includes the fourth IP address and the fourth TEID.

9. The serving gateway of claim 8,

the communication interface is further configured to receive a session establishment request message sent by a mobility management device, where the session establishment request message includes an access type of a terminal device, and the access type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial radio access network;

the processor is further configured to allocate the third IP address and the third TEID of the packet data network PDN connection according to the access type;

the communication interface is further configured to send a session establishment response message to the mobility management device, where the session establishment response message includes the third IP address and the third TEID.

10. The serving gateway of claim 9, wherein the communication interface is further to:

and sending a bearer establishment request message to the mobility management device, wherein the bearer establishment request message includes the third IP address and the third TEID.

11. The service gateway of any of claims 8-10, wherein the communication interface is further to:

receiving an update bearer request message or a first bearer establishment response message sent by a mobile management device, wherein the update bearer request message or the first bearer establishment response message contains the second IP address, the second TEID and the QoS flow identifier;

sending an update bearer response message to the mobility management device based on the update bearer request message; or sending a second bearer establishment response message to the data gateway based on the first bearer establishment response message.

12. An access device, comprising:

the system comprises a communication interface, a first tunnel endpoint identification TEID and a second internet protocol IP address, wherein the communication interface is used for receiving a first downlink data packet sent by a service gateway, and the first downlink data packet comprises a first internet protocol IP address and a first tunnel endpoint identification TEID;

a processor configured to obtain a quality of service parameter in a quality of service QoS flow context corresponding to the first IP address and the first TEID;

The communication interface is further configured to send a second downlink data packet to the terminal device according to the quality of service parameter;

or

The communication interface is used for receiving a first uplink data packet sent by the terminal equipment;

the processor is configured to acquire a second IP address and a second TEID of a QoS flow allocated by a service gateway in a QoS flow context in which the first uplink data packet is located;

the communication interface is further configured to send a second uplink data packet to the serving gateway, where the second uplink data packet includes the second IP address and the second TEID.

13. The access device of claim 12, wherein the communication interface is further to:

receiving a PDU session resource update request message or a PDU session resource establishment request message or a handover request message sent by a mobile management device, wherein the PDU session resource update request message or the PDU session resource establishment request message or the handover request message contains a QoS flow identification, the second IP address and the second TEID.

14. The access device of claim 12 or 13, wherein the communication interface is further configured to:

sending a PDU session resource update response message or a PDU session resource establishment response message or a switching request response message to a mobile management device, wherein the PDU session resource update response message or the PDU session resource establishment response message or the switching request response message includes the first IP address and the first TEID of the QoS flow allocated for the downlink data packet by the access device.

15. A computer-readable storage medium having stored thereon computer-executable instructions for causing a computer to perform the method of any one of claims 1-7 when invoked by the computer.