WO2019085888A1

WO2019085888A1 - Method, device and system for processing dedicated bearer flow

Info

Publication number: WO2019085888A1
Application number: PCT/CN2018/112626
Authority: WO
Inventors: 陈晓光
Original assignee: 华为技术有限公司
Priority date: 2017-11-01
Filing date: 2018-10-30
Publication date: 2019-05-09
Also published as: CN109756919A; CN109756919B

Abstract

Provided are a method, device and system for processing a dedicated bearer flow, falling within the field of communications. The method comprises: a border gateway receiving a first bearer flow of a first UE; sending the first bearer flow to a border server where the first bearer flow is a dedicated bearer flow, so as to shunt the first bearer flow; then, the border gateway sending shunting indication information to a PGW to instruct the PGW to turn off timeout monitoring for a first bearer used for transmitting the first bearer flow; and the border gateway turning on timeout monitoring for the first bearer where turn-off response information sent by the PGW is received. The present application solves the problem in the relevant art that a user's requirements for local information sharing cannot be greatly satisfied since the shunting of a dedicated bearer flow cannot be realized, can greatly satisfy the user's requirements for local information sharing and satisfy the requirement for a near-field communication service, and ensures that the service is normally processed. The present application is used for processing a dedicated bearer flow.

Description

Processing method, device and system for proprietary bearer flow

This application claims the priority of the Chinese patent application filed on November 1, 2017 by the State Intellectual Property Office of China, application number 201711057360.5, and the invention titled "Processing method, device and system for proprietary bearer flow". The citations are incorporated herein by reference.

Technical field

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.

Background technique

The 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS) 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. In EPC, services are provided by bearers, which are divided into default bearers and proprietary bearers. The default bearer is a user bearer that satisfies the data and signaling of the default Quality of Service (QoS). 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.

At present, users are increasingly demanding local information sharing. Most of the services are short-distance communication services, such as vehicle and bus communication services. In the related art, 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.

Summary of the invention

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. In the case of carrying a flow, the first bearer flow is sent to the edge server to offload the first bearer flow. After that, the edge gateway sends the offloading indication information to the PGW. When receiving the shutdown response information sent by 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.

In the present application, 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.

At the same time, 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.

Optionally, after the timeout monitoring for the first bearer is enabled, 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.

In the present application, 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.

Optionally, 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. Correspondingly, before 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. In the case that the default bearer stream needs to be offloaded and the default bearer stream is used to trigger the creation of the first bearer, 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.

Optionally, the default bearer flow carries the IP quintuple information of the default bearer flow. After receiving the default bearer flow sent by the first UE that is forwarded by the base station, 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.

In this application, in order to solve the problem that the uplink creation mode cannot trigger the creation of the dedicated 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.

Optionally, the first bearer stream carries the QoS parameter of the first bearer stream. After the timeout monitoring for the first bearer is enabled, the method may further include: the edge gateway detects that the QoS parameter of the first bearer stream changes. In the case, 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 then 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.

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.

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

Optionally, the rule is a network layer protocol and a transport layer protocol of the OSI reference model, or an application layer protocol.

For example, 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.

Optionally, if 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.

Optionally, the first bearer stream carries the IP quintuple information of the first bearer stream, and after receiving the first bearer stream of the first user equipment UE, 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.

For example, the bearer identifier of the dedicated bearer may be represented by any one of 6-15.

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

Optionally, after the sending the indication information to the PGW, 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.

In a second aspect, 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.

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. After monitoring, 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.

Optionally, after sending the shutdown response information to the edge gateway, 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.

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.

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

Optionally, the first bearer stream carries the QoS parameter of the first bearer stream, and after sending the close response information to the edge gateway, 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.

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

Optionally, after the first bearer is created based on the creation indication information, 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.

In a third aspect, a processing device for a proprietary bearer stream is provided, the device 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.

In a fourth aspect, a processing device for a proprietary bearer stream is provided, the device 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.

In a fifth aspect, a processing device for a proprietary bearer stream is provided, 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. Among them, 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.

In a seventh aspect, 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.

In an eighth aspect, a processing device for a proprietary bearer stream is provided, 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. Among them, 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.

According to a ninth 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.

In a tenth aspect, 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.

In an eleventh aspect, a processing system for a proprietary bearer stream is provided, 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;

Alternatively, the edge gateway includes the processing device of the proprietary bearer stream described in the fifth aspect, and the PGW includes the processing device of the proprietary bearer stream according to the eighth aspect.

The technical effects obtained by the third aspect, the fifth aspect, the sixth aspect, and the seventh aspect are similar to those obtained by the corresponding technical means in the first aspect, and are not described herein again.

The technical effects obtained by the fourth aspect, the eighth aspect, the ninth aspect, and the tenth aspect are similar to those obtained by the corresponding technical means in the second aspect, and are not described herein again.

The beneficial effects brought by the technical solutions provided by the present application are:

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.

DRAWINGS

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;

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.

Detailed ways

In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

Please refer to FIG. 1-1, which 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. For example, 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).

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. At present, 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. In the case of a preset offloading rule, 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.

Further, the implementation environment may further include an MME, an SGW, a firewall, a PCRF device, and the like. Wherein, 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.

In the related art, 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. Obviously, 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.

In the processing method of the dedicated bearer stream provided by the embodiment, 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.

In summary, 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.

Further, in the first implementation manner, 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. In the case that the idle duration of the dedicated bearer is monitored to reach a preset duration, the PGW is instructed to perform a release operation on the dedicated bearer to achieve the effect of saving network resources.

In the second implementation manner, when the default bearer flow used to trigger the creation of the dedicated bearer is offloaded by the edge gateway, and the creation of the dedicated bearer cannot be triggered, thereby causing the PGW to fail to create a dedicated bearer, the edge gateway Ability to instruct the PGW to create a proprietary bearer. The following describes the processing method of the dedicated bearer stream provided by the embodiment of the present invention by taking the two implementations as an example.

In the first implementation manner, as shown in FIG. 2, the processing method of the dedicated bearer stream may include:

Step 201: The edge gateway receives the first bearer stream of the first UE.

Step 202: The edge gateway acquires a bearer identifier of the first bearer.

The first bearer is used to transmit the first bearer stream.

Generally, 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. For example, 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.

Optionally, 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. For the acquisition process of the context information of the first UE and the content of the context information of the first UE, refer to the related art, and details are not described herein again.

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. In the case that the bearer identifier of the first bearer belongs to the preset private bearer identifier set, 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}. For example, the first bearer stream of the first UE received by the edge gateway is CZL1, the first bearer is CZ1, and 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, and 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. For example, in step 201, the first bearer stream of the first UE received by the edge gateway is CZL1, and 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. Optionally, 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.

For example, 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. In the IP quintuple information of the first bearer stream, the destination IP address belongs to the address range of the destination IP address in the second preset rule, and the destination port in the IP quintuple information of the first bearer stream belongs to the second preset rule. In the case of the port range of the port, and 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 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.

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.

Based on step 204, 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.

In the case that the first bearer is a dedicated bearer and the first bearer stream needs to be offloaded, the edge bearer sends the first bearer stream to the edge server to offload the first bearer stream.

In this step, 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.

For the short-range communication service, in the related art, 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. Obviously, in this processing mode, 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. In addition, in the embodiment of the present invention, 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. For example, the preset duration can be 120 seconds.

In the related art, 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.

In the embodiment of the present invention, 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. Therefore, 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), and then 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.

Optionally, in step 207, 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. In addition, each UE may be assigned a number, and the device identifier of the UE may also be the number of the corresponding UE.

For example, 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, and 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.

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

As described in step 202, generally, 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. For each dedicated bearer, if the idle duration of the dedicated bearer reaches the aging time, the dedicated bearer is released. For example, 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, and the aging time corresponding to CZ3 is 110 seconds. When the idle time of CZ1 reaches 120 seconds, CZ1 will be released; when CZ2 idle time reaches 130 seconds, CZ2 will be released; when CZ3 idle time reaches 110 seconds, CZ3 will be released. .

In this step, it is assumed that the first bearer is CZ1. In order to turn off the timeout monitoring for CZ1, the PGW can control the aging duration (ie, 120 seconds) corresponding to CZ1 to be in a failed state.

Table 1

专有承载Proprietary bearer	老化时长(单位：秒)Aging time (unit: second)
CZ1CZ1	120120
CZ2CZ2	130130
CZ3CZ3	110110

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. Upon receiving the shutdown response information, 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.

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

Assume that the first bearer is CZ1 in step 208. In order to enable timeout monitoring for CZ1, 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.

In the related art, 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. For example, the original Qos parameter of the proprietary bearer can be modified. , to achieve dynamic control of Qos parameters. Generally, in the case of dynamic changes in transmission data, it is necessary to modify the original Qos parameters of the dedicated bearer.

In the embodiment of the present invention, optionally, in step 201, 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. In this step, if 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.

For example, 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. For a description of each parameter, reference can be made to related art.

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.

Optionally, in step 211, 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:

1) 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.

2) 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.

3) 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.

4) 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.

5) 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.

6) 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.

7) The eNodeB sends a session management response to the MME.

8) 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.

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.

In this step, if 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.

Assume that the first bearer is CZ1 in step 208, and the preset duration is 120 seconds. When 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.

Optionally, in step 214, 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.

Wherein, step 215 can include the following steps:

1) 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.

2) 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.

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.

4) 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.

5) After receiving the RRC connection reconfiguration response information, the eNodeB sends a release bearer response information (deactive bearer response) to the MME.

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.

7) 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.

8) 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.

In the embodiment of the present invention, by performing step 201 to step 210, 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 For the timeout monitoring of the dedicated bearer, 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. By performing step 214 to step 216, 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.

In summary, 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 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.

In a second implementation manner, the first bearer stream is sent by the first UE to the edge gateway by using the base station. For example, as shown in FIG. 3, 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. Optionally, 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.

For example, in the IP quintuple information of the default bearer flow, the destination IP address belongs to the address range of the destination IP address in the first preset rule, and the destination port in the IP quintuple information of the default bearer flow belongs to the first preset rule. In the case of the port range of the destination port, and 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 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.

Based on step 302, 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.

It should be noted that after the related technology is created, 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, and the mode initiated by the UE is called the uplink creation mode. In 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. However, because the default bearer flow passes through the edge gateway, the edge gateway performs a traffic distribution matching operation on the default bearer flow. For example, 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. Therefore, while the IP quintuple information of the default bearer flow conforms to the first preset rule, if the default bearer flow is another bearer flow for triggering the creation of the dedicated bearer, the default bearer flow is not sent. To the PGW, the PGW cannot perform the creation of a dedicated bearer. In order to solve this problem, in the embodiment of the present invention, if the IP quintuple information of the default bearer flow conforms to the first preset rule, the edge gateway further determines whether the default bearer flow is used to trigger the exclusive The bearer stream created by the bearer. In the case that the default bearer flow is a bearer flow for triggering the creation of a dedicated bearer, the edge gateway sends a creation indication message to the PGW to instruct the PGW to create a dedicated bearer. In this way, 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.

Optionally, in the embodiment of the present invention, 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. For example, 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., and 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.

For example, if the protocol indicated by the protocol information in the IP quintuple information of the default bearer stream is TCP, and the creation rules are IP and TCP, 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.

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. In this case, 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.

In this step, 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.

Optionally, in step 306, 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:

1) 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.

2) 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.

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.

5) The eNodeB sends a bearer setup response to the MME.

6) The first UE sends the first bearer context accepting information to the eNodeB by direct transfer.

7) The eNodeB sends a session management response to the MME.

8) 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.

After the PGW creates the first bearer, 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 first bearer stream needs to be split. For the process of determining that the first bearer stream needs to be split, 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.

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

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

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.

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.

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.

In the embodiment of the present invention, by performing steps 301 to 308, 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. By performing steps 315 to 317, 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. By performing step 318 to step 320, 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.

In summary, 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. 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.

It should be noted that the sequence of the steps of the processing method of the dedicated bearer stream provided by the embodiment of the present invention may be appropriately adjusted, and the steps may also be correspondingly increased or decreased according to the situation, which is disclosed by those skilled in the art. Within the technical scope, methods that can be easily conceived are included in the scope of protection of the present application, and therefore will not be described again.

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. As shown in Figure 4-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.

Further, the second sending module 430 is further configured to perform step 214 or step 318 in the foregoing embodiment.

As shown in FIG. 4-2, the apparatus 400 may further include: a second receiving module 450, configured to perform step 216 or step 320 in the foregoing embodiment.

Optionally, the first receiving module 410 is configured to perform step 309 in the foregoing embodiment. Correspondingly, 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.

Optionally, the default bearer stream carries the IP quintuple information of the default bearer stream. Further, as shown in FIG. 4-2, 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.

Optionally, the first bearer stream carries the QoS parameter of the first bearer stream. Further, 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.

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

Optionally, the first sending module 420 is configured to perform step 206 or step 310 in the foregoing embodiment.

Optionally, the first bearer stream carries the IP quintuple information of the first bearer stream. Further, as shown in FIG. 4-2, 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.

Further, the second receiving module 450 is further configured to perform step 308 in the foregoing embodiment.

The meanings of other marks in Figure 4-2 can be referred to Figure 4-1.

In summary, the processing apparatus of the dedicated bearer stream 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 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. As shown in FIG. 5-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.

Further, the receiving module 610 is further configured to perform step 214 or step 318 in the foregoing embodiment.

As shown in FIG. 5-2, 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.

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

As shown in FIG. 5-2, the apparatus 600 may further include: a creating module 650, configured to perform step 307 in the foregoing embodiment.

Optionally, the first bearer stream carries the QoS parameter of the first bearer stream. Further, the receiving module 610 is further configured to perform step 211 or step 315 in the foregoing embodiment.

As shown in FIG. 5-2, 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.

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

Further, the sending module 630 is further configured to perform step 308 in the foregoing embodiment.

The meanings of other marks in Figure 5-2 can be referred to Figure 5-1.

In summary, 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. After the edge gateway sends the first bearer stream to the edge server, 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. As shown in FIG. 6, 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. Referring to Figure 6, the apparatus includes a processor (e.g., a CPU), a memory, a network interface, and a bus. Among them, 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 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.

It should be noted that, in the device embodiment provided by the present application, 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.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the module described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product comprising one or more computer 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.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, 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. In addition, 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.

The above description is only an optional embodiment of the present application, and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application are included in the protection of the present application. Within the scope.

Claims

A method for processing a proprietary bearer stream, the method comprising:

Receiving a first bearer flow of the first user equipment UE;

Transmitting the first bearer stream to an edge server, where the first bearer stream is a dedicated bearer stream, to offload the first bearer stream;

Sending offloading indication information to the packet data network gateway (PGW), the offloading indication information is used to instruct the PGW to turn off timeout monitoring for the first bearer for transmitting the first bearer flow, and the timeout monitoring is used to monitor the Whether the idle duration of the first bearer reaches a preset duration;

After receiving the shutdown response information sent by the PGW, the timeout monitoring for the first bearer is turned on, and the shutdown response information is used to indicate that the PGW has turned off timeout monitoring for the first bearer.
The method according to claim 1, wherein after the opening time monitoring for the first bearer is performed, the method further comprises:

And transmitting, in the case that the idle duration of the first bearer reaches the preset duration, based on the timeout monitoring, the release indication information is sent to the PGW, where the release indication information is used to indicate the PGW to the first a bearer performs a release operation;

Receiving release response information sent by the PGW, the release response information is used to indicate whether the release operation is successful.
The method according to claim 1 or 2, wherein the receiving the first bearer stream of the first user equipment UE comprises:

Receiving, by the base station, the first bearer stream sent by the first UE;

Before the receiving the first bearer stream sent by the first UE that is forwarded by the base station, the method further includes:

Receiving, by the base station, a default bearer flow sent by the first UE;

And in the case that the default bearer stream needs to be offloaded, and the default bearer stream is used to trigger the creation of the first bearer, the creation indication information is sent to the PGW, where the creation indication information is used to indicate the PGW creation Said the first bearer.
The method according to claim 3, wherein the default bearer stream carries Internet IP quintuple information of the default bearer stream, and is sent by the first UE that is forwarded by the base station. After the default bearer stream, the method further includes:

Determining whether the IP quintuple information of the default bearer flow meets the first preset rule;

And determining, in the case that the IP quintuple information of the default bearer flow meets the first preset rule, that the default bearer flow needs to be offloaded;

Determining whether the IP quintuple information of the default bearer flow meets a pre-configured creation rule of the edge gateway;

And determining, in the case that the IP quintuple information of the default bearer stream meets the creation rule, the default bearer flow is used to trigger the creation of the first bearer.
The method according to claim 1 or 2, wherein the first bearer stream carries a quality of service Qos parameter of the first bearer stream, after the timeout monitoring for the first bearer is started, The method further includes:

And detecting, in the case that the QoS parameter of the first bearer stream is changed, sending the modification indication information to the PGW, where the modification indication information is used to indicate that the PGW modifies the Qos parameter of the first bearer to Describe the Qos parameter of the first bearer stream;

And receiving the modification response information sent by the PGW, where the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
The method according to claim 1 or 2, wherein the enabling timeout monitoring for the first bearer comprises:

And setting an aging duration corresponding to the first bearer, where the aging duration is the same as the preset duration.
The method according to claim 4, wherein the creation rule is a network layer protocol and a transport layer protocol of an open system interconnection OSI reference model, or an application layer protocol.
The method according to claim 1 or 2, wherein the sending the first bearer stream to the edge server if the first bearer stream is a private bearer stream comprises:

And in a case that the first bearer is a dedicated bearer and the first bearer stream needs to be offloaded, the first bearer stream is sent to the edge server.
The method according to claim 8, wherein the first bearer stream carries IP quintuple information of the first bearer stream, after the receiving the first bearer stream of the first user equipment UE, The method further includes:

Obtaining a bearer identifier of the first bearer;

And determining, in the case that the bearer identifier of the first bearer belongs to the preset private bearer identifier set, the first bearer is a dedicated bearer, and the preset private bearer identifier set includes a bearer identifier of the dedicated bearer;

Determining whether the IP quintuple information of the first bearer stream meets the second preset rule;

And determining, in the case that the IP quintuple information of the first bearer stream meets the second preset rule, that the first bearer flow needs to be offloaded.
Method according to claim 1 or 2, characterized in that

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 according to claim 3, wherein after the sending the creation indication information to the PGW, the method further comprises:

And 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 proprietary bearer stream, the method comprising:

Receiving the offloading indication information sent by the edge gateway, where the offloading indication information is generated by the edge gateway sending the first bearer stream of the first user equipment UE to the edge server;

And performing the timeout monitoring for the first bearer according to the offloading indication information, where the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration, where the first bearer is used to transmit the first bearer flow. ;

And sending the shutdown response information to the edge gateway, where the shutdown response information is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
The method according to claim 12, after the sending the close response information to the edge gateway, the method further includes:

Receiving the release indication information sent by the edge gateway, where the release indication information is generated by the edge gateway when the idle duration of the first bearer reaches the preset duration according to the open timeout monitoring;

Performing a release operation on the first bearer based on the release indication information;

Sending release response information to the edge gateway, the release response information being used to indicate whether the release operation is successful.
The method according to claim 12 or 13, wherein the first bearer stream is sent by the first UE to the edge gateway by using a base station, before the offloading indication information sent by the receiving edge gateway, The method further includes:

Receiving creation instruction information sent by the edge gateway;

Creating the first bearer based on the creation indication information;

The creation indication information is generated by the edge gateway when it is detected that the default bearer flow needs to be offloaded, and the default bearer flow is used to trigger the creation of the first bearer, where the default bearer flow is The first UE is sent to the edge gateway by the base station.
The method according to claim 12 or 13, wherein the first bearer stream carries a quality of service Qos parameter of the first bearer stream, after the sending the close response information to the edge gateway, The method also includes:

Receiving the modification indication information sent by the edge gateway, where the modification indication information is generated by the edge gateway when detecting that the Qos parameter of the first bearer flow changes;

Modifying, according to the modification indication information, the Qos parameter of the first bearer to a Qos parameter of the first bearer stream;

The modification response information is sent to the edge gateway, where the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
The method according to claim 12 or 13, wherein the closing the timeout monitoring for the first bearer based on the offloading indication information comprises:

The aging duration corresponding to the first bearer is in a failed state, and the aging duration is the same as the preset duration.
Method according to claim 12 or 13, characterized in that

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 according to claim 14, wherein after the creating the first bearer based on the creation indication information, the method further comprises:

The creation response information is sent to the edge gateway, where the creation response information is used to indicate that the creation operation of the first bearer is successful.
A processing device for a proprietary carrier stream, characterized in that the device comprises:

a first receiving module, configured to receive a first bearer stream of the first user equipment UE;

a first sending module, configured to send the first bearer stream to an edge server, where the first bearer stream is a dedicated bearer stream, to offload the first bearer stream;

a second sending module, configured to send the offloading indication information to the packet data network gateway (PGW), where the offloading indication information is used to instruct the PGW to turn off 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;

And the opening module is configured to enable timeout monitoring for the first bearer, where the closing response information is used to indicate that the PGW is turned off for the first bearer, when receiving the shutdown response information sent by the PGW Timeout monitoring.
The device according to claim 19, characterized in that

The second sending module is further configured to send release indication information, the release indication information, to the PGW, if the idle duration of the first bearer reaches the preset duration, And configured to instruct the PGW to perform a release operation on the first bearer;

The device also includes:

And a second receiving module, configured to receive release response information sent by the PGW, where the release response information is used to indicate whether the release operation is successful.
The device according to claim 19 or 20, wherein the first receiving module is configured to:

Receiving, by the base station, the first bearer stream sent by the first UE;

The first receiving module is further configured to receive a default bearer flow sent by the first UE that is forwarded by the base station;

The second sending module is further configured to: when the default bearer flow needs to be offloaded, and the default bearer flow is used to trigger the creation of the first bearer, send the creation indication information to the PGW, where the The indication information is used to instruct the PGW to create the first bearer.
The device according to claim 21, wherein the default bearer stream carries Internet IP quintuple information of the default bearer stream, and the device further includes:

The first determining module is configured to determine whether the IP quintuple information of the default bearer flow meets the first preset rule;

a first determining module, configured to determine 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 first determining module is further configured to determine whether the IP quintuple information of the default bearer flow meets a pre-configured creation rule of the edge gateway;

The first determining module is further configured to: when the IP quintuple information of the default bearer flow meets the creation rule, determine that the default bearer flow is used to trigger the creation of the first bearer.
The apparatus according to claim 19 or 20, wherein the first bearer stream carries a quality of service Qos parameter of the first bearer stream,

The second sending module is further configured to: when the QoS parameter of the first bearer stream is changed, send the modification indication information to the PGW, where the modification indication information is used to indicate that the PGW is to be The QoS parameter of the first bearer is modified to the Qos parameter of the first bearer stream;

The second receiving module is further configured to receive the modification response information sent by the PGW, where the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
The device according to claim 19 or 20, wherein the opening module is configured to:

And setting an aging duration corresponding to the first bearer, where the aging duration is the same as the preset duration.
The apparatus according to claim 22, wherein the creation rule is a network layer protocol and a transport layer protocol of an open system interconnection OSI reference model, or an application layer protocol.
The device according to claim 19 or 20, wherein the first sending module is configured to:

And in a case that the first bearer is a dedicated bearer and the first bearer stream needs to be offloaded, the first bearer stream is sent to the edge server.
The device according to claim 26, wherein the first bearer stream carries IP quintuple information of the first bearer stream, and the device further includes:

An obtaining module, configured to acquire a bearer identifier of the first bearer;

a second determining module, configured to: when the bearer identifier of the first bearer belongs to a preset dedicated bearer identifier set, determine that the first bearer is a dedicated bearer, and the preset dedicated bearer identifier set includes a special Bearer ID of the bearer;

a second determining module, configured to determine whether the IP quintuple information of the first bearer stream meets a second preset rule;

The second determining module is configured to determine that the first bearer flow needs to be offloaded if the IP quintuple information of the first bearer flow meets the second preset rule.
Device according to claim 19 or 20, characterized in that

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 device according to claim 21, wherein

The second receiving module is further configured to receive 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 processing device for a proprietary carrier stream, characterized in that the device comprises:

a receiving module, configured to receive the offloading indication information sent by the edge gateway, where the offloading indication information is generated by the edge gateway sending the first bearer stream of the first user equipment UE to the edge server;

And the closing module is configured to close the timeout monitoring for the first bearer according to the offloading indication information, where the timeout monitoring is used to monitor whether the idle duration of the first bearer reaches a preset duration, where the first bearer is used for the transmission Describe the first bearer stream;

And a sending module, configured to send the shutdown response information to the edge gateway, where the shutdown response information is used to instruct the edge gateway to enable timeout monitoring for the first bearer.
The device of claim 30 wherein:

The receiving module is further configured to receive the release indication information that is sent by the edge gateway, where the release indication information is that the edge gateway detects that the idle time of the first bearer reaches the preset according to the timeout monitoring based on the timeout. Generated in the case of duration;

The device also includes:

a release module, configured to perform a release operation on the first bearer based on the release indication information;

The sending module is further configured to send release response information to the edge gateway, where the release response information is used to indicate whether the release operation is successful.
The apparatus according to claim 30 or 31, wherein the first bearer stream is sent by the first UE to the edge gateway via a base station,

The receiving module is further configured to receive creation indication information sent by the edge gateway;

The device also includes:

a creating module, configured to create the first bearer based on the creation indication information;

The creation indication information is generated by the edge gateway when it is detected that the default bearer flow needs to be offloaded, and the default bearer flow is used to trigger the creation of the first bearer, where the default bearer flow is The first UE is sent to the edge gateway by the base station.
The apparatus according to claim 30 or 31, wherein the first bearer stream carries a quality of service Qos parameter of the first bearer stream,

The receiving module is further configured to receive the modification indication information sent by the edge gateway, where the modification indication information is generated by the edge gateway when detecting that the Qos parameter of the first bearer flow changes;

The device also includes:

a modifying module, configured to modify a Qos parameter of the first bearer to a Qos parameter of the first bearer stream according to the modification indication information;

The sending module is further configured to send the modification response information to the edge gateway, where the modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer is performed successfully.
The device according to claim 30 or 31, wherein the shutdown module is configured to:

The aging duration corresponding to the first bearer is in a failed state, and the aging duration is the same as the preset duration.
A device according to claim 30 or 31, wherein

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 device of claim 32, wherein

The sending module is further configured to send 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 system for a proprietary bearer stream, comprising: an edge gateway and a PGW,

The edge gateway includes the processing device of the proprietary bearer stream of any one of claims 19 to 29;

The PGW comprises a processing device for a proprietary carrier stream according to any of claims 30 to 36.
A processing device for a proprietary bearer stream, the device comprising: a processor, a memory, a network interface, and a bus, the bus being configured to connect the processor, the memory, and the network interface;

The network interface is configured to implement a communication connection between the edge gateway and the PGW;

The processor is configured to execute a program stored in a memory to implement the processing method of the proprietary bearer stream according to any one of claims 1 to 11, or the processing method of the proprietary bearer stream according to any one of claims 12 to 18.
A computer readable storage medium, wherein the computer readable storage medium stores instructions for causing the computer to perform any of claims 1 to 11 when the computer readable storage medium is run on a computer A method of processing a proprietary bearer stream, or a method of processing a proprietary bearer stream as claimed in any one of claims 12 to 18.
A computer program product comprising instructions, wherein when the computer program product is run on a computer, causing the computer to perform the processing method of the proprietary bearer stream of any one of claims 1 to 11, or claim 12 A method of processing a proprietary bearer stream as described in any of 18.