WO2021047443A1 - 一种业务数据包转发的方法及装置 - Google Patents

一种业务数据包转发的方法及装置 Download PDF

Info

Publication number
WO2021047443A1
WO2021047443A1 PCT/CN2020/113342 CN2020113342W WO2021047443A1 WO 2021047443 A1 WO2021047443 A1 WO 2021047443A1 CN 2020113342 W CN2020113342 W CN 2020113342W WO 2021047443 A1 WO2021047443 A1 WO 2021047443A1
Authority
WO
WIPO (PCT)
Prior art keywords
teid
address
bearer
data packet
request message
Prior art date
Application number
PCT/CN2020/113342
Other languages
English (en)
French (fr)
Inventor
银宇
戚彩霞
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021047443A1 publication Critical patent/WO2021047443A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for forwarding service data packets.
  • the access network accesses the access and mobility management function (AMF) through the N2 interface, and the core network is based on services.
  • AMF access and mobility management function
  • SBA service-based architecture
  • the 5G network uses user plane function (UPF) equipment and access equipment to forward service data packets between terminal equipment and external data networks.
  • the access equipment and user plane function equipment are based on packet data unit (packet data unit).
  • PDU packet data unit
  • PDU session establishes a tunnel, and all service data packets related to the PDU session are transmitted in this tunnel.
  • the 5G network adopts a large number of new technologies, such as a service-oriented framework, hypertext transfer protocol (HTTP) or transport layer security (TLS), etc. These technologies have not been applied in mobile communication networks. Not mature enough. In addition, operators need to invest in the construction of new infrastructure for 5G networks, and the investment cost is relatively high. Therefore, the application of 5G networks is still relatively limited.
  • HTTP hypertext transfer protocol
  • TLS transport layer security
  • the present application provides a method and device for forwarding service data packets, which are used to ensure that services can be performed normally when accessing a 4G network through 5G technology.
  • the present application provides a method for forwarding service data packets.
  • the method may include: a serving gateway receives a first downlink data packet sent by a data gateway, where the first downlink data packet includes a first Internet protocol IP address and the first tunnel endpoint identifier TEID; the serving gateway determines the quality of service QoS flow identifier according to the first IP address and the first TEID, and the second IP address of the packet data unit PDU session assigned by the access device and A second TEID; the serving gateway sends a second downlink data packet to the access device, the second downlink data packet including 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, and the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier; the serving gateway according to the The third IP address, the third TEID, and the QoS flow identifier determine the fourth IP address and the
  • the serving gateway receives a session establishment request message sent by a mobile management device, and the session establishment request message includes an access type of the terminal device, and the access type is used to instruct the terminal device to renew Access to a wireless network or an evolved universal terrestrial radio access network; the serving gateway allocates the third IP address and the third TEID of the packet data network PDN connection according to the access type; the serving gateway sends The mobility management device sends a session establishment response message, and the session establishment response message includes the third IP address and the third TEID. This completes the establishment of the session.
  • the serving gateway sends a bearer establishment request message to the mobility management device, and the bearer establishment request message includes the third IP address and the third TEID. In this way, the bearer can be established later.
  • the serving gateway receives the bearer update request message or the first bearer establishment response message sent by the mobility management device, and the bearer update request message or the first bearer establishment response message includes the second IP address And the second TEID and the QoS flow identifier; the serving gateway sends an update bearer response message to the mobility management device based on the update bearer request message; or, the serving gateway sends an update bearer response message based on the first bearer establishment response The message sends a second bearer establishment response message to the data gateway. In this way, the subsequent bearer update or bearer establishment can be completed.
  • this application provides a method for forwarding service data packets.
  • the method may include: an access device receiving a first downlink data packet sent by a serving gateway, where the first downlink data packet contains a first Internet Protocol IP address and the first tunnel endpoint identifier TEID; the access device obtains the quality of service parameters in the context of the quality of service QoS flow corresponding to the first IP address and the first TEID; The service quality parameter sends a second downlink data packet to the terminal device; or, the access device receives the first uplink data packet sent by the terminal device; the access device obtains the QoS flow context in which the first uplink data packet is located The second IP address and the second TEID of the QoS flow allocated by the serving gateway in the server; the access device sends a second uplink data packet to the serving gateway, and the second uplink data packet contains the second IP address And the second TEID.
  • 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, the PDU session resource update request message or a PDU session resource establishment request message
  • the message or the handover request message includes the QoS flow identifier, the second IP address and the second TEID.
  • 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, the PDU session resource update response message or a PDU session resource establishment response message
  • the 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.
  • this application provides a method for forwarding service data packets.
  • the method may include: a mobility management device receives a first message, where the first message is used to establish a PDU session or bearer; and the mobility management device sends a service
  • the gateway sends a second message, the second message includes a bearer identifier; the mobility management device sends a third message to the access device, the third message includes a QoS flow identifier; the bearer identifier and the QoS flow Identifies a bearer used to identify a terminal device;
  • 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; or, the first message is a bearer setup request message sent by the serving gateway, the second message is a bearer setup response message, and the third message is a PDU session resource update request message; or the first The message is a forwarding handover request message sent by the source test mobile management device
  • the second message when the second message is a session establishment request message, the second message also contains the access type of the terminal device, and the access type is used to instruct the terminal device to renew the wireless network. Or evolved universal terrestrial radio access network access.
  • the mobility management device receives a session establishment response message sent by the serving gateway, and the session establishment response message includes the first IP address and the first TEID allocated by the serving gateway;
  • the first address and the first TEID are the IP address and TEID of the PDN connection or the IP address and TEID of the bearer;
  • the mobility management device sends a PDU session resource establishment request message or a handover request message to the access device,
  • the PDU session resource establishment request message or the handover request message includes the first IP address and the first TEID;
  • the mobility management device receives the PDU session resource establishment response message or the handover request response message sent by the access device,
  • the PDU session resource establishment response message or the handover request response message includes the second IP address and the second TEID allocated by the access device; wherein the second IP address and the second TEID are the IP address and the second TEID of the PDU session TEID is either the IP address and TEID of the QoS flow;
  • the mobility management device sends a
  • the update bearer request message also includes a QoS flow identifier.
  • the bearer establishment request message includes the first IP address and the first TEID allocated by the serving gateway; wherein the first address and the first TEID are the IP address and the first TEID of the PDN connection.
  • TEID is either the bearer’s IP address and TEID;
  • the mobility management device sends a PDU session resource update request message to the access device; where, when the first address and the first TEID are the bearer’s IP address and TEID
  • the PDU session resource update request message contains the first IP address and the first TEID, or when the first address and the first TEID are the IP address and TEID of the PDN connection,
  • the PDU session resource update request message does not include the first IP address and the first TEID;
  • the mobility management device receives the PDU session resource update response message sent by the access device; wherein, the PDU session resource
  • the update response message contains the second IP address and the second TEID allocated by the access device, and the second IP address and the second TEID are the IP address
  • the bearer establishment response message further includes the QoS flow identifier.
  • the present application also provides a service gateway, which has the function of implementing the service gateway in the above-mentioned method example of the first aspect.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the service gateway includes a processing unit and a communication unit. These units can perform the corresponding functions in the above-mentioned method example of the first aspect. For details, please refer to the detailed description in the method example, which will not be repeated here. .
  • the structure of the service gateway includes a communication interface and a processor, and optionally a memory.
  • the communication interface is used to send and receive data (information or signals, etc.), and to communicate with other devices in the communication system.
  • the processor is configured to support the service gateway to perform the corresponding function of the service gateway in the above-mentioned method in the first aspect.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the service gateway.
  • the present application also provides an access device that has the function of implementing the access device in the method example of the second aspect described above.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the access device includes a processing unit and a communication unit. These units can perform the corresponding functions in the method example of the second aspect. For details, please refer to the detailed description in the method example, which will not be described here. Go into details.
  • the structure of the access device includes a communication interface and a processor, and optionally may also include a memory.
  • the communication interface is used to send and receive data (information or signals, etc.), and to communicate with other devices in the communication system.
  • the device performs communication interaction, and the processor is configured to support the access device to perform the corresponding function of the access device in the above-mentioned second aspect method.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the access device.
  • the present application also provides a mobility management device that has the function of implementing the mobility management device in the method example of the third aspect.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the mobility management device includes a processing unit and a communication unit. These units can perform the corresponding functions in the method example of the third aspect. For details, please refer to the detailed description in the method example, which will not be described here. Go into details.
  • the structure of the mobile management device includes a communication interface and a processor, and optionally a memory.
  • the communication interface is used to send and receive data (information or signals, etc.), and to communicate with other devices in the communication system.
  • the device performs communication interaction, and the processor is configured to support the mobility management device to perform the corresponding functions of the mobility management device in the method of the third aspect described above.
  • the memory is coupled with the processor, and it stores program instructions and data necessary for the mobile management device.
  • the present application also provides a communication system, which includes at least the service gateway, access device, and mobility management device mentioned in the above design.
  • the serving gateway in the communication system may execute any method executed by the serving gateway in the foregoing method
  • the access device in the communication system may execute any method executed by the access device in the foregoing method.
  • a method, and the mobility management device in the communication system can execute any one of the methods executed by the mobility management device in the foregoing methods.
  • the present application provides a computer-readable storage medium that stores computer-executable instructions, and when called by the computer, the computer-executable instructions are used to make the computer Implementation of any one of the above-mentioned first aspect or any one of the possible designs of the first aspect, any one of the second or second aspects of any possible design, any one of the third aspects or any one of the third aspects Any one of the methods in the design.
  • this application provides a computer program product containing instructions that, when run on a computer, enable the computer to execute any one of the above-mentioned first aspect or first aspect of any possible design, second aspect, or second aspect Any one of the possible designs of the aspect, the third aspect, or any one of the possible designs of the third aspect.
  • the present application provides a chip, which is coupled with a memory, and is used to read and execute program instructions stored in the memory, so as to realize the above-mentioned first aspect or any one of the possibilities of the first aspect.
  • Figure 1 is a schematic diagram of a 5G network architecture in the prior art
  • Figure 2a is a schematic diagram of the architecture of a communication system provided by this application.
  • Figure 2b is a 4G NSA architecture diagram provided by this application.
  • FIG. 3 is a flowchart of a method for forwarding service data packets provided by this application
  • FIG. 4 is a flowchart of another method for forwarding service data packets provided by this application.
  • FIG. 5 is a flowchart of another method for forwarding service data packets provided by this application.
  • FIG. 6 is a flowchart of another method for forwarding service data packets provided by this application.
  • FIG. 7 is a flowchart of another method for forwarding service data packets provided by this application.
  • FIG. 8 is a flowchart of an example of a method for forwarding service data packets provided by this application.
  • FIG. 9 is a flowchart of an example of another method for forwarding service data packets provided by this application.
  • FIG. 10 is a flowchart of an example of another method for forwarding service data packets provided by this application.
  • FIG. 11 is a flowchart of an example of another method for forwarding service data packets provided by this application.
  • FIG. 12 is a flowchart of an example of another method for forwarding service data packets provided by this application.
  • FIG. 13 is a schematic structural diagram of a service gateway provided by this application.
  • FIG. 14 is a schematic structural diagram of an access device provided by this application.
  • FIG. 15 is a schematic structural diagram of a mobile management device provided by this application.
  • FIG. 16 is a structural diagram of a service gateway provided by this application.
  • FIG. 17 is a structural diagram of an access device provided by this application.
  • FIG. 18 is a structural diagram of a mobile management device provided by this application.
  • the embodiment of the present application provides a method and device for forwarding service data packets, which are used to ensure that the normal operation of the service can be ensured when accessing a 4G network through 5G technology.
  • the method and device described in this application are based on the same inventive concept. Since the method and the device have similar principles for solving the problem, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • the data packets (including uplink data packets and downlink data packets) involved in this application all refer to service data packets.
  • Figure 1 shows the architecture of a 5G network in the prior art.
  • the architecture of the 5G network includes a network slice selection function (NSSF) device and a network exposure function (NEF) device , Network function library function ((network function, NF) repository function, NRF) equipment, policy control function (PCF) equipment, unified data management (unified data management, UDM) equipment, application function (AF) ) Equipment, authentication server function (authentication server function, AUSF) equipment, access and mobility management function (AMF) equipment, session management function (SMF) equipment, service communication agent SCP , Terminal equipment (also known as user equipment (UE)), radio access network (RAN) equipment, user plane function (UPF) and data network (data network, DN).
  • NSF network slice selection function
  • NRF network exposure function
  • PCF policy control function
  • unified data management unified data management
  • UDM application function
  • AF application function
  • AMF access and mobility management function
  • SCP Session management function
  • Terminal equipment also known as user equipment (
  • the terminal equipment is connected to the access and mobility management function equipment through the N1 interface
  • the access network is connected to the access and mobility management function equipment through the N2 interface.
  • the core network is implemented based on a service-oriented architecture.
  • the 5G network adopts a large number of new technologies, such as a service framework, hypertext transfer protocol (HTTP) or transport layer security (TLS), etc., these technologies have not been applied in mobile communication networks. Not mature enough.
  • HTTP hypertext transfer protocol
  • TLS transport layer security
  • operators need to invest in the construction of new infrastructure for 5G networks, and the investment cost is relatively high, which leads to limited 5G network applications.
  • this application is based on the compatibility of the 5G network and the fourth generation (4th generation, 4G) network, and proposes that the terminal device and the access network can be connected to the evolved packet core network (evolved packet core, EPC) through the N1 or N2 interface. ), in the case of reuse of EPC network infrastructure, support 5G native access.
  • EPC evolved packet core 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. This is different from the method of 5G service data packet forwarding. Therefore, it can be implemented in this application.
  • accessing a 4G network through 5G technology normal business operations can be guaranteed.
  • this application provides a possible communication system architecture, which is a possible communication system architecture to which the method for forwarding service data packets provided by the embodiments of this application is applicable, as shown in Figure 2a
  • the architecture of the communication system may include a terminal device, an access network, a mobility management device, a service gateway, a data gateway, and a message data network, where:
  • Terminal equipment which can also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • the terminal device may include a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • the terminal devices may be: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile Internet devices (MID), wearable devices, virtual reality (VR) devices, augmented Augmented reality (AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) Wireless terminals in ), wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc.
  • MID mobile Internet devices
  • VR virtual reality
  • AR augmented Augmented reality
  • Wireless terminals in wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) Wireless terminals in ), wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc.
  • the terminal equipment is accessed through the local wireless access network.
  • the mobile management device is responsible for the location management, connection management, security authentication, gateway selection and other functions of the mobile user equipment.
  • the serving gateway is the local access gateway of the terminal device, responsible for connection management and data forwarding related to the access technology.
  • the data gateway is the gateway for terminal devices to access external data networks.
  • the EPC network can also be a network in which the control plane and the user plane are separated, that is, the control plane and the user plane of the service gateway and the data gateway are separated, and are divided into the service gateway of the user plane, the service gateway of the control plane, the data gateway of the user plane and the data gateway of the user plane.
  • the data 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 on the control plane is responsible for data forwarding control, and the data gateway on the user plane is responsible for data forwarding.
  • the service gateway on the control plane can be deployed together with the data gateway on the control plane, and the service gateway on the user plane can also be deployed together with the data gateway on the user plane.
  • the terminal device can be a 5G terminal; for the evolved universal terrestrial radio access network (evolved universal terrestrial radio access network, evolved E-UTRAN), the new radio (new radio, NR) access network, access
  • the equipment can be the next generation evolved NodeB (ng-eNB) or the next generation NodeB (gNB) in the 5G mobile communication system
  • the core network is the network element of the EPC network
  • the mobile management equipment can be
  • the mobility management entity mobility management entity
  • the serving gateway may be a serving gateway (serving gateway, S-GW)
  • the data gateway may be a packet data network gateway (packet data network gateway, PDN-GW).
  • the serving gateway can be the serving gateway user plane (SGW-U) of the user plane and the serving gateway control plane (SGW-C) of the control plane
  • the data gateway can be The data gateway on the user plane (packet data network gateway user plane, PGW-U) and the data gateway on the control plane (packet data network gateway control plane, PGW-C).
  • Mobile management equipment and service gateways can be enhanced on the basis of the existing EPC network to support the native access of 5G terminal equipment.
  • 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.
  • the terminal device in the 4G non-standalone architecture is a 4G terminal device, which is connected to the mobile management device through 4G NAS, and the main access network is connected to the mobile management device through the 4G S1 interface.
  • the user plane data packets of the terminal equipment can be forwarded through the primary access network and the secondary access network at the same time.
  • the primary access network is for E-UTRAN, and the corresponding access device is an evolved NodeB (eNodeB).
  • the second access network is an evolved E-UTRAN or NR access network, and the corresponding access device is ng-eNB or gNB.
  • the high bandwidth provided by the second access network enables 4G terminal devices to enjoy a service experience comparable to that of the 5G network.
  • the NSA architecture requires the deployment of a primary access network and a secondary access network, which is suitable for local hotspot deployment, and the entire network deployment is expensive. Therefore, the use of the network shown in FIG. 2a provided by the present application can avoid the above-mentioned problems and flexibly realize the access to the 4G network through the 5G technology.
  • FIG. 2a and FIG. 2b are not limited to only include the devices shown in the figures, and may also include other devices not shown in the figures. Specifically, this application will not be described here. One enumerate.
  • the method for forwarding service data packets provided by the embodiment of the present application is suitable for the communication system as shown in FIG. 2a.
  • the specific process of the method may include:
  • Step 301 The serving 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) ).
  • IP internet protocol
  • TEID tunnel endpoint identifier
  • the service gateway is an enhanced service gateway that enhances the existing service gateway.
  • Step 302 The serving gateway determines, according to the first IP address and the first TEID, the quality of service (QoS) flow identifier and the packet data unit (PDU) session allocated by the access device.
  • QoS quality of service
  • PDU packet data unit
  • the serving gateway obtains the bearer context corresponding to the first IP address and the first TEID, thereby obtaining the QoS flow identifier and 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.
  • first downlink data packet and the second downlink data packet are data packets for the same service
  • the second data packet is the service gateway sending the first downlink data packet After removing the first IP address and the first TEID in, the data packet obtained after the QoS flow identifier and the second IP address and the second TEID are encapsulated.
  • the access device determines the PDU session corresponding to the second IP address and the second TEID according to the second IP address and the second TEID
  • the corresponding QoS flow is determined according to the QoS flow identifier, and then the access device sends a third downlink data packet to the terminal device according to the quality of service QoS parameters associated with the QoS flow.
  • 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.
  • the serving gateway before the serving gateway receives the first downlink data packet sent by the data gateway, the serving gateway receives the session establishment request message sent by the mobile management device
  • the session establishment request message includes the access type of the terminal device, and the access type is used to instruct the terminal device to access from a new wireless network or an evolved universal terrestrial radio access network;
  • the access type allocates the third IP address and the third TEID of the PDN connection;
  • the serving gateway sends a session establishment response message to the mobility management device, and the session establishment response message includes the third IP address and the third TEID.
  • Three TEID Three TEID.
  • the mobility management device is an enhanced mobility management device that enhances the existing mobility management device.
  • the access type may be the type of the access device accessed by the terminal device, or the type of the wireless access network, or the type of the terminal device; wherein, the type of the access device
  • the type is an evolved base station ng-eNB type or a next-generation base station gNB type
  • the type of the radio access network is a new radio NR type or an evolved universal terrestrial radio access network Evolved E-UTRAN type
  • the type of the terminal equipment It is 5G type.
  • the session establishment request message received by the serving gateway further includes an associated bearer identifier allocated by the mobility management device for the default bearer of the PDN connection.
  • the associated bearer identifier is both the PDN connection identifier and the bearer identifier of the currently established bearer, and the currently established bearer is the default bearer.
  • the mobility management device may allocate the PDN connection identifier according to the PDU session identifier obtained from the terminal device. For example, the value of the PDN connection identifier and the value of the PDU session identifier are the same, or the PDU session identifier is set by a certain algorithm. The identification calculates the PDN connection identification.
  • the mobility management device may also allocate the PDN connection identifier according to the existing method, and locally store the corresponding relationship between the PDU session identifier and the PDN connection identifier, which is not limited in this application.
  • the serving gateway after receiving the session establishment request message, sends a session establishment request message 2 to the data gateway (here written as session establishment request message 2 for the purpose of communicating with the service gateway).
  • the received session establishment request message is distinguished, and has no other meaning); the service gateway receives the establishment session response message 2 sent by the data gateway (here written as the establishment session response message 2 to distinguish it from the establishment session request message sent by the service gateway , Has no other meaning).
  • the session establishment request message 2 may include the associated bearer identifier, the access type, 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 fourth TEID of the bearer allocated by the data gateway.
  • the serving gateway receives an update bearer request message sent by the mobility management device, and the update bearer request message includes the second IP address and the first IP address. 2. TEID and the QoS flow identifier; the serving gateway sends an update bearer response message to the mobility management device based on the update bearer request message.
  • the serving gateway before the serving gateway receives the first downlink data packet sent by the data gateway, the serving gateway sends the mobile The management device sends a bearer establishment request message, and the bearer establishment request message includes the third IP address and the third TEID.
  • the serving gateway before the serving gateway sends the bearer establishment request message to the mobility management device, it receives the bearer establishment request message 2 sent by the data gateway (here written as the bearer establishment request message 2 for the purpose of establishing the bearer establishment request message sent by the service gateway).
  • the bearer request message is distinguished 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.
  • the serving gateway receives a first bearer establishment response message sent by the mobility management device, and the first bearer establishment response message includes the second IP Address, the second TEID, and the QoS flow identifier; the serving gateway sends a second bearer establishment response message to the data gateway based on the first bearer establishment response message, and the second bearer establishment response message includes Bearer identification, the first IP and the first TEID.
  • the first bearer setup response message is used to respond to the above bearer setup request message
  • the second bearer setup response message is used to respond to the above bearer setup request message 2.
  • the service data packets of the terminal equipment can be forwarded normally to ensure the normal operation of the service and avoid affecting users Business experience. That is to say, when the above method realizes the access to the 4G network through the 5G technology, the normal operation of the service can be guaranteed.
  • Another method for forwarding service data packets provided by the embodiment of the present application is applicable to the communication system as shown in FIG. 2a.
  • the specific process of the method may include:
  • Step 401 The serving gateway receives a first uplink data packet sent by an access device, where the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier.
  • the service gateway is an enhanced service gateway that enhances the existing service gateway.
  • the access device after receiving the third uplink data packet sent by the terminal device, the access device sends the first uplink data packet to the serving gateway.
  • the third uplink data packet is sent on a corresponding air interface bearer
  • the access device determines the QoS flow corresponding to the third uplink data packet according to the air interface bearer, and the access device obtains the QoS flow in the QoS flow context.
  • the QoS flow identifier, and the third IP address and the third TEID in the PDU session context corresponding to the QoS flow; the third IP address and the third TEID are allocated by the serving gateway.
  • Step 402 The serving gateway determines the fourth IP address and the fourth TEID of the bearer allocated by the data gateway according to the third IP address, the third TEID, and the QoS flow identifier.
  • the serving gateway determines the PDN connection context corresponding to the third IP address and the third TEID, then determines the bearer context in the PDN connection context according to the QoS flow identifier, and obtains it according to the bearer context The fourth IP address and the fourth TEID.
  • Step 403 The 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.
  • the operation performed by the serving gateway is the same as In the embodiment shown in FIG. 3, the operations performed by the serving gateway before receiving the first downlink data packet sent by the data gateway are similar, and the details can be referred to each other, and details are not described herein again.
  • the serving gateway before the serving gateway receives the first uplink data packet sent by the access device, the serving gateway The operations performed are similar to those performed by the serving gateway before receiving the first downlink data packet sent by the data gateway in the embodiment shown in FIG. 3, and reference may be made to each other for details, and details are not described herein again.
  • the service data packets of the terminal equipment can be forwarded normally to ensure the normal operation of the service and avoid affecting users Business experience. That is to say, when the above method realizes the access to the 4G network through the 5G technology, the normal operation of the service can be guaranteed.
  • the service gateway is enhanced to support the tunnel of the PDN connection, so that the service data 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 the forwarding of downlink service data packets
  • the embodiment shown in FIG. 4 implements the forwarding of uplink service data packets.
  • the two embodiments are basically the same except that the forwarding process is different.
  • the two embodiments shown in Figure 5 and Figure 6 shown below are different from the embodiments shown in Figures 3 and 4 in that the embodiments shown in Figures 5 and 6 support QoS flows through enhanced access devices.
  • the tunnel enables the service data packets of the terminal equipment to be forwarded normally, avoiding affecting the user's service experience.
  • the embodiment shown in FIG. 5 realizes the forwarding of downlink service data packets
  • the embodiment shown in FIG. 6 realizes the forwarding of uplink service data packets.
  • the two embodiments are basically the same except that the forwarding process is different.
  • Another method for forwarding service data packets provided by the embodiment of the present application is applicable to the communication system as shown in FIG. 2a.
  • the specific process of the method may include:
  • Step 501 The access device receives a first downlink data packet sent by the serving gateway, where the first downlink data packet includes a first IP address and a first TEID.
  • the access device is an enhanced access device that enhances the existing access device.
  • the serving 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 contains the IP address and TEID allocated by the serving gateway for forwarding the downlink data packet carried by the serving gateway, and the serving gateway according to the IP address and TEID allocated by the serving gateway for forwarding the downlink data packet carried by the serving gateway.
  • the address and TEID determine the first IP address and the first TEID of the QoS flow allocated by the access device.
  • Step 502 The access device obtains the quality of service parameter in the QoS flow context corresponding to the first IP address and the first TEID.
  • the access device determines the QoS flow context corresponding to the first IP address and the first TEID, so as to obtain the quality of service parameter.
  • Step 503 The access device sends a second downlink data packet to the terminal device according to the service quality parameter.
  • the access device before the access device receives the first downlink data packet sent by the serving gateway, the access device receives the PDU session sent by the mobility management device A resource establishment request message, the PDU session resource establishment request message contains the QoS flow identifier and the second IP address and the second TEID of the QoS flow allocated by the serving gateway; then, the PDU session resource establishment request message also contains the message sent to A PDU session establishment accept message of the terminal device, and the access device forwards the PDU session establishment accept message to the terminal device based on the PDU session resource establishment request message.
  • the PDU session resource establishment request message may further include a PDU session identifier.
  • the PDU session establishment accept message may include the PDU session identifier and the QoS flow identifier.
  • the access device sends a PDU session resource establishment response message to the mobility management device.
  • the PDU session resource establishment response message includes the first IP of the QoS flow allocated by the access device for the downlink data packet. Address and the first TEID.
  • the PDU session resource establishment response message may further include the PDU session identifier and the QoS flow identifier.
  • the access device before the access device receives the first downlink data packet sent by the serving gateway, the access device receives the The PDU session resource update request message sent by the mobile management device, the PDU session resource update request message includes the QoS flow identifier, the second IP address and the second TEID; the PDU session resource update request message also includes A PDU session update request message sent to a terminal device, and the access device forwards the PDU session update request message to the terminal device based on the PDU session resource update request message.
  • the PDU session update request message includes the QoS flow identifier.
  • the access device sends a PDU session resource update response message to the mobility management device, and the PDU session resource update response message includes the first IP address of the QoS flow allocated by the access device for the downlink data packet and The first TEID.
  • the PDU session resource update response message also includes the QoS flow identifier.
  • the access device receives the PDU session update complete message sent by the terminal device and sends it to the mobility management device Forward the PDU session update complete message, where the PDU session update complete message includes the QoS flow identifier, which is used to indicate that the QoS flow is established.
  • the access device in the handover procedure in which the access device, the mobility management device, and the serving gateway are handed over, the access device is the new side access device, that is, the access device after the handover .
  • the access device before the access device receives the first downlink data packet sent by the serving gateway, the access device receives the mobility management device (the mobility management device here is the mobility management device of the new side, That is, the handover request message sent by the mobile management device after the handover), the handover request message includes the QoS flow identifier, the second IP address, and the second TEID.
  • the access device sends a handover request response message to the mobility management device, and the handover request response message contains the first IP address of the QoS flow allocated by the access device for the downlink data packet and the The first TEID.
  • the service data packets of the terminal equipment can be forwarded normally to ensure the normal operation of the service and avoid affecting users Business experience. That is to say, when the above method realizes the access to the 4G network through the 5G technology, the normal operation of the service can be guaranteed.
  • Another method for forwarding service data packets provided by the embodiment of the present application is applicable to the communication system as shown in FIG. 2a.
  • the specific process of the method may include:
  • Step 601 The access device receives the first uplink data packet sent by the terminal device.
  • the access device is an enhanced access device that enhances the existing access device.
  • Step 602 The access device obtains the second IP address and the second TEID of the QoS flow allocated by the serving gateway in the QoS flow context where the first uplink data packet is located.
  • 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.
  • the serving gateway after receiving the second uplink data packet, the serving gateway sends a third uplink data packet to the data gateway.
  • the serving gateway determines the IP address and TEID of the bearer allocated by the data gateway according to the second IP address and the second TEID; the third uplink data packet includes the IP address of the bearer allocated by the data gateway And TEID.
  • the operation performed by the access device is similar to that shown in FIG. 5
  • the operations performed by the access device before receiving the first downlink data packet sent by the serving gateway are similar, and specific reference may be made to each other, and details are not described herein again.
  • the operation performed by the access device before the access device receives the first uplink data packet sent by the terminal device It is similar to the operation performed by the access device before receiving the first downlink data packet sent by the serving gateway in the embodiment shown in FIG. 5, and reference may be made to each other for details, and details are not described herein again.
  • the access device in the handover procedure in which the access device, the mobility management device, and the serving gateway are handed over, the access device is the new side access device, that is, the access device after the handover .
  • the operation performed by the access device before the access device receives the first uplink data packet sent by the terminal device, the operation performed by the access device is the same as the operation performed by the access device in the embodiment shown in FIG.
  • the operations performed before the first downlink data packet sent are similar, which can be referred to each other for details, and details are not described herein again.
  • the service data packets of the terminal equipment can be forwarded normally to ensure the normal operation of the service and avoid affecting users Business experience. That is to say, when the above method realizes the access to the 4G network through the 5G technology, the normal operation of the service can be guaranteed.
  • FIG. 7 is another method for forwarding service data packets provided by an embodiment of the present application, and is suitable for the communication system shown in FIG. 2a.
  • the 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.
  • the mobility management device is an enhanced mobility management device that enhances the existing mobility management device.
  • Step 702 The mobility management device sends a second message to the serving 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.
  • the bearer identifier and the QoS flow identifier are used to identify a bearer of the terminal device.
  • the first message is a PDU session establishment request message sent by the terminal device
  • the second message is a session establishment request message
  • the third message is a PDU session resource establishment request.
  • the first message is a bearer establishment request message sent by the serving gateway
  • the second message is a bearer establishment response message
  • the third message is a PDU Session resource update request message
  • the mobility management device is a new-side mobility management device
  • the first message is sent by the source test mobility management device Forward a handover request message
  • the second message is a session establishment request message
  • the third message is a handover request message.
  • the first message, the second message, and the third message are used to establish a channel for forwarding service data packets.
  • the second message when the second message is a session establishment request message in a PDU session establishment scenario, the second message also includes the access type of the terminal device, and the access The type is used to indicate that the terminal device accesses from a new wireless network or an evolved universal terrestrial wireless access network.
  • the mobility management device receives a session establishment response message sent by the serving gateway, and the session establishment response message includes the first IP address and the first TEID allocated by the serving gateway; wherein , The first address and the first TEID are the IP address and TEID of the PDN connection or the IP address and TEID of the bearer;
  • the mobility management device receives the PDU session resource establishment response message or the handover request response message sent by the access device, and the PDU session resource establishment response message or the handover request response message contains the second IP address and the second IP address allocated by the access device.
  • TEID where the second IP address and the second TEID are the IP address and TEID of the PDU session or the IP address and TEID of the QoS flow;
  • the mobility management device sends a bearer update request message to the serving gateway, where the bearer update request message includes the second IP address and the second TEID.
  • the update bearer request message further includes a QoS flow identifier.
  • the bearer establishment request message includes the first IP address and the first TEID allocated by the serving gateway; wherein, the first address and the first TEID are connected by the PDN IP address and TEID or the IP address and TEID of the bearer;
  • the mobility management device sends a PDU session resource update request message to the access device; wherein, when the first address and the first TEID are the bearer's IP address and TEID, 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 the IP address and TEID of the PDN connection, the PDU session resource update request message does not include The first IP address and the first TEID;
  • the mobility management device receives 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 The IP address and the second TEID are the IP address and TEID of the PDU session or the IP address and TEID of the QoS flow; or, when the first address and the first TEID are the IP address and TEID of the PDN connection, The PDU session resource update response message does not include the IP address and TEID allocated by the access device;
  • the mobility management device sends a bearer establishment response message to the serving 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 included
  • the bearer establishment response message does not include the IP address and TEID allocated by the access device; or, the bearer establishment response message includes the second IP address and The second TEID, 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.
  • the bearer establishment response message further includes a QoS flow identifier.
  • the service data packets of the terminal equipment can be forwarded normally to ensure the normal operation of the service and avoid affecting users Business experience. That is to say, when the above method realizes the access to the 4G network through the 5G technology, the normal operation of the service can be guaranteed.
  • the embodiments of the present application provide an example of a method for forwarding service data packets.
  • This example is a scenario in which a PDU session is established.
  • the service gateway is enhanced to support the tunnel of the PDN connection, so that the service data packets of the terminal device can be Forward normally.
  • the serving gateway is an enhanced serving gateway
  • the mobility management device is an enhanced mobility management device.
  • the enhanced serving gateway and the enhanced mobility management device are shown. Referring to Figure 8, the 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.
  • the PDU session establishment request message includes the PDU session identifier allocated by the terminal device for the PDU session.
  • the PDU session establishment process is triggered.
  • the terminal device when the terminal device sends a PDU session establishment request message to the enhanced mobility management device, the terminal device sends a 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 the access type of the terminal device, and the access type is used to instruct the terminal device to access from a new wireless network or an evolved universal terrestrial radio access network.
  • Step 804 The enhanced service gateway sends a session establishment request message 2 to the data gateway for establishing a PDN connection.
  • the session establishment request message 2 may include the associated bearer identifier, the access type, and the IP address and TEID allocated by the enhanced service gateway for the downlink data packet forwarding of the default bearer of this PDN connection, which is shown in Figure 3.
  • Step 805 Establish a connection access network (Internet protocol-connectivity access network, IP-CAN) session of the PDN connection between the data gateway and a policy and charging rules function entity (PCRF). It is used to obtain corresponding billing and service quality strategies.
  • IP-CAN Internet protocol-connectivity access network
  • PCRF policy and charging rules function entity
  • 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, the IP address and TEID allocated by the data gateway for forwarding uplink data packets of the default bearer of this PDN connection, that is, in the embodiment shown in FIG. 3 The fourth IP address and the fourth TEID involved.
  • Step 807 The enhanced service gateway sends a session establishment response message to the enhanced mobility management device.
  • the enhanced service gateway learns that the terminal device is connected from Evolved E-UTRAN or NR, and then the enhanced service gateway allocates an IP address and TEID for forwarding of uplink data packets for this PDN connection
  • the IP address and TEID are the IP address and TEID of the PDN connection
  • the enhanced service gateway includes the IP address and TEID in the session establishment response message, that is, the first step involved in the embodiment shown in FIG. 3 Three IP addresses and third TEID.
  • the session establishment response message also 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 includes a PDU session identifier, a QoS flow identifier, and an IP address and TEID allocated by the enhanced service gateway.
  • the PDU session resource establishment request message also includes a PDU session establishment acceptance message sent to the terminal device.
  • the enhanced mobility management device allocates a QoS flow identifier.
  • the QoS flow identifier may be the same as the bearer identifier, or the QoS flow identifier may be calculated from the bearer identifier through a certain algorithm, or the allocation of the QoS flow identifier has nothing to do with the bearer identifier.
  • 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 establishment acceptance message to the terminal device.
  • the PDU session establishment accept message includes the PDU session identifier and the QoS flow identifier.
  • Step 810 The access device sends a PDU session resource establishment response message to the enhanced mobility management device.
  • the PDU session resource establishment response message includes the PDU session identifier, the QoS flow identifier, and the IP address and TEID allocated by the access device for forwarding downlink data packets of the PDU session, that is, the embodiment shown in FIG. 3 In the second IP address and second TEID.
  • Step 811 The enhanced mobility management network element sends a bearer update request message to the enhanced service gateway.
  • 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 also includes the QoS flow identifier and the bearer identifier, as described in this process
  • the bearer identifier is the associated bearer identifier.
  • the enhanced mobility management device determines the bearer identifier according to the QoS flow identifier (the QoS flow identifier uniquely identifies a bearer in the terminal device), or further, the enhanced mobility management device determines the PDN connection identifier according to the PDU session identifier , Determine the bearer identifier in the PDN connection according to the QoS flow identifier (the QoS flow identifier uniquely identifies a 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.
  • Step 813 The enhanced service gateway receives the first downlink data packet sent by the data gateway.
  • the first downlink data packet includes a first IP address and a first TEID.
  • Step 814 The enhanced service gateway determines, according to the first IP address and the first TEID, a QoS flow identifier and a second IP address and a second TEID of the PDU session allocated by the access device.
  • the enhanced service gateway obtains the bearer context corresponding to the first IP address and the first TEID, thereby obtaining the QoS flow identifier and the second IP address and the first TEID according to the bearer context. Two TEID.
  • Step 815 The enhanced service 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.
  • 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, and determines the corresponding QoS according to the QoS flow identifier Then, the access device forwards the third downlink data packet to the terminal device according to the quality of service QoS parameters associated with the QoS flow.
  • Step 817 The access device receives a third uplink data packet sent by the terminal device, the third uplink data packet is sent on a corresponding air interface bearer, and the access device determines the third uplink data according to the air interface bearer For the QoS flow corresponding to the packet, the access device obtains the QoS flow identifier in the QoS flow context, and the third IP address and the third TEID in the PDU session context corresponding to the QoS flow.
  • Step 818 The access device sends the first uplink data packet to the enhanced service gateway.
  • the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier.
  • the third IP address and the third TEID are allocated by the enhanced service gateway.
  • Step 819 The enhanced service gateway determines the fourth IP address and the fourth TEID of the bearer allocated by the data gateway according to the third IP address, the third TEID, and the QoS flow identifier.
  • the enhanced service gateway determines the PDN connection context corresponding to the third IP address and the third TEID, and then determines the bearer context in the PDN connection context according to the QoS flow identifier, and according to the bearer context Obtain the fourth IP address and the fourth TEID.
  • Step 820 The enhanced service 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.
  • the embodiments of this application provide an example of another method for forwarding service data packets.
  • This example is in the scenario of PDU session update triggered by the bearer establishment process, through the enhanced service gateway to support the tunnel of the PDN connection, so that The service data packet of the terminal device can be forwarded normally.
  • the serving gateway is an enhanced serving gateway
  • the mobility management device is an enhanced mobility management device.
  • the enhanced serving gateway and the enhanced mobility management device are shown. Referring to Figure 9, the specific process of this example may include:
  • Step 901 The policy and charging rule function entity triggers an IP-CAN session update and sends an IP-CAN session update request to the data gateway to send updated charging and quality of service rules to the data gateway.
  • Step 902 The data gateway makes a decision to trigger the bearer establishment process, and sends a bearer establishment request message 2 to the enhanced service gateway.
  • the bearer establishment request message 2 contains the IP address allocated by the data gateway for forwarding the uplink data packet corresponding to this bearer.
  • TEID that is, the fourth IP address and the 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 the third IP address and the 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 the IP address and the third TEID of the PDN connection.
  • TEID that is, the IP address and 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 allocates a QoS flow identification (allocation flow identification) to the corresponding QoS flow of the bearer
  • the PDU session resource update request message contains the QoS flow identification
  • the allocation method of the QoS flow identification is referred to in the above embodiment The method will not be described in detail here.
  • the PDU session resource update request message also includes a PDU session update request message sent to the terminal device.
  • Step 905 The access device forwards a PDU session update request message to the 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.
  • the PDU session update complete message includes a QoS flow identifier, which is used to indicate that the QoS flow is established.
  • 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 enhanced mobility management device.
  • the PDU session resource update response message includes a QoS flow identifier, which is used to indicate that the QoS flow is established.
  • Step 909 The enhanced mobility management device sends a first bearer establishment response message to the enhanced service gateway.
  • the enhanced mobility management device allocates a bearer identifier for this bearer.
  • the QoS flow identifier may be the same as the bearer identifier, or the bearer identifier can be calculated from the QoS flow identifier through a certain algorithm, or the assignment of the bearer identifier and the QoS flow identifier are not However, 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 process.
  • the first bearer establishment response message includes the bearer identifier.
  • the first bearer establishment response message also includes the IP address and TEID assigned by the access device (that is, the second IP address and the second TEID of the PDU session assigned by the access device, which is the example shown in FIG. 8
  • the IP address and TEID involved in step 810 in step 810), or the first bearer establishment response message does not include the IP address and TEID allocated by the access device.
  • the enhanced service gateway responds to Evolved E-UTRAN or For the terminal equipment accessed by the NR, all downlink service data packets corresponding to this PDN connection are sent to the IP address and TEID received in step 811 in the embodiment shown in FIG. 8.
  • Step 910 The enhanced service gateway sends a second bearer setup response message to the data gateway, where the second bearer setup response message includes the bearer identifier and the information allocated by the enhanced service gateway for forwarding the downlink data packet corresponding to this bearer.
  • IP address and TEID that is, the first IP address and the first TEID in the embodiment shown in FIG. 3).
  • Step 911 The data gateway sends an IP-CAN session update response message to the policy and charging rule function entity.
  • Step 912 The enhanced service gateway receives the first downlink data packet sent by the data gateway.
  • the first downlink data packet includes a first IP address and a first TEID.
  • Step 913 The enhanced service gateway determines the QoS flow identifier and the second IP address and second TEID of the PDU session allocated by the access device according to the first IP address and the first TEID.
  • the enhanced service gateway obtains the bearer context corresponding to the first IP address and the first TEID, thereby obtaining the QoS flow identifier and the second IP address and the second TEID according to the bearer context.
  • TEID the bearer context corresponding to the first IP address and the first TEID
  • Step 914 The enhanced service 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.
  • 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, and determines the corresponding QoS according to the QoS flow identifier Flow, and then the access device sends the third downlink data packet to the terminal device according to the quality of service QoS parameters associated with the QoS flow.
  • Step 916 The access device receives a third uplink data packet sent by the terminal device, the third uplink data packet is sent on a corresponding air interface bearer, and the access device determines the third uplink data according to the air interface bearer For the QoS flow corresponding to the packet, the access device obtains the QoS flow identifier in the QoS flow context, and the third IP address and the third TEID in the PDU session context corresponding to the QoS flow.
  • Step 917 The access device sends the first uplink data packet to the enhanced service gateway.
  • the first uplink data packet includes a third IP address, a third TEID, and the QoS flow identifier.
  • the third IP address and the third TEID are allocated by the enhanced service gateway.
  • Step 918 The enhanced service gateway determines the fourth IP address and the fourth TEID of the bearer allocated by the data gateway according to the third IP address, the third TEID, and the QoS flow identifier.
  • the enhanced service gateway determines the PDN connection context corresponding to the third IP address and the third TEID, and then determines the bearer context in the PDN connection context according to the QoS flow identifier, and according to the bearer context Obtain the fourth IP address and the fourth TEID.
  • Step 919 The enhanced service 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.
  • the sequence of the downstream data packet forwarding process and the upstream data packet forwarding process is not limited, and the figure is only an example of a sequence. It should be understood that the uplink data packet may be forwarded first, and the downlink data packet may be forwarded later, which is not limited in this application.
  • the embodiments of the present application also provide another example of a method for forwarding service data packets.
  • This example is a scenario in which a PDU session is established.
  • the access device is an enhanced access device
  • the mobility management device is an enhanced mobility management device.
  • the enhanced access device and the enhanced mobility management device are shown. Referring to Figure 10, the 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 the PDU session identifier allocated by the terminal device for the PDU session.
  • the PDU session establishment process is triggered.
  • the terminal device when the terminal device sends a PDU session establishment request message to the enhanced mobility management device, the terminal device sends a 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 the 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 mobility management device selects a serving gateway and a data gateway.
  • Step 1003 The enhanced mobility management device sends a session establishment request message to the serving gateway.
  • the session establishment request message includes the access type of the terminal device, and the access type is used to instruct the terminal device to access from a new wireless network or an evolved universal terrestrial radio access network.
  • Step 1004 The serving gateway sends a session establishment request message 2 to the data gateway for establishing a PDN connection.
  • the session establishment request message 2 may include the associated bearer identifier, the access type, and the IP address and TEID allocated by the serving gateway for forwarding downlink data packets of the default bearer of this PDN connection.
  • Step 1005 An IP-CAN session of the PDN connection is established between the data gateway and the policy and charging rule function entity to obtain 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, the IP address and TEID allocated by the data gateway for forwarding uplink data packets of the default bearer of this PDN connection.
  • Step 1007 The serving gateway sends a session establishment response message to the enhanced mobility management device.
  • the session establishment response message contains the IP address and TEID allocated by the serving gateway for forwarding of the uplink data packet of the default bearer of this PDN connection (that is, the second IP address and the second TEID involved in the embodiment shown in FIG. 6 ), the second IP address and the second TEID are bearer or QoS flow.
  • the session establishment response message also includes 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 the PDU session identifier, the QoS flow identifier, the IP address and TEID of the QoS flow (that is, the IP address and TEID allocated by the service gateway in step 1007).
  • the PDU session resource establishment request message also includes a PDU session establishment acceptance message sent to the terminal device.
  • the enhanced mobility management device allocates a QoS flow identifier.
  • the QoS flow identifier may be the same as the bearer identifier, or the QoS flow identifier may be calculated from the bearer identifier through a certain algorithm, or the allocation of the QoS flow identifier has nothing to do with the bearer identifier.
  • 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 1009 The enhanced access device sends a PDU session establishment acceptance message to the terminal device.
  • the PDU session establishment accept message includes the PDU session identifier and the QoS flow identifier.
  • 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 the PDU session identifier, the QoS flow identifier, and the IP address and TEID allocated by the enhanced access device for forwarding downlink data packets of the QoS flow of the PDU session, which is shown in Figure 4 The first IP address and the first TEID in the illustrated embodiment.
  • Step 1011 The enhanced mobility management device sends a bearer update request message to the serving gateway.
  • the update bearer request message contains the IP address and TEID of the bearer, the IP address and TEID received by the enhanced mobility management network element in step 1010, the bearer identifier, the bearer identifier in this process is the associated bearer identifier .
  • the enhanced mobility management device determines the bearer identifier according to the QoS flow identifier (the QoS flow identifier uniquely identifies a bearer in the terminal device), or further, the enhanced mobility management device determines the PDN connection identifier according to the PDU session identifier , Determine the bearer identifier in the PDN connection according to the QoS flow identifier (the QoS flow identifier uniquely identifies a bearer in the PDN connection).
  • Step 1012 The serving gateway sends an update bearer response message to the enhanced mobility management device to indicate that the bearer update is successful.
  • Step 1013 The serving gateway receives a third downlink data packet sent by the data gateway, and the third downlink data packet contains the IP address assigned by the serving gateway for forwarding downlink data packets of the default bearer of this PDN connection And TEID.
  • the serving gateway determines the first IP address and the first TEID of the QoS flow allocated by the enhanced access device according to the IP address and TEID allocated by the serving gateway for forwarding downlink data packets of the default bearer of this PDN connection.
  • Step 1014 The serving 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 quality of service parameter in the QoS flow context corresponding to the first IP address and the first TEID.
  • the enhanced access device determines the QoS flow context corresponding to the first IP address and the first TEID, so as to obtain the quality of service parameter.
  • Step 1016 The enhanced access device sends a second downlink data packet to the terminal device according to the quality of service parameter.
  • Step 1017 The enhanced access device receives the first uplink data packet sent by the terminal device.
  • Step 1018 The enhanced access device obtains the second IP address and the second TEID of the QoS flow allocated by the serving gateway in the QoS flow context where the first uplink data packet is located.
  • 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.
  • the serving gateway determines the IP address and TEID of the bearer allocated by the data gateway according to the second IP address and the second TEID; the third uplink data packet includes the IP address of the bearer allocated by the data gateway Address and TEID.
  • the embodiments of the present application also provide an example of another method for forwarding service data packets.
  • This example is in the scenario of PDU session update.
  • the access device is enhanced to support QoS flow tunnels. , So that the service data packet of the terminal device can be forwarded normally.
  • the access device is an enhanced access device
  • the mobility management device is an enhanced mobility management device.
  • the enhanced access device and the enhanced mobility management device are shown. Referring to Figure 11, the specific process of this example may include:
  • Step 1101 The policy and charging rule function entity triggers an IP-CAN session update, and sends an IP-CAN session update request to the data gateway to send updated charging and quality of service rules to the data gateway.
  • Step 1102 The data gateway decides to trigger the bearer establishment process, and sends a bearer establishment request message 2 to the serving gateway.
  • the bearer establishment request message 2 contains the IP address allocated by the data gateway for forwarding the uplink data packet corresponding to this bearer and TEID.
  • Step 1103 The serving gateway sends a bearer establishment request message to the enhanced mobility management device, and the bearer establishment request message includes the IP address and TEID allocated by the serving gateway for forwarding the uplink data packet corresponding to the bearer, that is,
  • the IP address and TEID are the bearer IP address and TEID, 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 allocates a QoS flow identification (allocation flow identification) to the corresponding QoS flow of the bearer
  • the PDU session resource update request message contains the QoS flow identification
  • the allocation method of the QoS flow identification is referred to in the above embodiment The method will not be described in detail here.
  • the PDU session resource update request message also carries the IP address and TEID of the QoS flow, that is, the IP address and TEID allocated by the serving gateway in step 1103 for forwarding the uplink data packet corresponding to this bearer.
  • the PDU session resource update request message also includes a PDU session update request message sent to the terminal device.
  • Step 1105 The enhanced access device sends a PDU session update request message to the 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.
  • the PDU session update complete message includes a QoS flow identifier, which is used to indicate that the QoS flow is established.
  • 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, which is used to indicate that the QoS flow is established.
  • the PDU session resource update response message also contains the IP address and TEID of the QoS flow, that is, the IP address and TEID allocated by the enhanced access device for forwarding the downlink data packet corresponding to this QoS flow, that is, the IP address And TEID are the IP address and 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 serving gateway.
  • the enhanced mobility management device allocates a bearer identifier for this bearer.
  • the QoS flow identifier may be the same as the bearer identifier, or the bearer identifier can be calculated from the QoS flow identifier through a certain algorithm, or the assignment of the bearer identifier and the QoS flow identifier are not However, 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 process.
  • the first bearer establishment response message includes the bearer identifier.
  • the first bearer establishment response message also includes the IP address and TEID of the bearer, that is, the IP address and TEID allocated by the enhanced access device received by the enhanced mobility management network element in step 1108.
  • Step 1110 The serving gateway sends a second bearer setup response message to the data gateway, where the second bearer setup response message includes the bearer identifier and the IP address assigned by the serving gateway for forwarding the downlink data packet corresponding to the bearer And TEID.
  • Step 1111 the data gateway sends an IP-CAN session update response message to the policy and charging rule function entity.
  • Step 1112 The serving gateway receives a third downlink data packet sent by the data gateway, where the third downlink data packet includes the IP address and TEID allocated by the serving gateway for forwarding the downlink data packet corresponding to this bearer .
  • the serving gateway determines the first IP address and the first TEID of the QoS flow allocated by the enhanced access device according to the IP address and TEID allocated by the serving gateway for forwarding the downlink data packet corresponding to the bearer.
  • Step 1113 The serving 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 the quality of service parameter in the QoS flow context corresponding to the first IP address and the first TEID.
  • the enhanced access device determines the QoS flow context corresponding to the first IP address and the first TEID, so as to obtain the quality of service parameter.
  • Step 1115 The enhanced access device sends a second downlink data packet to the terminal device according to the quality of service 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 serving gateway in the QoS flow context where the first uplink data packet is located.
  • 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 serving gateway sends a third uplink data packet to the data gateway.
  • the serving gateway determines the IP address and TEID of the bearer allocated by the data gateway according to the second IP address and the second TEID; the third uplink data packet contains the IP address of the bearer allocated by the data gateway Address and TEID.
  • the sequence of the downstream data packet forwarding process and the upstream data packet forwarding process is not limited, and the figure is only an example of the sequence. It should be understood that the uplink data packet may be forwarded first, and the downlink data packet may be forwarded later, which is not limited in this application.
  • the embodiments of the present application provide an example of a method for forwarding service data packets.
  • This example is an example of forwarding service data packets in a handover process in which an access device, a mobility management device, and a serving gateway are handed off.
  • the handover process may be a process in which a 4G to 5G mobility management device changes and a service gateway changes; in this process, the source access device is a 4G base station eNodeB, and the new access device is an ng-eNB or gNB.
  • the handover process can be a process in which the 5G to 5G mobility management device changes and the serving gateway changes; in this process, the source-side access device is ng-eNB or gNB, and the new-side access device (target access Equipment) is ng-eNB or gNB.
  • the specific process of this example may include:
  • Step 1201 The source-side access device triggers a handover process, and sends a handover request message to the source-side mobility management device.
  • the source-side access device detects that the signal strength of the terminal device under the new-side access device exceeds a certain threshold, and triggers the terminal device to switch to the new-side access device.
  • the handover request message includes an access type
  • the access type is used to indicate the access type of the terminal device in the new access device.
  • the access type may be a type of an access device accessed by the terminal device, or a type of a wireless access network, or a type of the terminal device.
  • the type of the access equipment can be the next-generation evolved base station ng-eNB type or the next-generation base station gNB type; the type of the wireless access network is the new wireless NR Type or Evolved E-UTRAN type; the type of the terminal equipment is 5G type.
  • the first handover request message further includes an identifier of the target access device (that is, the new side access device).
  • Step 1202 the source-side mobility management device sends a forwarding handover request message to the new-side mobility management device (target mobility management device).
  • the forwarding switching request message includes the access type.
  • the forwarding handover request message also includes the identity of the target access device (ie, the new side access device), and the context of the terminal device, including the context of one or more established PDN connections of the terminal device,
  • 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 TEID assigned by the data gateway.
  • Step 1203 The new-side mobility management device sends a session establishment request message to the new-side serving gateway (target serving gateway).
  • the session establishment request message includes the access type, the bearer identifier of each bearer, and the IP address and TEID assigned by the data gateway.
  • Step 1204 The new-side serving gateway sends a session establishment response message to the new-side mobile management device.
  • the new-side serving gateway allocates the IP address of the packet data network PDN connection and the TEID according to the access type (that is, the embodiment shown in FIG. 3 involves The third IP address and the third TEID); the session establishment response message contains the IP address of the packet data network PDN connection allocated by the new-side serving gateway according to the access type and the TEID.
  • the new-side serving gateway allocates the bearer's IP address and TEID
  • the session establishment response message includes the new-side serving gateway's allocation The IP address and TEID of the bearer.
  • 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.
  • the handover request message includes the IP address and TEID allocated by the new-side serving gateway in step 1204.
  • the handover request message also includes the QoS flow identifier 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 the IP address and TEID allocated by the new-side access device for forwarding downlink data packets , QoS flow identification.
  • the IP address and TEID allocated by the new-side access device for forwarding downlink data packets are the second IP address and the second TEID involved in the embodiment shown in FIG. 3;
  • the IP address and TEID allocated by the new-side access device for forwarding downlink data packets are the first IP address and the first IP address involved in the embodiment shown in FIG. 5. TEID.
  • Step 1207 The new-side mobility management device sends a forwarding handover request response message to the source-side mobility management device to instruct the new side to establish a successful bearer context.
  • Step 1208 The source-side mobility management device sends a switching instruction to the source-side access device, which is used to instruct the terminal device to switch to the target side (ie, the new side).
  • Step 1209 The source-side access device forwards the switching instruction to the terminal device, which is used to instruct the terminal device to switch to the target side.
  • Step 1210 The terminal device switches to the target side, and sends a handover complete 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 mobility management device sends a handover completion notification message to the source-side mobility management device, so that the source-side mobility management device releases resources on the source side.
  • Step 1213 The new-side mobility management device sends a first update bearer request message to the new-side serving gateway, where the first update bearer request message includes the IP address and TEID allocated by the access device in step 1206.
  • 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 the IP address and TEID of the bearer allocated by the new-side serving gateway for forwarding downlink data packets.
  • Step 1215 The data gateway sends a first update bearer response message to the new-side serving 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 includes the IP address and TEID allocated by the new-side serving gateway.
  • Step 1218 The new-side serving gateway determines the IP address and TEID of the PDU session allocated by the new-side access device according to the IP address and TEID allocated by the new-side serving gateway.
  • the new-side serving gateway obtains the IP address assigned by the new-side serving gateway and the bearer context corresponding to the TEID, thereby obtaining the QoS flow identifier according to the bearer context and the PDU session assigned by the new-side access device IP address and TEID.
  • the new-side serving gateway determines the IP address and TEID of the QoS flow allocated by the new-side access device according to the IP address and TEID allocated by the new-side serving gateway.
  • the new-side serving gateway obtains the IP address assigned by the new-side serving gateway and the bearer context corresponding to the TEID, thereby obtaining the IP address and the IP address of the QoS flow assigned by the new-side access device according to the bearer context.
  • TEID the IP address assigned by the new-side serving gateway and the bearer context corresponding to the TEID
  • 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 PDU session allocated by the new-side access device IP address and TEID.
  • 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 IP address and TEID of the 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.
  • 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 TEID of the PDU session allocated by the new side access device,
  • the corresponding QoS flow is determined 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 quality of service QoS parameters associated with the QoS flow.
  • 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 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 quality of service 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, the third uplink data packet is sent on a corresponding air interface bearer, and the new side access device determines according to the air interface bearer For the QoS flow corresponding to the third uplink data packet, the new-side access device obtains the QoS flow identifier in the QoS flow context, and the IP address and TEID allocated by the new-side serving gateway in the PDU session context corresponding to the QoS flow.
  • the new-side access device obtains the IP address and TEID of the QoS flow allocated by the new-side serving 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.
  • the first uplink data packet includes the IP address and TEID of the QoS flow allocated by the new-side serving gateway.
  • Step 1223 The new-side serving gateway determines the IP address and TEID of the bearer allocated by the data gateway according to the IP address and TEID allocated by the new-side serving gateway.
  • the new-side serving gateway determines the IP address allocated by the new-side serving gateway and the PDN connection context corresponding to the TEID, and then determines the bearer context in the PDN connection context according to the QoS flow identifier, and according to the bearer The context obtains the IP address and TEID of the bearer assigned by the data gateway.
  • the new-side serving gateway determines the bearer context corresponding to the IP address and TEID assigned by the new-side serving gateway, and obtains the IP address and TEID of the bearer assigned 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 TEID of the bearer allocated by the data gateway.
  • the embodiments of the present application also provide a service gateway, which is applied to the communication system as shown in FIG. 2a, and is used to implement the service gateway (or enhanced service gateway) in the above embodiments or examples.
  • the service gateway 1300 includes: a communication unit 1301 and a processing unit 1302, where:
  • 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 According to the first IP address and the first TEID, determine the quality of service QoS flow identifier and the second IP address and the second TEID of the packet data unit PDU session allocated by the access device; the communication unit 1301 is also used to communicate with the Sending a second downlink data packet by the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID;
  • 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 The fourth IP address and the fourth TEID of the bearer allocated by the data gateway are determined according to the third IP address, the third TEID, and the QoS flow identifier; the communication unit 1301 is also used to send the data to the data gateway Sending a second uplink data packet, where the second uplink data packet includes the fourth IP address and the fourth TEID.
  • the communication unit 1301 is further configured to receive a session establishment request message sent by a mobile management device, and the session establishment request message includes the access type of the terminal device, and the access type It is used to instruct the terminal device to access from a new wireless network or an evolved universal terrestrial wireless access network; the processing unit 1302 is also used to allocate the third IP of the packet data network PDN connection according to the access type Address and the third TEID; the communication unit 1301 is further configured to send a session establishment response message to the mobility management device, and the session establishment response message includes the third IP address and the third TEID.
  • the communication unit 1301 is further configured to send 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.
  • the communication unit 1301 is further configured to receive a bearer update request message or a first bearer establishment response message sent by the mobility management device, and the bearer update request message or the first bearer establishment response message includes the second IP address. And the second TEID and the QoS flow identifier; send an update bearer response message to the mobility management device based on the update bearer request message; or send a second bearer response message to the data gateway based on the first bearer establishment response message 2. Create a bearer response message.
  • Using the service gateway provided by the embodiment of the present application can ensure the normal operation of the service when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • the embodiments of the present application also provide an access device, which is applied to the communication system as shown in FIG. 2a, and is used to implement the functions of the access device in the foregoing embodiment or example.
  • the access device 1400 includes: a communication unit 1401 and a processing unit 1402, where:
  • the communication unit 1401 is configured to receive a first downlink data packet sent by a serving gateway, where the first downlink data packet contains a first Internet Protocol IP address and a first tunnel endpoint identifier TEID; the processing unit 1402 is configured to Acquire the quality of service parameter in the 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 ;
  • the communication unit 1401 is configured to receive the first uplink data packet sent by the terminal device; the processing unit 1402 is configured to obtain the second QoS flow allocated by the serving gateway in the QoS flow context where the first uplink data packet is located. IP address and a second TEID; the communication unit 1401 is further configured to send a second uplink data packet to the serving gateway, and the second uplink data packet includes the second IP address and the second TEID.
  • 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 mobile management device, 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.
  • 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 mobile management device, the PDU session resource update response message or a PDU session resource establishment response message
  • the 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.
  • Using the access device provided in the embodiment of the present application can ensure the normal operation of the service when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • the embodiments of the present application also provide a mobility management device, which is applied to the communication system as shown in FIG. 2a, and is used to implement the mobility management device (or enhanced mobility) in the above embodiment or example.
  • Management network element function.
  • the mobility management device 1500 includes: a communication unit 1501 and a processing unit 1502, where:
  • the communication unit 1501 is used to send and receive information
  • the processing unit 1502 is configured to control the communication unit 1501 to receive a first message, and the first message is used to establish a PDU session or bearer; and to control the communication unit 1501 to send a second message to the service gateway, the second message is
  • the message includes a bearer identifier; the communication unit 1501 is controlled to send a third message to the access device, and the third message includes a QoS flow identifier; wherein, the bearer identifier and the QoS flow identifier are used to identify the terminal device A bearer;
  • 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; or, the first One message is a bearer setup request message sent by the serving gateway, the second message is a bearer setup response message, and the third message is a PDU session resource update request message; or the first message is a source test mobile management device A forwarding handover request message sent, the second message is
  • the second message when the second message is a session establishment request message, the second message further includes the access type of the terminal device, and the access type is used to indicate the terminal device Access from a new wireless network or an evolved universal terrestrial wireless access network.
  • processing unit 1502 is further configured to:
  • the communication unit 1501 is controlled to receive the PDU session resource establishment response message or the handover request response message sent by the access device.
  • the PDU session resource establishment response message or the handover request response message contains the second IP address and the second IP address allocated by the access device. Two TEIDs; where the second IP address and the second TEID are the IP address and TEID of the PDU session or the IP address and TEID of the QoS flow;
  • the update bearer request message also includes a QoS flow identifier.
  • the bearer establishment request message includes a first IP address and a first TEID allocated by the serving gateway; wherein the first address and the first TEID are the IP addresses of the PDN connection Address and TEID or the IP address and TEID of the bearer;
  • the processing unit 1502 is further configured to: control the communication unit 1501 to send a PDU session resource update request message to the access device; wherein, when the first address and the first TEID are the bearer's IP address and TEID When the PDU session resource update request message contains the first IP address and the first TEID, or when the first address and the first TEID are the IP address and TEID of the PDN connection, The PDU session resource update request message does not include the first IP address and the first TEID;
  • the communication unit 1501 Control the communication unit 1501 to receive the PDU session resource update response message sent by the access device; wherein the PDU session resource update response message contains the second IP address and the second TEID allocated by the access device, so The second IP address and the second TEID are the IP address and TEID of the QoS flow; or, when the first IP address and the first TEID are the IP address and TEID of the PDN connection, the PDU session resource The update response message does not include the IP address and TEID assigned by the access device;
  • the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID
  • the bearer establishment response message does not include the IP address and TEID assigned by the access device; or, the bearer establishment response message includes the second IP address and the TEID.
  • the second TEID, 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.
  • the bearer establishment response message also includes the QoS flow identifier.
  • Using the mobile management device provided by the embodiment of the present application can ensure that the service is normally performed when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods 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 may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including a number of instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the embodiments of the present application also provide a service gateway, which is applied to the communication system as shown in FIG. 2a, and is used to implement the service gateway (or enhanced service gateway) in the above embodiment or example.
  • the mobility management device 1600 may include a communication interface 1601 and a processor 1602, and 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 CPU and NP, or the like.
  • the processor 1602 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL generic array logic
  • the processor 1602 implements the above-mentioned functions, it may be implemented by hardware, and of course, it may also be implemented by hardware executing corresponding software.
  • the communication interface 1601 and the processor 1602 are connected to each other.
  • the communication interface 1601 and the processor 1602 are connected to each other through a bus 1604;
  • the bus 1604 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard). Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.
  • the memory 1603 is coupled with the processor 1602, and is used to store the necessary programs of the SRS transmission device 1600 and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1603 may include RAM, or may also include non-volatile memory, such as at least one disk memory.
  • the processor 1602 executes the application program stored in the memory 1603 to realize the function of the service gateway 1600.
  • the serving gateway 1600 implements the function of the serving gateway (or enhanced serving gateway) in the foregoing embodiment or example:
  • 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 the quality of service QoS flow identifier and the second IP address and second TEID of the packet data unit PDU session allocated by the access device according to the first IP address and the first TEID; the communication interface 1601 is also used to communicate with Sending a second downlink data packet by the access device, where the second downlink data packet includes the QoS flow identifier, the second IP address, and the second TEID;
  • the communication interface 1601 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 1602 It is used to determine the fourth IP address and the fourth TEID of the bearer allocated by the data gateway according to the third IP address, the third TEID, and the QoS flow identifier; the communication interface 1601 is also used to communicate to the data gateway Sending a second uplink data packet, where the second uplink data packet includes the fourth IP address and the fourth TEID.
  • the communication interface 1601 is further configured to receive a session establishment request message sent by a mobility management device, and the session establishment request message includes the access type of the terminal device, and the access type It is used to instruct the terminal device to access from a new wireless network or an evolved universal terrestrial wireless access network; the processor 1602 is also used to allocate the third IP of the packet data network PDN connection according to the access type Address and the third TEID; the communication interface 1601 is also used to send a session establishment response message to the mobility management device, and the session establishment response message includes the third IP address and the third TEID.
  • the communication interface 1601 is further configured to send 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.
  • the communication interface 1601 is further configured to receive a bearer update request message or a first bearer establishment response message sent by a mobility management device, and the bearer update request message or the first bearer establishment response message includes the second IP address. And the second TEID and the QoS flow identifier; send an update bearer response message to the mobility management device based on the update bearer request message; or send a second bearer response message to the data gateway based on the first bearer establishment response message 2. Create a bearer response message.
  • Using the service gateway provided by the embodiment of the present application can ensure the normal operation of the service when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • the mobility management device 1700 may include a communication interface 1701 and a processor 1702, and optionally may also include a memory 1703.
  • the processor 1702 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP), or a combination of CPU and NP, or the like.
  • the processor 1702 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL generic array logic
  • the processor 1702 implements the above functions, it may be implemented by hardware, and of course, it may also be implemented by hardware executing corresponding software.
  • the communication interface 1701 and the processor 1702 are connected to each other.
  • the communication interface 1701 and the processor 1702 are connected to each other through a bus 1704;
  • the bus 1704 may be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard). Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • the memory 1703 is coupled with the processor 1702, and is used to store necessary programs and the like of the SRS transmission device 1700.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1703 may include RAM, or may also include 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 function of the access device 1700.
  • the mobility management device 1700 implements the function of the access device in the foregoing embodiment or example:
  • the communication interface 1701 is configured to receive a first downlink data packet sent by a serving 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 Acquire the quality of service parameter in the 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 quality of service parameter ;
  • the communication interface 1701 is configured to receive the first uplink data packet sent by the terminal device; the processor 1702 is configured to obtain the second QoS flow allocated by the serving gateway in the QoS flow context where the first uplink data packet is located. IP address and a second TEID; the communication interface 1701 is further configured to send a second uplink data packet to the serving gateway, and the second uplink data packet includes the second IP address and the second TEID.
  • 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 mobile management device, 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.
  • 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 mobile management device, the PDU session resource update response message or a PDU session resource establishment response message
  • the 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.
  • Using the access device provided in the embodiment of the present application can ensure the normal operation of the service when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • the embodiments of the present application also provide a mobility management device, which is applied to the communication system as shown in FIG. 2a, and is used to implement the mobility management device (or enhanced) in the above embodiments or examples.
  • Mobile management network element function.
  • the mobility management device 1800 may include a communication interface 1801 and a processor 1802, and optionally may also include a memory 1803.
  • the processor 1802 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP, or the like.
  • the processor 1802 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL generic array logic
  • the processor 1802 implements the above-mentioned functions, it may be implemented by hardware, and of course, it may also be implemented by hardware executing corresponding software.
  • the communication interface 1801 and the processor 1802 are connected to each other.
  • 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 or an extended industry standard structure (Extended Industry Standard). Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used to represent in FIG. 18, but it does not mean that there is only one bus or one type of bus.
  • the memory 1803 is coupled with the processor 1802, and is used to store the necessary programs of the SRS transmission device 1800 and the like.
  • the program may include program code, and the program code includes computer operation instructions.
  • the memory 1803 may include RAM, or may also include non-volatile memory, such as at least one disk memory.
  • the processor 1802 executes the application program stored in the memory 1803 to realize the function of the mobile management device 1800.
  • the mobility management device 1800 implements the functions of the mobility management device (or enhanced mobility management network element) in the foregoing embodiment or example:
  • the communication interface 1801 is used to send and receive information
  • the processor 1802 is configured to control the communication interface 1801 to receive a first message, and the first message is used to establish a PDU session or bearer; and to control the communication interface 1801 to send a second message to the service gateway, the second message is The message includes a bearer identifier; the communication interface 1801 is controlled to send a third message to the access device, and the third message includes a QoS flow identifier; wherein, the bearer identifier and the QoS flow identifier are used to identify the terminal device A bearer; 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; or, the first One message is a bearer setup request message sent by the serving gateway, the second message is a bearer setup response message, and the third message is a PDU session resource update request message; or the first message is a source test mobile management device A forwarding handover request message sent, the second message is a session establishment request
  • the second message when the second message is a session establishment request message, the second message further includes the access type of the terminal device, and the access type is used to indicate the terminal device Access from a new wireless network or an evolved universal terrestrial wireless access network.
  • processor 1802 is further configured to:
  • the communication interface 1801 is controlled to receive the session establishment response message sent by the service gateway, and the session establishment response message includes the first IP address and the first TEID allocated by the service gateway; wherein, the first address and the first TEID are assigned by the service gateway.
  • the first TEID is the IP address and TEID of the PDN connection or the IP address and TEID of the bearer;
  • the communication interface 1801 is controlled to receive the PDU session resource establishment response message or the handover request response message sent by the access device.
  • the PDU session resource establishment response message or the handover request response message contains the second IP address and the second IP address allocated by the access device. Two TEIDs; where the second IP address and the second TEID are the IP address and TEID of the PDU session or the IP address and TEID of the QoS flow;
  • the update bearer request message also includes a QoS flow identifier.
  • the bearer establishment request message includes a first IP address and a first TEID allocated by the serving gateway; wherein, the first address and the first TEID are the IP addresses of the PDN connection Address and TEID or the IP address and TEID of the bearer;
  • the processor 1802 is further configured to: control 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 the bearer's IP address and TEID When the PDU session resource update request message contains the first IP address and the first TEID, or when the first address and the first TEID are the IP address and TEID of the PDN connection, The PDU session resource update request message does not include the first IP address and the first TEID;
  • the PDU session resource update response message contains the second IP address and the second TEID allocated by the access device, so The second IP address and the second TEID are the IP address and TEID of the QoS flow; or, when the first IP address and the first TEID are the IP address and TEID of the PDN connection, the PDU session resource
  • the update response message does not include the IP address and TEID assigned by the access device;
  • the bearer establishment response message includes the second IP address and the second TEID; or, when the second IP address and the second TEID
  • the bearer establishment response message does not include the IP address and TEID assigned by the access device; or, the bearer establishment response message includes the second IP address and the TEID.
  • the second TEID, 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.
  • the bearer establishment response message also includes the QoS flow identifier.
  • Using the mobile management device provided by the embodiment of the present application can ensure that the service is normally performed when accessing the 4G network through the 5G technology, and avoid affecting the user's service experience.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

一种业务数据包转发的方法及装置，用以实现通过5G技术接入4G网络时，保证业务正常进行。方法为：服务网关接收数据网关发送的第一下行数据包，根据第一下行数据包包含的第一IP地址和第一TEID确定QoS流标识以及接入设备分配的PDU会话的第二IP地址和第二TEID；向接入设备发送第二下行数据包，第二下行数据包包含QoS流标识以及第二IP地址和第二TEID；或者，服务网关接收接入设备发送的第一上行数据包，根据第一上行数据包包含的第三IP地址和第三TEID以及QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；向数据网关发送第二上行数据包，第二上行数据包包含第四IP地址和第四TEID。

Description

一种业务数据包转发的方法及装置
本申请要求于2019年9月9日提交中国国家知识产权局、申请号为201910848792.0、发明名称为“一种业务数据包转发的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种业务数据包转发的方法及装置。
背景技术
目前，在第五代(5th generation，5G)网络中，接入网络(access network，AN)通过N2接口接入接入和移动性管理功能(access and mobility management function，AMF)，核心网基于服务化架构(service based architecture，SBA)实现。
5G网络通过用户面功能(user plane function，UPF)设备和接入设备转发终端设备和外部数据网络之间的业务数据包，接入设备和用户面功能设备之间基于分组数据单元(packet data unit，PDU)会话建立隧道，所有PDU会话相关的业务数据包在这一个隧道内传输。
5G网络采用大量新的技术，比如服务化框架，超文本传输协议(hyperText transfer protocol，HTTP)或者传输安全协议(transport layer security，TLS)等，这些技术在移动通信网络内没有应用过，目前还不够成熟。另外，运营商为5G网络需要投资建设新的基础设施，投资成本较大。因此，5G网络的应用还比较受限。
发明内容
本申请提供一种业务数据包转发的方法及装置，用以实现通过5G技术接入4G网络时，可以保证业务正常进行。
第一方面，本申请提供了一种业务数据包转发的方法，该方法可以包括：服务网关接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述服务网关根据所述第一IP地址和所述第一TEID确定服务质量QoS流标识以及接入设备分配的分组数据单元PDU会话的第二IP地址和第二TEID；所述服务网关向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID；或者，所述服务网关接收所述接入设备发送的第一上行数据包，所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识；所述服务网关根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；所述服务网关向所述数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
通过上述方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述 方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
在一个可能的设计中，所述服务网关接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；所述服务网关根据所述接入类型分配报文数据网络PDN连接的所述第三IP地址和所述第三TEID；所述服务网关向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。这样可以完成建立会话。
在一个可能的设计中，所述服务网关向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。这样后续可以进行承载建立。
在一个可能的设计中，所述服务网关接收移动管理设备发送的更新承载请求消息或者第一建立承载响应消息，所述更新承载请求消息或者第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；所述服务网关基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息；或者，所述服务网关基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息。这样后续可以进行承载更新或者完成承载建立。
第二方面，本申请提供了一种业务数据包转发的方法，该方法可以包括：接入设备接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述接入设备获取与所述第一IP地址和所述第一TEID对应的服务质量QoS流上下文中的服务质量参数；所述接入设备根据所述服务质量参数向终端设备发送第二下行数据包；或者，所述接入设备接收终端设备发送的第一上行数据包；所述接入设备获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID；所述接入设备向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
通过上述方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
在一个可能的设计中，所述接入设备接收移动管理设备发送的PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
在一个可能的设计中，所述接入设备向移动管理设备发送PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
第三方面，本申请提供了一种业务数据包转发的方法，该方法可以包括：移动管理设备接收第一消息，所述第一消息用于建立PDU会话或承载；所述移动管理设备向服务网关 发送第二消息，所述第二消息中包含承载标识；所述移动管理设备向接入设备发送第三消息，所述第三消息中包含QoS流标识；所述承载标识和所述QoS流标识用于标识终端设备的一个承载；所述第一消息为所述终端设备发送的PDU会话建立请求消息，所述第二消息为建立会话请求消息，所述第三消息为PDU会话资源建立请求消息；或者，所述第一消息为所述服务网关发送的建立承载请求消息，所述第二消息为建立承载响应消息，所述第三消息为PDU会话资源更新请求消息；或者所述第一消息为源测移动管理设备发送的转发切换请求消息，所述第二消息为建立会话请求消息，所述第三消息为切换请求消息；所述第一消息、所述第二消息和所述第三消息用于建立业务数据包转发的通道。
通过上述方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
在一个可能的设计中，当所述第二消息为建立会话请求消息时，所述第二消息中还包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
在一个可能的设计中，所述移动管理设备接收所述服务网关发送的建立会话响应消息，所述建立会话响应消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；所述移动管理设备向所述接入设备发送PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源建立请求消息或者切换请求消息中包含所述第一IP地址和所述第一TEID；所述移动管理设备接收接入设备发送的PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源建立响应消息或者切换请求响应消息中包含接入设备分配的第二IP地址和第二TEID；其中，所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID或者为QoS流的IP地址和TEID；所述移动管理设备向所述服务网关发送更新承载请求消息，所述更新承载请求消息中包含所述第二IP地址和所述第二TEID。
在一个可能的设计中，所述更新承载请求消息中还包含QoS流标识。
在一个可能的设计中，所述建立承载请求消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；所述移动管理设备向所述接入设备发送PDU会话资源更新请求消息；其中，当所述第一地址和所述第一TEID为承载的IP地址和TEID时，所述PDU会话资源更新请求消息中包含所述第一IP地址和所述第一TEID，或者，当所述第一地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新请求消息中不包含所述第一IP地址和所述第一TEID；所述移动管理设备接收所述接入设备发送的PDU会话资源更新响应消息；其中，所述PDU会话资源更新响应消息中包含所述接入设备分配的第二IP地址和第二TEID，所述第二IP地址和所述第二TEID为QoS流的IP地址和TEID；或者，当所述第一IP地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新响应消息中不包含接入设备分配的IP地址和TEID；所述移动管理设备向所述服务网关发送建立承载响应消息；所述建立承载响应消息中包含所述第二IP地址和所述第二TEID；或者，当所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID时， 所述建立承载响应消息中不包含接入设备分配的IP地址和TEID；或者，所述建立承载响应消息中包含所述第二IP地址和所述第二TEID，所述第二IP地址和所述第二TEID为所述移动管理设备从PDU会话资源建立响应消息或者切换请求响应消息中获得的。
在一个可能的设计中，所述建立承载响应消息中还包含所述QoS流标识。
第四方面，本申请还提供了一种服务网关，所述服务网关具有实现上述第一方面方法实例中服务网关的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述服务网关的结构中包括处理单元和通信单元，这些单元可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述服务网关的结构中包括通信接口和处理器，可选的还可以包括存储器，通信接口用于收发数据(信息或信号等)，以及与通信系统中的其他设备进行通信交互，处理器被配置为支持服务网关执行上述第一方面方法中服务网关相应的功能。存储器与处理器耦合，其保存服务网关必要的程序指令和数据。
第五方面，本申请还提供了一种接入设备，所述接入设备具有实现上述第二方面方法实例中接入设备的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述接入设备的结构中包括处理单元和通信单元，这些单元可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述接入设备的结构中包括通信接口和处理器，可选的还可以包括存储器，通信接口用于收发数据(信息或信号等)，以及与通信系统中的其他设备进行通信交互，处理器被配置为支持接入设备执行上述第二方面方法中接入设备相应的功能。存储器与处理器耦合，其保存接入设备必要的程序指令和数据。
第六方面，本申请还提供了一种移动管理设备，所述移动管理设备具有实现上述第三方面方法实例中移动管理设备的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述移动管理设备的结构中包括处理单元和通信单元，这些单元可以执行上述第三方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述移动管理设备的结构中包括通信接口和处理器，可选的还可以包括存储器，通信接口用于收发数据(信息或信号等)，以及与通信系统中的其他设备进行通信交互，处理器被配置为支持移动管理设备执行上述第三方面方法中移动管理设备相应的功能。存储器与处理器耦合，其保存移动管理设备必要的程序指令和数据。
第七方面，本申请还提供了一种通信系统，所述通信系统至少包括上述设计中提及的服务网关、接入设备和移动管理设备。进一步地，所述通信系统中的所述服务网关可以执行上述方法中服务网关执行的任一种方法，以及所述通信系统中的所述接入设备可以执行上述方法中接入设备执行的任一种方法以及，所述通信系统中的所述移动管理设备可以执行上述方法中移动管理设备执行的任一种方法。
第八方面，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述第一方面或第一方面的任意一种可能的设计、第二方面或第二方面的任意一种可能的设计中的任一种方法、第三方面或第三方面的任意一种可能的设计中的任一种方法。
第九方面，本申请提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意一种可能的设计、第二方面或第二方面的任意一种可能的设计中的任一种方法、第三方面或第三方面的任意一种可能的设计中的任一种方法。
第十方面，本申请提供了一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现上述第一方面或第一方面的任意一种可能的设计、第二方面或第二方面的任意一种可能的设计中的任一种方法、第三方面或第三方面的任意一种可能的设计中的任一种方法。
附图说明
图1为现有技术中的一种5G网络的架构示意图；
图2a为本申请提供的一种通信系统的架构示意图；
图2b为本申请提供的一种4G NSA架构图；
图3为本申请提供的一种业务数据包转发的方法的流程图；
图4为本申请提供的另一种业务数据包转发的方法的流程图；
图5为本申请提供的另一种业务数据包转发的方法的流程图；
图6为本申请提供的另一种业务数据包转发的方法的流程图；
图7为本申请提供的另一种业务数据包转发的方法的流程图；
图8为本申请提供的一种业务数据包转发的方法的示例的流程图；
图9为本申请提供的另一种业务数据包转发的方法的示例的流程图；
图10为本申请提供的另一种业务数据包转发的方法的示例的流程图；
图11为本申请提供的另一种业务数据包转发的方法的示例的流程图；
图12为本申请提供的另一种业务数据包转发的方法的示例的流程图；
图13为本申请提供的一种服务网关的结构示意图；
图14为本申请提供的一种接入设备的结构示意图；
图15为本申请提供的一种移动管理设备的结构示意图；
图16为本申请提供的一种服务网关的结构图；
图17为本申请提供的一种接入设备的结构图；
图18为本申请提供的一种移动管理设备的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种业务数据包转发的方法及装置，用以实现通过5G技术接入4G网络时，可以保证业务正常进行。其中，本申请所述方法和装置基于同一发明构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请中涉及的数据包(包括上行数据包和下行数据包)均指业务数据包。
在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的业务数据包转发的方法及装置进行详细说明。
图1示出了现有技术中的一种5G网络的架构，所述5G网络的架构中包括网络切片选择功能(network slice selection function，NSSF)设备、网络开放功能(network exposure function，NEF)设备、网络功能库功能((network function，NF)repository function，NRF)设备、策略控制功能(policy control function，PCF)设备、统一数据管理(unified data management，UDM)设备、应用功能(application function，AF)设备、鉴权服务器功能(authentication server function，AUSF)设备、接入和移动性管理功能(access and mobility management function，AMF)设备、会话管理功能(session management function，SMF)设备、服务通信代理SCP、终端设备(又称为用户设备(user equipment，UE))、无线接入网(radio access network，RAN)设备、用户面功能(user plane function，UPF)和数据网络(data network，DN)。
在现有的5G网络中终端设备通过N1接口，接入网络通过N2接口接入接入和移动性管理功能设备，核心网基于服务化架构实现。
由于5G网络采用大量新的技术，比如服务化框架，超文本传输协议(hyperText transfer protocol，HTTP)或者传输安全协议(transport layer security，TLS)等，这些技术在移动通信网络内没有应用过，目前还不够成熟。另外，运营商为5G网络需要投资建设新的基础设施，投资成本较大，这样导致5G网络应用受限。基于此，本申请基于5G网络和第四代(4th generation，4G)网络的兼容出发，提出可以使终端设备和接入网络通过N1或N2接口接入演进的分组核心网络(evolved packet core，EPC)，在重用EPC网络基础设施的情况下，支持5G原生接入。但是传统的EPC网络中通过接入设备、服务网关和数据网关转发终端设备和外部数据网络之间的业务数据包，这与5G的业务数据包转发的方法不同，因此，在本申请中可以实现通过5G技术接入4G网络时，可以保证业务正常进行。
基于上述描述，本申请提供了一种可能的通信系统的架构，所述通信系统的架构为本申请实施例提供的业务数据包转发的方法适用的一种可能的通信系统的架构，如图2a所示，所述通信系统的架构中可以包括终端设备、接入网络、移动管理设备、服务网关、数据网关和报文数据网络，其中：
终端设备，又可以称之为用户设备(user equipment，UE)、移动台(mobile station， MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音和/或数据连通性的设备。例如，所述终端设备可以包括具有无线连接功能的手持式设备、车载设备等。目前，所述终端设备可以是：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端，或智慧家庭(smart home)中的无线终端等。
终端设备通过本地的无线接入网络接入。
移动管理设备负责移动用户设备的位置管理、连接管理、安全认证、网关选择等功能。
服务网关是终端设备的本地接入网关，负责接入技术相关的连接管理和数据转发。
数据网关是终端设备访问外部数据网络的网关。
其中，EPC网络也可以为控制面和用户面分离的网络，即服务网关和数据网关的控制面和用户面分离，分为用户面的服务网关，控制面的服务网关，用户面的数据网关和控制面的数据网关。控制面的服务网关负责接入技术相关的连接管理和数据转发控制，用户面的服务网关负责数据转发。控制面的数据网关负责数据转发控制，用户面的数据网关负责数据转发。其中控制面的服务网关可以和控制面的数据网关合一部署，用户面的服务网关也可以和用户面的数据网关合一部署。
实际中，所述终端设备可以是5G终端；对于演进的通用陆地无线接入网(evolved universal terrestrial radio access network，evolved E-UTRAN)、新无线(new radio，NR)接入网中，接入设备可以为下一代演进型基站(next generation evolved NodeB，ng-eNB)或者5G移动通信系统中的下一代基站(next generation NodeB，gNB)，核心网为EPC网络的网元，移动管理设备可以是移动性管理实体(mobility management entity，MME)，服务网关可以是服务网关(serving gateway，S-GW)，数据网关可以是报文数据网络网关(packet data network gateway，PDN-GW)。针对控制面和用户面分离的网络，服务网关可以是用户面的服务网关(serving gateway user plane，SGW-U)和控制面的服务网关(serving gateway control plane，SGW-C)，数据网关可以是用户面的数据网关(packet data network gateway user plane，PGW-U)和控制面的数据网关(packet data network gateway control plane，PGW-C)。移动管理设备、服务网关可以在现有EPC网络的基础上，进行一定的增强，以支持5G终端设备的原生接入。
需要说明的是，当移动管理设备和服务网关进行了增强时，移动管理设备可以称为增强移动管理设备，服务网关可以称为增强服务网关。
如图2b所示的4G非独立组网架构(non standalone architecture，NSA)中终端设备为4G终端设备，通过4G NAS接入移动管理设备，主接入网络通过4G S1接口接入移动管理设备。终端设备的用户面数据包可以同时通过主接入网络和第二接入网络转发，其中主接入网络是对于E-UTRAN，对应的接入设备为演进型基站(evolved NodeB，eNodeB)，第二接入网络是对于evolved E-UTRAN或者NR接入网，对应的接入设备为ng-eNB或者gNB。通过第二接入网络提供的高带宽使得4G终端设备可以享受媲美5G网络的业务体验。但是 NSA架构需要部署主接入网络和第二接入网络，适用于局部热点部署，全网部署代价高。因此，采用本申请提供的图2a所示的网络可以避免上述问题，灵活实现通过5G技术接入4G网络。
需要说明的是，图2a、图2b所示的通信系统的架构中不限于仅包含图中所示的设备，还可以包含其它未在图中表示的设备，具体本申请在此处不再一一列举。
本申请实施例提供的一种业务数据包转发的方法，适用于如图2a所示的通信系统。参阅图3所示，该方法的具体流程可以包括：
步骤301、服务网关接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议(internet protocol，IP)地址和第一隧道端点标识(tunnel endpoint identifier，TEID)。
在此实施例中，所述服务网关为对现有的服务网关进行了增强的增强服务网关。
步骤302、所述服务网关根据所述第一IP地址和所述第一TEID确定服务质量(quality of service，QoS)流标识以及接入设备分配的分组数据单元(packet data unit，PDU)会话的第二IP地址和第二TEID。
具体的，所述服务网关获取所述第一IP地址和所述第一TEID对应的承载上下文，从而根据所述承载上下文获得所述QoS流标识以及所述第二IP地址和所述第二TEID。
步骤303、所述服务网关向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID。
需要说明的是，所述第一下行数据包和所述第二下行数据包是针对同一个业务的数据包，所述第二数据包是所述服务网关将所述第一下行数据包中的所述第一IP地址和所述第一TEID去掉后，封装上所述QoS流标识以及所述第二IP地址和所述第二TEID后得到的数据包。
进一步地，所述接入设备在接收到所述第二下行数据包后，根据所述第二IP地址和所述第二TEID确定所述第二IP地址和所述第二TEID对应的PDU会话上下文，根据所述QoS流标识确定对应的QoS流，然后所述接入设备根据所述QoS流关联的服务质量QoS参数发送第三下行数据包给终端设备。
需要说明的是，所述接入设备向所述终端发送的所述第三下行数据包，是将所述第二下行数据包中的第二IP地址和第二TEID去掉后得到的数据包。
在一种可选的实施方式中，在PDU会话建立的场景中，所述服务网关在接收数据网关发送的第一下行数据包之前，所述服务网关接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；所述服务网关根据所述接入类型分配PDN连接的第三IP地址和第三TEID；所述服务网关向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。
在此实施例中，所述移动管理设备为对现有的移动管理设备进行了增强的增强移动管理设备。
示例性的，所述接入类型可以为所述终端设备接入的接入设备的类型，或者为无线接 入网络的类型，或者为所述终端设备的类型；其中，所述接入设备的类型为演进型基站ng-eNB类型或者下一代基站gNB类型；所述无线接入网络的类型为新无线NR类型或者演进的通用陆地无线接入网Evolved E-UTRAN类型；所述终端设备的类型为5G类型。
在一种具体的实施方式中，所述服务网关接收的所述建立会话请求消息中还包含所述移动管理设备为PDN连接的缺省承载分配的关联承载标识。所述关联承载标识既是PDN连接标识，又是当前建立的承载的承载标识，当前建立的承载为缺省承载。需要说明的是，所述移动管理设备可以根据从终端设备获取的PDU会话标识分配PDN连接标识，如所述PDN连接标识的值和PDU会话标识的值相同，又如通过一定的算法由PDU会话标识计算出PDN连接标识。所述移动管理设备也可以按照现有的方法分配PDN连接标识，本地保存PDU会话标识和PDN连接标识的对应关系，本申请对此不作限定。
在一种示例性的实施方式中，所述服务网关在接收到所述建立会话请求消息后，向所述数据网关发送建立会话请求消息2(这里写成建立会话请求消息2是为了与服务网关接收到的建立会话请求消息区分，并没有其他含义)；所述服务网关接收所述数据网关发送的建立会话响应消息2(这里写成建立会话响应消息2是为了与服务网关发送的建立会话请求消息区分，并没有其他含义)。所述建立会话请求消息2中可以包含所述关联承载标识、所述接入类型以及所述第一IP地址和所述第一TEID。所述建立会话响应消息2中可以包含所述关联承载标识以及所述数据网关分配的承载的第四IP地址和第四TEID。
一种可选的实施方式中，在PDU会话建立完成之后，所述服务网关接收所述移动管理设备发送的更新承载请求消息，所述更新承载请求消息包含所述第二IP地址和所述第二TEID以及所述QoS流标识；所述服务网关基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息。
在另一种可选的实施方式中，在承载建立流程触发的PDU会话更新的场景中，所述服务网关在接收数据网关发送的第一下行数据包之前，所述服务网关向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。
示例性的，所述服务网关在向所述移动管理设备发送建立承载请求消息之前，接收所述数据网关发送的建立承载请求消息2(这里写成建立承载请求消息2是为了与服务网关发送的建立承载请求消息区分，并没有其他含义)，所述建立承载请求消息2中包含所述数据网关分配的承载的第四IP地址和第四TEID。
在一种具体的实施方式中，在PDU会话更新完成后，所述服务网关接收所述移动管理设备发送的第一建立承载响应消息，所述第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；所述服务网关基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息，所述第二建立承载响应消息中包含承载标识以及所述第一IP和所述第一TEID。其中，所述第一建立承载响应消息用于响应上述建立承载请求消息，所述第二建立承载响应消息用于响应上述建立承载请求消息2。
采用本申请实施例提供的业务数据包转发的方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
本申请实施例提供的另一种业务数据包转发的方法，适用于如图2a所示的通信系统。参阅图4所示，该方法的具体流程可以包括：
步骤401、服务网关接收接入设备发送的第一上行数据包，所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识。
在此实施例中，所述服务网关为对现有的服务网关进行了增强的增强服务网关。
具体的，所述接入设备接收到终端设备发送的第三上行数据包后，向所述服务网关发送所述第一上行数据包。其中，所述第三上行数据包在对应的空口承载发送，所述接入设备根据所述空口承载确定所述第三上行数据包对应的QoS流，所述接入设备获得QoS流上下文中的QoS流标识，以及QoS流对应的PDU会话上下文中的第三IP地址和第三TEID；所述第三IP地址和第三TEID是所述服务网关分配的。
步骤402、所述服务网关根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID。
具体的，所述服务网关确定所述第三IP地址和所述第三TEID对应的PDN连接上下文，然后根据所述QoS流标识确定所述PDN连接上下文中的承载上下文，根据所述承载上下文获得所述第四IP地址和所述第四TEID。
步骤403、所述服务网关向数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
在一种可选的实施方式中，在PDU会话建立的场景中，所述服务网关在接收到所述接入设备发送的所述第一上行数据包之前，所述服务网关执行的操作，与图3所示的实施例中所述服务网关在接收到数据网关发送的第一下行数据包之前执行的操作类似，具体可以相互参见，此处不再详细赘述。
在另一种可选的实施方式中，在承载建立流程触发的PDU会话更新场景中，所述服务网关在接收到所述接入设备发送的所述第一上行数据包之前，所述服务网关执行的操作，与图3所示的实施例中所述服务网关在接收到数据网关发送的第一下行数据包之前执行的操作类似，具体可以相互参见，此处不再详细赘述。
采用本申请实施例提供的业务数据包转发的方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
需要说明的是，在上述图3和图4所示的实施例中，均是通过增强服务网关支持PDN连接的隧道，使得终端设备的业务数据包可以正常转发，避免影响用户的业务体验。其中，图3所示的实施例实现下行业务数据包的转发，图4所示的实施例实现的是上行业务数据包的转发，两个实施例除了转发流程不相同，其他流程基本相同。
下面示出的图5和图6两个实施例，与图3和图4所示的实施例不同的是，图5和图6所示的实施例中是通过增强接入设备支持QoS流的隧道，使得终端设备的业务数据包可以正常转发，避免影响用户的业务体验。其中，图5所示的实施例实现下行业务数据包的转 发，图6所示的实施例实现的是上行业务数据包的转发，两个实施例除了转发流程不相同，其他流程基本相同。
本申请实施例提供的另一种业务数据包转发的方法，适用于如图2a所示的通信系统。参阅图5所示，该方法的具体流程可以包括：
步骤501、接入设备接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一IP地址和第一TEID。
在本实施例中，所述接入设备为对现有的接入设备进行了增强的增强接入设备。
具体的，所述服务网关接收数据网关发送的所述第三下行数据包，然后向所述接入设备发送所述第一下行数据包。其中，所述第三下行数据包中包含所述服务网关为此承载的下行数据包转发分配的IP地址和TEID，所述服务网关根据所述服务网关为此承载的下行数据包转发分配的IP地址和TEID，确定所述接入设备分配的QoS流的所述第一IP地址和所述第一TEID。
步骤502、所述接入设备获取与所述第一IP地址和所述第一TEID对应的QoS流上下文中的服务质量参数。
具体的，所述接入设备确定所述第一IP地址和所述第一TEID对应的所述QoS流上下文，从而获得所述服务质量参数。
步骤503、所述接入设备根据所述服务质量参数向终端设备发送第二下行数据包。
在一种可选的实施方式中，在PDU会话建立的场景中，所述接入设备在接收服务网关发送的第一下行数据包之前，所述接入设备接收移动管理设备发送的PDU会话资源建立请求消息，所述PDU会话资源建立请求消息中包含QoS流标识以及服务网关分配的QoS流的第二IP地址和第二TEID；然后，所述PDU会话资源建立请求消息中还包含发送给终端设备的PDU会话建立接受消息，所述接入设备基于所述PDU会话资源建立请求消息向所述终端设备转发该PDU会话建立接受消息。
示例性的，所述PDU会话资源建立请求消息还可以包括PDU会话标识。
可选的，所述PDU会话建立接受消息中可以包含所述PDU会话标识和所述QoS流标识。
之后，所述接入设备向所述移动管理设备发送PDU会话资源建立响应消息，所述PDU会话资源建立响应消息中包括所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
示例性的，所述PDU会话资源建立响应消息中还可以包含所述PDU会话标识和所述QoS流标识。
在另一种可选的实施方式中，在承载建立流程触发的PDU会话更新场景中，所述接入设备在接收服务网关发送的第一下行数据包之前，所述接入设备接收所述移动管理设备发送的PDU会话资源更新请求消息，所述PDU会话资源更新请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID；所述PDU会话资源更新请求消息中还包含发送给终端设备的PDU会话更新请求消息，所述接入设备基于所述PDU会话资源更新请求消息向所述终端设备转发该PDU会话更新请求消息。其中，所述PDU会话更新请求消息中包含所述QoS流标识。
之后，所述接入设备向所述移动管理设备发送PDU会话资源更新响应消息，所述PDU会话资源更新响应消息中包括所述接入设备为下行数据包分配的QoS流的第一IP地址和第一TEID。其中，所述PDU会话资源更新响应消息中还包含所述QoS流标识。
示例性的，在所述接入设备向所述移动管理设备发送PDU会话资源更新响应消息之前，所述接入设备接收所述终端设备发送的PDU会话更新完成消息，并向所述移动管理设备转发所述PDU会话更新完成消息，其中，所述PDU会话更新完成消息中包含所述QoS流标识，用于指示所述QoS流建立完成。
在又一种可选的实施方式中，在接入设备、移动管理设备和服务网关发生过切换的切换流程中，所述接入设备为新侧接入设备，也即切换后的接入设备。在此场景中，所述接入设备在接收服务网关发送的第一下行数据包之前，所述接入设备接收所述移动管理设备(此处的移动管理设备为新侧的移动管理设备，也即切换后的移动管理设备)发送的切换请求消息，所述切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
之后，所述接入设备向所述移动管理设备发送切换请求响应消息，所述切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
采用本申请实施例提供的业务数据包转发的方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
本申请实施例提供的另一种业务数据包转发的方法，适用于如图2a所示的通信系统。参阅图6所示，该方法的具体流程可以包括：
步骤601、接入设备接收终端设备发送的第一上行数据包。
在本实施例中，所述接入设备为对现有的接入设备进行了增强的增强接入设备。
步骤602、所述接入设备获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID。
步骤603、所述接入设备向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
具体的，所述服务网关在接收到所述第二上行数据包后，向数据网关发送第三上行数据包。其中，所述服务网关根据所述第二IP地址和所述第二TEID确定数据网关分配的承载的IP地址和TEID；所述第三上行数据包中包括所述数据网关分配的承载的IP地址和TEID。
在一种可选的实施方式中，在PDU会话建立的场景中，所述接入设备接收到终端设备发送的第一上行数据包之前，所述接入设备执行的操作，与图5所示的实施例中所述接入设备接收到服务网关发送的第一下行数据包之前执行的操作类似，具体可以相互参见，此处不再详细赘述。
在另一种可选的实施方式中，在承载建立流程触发的PDU会话更新的场景中，所述接入设备接收到终端设备发送的第一上行数据包之前，所述接入设备执行的操作，与图5所示的实施例中所述接入设备接收到服务网关发送的第一下行数据包之前执行的操作类似， 具体可以相互参见，此处不再详细赘述。
在又一种可选的实施方式中，在接入设备、移动管理设备和服务网关发生过切换的切换流程中，所述接入设备为新侧接入设备，也即切换后的接入设备。在此场景中，所述接入设备接收到终端设备发送的第一上行数据包之前，所述接入设备执行的操作，与图5所示的实施例中所述接入设备接收到服务网关发送的第一下行数据包之前执行的操作类似，具体可以相互参见，此处不再详细赘述。
采用本申请实施例提供的业务数据包转发的方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
下面图7示出的实施例，是本申请实施例提供了的另一种业务数据包转发的方法，适用于如图2a所示的通信系统。参阅图7所示，该方法的具体流程可以包括：
步骤701、移动管理设备接收第一消息，所述第一消息用于建立PDU会话或承载。
在此实施例中，所述移动管理设备为对现有的移动管理设备进行了增强的增强移动管理设备。
步骤702、所述移动管理设备向服务网关发送第二消息，所述第二消息中包含承载标识。
步骤703、所述移动管理设备向接入设备发送第三消息，所述第三消息中包含QoS流标识。
其中，所述承载标识和所述QoS流标识用于标识终端设备的一个承载。
其中，在PDU会话建立的场景中，所述第一消息为所述终端设备发送的PDU会话建立请求消息，所述第二消息为建立会话请求消息，所述第三消息为PDU会话资源建立请求消息；在承载建立流程触发的PDU会话更新的场景中，所述第一消息为所述服务网关发送的建立承载请求消息，所述第二消息为建立承载响应消息，所述第三消息为PDU会话资源更新请求消息；在接入设备、移动管理设备和服务网关发生过切换的切换流程中，所述移动管理设备为新侧移动管理设备，所述第一消息为源测移动管理设备发送的转发切换请求消息，所述第二消息为建立会话请求消息，所述第三消息为切换请求消息。
具体的，所述第一消息、所述第二消息和所述第三消息用于建立业务数据包转发的通道。
在一种可选的实施方式中，当在PDU会话建立的场景中，所述第二消息为建立会话请求消息时，所述第二消息中还包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
在一种具体的实施方式中，所述移动管理设备接收所述服务网关发送的建立会话响应消息，所述建立会话响应消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
所述移动管理设备向所述接入设备发送PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源建立请求消息或者切换请求消息中包含所述第一IP地址和所述第一TEID；
所述移动管理设备接收接入设备发送的PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源建立响应消息或者切换请求响应消息中包含接入设备分配的第二IP地址和第二TEID；其中，所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID或者为QoS流的IP地址和TEID；
所述移动管理设备向所述服务网关发送更新承载请求消息，所述更新承载请求消息中包含所述第二IP地址和所述第二TEID。
一种可选的实施方式中，所述更新承载请求消息中还包含QoS流标识。
在另一种具体的实施方式中，所述建立承载请求消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
所述移动管理设备向所述接入设备发送PDU会话资源更新请求消息；其中，当所述第一地址和所述第一TEID为承载的IP地址和TEID时，所述PDU会话资源更新请求消息中包含所述第一IP地址和所述第一TEID，或者，当所述第一地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新请求消息中不包含所述第一IP地址和所述第一TEID；
所述移动管理设备接收所述接入设备发送的PDU会话资源更新响应消息；其中，所述PDU会话资源更新响应消息中包含接入设备分配的第二IP地址和第二TEID，所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID或者为QoS流的IP地址和TEID；或者，当所述第一地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新响应消息中不包含接入设备分配的IP地址和TEID；
所述移动管理设备向所述服务网关发送建立承载响应消息；其中，所述建立承载响应消息中包含所述第二IP地址和所述第二TEID；或者，当所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID时，所述建立承载响应消息中不包含接入设备分配的IP地址和TEID；或者，所述建立承载响应消息中包含所述第二IP地址和所述第二TEID，所述第二IP地址和所述第二TEID为所述移动管理设备从PDU会话资源建立响应消息或者切换请求响应消息中获得的。
一种可选的实施方式中，所述建立承载响应消息中还包含QoS流标识。
采用本申请实施例提供的业务数据包转发的方法，可以使得5G终端设备和接入设备接入演进的分组核心网络时，可以正常转发终端设备的业务数据包，保证业务正常进行，避免影响用户的业务体验。也即上述方法实现通过5G技术接入4G网络时，可以保证业务正常进行。
基于以上实施例，本申请实施例提供了一种业务数据包转发的方法的示例，该示例是PDU会话建立的场景中，通过增强服务网关支持PDN连接的隧道，使得终端设备的业务数据包可以正常转发。在该示例中，服务网关为增强服务网关，移动管理设备为增强移动管理设备，在该示例中以增强服务网关和增强移动管理设备示出。参阅图8所示，该示例的具体流程可以包括：
步骤801、终端设备向增强移动管理设备发送PDU会话建立请求消息，所述PDU会话 建立请求消息中包含终端设备为此PDU会话分配的PDU会话标识。
其中，所述终端设备需要进行业务时，触发PDU会话建立流程。
示例性的，所述终端设备向所述增强移动管理设备发送PDU会话建立请求消息时，所述终端设备通过接入设备向增强移动管理设备发送PDU会话建立请求消息。具体的，所述终端设备先向接入设备发送所述PDU会话建立请求消息，然后所述接入设备向所述增强移动管理设备转发PDU会话建立请求消息。
步骤802、所述增强移动管理设备选择增强服务网关和数据网关。
步骤803、所述增强移动管理设备向所述增强服务网关发送建立会话请求消息。
所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
具体的，所述接入类型的相关描述可以参见图3所示的实施例中涉及的接入类型的描述，此处不再详细描述。
同样的，所述建立会话请求消息的相关描述可以参见图3所示的实施例中涉及的建立会话请求消息的描述，此处不再详细描述。
步骤804、所述增强服务网关向所述数据网关发送建立会话请求消息2，用于PDN连接的建立。
所述建立会话请求消息2中可以包含所述关联承载标识、所述接入类型以及增强服务网关为此PDN连接的缺省承载的下行数据包转发分配的IP地址和TEID，也就是图3所示的实施例中涉及的第一IP地址和第一TEID。
步骤805、所述数据网关与策略和计费规则功能实体(policy and charging rules function，PCRF)之间建立所述PDN连接的连接接入网络(internet protocol-connectivity access network，IP-CAN)会话，用以获取对应的计费和服务质量等策略。
步骤806、所述数据网关向所述增强服务网关发送建立会话响应消息2。
所述建立会话响应消息2中可以包含所述关联承载标识、所述数据网关为此PDN连接的缺省承载的上行数据包转发分配的IP地址和TEID，也就是图3所示的实施例中涉及的第四IP地址和第四TEID。
步骤807、所述增强服务网关向所述增强移动管理设备发送建立会话响应消息。
所述增强服务网关根据步骤803中收到的接入类型，获知终端设备从Evolved E-UTRAN或者NR接入，则增所述增强服务网关为此PDN连接的上行数据包转发分配IP地址和TEID，所述IP地址和TEID为PDN连接的IP地址和TEID，所述增强服务网关将此IP地址和TEID包含在所述建立会话响应消息中，也就是图3所示的实施例中涉及的第三IP地址和第三TEID。
可选的，所述建立会话响应消息中还包含关联承载标识。
步骤808、所述增强移动管理设备向所述接入设备发送PDU会话资源建立请求消息。
其中，所述PDU会话资源建立请求消息中包含PDU会话标识，QoS流标识，所述增强服务网关分配的IP地址和TEID。所述PDU会话资源建立请求消息中还包含发送给所述终端设备的PDU会话建立接受消息。
具体的，所述增强移动管理设备分配QoS流标识，所述QoS流标识可以和承载标识相 同，或者通过一定的算法由承载标识计算出QoS流标识，或者QoS流标识的分配和承载标识没有关系，但是所述增强移动管理设备本地保存QoS流标识和承载标识的对应关系。所述QoS流标识或者承载标识用于标识一个承载。
步骤809、所述接入设备向所述终端设备转发PDU会话建立接受消息。所述PDU会话建立接受消息中包含PDU会话标识和QoS流标识。
步骤810、所述接入设备向所述增强移动管理设备发送PDU会话资源建立响应消息。
其中，所述PDU会话资源建立响应消息中包含PDU会话标识，QoS流标识和所述接入设备为此PDU会话的下行数据包转发分配的IP地址和TEID，也即图3所示的实施例中的第二IP地址和第二TEID。
步骤811、所述增强移动管理网元向所述增强服务网关发送更新承载请求消息。
其中，所述更新承载请求消息中包含增强移动管理设备在步骤810收到的接入设备分配的IP地址和TEID，所述更新承载请求消息还包含QoS流标识，承载标识，本流程中所述承载标识即为关联承载标识。
具体的，所述增强移动管理设备根据QoS流标识确定所述承载标识(QoS流标识在终端设备内唯一标识一个承载)，或者进一步的，所述增强移动管理设备根据PDU会话标识确定PDN连接标识，根据QoS流标识确定PDN连接内的承载标识(QoS流标识在PDN连接内唯一标识一个承载)。
步骤812、所述增强服务网关向所述增强移动管理设备发送更新承载响应消息，以指示承载更新成功。
步骤813、所述增强服务网关接收所述数据网关发送的第一下行数据包。所述第一下行数据包中包含第一IP地址和第一TEID。
步骤814、所述增强服务网关根据所述第一IP地址和所述第一TEID确定QoS流标识以及所述接入设备分配的PDU会话的第二IP地址和第二TEID。
具体的，所述增强服务网关获取所述第一IP地址和所述第一TEID对应的承载上下文，从而获取根据所述承载上下文获得所述QoS流标识以及所述第二IP地址和所述第二TEID。
步骤815、所述增强服务网关向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID。
步骤816、所述接入设备向所述终端设备发送第三下行数据包。
具体的，所述接入设备根据所述第二IP地址和所述第二TEID确定所述第二IP地址和所述第二TEID对应的PDU会话上下文，根据所述QoS流标识确定对应的QoS流，然后所述接入设备根据所述QoS流关联的服务质量QoS参数转发所述第三下行数据包给终端设备。
步骤817、所述接入设备接收所述终端设备发送的第三上行数据包，所述第三上行数据包在对应的空口承载发送，所述接入设备根据所述空口承载确定第三上行数据包对应的QoS流，所述接入设备获得QoS流上下文中的QoS流标识，以及QoS流对应的PDU会话上下文中的第三IP地址和第三TEID。
步骤818、所述接入设备向所述增强服务网关发送所述第一上行数据包。
所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识。
所述第三IP地址和第三TEID是所述增强服务网关分配的。
步骤819、所述增强服务网关根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID。
具体的，所述增强服务网关确定所述第三IP地址和所述第三TEID对应的PDN连接上下文，然后根据所述QoS流标识确定所述PDN连接上下文中的承载上下文，根据所述承载上下文获得所述第四IP地址和所述第四TEID。
步骤820、所述增强服务网关向数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
基于以上实施例，本申请实施例提供了另一种业务数据包转发的方法的示例，该示例是在承载建立流程触发的PDU会话更新的场景中，通过增强服务网关支持PDN连接的隧道，使得终端设备的业务数据包可以正常转发。在该示例中，服务网关为增强服务网关，移动管理设备为增强移动管理设备，在该示例中以增强服务网关和增强移动管理设备示出。参阅图9所示，该示例的具体流程可以包括：
步骤901、策略和计费规则功能实体触发IP-CAN会话更新，向数据网关发送IP-CAN会话更新请求，以发送更新的计费和服务质量等规则给数据网关。
步骤902、所述数据网关决策触发承载建立流程，向增强服务网关发送建立承载请求消息2，所述建立承载请求消息2中包含数据网关分配的用于转发此承载对应的上行数据包的IP地址和TEID，也就是图3所示的实施例中涉及的第四IP地址和第四TEID。
步骤903、所述增强服务网关向增强移动管理设备发送建立承载请求消息。
其中，所述建立承载请求消息中包含服务网关根据所述接入类型分配的PDN连接的第三IP地址和第三TEID，即所述第三IP地址和第三TEID为PDN连接的IP地址和TEID，也即图8所示的示例中步骤807中分配的PDU会话的IP地址和TEID。
步骤904、所述增强移动管理设备向接入设备发送PDU会话资源更新请求消息。
其中，所述增强移动管理设备为承载对应的QoS流分配QoS流标识(分配流标识)，所述PDU会话资源更新请求消息中包含QoS流标识，QoS流标识的分配方法参见上述实施例中涉及的方法，此处不再详细描述。所述PDU会话资源更新请求消息中还包含发送给终端设备的PDU会话更新请求消息。
步骤905、所述接入设备向终端设备转发PDU会话更新请求消息，所述PDU会话更新请求消息中包含所述QoS流标识。
步骤906、所述终端设备向所述接入设备发送PDU会话更新完成消息，所述送PDU会话更新完成消息中包含QoS流标识，用于指示所述QoS流建立完成。
步骤907、所述接入设备向所述增强移动管理设备转发所述PDU会话更新完成消息。
步骤908、所述接入设备向所述增强移动管理设备发送PDU会话资源更新响应消息，所述PDU会话资源更新响应消息中包含QoS流标识，用于指示所述QoS流建立完成。
步骤909、所述增强移动管理设备向所述增强服务网关发送第一建立承载响应消息。
其中，所述增强移动管理设备为此承载分配承载标识，所述QoS流标识可以和承载标识相同，或者通过一定的算法由QoS流标识计算出承载标识，或者承载标识的分配和QoS流标识没有关系，但是增强移动管理设备本地保存QoS流标识和承载标识的对应关系。QoS 流标识或者承载标识用于标识一个承载，本流程中为专有承载。所述第一建立承载响应消息中包含所述承载标识。
所述第一建立承载响应消息中还包含所述接入设备分配的IP地址和TEID(也即接入设备分配的PDU会话的第二IP地址和第二TEID，也即图8所示的示例中步骤810中涉及的IP地址和TEID)，或者所述第一建立承载响应消息中不包含接入设备分配的IP地址和TEID，所述增强服务网关收到消息后，针对Evolved E-UTRAN或者NR接入的终端设备，所有此PDN连接对应的下行业务数据包都发往在图8所示的实施例中步骤811收到的IP地址和TEID。
步骤910、所述增强服务网关向所述数据网关发送第二建立承载响应消息，所述第二建立承载响应消息中包括承载标识和增强服务网关分配的用于转发此承载对应的下行数据包的IP地址和TEID(也即图3所示的实施例中的第一IP地址和第一TEID)。
步骤911、所述数据网关向所述策略和计费规则功能实体发送IP-CAN会话更新响应消息。
步骤912、所述增强服务网关接收所述数据网关发送的第一下行数据包。所述第一下行数据包中包含第一IP地址和第一TEID。
步骤913、所述增强服务网关根据所述第一IP地址和所述第一TEID确定QoS流标识以及所述接入设备分配的PDU会话的第二IP地址和第二TEID。
具体的，所述增强服务网关获取所述第一IP地址和所述第一TEID对应的承载上下文，从而根据所述承载上下文获得所述QoS流标识以及所述第二IP地址和所述第二TEID。
步骤914、所述增强服务网关向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID。
步骤915、所述接入设备向所述终端设备发送所述第三下行数据包。
具体的，所述接入设备根据所述第二IP地址和所述第二TEID确定所述第二IP地址和所述第二TEID对应的PDU会话上下文，根据所述QoS流标识确定对应的QoS流，然后所述接入设备根据所述QoS流关联的服务质量QoS参数发送所述第三下行数据包给终端设备。
步骤916、所述接入设备接收所述终端设备发送的第三上行数据包，所述第三上行数据包在对应的空口承载发送，所述接入设备根据所述空口承载确定第三上行数据包对应的QoS流，所述接入设备获得QoS流上下文中的QoS流标识，以及QoS流对应的PDU会话上下文中的第三IP地址和第三TEID。
步骤917、所述接入设备向所述增强服务网关发送所述第一上行数据包。
所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识。
所述第三IP地址和第三TEID是所述增强服务网关分配的。
步骤918、所述增强服务网关根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID。
具体的，所述增强服务网关确定所述第三IP地址和所述第三TEID对应的PDN连接上下文，然后根据所述QoS流标识确定所述PDN连接上下文中的承载上下文，根据所述承载上下文获得所述第四IP地址和所述第四TEID。
步骤919、所述增强服务网关向数据网关发送第二上行数据包，所述第二上行数据包中 包含所述第四IP地址和所述第四TEID。
需要说明的是，在图8所示的示例中或者图9所示的示例中，下行数据包转发的过程和上行数据包转发的过程的发生顺序并不限定，图中仅仅是一种顺序示例，应理解，可以上行数据包转发在先，下行数据包转发在后，本申请对此不作限定。
基于以上实施例，本申请实施例还提供了另一种业务数据包转发的方法的示例，该示例是PDU会话建立的场景中，通过增强接入设备支持QoS流的隧道，使得终端设备的业务数据包可以正常转发。在该示例中，接入设备为增强接入设备，移动管理设备为增强移动管理设备，在该示例中以增强接入设备和增强移动管理设备示出。参阅图10所示，该示例的具体流程可以包括：
步骤1001、终端设备向增强移动管理设备发送PDU会话建立请求消息，所述PDU会话建立请求消息中包含终端设备为此PDU会话分配的PDU会话标识。
其中，所述终端设备需要进行业务时，触发PDU会话建立流程。
示例性的，所述终端设备向所述增强移动管理设备发送PDU会话建立请求消息时，所述终端设备通过增强接入设备向增强移动管理设备发送PDU会话建立请求消息。具体的，所述终端设备先向增强接入设备发送所述PDU会话建立请求消息，然后所述增强接入设备向所述增强移动管理设备转发PDU会话建立请求消息。
步骤1002、所述增强移动管理设备选择服务网关和数据网关。
步骤1003、所述增强移动管理设备向所述服务网关发送建立会话请求消息。
所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
具体的，所述接入类型的相关描述可以参见图3所示的实施例中涉及的接入类型的描述，此处不再详细描述。
同样的，所述建立会话请求消息的相关描述可以参见图3所示的实施例中涉及的建立会话请求消息的描述，此处不再详细描述。
步骤1004、所述服务网关向所述数据网关发送建立会话请求消息2，用于PDN连接的建立。
所述建立会话请求消息2中可以包含所述关联承载标识、所述接入类型以及所述服务网关为此PDN连接的缺省承载的下行数据包转发分配的IP地址和TEID。
步骤1005、所述数据网关与策略和计费规则功能实体之间建立所述PDN连接的IP-CAN会话，用以获取对应的计费和服务质量等策略。
步骤1006、所述数据网关向所述服务网关发送建立会话响应消息2。
所述建立会话响应消息2中可以包含所述关联承载标识、所述数据网关为此PDN连接的缺省承载的上行数据包转发分配的IP地址和TEID。
步骤1007、所述服务网关向所述增强移动管理设备发送建立会话响应消息。
所述建立会话响应消息中包含服务网关为此PDN连接的缺省承载的上行数据包转发分配的IP地址和TEID(也即图6所示的实施例中涉及的第二IP地址和第二TEID)，所述第二IP地址和第二TEID为承载或者QoS流的。所述建立会话响应消息中还包含关联承载标 识。
步骤1008、所述增强移动管理设备向所述增强接入设备发送PDU会话资源建立请求消息。
其中，所述PDU会话资源建立请求消息中包含PDU会话标识，QoS流标识，QoS流的IP地址和TEID(也即步骤1007中所述服务网关分配的IP地址和TEID)。所述PDU会话资源建立请求消息中还包含发送给所述终端设备的PDU会话建立接受消息。
具体的，所述增强移动管理设备分配QoS流标识，所述QoS流标识可以和承载标识相同，或者通过一定的算法由承载标识计算出QoS流标识，或者QoS流标识的分配和承载标识没有关系，但是所述增强移动管理设备本地保存QoS流标识和承载标识的对应关系。所述QoS流标识或者承载标识用于标识一个承载。
步骤1009、所述增强接入设备向所述终端设备发送PDU会话建立接受消息。所述PDU会话建立接受消息中包含PDU会话标识和QoS流标识。
步骤1010、所述增强接入设备向所述增强移动管理设备发送PDU会话资源建立响应消息。
其中，所述PDU会话资源建立响应消息中包含PDU会话标识，QoS流标识和所述增强接入设备为此PDU会话的QoS流的下行数据包转发分配的IP地址和TEID，也即图4所示的实施例中的第一IP地址和第一TEID。
步骤1011、所述增强移动管理设备向所述服务网关发送更新承载请求消息。
其中，所述更新承载请求消息中包含承载的IP地址和TEID，所述增强移动管理网元在步骤1010收到的IP地址和TEID，承载标识，本流程中所述承载标识即为关联承载标识。
具体的，所述增强移动管理设备根据QoS流标识确定所述承载标识(QoS流标识在终端设备内唯一标识一个承载)，或者进一步的，所述增强移动管理设备根据PDU会话标识确定PDN连接标识，根据QoS流标识确定PDN连接内的承载标识(QoS流标识在PDN连接内唯一标识一个承载)。
步骤1012、所述服务网关向所述增强移动管理设备发送更新承载响应消息，以指示承载更新成功。
步骤1013：所述服务网关接收所述数据网关发送的第三下行数据包，所述第三下行数据包中包含所述服务网关为此PDN连接的缺省承载的下行数据包转发分配的IP地址和TEID。
所述服务网关根据所述服务网关为此PDN连接的缺省承载的下行数据包转发分配的IP地址和TEID，确定增强接入设备分配的QoS流的第一IP地址和第一TEID。
步骤1014、所述服务网关向所述增强接入设备发送第一下行数据包，所述第一下行数据包中包含所述第一IP地址和所述第一TEID。
步骤1015、所述增强接入设备获取与所述第一IP地址和所述第一TEID对应的QoS流上下文中的服务质量参数。
具体的，所述增强接入设备确定所述第一IP地址和所述第一TEID对应的所述QoS流上下文，从而获得所述服务质量参数。
步骤1016、所述增强接入设备根据所述服务质量参数向所述终端设备发送第二下行数 据包。
步骤1017、所述增强接入设备接收所述终端设备发送的第一上行数据包。
步骤1018、所述增强接入设备获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID。
步骤1019、所述增强接入设备向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
步骤1020、所述服务网关向所述数据网关发送第三上行数据包。
具体的，所述服务网关根据所述第二IP地址和所述第二TEID确定数据网关分配的承载的IP地址和TEID；所述第三上行数据包中包括所述数据网关分配的承载的IP地址和TEID。
基于以上实施例，本申请实施例还提供了另一种业务数据包转发的方法的示例，该示例是PDU会话更新的场景中，在承载建立流程中，通过增强接入设备支持QoS流的隧道，使得终端设备的业务数据包可以正常转发。在该示例中，接入设备为增强接入设备，移动管理设备为增强移动管理设备，在该示例中以增强接入设备和增强移动管理设备示出。参阅图11所示，该示例的具体流程可以包括：
步骤1101、策略和计费规则功能实体触发IP-CAN会话更新，向数据网关发送IP-CAN会话更新请求，以发送更新的计费和服务质量等规则给数据网关。
步骤1102、所述数据网关决策触发承载建立流程，向服务网关发送建立承载请求消息2，所述建立承载请求消息2中包含数据网关分配的用于转发此承载对应的上行数据包的IP地址和TEID。
步骤1103、所述服务网关向增强移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述服务网关分配的用于转发此承载对应的上行数据包的IP地址和TEID，即所述IP地址和TEID为承载的IP地址和TEID，也即图6所示的实施例中涉及的第二IP地址和第二TEID。
步骤1104、所述增强移动管理设备向增强接入设备发送PDU会话资源更新请求消息。
其中，所述增强移动管理设备为承载对应的QoS流分配QoS流标识(分配流标识)，所述PDU会话资源更新请求消息中包含QoS流标识，QoS流标识的分配方法参见上述实施例中涉及的方法，此处不再详细描述。
所述PDU会话资源更新请求消息中还携带QoS流的IP地址和TEID，即步骤1103中服务网关分配的用于转发此承载对应的上行数据包的IP地址和TEID。
所述PDU会话资源更新请求消息中还包含发送给终端设备的PDU会话更新请求消息。
步骤1105、所述增强接入设备向终端设备发送PDU会话更新请求消息，所述PDU会话更新请求消息中包含所述QoS流标识。
步骤1106、所述终端设备向所述增强接入设备发送PDU会话更新完成消息，所述送PDU会话更新完成消息中包含QoS流标识，用于指示所述QoS流建立完成。
步骤1107、所述增强接入设备向所述增强移动管理设备转发所述PDU会话更新完成消息。
步骤1108、所述接入设备向所述增强移动管理设备发送PDU会话资源更新响应消息，所述PDU会话资源更新响应消息中包含QoS流标识，用于指示所述QoS流建立完成。
其中，所述PDU会话资源更新响应消息中还包含QoS流的IP地址和TEID，即增强接入设备分配的用于转发此QoS流对应的下行数据包的IP地址和TEID，即所述IP地址和TEID为QoS流的IP地址和TEID，也即图4所示的实施例中的第一IP地址和第一TEID。
步骤1109、所述增强移动管理设备向所述服务网关发送第一建立承载响应消息。
其中，所述增强移动管理设备为此承载分配承载标识，所述QoS流标识可以和承载标识相同，或者通过一定的算法由QoS流标识计算出承载标识，或者承载标识的分配和QoS流标识没有关系，但是增强移动管理设备本地保存QoS流标识和承载标识的对应关系。QoS流标识或者承载标识用于标识一个承载，本流程中为专有承载。所述第一建立承载响应消息中包含所述承载标识。
具体的，所述第一建立承载响应消息中还包含承载的IP地址和TEID，即增强移动管理网元在步骤1108收到的增强接入设备分配的IP地址和TEID。
步骤1110、所述服务网关向所述数据网关发送第二建立承载响应消息，所述第二建立承载响应消息中包括承载标识和服务网关分配的用于转发此承载对应的下行数据包的IP地址和TEID。
步骤1111、所述数据网关向所述策略和计费规则功能实体发送IP-CAN会话更新响应消息。
步骤1112：所述服务网关接收所述数据网关发送的第三下行数据包，所述第三下行数据包中包含所述服务网关分配的用于转发此承载对应的下行数据包的IP地址和TEID。
所述服务网关根据所述服务网关分配的用于转发此承载对应的下行数据包的IP地址和TEID，确定增强接入设备分配的QoS流的第一IP地址和第一TEID。
步骤1113、所述服务网关向所述接入设备发送第一下行数据包，所述第一下行数据包中包含所述第一IP地址和所述第一TEID。
步骤1114、所述增强接入设备获取与所述第一IP地址和所述第一TEID对应的QoS流上下文中的服务质量参数。
具体的，所述增强接入设备确定所述第一IP地址和所述第一TEID对应的所述QoS流上下文，从而获得所述服务质量参数。
步骤1115、所述增强接入设备根据所述服务质量参数向所述终端设备发送第二下行数据包。
步骤1116、所述增强接入设备接收所述终端设备发送的第一上行数据包。
步骤1117、所述增强接入设备获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID。
步骤1118、所述增强接入设备向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
步骤1119、所述服务网关向所述数据网关发送第三上行数据包。
具体的，所述服务网关根据所述第二IP地址和所述第二TEID确定数据网关分配的承载的IP地址和TEID；所述第三上行数据包中包含所述数据网关分配的承载的IP地址和 TEID。
需要说明的是，在图10所示的示例中或者图11所示的示例中，下行数据包转发的过程和上行数据包转发的过程的发生顺序并不限定，图中仅仅是一种顺序示例，应理解，可以上行数据包转发在先，下行数据包转发在后，本申请对此不作限定。
基于以上实施例，本申请实施例提供了一种业务数据包转发的方法的示例，该示例是接入设备、移动管理设备和服务网关发生切换的切换流程中，业务数据包转发的示例。其中，在该示例中，切换流程可以是4G到5G移动管理设备改变，服务网关改变的流程；在该流程中源接入设备为4G基站eNodeB，新接入设备为ng-eNB或者gNB。或者，在该示例中，切换流程可以是5G到5G移动管理设备改变，服务网关改变的流程；在该流程中源侧接入设备为ng-eNB或者gNB，新侧接入设备(目标接入设备)为ng-eNB或者gNB。参阅图12所示，该示例的具体流程可以包括：
步骤1201、源侧接入设备触发切换流程，向源侧移动管理设备发送切换要求消息。
具体的，所述源侧接入设备检测到终端设备在新侧接入设备下的信号强度超过一定门限，则触发终端设备切换到所述新侧接入设备。
其中，所述切换要求消息中包含接入类型，所述接入类型用于指示所述终端设备在新接入设备的接入类型。示例性的，所述接入类型可以为所述终端设备接入的接入设备的类型，或者为无线接入网络的类型，或者为所述终端设备的类型。
其中，4G到5G，或者5G到5G的切换流程所述接入设备的类型可以为下一代演进型基站ng-eNB类型或者下一代基站gNB类型；所述无线接入网络的类型为新无线NR类型或者演进的通用陆地无线接入网Evolved E-UTRAN类型；所述终端设备的类型为5G类型。
可选的，所述第一切换请求消息中还包含目标接入设备(也即新侧接入设备)的标识。
步骤1202、所述源侧移动管理设备向新侧移动管理设备(目标移动管理设备)发送转发切换请求消息。
其中，所述转发切换请求消息中包含所述接入类型。
所述转发切换请求消息中还包含所述目标接入设备(即新侧接入设备)的标识，以及所述终端设备的上下文，包含终端设备的一个或者多个已经建立的PDN连接的上下文，每个PDN连接上下文包含一个或者多个承载上下文，每个承载上下文中包含承载标识，QoS流标识，以及数据网关分配的IP地址和TEID。
步骤1203、所述新侧移动管理设备向新侧服务网关(目标服务网关)发送建立会话请求消息。
所述建立会话请求消息中包含所述接入类型，每个承载的承载标识，以及数据网关分配的IP地址和TEID。
步骤1204、所述新侧服务网关向所述新侧移动管理设备发送建立会话响应消息。
其中，一种示例中，针对PDN连接粒度的隧道：所述新侧服务网关根据所述接入类型分配报文数据网络PDN连接的IP地址和所述TEID(即图3所示的实施例涉及的第三IP地址和第三TEID)；所述建立会话响应消息中包含所述新侧服务网关根据所述接入类型分配的报文数据网络PDN连接的IP地址和所述TEID。
另一种示例中，针对承载粒度的隧道(和现有4G网络技术一样)：所述新侧服务网关分配承载的IP地址和TEID，所述建立会话响应消息中包含所述新侧服务网关分配承载的IP地址和TEID。
步骤1205、所述新侧移动管理设备向新侧接入设备发送切换请求消息，所述切换请求消息用于请求新侧接入设备建立终端设备的业务数据包转发通道。
其中，所述切换请求消息中包括步骤1204中新侧服务网关分配的IP地址和TEID。
所述切换请求消息中还包含步骤1202收到的QoS流标识。
步骤1206、所述新侧接入设备向所述新侧移动管理设备发送切换请求响应消息，所述切换请求响应消息中包含所述新侧接入设备为转发下行数据包分配的IP地址和TEID，QoS流标识。
一种示例中，针对PDN连接粒度的隧道：所述新侧接入设备为转发下行数据包分配的IP地址和TEID为图3所示的实施例中涉及的第二IP地址和第二TEID；
另一种示例中，针对承载粒度的隧道，所述新侧接入设备为转发下行数据包分配的IP地址和TEID，即为图5所示的实施例中涉及的第一IP地址和第一TEID。
步骤1207、所述新侧移动管理设备向所述源侧移动管理设备发送转发切换请求响应消息，指示新侧建立成功的承载上下文。
步骤1208、所述源侧移动管理设备向源侧接入设备发送切换指令，用于指示终端设备可以切换到目标侧(即新侧)。
步骤1209、所述源侧接入设备向终端设备转发所述切换指令，用于指示终端设备可以切换到目标侧。
步骤1210、所述终端设备切换到目标侧，向所述新侧接入设备发送切换完成消息。
步骤1211、所述新侧接入设备向所述新侧移动管理设备转发所述切换完成消息。
步骤1212、所述新侧移动管理设备向所述源侧移动管理设备发送切换完成通知消息，以便所述源侧移动管理设备释放源侧的资源。
步骤1213、所述新侧移动管理设备向所述新侧服务网关发送第一更新承载请求消息，所述第一更新承载请求消息中包含步骤1206中接入设备分配的IP地址和TEID。
示例性的，针对PDN连接粒度的隧道，所述第一更新承载请求消息中还包含QoS流标识。
步骤1214、所述新侧服务网关向数据网关发送第二更新承载请求消息，所述第二更新承载请求消息中包含所述新侧服务网关为转发下行数据包分配的承载的IP地址和TEID。
步骤1215、所述数据网关向所述新侧服务网关发送第一更新承载响应消息。
步骤1216、所述新侧服务网关向所述新侧移动管理设备发送第二更新承载响应消息。
步骤1217、所述新侧服务网关接收所述数据网关发送的第一下行数据包。所述第一下行数据包中包含所述新侧服务网关分配的IP地址和TEID。
步骤1218、所述新侧服务网关根据所述新侧服务网关分配的IP地址和TEID确定所述新侧接入设备分配的PDU会话的IP地址和TEID。
具体的，所述新侧服务网关获取所述新侧服务网关分配的IP地址和TEID对应的承载上下文，从而获取根据所述承载上下文获得QoS流标识以及所述新侧接入设备分配的PDU 会话的IP地址和TEID。
或者，所述新侧服务网关根据所述新侧服务网关分配的IP地址和TEID确定所述新侧接入设备分配的QoS流的IP地址和TEID。
具体的，所述新侧服务网关获取所述新侧服务网关分配的IP地址和TEID对应的承载上下文，从而获取根据所述承载上下文获得所述新侧接入设备分配的QoS流的IP地址和TEID。
步骤1219、所述新侧服务网关向所述新侧接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述新侧接入设备分配的PDU会话的IP地址和TEID。或者，所述新侧服务网关向所述新侧接入设备发送第二下行数据包，所述第二下行数据包中包含所述新侧接入设备分配的PDU会话的IP地址和TEID。
步骤1220、所述新侧接入设备向所述终端设备发送第三下行数据包。
具体的，所述新侧接入设备根据所述新侧接入设备分配的PDU会话的IP地址和TEID确定所述新侧接入设备分配的PDU会话的IP地址和TEID对应的PDU会话上下文，根据所述QoS流标识确定对应的QoS流，然后所述新侧接入设备根据所述QoS流关联的服务质量QoS参数发送所述第三下行数据包给终端设备。
或者，所述新侧接入设备根据所述新侧接入设备分配的QoS流的IP地址和TEID确定所述新侧接入设备分配的QoS流的IP地址和TEID对应的QoS流上下文，然后所述新侧接入设备根据所述QoS流关联的服务质量QoS参数发送所述第三下行数据包给终端设备。
步骤1221、所述新侧接入设备接收所述终端设备发送的第三上行数据包，所述第三上行数据包在对应的空口承载发送，所述新侧接入设备根据所述空口承载确定第三上行数据包对应的QoS流，所述新侧接入设备获得QoS流上下文中的QoS流标识，以及QoS流对应的PDU会话上下文中的所述新侧服务网关分配的IP地址和TEID。
或者，所述新侧接入设备获得QoS流上下文中的所述新侧服务网关分配的QoS流的IP地址和TEID。
步骤1222、所述新侧接入设备向所述新侧服务网关发送第一上行数据包。
所述第一上行数据包中包含所述新侧服务网关分配的PDN连接的IP地址和TEID以及所述QoS流标识。
或者，所述第一上行数据包中包含所述新侧服务网关分配的QoS流的IP地址和TEID。
步骤1223、所述新侧服务网关根据所述新侧服务网关分配的IP地址和TEID确定数据网关分配的承载的IP地址和TEID。
具体的，所述新侧服务网关确定所述新侧服务网关分配的IP地址和TEID对应的PDN连接上下文，然后根据所述QoS流标识确定所述PDN连接上下文中的承载上下文，根据所述承载上下文获得所述数据网关分配的承载的IP地址和TEID。
或者，所述新侧服务网关确定所述新侧服务网关分配的IP地址和TEID对应的承载上下文，根据所述承载上下文获得所述数据网关分配的承载的IP地址和TEID。
步骤1224、所述新侧服务网关向数据网关发送第二上行数据包，所述第二上行数据包中包含所述数据网关分配的承载的IP地址和TEID。
基于以上实施例，本申请实施例还提供了一种服务网关，该服务网关应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的服务网关(或者增强服务网关)的功能。参阅图13所示，该服务网关1300包括：通信单元1301和处理单元1302，其中：
所述通信单元1301用于接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述处理单元1302用于根据所述第一IP地址和所述第一TEID确定服务质量QoS流标识以及接入设备分配的分组数据单元PDU会话的第二IP地址和第二TEID；所述通信单元1301还用于向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID；
或者，
所述通信单元1301用于接收所述接入设备发送的第一上行数据包，所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识；所述处理单元1302用于根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；所述通信单元1301还用于向所述数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
在一种可选的实施方式中，所述通信单元1301，还用于接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；所述处理单元1302，还用于根据所述接入类型分配报文数据网络PDN连接的所述第三IP地址和所述第三TEID；所述通信单元1301，还用于向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。
示例性的，所述通信单元1301还用于向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。
具体的，所述通信单元1301还用于接收移动管理设备发送的更新承载请求消息或者第一建立承载响应消息，所述更新承载请求消息或者第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息；或者，基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息。
采用本申请实施例提供的服务网关，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
基于以上实施例，本申请实施例还提供了一种接入设备，该接入设备应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的接入设备的功能。参阅图14所示，该接入设备1400包括：通信单元1401和处理单元1402，其中：
所述通信单元1401用于接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述处理单元1402用于获取与所述第一IP地址和所述第一TEID对应的服务质量QoS流上下文中的服务质量参数；所述通信单元1401还用于根据所述服务质量参数向终端设备发送第二下行数据包；
或者，
所述通信单元1401用于接收终端设备发送的第一上行数据包；所述处理单元1402，用于获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID；所述通信单元1401还用于向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
在一种可选的实施方式中，所述通信单元1401还用于接收移动管理设备发送的PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
示例性的，所述通信单元1401还用于向移动管理设备发送PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
采用本申请实施例提供的接入设备，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
基于以上实施例，本申请实施例还提供了一种移动管理设备，该移动管理设备应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的移动管理设备(或增强移动管理网元)的功能。参阅图15所示，该移动管理设备1500包括：通信单元1501和处理单元1502，其中：
所述通信单元1501用于收发信息；
所述处理单元1502，用于控制所述通信单元1501接收第一消息，所述第一消息用于建立PDU会话或承载；控制所述通信单元1501向服务网关发送第二消息，所述第二消息中包含承载标识；控制所述通信单元1501向接入设备发送第三消息，所述第三消息中包含QoS流标识；其中，所述承载标识和所述QoS流标识用于标识终端设备的一个承载；所述第一消息为所述终端设备发送的PDU会话建立请求消息，所述第二消息为建立会话请求消息，所述第三消息为PDU会话资源建立请求消息；或者，所述第一消息为所述服务网关发送的建立承载请求消息，所述第二消息为建立承载响应消息，所述第三消息为PDU会话资源更新请求消息；或者所述第一消息为源测移动管理设备发送的转发切换请求消息，所述第二消息为建立会话请求消息，所述第三消息为切换请求消息；所述第一消息、所述第二消息和所述第三消息用于建立业务数据包转发的通道。
在一种可选的实施方式中，当所述第二消息为建立会话请求消息时，所述第二消息中还包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
示例性的，所述处理单元1502，还用于：
控制所述通信单元1501接收所述服务网关发送的建立会话响应消息，所述建立会话响应消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
控制所述通信单元1501向所述接入设备发送PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源建立请求消息或者切换请求消息中包含所述第一IP地址和所述第一TEID；
控制所述通信单元1501接收接入设备发送的PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源建立响应消息或者切换请求响应消息中包含接入设备分配的第二IP地址和第二TEID；其中，所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID或者为QoS流的IP地址和TEID；
控制所述通信单元1501向所述服务网关发送更新承载请求消息，所述更新承载请求消息中包含所述第二IP地址和所述第二TEID。
具体的，所述更新承载请求消息中还包含QoS流标识。
在一种可能的实现方式中，所述建立承载请求消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
所述处理单元1502还用于：控制所述通信单元1501向所述接入设备发送PDU会话资源更新请求消息；其中，当所述第一地址和所述第一TEID为承载的IP地址和TEID时，所述PDU会话资源更新请求消息中包含所述第一IP地址和所述第一TEID，或者，当所述第一地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新请求消息中不包含所述第一IP地址和所述第一TEID；
控制所述通信单元1501接收所述接入设备发送的PDU会话资源更新响应消息；其中，所述PDU会话资源更新响应消息中包含所述接入设备分配的第二IP地址和第二TEID，所述第二IP地址和所述第二TEID为QoS流的IP地址和TEID；或者，当所述第一IP地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新响应消息中不包含接入设备分配的IP地址和TEID；
控制所述通信单元1501向所述服务网关发送建立承载响应消息；所述建立承载响应消息中包含所述第二IP地址和所述第二TEID；或者，当所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID时，所述建立承载响应消息中不包含接入设备分配的IP地址和TEID；或者，所述建立承载响应消息中包含所述第二IP地址和所述第二TEID，所述第二IP地址和所述第二TEID为所述移动管理设备从PDU会话资源建立响应消息或者切换请求响应消息中获得的。
具体的，所述建立承载响应消息中还包含所述QoS流标识。
采用本申请实施例提供的移动管理设备，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者 说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供了一种服务网关，所述服务网关应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的服务网关(或者增强服务网关)的功能。参阅图16所示，所述移动管理设备1600可以包括：通信接口1601和处理器1602，可选的还可以包括存储器1603。其中，所述处理器1602可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合等等。所述处理器1602还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。所述处理器1602在实现上述功能时，可以通过硬件实现，当然也可以通过硬件执行相应的软件实现。
所述通信接口1601和所述处理器1602之间相互连接。可选的，所述通信接口1601和所述处理器1602通过总线1604相互连接；所述总线1604可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述存储器1603，与所述处理器1602耦合，用于存放所述SRS的传输装置1600必要的程序等。例如，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1603可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。所述处理器1602执行所述存储器1603所存放的应用程序，实现所述服务网关1600的功能。
具体的，所述服务网关1600在实现上述实施例或者示例中的服务网关(或者增强服务网关)的功能时：
所述通信接口1601用于接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述处理器1602用于根据所述第一IP地址和所述第一TEID确定服务质量QoS流标识以及接入设备分配的分组数据单元PDU会话的第二IP地址和第二TEID；所述通信接口1601还用于向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID；
或者，
所述通信接口1601用于接收所述接入设备发送的第一上行数据包，所述第一上行数据 包中包含第三IP地址和第三TEID以及所述QoS流标识；所述处理器1602用于根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；所述通信接口1601还用于向所述数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
在一种可选的实施方式中，所述通信接口1601，还用于接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；所述处理器1602，还用于根据所述接入类型分配报文数据网络PDN连接的所述第三IP地址和所述第三TEID；所述通信接口1601，还用于向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。
示例性的，所述通信接口1601还用于向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。
具体的，所述通信接口1601还用于接收移动管理设备发送的更新承载请求消息或者第一建立承载响应消息，所述更新承载请求消息或者第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息；或者，基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息。
采用本申请实施例提供的服务网关，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
基于以上实施例，本申请实施例还提供了一种接入设备，所述接入设备应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的接入设备的功能。参阅图17所示，所述移动管理设备1700可以包括：通信接口1701和处理器1702，可选的还可以包括存储器1703。其中，所述处理器1702可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合等等。所述处理器1702还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。所述处理器1702在实现上述功能时，可以通过硬件实现，当然也可以通过硬件执行相应的软件实现。
所述通信接口1701和所述处理器1702之间相互连接。可选的，所述通信接口1701和所述处理器1702通过总线1704相互连接；所述总线1704可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述存储器1703，与所述处理器1702耦合，用于存放所述SRS的传输装置1700必要的程序等。例如，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器 1703可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。所述处理器1702执行所述存储器1703所存放的应用程序，实现所述接入设备1700的功能。
具体的，所述移动管理设备1700在实现上述实施例或者示例中的接入设备的功能时：
所述通信接口1701用于接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；所述处理器1702用于获取与所述第一IP地址和所述第一TEID对应的服务质量QoS流上下文中的服务质量参数；所述通信接口1701还用于根据所述服务质量参数向终端设备发送第二下行数据包；
或者，
所述通信接口1701用于接收终端设备发送的第一上行数据包；所述处理器1702，用于获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID；所述通信接口1701还用于向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
在一种可选的实施方式中，所述通信接口1701还用于接收移动管理设备发送的PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
示例性的，所述通信接口1701还用于向移动管理设备发送PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
采用本申请实施例提供的接入设备，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
基于以上实施例，本申请实施例还提供了一种移动管理设备，所述移动管理设备应用于如图2a所示的通信系统，用于实现上述实施例或者示例中的移动管理设备(或增强移动管理网元)的功能。参阅图18所示，所述移动管理设备1800可以包括：通信接口1801和处理器1802，可选的还可以包括存储器1803。其中，所述处理器1802可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合等等。所述处理器1802还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。所述处理器1802在实现上述功能时，可以通过硬件实现，当然也可以通过硬件执行相应的软件实现。
所述通信接口1801和所述处理器1802之间相互连接。可选的，所述通信接口1801和所述处理器1802通过总线1804相互连接；所述总线1804可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry  Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述存储器1803，与所述处理器1802耦合，用于存放所述SRS的传输装置1800必要的程序等。例如，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1803可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。所述处理器1802执行所述存储器1803所存放的应用程序，实现所述移动管理设备1800的功能。
具体的，所述移动管理设备1800在实现上述实施例或者示例中的移动管理设备(或增强移动管理网元)的功能时：
所述通信接口1801用于收发信息；
所述处理器1802，用于控制所述通信接口1801接收第一消息，所述第一消息用于建立PDU会话或承载；控制所述通信接口1801向服务网关发送第二消息，所述第二消息中包含承载标识；控制所述通信接口1801向接入设备发送第三消息，所述第三消息中包含QoS流标识；其中，所述承载标识和所述QoS流标识用于标识终端设备的一个承载；所述第一消息为所述终端设备发送的PDU会话建立请求消息，所述第二消息为建立会话请求消息，所述第三消息为PDU会话资源建立请求消息；或者，所述第一消息为所述服务网关发送的建立承载请求消息，所述第二消息为建立承载响应消息，所述第三消息为PDU会话资源更新请求消息；或者所述第一消息为源测移动管理设备发送的转发切换请求消息，所述第二消息为建立会话请求消息，所述第三消息为切换请求消息；所述第一消息、所述第二消息和所述第三消息用于建立业务数据包转发的通道。
在一种可选的实施方式中，当所述第二消息为建立会话请求消息时，所述第二消息中还包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入。
示例性的，所述处理器1802，还用于：
控制所述通信接口1801接收所述服务网关发送的建立会话响应消息，所述建立会话响应消息中包含所述服务网关分配的第一IP地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
控制所述通信接口1801向所述接入设备发送PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源建立请求消息或者切换请求消息中包含所述第一IP地址和所述第一TEID；
控制所述通信接口1801接收接入设备发送的PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源建立响应消息或者切换请求响应消息中包含接入设备分配的第二IP地址和第二TEID；其中，所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID或者为QoS流的IP地址和TEID；
控制所述通信接口1801向所述服务网关发送更新承载请求消息，所述更新承载请求消息中包含所述第二IP地址和所述第二TEID。
具体的，所述更新承载请求消息中还包含QoS流标识。
在一种可能的实现方式中，所述建立承载请求消息中包含所述服务网关分配的第一IP 地址和第一TEID；其中，所述第一地址和所述第一TEID为PDN连接的IP地址和TEID或者为承载的IP地址和TEID；
所述处理器1802还用于：控制所述通信接口1801向所述接入设备发送PDU会话资源更新请求消息；其中，当所述第一地址和所述第一TEID为承载的IP地址和TEID时，所述PDU会话资源更新请求消息中包含所述第一IP地址和所述第一TEID，或者，当所述第一地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新请求消息中不包含所述第一IP地址和所述第一TEID；
控制所述通信接口1801接收所述接入设备发送的PDU会话资源更新响应消息；其中，所述PDU会话资源更新响应消息中包含所述接入设备分配的第二IP地址和第二TEID，所述第二IP地址和所述第二TEID为QoS流的IP地址和TEID；或者，当所述第一IP地址和所述第一TEID为PDN连接的IP地址和TEID时，所述PDU会话资源更新响应消息中不包含接入设备分配的IP地址和TEID；
控制所述通信接口1801向所述服务网关发送建立承载响应消息；所述建立承载响应消息中包含所述第二IP地址和所述第二TEID；或者，当所述第二IP地址和所述第二TEID为PDU会话的IP地址和TEID时，所述建立承载响应消息中不包含接入设备分配的IP地址和TEID；或者，所述建立承载响应消息中包含所述第二IP地址和所述第二TEID，所述第二IP地址和所述第二TEID为所述移动管理设备从PDU会话资源建立响应消息或者切换请求响应消息中获得的。
具体的，所述建立承载响应消息中还包含所述QoS流标识。
采用本申请实施例提供的移动管理设备，可以实现通过5G技术接入4G网络时，保证业务正常进行，避免影响用户的业务体验。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (15)

  1. 一种业务数据包转发的方法，其特征在于，包括：
    服务网关接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；
    所述服务网关根据所述第一IP地址和所述第一TEID确定服务质量QoS流标识以及接入设备分配的分组数据单元PDU会话的第二IP地址和第二TEID；
    所述服务网关向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID；
    或者
    所述服务网关接收所述接入设备发送的第一上行数据包，所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识；
    所述服务网关根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；
    所述服务网关向所述数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；
    所述服务网关根据所述接入类型分配报文数据网络PDN连接的所述第三IP地址和所述第三TEID；
    所述服务网关向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述服务网关向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收移动管理设备发送的更新承载请求消息或者第一建立承载响应消息，所述更新承载请求消息或者第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；
    所述服务网关基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息；或者，所述服务网关基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息。
  5. 一种业务数据包转发的方法，其特征在于，包括：
    接入设备接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；
    所述接入设备获取与所述第一IP地址和所述第一TEID对应的服务质量QoS流上下文中的服务质量参数；
    所述接入设备根据所述服务质量参数向终端设备发送第二下行数据包；
    或者
    所述接入设备接收终端设备发送的第一上行数据包；
    所述接入设备获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID；
    所述接入设备向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述接入设备接收移动管理设备发送的PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
  7. 如权利要求5或6所述的方法，其特征在于，所述方法还包括：
    所述接入设备向移动管理设备发送PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
  8. 一种服务网关，其特征在于，包括：
    通信接口，用于接收数据网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；
    处理器，用于根据所述第一IP地址和所述第一TEID确定服务质量QoS流标识以及接入设备分配的分组数据单元PDU会话的第二IP地址和第二TEID；
    所述通信接口，还用于向所述接入设备发送第二下行数据包，所述第二下行数据包中包含所述QoS流标识以及所述第二IP地址和所述第二TEID；
    或者
    所述通信接口，用于接收所述接入设备发送的第一上行数据包，所述第一上行数据包中包含第三IP地址和第三TEID以及所述QoS流标识；
    所述处理器，用于根据所述第三IP地址和所述第三TEID以及所述QoS流标识确定数据网关分配的承载的第四IP地址和第四TEID；
    所述通信接口，还用于向所述数据网关发送第二上行数据包，所述第二上行数据包中包含所述第四IP地址和所述第四TEID。
  9. 如权利要求8所述的服务网关，其特征在于，
    所述通信接口，还用于接收移动管理设备发送的建立会话请求消息，所述建立会话请求消息中包含终端设备的接入类型，所述接入类型用于指示所述终端设备从新无线网络或者演进的通用陆地无线接入网接入；
    所述处理器，还用于根据所述接入类型分配报文数据网络PDN连接的所述第三IP地址 和所述第三TEID；
    所述通信接口，还用于向所述移动管理设备发送建立会话响应消息，所述建立会话响应消息中包含所述第三IP地址和所述第三TEID。
  10. 如权利要求9所述的服务网关，其特征在于，所述通信接口，还用于：
    向所述移动管理设备发送建立承载请求消息，所述建立承载请求消息中包含所述第三IP地址和所述第三TEID。
  11. 如权利要求8-10任一项所述的服务网关，其特征在于，所述通信接口，还用于：
    接收移动管理设备发送的更新承载请求消息或者第一建立承载响应消息，所述更新承载请求消息或者第一建立承载响应消息中包含所述第二IP地址和所述第二TEID以及所述QoS流标识；
    基于所述更新承载请求消息向所述移动管理设备发送更新承载响应消息；或者，基于所述第一建立承载响应消息向所述数据网关发送第二建立承载响应消息。
  12. 一种接入设备，其特征在于，包括：
    通信接口，用于接收服务网关发送的第一下行数据包，所述第一下行数据包中包含第一互联网协议IP地址和第一隧道端点标识TEID；
    处理器，用于获取与所述第一IP地址和所述第一TEID对应的服务质量QoS流上下文中的服务质量参数；
    所述通信接口，还用于根据所述服务质量参数向终端设备发送第二下行数据包；
    或者
    所述通信接口，用于接收终端设备发送的第一上行数据包；
    所述处理器，用于获取所述第一上行数据包所在的QoS流上下文中的服务网关分配的QoS流的第二IP地址和第二TEID；
    所述通信接口，还用于向所述服务网关发送第二上行数据包，所述第二上行数据包中包含所述第二IP地址和所述第二TEID。
  13. 如权利要求12所述的接入设备，其特征在于，所述通信接口，还用于：
    接收移动管理设备发送的PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息，所述PDU会话资源更新请求消息或者PDU会话资源建立请求消息或者切换请求消息中包含QoS流标识以及所述第二IP地址和所述第二TEID。
  14. 如权利要求12或13所述的接入设备，其特征在于，所述通信接口，还用于：
    向移动管理设备发送PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息，所述PDU会话资源更新响应消息或者PDU会话资源建立响应消息或者切换请求响应消息中包含所述接入设备为下行数据包分配的QoS流的所述第一IP地址和所述第一TEID。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述权利要求1-7中任一项所述的方法。
PCT/CN2020/113342 2019-09-09 2020-09-03 一种业务数据包转发的方法及装置 WO2021047443A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910848792.0 2019-09-09
CN201910848792.0A CN112469077B (zh) 2019-09-09 2019-09-09 一种业务数据包转发的方法及装置

Publications (1)

Publication Number Publication Date
WO2021047443A1 true WO2021047443A1 (zh) 2021-03-18

Family

ID=74807339

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/113342 WO2021047443A1 (zh) 2019-09-09 2020-09-03 一种业务数据包转发的方法及装置

Country Status (2)

Country Link
CN (1) CN112469077B (zh)
WO (1) WO2021047443A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333788B (zh) * 2020-11-13 2022-10-11 武汉虹旭信息技术有限责任公司 N2接口切换场景下的会话管理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180255463A1 (en) * 2017-02-16 2018-09-06 Casa Systems, Inc. Scalable evolved packet core
WO2018165934A1 (en) * 2017-03-16 2018-09-20 Intel Corporation Systems, methods and devices for user plane traffic forwarding
CN109155949A (zh) * 2017-01-09 2019-01-04 Lg 电子株式会社 无线通信中在网络之间的互通方法及其装置
CN109842535A (zh) * 2017-11-28 2019-06-04 华为技术有限公司 一种接入本地网络的方法和设备
CN110035423A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 会话管理方法、设备及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730142B (zh) * 2009-06-30 2012-09-05 中兴通讯股份有限公司 多分组数据网络连接的建立方法以及装置
CN102892109B (zh) * 2011-07-21 2018-05-11 中兴通讯股份有限公司 一种实现ip地址属性通知的方法和系统
US11265935B2 (en) * 2016-01-18 2022-03-01 Samsung Electronics Co., Ltd. Resource assignment for general packet radio service tunneling protocol (GTP) entities in 5G
US20180048558A1 (en) * 2016-08-10 2018-02-15 Cisco Technology, Inc. Optimizing traffic in a packet core network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109155949A (zh) * 2017-01-09 2019-01-04 Lg 电子株式会社 无线通信中在网络之间的互通方法及其装置
US20180255463A1 (en) * 2017-02-16 2018-09-06 Casa Systems, Inc. Scalable evolved packet core
WO2018165934A1 (en) * 2017-03-16 2018-09-20 Intel Corporation Systems, methods and devices for user plane traffic forwarding
CN109842535A (zh) * 2017-11-28 2019-06-04 华为技术有限公司 一种接入本地网络的方法和设备
CN110035423A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 会话管理方法、设备及系统

Also Published As

Publication number Publication date
CN112469077B (zh) 2022-07-29
CN112469077A (zh) 2021-03-09

Similar Documents

Publication Publication Date Title
JP7123920B2 (ja) 切り替え方法及び装置
US20230180349A1 (en) Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device
US20230217526A1 (en) Packet Transmission Method, Apparatus, and System
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
EP3681201B1 (en) Data forwarding method, device, and system
CN105723801B (zh) 无线资源控制rrc消息处理方法、装置和系统
TWI719836B (zh) Eps承載處理方法及使用者設備
WO2020199960A1 (zh) 时延获取方法及装置、优化方法及装置
US20210120620A1 (en) Communication Method and Apparatus
US11489760B2 (en) Multicast group creation method, multicast group joining method, and apparatus
EP3445081B1 (en) Flow-based bearer management method and device
US11689956B2 (en) Relocation method and apparatus
KR20200058478A (ko) 복제 전송을 위한 방법 및 장치
CN111586602B (zh) 一种策略管理的方法及装置
WO2022052798A1 (zh) QoS控制方法、装置及处理器可读存储介质
US20230029292A1 (en) Data transmission method and apparatus
CN105101311B (zh) 一种承载切换方法、设备及系统
WO2021047443A1 (zh) 一种业务数据包转发的方法及装置
EP2850912A1 (en) Efficient distribution of signaling messages in a mobility access gateway or!local mobility anchor
WO2023087965A1 (zh) 一种通信方法及装置
TW201929571A (zh) 網路重定向方法及終端、存取網設備、移動管理設備
WO2022017403A1 (zh) 通信方法及装置
WO2021047514A1 (zh) 一种会话管理的方法及装置
CN114040343B (zh) 一种wifi设备接入5g核心网方法及系统
WO2019136927A1 (zh) 一种数据传输方法及装置、计算机存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20863335

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20863335

Country of ref document: EP

Kind code of ref document: A1