WO2017143915A1

WO2017143915A1 - Method and device for throttling bandwidth of access point

Info

Publication number: WO2017143915A1
Application number: PCT/CN2017/073358
Authority: WO
Inventors: 吴锦花; 朱进磊; 陈东华; 周晓云; 朱宜斌
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-02-22
Filing date: 2017-02-13
Publication date: 2017-08-31
Also published as: CN107105457B; CN107105457A

Abstract

Disclosed herein is a method for throttling a bandwidth of an access point, the method comprising: establishing a shared access point name-aggregate maximum bit rate (APN-AMBR) statistical table for a plurality of gateway user (GwU) modules; after a GwU module receives a data packet, accessing the shared APN-AMBR statistical table of a user equipment corresponding to the data packet under a current access point; compiling statistics on the APN-AMBR of the user equipment under the current access point according to measurement information of the current data packet and an APN-AMBR value obtained by accessing the shared APN-AMBR statistical table; and performing APN-AMBR-based bandwidth throttling according to the statistics results.

Description

Method and device for realizing access point bandwidth limitation

Technical field

The present application relates to, but is not limited to, the field of wireless communication technologies, and in particular, to a method and apparatus for implementing access point bandwidth limitation.

Background technique

As shown in FIG. 1, the 3rd Generation Partnership Project (EPS) Evolved Packet System (EPS) is an evolved universal mobile communication system terrestrial radio access network (E-UTRAN, Evolved Universal Terrestrial) Radio Access Network), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (PDN GW or P-GW, Packet Data Network Gateway), Home Subscriber Server (HSS) , Home Subscriber Server), 3GPP Authentication, Authorization and Accounting (AAA), Policy and Charging Rules Function (PCRF) and other supporting nodes.

The MME is used for control plane related operations such as mobility management, non-access stratum signaling processing, and user mobility management context management; the S-GW is an access gateway device connected to the E-UTRAN, in the E-UTRAN and The P-GW forwards data and buffers the paging waiting data. The P-GW is a border gateway between the EPS and the PDN, and is used for PDN access and forwarding data between the EPS and the PDN. The PCRF is responsible for the formulation of policy decisions and charging rules, providing gating, quality of service control, and charging rules based on service data flows to the gateway, and executing the policies and charging rules established by the PCRF on the bearer plane. When the bearer is established, the gateway performs QoS (Quality of Service) authorization and gating control according to the rules sent by the PCRF. The corresponding service data flow charging operation is performed according to the charging rule sent by the PCRF.

In the EPS system, the control plane of the gateway is highly coupled with the forwarding plane, which is not conducive to the smooth evolution of the core network. Therefore, the control functions and forwarding functions in the packet domain gateway can be further separated to meet the needs of network development and market applications.

2 is an architecture of a gateway control plane and a user plane separated in a non-roaming scenario. The architecture splits the S-GW and the P-GW in the original EPS architecture into two functional network elements: GwC (Gateway Controller) and GwU (Gateway User). GwC is responsible for the control plane functions of S-GW and P-GW, including load sharing, GwU selection, IP address and tunnel identification assignment, policy and charging control. GwU is responsible for user plane related functions of S-GW and P-GW, including data stream identification and deep packet parsing, QoS processing and bearer binding, and buffering of downlink paging data.

In order to access a Packet Data Network (PDN), a UE (User Equipment) establishes a PDN connection of an IP-Connected Access Network (IP-CAN) session. A PDN connection consists of a bearer, and a bearer consists of a service data stream. The network provides network resources for data transmission for its service data flow according to the corresponding authorized QoS, and the service data flows in the same bearer have the same QoS parameters, that is, the same bearer QoS characteristics. Related QoS parameters include QoS Class Identifier (QCI), Resource Allocation and Retention Priority (ARP), Guaranteed Band Rate (GBR), and Maximum Bit Rate (MBR). And the QoS parameters UE-AMBR (User Equipment Aggregate Maximum Bit Rate) and the APN-AMBR (Access Point Node Aggregate Maximum Bit Rate) Inbound aggregation maximum bit rate (access point maximum bandwidth)).

The bearer is divided into a GBR bearer and a non-GBR bearer: the GBR bearer includes the MBR and the GBR, which is the bearer that guarantees the lowest bandwidth; the non-GBR bearer only includes the MBR, and is the bearer that provides the best effort bandwidth. When the UE attaches to the network to establish a PDN connection, a default bearer is established, and a dedicated bearer is established for the data service with higher QoS requirements. Usually the proprietary bearer QoS is higher than the default bearer QoS requirement. The default bearer must be a Non-GBR bearer. The dedicated bearer can be a GBR bearer or a Non-GBR bearer.

APN-AMBR is a subscription parameter for each APN stored in the HSS. This parameter limits the maximum bit rate of non-GBR bearers for all PDN connections under the same APN. Each non-GBR bearer may occupy all APN-AMBR bandwidths, for example when other non-GBR bearers do not have any data traffic. APN-AMBR only targets non-GBR bearers, excluding GBR Carrying. The P-GW performs bandwidth limitation on the uplink and downlink data flows of the non-GBR bearers connected to all PDNs in the APN according to the APN-AMBR value signed in the HSS. All simultaneously activated PDN connections on the same APN of one UE are on the same PGW. That is, even if the UE supports the single APN multi-PDN connection function, all simultaneously activated associations of the UE to the PDN connection under the same APN are also provided by the same PGW. Therefore, the current APN-AMBR only needs to be executed on the P-GW corresponding to the APN.

However, for the architecture of the gateway control plane and the user plane separation, the P-GW is divided into multiple GwC instances and multiple GwU instances. Due to the problem of multiple sessions and multiple bearers, the data flow distribution on the GwU cannot be guaranteed to be the same. All PDN connections of the same APN are distributed to the same GwU instance. For example, some UEs use static addresses. If the IP segment of the part is bound to the corresponding GTPU (GPRS Tunnel Protocol User Plane) node, That is, the IP segment of the part corresponds to the corresponding GwU instance, but the part of the UE is switched between the GTP (GPRS Tunnel Protocol) and the PMIP (Proxy Mobile IP) protocol, and the UE selects before and after. It may be two GwU instances, so APN-AMBR cannot perform bandwidth statistics and restrictions on the same GwU.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The present invention provides a method and apparatus for implementing access point bandwidth limitation, which can accurately perform bandwidth control based on an access point aggregation maximum bit rate APN-AMBR in a gateway control plane and a user plane separation architecture.

A method for implementing bandwidth limitation of an access point, the method comprising:

Establishing a shared access point aggregation maximum bit rate APN-AMBR statistical table for multiple gateway user plane GwU modules;

When receiving the data packet, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, and obtains according to the measurement information of the current data packet and the access to the shared APN-AMBR statistics table. APN-AMBR value is currently accessed by the user equipment The APN-AMBR is used for statistics, and the bandwidth control based on APN-AMBR is performed according to the statistical result.

In an embodiment, the establishing a shared access point aggregation maximum bit rate APN-AMBR statistics table for multiple GwU modules includes:

The shared APN-AMBR statistics table is established in an independent GwU instance, or the shared APN-AMBR statistics table is established in a shared memory of multiple GwU instances.

In an embodiment, the shared APN-AMBR statistics table is accessed or modified by the GwU module. Only one GwU module has the right to access or modify the shared APN-AMBR statistics table at the same time.

In one embodiment, one or more GwU instances exist in the GwU module, each GwU instance processes service data of multiple user equipments, and multiple GwU instances share an APN-AMBR statistics table; one gateway control plane exists under the GwC module. Or multiple GwU modules.

In an embodiment, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point when receiving the data packet, according to the measurement information of the current data packet, and accessing the sharing. The APN-AMBR value obtained by the APN-AMBR statistic is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistical result, including:

When receiving the data packet, the GwU service instance sends a request for accessing the shared APN-AMBR statistics table to the independent GwU shared data table instance, where the identifier of the shared APN-AMBR statistics table to be accessed, and the measurement information of the current data packet are carried;

After receiving the request for accessing the shared APN-AMBR statistics table, the GwU shared data table instance is in the user equipment according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR of the current access point performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the decision is made to allow the data packet to be forwarded. For example, the APN-AMBR value after the statistics is greater than the user equipment. The contract value is used to decide to discard the data packet, and return a response message to the GwU service instance, where the decision indication information is carried;

Receiving, by the GwU service instance, a response message returned by the GwU shared data table instance Afterwards, forwarding or discarding the data packet according to the decision indication information carried in the response message;

The shared APN-AMBR statistics table records the APN-AMBR value of each user equipment under the access point.

The GwU service instance accesses the shared APN-AMBR statistics table stored in the shared memory, and the user equipment is under the current access point according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the data packet is forwarded. If the APN-AMBR value is greater than the subscription value of the user equipment, the data packet is discarded.

A device for implementing bandwidth limitation of an access point, comprising:

Setting a module, configured to establish a shared access point aggregation maximum bit rate APN-AMBR statistical table for multiple gateway user plane GwU modules;

The bandwidth control module is configured to: when the GwU module receives the data packet, access the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet and accessing the shared APN- The APN-AMBR value obtained by the AMBR statistics table counts the APN-AMBR of the user equipment at the current access point, and performs bandwidth control based on the APN-AMBR according to the statistical result.

In one embodiment, the setup module is set to:

In an embodiment, the GWU module uses a lock mutual exclusion mechanism to access or modify the shared APN-AMBR statistics table, and only one GwU module has permission to access or modify the same time. Share the APN-AMBR statistics table.

In one embodiment, the bandwidth control module is configured to:

After receiving the response message returned by the GwU shared data table instance, the GwU service instance forwards or discards the data packet according to the decision indication information carried in the response message;

In one embodiment, the bandwidth control module is configured to:

A computer readable storage medium storing computer executable instructions, the computer being executable The above method is implemented when the line instruction is executed by the processor.

A method and device for implementing bandwidth limitation of an access point according to an embodiment of the present invention, for establishing a maximum access rate aggregation APN-AMBR statistics table for a plurality of gateway user plane GwU modules, when the GwU module receives a data packet Accessing the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, and the user equipment according to the current data packet measurement information and the APN-AMBR value obtained by accessing the shared APN-AMBR statistics table The APN-AMBR under the current access point performs statistics, and the APN-AMBR-based bandwidth control is performed according to the statistics. In this embodiment of the present invention, bandwidth control can be accurately performed in the gateway control plane and the user plane separation architecture, and the network is guaranteed to be contracted according to the user. The APN-AMBR performs the correct bandwidth limitation and data flow gating restrictions.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a schematic structural diagram of a 3GPP evolved packet system in the related art.

FIG. 2 is a schematic structural diagram of separation of a gateway control plane and a user plane in a non-roaming scenario.

FIG. 3 is a flowchart of a method for implementing bandwidth limitation of an access point according to an embodiment of the present invention.

FIG. 4 is a schematic diagram of an apparatus for implementing bandwidth limitation of an access point according to an embodiment of the present invention.

FIG. 5 is a schematic diagram (shared example) of bandwidth restriction information interaction of a pair of uplink data streams according to an example of the present invention.

FIG. 6 is a schematic diagram (shared example) of bandwidth restriction information interaction of a second pair of downlink data streams according to an example of the present invention.

FIG. 7 is a schematic diagram (shared memory) of bandwidth limitation information interaction of an example three pairs of uplink data streams according to an example of the present invention.

FIG. 8 is a schematic diagram of a bandwidth restriction information interaction (shared memory) of an example four pairs of downlink data streams according to the present invention.

Embodiments of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The embodiments in the present application and the features in the embodiments may be arbitrarily combined with each other without conflict.

As shown in FIG. 3, an embodiment of the present invention provides a method for implementing bandwidth limitation of an access point, where the method includes:

S301. Establish a shared access point aggregation maximum bit rate APN-AMBR statistics table for multiple gateway user plane GwU modules.

S302. When receiving the data packet, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet, and accesses the shared APN-AMBR statistics table. The obtained APN-AMBR value is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and perform bandwidth control based on the APN-AMBR according to the statistical result.

The method for establishing a shared access point aggregation maximum bit rate APN-AMBR statistics table for multiple GwU modules includes:

Establishing the shared APN-AMBR statistic table in an independent GwU instance, or establishing the shared APN-AMBR statistic table in a shared memory of multiple GwU instances;

The GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point when receiving the data packet, according to the measurement information of the current data packet and accessing the shared APN-AMBR statistics. The APN-AMBR value obtained by the table is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistics, including:

After receiving the request for accessing the shared APN-AMBR statistics table, the GwU shared data table instance is based on the measurement information of the current data packet and the record in the shared APN-AMBR statistics table. The recorded APN-AMBR value is used to count the APN-AMBR of the user equipment at the current access point. If the APN-AMBR value after the statistics is smaller than the subscription value of the user equipment, the decision is allowed to forward the data packet, such as after statistics. If the APN-AMBR value is greater than or equal to the subscription value of the user equipment, the data packet is discarded, and the response message is returned to the GwU service instance, where the decision indication information is carried;

The GwU module uses a lock mutual exclusion mechanism to access or modify the shared APN-AMBR statistics table. Only one GwU module has the right to access or modify the shared APN-AMBR statistics table at the same time;

One or more GwU instances exist in the GwU module. Each GwU instance processes service data of multiple user equipments. Multiple GwU instances share the APN-AMBR statistics table. One GwU module has one or more GwUs under the GwC module. Module

As shown in FIG. 4, an embodiment of the present invention provides an apparatus for implementing bandwidth limitation of an access point, including:

The setting module 401 is configured to establish a shared access point aggregation maximum bit rate APN-AMBR statistics table for the plurality of gateway user plane GwU modules;

The bandwidth control module 402 is configured to: when the GwU module receives the data packet, access the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet, and access the shared APN. The APN-AMBR value obtained by the -AMBR statistic is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistical result.

Wherein, the setting module 401 is set to:

The GWU module uses the lock mutual exclusion mechanism to access or modify the shared APN-AMBR statistics table. Only one GwU module has the right to access or modify the shared APN-AMBR statistics table at the same time.

One or more GwU instances exist in the GwU module. Each GwU instance processes service data of multiple user equipments. Multiple GwU instances share the APN-AMBR statistics table. One GwU module has one or more GwUs under the GwC module. Module.

The bandwidth control module 402 is configured to:

The shared APN-AMBR statistic table records each user equipment under the access point. APN-AMBR value.

The bandwidth control module 402 is configured to:

Example one

As shown in Figure 5, this example corresponds to the non-roaming scenario. The UE accesses the 3GPP network and creates a default bearer after activation. The user session table and bearer forwarding table are established for the user on the GwU. The user is obtained and saved on the GwC. Policies such as QoS authorization information, PCC (Policy and Charging Control) rules. By establishing a shared statistics table for each GwU instance, which is stored in a separate GwU instance, the GwU performs APN-AMBR-based bandwidth control on the non-GBR bearer data stream of the UE uplink, including the following steps:

Step 501: The GwU receiving instance receives the uplink data packet. The uplink packet is identified as a GPRS Tunnel Protocol User Plane (GPRS Tunnel Protocol User Plane) message, and the forwarding table is found to find a corresponding GwU service instance of the user service.

Step 502: The GwU receiving instance forwards the data stream to the found GwU service instance.

Step 503: The GwU service instance performs bearer forwarding table matching according to the TEIDU (Tunnel terminal identification for user plane), and performs internal quintuple matching after decapsulating the data. If the corresponding flow table and policy are matched, step 510 is performed.

Step 504: If the current flow table and the policy are not matched, a new flow table is created, and the data packet is forwarded to the GwU DPI (Deep Packet Inspection) instance to identify the application information of the data flow.

Step 505: After the GwU DPI instance matches the related service information according to the local signature database, the GwU DPI instance returns information such as the packet and the corresponding application identifier to the GwU service instance.

Step 506: The GwU service instance performs a TFT (Traffic Flow Template) matching according to the received application identifier. If the corresponding flow table and policy are matched, step 510 is performed; if the application identifier is not recognized (Failed to match the corresponding flow table and policy), or if the change occurs, the message is cached, and step 507 is performed.

Step 507: The GwU service instance sends the TEIDU, the quintuple information, and the application identifier of the packet to the GwC, and obtains corresponding QoS policy and charging information.

Step 508: The GwC obtains the local policy according to the application identifier and the quintuple information carried in the request message, or requests the policy rule information from the external (PCRF, etc.).

Step 509: The GwC returns the policy information (including the information of the QoS, the charging, and the routing and forwarding policy) provided by the local or external policy decision entity (such as the PCRF) to the GwU service instance for policy execution.

Step 510: The GwU service instance performs a bearer-level QoS policy such as uplink gating according to the current policy (the local policy or the policy provided by the GwC), performs bearer binding, performs metering of usage statistics and usage statistics of the uplink data, and updates the traffic to the traffic. In the table.

Step 511: After performing the bearer-related policy, charging, and usage statistics, the GwU service instance sends a request message to the GwU sharing statistics table instance, requesting the APN-AMBR decision indication, or the current APN-AMBR value. The request message carries the APN-AMBR identification information (for example, the ID of the APN-AMBR shared meter), the measurement information of the current data (for example, meter statistics), and the TEID and quintuple information.

Step 512: The GwU sharing statistics table instance receives the request message that carries the measurement information and the APN-AMBR identification information sent by the GwU service instance. The unified APN-AMBR subscription information and the local APN-AMBR shared measurement statistics table are compared, and the unified measurement statistics are performed according to the measurement information carried in the request message. After the statistics, when the maximum bit rate of all non-GBR bearers of the UE under the APN is greater than the subscribed APN-AMBR, it is determined to discard the data stream. If the maximum bit rate of all non-GBR bearers of the UE under the APN is smaller than the subscribed APN-AMBR, the data stream may be sent. Update current APN-AMBR shared measurements A statistical table that determines the discarding or forwarding of current data streams. And return the decision indication to the GwU service instance that sent the request. The execution of the statistics entry between the GwU instances uses the lock mutual exclusion mechanism to ensure that only one GwU instance has permission to access or modify the statistics table.

Step 513: The GwU sharing statistics table instance returns the APN-AMBR decision response to the GwU service instance that sends the request, and carries the APN-AMBR indication flag, indicating that the current data stream is discarded or forwarded. The message may carry the value of the current APN-AMBR of the shared statistics table.

Step 514: The GwU service instance receives the response message from the GwU shared statistics table instance, where the response message carries the APN-AMBR execution indication flag, and may also carry the APN-AMBR value. The meter statistics of the billing and usage of the current uplink data are reduced, and the flow table is updated. If the APN-AMBR value is greater than the subscription allowable value, or indicates that the APN-AMBR exceeds the threshold, the data flow cannot be sent and is gated by the execution. If the APN-AMBR value is less than the allowed value of the subscription, or indicates that the APN-AMBR is within the allowed range, the information to be carried, such as binding bearer information, routing and forwarding information, is enhanced into the packet header, and the data packet is encapsulated.

Step 515: Confirm that within the range of APN-AMBR allowed by the subscription, the GwU service instance sends the data packet to the next routing node or the external PDN network node according to the routing and forwarding policy of the data packet.

In the above steps 501-515, for the uplink data stream, the shared data statistics table is stored in the independent GwU shared data table instance, and the execution of the statistics entry between the GwU service instances adopts a lock mutual exclusion mechanism to ensure that there is only one GwU at the same time. The instance has permission to access or modify the statistics.

The GwU instance in this embodiment may be a logical function entity in the actual deployment network element, or an independent actual deployment network element; or may be a virtualization function device or a processor in the function device, or It is a network slice or micro service that is virtualized. This application is not limited.

Example two

As shown in Figure 6, this example corresponds to a non-roaming scenario. The UE accesses the 3GPP network and creates a default bearer after activation. The user session table and bearer forwarding table are established for the user on the GwU. The user is obtained and saved on the GwC. QoS authorization information, PCC rules and other strategies. By for each The GwU instance establishes a shared APN-AMBR statistic table (the shared statistic table is stored in an independent GwU shared data table instance), and the GwU performs APN-AMBR-based bandwidth control on the downlink non-GBR bearer data stream, including the following steps:

Step 601: The GwU receiving instance receives the downlink data packet.

Step 602: The GwU receiving instance identifies that the data packet is a downlink packet, and finds a GwU service instance corresponding to the user service according to the IP lookup forwarding table.

Step 603: The GwU forwards the data packet to the corresponding GwU service instance.

Step 604: The GwU service instance matches the user session table according to the IP and virtual routing forwarding table VRF (Virtual Routing and Forwarding), and performs quintuple matching. If the downlink data packet matches the flow table, it is determined according to the flag in the flow table whether to send to the GwU DPI instance for further analysis. If the GwU DPI instance needs to be sent for further analysis, step 605 is performed; if the corresponding flow table and policy are matched, and the GwU DPI instance is not required to be further analyzed, step 611 is performed; if the corresponding flow table is not matched, Then, the flow table is created, the message is cached, and step 608 is performed.

Step 605: Cache the packet, and send the key information of the data packet to the GwU DPI instance to identify the information such as the application identifier of the data stream.

Step 606: After the GwU DPI instance matches the related service information according to the local signature database, the GwU DPI instance returns information such as the packet and the corresponding application identifier to the GwU service instance.

Step 607: The GwU service instance performs TFT matching such as quintuple according to the received application identifier. If the corresponding flow table and policy are matched, step 611 is performed; if the application identifier cannot be identified or changed, The message is cached, and step 608 is performed.

Step 608: The GwU service instance sends a Get Processing Policy Request message to the GwC, where the request message carries the TEIDU, the quintuple information, and the application identifier of the packet.

Step 609: The GwC obtains a local policy according to information such as an application identifier and a quintuple carried in the request message, or requests policy rule information from an external (for example, a PCRF).

Step 610: The GwC returns information of the QoS and charging, and routing and forwarding policies provided by the local or external policy decision entity (such as the PCRF) to the GwU service instance for policy execution.

Step 611: The GwU service instance performs a bearer-level QoS policy such as a downlink gating according to the current policy (the local policy or the policy provided by the GwC), performs bearer binding, performs meter statistics of the downlink data charging and usage, and updates the traffic to the flow. In the table.

Step 612: After performing the bearer-related policy and charging and usage statistics, the GwU service instance sends a request message to the GwU sharing statistics table instance, requesting the APN-AMBR decision indication, or the current APN-AMBR value. The request message carries the APN-AMBR identification information (for example, the ID of the APN-AMBR shared meter), the measurement information of the current data (for example, meter statistics), and the TEID and quintuple information. The execution of the statistics entry between the GwU instances uses the lock mutual exclusion mechanism to ensure that only one GwU instance has permission to access or modify the statistics table.

Step 613: The GwU sharing statistics table instance receives the request message carrying the measurement information and the APN-AMBR identification information sent by the GwU service instance. The unified APN-AMBR subscription information and the local APN-AMBR shared measurement statistics table are compared, and the unified measurement statistics are performed according to the measurement information carried in the request message. After the statistics, when the maximum bit rate of all non-GBR bearers of the UE under the APN is greater than the subscribed APN-AMBR, it is determined to discard the data stream. If the maximum bit rate of all non-GBR bearers of the UE under the APN is smaller than the subscribed APN-AMBR, the data stream may be sent. Update the current APN-AMBR shared measurement statistics table to decide whether to discard or forward the current data stream. And return the decision indication to the GwU service instance that sent the request.

Step 614: The GwU sharing statistics table instance returns a decision response of the APN-AMBR to the GwU service instance that sends the request, and carries an APN-AMBR indication flag, indicating that the current data stream is discarded or forwarded. The message may carry the value of the current APN-AMBR of the shared statistics table.

Step 615: The GwU service instance receives the response message from the GwU shared statistics table instance, where the response message carries the APN-AMBR execution indication flag, and may also carry the APN-AMBR value. The meter statistics of the billing and usage of the current downlink data are reduced, and the flow table is updated. If the APN-AMBR value is greater than the subscription allowable value, or indicates that the APN-AMBR exceeds the threshold, the data flow cannot be sent and is gated by the execution. If the APN-AMBR value is less than the allowed value of the subscription, or indicates that the APN-AMBR is within the allowed range, the information to be carried, such as binding bearer information, routing and forwarding information, is enhanced into the packet header, and the data packet is encapsulated.

Step 616: Confirm that the GwU service instance root is within the range of the APN-AMBR allowed for the subscription. The data packet is delivered according to the routing and forwarding policy of the data packet.

In the following steps 601-616, for the downlink data stream, the shared data statistics table is stored in the independent GwU shared data table instance, and the execution of the statistics entry between the GwU service instances adopts a lock mutual exclusion mechanism to ensure that there is only one at the same time. The GwU instance has permission to access or modify the statistics.

Example three

As shown in Figure 7, this example corresponds to the non-roaming scenario. The UE accesses the 3GPP network and creates a default bearer after activation. The user session table and bearer forwarding table are established for the user on the GwU. The user is obtained and saved on the GwC. QoS authorization information, PCC rules and other strategies. By establishing a shared APN-AMBR statistic table for each GwU instance (the shared statistic table is stored in the shared memory of each GwU instance), the GwU performs APN-AMBR-based bandwidth control on the UE's uplink non-GBR bearer data stream. Including the following steps:

Step 701: The GwU receiving instance receives the uplink data packet. The uplink packet is identified as a user plane data GTPU packet, and the forwarding table is found to find a corresponding GwU service instance of the user service.

Step 702: The GwU receiving instance forwards the data stream to the found corresponding GwU service instance.

Step 703: The GwU service instance performs bearer forwarding table matching according to the TEIDU, and performs internal quintuple matching after decapsulating the data. If the corresponding flow table and policy are matched, step 710 is performed.

Step 704: If the current flow table and the policy are not matched, a new flow table is created, and the data packet is forwarded to the GwU DPI instance to identify the application information of the data flow.

Step 705: After the GwU DPI instance matches the related service information according to the local signature database, the GwU DPI instance returns information such as the packet and the corresponding application identifier to the GwU service instance.

Step 706: The GwU service instance performs a quintuple and other TFTs according to the received application identifier. If the matching of the corresponding flow table and policy is performed, step 710 is performed; if the application identifier is not recognized (failure to match the corresponding flow table and policy), or the change occurs, the message is cached, and the step is performed. 707.

Step 707: The GwU service instance sends the TEIDU, the quintuple information, and the application identifier of the packet to the GwC, and obtains corresponding QoS policy and charging information.

Step 708: The GwC obtains the local policy according to the service identifier and the quintuple information carried in the request message, or requests the policy rule information from the external (PCRF).

Step 709: The GwC returns the information of the policy including the QoS, the charging, and the routing and forwarding, which is provided by the local or the external policy decision entity, such as the PCRF, to the GwU service instance for policy execution.

Step 710: The GwU service instance performs a bearer-level QoS policy such as uplink gating according to the current policy (the local policy or the policy provided by the GwC), performs bearer binding, performs metering of usage statistics and usage statistics of the uplink data, and updates the traffic to the flow. In the table. Access the shared APN-AMBR statistics table in the shared memory of each GwU instance, perform meter measurement, and compare the current APN-AMBR subscription information of the UE. If the maximum bit rate of the non-GBR bearer of the UE under the APN is greater than the subscribed APN-AMBR, the data is subjected to a gating policy and discarded (for example, counted in the discarding traffic). If the maximum bit rate of the non-GBR bearer of the UE in the APN is less than the signed APN-AMBR, the data is re-encapsulated and sent according to the routing policy, such as binding bearer information. Routing and forwarding information is enhanced into the packet header to encapsulate the data packet.

The execution of the statistics entry between the GwU instances uses the lock mutual exclusion mechanism to ensure that only one GwU instance has permission to access or modify the statistics table.

Step 711: Confirm that within the APN-AMBR range allowed by the subscription, the GwU service instance sends the data packet to the next routing node or the external PDN network node according to the routing and forwarding policy of the data packet.

For the uplink data stream, the shared data statistics table is stored in the independent GwU shared data table instance. The execution of the statistics entry between the GwU service instances uses a lock mutual exclusion mechanism to ensure that there is only one GwU at the same time. The instance has permission to access or modify the statistics.

Example four

As shown in Figure 8, this example corresponds to the non-roaming scenario. The UE accesses the 3GPP network and creates a default bearer after activation. The user session table and bearer forwarding table are established for the user on the GwU. The user is obtained and saved on the GwC. QoS authorization information, PCC rules and other strategies. By establishing a shared APN-AMBR statistic table for each GwU instance (the shared statistic table is stored in the shared memory of each GwU instance), GwU performs APN-AMBR-based bandwidth control on the downlink non-GBR bearer data stream, including The following steps:

Step 801: The GwU receiving instance receives the downlink data packet.

Step 802: The GwU receiving instance identifies that the data packet is a downlink packet, and finds a corresponding GwU service instance of the user service according to the IP lookup forwarding table.

Step 803: The GwU receiving instance forwards the data packet to the GwU service instance corresponding to the forwarding table.

Step 804: The GwU service instance matches the user session table according to the IP and virtual route forwarding table VRF, and performs quintuple matching. If the downlink data packet matches the flow table, it is determined according to the flag in the flow table whether to send to the GwU DPI instance for further analysis. If the GwU DPI instance needs to be sent for further analysis, step 805 is performed; if the corresponding flow table and policy are matched, and the GwU DPI instance is not required to be further analyzed, step 811 is performed. If the corresponding flow table is not matched, the flow table is created, the message is cached, and step 808 is performed.

Step 805: If the current flow table is matched, but the GwU DPI is further analyzed according to the flag in the flow table, the packet is buffered, and the key information of the data packet is sent to the GwU DPI instance to perform information identification and the like of the data flow. Identification.

Step 806: After the GwU DPI instance matches the related service information according to the local feature database, The information such as the report and the corresponding application identifier are sent to the GwU service instance.

Step 807: The GwU service instance performs TFT matching such as quintuple according to the received application identifier. If the corresponding flow table and policy are matched, step 811 is performed. If the application identifier is unrecognized or changed, the packet is cached, and step 808 is performed. If the application identifier can be matched to the flow table to obtain a detailed policy, step 811 is performed.

Step 808: The GwU service instance sends a Get Processing Policy Request message to the GwC, where the request message carries the TEIDU, quintuple information, and application identifier of the packet.

Step 809: The GwC obtains a local policy according to the service identifier and the quintuple information carried in the request message, or requests policy rule information from an external (for example, a PCRF).

Step 810: The GwC returns the information provided by the external policy decision entity, such as the QoS and the accounting, and the routing and forwarding, to the GwU service instance, and performs the policy execution.

Step 811: The GwU service instance performs a bearer-level QoS policy such as a downlink gating according to the current policy (the local policy or the policy provided by the GwC), performs bearer binding, performs metering of usage statistics and usage statistics of the downlink data, and updates the traffic to the flow. In the table. Access the shared APN-AMBR statistics table in the shared memory of each GwU instance, perform meter measurement, and compare the current APN-AMBR subscription information of the UE. If the maximum bit rate of the non-GBR bearer of the UE under the APN is greater than the subscribed APN-AMBR, the data is subjected to a gating policy and discarded (for example, counted in the discarding traffic). If the maximum bit rate of the non-GBR bearer of the UE in the APN is less than the signed APN-AMBR, the data is re-encapsulated and sent according to the routing policy, such as binding bearer information. Routing and forwarding information is enhanced into the packet header to encapsulate the data packet.

Step 812: Confirm that the GwU service instance delivers the data packet according to the routing and forwarding policy of the data packet in the range of the APN-AMBR allowed by the subscription.

As shown in the above 801-812, for the downlink data stream, the shared data statistics table is stored in the shared memory of each GwU instance, and the execution of the statistics entry between the GwU service instances is performed by using the lock mutual exclusion. The mechanism ensures that only one GwU instance has permission to access or modify the statistics table at the same time.

In the above example one to the fourth example, the GwU may be forwarded by direct data forwarding or by defining a new interface, which is not limited in this application.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by the processor to implement the above method for realizing access point bandwidth limitation.

The method and device for implementing the bandwidth limitation of the access point provided by the foregoing embodiment are used to establish a shared access point aggregation maximum bit rate APN-AMBR statistics table for multiple gateway user plane GwU modules, and the GwU module accesses when receiving the data packet. The shared APN-AMBR statistics table of the user equipment corresponding to the data packet in the current access point, according to the current data packet measurement information and the APN-AMBR value obtained by accessing the shared APN-AMBR statistics table, the user equipment is currently The APN-AMBR under the access point performs statistics, and performs APN-AMBR-based bandwidth control according to the statistics. In this embodiment of the present invention, bandwidth control can be accurately performed in the gateway control plane and the user plane separation architecture, and the APN secured by the network according to the user is guaranteed. -AMBR performs correct bandwidth limits and data flow gating restrictions.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. All or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, the modules/units in the foregoing embodiments may be implemented in the form of hardware or in the form of software functional modules. This application is not limited to any specific combination of hardware and software.

There may be other various embodiments of the present invention, and those skilled in the art can make corresponding changes and modifications according to the present application without departing from the spirit and scope of the present application, but the corresponding changes and modifications should be It is within the scope of protection of the claims appended hereto.

Industrial applicability

The embodiment of the invention can accurately perform bandwidth control in the gateway control plane and the user plane separation architecture, and ensure that the network performs correct bandwidth limitation and data flow gating restriction according to the APN-AMBR subscribed by the user.

Claims

A method for implementing access point bandwidth limitation includes:

Establishing a shared access point aggregation maximum bit rate APN-AMBR statistical table for multiple gateway user plane GwU modules;

When receiving the data packet, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, and obtains according to the measurement information of the current data packet and the access to the shared APN-AMBR statistics table. The APN-AMBR value is used to count the APN-AMBR of the user equipment under the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistical result.
The method of claim 1 wherein:

The method for establishing a shared access point aggregation maximum bit rate APN-AMBR statistics table for multiple GwU modules includes:

The shared APN-AMBR statistics table is established in an independent GwU instance, or the shared APN-AMBR statistics table is established in a shared memory of multiple GwU instances.
The method of claim 1 wherein:

The GWU module uses a lock mutual exclusion mechanism to access or modify the shared APN-AMBR statistics table. Only one GwU module has the right to access or modify the shared APN-AMBR statistics table at the same time.
The method of claim 1 wherein:

One or more GwU instances exist in the GwU module, each GwU instance processes service data of multiple user equipments, and multiple GwU instances share an APN-AMBR statistics table; one GwU module has one or more GwUs under the GwC module. Module.
The method of claim 2 wherein:

When receiving the data packet, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet, and accesses the shared APN-AMBR statistics table. The obtained APN-AMBR value is current for the user equipment The APN-AMBR under the access point performs statistics, and performs bandwidth control based on APN-AMBR according to the statistics, including:

When receiving the data packet, the GwU service instance sends a request for accessing the shared APN-AMBR statistics table to the independent GwU shared data table instance, where the identifier of the shared APN-AMBR statistical table to be accessed, and the measurement information of the current data packet are carried. ;

After receiving the request for accessing the shared APN-AMBR statistics table, the GwU shared data table instance is in the user equipment according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR of the current access point performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the decision is made to allow the data packet to be forwarded. For example, the APN-AMBR value after the statistics is greater than the user equipment. The contract value is used to decide to discard the data packet, and return a response message to the GwU service instance, where the decision indication information is carried;

After receiving the response message returned by the GwU shared data table instance, the GwU service instance forwards or discards the data packet according to the decision indication information carried in the response message;

The shared APN-AMBR statistics table records the APN-AMBR value of each user equipment under the access point.
The method of claim 2 wherein:

When receiving the data packet, the GwU module accesses the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet, and accesses the shared APN-AMBR statistics table. The obtained APN-AMBR value is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistics, including:

The GwU service instance accesses the shared APN-AMBR statistics table stored in the shared memory, and the user equipment is under the current access point according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the data packet is forwarded. If the APN-AMBR value is greater than the subscription value of the user equipment, the data packet is discarded.

The shared APN-AMBR statistic table records each user equipment under the access point. APN-AMBR value.
A device for implementing bandwidth limitation of an access point, comprising:

Setting a module, configured to establish a shared access point aggregation maximum bit rate APN-AMBR statistical table for multiple gateway user plane GwU modules;

The bandwidth control module is configured to: when the GwU module receives the data packet, access the shared APN-AMBR statistics table of the user equipment corresponding to the data packet at the current access point, according to the measurement information of the current data packet, and access the shared APN. The APN-AMBR value obtained by the -AMBR statistic is used to collect statistics on the APN-AMBR of the user equipment at the current access point, and the bandwidth control based on the APN-AMBR is performed according to the statistical result.
The apparatus of claim 7 wherein:

Set the module to be set to:

The shared APN-AMBR statistics table is established in an independent GwU instance, or the shared APN-AMBR statistics table is established in a shared memory of multiple GwU instances.
The apparatus of claim 7 wherein:

The shared APN-AMBR statistics table is accessed or modified by the GwU module. Only one GwU module has the right to access or modify the shared APN-AMBR statistics table at the same time.
The apparatus of claim 7 wherein:

One or more GwU instances exist in the GwU module. Each GwU instance processes service data of multiple user devices. Multiple GwU instances share the APN-AMBR statistics table. One GwU module exists under one GwC module.
The apparatus of claim 8 wherein:

Bandwidth control module, set to:

When receiving the data packet, the GwU service instance sends a request for accessing the shared APN-AMBR statistics table to the independent GwU shared data table instance, where the identifier of the shared APN-AMBR statistics table to be accessed, and the measurement information of the current data packet are carried;

After receiving the request for accessing the shared APN-AMBR statistics table, the GwU shared data table instance is in the user equipment according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR of the current access point performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the decision is made to allow the data packet to be forwarded. For example, the APN-AMBR value after the statistics is greater than the user equipment. The contract value is used to decide to discard the data packet, and return a response message to the GwU service instance, where the decision indication information is carried;

After receiving the response message returned by the GwU shared data table instance, the GwU service instance forwards or discards the data packet according to the decision indication information carried in the response message;

The shared APN-AMBR statistics table records the APN-AMBR value of each user equipment under the access point.
The apparatus of claim 8 wherein:

Bandwidth control module,

The GwU service instance accesses the shared APN-AMBR statistics table stored in the shared memory, and the user equipment is under the current access point according to the measurement information of the current data packet and the APN-AMBR value recorded in the shared APN-AMBR statistics table. The APN-AMBR performs statistics. If the APN-AMBR value is less than or equal to the subscription value of the user equipment, the data packet is forwarded. If the APN-AMBR value is greater than the subscription value of the user equipment, the data packet is discarded.

The shared APN-AMBR statistics table records the APN-AMBR value of each user equipment under the access point.