CN109756919B

CN109756919B - Method, device and system for processing proprietary bearer stream

Info

Publication number: CN109756919B
Application number: CN201711057360.5A
Authority: CN
Inventors: 陈晓光
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2017-11-01
Filing date: 2017-11-01
Publication date: 2021-02-26
Anticipated expiration: 2037-11-01
Also published as: WO2019085888A1; CN109756919A

Abstract

The application provides a processing method, a device and a system of a proprietary bearer stream, and belongs to the field of communication. The method comprises the following steps: the method comprises the steps that an edge gateway receives a first bearer flow of first UE, the first bearer flow is sent to an edge server under the condition that the first bearer flow is a proprietary bearer flow so as to shunt the first bearer flow, then the edge gateway sends shunting indication information to a PGW so as to indicate the PGW to close overtime monitoring aiming at the first bearer for transmitting the first bearer flow, and the edge gateway opens overtime monitoring aiming at the first bearer under the condition that closing response information sent by the PGW is received. The method and the device solve the problem that the requirement of the user for local information sharing cannot be well met due to the fact that the distribution of the proprietary bearer flow cannot be achieved in the related technology, can well meet the requirement of the user for local information sharing, meet the requirement of near field communication services, and ensure that the services are normally processed. The present application is for processing a proprietary bearer stream.

Description

Method, device and system for processing proprietary bearer stream

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 dedicated bearer stream.

Background

The 3rd Generation Partnership Project (3 GPP) Evolved Packet System (EPS) includes an Evolved Packet Core (EPC), an edge Gateway, a base station (eNodeB), and a 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 Rules Function (PCRF) device, and the like. In EPC, traffic is provided by bearers (bearer), which are divided into default bearers and proprietary bearers. A default bearer is a user bearer for data and signaling that satisfies a default Quality of Service (QoS), which may be understood as a bearer that provides best effort connections. The dedicated bearer is a bearer that can meet the requirement of a user for a specific QoS and is suitable for a specific service (e.g., a Voice over Long Term Evolution (VoLTE) service).

At present, the demand of users for local information sharing is higher and higher, and most services are near field communication services, such as vehicle-to-vehicle communication services. In the related art, a service flow (referred to as a dedicated bearer flow for short) transmitted by a dedicated bearer is transmitted from an edge gateway to a PGW, the edge gateway does not directly transmit the dedicated bearer flow to an edge server deployed on an edge gateway side (the edge server belongs to a regional server), and the dedicated bearer flow cannot be distributed, so that a user's requirement for local shared information cannot be met well, and therefore a method for distributing the dedicated bearer flow is urgently needed.

Disclosure of Invention

The application provides a processing method, device and system of a proprietary bearer flow, which can solve the problem that the demand of a user on local shared information cannot be well met because the proprietary bearer flow cannot be shunted in the related art. The technical scheme is as follows:

in a first aspect, a method for processing a proprietary bearer stream is provided, where the method may be used for an edge gateway, and the method includes: the edge gateway receives a first bearer flow of a first UE, and then sends the first bearer flow to an edge server to shunt the first bearer flow under the condition that the first bearer flow is a proprietary bearer flow. And then, the edge gateway sends the distribution indication information to the PGW. And the edge gateway starts the overtime monitoring aiming at the first bearer under the condition of receiving the closing response information sent by the PGW. The shunting indication information is used for indicating the PGW to close the overtime monitoring for the first bearer used for transmitting the first bearer, and the overtime monitoring is used for monitoring whether the idle time of the first bearer reaches the preset time. The close response information is used to indicate that the PGW has closed the monitoring timeout for the first bearer.

In the method, the edge gateway can execute the shunting operation on the special bearing flow, and the edge gateway can directly transmit the special bearing flow to the edge server arranged on the edge gateway side, so that the transmission path of the special bearing flow is shortened, the number of transmission nodes is reduced, the transmission time delay is reduced, and the requirement of a user on local information sharing is well met.

Meanwhile, after the edge gateway performs the shunting operation on the dedicated bearer flow, in order to ensure that the service is normally processed and avoid service interruption or failure, the edge gateway sends shunting indication information to the PGW, so that the PGW closes the timeout monitoring for the current dedicated bearer (i.e., the first bearer) based on the shunting indication information, and then the edge gateway opens the timeout monitoring for the dedicated bearer to monitor the state of the dedicated bearer.

Optionally, after starting the timeout monitoring for the first bearer, the method may further include: and the edge gateway sends release indication information to the PGW under the condition that the open overtime monitoring monitors that the idle time of the first bearer reaches a preset time, wherein the release indication information is used for indicating the PGW to execute a release operation on the first bearer. And then, the edge gateway receives release response information sent by the PGW, where the release response information is used to indicate whether the release operation is successfully executed.

In this application, if the edge gateway monitors that the idle duration of the first bearer reaches the preset duration, the edge gateway sends release indication information to the PGW to indicate the PGW to perform a release operation on the first bearer: and releasing the resources occupied by the first bearer, thereby achieving the effect of saving network resources.

Optionally, receiving the first bearer stream of the first UE may include: and receiving a first bearer stream transmitted by the first UE forwarded by the base station. Correspondingly, before receiving the first bearer flow transmitted by the first UE forwarded by the base station, the method may further include: the edge gateway receives a default bearer stream sent by the first UE forwarded by the base station. And under the condition that the default bearer flow needs to be shunted and the default bearer flow is used for triggering the creation of the first bearer, the edge gateway sends creation indication information to the PGW, wherein the creation indication information is used for indicating the PGW to create the first bearer.

Optionally, the default bearer stream carries IP quintuple information of the default bearer stream, and after receiving the default bearer stream sent by the first UE forwarded by the base station, the method may further include: the edge gateway judges whether the IP quintuple information of the default bearer stream conforms to a first preset rule. And under the condition that the IP quintuple information of the default bearer flow accords with a first preset rule, the edge gateway determines that the default bearer flow needs to be shunted. And then the edge gateway judges whether the IP quintuple information of the default bearer stream conforms to a preset creation rule of the edge gateway. And under the condition that the IP five-tuple information of the default bearer flow accords with a creation rule, the edge gateway determines that the default bearer flow is used for triggering the creation of the first bearer.

In the present application, to solve the problem that the uplink creation mode cannot trigger the creation of the dedicated bearer, the edge gateway further determines whether the default bearer flow is a bearer flow for triggering the creation of the dedicated bearer, when the IP five-tuple information of the default bearer flow conforms to the first preset rule. The edge gateway can trigger the creation of the first bearer to indicate the PGW to create the first bearer under the condition that a default bearer flow for triggering the creation of the first bearer is shunted by the edge gateway, so as to avoid that the creation of the first bearer cannot be triggered because the default bearer flow is shunted by the edge gateway.

Optionally, the first bearer flow carries a Qos parameter of the first bearer flow, and after starting timeout monitoring for the first bearer, the method may further include: and the edge gateway sends modification indication information to the PGW under the condition that the Qos parameter of the first bearer flow is detected to change, wherein the modification indication information is used for indicating the PGW to modify the Qos parameter of the first bearer flow into the Qos parameter of the first bearer flow. And then, the edge gateway receives 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 successfully performed.

If the edge gateway detects that the Qos parameter of the first bearer flow changes, the edge gateway sends modification indication information to the PGW to indicate the PGW to modify the Qos parameter of the first bearer, so as to meet the service requirement, achieve reliable Qos guarantee for the user, and enable the user to obtain better service experience.

Optionally, starting timeout monitoring for the first bearer may include: and setting the aging duration corresponding to the first load, wherein the aging duration is the same as the preset duration.

Optionally, the creation 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 a hypertext Transfer Protocol (HTTP), a File Transfer Protocol (FTP), a Simple Mail Transfer Protocol (SMTP), a remote terminal Protocol (TELNET), a Network File System (NFS), or the like.

Optionally, sending the first bearer flow to the edge server when the first bearer flow is a dedicated bearer flow, includes: and the edge gateway sends the first bearer flow to the edge server under the condition that the first bearer is a proprietary bearer and the first bearer flow needs to be shunted.

Optionally, the first bearer flow carries IP five-tuple information of the first bearer flow, and after receiving the first bearer flow of the first user equipment UE, the method further includes: the edge gateway obtains a bearer identifier of the first bearer, and determines that the first bearer is a dedicated bearer when the bearer identifier of the first bearer belongs to a preset dedicated bearer identifier set, where the preset dedicated bearer identifier set includes the bearer identifier of the dedicated bearer. Then, the edge gateway judges whether the IP quintuple information of the first bearer flow accords with a second preset rule, and determines that the first bearer flow needs to be shunted under the condition that the IP quintuple information of the first bearer flow accords with the second preset rule.

For example, the bearer identity of the proprietary bearer may be represented by any number from 6 to 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 sending the creation indication information to the PGW, the method may further include: and the edge gateway receives creation response information sent by the PGW, wherein the creation response information is used for indicating that the creation operation of the first bearer is successfully executed.

In a second aspect, there is provided a method of processing a proprietary bearer stream, the method being usable with a PGW, the method comprising: the PGW receives offloading indication information sent by the edge gateway, and closes, based on the offloading indication information, timeout monitoring for the first bearer, and then sends, to the edge gateway, closing response information. Wherein the first bearer is used for transmitting a first bearer stream. The offloading indication information is generated after the edge gateway sends the first bearer flow of the first UE to the edge server. The timeout monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time. The close response information is used to instruct the edge gateway to start timeout monitoring for the first bearer.

After the edge gateway performs the shunting operation on the dedicated bearer flow, in order to ensure that the service is normally processed and avoid service interruption or failure, the edge gateway sends shunting indication information to the PGW, the PGW closes the timeout monitoring for the first bearer based on the shunting indication information, and then the PGW sends a close response information to the edge gateway, so that the edge gateway opens the timeout monitoring for the first bearer, thereby facilitating monitoring of the state of the first bearer.

Optionally, after sending the shutdown response message to the edge gateway, the method may further include: the PGW receives release indication information sent by the edge gateway, and the PGW performs a release operation on the first bearer based on the release indication information, and then sends release response information to the edge gateway. The release indication information is generated by the edge gateway when it is monitored that the idle time of the first bearer reaches the preset time based on the opened overtime monitoring, and the release response information is used for indicating whether the release operation is successfully executed.

If the edge gateway monitors that the idle time of the first bearer reaches a preset time, the edge gateway sends release indication information to the PGW to indicate the PGW to execute a release operation on the first bearer: and releasing the resources occupied by the first bearer, thereby achieving the effect of saving network resources.

Optionally, the first bearer stream is sent by the first UE to the edge gateway through the base station, and before receiving the offloading indication information sent by the edge gateway, the method may further include: and the PGW receives creation indication information sent by the edge gateway, and the PGW creates a first bearer based on the creation indication information. The creation indication information is generated by the edge gateway when detecting that the default bearer flow needs to be shunted and the default bearer flow is used for triggering creation of the first bearer, and the default bearer flow is sent by the first UE to the edge gateway through the base station.

The edge gateway can instruct the PGW to create the first bearer under the condition that a default bearer flow for triggering creation of the first bearer is shunted by the edge gateway, so as to avoid that the creation of the first bearer cannot be triggered because the default bearer flow is shunted by the edge gateway.

Optionally, the first bearer flow carries a Qos parameter of the first bearer flow, and after sending the close response information to the edge gateway, the method may further include: and the PGW receives modification indication information sent by the edge gateway, modifies the Qos parameter of the first bearer into the Qos parameter of the first bearer based on the modification indication information, and then sends modification response information to the edge gateway. Wherein the modification indication information is generated by the edge gateway when the change of the QoS parameter of the first bearer flow is detected. The modification response information is used to indicate whether the modification operation of the Qos parameter of the first bearer was successfully performed.

Optionally, closing timeout monitoring for the first bearer based on the offloading indication information includes: and controlling the aging duration corresponding to the first load to be in a failure state, wherein the aging duration is the same as the preset duration.

Optionally, after creating the first bearer based on the creation indication information, the method may further include: and the PGW sends creating response information to the edge gateway, wherein the creating response information is used for indicating that the creating operation of the first bearer is successfully executed.

In a third aspect, there is provided a processing apparatus for a proprietary bearer stream, the apparatus comprising at least one module for implementing the processing method for a proprietary bearer stream according to the first aspect.

In a fourth aspect, there is provided a processing apparatus for a proprietary bearer stream, the apparatus comprising at least one module for implementing the processing method for a proprietary bearer stream according to the second aspect.

In a fifth aspect, there is provided a processing apparatus for a proprietary bearer stream, which may be used for an edge gateway, the processing apparatus for the proprietary bearer stream comprising: a processor, memory, a network interface, and a bus. Wherein the bus is used for connecting the processor, the memory and the network interface. The network interface is used for realizing communication connection between the edge gateway and the PGW. The processor is configured to execute the program stored in the memory to implement the processing method of the exclusive bearer stream according to the first aspect.

In a sixth aspect, there is provided a computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of processing a proprietary bearer stream according to the first aspect.

In a seventh aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of processing a proprietary bearer stream according to the first aspect.

In an eighth aspect, there is provided a processing apparatus for a proprietary bearer stream, usable with a PGW, the processing apparatus for the proprietary bearer stream comprising: a processor, memory, a network interface, and a bus. Wherein the bus is used for connecting the processor, the memory and the network interface. The network interface is used for realizing communication connection between the PGW and the edge gateway. The processor is configured to execute the program stored in the memory to implement the processing method of the proprietary bearer stream according to the second aspect.

In a ninth aspect, there is provided a computer-readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the method of processing a proprietary bearer stream according to the second aspect.

In a tenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of processing a proprietary bearer stream according to the second aspect.

In an eleventh aspect, a processing system for exclusively carrying streams is provided, which includes an edge gateway and a PGW.

The edge gateway comprises the processing device of the exclusive bearer stream according to the third aspect, and the PGW comprises the processing device of the exclusive bearer stream according to the fourth aspect;

alternatively, the edge gateway includes the processing apparatus for the dedicated bearer stream according to the fifth aspect, and the PGW includes the processing apparatus for the dedicated bearer stream according to the eighth aspect.

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

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

The beneficial effect that technical scheme that this application provided brought is:

the edge gateway receives a first bearer flow of the first UE, sends the first bearer flow to the edge server and sends shunting indication information to the PGW under the condition that the first bearer flow for transmitting the first bearer flow is a special bearer and needs to be shunted, so that the PGW closes overtime monitoring aiming at the first bearer, and then the edge gateway opens overtime monitoring aiming at the first bearer, thereby realizing shunting of the special bearer flow, better meeting the requirement of a user on local shared information, meeting the requirement of near field communication service and ensuring that the service is normally processed. And the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer when detecting that the Qos parameter of the first bearer flow changes, so as to meet the service requirement. The edge gateway can also instruct the PGW to perform a release operation on the first bearer when monitoring that the idle duration of the first bearer reaches a preset duration, so as to achieve an effect of saving network resources.

Drawings

FIG. 1-1 is a schematic illustration of an implementation environment in accordance with an embodiment of the present invention;

FIGS. 1-2 are flow diagrams of a method for processing a proprietary bearer stream in accordance with an embodiment of the present invention;

FIG. 2 is a flowchart of a method for processing a proprietary bearer stream according to an embodiment of the present invention;

FIG. 3 is a flow chart of a method of processing a proprietary bearer stream according to an embodiment of the present invention;

FIG. 4-1 is a schematic structural diagram of a processing apparatus for exclusively carrying a stream according to an embodiment of the present invention;

fig. 4-2 is a schematic structural diagram of another processing apparatus for exclusively carrying a stream according to an embodiment of the present invention;

FIG. 5-1 is a schematic diagram of another embodiment of a device for processing a proprietary carrier stream;

fig. 5-2 is a schematic structural diagram of another processing apparatus for exclusively carrying a stream according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a processing apparatus for exclusively carrying a stream according to an embodiment of the present invention.

Detailed Description

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

Referring to fig. 1-1, a schematic diagram of an implementation environment is shown in which various embodiments of the present application are implemented. The implementation environment may be a 3GPP EPS, which may include UE001, eNodeB 002, edge gateway 003, edge server 004, PGW005, and center server 006, as shown in fig. 1-1.

Where UE001 refers to a device that provides voice and/or data connectivity to a user, the UE may be a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user agent, user equipment, a subscriber station, a subscriber unit, a mobile terminal device, a wireless terminal device, or the like. For example, a 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 (PDA), a handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a Mobile station in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and so on.

The Edge gateway 003, also called a remote gateway, addresses the problem of Edge Computing (MEC) for short-range communication services (e.g., car-to-car communication services) via the Edge gateway: a user is provided with Information Technology (IT) architecture and cloud computing based capabilities in a Radio Access Network (RAN) Network near the mobile user. Currently, an edge gateway can perform a splitting operation on a default bearer stream, generally, it is determined whether Internet Protocol (IP) quintuple information of the default bearer stream conforms to a preset splitting rule, and the edge gateway transmits the default bearer stream to an edge server under the condition that the IP quintuple information of the default bearer stream conforms to the preset splitting rule; and under the condition that the IP quintuple information of the default bearer flow does not accord with the preset shunting rule, the edge gateway transmits the default bearer flow to the PGW.

The edge server 004 can be seen as a cloud server running at the edge of the mobile network, running a specific task. The edge server may be a server, a server cluster composed of several servers, or a cloud computing service center. The edge server is flexible in deployment position, can be deployed at the positions of a single base station, a cloud wireless access network, a metropolitan area and the like, and can also be integrated with a third-party service server.

PGW005 is a central gateway of EPC in 3GPP EPS for implementing session management and bearer management, data forwarding, policy enforcement, charging, etc. An S18 interface is arranged between the edge gateway and the PGW, and an S18 interface is used for completing the transmission of signaling and data of a control plane between the edge gateway and the PGW.

The central server 006 may be a server, a server cluster composed 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. The SGW and the PGW may be combined together, and both may be implemented in one physical node. The embodiments of the present invention mainly use an edge gateway and a PGW as examples for description.

In the related art, the edge gateway only performs the shunting matching operation on the default bearer stream, and does not perform the shunting matching operation on the proprietary bearer stream, the edge gateway always directly transmits the proprietary bearer stream to the PGW, the PGW transmits the proprietary bearer stream to the central server (the central server belongs to a provincial server), and the central server can transmit the proprietary bearer stream to the edge server according to the requirement.

In the method for processing the dedicated bearer flow provided in the embodiment of the present invention, the edge gateway may perform a split matching operation on the dedicated bearer flow, and in order to ensure that the service is processed normally, after splitting the dedicated bearer flow, the edge gateway may instruct the PGW to close the timeout monitoring for the dedicated bearer used for transmitting the dedicated bearer flow, and then the edge gateway starts the timeout monitoring for the dedicated bearer. Fig. 1-2 show a flow chart of a method of processing a proprietary bearer stream, as shown in fig. 1-2, the method comprising:

step 101, an edge gateway receives a first bearer stream of a first UE.

The first bearer flow may be sent to the edge gateway by the first UE through the base station, or may be sent to the edge gateway by a network side, such as a PGW. That is, the processing method of the dedicated bearer stream may be applied to a scenario of uplink data transmission, and may also be applied to a scenario of downlink data transmission.

Step 102, the edge gateway sends the first bearer flow to the edge server under the condition that the first bearer flow is a proprietary bearer flow, so as to shunt the first bearer flow.

The edge gateway directly transmits the special bearing stream to the edge server deployed on the edge gateway side, so that the transmission path of the special bearing stream is shortened, the number of transmission nodes is reduced, transmission delay is reduced, and the requirement of a user on local shared information is well met.

And step 103, the edge gateway sends the distribution indication information to the PGW.

The offloading indication information is used to indicate the PGW to turn off monitoring for a timeout of a first bearer used for transmitting the first bearer stream. The timeout monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time. Wherein the idle duration refers to a duration of time during which no dedicated bearer stream is transmitted.

And step 104, the PGW closes the timeout monitoring for the first bearer based on the offloading indication information.

And 105, the PGW sends a close response message to the edge gateway.

The close response information is used to instruct the edge gateway to start timeout monitoring for the first bearer.

And step 106, the edge gateway starts timeout monitoring for the first bearer when receiving the close response information sent by the PGW.

The edge gateway starts the overtime monitoring aiming at the first bearing and monitors the state of the first bearing, so that the normal processing of the service can be ensured, and the service interruption or failure is avoided.

In summary, in the method for processing the dedicated bearer flow provided in the embodiment of the present invention, the edge gateway receives the first bearer flow of the first UE, sends the first bearer flow to the edge server when the first bearer flow is the dedicated bearer flow, and sends the diversion indication information to the PGW, so that the PGW closes the timeout monitoring for the first bearer, and then the edge gateway opens the timeout monitoring for the first bearer, thereby implementing diversion of the dedicated bearer flow, and being capable of better meeting the user requirement for local shared information, meeting the requirement of the near field communication service, and ensuring that the service is normally processed.

Further, in the first implementation manner, the edge gateway may further instruct the PGW to modify the Qos parameter of the corresponding dedicated bearer to meet the service requirement when detecting that the Qos parameter of the dedicated bearer changes, and may instruct the PGW to perform a release operation on the dedicated bearer when monitoring that the idle duration of the dedicated bearer reaches a preset duration, so as to achieve an effect of saving network resources.

In a second implementation manner, in a case that a default bearer flow for triggering creation of the dedicated bearer is shunted by the edge gateway, so that creation of the dedicated bearer cannot be triggered, and further, the PGW cannot create the dedicated bearer, the edge gateway can instruct the PGW to create the dedicated bearer. The following describes a processing method of a dedicated bearer stream provided by an embodiment of the present invention by taking these two realizable manners as examples.

In a first implementation manner, as shown in fig. 2, the processing method of the exclusive bearer stream may include:

step 201, the edge gateway receives a first bearer stream of the first UE.

Step 202, the edge gateway obtains a bearer identifier of the first bearer.

The first bearer is for transmitting a first bearer stream.

Generally, one UE corresponds to a plurality of dedicated bearers, each dedicated bearer is used for transmitting one dedicated bearer stream, each dedicated bearer has one bearer identifier, and the bearer identifiers of different dedicated bearers in the plurality of dedicated bearers are different. The bearer identification of the proprietary bearer can be represented by any number from 6 to 15. Illustratively, the first UE corresponds to 3 dedicated bearers: CZ1, CZ2 and CZ 3. CZ1 is used for transmitting a proprietary bearer stream CZL1, and the bearer identification of CZ1 is 6; CZ2 is used for transmitting the proprietary bearer stream CZL2, and the bearer identification of CZ2 is 7; CZ3 is used to transport the proprietary bearer stream CZL3, and the bearer identification of CZ3 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 sent by the edge gateway by the PGW in the process of creating the S18 interface session. For the process of acquiring the context information of the first UE by the edge gateway and the content of the context information of the first UE, reference may be made to related technologies, which are not described herein again.

Step 203, the edge gateway determines that the first bearer is the dedicated bearer under the condition that the bearer identifier of the first bearer belongs to the preset dedicated bearer identifier set.

The preset special bearing identification set comprises bearing identifications of special bearings. In the case that the bearer identifier of the first bearer belongs to the preset dedicated bearer identifier set, the edge gateway may determine that the first bearer is a dedicated bearer, that is, the first bearer is a dedicated bearer.

Since the bearer id of the dedicated bearer can be represented by any number from 6 to 15, in this step, the preset set of dedicated bearer ids may be {6,7,8,9,10,11,12,13,14,15 }. For example, the edge gateway may determine CZ1 to be the proprietary bearer and CZ1 to be the proprietary bearer since 6 belongs to {6,7,8,9,10,11,12,13,14,15}, the edge gateway receives the first bearer flow of the first UE as CZL1, the first bearer is CZ1, and the bearer identification of the first bearer is 6.

And step 204, the edge gateway judges whether the IP quintuple information of the first bearer flow accords with a second preset rule.

The first bearer flow carries IP quintuple information of the first bearer flow. The IP five-tuple 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 edge gateway receives the first bearer stream of the first UE as CZL1, and the IP quintuple information of CZL1 is: 192.168.1.110000 TCP 121.14.88.7680, where 192.168.1.1 represents the source IP address, 10000 represents the source port, TCP represents the protocol information, 121.14.88.76 represents the destination IP address, and 80 represents the destination port. The IP quintuple information is used to indicate that the first UE with the IP address 192.168.1.1 connects to the terminal with the IP address 121.14.88.76 and the port 80 through the port 10000 by using TCP.

The second preset rule is used for judging whether the first bearer flow needs to be shunted. 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 may be an IP protocol, ARP, etc. The transport layer protocol may be UDP, TCP, etc. The application layer protocol may be HTTP, FTP, SMTP, TELNET, NFS, etc.

For example, the edge gateway may determine whether a destination IP address in the IP quintuple information of the first bearer stream belongs to an address range of the destination IP address in the second preset rule, whether a destination port in the IP quintuple information of the first bearer stream belongs to a port range of the destination port in the second preset rule, and whether a 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. And under the condition that the destination IP address in the IP quintuple information of the first bearing flow belongs to the address range of the destination IP address in the second preset rule, the destination port in the IP quintuple information of the first bearing flow belongs to the port range of the destination port in the second preset rule, and the protocol indicated by the protocol information in the IP quintuple information of the first bearing flow belongs to the protocol information in the second preset rule, the edge gateway determines that the IP quintuple information of the first bearing flow accords with the second preset rule. As an example, the second preset rule is: 121.14.88.0-121.14.88.255, 10-100, IP, TCP. Wherein, 121.14.88.0-121.14.88.255 are address ranges of destination IP addresses, 10-100 are port ranges of destination ports, and IP and TCP are protocol information. Assuming that the destination IP address is 121.14.88.76, the destination port is 80, and the protocol indicated by the protocol information is TCP in the IP quintuple information of the first bearer stream, the edge gateway may determine that the IP quintuple information of the first bearer stream conforms to the second preset rule.

Step 205, the edge gateway determines that the first bearer flow needs to be shunted when the IP five-tuple information of the first bearer flow conforms to the second preset rule.

Based on step 204, the edge gateway determines that the first bearer flow needs to be shunted when the IP quintuple information of the first bearer flow conforms to the second preset rule; and the edge gateway determines that the first bearer flow does not need to be shunted under the condition that the IP five-tuple information of the first bearer flow does not accord with the second preset rule.

Step 206, the edge gateway sends the first bearer flow to the edge server to offload the first bearer flow when the first bearer is a dedicated bearer and the first bearer flow needs to be offloaded.

In this step, the edge gateway performs a split operation on the dedicated bearer stream to better satisfy the user's demand for local shared information.

For the near field communication service, in the related art, the edge gateway always directly transmits the dedicated bearer stream to the PGW, the PGW transmits the dedicated bearer stream to the central server, and the central server transmits the dedicated bearer stream to the edge server deployed on the edge gateway side as required, so that the edge gateway cannot realize the shunting of the dedicated bearer stream. Obviously, in this processing mode, the transmission path of the proprietary bearer stream is long, there are many transmission nodes, the transmission delay is high, the requirement of the user on local shared information cannot be well met, the requirement of the near field communication service cannot be met, and meanwhile, the great waste of network resources is also caused; in the embodiment of the present invention, the edge gateway can directly transmit the proprietary bearer stream to the edge server deployed at the edge gateway side, so that the transmission path of the proprietary bearer stream is shortened, the number of transmission nodes is reduced, the transmission delay is reduced, the requirement of the user for local information sharing is better met, and the MEC problem of the near field communication service is really solved: the method provides the capability based on IT architecture and cloud computing for the user in the RAN network close to the mobile user, thereby providing a service environment with low time delay, high bandwidth and directly-acquired real-time wireless network information (such as user position, base station load and the like) for service providers such as an application developer, a content provider and the like, and further enabling the service providers to provide differentiated services and services for the user.

And step 207, the edge gateway sends the distribution indication information to the PGW.

The offloading indication information is used to indicate the PGW to close the timeout monitoring for the first bearer.

The timeout monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time. For example, the preset time period may be 120 seconds.

In the related art, in order to save network resources, generally, the PGW monitors whether the idle duration of the dedicated bearer reaches a preset duration based on locally-started timeout monitoring, and when the idle duration of the dedicated bearer reaches the preset duration, the PGW performs a release operation on the dedicated bearer: the resources occupied by the dedicated bearer are released.

In the embodiment of the present invention, after the edge gateway performs the shunting operation on the dedicated bearer flow, since the dedicated bearer flow does not pass through the PGW any more, if the PGW still monitors whether the idle duration of the dedicated bearer reaches the preset duration based on local timeout, and performs the release operation on the dedicated bearer under the condition that the idle duration of the dedicated bearer reaches the preset duration, the dedicated bearer flow directly sent to the edge server by the edge gateway cannot be successfully transmitted, so that the service cannot be normally processed, and finally the service is interrupted or fails. Therefore, after the edge gateway performs the shunting operation on the dedicated bearer flow, in order to ensure that the service is normally processed and avoid service interruption or failure, the edge gateway sends shunting indication information to the PGW, so that the PGW closes the timeout monitoring for the current dedicated bearer (i.e., the first bearer) based on the shunting indication information, and then the edge gateway opens the timeout monitoring for the current dedicated bearer, thereby monitoring the state of the current dedicated bearer.

Step 208, the PGW closes the 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 identity of the first UE, the gateway identity of the edge gateway, and the bearer identity 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 also 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, then the offloading indication information sent by the edge gateway to the PGW may include the device identifier 001 of the first UE, the gateway identifier 01 of the edge gateway, and the bearer identifier 6 of CZ 1. The PGW turns off timeout monitoring for CZ1 based on the diversion indication information.

Optionally, step 208 may include:

the PGW controls an Aging duration (Aging time) corresponding to the first bearer to be in a failure state, where the Aging duration is the same as the preset duration in step 207.

As shown in step 202, generally, one UE corresponds to a plurality of dedicated bearers, each of which has an aging duration. The aging duration is used for monitoring the state of the corresponding proprietary bearer. For each dedicated bearer, the dedicated bearer is released in case the idle duration of the dedicated bearer reaches the aging duration. Illustratively, the first UE corresponds to 3 dedicated bearers: CZ1, CZ2 and CZ3, table 1 exemplarily shows the correspondence of the proprietary bearers with the aging duration. The aging time length corresponding to CZ1 is 120 seconds, the aging time length corresponding to CZ2 is 130 seconds, and the aging time length corresponding to CZ3 is 110 seconds. In case the idle duration of CZ1 reaches 120 seconds, CZ1 will be released; in case the idle duration of CZ2 reaches 130 seconds, CZ2 will be released; in case the idle duration of CZ3 reaches 110 seconds, CZ3 will be released.

In this step, assuming that the first bearer is CZ1, to turn off the timeout monitoring for CZ1, the PGW may control the aging duration (i.e., 120 seconds) corresponding to CZ1 to be in a failure state.

TABLE 1

Proprietary bearers	Aging duration (unit: second)
		CZ1	120
CZ2	130
		CZ3	110

Step 209, the PGW sends a close response message to the edge gateway.

The close response information is used to instruct the edge gateway to start timeout monitoring for the first bearer. And the PGW generates closing response information and sends the closing response information to the edge gateway under the condition that the overtime monitoring aiming at the first bearer is closed. And the edge gateway determines that the PGW has closed the timeout monitoring for the first bearer under the condition of receiving the closing response information, and then starts the timeout monitoring for the first bearer.

Step 210, the edge gateway starts timeout monitoring for the first bearer when receiving the close response information sent by the PGW.

The edge gateway opens a timeout monitoring for the first bearer such that the monitoring operation of the status of the first bearer is no longer performed by the PGW but is performed by the edge gateway. Because the state of the first bearer is monitored by the edge gateway, normal processing of the service can be ensured, and service interruption or failure is avoided.

Optionally, the edge gateway starts timeout monitoring for the first bearer, including:

the edge gateway sets an aging duration corresponding to the first bearer, where the aging duration is the same as the preset duration in step 207.

Assuming that the first bearer is CZ1 in step 208, to start the timeout monitoring for CZ1, the edge gateway may set the aging duration corresponding to CZ1, i.e., 120 seconds.

And step 211, the edge gateway sends modification indication information to the PGW when detecting that the Qos parameter of the first bearer flow changes.

The modification indication information is used for indicating the PGW to modify the Qos parameter of the first bearer to the Qos parameter of the first bearer stream.

In the related art, the 3GPP EPS may ensure the quality of service level provided by the dedicated bearer, such as a rate, a delay packet loss rate, and the like, by controlling the Qos parameter of the dedicated bearer, for example, the original Qos parameter of the dedicated bearer may be modified, so as to implement dynamic control of the Qos parameter. In general, in the case of dynamic change of transmission data, the original Qos parameters of the dedicated bearer need to be modified.

In this step, if the edge gateway detects that the Qos parameter of the first bearer flow changes, the edge gateway sends modification indication information to the PGW to indicate the PGW to modify the Qos parameter of the first bearer, so as to meet service requirements, achieve reliable Qos guarantee for the user, and enable the user to obtain a better service experience effect.

For example, the Qos parameter may include Qos Class Identifier (QCI), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), and other parameters. The description about the respective parameters may refer to the related art.

And 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, where the Qos parameter of the first bearer is an expected result 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.

Step 212 may include the following steps:

1) the PGW sends a change bearer request (update bearer request) to the MME.

The change bearer request carries the device identifier of the first UE, the bearer identifier of the first bearer, and the Qos parameter of the first bearer in the modification indication information.

2) The MME sends a radio bearer modification request (bearer modification request) and a session management request (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. 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, and then sends Radio Resource Control (RRC) connection reconfiguration information (connection reconfiguration) to the first UE.

4) And the first UE sends RRC connection reconfiguration response information to the eNodeB.

The RRC connection reconfiguration response message is used to indicate that the RRC connection reconfiguration is complete.

5) After the radio resource and S1(S1 is an interface between the eNodeB and the SGW) resource modification is successful, the eNodeB sends radio bearer modification response information (bearer modification response) to the MME.

6) The first UE sends, to the eNodeB, modification first bearer context acceptance information through direct transfer information (direct transfer), indicating that the first bearer is successfully modified.

7) The eNodeB transmits session management response information (session management response) to the MME.

8) The MME sends modify bearer response information (update bearer response) to the PGW.

The modifying process of the Qos parameter of the first bearer in step 1) to step 8) included in step 212 may refer to a modifying process of a Qos parameter of a dedicated bearer in the related art, which is not described again in this embodiment of the present invention.

Step 213, the PGW sends a modification response message 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 successfully performed.

After the PGW performs the modification operation on the Qos parameter of the first bearer, whether the modification is successful or failed, the PGW sends modification response information to the edge gateway, so as to notify the edge gateway whether the modification operation on the Qos parameter of the first bearer is successful.

Step 214, the edge gateway sends release indication information to the PGW when monitoring that the idle duration of the first bearer reaches the preset duration based on the opened timeout.

The release indication information is used to indicate 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 the preset duration based on the open timeout monitoring, the edge gateway sends release indication information to the PGW to indicate the PGW to execute a release operation on the first bearer: and releasing (also called deactivating) the resources occupied by the first bearer to achieve the effect of saving network resources.

Assuming that the first bearer is CZ1 in step 208, the preset duration is 120 seconds, and the edge gateway sends release indication information to the PGW to indicate the PGW to perform a release operation on CZ1 when monitoring that the idle duration of CZ1 reaches 120 seconds.

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 a device identifier of the first UE and a bearer identifier of the first bearer. The edge gateway may determine the first bearer based on the device identifier of the first UE and the bearer identifier of the first bearer in the release indication information, and perform a release operation on the first bearer.

Step 215 may include the following steps:

1) the PGW sends a delete bearer request (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 release bearer request (inactive bearer request) to the eNodeB.

The bearer release request carries the device identifier of the first UE and the bearer identifier of the first bearer, and the bearer release request also carries NAS information of the first bearer context release request.

3) And after receiving the bearer release request, the eNodeB starts a first bearer release process and sends RRC connection reconfiguration information to the first UE. The RRC connection reconfiguration information includes NAS information of the release first bearer context request.

4) And after receiving the NAS information in the RRC connection reconfiguration information, the first UE releases the resources of the first bearer and then sends RRC connection reconfiguration response information to the eNodeB.

The RRC connection reconfiguration response information is used to indicate that the first bearer release is successful.

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

6) After the first UE completes RRC connection reconfiguration, it sends an accept message for releasing the first bearer context to the eNodeB through direct transfer (direct transfer), which indicates that the first bearer is successfully deleted.

7) The eNodeB sends a first bearer context release accept message (inactive EPS bearer context accept) to the MME, and notifies the MME that the first bearer release operation is completed.

8) The MME sends a delete bearer response message (delete bearer response) to the PGW, and notifies the PGW that the release operation of the first bearer is completed.

The release process of the first bearer in step 1) to step 10) included in step 215 may refer to a release process of a dedicated bearer in the related art, which is not described again in this embodiment of the present invention.

Step 216, the PGW sends a release response message to the edge gateway.

The release response information is used to indicate whether the release operation was successfully performed.

In the embodiment of the present invention, by performing steps 201 to 210, the edge gateway can perform a split matching operation on the dedicated bearer flow, instruct the PGW to close the timeout monitoring for the dedicated bearer used for transmitting the dedicated bearer flow, and then start the timeout monitoring for the dedicated bearer, where steps 202 to 205 are optional steps; by executing steps 211 to 213, the edge gateway can instruct the PGW to modify the Qos parameter of the dedicated bearer to meet the service requirement when detecting that the Qos parameter of the dedicated bearer stream changes; by executing steps 214 to 216, the edge gateway can instruct the PGW to perform a release operation on the dedicated bearer when monitoring that the idle duration of the dedicated bearer reaches the preset duration, so as to achieve an effect of saving network resources.

In summary, in the processing method for the dedicated bearer flow provided in the embodiment of the present invention, the edge gateway receives the first bearer flow of the first UE, sends the first bearer flow to the edge server and sends the offloading indication information to the PGW under the condition that the first bearer flow used for transmitting the first bearer flow is the dedicated bearer and the first bearer flow needs to be offloaded, so that the PGW closes the timeout monitoring for the first bearer, and then the edge gateway opens the timeout monitoring for the first bearer, thereby implementing offloading of the dedicated bearer flow, better meeting the requirement of the user for local shared information, meeting the requirement of the near field communication service, and ensuring that the service is normally processed. And the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer when detecting that the Qos parameter of the first bearer flow changes, so as to meet the service requirement. The edge gateway can also instruct the PGW to perform a release operation on the first bearer when monitoring that the idle duration of the first bearer reaches a preset duration, so as to achieve an effect of saving network resources.

In a second implementation manner, the first bearer stream is sent by the first UE to the edge gateway through the base station, for example, as shown in fig. 3, the method for processing the dedicated bearer stream may include:

step 301, the edge gateway receives the default bearer stream sent by the first UE forwarded by the base station.

The edge gateway may determine whether the bearer flow sent by the first UE forwarded by the base station is a default bearer flow based on the bearer identification of the bearer flow. Typically, the bearer identification of the default bearer flow is 5.

Step 302, the edge gateway determines whether the IP quintuple information of the default bearer stream conforms to a first preset rule.

The default bearer stream carries IP quintuple information for the default bearer stream. The IP five-tuple 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 for judging whether the default bearer flow needs to be shunted. 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, among other things, the network layer protocol and the transport layer protocol of the OSI reference model, or the application layer protocol. The edge gateway may determine whether a destination IP address in the IP quintuple information of the default bearer stream belongs to an address range of the destination IP address in the first preset rule, whether a destination port in the IP quintuple information of the default bearer stream belongs to a port range of the destination port in the first preset rule, and whether a protocol indicated by protocol information in the IP quintuple information of the default bearer stream belongs to protocol information in the first preset rule.

For example, in the case that the destination IP address in the IP quintuple information of the default bearer stream belongs to the address range of the destination IP address in the first preset rule, the destination port in the IP quintuple information of the default bearer stream belongs to the port range of the destination port in the first preset rule, and the protocol indicated by the protocol information in the IP quintuple information of the default bearer stream belongs to the protocol information in the first preset rule, the edge gateway determines that the IP quintuple information of the default bearer stream conforms to the first preset rule.

Step 302 may refer to step 204.

Step 303, the edge gateway determines that the default bearer flow needs to be shunted when the IP quintuple information of the default bearer flow conforms to the first preset rule.

Based on step 302, the edge gateway determines that the default bearer flow needs to be shunted when the IP quintuple information of the default bearer flow conforms to the first preset rule; and under the condition that the IP quintuple information of the default bearer flow does not accord with the first preset rule, determining that the default bearer flow does not need to be shunted.

Step 304, the edge gateway judges whether the IP quintuple information of the default bearer stream conforms to a creation rule configured in advance by the edge gateway.

It should be noted that, in the related art, after the default bearer is created, a procedure of creating a dedicated bearer is initiated, where the procedure of creating the dedicated bearer is initiated by the network side or by the UE. The mode initiated by the network side is called a downlink creation mode, and the mode initiated by the UE is called an uplink creation mode. In the uplink creation mode, in order to initiate a process of creating a dedicated bearer, a default bearer flow for triggering creation of the dedicated bearer needs to be transmitted to the PGW, so that the PGW performs an operation of creating the dedicated bearer based on the default bearer flow. However, when the default bearer flow passes through the edge gateway, the edge gateway performs a shunting matching operation on the default bearer flow, if the edge gateway determines whether the IP quintuple information of the default bearer flow conforms to a first preset rule, the edge gateway sends the default bearer flow to the edge server under the condition that the IP quintuple information of the default bearer flow conforms to the first preset rule, and the shunting operation on the default bearer flow is completed; and under the condition that the IP quintuple information of the default bearer flow does not accord with the first preset rule, the edge gateway sends the default bearer flow to the PGW, and the edge gateway cannot perform shunting 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 the bearer flow for triggering the creation of the dedicated bearer, the PGW cannot perform the creation operation of the dedicated bearer because the default bearer flow is not sent to the PGW. In order to solve this problem, in the embodiment of the present invention, in a case that 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 a bearer flow for triggering creation of a dedicated bearer. When the default bearer flow is a bearer flow for triggering creation of the dedicated bearer, the edge gateway may send creation indication information to the PGW to indicate the PGW to create the dedicated bearer. In this way, the creation of the dedicated bearer can be triggered when the default bearer flow for triggering the creation of the dedicated bearer is shunted by the edge gateway, so as to avoid that the creation of the dedicated bearer cannot be triggered because the default bearer flow for triggering the creation of the dedicated bearer is shunted by the edge gateway.

Optionally, in the embodiment of the present invention, in order to determine that the default bearer flow is a bearer flow for triggering creation of the dedicated bearer, a creation rule may be configured in advance on the edge gateway. The creation rules may be, for example, network layer protocols and transport layer protocols of the OSI reference model, or alternatively, application layer protocols. The network layer protocol may be IP, ARP, etc., and the transport layer protocol may be UDP, TCP, etc. The application layer protocol may be HTTP, FTP, SMTP, TELNET, NFS, etc.

Step 305, the edge gateway determines that the default bearer flow is used for triggering the creation of the first bearer under the condition that the IP five-tuple information of the default bearer flow conforms to the creation rule.

The first bearer is a dedicated bearer.

For example, assuming that the protocol indicated by the protocol information in the IP quintuple information of the default bearer flow is TCP and the creation rules are IP and TCP, the edge gateway may determine that the default bearer flow is for triggering creation of the first bearer.

Step 306, the edge gateway sends creation indication information to the PGW when the default bearer flow needs to be shunted and the default bearer flow is used for triggering creation of the first bearer.

The creation indication information is used to indicate that the PGW creates the first bearer.

Based on steps 302 to 305, the edge gateway sends creation indication information to the PGW to indicate the PGW to create the first bearer, when the default bearer flow needs to be shunted and the default bearer flow is used to trigger the creation of the first bearer. In this way, the creation of the first bearer can be triggered when the default bearer flow for triggering the creation of the first bearer is shunted by the edge gateway, so as to avoid that the creation of the first bearer cannot be triggered because the default bearer flow for triggering the creation of the first bearer is shunted by the edge gateway.

In this step, the edge gateway may send creation indication information to the PGW through the S18 interface.

Step 307, the PGW creates the 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 QCI, ARP, GBR, MBR, and other parameters.

Step 307 may include the following steps:

1) the PGW sends a create bearer request (create bearer request) to the MME.

The creating bearer request carries IP quintuple information of a default bearer flow, a transmission bandwidth required by the default bearer flow, Qos parameters of the default bearer flow, and the like in the creating indication information.

The bearer creation 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 (bearer setup request) and a session management request (session management request) to the eNodeB.

The bearer start request carries IP quintuple information of a default bearer flow, a transmission bandwidth required by the default bearer flow, a Qos parameter of the default bearer flow, and the like.

3) And after receiving the bearer starting request, the eNodeB starts a first bearer creating process and sends RRC connection reconfiguration information to the first UE.

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

6) The first UE sends the creation of the first bearer context acceptance information to the eNodeB through direct transfer information (direct transfer).

8) The MME sends create bearer response information (create bearer response) to the PGW.

The process of creating the first bearer in step 1) to step 8) included in step 307 may refer to a process of creating a dedicated bearer by a PGW in the related art, which is not described again in this embodiment of the present invention.

Step 308, the PGW sends a create response message to the edge gateway.

The creation response information is used to indicate that the creation operation of the first bearer was successfully performed.

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 for transmitting a first bearer stream.

In step 310, the edge gateway sends the first bearer flow to the edge server to offload the first bearer flow when the first bearer flow needs to be offloaded.

Step 310 may include: the edge gateway judges whether the IP quintuple information of the first bearing stream meets a second preset rule or not; and the edge gateway determines that the first bearer flow needs to be shunted under the condition that the IP five-tuple information of the first bearer flow accords with a second preset rule. The process of determining that the first bearer flow needs to be split by the edge gateway may refer to step 204 to step 205 in the foregoing embodiment, which is not described herein again.

Step 311, the edge gateway sends the offloading indication information to the PGW.

The offloading indication information is used to indicate the PGW to close the timeout monitoring for the first bearer. The timeout monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time.

Step 311 may refer to step 207.

Step 312, the PGW closes the timeout monitoring for the first bearer based on the offloading indication information.

Optionally, step 312 may include:

the PGW controls an aging duration corresponding to the first bearer to be in a failure state, where the aging duration is the same as the preset duration in step 311.

Step 312 may refer to step 208.

Step 313, the PGW sends a close response message to the edge gateway.

Step 313 may refer to step 209.

Step 314, the edge gateway starts timeout monitoring for the first bearer when receiving the close response information sent by the PGW.

the edge gateway sets an aging duration corresponding to the first bearer, where the aging duration is the same as the preset duration in step 311.

Step 314 may refer to step 210.

Step 315, the edge gateway sends modification indication information to the PGW when detecting that the Qos parameter of the first bearer flow changes.

Step 315 may 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 may refer to step 212.

Step 317, the PGW sends a modification response message to the edge gateway.

Step 317 may refer to step 213.

Step 318, the edge gateway sends release indication information to the PGW when monitoring that the idle duration of the first bearer reaches the preset duration based on the opened timeout.

Step 318 may refer to step 214.

Step 319, the PGW performs a release operation on the first bearer based on the release indication information.

Step 319 may refer to step 215.

Step 320, the PGW sends a release response message to the edge gateway.

In this embodiment of the present invention, by executing steps 301 to 308, in a case that a default bearer flow for triggering creation of a dedicated bearer is shunted by an edge gateway and creation of the dedicated bearer cannot be triggered, the edge gateway can instruct a PGW to create the dedicated bearer, where step 308 is an optional step; by executing steps 309 to 314, the edge gateway can perform a split matching operation on the dedicated bearer flow, instruct the PGW to close the timeout monitoring for the dedicated bearer used for transmitting the dedicated bearer flow, and then open the timeout monitoring for the dedicated bearer; by executing steps 315 to 317, the edge gateway can instruct the PGW to modify the Qos parameter of the dedicated bearer to meet the service requirement when detecting that the Qos parameter of the dedicated bearer stream changes; by executing steps 318 to 320, the edge gateway can instruct the PGW to perform a release operation on the dedicated bearer when monitoring that the idle duration of the dedicated bearer reaches the preset duration, so as to achieve an effect of saving network resources.

In summary, in the processing method for the dedicated bearer flow provided in the embodiment of the present invention, the edge gateway can trigger the creation of the first bearer under the condition that the default bearer flow for triggering the creation of the first bearer is shunted by the edge gateway, so as to avoid that the creation of the first bearer cannot be triggered due to the shunting of the default bearer flow by the edge gateway. The edge gateway sends the first bearer flow to the edge server under the condition that the first bearer flow needs to be shunted, and sends shunting indication information to the PGW, so that the PGW closes overtime monitoring for the first bearer, and then the edge gateway opens overtime monitoring for the first bearer, thereby realizing shunting of the proprietary bearer flow, better meeting the requirement of a user on local shared information, meeting the requirement of near field communication service, and ensuring that the service is normally processed. And the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer, so as to meet the service requirement, and the edge gateway can also instruct the PGW to execute the release operation on the first bearer, so as to achieve the effect of saving network resources.

It should be noted that, the sequence of the steps of the method for processing a dedicated bearer stream provided in the embodiments of the present invention may be appropriately adjusted, and the steps may also be increased or decreased according to the circumstances.

An embodiment of the present invention provides an apparatus 400 for processing a dedicated bearer stream, which may be used in an edge gateway shown in fig. 1-1, as shown in fig. 4-1, where the apparatus 400 includes:

a first receiving module 410, configured to perform step 101, step 201, or step 309 in the foregoing embodiments.

A first sending module 420, configured to perform step 102, step 206, or step 310 in the above embodiments.

A second sending module 430, configured to execute step 103, step 207, or step 311 in the foregoing embodiment.

The starting module 440 is configured to execute step 106, step 210, or step 314 in the foregoing embodiments.

Further, the second sending module 430 is further configured to execute 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 embodiments.

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 execute step 306 in the foregoing embodiment.

Optionally, the default bearer stream carries IP quintuple information of the default bearer stream, and further, as shown in fig. 4-2, the apparatus 400 may further include:

a first determining module 460, configured to perform step 302 in the foregoing embodiment.

A first determining module 470, configured to perform step 303 in the foregoing embodiment.

The first determining module 460 is further configured to execute step 304 in the foregoing embodiment.

The first determining module 470 is further configured to execute step 305 in the foregoing embodiment.

Optionally, the first bearer flow carries a Qos parameter of the first bearer flow, and further, the second sending module 430 is further configured to execute 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 embodiments.

Optionally, the starting module 440 is configured to: and setting the aging duration corresponding to the first load, wherein 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 flow carries IP five-tuple information of the first bearer flow, and further, as shown in fig. 4-2, the apparatus 400 may further include:

an obtaining module 480, configured to perform step 202 in the foregoing embodiment.

A second determining module 490, configured to perform step 203 in the foregoing embodiment.

The second determining module 491 is configured to execute 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.

Other reference meanings in FIG. 4-2 can be referred to in FIG. 4-1.

In summary, in the processing apparatus for dedicated bearer flows provided in the embodiments of the present invention, the edge gateway can trigger the creation of the first bearer to instruct the PGW to create the first bearer under the condition that the default bearer flow used for triggering the creation of the first bearer is shunted by the edge gateway, so as to avoid that the creation of the first bearer cannot be triggered due to the default bearer flow being shunted by the edge gateway. The edge gateway sends the first bearer flow to the edge server under the condition that the first bearer flow needs to be shunted, and sends shunting indication information to the PGW, so that the PGW closes overtime monitoring for the first bearer, and then the edge gateway opens overtime monitoring for the first bearer, thereby realizing shunting of the proprietary bearer flow, better meeting the requirement of a user on local shared information, meeting the requirement of near field communication service, and ensuring that the service is normally processed. And the edge gateway can instruct the PGW to modify the Qos parameter of the first bearer, so as to meet the service requirement, and the edge gateway can also instruct the PGW to execute the release operation on the first bearer, so as to achieve the effect of saving network resources.

Another embodiment of the present invention provides another processing apparatus 600 for exclusively carrying a stream, which may be used in the PGW shown in fig. 1-1, as shown in fig. 5-1, where the apparatus 600 includes:

a receiving module 610, configured to perform step 207 or step 311 in the foregoing embodiments.

A shutdown module 620, configured to perform step 104, step 208, or step 312 in the foregoing embodiments.

A sending module 630, configured to execute step 105, step 209, or step 313 in the foregoing embodiments.

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

As shown in fig. 5-2, the apparatus 600 may further include: a releasing module 640, configured to perform step 215 or step 319 in the foregoing embodiments.

The sending module 630 is further configured to execute step 216 or step 320 in the foregoing embodiment.

Optionally, the first bearer stream is sent by the first UE to the edge gateway through the base station, and further, the receiving module 610 is further configured to execute step 306 in the foregoing embodiment.

As shown in fig. 5-2, the apparatus 600 may further include: a creating module 650 for executing the step 307 in the above embodiment.

Optionally, the first bearer flow carries a Qos parameter of the first bearer flow, and further, the receiving module 610 is further configured to execute 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 embodiments.

The sending module 630 is further configured to execute step 213 or step 317 in the foregoing embodiment.

Optionally, the closing module 620 is configured to:

and controlling the aging duration corresponding to the first load to be in a failure state, wherein the aging duration is the same as the preset duration.

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

Other reference meanings in FIG. 5-2 can be referred to in FIG. 5-1.

In summary, in the processing apparatus for dedicated bearer flows provided in the embodiments of the present invention, when a default bearer flow used to trigger creation of a first bearer is shunted by an edge gateway, a PGW can create the first bearer under an instruction of the edge gateway, so as to avoid that the first bearer cannot be created due to the default bearer flow being shunted by the edge gateway. After the edge gateway sends the first bearer flow to the edge server, the PGW can close the overtime monitoring for the first bearer under the indication of the edge gateway, and then the edge gateway opens the overtime monitoring for the first bearer, so that the flow distribution of the proprietary bearer flow is realized, the requirement of a user on local shared information can be well met, the requirement of near field communication service is met, and the service is ensured to be normally processed. And the PGW can modify the Qos parameter of the first bearer under the indication of the edge gateway, so as to meet the service requirement, and the PGW can also perform a release operation on the first bearer under the indication of the edge gateway, thereby achieving the effect of saving network resources.

The embodiment of the invention also provides a processing system of the proprietary bearer stream, which comprises the edge gateway and the PGW.

Wherein the edge gateway may comprise the processing means for the exclusive bearer stream shown in fig. 4-1 or fig. 4-2, and the PGW may comprise the processing means for the exclusive bearer stream shown in fig. 5-1 or fig. 5-2.

Fig. 6 is a schematic structural diagram of a processing apparatus 700 for exclusively carrying a flow according to an embodiment of the present invention, which 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 (e.g., 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) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the edge gateway and the PGW is implemented through a network interface 703 (which may be wired or wireless). The memory 702 stores a program 7021, the program 7021 is used to implement various application functions, and the processor 701 is used to execute the program 7021 stored in the memory 702 to implement the processing method of the exclusive bearer flow shown in fig. 2 or 3 in cooperation.

Embodiments of the present invention further provide a device for processing a proprietary bearer stream, which may be used for a PGW in the implementation environment shown in fig. 1-1. Referring to fig. 6, the apparatus includes a processor (e.g., CPU), a memory, a network interface, and a bus. Wherein the bus is used for connecting the processor, the memory and the network interface. The memory may comprise random access memory or may comprise non-volatile memory, such as at least one disk memory. The communication connection between the PGW and the edge gateway is realized through a network interface (which may be wired or wireless). The memory stores programs for implementing various application functions, and the processor executes the programs stored in the memory to implement the processing method of the exclusive bearer stream shown in fig. 2 or 3 in cooperation.

The edge gateway may include the processing device shown in fig. 6 for the dedicated bearer stream, and the PGW may include the processing device shown in fig. 6 for the dedicated bearer stream.

It should be noted that, in the device embodiments provided in the present application, the edge gateway and the PGW are used as device names, which do not limit the device itself, that is, other devices having the same function also fall within the protection scope of the present application.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product comprising one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (e.g., solid state disk), among others.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of processing a proprietary bearer stream, the method comprising:

receiving a first bearer stream of a first User Equipment (UE);

sending the first bearer flow to an edge server under the condition that the first bearer flow is a proprietary bearer flow so as to shunt the first bearer flow;

sending shunting indication information to a packet data network gateway (PGW), wherein the shunting indication information is used for indicating the PGW to close overtime monitoring on a first bearer for transmitting the first bearer, and the overtime monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time;

and starting the timeout monitoring for the first bearer on the condition that a close response message sent by the PGW is received, where the close response message is used to indicate that the PGW has closed the timeout monitoring for the first bearer.

2. The method of claim 1, wherein after the opening of the timeout monitoring for the first bearer, the method further comprises:

sending release indication information to the PGW under the condition that it is monitored that the idle time of the first bearer reaches the preset time based on open overtime monitoring, wherein the release indication information is used for indicating the PGW to execute a release operation on the first bearer;

and receiving release response information sent by the PGW, wherein the release response information is used for indicating whether the release operation is successfully executed.

3. The method of claim 1 or 2, wherein the receiving the first bearer stream for the first User Equipment (UE) comprises:

receiving a first bearer stream transmitted by the first UE forwarded by a base station;

before the receiving the first bearer flow transmitted by the first UE forwarded by the base station, the method further includes:

receiving a default bearer stream transmitted by the first UE forwarded by the base station;

sending, to the PGW, creation indication information when the default bearer flow needs to be shunted and the default bearer flow is used to trigger creation of the first bearer, where the creation indication information is used to indicate the PGW to create the first bearer.

4. The method according to claim 3, wherein the default bearer flow carries internet IP quintuple information of the default bearer flow, and after the receiving the default bearer flow sent by the first UE and forwarded by the base station, the method further comprises:

judging whether the IP quintuple information of the default bearer stream meets a first preset rule or not;

determining that the default bearer flow needs to be shunted under the condition that the IP quintuple information of the default bearer flow conforms to the first preset rule;

judging whether the IP quintuple information of the default bearer stream conforms to a preset creation rule of the edge gateway or not;

and determining that the default bearer flow is used for triggering the creation of the first bearer under the condition that the IP five-tuple information of the default bearer flow conforms to the creation rule.

5. The method according to claim 1 or 2, wherein the first bearer flow carries a quality of service, Qos, parameter of the first bearer flow, and after the starting of the timeout monitoring for the first bearer, the method further comprises:

sending modification indication information to the PGW when it is detected that the Qos parameter of the first bearer flow changes, where the modification indication information is used to indicate the PGW to modify the Qos parameter of the first bearer flow to the Qos parameter of the first bearer flow;

receiving modification response information sent by the PGW, where the modification response information is used to indicate whether a modification operation of the Qos parameter of the first bearer is successfully executed.

6. The method according to claim 1 or 2, wherein said initiating a timeout monitoring for the first bearer comprises:

and setting the aging duration corresponding to the first load, wherein the aging duration is the same as the preset duration.

7. The method of claim 4, wherein the creation rule is a network layer protocol and a transport layer protocol of the Open Systems Interconnection (OSI) reference model, or an application layer protocol.

8. The method of claim 1 or 2, wherein sending the first bearer flow to an edge server if the first bearer flow is a proprietary bearer flow comprises:

and sending the first bearer flow to the edge server under the condition that the first bearer is a proprietary bearer and the first bearer flow needs to be shunted.

9. The method according to claim 8, wherein the first bearer flow carries IP quintuple information of the first bearer flow, and after the receiving the first bearer flow of the first user equipment UE, the method further comprises:

acquiring a bearing identifier of the first bearing;

determining that the first bearer is a dedicated bearer under the condition that the bearer identifier of the first bearer belongs to a preset dedicated bearer identifier set, wherein the preset dedicated bearer identifier set comprises the bearer identifier of the dedicated bearer;

judging whether the IP quintuple information of the first bearing stream meets a second preset rule or not;

and under the condition that the IP quintuple information of the first bearer flow conforms to the second preset rule, determining that the first bearer flow needs to be shunted.

10. The method according to claim 1 or 2,

the offloading indication information includes the device identifier of the first UE, the gateway identifier of the edge gateway, and the bearer identifier of the first bearer.

11. The method of claim 3, wherein after the sending creation indication information to the PGW, the method further comprises:

and receiving 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 successfully executed.

12. A method of processing a proprietary bearer stream, the method comprising:

receiving distribution indication information sent by an edge gateway, wherein the distribution indication information is generated after the edge gateway sends a first bearer flow of first User Equipment (UE) to an edge server;

closing overtime monitoring aiming at a first bearer based on the shunting indication information, wherein the overtime monitoring is used for monitoring whether the idle time of the first bearer reaches a preset time, and the first bearer is used for transmitting the first bearer;

and sending closing response information to the edge gateway, wherein the closing response information is used for indicating the edge gateway to start the timeout monitoring for the first bearer.

13. The method of claim 12, wherein after sending the shutdown response message to the edge gateway, the method further comprises:

receiving release indication information sent by the edge gateway, wherein the release indication information is generated by the edge gateway under the condition that the open overtime monitoring monitors that the idle time of the first bearer reaches the preset time;

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

and sending release response information to the edge gateway, wherein the release response information is used for indicating whether the release operation is successfully executed.

14. The method according to claim 12 or 13, wherein the first bearer stream is sent by the first UE to the edge gateway via a base station, and before the receiving the offloading indication information sent by the edge gateway, the method further comprises:

receiving creation indication information sent by the edge gateway;

creating the first bearer based on the creation indication information;

wherein the creation indication information is generated by the edge gateway when detecting that a default bearer flow needs to be shunted and the default bearer flow is used for triggering creation of the first bearer, and the default bearer flow is sent by the first UE to the edge gateway through the base station.

15. The method according to claim 12 or 13, wherein the first bearer flow carries a quality of service Qos parameter of the first bearer flow, and after the sending of the close response information to the edge gateway, the method further comprises:

receiving modification indication information sent by the edge gateway, wherein the modification indication information is generated by the edge gateway when the change of the Qos parameter of the first bearer flow is detected;

modifying the QoS parameter of the first bearer into the QoS parameter of the first bearer flow based on the modification indication information;

sending 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 successfully performed.

16. The method according to claim 12 or 13, wherein the closing of the timeout monitoring for the first bearer based on the offloading indication information comprises:

and controlling the aging duration corresponding to the first bearer to be in a failure state, wherein the aging duration is the same as the preset duration.

17. The method according to claim 12 or 13,

18. The method according to claim 14, wherein after the creating the first bearer based on the creation indication information, the method further comprises:

and sending creation response information to the edge gateway, wherein the creation response information is used for indicating that the creation operation of the first bearer is successfully executed.

19. A device for processing a proprietary bearer stream, the device comprising:

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

a first sending module, configured to send the first bearer flow to an edge server when the first bearer flow is a dedicated bearer flow, so as to split the first bearer flow;

a second sending module, configured to send, to a packet data network gateway PGW, offload indication information, where the offload indication information is used to indicate that the PGW closes timeout monitoring for a first bearer used for transmitting the first bearer, and the timeout monitoring is used to monitor whether an idle duration of the first bearer reaches a preset duration;

an opening module, configured to open timeout monitoring for the first bearer when receiving a close response message sent by the PGW, where the close response message is used to indicate that the PGW has closed the timeout monitoring for the first bearer.

20. The apparatus of claim 19,

the second sending module is further configured to send release indication information to the PGW when it is monitored based on the started timeout monitoring that the idle duration of the first bearer reaches the preset duration, where the release indication information is used to indicate the PGW to perform a release operation on the first bearer;

the device further comprises:

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

21. The apparatus of claim 20, wherein the first receiving module is configured to:

the first receiving module is further configured to receive a default bearer stream sent by the first UE and forwarded by the base station;

the second sending module is further configured to send creation indication information to the PGW when the default bearer flow needs to be shunted and the default bearer flow is used to trigger creation of the first bearer, where the creation indication information is used to indicate the PGW to create the first bearer.

22. The apparatus of claim 21, wherein the default bearer flow carries internet IP quintuple information of the default bearer flow, the apparatus further comprising:

the first judgment module is used for judging whether the IP quintuple information of the default bearer flow accords with a first preset rule or not;

a first determining module, configured to determine that the default bearer flow needs to be shunted when the IP quintuple information of the default bearer flow conforms to the first preset rule;

the first judging module is further configured to judge whether the IP quintuple information of the default bearer stream conforms to a creation rule preconfigured by the edge gateway;

the first determining module is further configured to determine that the default bearer flow is used to trigger creation of the first bearer, when the IP quintuple information of the default bearer flow conforms to the creation rule.

23. The apparatus of claim 20, wherein the first bearer flow carries a quality of service (Qos) parameter of the first bearer flow,

the second sending module is further configured to send modification indication information to the PGW when it is detected that the Qos parameter of the first bearer flow changes, where the modification indication information is used to indicate the PGW to modify the Qos parameter of the first bearer flow to the Qos parameter of the first bearer flow;

the second receiving module is further configured to receive 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 successfully executed.

24. The apparatus of claim 19 or 20, wherein the activation module is configured to:

25. The apparatus of claim 22, wherein the creation rule is a network layer protocol and a transport layer protocol of an Open Systems Interconnection (OSI) reference model, or an application layer protocol.

26. The apparatus of claim 19 or 20, wherein the first sending module is configured to:

27. The apparatus of claim 26, wherein the first bearer flow carries IP quintuple information of the first bearer flow, and wherein the apparatus further comprises:

an obtaining module, configured to obtain a bearer identifier of the first bearer;

a second determining module, configured to determine that the first bearer is a dedicated bearer when a bearer identifier of the first bearer belongs to a preset dedicated bearer identifier set, where the preset dedicated bearer identifier set includes a bearer identifier of the dedicated bearer;

the second judgment module is used for judging whether the IP quintuple information of the first bearing stream meets a second preset rule or not;

the second determining module is configured to determine that the first bearer flow needs to be shunted when the IP quintuple information of the first bearer flow conforms to the second preset rule.

28. The apparatus of claim 19 or 20,

29. The apparatus of claim 21,

the second receiving module is further configured to receive 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 successfully executed.

30. A device for processing a proprietary bearer stream, the device comprising:

a receiving module, configured to receive distribution indication information sent by an edge gateway, where the distribution indication information is generated after the edge gateway sends a first bearer stream of a first User Equipment (UE) to an edge server;

a closing module, configured to close an timeout monitor for a first bearer based on the offloading indication information, where the timeout monitor is configured to monitor whether an idle duration of the first bearer reaches a preset duration, and the first bearer is configured to transmit the first bearer stream;

a sending module, configured to send a close response message to the edge gateway, where the close response message is used to instruct the edge gateway to start timeout monitoring for the first bearer.

31. The apparatus of claim 30,

the receiving module is further configured to receive release indication information sent by the edge gateway, where the release indication information is generated by the edge gateway when it is monitored based on the opened timeout monitor that the idle duration of the first bearer reaches the preset duration;

the device further comprises:

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

32. 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 further comprises:

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

33. The apparatus according to claim 30 or 31, wherein the first bearer flow carries a quality of service (Qos) parameter of the first bearer flow,

the receiving module is further configured to receive modification indication information sent by the edge gateway, where the modification indication information is generated by the edge gateway when the change of the Qos parameter of the first bearer stream is detected;

the device further comprises:

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

the sending module is further configured to send 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 successfully executed.

34. The apparatus of claim 30 or 31, wherein the shutdown module is configured to:

35. The apparatus of claim 30 or 31,

36. The apparatus of claim 32,

the sending module is further configured to send a create response message to the edge gateway, where the create response message is used to indicate that the creating operation of the first bearer is successfully executed.

37. A processing system for exclusively carrying a stream, comprising: an edge gateway and a PGW,

the edge gateway comprising processing means for exclusively carrying streams as claimed in any one of claims 19 to 29;

the PGW comprising a processing apparatus for exclusively carrying streams as claimed in any one of claims 30 to 36.

38. A device for processing a proprietary bearer stream, the device comprising: the system comprises a processor, a memory, a network interface and a bus, wherein the bus is used for connecting the processor, the memory and the network interface;

the network interface is used for realizing 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 special bearer stream according to any one of claims 1 to 11 or the processing method of the special bearer stream according to any one of claims 12 to 18.

39. A computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of processing a proprietary bearer stream of any one of claims 1 to 11, or the method of processing a proprietary bearer stream of any one of claims 12 to 18.