Nothing Special   »   [go: up one dir, main page]

WO2019085888A1 - Procédé, dispositif, et système de traitement de flux de trafic support dédié - Google Patents

Procédé, dispositif, et système de traitement de flux de trafic support dédié Download PDF

Info

Publication number
WO2019085888A1
WO2019085888A1 PCT/CN2018/112626 CN2018112626W WO2019085888A1 WO 2019085888 A1 WO2019085888 A1 WO 2019085888A1 CN 2018112626 W CN2018112626 W CN 2018112626W WO 2019085888 A1 WO2019085888 A1 WO 2019085888A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
stream
edge gateway
pgw
indication information
Prior art date
Application number
PCT/CN2018/112626
Other languages
English (en)
Chinese (zh)
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 WO2019085888A1 publication Critical patent/WO2019085888A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present application relates to the field of communications, and in particular, to a method, an apparatus, and a system for processing a proprietary bearer stream.
  • the 3rd Generation Partnership Project (3GPP) Evolved Packet System includes Evolved Packet Core (EPC), edge gateway, base station (eNodeB), and user equipment (User Equipment). , UE), wherein the EPC includes a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network GateWay (PGW), and a policy and charging rule function (Policy) And Charging Rules Function, PCRF) devices, etc.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network GateWay
  • Policy Policy And Charging Rules Function
  • PCRF Policy And Charging Rules Function
  • the default bearer can be understood as a bearer that provides a best effort connection.
  • a proprietary bearer is a bearer that can meet the requirements of a user-specific QoS and is applicable to a specific service, such as a Voice over Long Term Evolution (VoLTE) service.
  • VoIP Voice over Long Term Evolution
  • a service flow (referred to as a proprietary bearer flow) transmitted by a dedicated bearer is transmitted from an edge gateway to a PGW, and the edge gateway does not directly transmit the proprietary bearer flow to an edge server deployed on the edge gateway side (
  • the edge server belongs to the area-level server.
  • the offloading of the dedicated bearer stream cannot be implemented. Therefore, the user needs to share the information locally. Therefore, a method for offloading the dedicated bearer stream is needed.
  • the present invention provides a method, an apparatus, and a system for processing a proprietary bearer stream, which can solve the problem that the dedicated bearer stream cannot be implemented in the related art, and the user cannot properly satisfy the local information sharing requirement.
  • the technical solution is as follows:
  • the first aspect provides a method for processing a proprietary bearer stream, where the method can be used for an edge gateway, where the method includes: the edge gateway receives the first bearer stream of the first UE, and then is private in the first bearer stream.
  • the first bearer flow is sent to the edge server to offload the first bearer flow.
  • the edge gateway sends the offloading indication information to the PGW.
  • the edge gateway starts timeout monitoring for the first bearer.
  • the offloading indication information is used to indicate that the PGW is to disable the timeout monitoring for the first bearer for transmitting the first bearer flow, and the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration.
  • the close response message is used to indicate that the PGW has turned off timeout monitoring for the first bearer.
  • the edge gateway can perform the offloading operation on the dedicated bearer stream, and the edge gateway can directly transmit the proprietary bearer stream to the edge server deployed on the edge gateway side, thereby shortening the transmission path of the proprietary bearer stream.
  • the number of transmission nodes is reduced, the transmission delay is reduced, and the user's need to share information locally is better satisfied.
  • the edge gateway After the edge gateway performs the offloading operation on the dedicated bearer stream, the edge gateway sends the offloading indication information to the PGW to prevent the service from being interrupted or failed. There is timeout monitoring of the bearer (ie, the first bearer), and then the edge gateway turns on timeout monitoring for the dedicated bearer to monitor the state of the dedicated bearer.
  • the method may further include: the edge gateway sends a release indication to the PGW if the idle duration of the first bearer reaches a preset duration based on the open timeout monitoring. Information, the release indication information is used to instruct the PGW to perform a release operation on the first bearer. Afterwards, the edge gateway receives the release response information sent by the PGW, and the release response information is used to indicate whether the release operation is successful.
  • the edge gateway if the edge gateway detects that the idle duration of the first bearer reaches a preset duration, the edge gateway sends a release indication information to the PGW to instruct the PGW to perform a release operation on the first bearer: releasing resources occupied by the first bearer. To achieve the effect of saving network resources.
  • receiving the first bearer stream of the first UE may include: receiving the first bearer stream sent by the first UE that is forwarded by the base station.
  • the method may further include: the edge gateway receiving the default bearer stream sent by the first UE forwarded by the base station.
  • the edge gateway sends the creation indication information to the PGW, and the creation indication information is used to instruct the PGW to create the first bearer.
  • the default bearer flow carries the IP quintuple information of the default bearer flow.
  • the method may further include: determining, by the edge gateway, the IP of the default bearer flow. Whether the tuple information conforms to the first preset rule. In the case that the IP quintuple information of the default bearer flow conforms to the first preset rule, the edge gateway determines that the default bearer flow needs to be offloaded. The edge gateway then determines whether the IP quintuple information of the default bearer flow complies with the pre-configured creation rules of the edge gateway. In the case that the IP quintuple information of the default bearer flow conforms to the creation rule, the edge gateway determines that the default bearer flow is used to trigger the creation of the first bearer.
  • the edge gateway further determines the default bearer flow if the IP quintuple information of the default bearer flow conforms to the first preset rule. Whether it is a bearer stream used to trigger a dedicated bearer creation.
  • the edge gateway can trigger the creation of the first bearer in the case that the default bearer flow for triggering the creation of the first bearer is offloaded by the edge gateway, instructing the PGW to create the first bearer, and avoiding the default bearer flow being shunted by the edge gateway. The creation of the first bearer could not be triggered.
  • the first bearer stream carries the QoS parameter of the first bearer stream.
  • the method may further include: the edge gateway detects that the QoS parameter of the first bearer stream changes.
  • the modification indication information is sent to the PGW, and the modification indication information is used to indicate that the PGW modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer flow.
  • the edge gateway receives the modification response information sent by the PGW, and the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
  • the edge gateway If the edge gateway detects that the QoS parameter of the first bearer stream changes, the edge gateway sends a modification indication information to the PGW to instruct the PGW to modify the QoS parameter of the first bearer to meet the service requirement, so as to provide a reliable QoS for the user. Guarantee, so that users get a better business experience.
  • the timeout monitoring for the first bearer is enabled, and the method includes: setting an aging duration corresponding to the first bearer, and the aging duration is the same as the preset duration.
  • the rule is a network layer protocol and a transport layer protocol of the OSI reference model, or an application layer protocol.
  • the network layer protocol may be an IP protocol, an Address Resolution Protocol (ARP), or the like.
  • the transport layer protocol may be a User Datagram Protocol (UDP), a Transmission Control Protocol (TCP), or the like.
  • the application layer protocol may be Hyper Text Transport Protocol (HTTP), File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Remote Terminal Protocol (TELNET), network. File System (NFS), etc.
  • the first bearer stream is a dedicated bearer stream
  • the first bearer stream is sent to the edge server, where the edge gateway is configured to be a dedicated bearer and the first bearer stream needs to be split. Send the first bearer stream to the edge server.
  • the first bearer stream carries the IP quintuple information of the first bearer stream
  • the method further includes: the edge gateway acquiring the bearer identifier of the first bearer, If the bearer identifier of the first bearer belongs to the preset private bearer identifier set, the edge gateway determines that the first bearer is a dedicated bearer, and the preset private bearer identifier set includes the bearer identifier of the dedicated bearer. Then, the edge gateway determines whether the IP quintuple information of the first bearer flow meets the second preset rule, and the edge gateway determines the first bearer if the IP quintuple information of the first bearer flow meets the second preset rule. The stream needs to be shunted.
  • the bearer identifier of the dedicated bearer may be represented by any one of 6-15.
  • the offloading indication information includes a device identifier of the first UE, a gateway identifier of the edge gateway, and a bearer identifier of the first bearer.
  • the method may further include: the edge gateway receiving the creation response information sent by the PGW, where the creation response information is used to indicate that the creation operation of the first bearer is performed successfully.
  • a method for processing a dedicated bearer stream is provided, and the method is applicable to a PGW.
  • the method includes: the PGW receiving the offloading indication information sent by the edge gateway, where the PGW turns off the timeout for the first bearer based on the offloading indication information. After monitoring, the PGW sends a close response message to the edge gateway.
  • the first bearer is used to transmit the first bearer stream.
  • the offload indication information is generated after the edge gateway sends the first bearer stream of the first UE to the edge server.
  • the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration.
  • the close response message is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
  • the edge gateway After the edge gateway performs the offloading operation on the dedicated bearer stream, the edge gateway sends the offloading indication information to the PGW to prevent the service from being interrupted or failed.
  • the PGW disables the timeout for the first bearer based on the offloading indication information.
  • the PGW sends a shutdown response message to the edge gateway, so that the edge gateway enables timeout monitoring for the first bearer, which is convenient for monitoring the state of the first bearer.
  • the method may further include: the PGW receiving the release indication information sent by the edge gateway, and the PGW performing a release operation on the first bearer based on the release indication information, and then, the PGW to the edge gateway Send release response information.
  • the release indication information is generated by the edge gateway when the idle duration of the first bearer reaches a preset duration based on the open timeout monitoring, and the release response information is used to indicate whether the release operation is successful.
  • the edge gateway If the edge gateway detects that the idle duration of the first bearer reaches a preset duration, the edge gateway sends a release indication information to the PGW to instruct the PGW to perform a release operation on the first bearer: releasing the resources occupied by the first bearer, thereby saving the network. The effect of the resource.
  • the first bearer stream is sent by the first UE to the edge gateway, and before receiving the offloading indication information sent by the edge gateway, the method may further include: the PGW receiving the creation indication information sent by the edge gateway, where the PGW is based on the Create instructions to create the first bearer.
  • the creation of the indication information is that the edge gateway is configured to detect that the default bearer flow needs to be offloaded, and the default bearer flow is used to trigger the creation of the first bearer.
  • the default bearer flow is sent by the first UE to the edge gateway by using the base station.
  • the edge gateway can instruct the PGW to create the first bearer in the case that the default bearer flow for triggering the creation of the first bearer is offloaded by the edge gateway, so as to prevent the first bearer from being triggered because the default bearer flow is offloaded by the edge gateway.
  • the first bearer stream carries the QoS parameter of the first bearer stream
  • the method may further include: the PGW receiving the modification indication information sent by the edge gateway, where the PGW is based on the modification indication information
  • the QoS parameter of the first bearer is modified to the Qos parameter of the first bearer stream, and then the PGW sends the modify response information to the edge gateway.
  • the modification indication information is generated by the edge gateway when detecting that the Qos parameter of the first bearer flow changes.
  • the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
  • the edge gateway If the edge gateway detects that the QoS parameter of the first bearer stream changes, the edge gateway sends a modification indication information to the PGW to instruct the PGW to modify the QoS parameter of the first bearer to meet the service requirement, so as to provide a reliable QoS for the user. Guarantee, so that users get a better business experience.
  • the timeout monitoring for the first bearer is disabled based on the offloading indication information, including: controlling the aging duration corresponding to the first bearer to be in a failed state, and the aging duration is the same as the preset duration.
  • the offloading indication information includes a device identifier of the first UE, a gateway identifier of the edge gateway, and a bearer identifier of the first bearer.
  • the method may further include: the PGW sending the creation response information to the edge gateway, where the creation response information is used to indicate that the creation operation of the first bearer is performed successfully.
  • a processing device for a proprietary bearer stream comprising at least one module, at least one module for implementing the processing method of the proprietary bearer stream described in the first aspect above.
  • a processing device for a proprietary bearer stream comprising at least one module, at least one module for implementing the processing method of the proprietary bearer stream described in the second aspect above.
  • a processing device for a proprietary bearer stream which can be used for an edge gateway, and the processing device of the dedicated bearer stream includes: a processor, a memory, a network interface, and a bus.
  • the bus is used to connect the processor, memory and network interface.
  • the network interface is used to implement a communication connection between the edge gateway and the PGW.
  • the processor is configured to execute a program stored in the memory to implement the processing method of the proprietary bearer stream described in the first aspect.
  • a sixth aspect provides a computer readable storage medium having stored therein instructions for causing a computer to perform the proprietary bearer of the first aspect when the computer readable storage medium is run on a computer The processing method of the stream.
  • a computer program product comprising instructions for causing a computer to perform a method of processing a proprietary bearer stream of the first aspect when the computer program product is run on a computer is provided.
  • a processing device for a proprietary bearer stream which can be used in a PGW
  • the processing device of the proprietary bearer stream includes: a processor, a memory, a network interface, and a bus.
  • the bus is used to connect the processor, memory and network interface.
  • the network interface is used to implement a communication connection between the PGW and the edge gateway.
  • the processor is configured to execute a program stored in the memory to implement the processing method of the proprietary bearer stream described in the second aspect.
  • a computer readable storage medium storing instructions for causing a computer to perform the proprietary bearer of the second aspect when the computer readable storage medium is run on a computer The processing method of the stream.
  • a computer program product comprising instructions for causing a computer to perform a method of processing a proprietary bearer stream of the second aspect when the computer program product is run on a computer is provided.
  • a processing system for a proprietary bearer stream including an edge gateway and a PGW.
  • the edge gateway includes the processing device of the proprietary bearer stream described in the third aspect, and the PGW includes the processing device of the proprietary bearer stream according to the fourth aspect;
  • the edge gateway includes the processing device of the proprietary bearer stream described in the fifth aspect
  • the PGW includes the processing device of the proprietary bearer stream according to the eighth aspect.
  • the edge gateway receives the first bearer stream of the first UE, and sends the first bearer stream to the edge server if the first bearer used for transmitting the first bearer stream is a dedicated bearer and the first bearer stream needs to be offloaded. And sending the offloading indication information to the PGW, so that the PGW disables the timeout monitoring for the first bearer, and then the edge gateway starts the timeout monitoring for the first bearer, and implements the offloading of the dedicated bearer flow, which can better satisfy the user to the local
  • the need to share information meets the requirements of short-range communication services and ensures that services are handled normally.
  • the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer to meet the service requirement, if the QoS parameter of the first bearer stream is changed.
  • the edge gateway can also instruct the PGW to perform a release operation on the first bearer to achieve the effect of saving network resources, if the idle duration of the first bearer is up to a preset duration.
  • 1-1 is a schematic diagram of an implementation environment according to an embodiment of the present invention.
  • 1-2 is a flowchart of a method for processing a proprietary bearer stream according to an embodiment of the present invention
  • FIG. 2 is a flowchart of still another method for processing a proprietary bearer stream according to an embodiment of the present invention
  • FIG. 3 is a flowchart of another method for processing a proprietary bearer stream according to an embodiment of the present invention.
  • 4-1 is a schematic structural diagram of a processing apparatus for a proprietary bearer stream according to an embodiment of the present invention
  • 4-2 is a schematic structural diagram of another processing apparatus for a proprietary bearer stream according to an embodiment of the present invention.
  • 5-1 is a schematic structural diagram of another apparatus for processing a dedicated bearer stream according to an embodiment of the present invention.
  • FIG. 5-2 is a schematic structural diagram of another apparatus for processing a dedicated bearer stream according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a processing apparatus for a proprietary bearer stream according to an embodiment of the present invention.
  • FIG. 1-1 shows a schematic diagram of an implementation environment involved in various embodiments of the present application.
  • the implementation environment may be a 3GPP EPS, as shown in FIG. 1-1.
  • the implementation environment may include UE001, eNodeB 002, edge gateway 003, edge server 004, PGW005, and central server 006.
  • the UE 001 refers to a device that provides voice and/or data connectivity to the user.
  • the UE may be a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, and a user agent. , user equipment, subscriber stations, subscriber units, mobile terminal equipment or wireless terminal equipment.
  • the UE may be a mobile phone (or "cellular" phone), a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal) Digital Assistant, PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and mobile station in a future 5G network or a future evolved public land mobile network (Public) Terminal devices in the Land Mobile Network, PLMN).
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal digital assistant
  • handheld device with wireless communication capabilities computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and mobile station in a future 5G network or a future evolved public land mobile network (Public) Terminal devices in the Land Mobile Network, PLMN).
  • PLMN public land mobile network
  • the edge gateway 003 also known as the remote gateway, solves the problem of Multi-Access Edge Computing (MEC) of the short-range communication service (such as the vehicle-to-vehicle communication service) through the edge gateway: in the wireless access network close to the mobile user (
  • the Radio Access Network (RAN) network provides users with the ability to build information based on the Internet (IT) architecture and cloud computing.
  • the edge gateway can perform the offloading operation on the default bearer stream, which is usually to determine whether the Internet Protocol (IP) quintuple information of the default bearer stream conforms to the preset offloading rule, and the IP quintuple information of the default bearer stream matches.
  • IP Internet Protocol
  • the edge gateway transmits the default bearer stream to the edge server; if the IP quintuple information of the default bearer stream does not comply with the preset offloading rule, the edge gateway transmits the default bearer stream to the PGW.
  • the edge server 004 can be thought of as a cloud server running a specific task running on the edge of the mobile network.
  • the edge server can be a server, or a server cluster consisting of several servers, or a cloud computing service center.
  • the edge server is deployed in a flexible location. It can be deployed in a single base station, cloud wireless access network, and metropolitan area. It can also integrate third-party service servers.
  • PGW005 is the central gateway of EPC in 3GPP EPS, which is used to implement session management and bearer management, data forwarding, policy enforcement, and accounting.
  • An S18 interface is provided between the edge gateway and the PGW, and the S18 interface is used to complete signaling and data transmission between the edge gateway and the PGW.
  • the central server 006 can be a server, or a server cluster consisting of several servers, or a cloud computing service center.
  • the implementation environment may further include an MME, an SGW, a firewall, a PCRF device, and the like.
  • the SGW and the PGW can be combined, and the two can be implemented in one physical node.
  • the embodiments of the present invention are mainly described by using an edge gateway and a PGW as an example.
  • the edge gateway performs the offload matching operation only on the default bearer stream, and does not perform the offload matching operation on the dedicated bearer stream.
  • the edge gateway always transmits the proprietary bearer stream directly to the PGW, and the PGW then performs the dedicated bearer.
  • Streaming to the central server the central server belongs to the provincial server
  • the central server can then transmit the proprietary bearer stream to the edge server according to requirements.
  • the dedicated bearer stream has a long transmission path and many transmission nodes. The higher the delay, the better the user's need to share information locally, the inability to meet the requirements of the short-distance communication service, and the great waste of network resources.
  • the edge gateway can perform the offload matching operation on the dedicated bearer stream, and the edge gateway instructs the PGW after the dedicated bearer stream is shunted to ensure that the service is processed normally.
  • the timeout monitoring for the dedicated bearer used to transport the proprietary bearer stream is turned off, and then the edge gateway turns on timeout monitoring for the dedicated bearer.
  • Figure 1-2 shows a flow chart of a method for processing a proprietary bearer stream. As shown in Figure 1-2, the method includes:
  • Step 101 The edge gateway receives the first bearer stream of the first UE.
  • the first bearer stream may be sent by the first UE to the edge gateway through the base station, or may be sent by the network side, such as the PGW, to the edge gateway. That is, the processing method of the dedicated bearer stream can be applied to the scenario of uplink data transmission, and can also be applied to the scenario of downlink data transmission.
  • Step 102 The edge gateway sends the first bearer stream to the edge server to split the first bearer stream, where the first bearer stream is a dedicated bearer stream.
  • the edge gateway directly transmits the proprietary bearer stream to the edge server deployed on the edge gateway side. This shortens the transmission path of the proprietary bearer stream, reduces the number of transmission nodes, and reduces the transmission delay. The need for users to share information locally.
  • Step 103 The edge gateway sends the offloading indication information to the PGW.
  • the offloading indication information is used to instruct the PGW to close the timeout monitoring for the first bearer for transmitting the first bearer flow.
  • the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration.
  • the idle duration refers to the length of time when there is no proprietary bearer stream transmission.
  • Step 104 The PGW turns off timeout monitoring for the first bearer based on the offloading indication information.
  • Step 105 The PGW sends a close response message to the edge gateway.
  • the shutdown response information is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
  • Step 106 The edge gateway starts timeout monitoring for the first bearer when receiving the closing response information sent by the PGW.
  • the edge gateway starts the timeout monitoring for the first bearer and monitors the state of the first bearer. Therefore, the service can be processed normally to avoid service interruption or failure.
  • the method for processing a proprietary bearer stream is provided by the embodiment of the present invention.
  • the edge gateway receives the first bearer stream of the first UE, and sends the first bearer stream if the first bearer stream is a dedicated bearer stream.
  • To the edge server and send the offloading indication information to the PGW, so that the PGW disables the timeout monitoring for the first bearer, and then the edge gateway starts the timeout monitoring for the first bearer, and implements the offloading of the dedicated bearer flow, which can better It satisfies the user's need to share information locally, meets the requirements of short-distance communication services, and ensures that services are processed normally.
  • the edge gateway can also instruct the PGW to modify the Qos parameter of the corresponding dedicated bearer to meet the service requirement, if the QoS parameter of the dedicated bearer flow is changed.
  • the PGW is instructed to perform a release operation on the dedicated bearer to achieve the effect of saving network resources.
  • the edge gateway Ability to instruct the PGW to create a proprietary bearer.
  • the processing method of the dedicated bearer stream may include:
  • Step 201 The edge gateway receives the first bearer stream of the first UE.
  • the first bearer stream may be sent by the first UE to the edge gateway through the base station, or may be sent by the network side, such as the PGW, to the edge gateway. That is, the processing method of the dedicated bearer stream can be applied to the scenario of uplink data transmission, and can also be applied to the scenario of downlink data transmission.
  • Step 202 The edge gateway acquires a bearer identifier of the first bearer.
  • the first bearer is used to transmit the first bearer stream.
  • one UE corresponds to multiple dedicated bearers, and each dedicated bearer is used to transmit a dedicated bearer stream, and each dedicated bearer has a bearer identifier, and different bearer identifiers of different dedicated bearers in the multiple dedicated bearers are different.
  • the bearer identifier of the dedicated bearer can be represented by any one of 6-15.
  • the first UE corresponds to three dedicated bearers: CZ1, CZ2, and CZ3.
  • CZ1 is used to transmit the dedicated bearer stream CZL1, and the bearer identifier of CZ1 is 6;
  • CZ2 is used to transmit the dedicated bearer stream CZL2, and the bearer identifier of CZ2 is 7;
  • CZ3 is used to transmit the proprietary bearer stream CZL3, and the bearer of CZ3
  • the logo is 8.
  • the edge gateway may obtain the bearer identifier of the first bearer from the context information of the first UE.
  • the context information of the first UE is that the edge gateway sends the S18 interface session to the edge gateway.
  • Step 203 The edge gateway determines that the first bearer is a dedicated bearer if the bearer identifier of the first bearer belongs to the preset private bearer identifier set.
  • the preset private bearer identifier set includes the bearer identifier of the dedicated bearer.
  • the edge gateway may determine that the first bearer is a dedicated bearer, that is, the first bearer stream is a dedicated bearer stream.
  • the bearer identifier of the dedicated bearer may be represented by any one of 6 to 15, so in this step, the preset private bearer identifier set may be ⁇ 6, 7, 8, 9, 10, 11, 12, 13,14,15 ⁇ .
  • the first bearer stream of the first UE received by the edge gateway is CZL1
  • the first bearer is CZ1
  • the bearer identifier of the first bearer is 6, since 6 belongs to ⁇ 6, 7, 8, 9, 10, 11, 12 , 13, 14, 15 ⁇ , therefore, the edge gateway can determine that CZ1 is a proprietary bearer
  • CZL1 is a proprietary bearer stream.
  • Step 204 The edge gateway determines whether the IP quintuple information of the first bearer flow meets the second preset rule.
  • the first bearer stream carries IP quintuple information of the first bearer stream.
  • the IP quintuple information may include a source IP address, a source port, a destination IP address, a destination port, and protocol information.
  • the first bearer stream of the first UE received by the edge gateway is CZL1
  • the IP quintuple information of CZL1 is: 192.168.1.1 10000 TCP 121.14.88.7680, where 192.168.1.1 represents the source IP address. 10000 indicates the source port, TCP indicates the protocol information, 121.14.88.76 indicates the destination IP address, and 80 indicates the destination port.
  • the IP quintuple information is used to indicate that the first UE with the IP address of 192.168.1.1 is connected to the terminal with the port number of 80 through the port 10000 using TCP and the IP address of 121.14.88.76.
  • the second preset rule is used to determine whether the first bearer stream needs to be offloaded.
  • the second preset rule may include an address range of the destination IP address, a port range of the destination port, and protocol information.
  • the protocol information may be used to indicate a network layer protocol and a transport layer protocol of an Open System Interconnection (OSI) reference model, or an application layer protocol.
  • the network layer protocol can be an IP protocol, an ARP, or the like.
  • the transport layer protocol can be UDP, TCP, and the like.
  • the application layer protocol can be HTTP, FTP, SMTP, TELNET, NFS, and the like.
  • the edge gateway can determine whether the destination IP address in the IP quintuple information of the first bearer stream belongs to the address range of the destination IP address in the second preset rule, and whether the destination port in the IP quintuple information of the first bearer stream is The port range of the destination port in the second preset rule, and whether the protocol indicated by the protocol information in the IP quintuple information of the first bearer stream belongs to the protocol information in the second preset rule.
  • the destination IP address belongs to the address range of the destination IP address in the second preset rule
  • the destination port in the IP quintuple information of the first bearer stream belongs to the second preset rule.
  • the edge gateway determines that the IP quintuple information of the first bearer stream is consistent.
  • the second preset rule For example, the second preset rule is: 121.14.88.0 ⁇ 121.14.88.255, 10 ⁇ 100, IP, TCP. 121.14.88.0 ⁇ 121.14.88.255 is the address range of the destination IP address, and 10 to 100 are the port ranges of the destination port.
  • IP and TCP are protocol information. Assume that the IP address of the first bearer stream is 121.14.88.76, the destination port is 80, and the protocol indicated by the protocol information is TCP.
  • the edge gateway can determine that the IP quintuple information of the first bearer stream matches.
  • the second preset rule is: 121.14.88.0 ⁇ 121.14.88.255, 10 ⁇ 100, IP, TCP. 121.14.88.0 ⁇ 121.14.88.255 is the address range of the destination IP address, and 10 to 100 are the port ranges of the destination port.
  • IP and TCP are protocol information. Assume that
  • Step 205 The edge gateway determines that the first bearer flow needs to be offloaded if the IP quintuple information of the first bearer flow meets the second preset rule.
  • the edge gateway determines that the first bearer flow needs to be offloaded if the IP quintuple information of the first bearer flow meets the second preset rule; the IP quintuple information of the edge bearer in the first bearer flow is not If the second preset rule is met, it is determined that the first bearer stream does not need to be split.
  • the edge bearer sends the first bearer stream to the edge server to offload the first bearer stream.
  • the edge gateway performs a traffic distribution operation on the private bearer stream to better meet the requirements of the user for sharing information locally.
  • the edge gateway always transmits the proprietary bearer stream directly to the PGW, and the PGW transmits the dedicated bearer stream to the central server, and the central server then transmits the proprietary bearer stream according to requirements. It is transmitted to the edge server deployed on the edge gateway side, and the edge gateway cannot implement the offloading of the dedicated bearer stream.
  • the transmission path of the dedicated bearer stream is long, the number of transmission nodes is large, and the transmission delay is high, which cannot satisfactorily satisfy the user's need for local sharing information, and cannot meet the requirements of the short-distance communication service.
  • the edge gateway can directly transmit the proprietary bearer stream to the edge server deployed on the edge gateway side, thereby shortening the dedicated bearer stream.
  • the transmission path reduces the number of transmission nodes and reduces the transmission delay, which satisfies the user's need to share information locally, and truly solves the problem of MEC of short-distance communication service:
  • RAN network close to mobile users Provide users with IT-based and cloud-based capabilities to provide low-latency, high-bandwidth, and directly-obtainable real-time wireless network information (such as user location, base station load) for service developers and content providers The business environment of the company, so that the service provider can provide differentiated services and services to users.
  • Step 207 The edge gateway sends the offloading indication information to the PGW.
  • the offload indication information is used to instruct the PGW to turn off timeout monitoring for the first bearer.
  • the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration.
  • the preset duration can be 120 seconds.
  • the PGW in order to save the network resources, the PGW normally monitors whether the idle duration of the dedicated bearer reaches a preset duration based on the locally enabled timeout monitoring, and when the idle duration of the dedicated bearer is detected to reach the preset duration, The PGW performs a release operation on the dedicated bearer: releasing the resources occupied by the dedicated bearer.
  • the edge gateway after the edge gateway performs the offload operation on the dedicated bearer stream, since the private bearer stream no longer passes the PGW, if the PGW still monitors the idle duration of the dedicated bearer based on the local timeout monitoring, After the preset duration is reached, and the idle time of the dedicated bearer is monitored to reach the preset duration, the release operation is performed on the dedicated bearer, which may cause the proprietary bearer stream directly sent by the edge gateway to the edge server to be unsuccessful. The transmission causes the service to be unable to be processed normally, and the final service is interrupted or fails.
  • the edge gateway After the edge gateway performs the offloading operation on the dedicated bearer stream, the edge gateway sends the offloading indication information to the PGW, so that the PGW closes the current proprietary based on the offloading indication information, in order to ensure that the service is processed normally and the service is interrupted or failed.
  • the timeout monitoring of the bearer ie, the first bearer
  • the edge gateway turns on the timeout monitoring for the current dedicated bearer, thereby monitoring the state of the current proprietary bearer.
  • Step 208 The PGW turns off timeout monitoring for the first bearer based on the offloading indication information.
  • the offloading indication information sent by the edge gateway to the PGW may include a device identifier of the first UE, a gateway identifier of the edge gateway, and a bearer identifier of the first bearer.
  • the device identifier of the first UE, the gateway identifier of the edge gateway, and the bearer identifier of the first bearer may be used to uniquely identify the first bearer.
  • the PGW may close the timeout monitoring for the first bearer based on the device identifier of the first UE, the gateway identifier of the edge gateway, and the bearer identifier of the first bearer in the offloading indication information.
  • the device identifier of the UE may be an IP address of the UE.
  • each UE may be assigned a number, and the device identifier of the UE may also be the number of the corresponding UE.
  • the device identifier of the first UE is 001
  • the gateway identifier of the edge gateway is 01
  • the first bearer is CZ1 in step 202
  • the bearer identifier of CZ1 is 6
  • the shunt indication information sent by the edge gateway to the PGW may include the first The device identifier 001 of a UE, the gateway identifier 01 of the edge gateway, and the bearer identifier 6 of the CZ1.
  • the PGW turns off timeout monitoring for CZ1 based on the offload indication information.
  • step 208 can include:
  • the aging time corresponding to the first bearer in the PGW is in a failed state, and the aging time is the same as the preset duration in step 207.
  • one UE corresponds to multiple dedicated bearers, and each dedicated bearer has an aging time.
  • the aging time is used to monitor the status of the corresponding dedicated bearer.
  • the dedicated bearer if the idle duration of the dedicated bearer reaches the aging time, the dedicated bearer is released.
  • the first UE corresponds to three dedicated bearers: CZ1, CZ2, and CZ3, and Table 1 exemplarily shows the correspondence between the dedicated bearer and the aging duration.
  • the aging time corresponding to CZ1 is 120 seconds
  • the aging time corresponding to CZ2 is 130 seconds
  • the aging time corresponding to CZ3 is 110 seconds.
  • the PGW can control the aging duration (ie, 120 seconds) corresponding to CZ1 to be in a failed state.
  • Step 209 The PGW sends the close response information to the edge gateway.
  • the shutdown response information is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
  • the PGW generates the shutdown response information when the timeout monitoring for the first bearer is turned off, and sends the shutdown response information to the edge gateway.
  • the edge gateway determines that the PGW has turned off timeout monitoring for the first bearer, and then turns on timeout monitoring for the first bearer.
  • Step 210 The edge gateway starts timeout monitoring for the first bearer when receiving the closing response information sent by the PGW.
  • the edge gateway enables timeout monitoring for the first bearer so that the monitoring operation of the state of the first bearer is no longer performed by the PGW, but by the edge gateway. Since the edge of the first bearer is monitored by the edge gateway, the service can be processed normally to avoid service interruption or failure.
  • the edge gateway enables timeout monitoring for the first bearer, including:
  • the edge gateway sets the aging duration corresponding to the first bearer, and the aging duration is the same as the preset duration in step 207.
  • the edge gateway can set the aging duration corresponding to CZ1, that is, 120 seconds.
  • Step 211 The edge gateway sends the modification indication information to the PGW when detecting that the QoS parameter of the first bearer stream changes.
  • the modification indication information is used to indicate that the PGW modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer flow.
  • the 3GPP EPS can control the quality of the service provided by the dedicated bearer by controlling the QoS parameters of the dedicated bearer, such as the rate and delay packet loss rate.
  • the original Qos parameter of the proprietary bearer can be modified. , to achieve dynamic control of Qos parameters.
  • the first bearer stream of the first UE that is received by the edge gateway may carry the Qos parameter of the first bearer stream.
  • the edge gateway detects The QoS parameter of the first bearer stream is changed, and the edge gateway sends a modification indication information to the PGW to instruct the PGW to modify the QoS parameter of the first bearer to meet the service requirement, so as to provide a reliable QoS guarantee for the user, so that the user obtains The effect of a better business experience.
  • the Qos parameter may include a QoS Class Identifier (QCI), an Allocation and Retention Priority (ARP), a Guaranteed Bit Rate (GBR), and a Maximum Bit Rate (Maximum Bit). Rate, MBR) and other parameters.
  • QCI QoS Class Identifier
  • ARP Allocation and Retention Priority
  • GRR Guaranteed Bit Rate
  • MBR Maximum Bit Rate
  • Step 212 The PGW modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer stream based on the modification indication information.
  • the modification indication information sent by the edge gateway to the PGW may include a device identifier of the first UE, a bearer identifier of the first bearer, and a Qos parameter of the first bearer stream, where the Qos parameter of the first bearer stream is also That is, the result expected after modification.
  • the PGW may determine the first bearer based on the device identifier of the first UE and the bearer identifier of the first bearer in the modification indication information, and then modify the Qos parameter of the first bearer to the Qos parameter of the first bearer flow.
  • the step 212 may include the following steps:
  • the PGW sends an update bearer request to the MME.
  • the change bearer request carries the device identifier of the first UE in the modification indication information, the bearer identifier of the first bearer, and the Qos parameter of the first bearer stream.
  • the MME sends a bearer modify request and a session management request to the eNodeB.
  • the radio bearer modification request carries the device identifier of the first UE, the bearer identifier of the first bearer, and the Qos parameter of the first bearer stream.
  • the radio bearer modification request also carries non-access stratum (NAS) information that modifies the first bearer context request.
  • NAS non-access stratum
  • the eNodeB modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer stream, and then sends a Radio Resource Control (RRC) connection reconfiguration information (connection reconfiguration) to the first UE.
  • RRC Radio Resource Control
  • the first UE sends an RRC connection reconfiguration response message to the eNodeB.
  • the RRC connection reconfiguration response information is used to indicate that the RRC connection reconfiguration is complete.
  • the eNodeB After the radio resource and the S1 (the interface between the eNodeB and the SGW are successfully modified), the eNodeB sends a bearer modify response to the MME.
  • the first UE sends the modified first bearer context accepting information to the eNodeB by direct transfer, indicating that the first bearer is successfully modified.
  • the eNodeB sends a session management response to the MME.
  • the MME sends an update bearer response to the PGW.
  • the process of modifying the QoS parameters of the first bearer in the step 1) to the step 8) may be referred to the modification process of the QoS parameters of the dedicated bearer in the related art.
  • Step 213 The PGW sends the modification response information to the edge gateway.
  • the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
  • the PGW After the modification of the QoS parameter of the first bearer, the PGW sends a modification response message to the edge gateway to notify the edge gateway that the modification operation of the QoS parameter of the first bearer is successful.
  • Step 214 The edge gateway sends the release indication information to the PGW when the idle duration of the first bearer reaches a preset duration based on the timeout monitoring of the open time.
  • the release indication information is used to instruct the PGW to perform a release operation on the first bearer.
  • the edge gateway monitors that the idle duration of the first bearer reaches a preset duration based on the timeout monitoring, the edge gateway sends a release indication information to the PGW to instruct the PGW to perform a release operation on the first bearer: release (release Also known as deactivation) the resources occupied by the first bearer to achieve the effect of saving network resources.
  • the edge gateway detects that the idle time of CZ1 reaches 120 seconds, the edge gateway sends a release indication message to the PGW to instruct the PGW to perform a release operation on CZ1.
  • Step 215 The PGW performs a release operation on the first bearer based on the release indication information.
  • the release indication information sent by the edge gateway to the PGW may include the device identifier of the first UE and the bearer identifier of the first bearer.
  • the edge gateway may determine the first bearer based on the device identifier of the first UE and the bearer identifier of the first bearer in the release indication information, and perform a release operation on the first bearer.
  • step 215 can include the following steps:
  • the PGW sends a delete bearer request to the MME.
  • the delete bearer request carries the device identifier of the first UE and the bearer identifier of the first bearer in the release indication information.
  • the MME sends a deactivate bearer request to the eNodeB.
  • the release bearer request carries the device identifier of the first UE and the bearer identifier of the first bearer, and the release bearer request further carries the NAS information that releases the first bearer context request.
  • the eNodeB After receiving the release bearer request, the eNodeB starts the first bearer release procedure, and sends the RRC connection reconfiguration information to the first UE.
  • the RRC connection reconfiguration information includes releasing NAS information of the first bearer context request.
  • the first UE After receiving the NAS information in the RRC connection reconfiguration information, the first UE releases the resources of the first bearer, and then sends the RRC connection reconfiguration response information to the eNodeB.
  • the RRC connection reconfiguration response information is used to indicate that the first bearer is successfully released.
  • the eNodeB After receiving the RRC connection reconfiguration response information, the eNodeB sends a release bearer response information (deactive bearer response) to the MME.
  • the first UE After the RRC connection reconfiguration is completed, the first UE sends the first bearer context acceptance information to the eNodeB by direct transfer, indicating that the first bearer is successfully deleted.
  • the eNodeB sends a release of the first bearer context accept information to the MME, and notifies the MME that the release operation of the first bearer is completed.
  • the MME sends a delete bearer response message to the PGW to notify the PGW that the release operation of the first bearer is completed.
  • the release process of the first bearer in the step 1) to the step 10) may refer to the release process of the dedicated bearer in the related art, which is not described in detail in the embodiment of the present invention.
  • Step 216 The PGW sends release response information to the edge gateway.
  • the release response information is used to indicate whether the release operation is successful.
  • the edge gateway can perform a offload matching operation on the dedicated bearer stream, instructing the PGW to close the timeout monitoring for the dedicated bearer for transmitting the dedicated bearer stream, and then turning on
  • step 202 to step 205 are optional steps; by performing steps 211 to 213, the edge gateway can indicate the PGW when detecting that the Qos parameter of the dedicated bearer flow changes.
  • the QoS parameter of the dedicated bearer is modified to meet the service requirement.
  • the edge gateway can instruct the PGW to indicate the idle duration of the dedicated bearer to reach the preset duration. There are bearer execution release operations to save network resources.
  • the edge gateway receives the first bearer stream of the first UE, and the first bearer used for transmitting the first bearer stream is a dedicated bearer and the first If the bearer stream needs to be offloaded, the first bearer stream is sent to the edge server, and the offloading indication information is sent to the PGW, so that the PGW disables the timeout monitoring for the first bearer, and then the edge gateway turns on the timeout for the first bearer.
  • the monitoring implements the offloading of the dedicated bearer stream, which can better meet the user's need to share information locally, meet the requirements of the short-range communication service, and ensure that the service is processed normally.
  • the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer to meet the service requirement, if the QoS parameter of the first bearer stream is changed.
  • the edge gateway can also instruct the PGW to perform a release operation on the first bearer to achieve the effect of saving network resources, if the idle duration of the first bearer is up to a preset duration.
  • the first bearer stream is sent by the first UE to the edge gateway by using the base station.
  • the processing method of the dedicated bearer stream may include:
  • Step 301 The edge gateway receives a default bearer flow sent by the first UE forwarded by the base station.
  • the edge gateway may determine, according to the bearer identifier of the bearer flow, whether the bearer flow sent by the first UE forwarded by the base station is a default bearer flow. Generally, the bearer ID of the default bearer stream is 5.
  • Step 302 The edge gateway determines whether the IP quintuple information of the default bearer flow conforms to the first preset rule.
  • the default bearer stream carries IP quintuple information with the default bearer stream.
  • the IP quintuple information may include a source IP address, a source port, a destination IP address, a destination port, and protocol information.
  • the first preset rule is used to determine whether the default bearer flow needs to be offloaded.
  • the first preset rule may include an address range of the destination IP address, a port range of the destination port, and protocol information.
  • the protocol information may be used to indicate a network layer protocol and a transport layer protocol of the OSI reference model, or an application layer protocol.
  • the edge gateway can determine whether the destination IP address in the IP quintuple information of the default bearer flow belongs to the address range of the destination IP address in the first preset rule, and whether the destination port in the IP quintuple information of the default bearer flow belongs to the first preset. Indicates the port range of the destination port in the rule, and whether the protocol indicated by the protocol information in the IP quintuple information of the default bearer flow belongs to the protocol information in the first preset rule.
  • the destination IP address belongs to the address range of the destination IP address in the first preset rule
  • the destination port in the IP quintuple information of the default bearer flow belongs to the first preset rule.
  • the edge gateway determines that the IP quintuple information of the default bearer flow meets the A default rule.
  • Step 302 can refer to step 204.
  • Step 303 The edge gateway determines that the default bearer flow needs to be offloaded if the IP quintuple information of the default bearer flow meets the first preset rule.
  • the edge gateway determines that the default bearer flow needs to be offloaded if the IP quintuple information of the default bearer flow meets the first preset rule; the IP quintuple information of the default bearer flow does not meet the first preset. In the case of a rule, it is determined that the default bearer flow does not need to be offloaded.
  • Step 304 The edge gateway determines whether the IP quintuple information of the default bearer flow meets a pre-configured creation rule of the edge gateway.
  • the related technology initiates a process of creating a dedicated bearer, which may be initiated by the network side or by the UE.
  • the mode initiated by the network side is called the downlink creation mode
  • the mode initiated by the UE is called the uplink creation mode.
  • the uplink creation mode in order to initiate the process of creating a dedicated bearer, the default bearer flow for triggering the creation of the dedicated bearer needs to be transmitted to the PGW, so that the PGW performs the creation operation of the dedicated bearer based on the default bearer flow.
  • the edge gateway performs a traffic distribution matching operation on the default bearer flow.
  • the edge gateway determines whether the IP quintuple information of the default bearer flow conforms to the first preset rule, and the default bearer flow. If the IP quintuple information meets the first preset rule, the edge gateway sends the default bearer flow to the edge server to complete the offload operation on the default bearer flow; the IP quintuple information in the default bearer flow does not match the first In the case of a preset rule, the edge gateway sends the default bearer flow to the PGW, and the edge gateway does not perform the offload operation on the default bearer flow.
  • the edge gateway determines whether the default bearer flow is used to trigger the exclusive The bearer stream created by the bearer.
  • the edge gateway sends a creation indication message to the PGW to instruct the PGW to create a dedicated bearer.
  • the default bearer flow can be triggered by the edge gateway when the default bearer flow for triggering the creation of the dedicated bearer is triggered, so that the default bearer flow used for triggering the creation of the dedicated bearer is avoided by the edge gateway.
  • the shunting prevents the creation of a dedicated bearer from being triggered.
  • the edge gateway in order to determine that the default bearer flow is a bearer flow for triggering the creation of a dedicated bearer, the edge gateway may be pre-configured with a creation rule.
  • the creation rule may be a network layer protocol and a transport layer protocol of the OSI reference model, or an application layer protocol.
  • the network layer protocol may be IP, ARP, etc.
  • the transport layer protocol may be UDP, TCP, or the like.
  • the application layer protocol can be HTTP, FTP, SMTP, TELNET, NFS, and the like.
  • Step 305 The edge gateway determines that the default bearer flow is used to trigger the creation of the first bearer if the IP quintuple information of the default bearer flow meets the creation rule.
  • the first bearer is a proprietary bearer.
  • the edge gateway may determine that the default bearer flow is used to trigger the creation of the first bearer.
  • Step 306 The edge gateway sends the creation indication information to the PGW if the default bearer flow needs to be offloaded and the default bearer flow is used to trigger the creation of the first bearer.
  • the creation indication information is used to instruct the PGW to create the first bearer.
  • the edge gateway Based on the step 302 to the step 305, the edge gateway sends the creation indication information to the PGW to indicate that the PGW creates the first bearer, if the default bearer flow needs to be offloaded and the default bearer flow is used to trigger the creation of the first bearer.
  • the default bearer flow used to trigger the creation of the first bearer is triggered by the edge gateway, and the first bearer is triggered to be avoided. The traffic is split, and the creation of the first bearer cannot be triggered.
  • the edge gateway can send the creation indication information to the PGW through the S18 interface.
  • Step 307 The PGW creates a first bearer based on the creation indication information.
  • the creation indication information sent by the edge gateway to the PGW may include IP quintuple information of the default bearer flow, a transmission bandwidth required by the default bearer flow, and a Qos parameter of the default bearer flow.
  • the Qos parameter may include parameters such as QCI, ARP, GBR, and MBR.
  • Step 307 can include the following steps:
  • the PGW sends a create bearer request to the MME.
  • the create bearer request carries the IP quintuple information of the default bearer flow in the creation indication information, the transmission bandwidth required by the default bearer flow, and the Qos parameter of the default bearer flow.
  • the create bearer request also carries other parameters for creating the first bearer, such as a Traffic Flow Template (TFT), a Tunnel Endpoint Identifier (TEID), and the like.
  • TFT Traffic Flow Template
  • TEID Tunnel Endpoint Identifier
  • the MME sends a bearer setup request and a session management request to the eNodeB.
  • the bearer initiation request carries the IP quintuple information of the default bearer flow, the transmission bandwidth required by the default bearer flow, and the Qos parameter of the default bearer flow.
  • the eNodeB After receiving the bearer initiation request, the eNodeB starts the first bearer creation process, and sends the RRC connection reconfiguration information to the first UE.
  • the first UE sends an RRC connection reconfiguration response message to the eNodeB.
  • the eNodeB sends a bearer setup response to the MME.
  • the first UE sends the first bearer context accepting information to the eNodeB by direct transfer.
  • the eNodeB sends a session management response to the MME.
  • the MME sends a create bearer response to the PGW.
  • the process of creating the first bearer in the step 1) to the step 8) may refer to the process of creating a dedicated bearer in the PGW in the related art, which is not repeatedly described in the embodiment of the present invention.
  • Step 308 The PGW sends the creation response information to the edge gateway.
  • the creation response information is used to indicate that the creation operation of the first bearer is performed successfully.
  • Step 309 The edge gateway receives the first bearer stream sent by the first UE forwarded by the base station.
  • the edge gateway receives the first bearer stream sent by the first UE.
  • the first bearer is used to transmit the first bearer stream.
  • Step 310 The edge gateway sends the first bearer stream to the edge server to offload the first bearer stream if the first bearer stream needs to be offloaded.
  • Step 310 may include: determining, by the edge gateway, whether the IP quintuple information of the first bearer flow meets the second preset rule; and determining, by the edge gateway, that the IP quintuple information of the first bearer flow meets the second preset rule,
  • the edge gateway may refer to step 204 to step 205 in the foregoing embodiment, and details are not described herein again.
  • Step 311 The edge gateway sends the offloading indication information to the PGW.
  • the offload indication information is used to instruct the PGW to turn off timeout monitoring for the first bearer.
  • the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration.
  • Step 311 can refer to step 207.
  • Step 312 The PGW turns off timeout monitoring for the first bearer based on the offloading indication information.
  • step 312 can include:
  • the aging time corresponding to the first bearer is in a failed state, and the aging duration is the same as the preset duration in step 311.
  • Step 312 can refer to step 208.
  • Step 313 The PGW sends the close response information to the edge gateway.
  • the shutdown response information is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
  • Step 313 can refer to step 209.
  • Step 314 The edge gateway starts timeout monitoring for the first bearer when receiving the closing response information sent by the PGW.
  • the edge gateway enables timeout monitoring for the first bearer, including:
  • the edge gateway sets the aging duration corresponding to the first bearer, and the aging duration is the same as the preset duration in step 311.
  • Step 314 can refer to step 210.
  • Step 315 The edge gateway sends the modification indication information to the PGW when detecting that the QoS parameter of the first bearer flow changes.
  • the modification indication information is used to indicate that the PGW modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer flow.
  • Step 315 can refer to step 211.
  • Step 316 The PGW modifies the Qos parameter of the first bearer to the Qos parameter of the first bearer stream based on the modification indication information.
  • Step 316 can refer to step 212.
  • Step 317 The PGW sends the modification response information to the edge gateway.
  • the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
  • Step 317 can refer to step 213.
  • Step 318 The edge gateway sends the release indication information to the PGW if the idle duration of the first bearer reaches a preset duration based on the timeout monitoring of the open time.
  • the release indication information is used to instruct the PGW to perform a release operation on the first bearer.
  • Step 318 can refer to step 214.
  • Step 319 The PGW performs a release operation on the first bearer based on the release indication information.
  • Step 319 can refer to step 215.
  • Step 320 The PGW sends release response information to the edge gateway.
  • the release response information is used to indicate whether the release operation is successful.
  • the edge gateway can indicate the PGW if the default bearer flow for triggering the creation of the dedicated bearer is offloaded by the edge gateway and the creation of the dedicated bearer cannot be triggered.
  • Creating a dedicated bearer wherein step 308 is an optional step; by performing steps 309 to 314, the edge gateway can perform a split matching operation on the dedicated bearer stream, indicating that the PGW is closed for the proprietary transport stream The timeout monitoring of the bearer is performed, and then the timeout monitoring for the dedicated bearer is started.
  • the edge gateway can instruct the PGW to detect the dedicated bearer if the QoS parameter of the dedicated bearer flow is changed.
  • the QoS parameter is modified to meet the service requirement.
  • the edge gateway can instruct the PGW to perform the release operation on the private bearer after detecting that the idle duration of the dedicated bearer reaches a preset duration. To achieve the effect of saving network resources.
  • the method for processing a dedicated bearer stream is provided by the embodiment of the present invention.
  • the edge gateway can trigger the creation of the first bearer if the default bearer flow used to trigger the creation of the first bearer is offloaded by the edge gateway.
  • the creation of the first bearer cannot be triggered because the default bearer stream is offloaded by the edge gateway.
  • the edge gateway sends the first bearer stream to the edge server, and sends the offloading indication information to the PGW, so that the PGW disables the timeout monitoring for the first bearer.
  • the timeout monitoring of the first bearer implements the offloading of the dedicated bearer flow, which satisfies the user's need for local shared information, satisfies the requirements of the short-range communication service, and ensures that the service is processed normally.
  • the edge gateway can instruct the PGW to modify the QoS parameters of the first bearer to meet the service requirements.
  • the edge gateway can also instruct the PGW to perform a release operation on the first bearer to save network resources.
  • the embodiment of the present invention provides a processing device 400 for a dedicated bearer stream.
  • the device can be used in the edge gateway shown in Figure 1-1.
  • the device 400 includes:
  • the first receiving module 410 is configured to perform step 101, step 201 or step 309 in the above embodiment.
  • the first sending module 420 is configured to perform step 102, step 206 or step 310 in the above embodiment.
  • the second sending module 430 is configured to perform step 103, step 207 or step 311 in the foregoing embodiment.
  • the module 440 is configured to perform step 106, step 210 or step 314 in the above embodiment.
  • the second sending module 430 is further configured to perform step 214 or step 318 in the foregoing embodiment.
  • the apparatus 400 may further include: a second receiving module 450, configured to perform step 216 or step 320 in the foregoing embodiment.
  • the first receiving module 410 is configured to perform step 309 in the foregoing embodiment.
  • the first receiving module 410 is further configured to perform step 301 in the foregoing embodiment.
  • the second sending module 430 is further configured to perform step 306 in the foregoing embodiment.
  • the default bearer stream carries the IP quintuple information of the default bearer stream.
  • the apparatus 400 may further include:
  • the first determining module 460 is configured to perform step 302 in the foregoing embodiment.
  • the first determining module 470 is configured to perform step 303 in the foregoing embodiment.
  • the first determining module 460 is further configured to perform step 304 in the foregoing embodiment.
  • the first determining module 470 is further configured to perform step 305 in the foregoing embodiment.
  • the first bearer stream carries the QoS parameter of the first bearer stream.
  • the second sending module 430 is further configured to perform step 211 or step 315 in the foregoing embodiment.
  • the second receiving module 450 is further configured to perform step 213 or step 317 in the foregoing embodiment.
  • the opening module 440 is configured to: set an aging duration corresponding to the first bearer, where the aging duration is the same as the preset duration.
  • the first sending module 420 is configured to perform step 206 or step 310 in the foregoing embodiment.
  • the first bearer stream carries the IP quintuple information of the first bearer stream.
  • the apparatus 400 may further include:
  • the obtaining module 480 is configured to perform step 202 in the above embodiment.
  • the second determining module 490 is configured to perform step 203 in the foregoing embodiment.
  • the second determining module 491 is configured to perform step 204 in the foregoing embodiment.
  • the second determining module 490 is further configured to perform step 205 in the foregoing embodiment.
  • the second receiving module 450 is further configured to perform step 308 in the foregoing embodiment.
  • the edge gateway can trigger the creation of the first bearer if the default bearer flow used to trigger the creation of the first bearer is offloaded by the edge gateway.
  • the PGW is instructed to create a first bearer, so that the creation of the first bearer cannot be triggered because the default bearer flow is offloaded by the edge gateway. If the first bearer stream needs to be offloaded, the edge gateway sends the first bearer stream to the edge server, and sends the offloading indication information to the PGW, so that the PGW disables the timeout monitoring for the first bearer.
  • the timeout monitoring of the first bearer implements the offloading of the dedicated bearer flow, which satisfies the user's need for local shared information, satisfies the requirements of the short-range communication service, and ensures that the service is processed normally.
  • the edge gateway can instruct the PGW to modify the QoS parameters of the first bearer to meet the service requirements.
  • the edge gateway can also instruct the PGW to perform a release operation on the first bearer to save network resources.
  • the embodiment of the present invention provides another processing device 600 for a dedicated bearer stream.
  • the device can be used for the PGW shown in FIG. 1-1.
  • the device 600 includes:
  • the receiving module 610 is configured to perform step 207 or step 311 in the foregoing embodiment.
  • the closing module 620 is configured to perform step 104, step 208 or step 312 in the above embodiment.
  • the sending module 630 is configured to perform step 105, step 209 or step 313 in the above embodiment.
  • the receiving module 610 is further configured to perform step 214 or step 318 in the foregoing embodiment.
  • the apparatus 600 may further include: a release module 640, configured to perform step 215 or step 319 in the foregoing embodiment.
  • the sending module 630 is further configured to perform step 216 or step 320 in the foregoing embodiment.
  • the first bearer stream is sent by the first UE to the edge gateway by using the base station, and further, the receiving module 610 is further configured to perform step 306 in the foregoing embodiment.
  • the apparatus 600 may further include: a creating module 650, configured to perform step 307 in the foregoing embodiment.
  • the first bearer stream carries the QoS parameter of the first bearer stream.
  • the receiving module 610 is further configured to perform step 211 or step 315 in the foregoing embodiment.
  • the apparatus 600 may further include: a modification module 660, configured to perform step 212 or step 316 in the foregoing embodiment.
  • the sending module 630 is further configured to perform step 213 or step 317 in the foregoing embodiment.
  • the module 620 is closed for:
  • the aging duration corresponding to the first bearer is in a failed state, and the aging duration is the same as the preset duration.
  • the sending module 630 is further configured to perform step 308 in the foregoing embodiment.
  • the processing apparatus of the dedicated bearer stream provided by the embodiment of the present invention can be created under the direction of the edge gateway when the default bearer stream for triggering the creation of the first bearer is offloaded by the edge gateway.
  • a bearer prevents the first bearer from being created because the default bearer stream is offloaded by the edge gateway.
  • the PGW can turn off the timeout monitoring for the first bearer under the indication of the edge gateway, and then the edge gateway turns on the timeout monitoring for the first bearer, and implements the dedicated bearer flow.
  • the shunting can better meet the user's need to share information locally, meet the requirements of short-distance communication services, and ensure that services are processed normally.
  • the PGW can modify the QoS parameters of the first bearer under the direction of the edge gateway to meet the service requirements.
  • the PGW can also perform the release operation on the first bearer under the indication of the edge gateway to save network resources.
  • the embodiment of the invention further provides a processing system for a proprietary bearer stream, including an edge gateway and a PGW.
  • the edge gateway may include the processing device of the dedicated bearer stream shown in FIG. 4-1 or FIG. 4-2, and the PGW may include the processing device of the dedicated bearer stream shown in FIG. 5-1 or FIG. 5-2.
  • FIG. 6 is a schematic structural diagram of a processing apparatus 700 for a proprietary bearer stream according to an embodiment of the present invention.
  • the apparatus may be used in an edge gateway in the implementation environment shown in FIG. 1-1.
  • the apparatus 700 includes a processor 701 (such as a CPU), a memory 702, a network interface 703, and a bus 704.
  • the bus 704 is used to connect the processor 701, the memory 702, and the network interface 703.
  • the memory 702 may include a random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage.
  • the communication connection between the edge gateway and the PGW is implemented through the network interface 703 (which may be wired or wireless).
  • the program 702 is stored in the memory 702, and the program 7021 is used to implement various application functions, and the processor 701 is configured to execute the program 7021 stored in the memory 702 to cooperate with the processing method for implementing the dedicated bearer stream shown in FIG. 2 or FIG. .
  • the embodiment of the present invention further provides a processing device for a proprietary bearer stream, which can be used for the PGW in the implementation environment shown in FIG. 1-1.
  • the apparatus includes a processor (e.g., a CPU), a memory, a network interface, and a bus.
  • the bus is used to connect the processor, memory and network interface.
  • the memory may contain random access memory, and may also contain non-volatile memory, such as at least one disk storage.
  • the communication connection between the PGW and the edge gateway is implemented through a network interface (which may be wired or wireless).
  • a program is stored in the memory for implementing various application functions, and the processor is configured to execute a program stored in the memory to cooperate with a processing method for implementing the proprietary bearer stream shown in FIG. 2 or FIG.
  • the embodiment of the invention further provides a processing system for a proprietary bearer stream, including an edge gateway and a PGW.
  • the edge gateway may include the processing device of the dedicated bearer stream shown in FIG. 6, and the PGW may include the processing device of the dedicated bearer stream shown in FIG. 6.
  • the edge gateway and the PGW are used as device names, which are not limited to the device itself, that is, other devices having the same function are also within the protection scope of the present application.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product comprising one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a readable storage medium of a computer or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data
  • the center transmits to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium (eg, a solid state hard disk) or the like.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division.
  • there may be another division manner for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

L'invention appartient au domaine technique des communications, et concerne un procédé, un dispositif, et un système de traitement de flux de trafic support dédié. Dans le procédé, une passerelle frontière : reçoit un premier flux de trafic support d'un premier UE ; envoie le premier flux de trafic support à un serveur frontière, le premier flux de trafic support étant un flux de trafic support dédié, de sorte à dériver le premier flux de trafic support ; envoie des informations d'indication de dérivation à une PGW pour lui commander de désactiver une surveillance temporisée d'un premier support utilisé pour transmettre le premier flux de trafic support ; et active une surveillance temporisée du premier support, des informations de réponse de désactivation envoyées par la PGW étant reçues. La présente invention résout le problème lié, dans l'état de la technique, au fait que les exigences de partage d'informations locales d'un utilisateur ne peuvent pas être satisfaites car la dérivation d'un flux de trafic support dédié ne peut pas être exécutée. L'invention répond parfaitement aux exigences de partage d'informations locales d'un utilisateur ainsi qu'à l'exigence d'un service de communication en champ proche, et garantit un traitement normal du service. La présente invention est utilisée pour traiter un flux de porteuses dédiées.
PCT/CN2018/112626 2017-11-01 2018-10-30 Procédé, dispositif, et système de traitement de flux de trafic support dédié WO2019085888A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711057360.5A CN109756919B (zh) 2017-11-01 2017-11-01 专有承载流的处理方法、装置及系统
CN201711057360.5 2017-11-01

Publications (1)

Publication Number Publication Date
WO2019085888A1 true WO2019085888A1 (fr) 2019-05-09

Family

ID=66332443

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/112626 WO2019085888A1 (fr) 2017-11-01 2018-10-30 Procédé, dispositif, et système de traitement de flux de trafic support dédié

Country Status (2)

Country Link
CN (1) CN109756919B (fr)
WO (1) WO2019085888A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770477B (zh) * 2020-06-08 2024-01-30 中天通信技术有限公司 一种mec网络的保护资源的部署方法及相关装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425959A (zh) * 2007-10-29 2009-05-06 华为技术有限公司 一种承载处理方法和装置
CN102271405A (zh) * 2010-06-04 2011-12-07 中兴通讯股份有限公司 一种承载资源分配方法及装置
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
US20140334360A1 (en) * 2012-06-13 2014-11-13 All Purpose Networks LLC Baseband data transmission and reception in an lte wireless base station employing periodically scanning rf beam forming techniques
WO2016141143A1 (fr) * 2015-03-04 2016-09-09 Alcatel-Lucent Usa Inc. Système et procédé de mise en place d'une liaison à remplissage maximal via des services liés

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102300194B (zh) * 2010-06-22 2015-08-12 中兴通讯股份有限公司 一种传递分流信息的方法及装置、系统
US8787303B2 (en) * 2010-10-05 2014-07-22 Cisco Technology, Inc. Methods and apparatus for data traffic offloading at a router
WO2013078678A1 (fr) * 2011-12-02 2013-06-06 华为技术有限公司 Procédé pour déterminer un mode d'accès d'un équipement d'utilisateur, et système et dispositif correspondants
CN104639451B (zh) * 2013-11-14 2019-03-22 中兴通讯股份有限公司 数据流分流方法及控制器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425959A (zh) * 2007-10-29 2009-05-06 华为技术有限公司 一种承载处理方法和装置
CN102271405A (zh) * 2010-06-04 2011-12-07 中兴通讯股份有限公司 一种承载资源分配方法及装置
US20140334360A1 (en) * 2012-06-13 2014-11-13 All Purpose Networks LLC Baseband data transmission and reception in an lte wireless base station employing periodically scanning rf beam forming techniques
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
WO2016141143A1 (fr) * 2015-03-04 2016-09-09 Alcatel-Lucent Usa Inc. Système et procédé de mise en place d'une liaison à remplissage maximal via des services liés

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MOTOROLA: "CI -082510: Pseudo-CR on Separate ESM Messages for Default and Dedicated Bearers", 3GPP TSG CT WG1 MEETING #54, 27 June 2008 (2008-06-27), XP050029747 *
NOKIA NETWORKS: "R3-150981: Discussion on Bearer Type Indication for DC", 3GPP TSG-RAN WG3 MEETING #8 8, 29 May 2015 (2015-05-29), XP050968144 *

Also Published As

Publication number Publication date
CN109756919A (zh) 2019-05-14
CN109756919B (zh) 2021-02-26

Similar Documents

Publication Publication Date Title
RU2764259C1 (ru) Способ для активизации или деактивизации соединения плоскости пользователя в каждом сеансе
JP7040556B2 (ja) 方法、セッション管理機能ノード、ユーザプレーン機能ノード、ならびにセッション管理パラメータメンテナンス用ユーザ機器およびそのコンピュータ可読記録媒体
US11375396B2 (en) Session management method, interworking method, and network apparatus
US11153797B2 (en) Quality of service rule management in 5G
US9942748B2 (en) Service provisioning system and method, and mobile edge application server and support node
KR102267267B1 (ko) 세션 컨텍스트 변환
US10129802B2 (en) Layered connectivity in wireless systems
EP2717538B1 (fr) Procédé et système de communication, dispositif de réseau d'accès et serveur d'application
US9872213B2 (en) Methods and apparatus for wireless connection management
EP3001735B1 (fr) Procédé de délestage de service et station de base
CN107079372B (zh) 一种网络终端设备进行通信的方法及装置
EP3790314A1 (fr) Procédé et dispositif de communication
US11202338B2 (en) Session establishment method and apparatus
WO2018126547A1 (fr) Procédé de communication, dispositif associé et système
WO2016191963A1 (fr) Procédé pour l'établissement de porteuses, équipement d'utilisateur et station de base
WO2020233249A1 (fr) Procédé de transmission de paquets et appareil associé
WO2017219355A1 (fr) Procédé et dispositif de communications multi-connexion
WO2018170747A1 (fr) Procédé et appareil de communication
JP2016536814A (ja) 専用ベアラを用いるローカルａｎｄｓｆサーバへのアクセス
US20220116798A1 (en) Data transmission method, apparatus, and device
WO2018082070A1 (fr) Procédé de traitement de paquets de données, élément de réseau de plan de commande et élément de réseau de plan d'utilisateur
US20180255481A1 (en) Service flow transmission method and apparatus
WO2018141278A1 (fr) Procédé de communication sans fil, équipement utilisateur, équipement de réseau d'accès et système de réseau
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
WO2019085888A1 (fr) Procédé, dispositif, et système de traitement de flux de trafic support dédié

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

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

Country of ref document: EP

Kind code of ref document: A1