CN107105457B

Movatterモバイル変換

Info

Publication number: CN107105457B
Application number: CN201610097438.5A
Authority: CN
Inventors: 吴锦花; 朱进磊; 陈东华; 周晓云; 朱宜斌
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-02-22
Filing date: 2016-02-22
Publication date: 2020-05-15
Anticipated expiration: 2036-02-22
Also published as: WO2017143915A1; CN107105457A

Abstract

The invention discloses a method for realizing access point bandwidth limitation, which comprises the following steps: establishing a shared access point aggregation maximum bit rate APN-AMBR statistical table for a plurality of gateway user plane GwU modules; the GwU module accesses the shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, and performs statistics on the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs bandwidth control based on the APN-AMBR according to the statistical result. The invention can accurately execute the bandwidth control based on the APN-AMBR in the separation architecture of the gateway control plane and the user plane.

Description

Method and device for realizing access point bandwidth limitation

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for implementing access point bandwidth limitation.

Background

As shown in fig. 1, the 3GPP Evolved Packet System (EPS) is composed of an Evolved Universal mobile telecommunications System Terrestrial Radio access Network (E-UTRAN), a Mobility Management unit (MME), a Mobility Management Entity (Mobility Management Entity), a serving Gateway (S-GW), a Packet Data Network Gateway (PDN GW or P-GW), a Packet Data Network Gateway (HSS), a Home Subscriber Server (HSS), an Authentication Authorization and Accounting (AAA) Server of the 3GPP, a Policy and Charging Rules Function (PCRF), and other support nodes.

The MME is used for control plane related work such as mobility management, processing of non-access stratum signaling, management of user mobility management context and the like; the S-GW is an access gateway device connected with the E-UTRAN, forwards data between the E-UTRAN and the P-GW, and is used for caching paging waiting data; the P-GW is a border gateway between the EPS and the PDN, and is used for accessing the PDN and forwarding data between the EPS and the PDN. The PCRF is responsible for making policy decision and charging rules, providing gate control, service quality control and charging rules based on the service data flow to the gateway, and executing the policy and charging rules made by the PCRF on the bearing surface. When the load bearing is established, the gateway carries out QoS authorization and gating control according to the rule sent by the PCRF. And executing corresponding service data flow charging operation 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 favorable for smooth evolution of the core network. Therefore, it is necessary to further separate the control function from the forwarding function in the packet domain gateway to meet the requirements of network development and market application.

Fig. 2 is an architecture in which the gateway control plane and the user plane are separated in a non-roaming scenario. The architecture splits an S-GW and a P-GW in an original EPS architecture into two types of functional network elements, namely GwC (Gateway Controller, Gateway control plane) and GwU (Gateway User plane). GwC is responsible for the control plane functions of S-GW and P-GW, including the functions of load sharing, selection of GwU, allocation of IP address and tunnel identification, policy and charging control, etc. GwU is responsible for the user plane related functions of S-GW and P-GW, including the functions of data flow identification and deep packet analysis, QoS processing and bearing binding, and the buffer storage of downlink paging data.

In order to Access a Packet Data Network (PDN), a UE establishes a PDN connection for an IP Connectivity Access Network (IP-CAN) session. The PDN connection consists of bearers, which consist of traffic data flows. The network provides network resources required by data transmission for the service data flow according to the corresponding authorized QoS, and the service data flows in the same bearer have the same QoS parameters, namely the same bearer QoS characteristics. The related QoS parameters include QoS Class Identifier (QCI) of bearer level, resource Allocation and Retention Priority (ARP), guaranteed bandwidth gbr (guaranteed Bit Rate) and Maximum bandwidth mbr (Maximum Bit Rate), and a plurality of EPS bearer aggregation related QoS parameters UE-AMBR (user equipment Maximum Bit Rate, user equipment aggregation Maximum Bit Rate) and APN-AMBR (Access Point Node aggregation Maximum Bit Rate, Access Point aggregation Maximum Bit Rate (Maximum Access Point bandwidth)).

The bearers are classified into GBR bearers and non-GBR bearers: the GBR bearer comprises MBR and GBR, and is a bearer for ensuring the lowest bandwidth; the non-GBR bearer contains only MBR and is the bearer providing best effort bandwidth. When UE attaches to network to establish PDN connection, default load will be established, and exclusive load will be established for data service with higher QoS requirement. Typically the proprietary bearer QoS is more demanding than the default bearer QoS. The default bearer must be a Non-GBR bearer. The dedicated bearer may be a GBR bearer or a Non-GBR bearer.

APN-AMBR is one subscription parameter per APN stored in HSS. This parameter limits the maximum bit rate of non-GBR bearers for all PDN connections under the same APN. It is possible that each non-GBR bearer occupies all APN-AMBR bandwidth, for example when other non-GBR bearers do not have any data traffic. The APN-AMBR is only for non-GBR bearers and does not include GBR bearers. And the P-GW executes bandwidth limitation on uplink and downlink data flows of non-GBR load of all PDN connections under the APN according to the signed APN-AMBR value in the HSS. All simultaneously activated PDN connections on the same APN of one UE need to be on the same PGW. That is, even if the UE supports single-APN multi-PDN connectivity functionality, all simultaneously activated associations of the UE to PDN connections under the same APN must be provided by the same PGW. Therefore, the current APN-AMBR can be executed on the P-GW corresponding to the APN.

However, for an architecture in which a gateway control Plane and a User Plane are separated, a P-GW is divided into multiple GwC instances and multiple GwU instances, and due to the problem of multiple sessions and multiple bearers, data stream distribution on GwU cannot guarantee that all PDN connections under the same APN of the same User are distributed to the same GwU instance, for example, a part of UEs use static addresses, if an IP segment of the part is already bound to a corresponding GTPU (GPRS Tunnel Protocol User Plane) node, that is, an IP segment of the part corresponds to a corresponding GwU instance, but the part of UEs switch between a GTP (GPRS Tunnel Protocol) and a PMIP (Proxy Mobile IP) Protocol, two GwU instances may be selected before and after the UEs, and thus, the APN-AMBR cannot perform bandwidth statistics and restriction on the same GwU.

Therefore, how to accurately perform APN-AMBR bandwidth control in a gateway control plane and user plane separation architecture is a problem to be researched and solved.

Disclosure of Invention

The technical problem to be solved by the present invention is to provide a method and a device for implementing access point bandwidth limitation, which can accurately execute bandwidth control based on access point aggregation maximum bit rate APN-AMBR in a gateway control plane and user plane separation architecture.

The invention provides a method for realizing access point bandwidth limitation, which comprises the following steps:

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

the GwU module accesses the shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, and performs statistics on the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs bandwidth control based on the APN-AMBR according to the statistical result.

Optionally, a shared access point aggregate maximum bit rate APN-AMBR statistical table is established for the plurality of GwU modules, including:

establishing the shared APN-AMBR statistical table in an independent GwU instance, or establishing the shared APN-AMBR statistical table in a shared memory of a plurality of GwU instances.

Optionally, a lock and mutual exclusion mechanism is used between the GwU modules to access or modify the shared APN-AMBR statistical table, and only one GwU module has the right to access or modify the shared APN-AMBR statistical table at the same time.

Optionally, there are one or more GwU instances in the GwU module, each GwU instance handles traffic data of multiple user equipments, and multiple GwU instances share an APN-AMBR statistics table; one or more GwU modules exist below one gateway control plane GwC module.

Optionally, the GwU module, when receiving the data packet, accesses a shared APN-AMBR statistical table of the ue corresponding to the data packet under the current access point, performs statistics on an APN-AMBR of the ue under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs bandwidth control based on the APN-AMBR according to the statistical result, including:

GwU the service instance sends a request for accessing the shared APN-AMBR statistical table to the independent GwU shared data table instance when receiving the data packet, wherein the request carries the identifier of the shared APN-AMBR statistical table to be accessed and the measurement information of the current data packet;

the GwU shared data table example receives the request for accessing the shared APN-AMBR statistical table, and counts the APN-AMBR of the user equipment 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 statistical table, if the counted APN-AMBR value is less than or equal to the signing value of the user equipment, the decision is made to allow the data packet to be forwarded, if the counted APN-AMBR value is greater than the signing value of the user equipment, the decision is made to discard the data packet, and a response message is returned to the GwU service example, wherein the response message carries decision indication information;

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

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

GwU accessing the shared APN-AMBR statistical table stored in the shared memory by the service instance, counting the APN-AMBR of the user equipment 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 statistical table, if the counted APN-AMBR value is less than or equal to the signing value of the user equipment, forwarding the data packet, if the counted APN-AMBR value is greater than the signing value of the user equipment, discarding the data packet;

The invention also provides a device for realizing the access point bandwidth limitation, which comprises:

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

and the bandwidth control module is used for the GwU module to access a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, to count the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and to perform bandwidth control based on the APN-AMBR according to the statistical result.

Optionally, the setting module is configured to establish a shared access point aggregated maximum bit rate APN-AMBR statistical table for the plurality of GwU modules, and includes:

Optionally, the bandwidth control module, configured to access, by the GwU module, a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when the data packet is received, perform statistics on an APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and an APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and perform bandwidth control based on the APN-AMBR according to a statistical result, includes:

Compared with the prior art, the method and the device for realizing the access point bandwidth limitation establish a shared access point aggregation maximum bit rate APN-AMBR statistical table for a plurality of gateway user planes GwU modules, a GwU module accesses the shared APN-AMBR statistical table of user equipment corresponding to a data packet under a current access point when receiving the data packet, performs statistics on the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs APN-AMBR-based bandwidth control according to the statistical result.

Drawings

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

Fig. 2 is a schematic diagram of an architecture in which a gateway control plane and a user plane are separated in a non-roaming scenario.

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

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

Fig. 5 is a schematic diagram illustrating bandwidth limitation information interaction between a pair of upstream flows (sharing example) according to the present invention.

Fig. 6 is a schematic diagram illustrating bandwidth limitation information interaction between two pairs of downstream data streams (sharing example) according to an embodiment of the present invention.

Fig. 7 is a schematic diagram illustrating bandwidth limitation information interaction (shared memory) of three pairs of upstream data streams according to an embodiment of the present invention.

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

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application 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, establishing a shared access point aggregation maximum bit rate APN-AMBR statistical table for a plurality of gateway user plane GwU modules;

the S302, GwU module accesses the shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, and according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, the APN-AMBR of the user equipment under the current access point is counted, and according to the statistical result, the bandwidth control based on the APN-AMBR is carried out;

the method for establishing the APN-AMBR statistical table for the multiple GwU modules comprises the following steps:

establishing a shared access point aggregate maximum bit rate APN-AMBR statistical table for a plurality of GwU modules, comprising:

establishing the shared APN-AMBR statistical table in an independent GwU instance, or establishing the shared APN-AMBR statistical table in shared memories of a plurality of GwU instances;

the shared APN-AMBR statistical table records APN-AMBR values of each user equipment under an access point;

the GwU module accesses a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, performs statistics on the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs bandwidth control based on the APN-AMBR according to the statistical result, including:

the GwU shared data table example receives the request for accessing the shared APN-AMBR statistical table, and counts the APN-AMBR of the user equipment 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 statistical table, if the counted APN-AMBR value is smaller than the signing value of the user equipment, the decision is made to allow the data packet to be forwarded, if the counted APN-AMBR value is larger than or equal to the signing value of the user equipment, the decision is made to discard the data packet, and a response message is returned to the GwU service example, wherein the response message carries decision indication information;

the GwU modules access or modify the shared APN-AMBR statistical table by adopting a lock mutual exclusion mechanism, and only one GwU module has the right to access or modify the shared APN-AMBR statistical table at the same time;

one or more GwU instances exist in the GwU module, each GwU instance processes service data of a plurality of user equipment, and a plurality of GwU instances share an APN-AMBR statistical table; one or more GwU modules exist under one gateway control plane GwC module;

as shown in fig. 4, an apparatus for implementing bandwidth limitation of an access point according to an embodiment of the present invention includes:

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

and abandwidth control module 402, configured to access, by the GwU module, a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when the data packet is received, perform statistics on an APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and perform bandwidth control based on the APN-AMBR according to the statistical result.

Thesetting module 401 is configured to establish a shared access point aggregation maximum bit rate APN-AMBR statistical table for multiple GwU modules, and includes:

And GwU modules access or modify the shared APN-AMBR statistical table by adopting a lock mutual exclusion mechanism, and only one GwU module has the right to access or modify the shared APN-AMBR statistical table at the same time.

One or more GwU instances exist in the GwU module, each GwU instance processes service data of a plurality of user equipment, and a plurality of GwU instances share an APN-AMBR statistical table; one or more GwU modules exist below one gateway control plane GwC module.

Thebandwidth control module 402 is configured to, when receiving a data packet, the GwU module accesses a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point, performs statistics on an 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 performs bandwidth control based on the APN-AMBR according to a statistical result, and includes:

Example 1

As shown in fig. 5, this example corresponds to a non-roaming scenario, where a UE accesses a 3GPP network, creates a default bearer after activation, establishes a user session table and a bearer forwarding table for the user at GwU, and acquires and stores policies such as QoS authorization information of the user, PCC (Policy and Charging Control) rules, and the like at GwC. GwU performs APN-AMBR based bandwidth control on non-GBR bearer data flows uplink to the UE by establishing a shared statistics table for each GwU instance (the statistics table is stored in a separate GwU instance), which specifically includes the following steps:

step 501: GwU the receiving instance receives the upstream packet. Recognizing the uplink message as User Plane data GTPU (GPRS Tunnel Protocol User Plane) message, and searching the forwarding table to find GwU service instance corresponding to the User service.

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

Step 503: GwU service instance carries out bearing and forwarding table matching according to TEIDU (Tunnel identification for user plane Tunnel terminal identification), and carries out internal five-tuple matching after data is decapsulated. If the corresponding flow table and policy are matched, step 510 is performed.

Step 504: and if the current flow table and the strategy are not matched, establishing a new flow table, and forwarding the data message to a GwU (Deep Packet Inspection) instance to identify the application information of the data flow.

Step 505: and after the GwU DPI instance is matched with the relevant service information according to the local feature library, returning information such as the message and the corresponding application identifier to the GwU service instance.

Step 506: GwU, matching the service instance with TFT (transport flow template) such as quintuple according to the received application identifier, if matching the corresponding flow table and strategy, executing step 510; if the application identifier cannot be identified (cannot be matched with the corresponding flow table and policy), or is changed, the message is cached, and step 507 is executed.

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

Step 508: GwC, according to the application identifier and quintuple carried by the request message, acquires the local policy, or requests the policy rule information to the outside (PCRF, etc.).

Step 509: GwC, the policy information (including information of policies such as QoS, charging, and route forwarding) provided by local or external policy decision entity (PCRF, etc.) is returned to GwU service instance for policy enforcement.

Step 510: GwU service instance executes the load level QoS policy such as up gate control according to the current policy (local policy or policy provided by GwC), executes load binding, executes the meter statistics of the charging and usage of up data, and updates the flow into the flow table.

Step 511: GwU after the service instance executes the policy and charging related to the load and the usage statistics, it sends a request message to GwU shared statistics table instance to request the APN-AMBR decision indication or the current APN-AMBR value. The request message carries APN-AMBR identification information (e.g., ID of APN-AMBR shared meter), measurement information of current data (e.g., meter statistic), TEID and quintuple information, etc.

Step 512: GwU the shared statistical table instance receives a request message carrying measurement information and APN-AMBR identification information sent by GwU service instance. And comparing the current APN-AMBR subscription information of the UE with a local APN-AMBR shared measurement statistical table, and performing unified measurement statistics according to the measurement information carried in the request message. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is larger than the signed APN-AMBR after statistics, the data stream needs to be discarded. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is smaller than the signed APN-AMBR after statistics, the data stream can be sent. And updating the current APN-AMBR shared measurement statistical table, and deciding the discarding or forwarding of the current data flow. And returns a decision indication to the requesting GwU service instance. GwU, the execution of the statistic table item between the instances adopts a lock mutual exclusion mechanism to ensure that only one GwU instance has right to access or modify the statistic table at the same time, and the invention is not limited to the specific mechanism.

Step 513: GwU the shared statistics table example returns the decision response of APN-AMBR to the GwU service example sending the request, carries APN-AMBR indication mark, and indicates the discarding or forwarding of the current data stream. Optionally, the message carries a value of the current APN-AMBR of the shared statistics table.

Step 514: GwU the service instance receives a response message from GwU instance, the response message carries APN-AMBR execution indication mark and possibly APN-AMBR value. And (4) reducing the meter statistics of the charging and the consumption of the current uplink data, and updating the flow table. And if the APN-AMBR value is larger than the signed allowable value or indicates that the APN-AMBR exceeds the threshold value, the data flow cannot be sent and gating discarding is performed. And if the APN-AMBR value is smaller than the signing allowable value or indicates that the APN-AMBR is in the allowable range, enhancing the information to be carried, such as binding bearing information and routing forwarding information, into a data packet header, and encapsulating the data packet.

Step 515: confirming that the data packet is within the range of the 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 forwarding strategy of the data packet.

As shown in step 501-515, for the upstream data stream, the shared data statistics table is stored in an independent GwU shared data table instance, and the execution of the statistics table entry between GwU service instances adopts a lock/mutex mechanism to ensure that only one GwU instance has permission to access or modify the statistics table at the same time.

The GwU example in this embodiment may be a logical functional entity in an actually deployed network element, or may be an independent actually deployed network element; but also may be a virtualized functional device, or a processor in a functional device, or a virtualized network slice or microservice, and the invention is not limited thereto.

Example two

As shown in fig. 6, this example corresponds to a non-roaming scenario, where a UE accesses a 3GPP network, creates a default bearer after activation, establishes a user session table and a bearer forwarding table for the user at GwU, and acquires and stores policies such as QoS authorization information and PCC rules of the user at GwC. By establishing a shared APN-AMBR statistics table for each GwU instance (the shared statistics table is stored in a separate GwU shared data table instance), GwU performs APN-AMBR based bandwidth control on the downlink non-GBR bearer data stream, which specifically includes the following steps:

step 601: GwU the receiving instance receives the downstream packet.

Step 602: GwU the receiving instance recognizes the data packet as a downlink message, and finds out the GwU service instance corresponding to the user service according to the IP forwarding table.

Step 603: GwU forward the packet onto the corresponding GwU service instance.

Step 604: GwU, the service instance matches the user session table according to the IP and the virtual Routing forwarding table VRF (virtual Routing and forwarding), and performs five-tuple matching. And if the downlink data packet is matched with the flow table, determining whether to send the downlink data packet to the GwU DPI instance for further analysis according to the mark in the flow table. If the GwU DPI instance needs to be sent for further analysis, executing step 605; if the corresponding flow table and policy are matched and no further GwU DPI instance needs to be sent for further analysis, executing step 611; if the corresponding flow table is not matched, a flow table is established, the message is cached, and step 608 is executed.

Step 605: and caching the message, and sending the key information of the data message to a GwU DPI example to identify information such as application identification of the data stream.

Step 606: and after the GwU DPI instance is matched with the relevant service information according to the local feature library, returning information such as the message and the corresponding application identifier to the GwU service instance.

Step 607: GwU, matching TFT such as quintuple according to the received application identifier, if matching the corresponding flow table and strategy, executing step 611; if the application id cannot be identified or has changed, the message is cached, and step 608 is executed.

Step 608: GwU, the service instance sends request message for obtaining processing policy to GwC, where the request message carries TEIDU of the message, quintuple information, and application identifier.

Step 609: GwC, according to the information such as application identification and quintuple carried by the request message, acquires the local policy, or requests the policy rule information to the outside (for example, PCRF).

Step 610: GwC, the information provided by local or external policy decision entity (PCRF, etc.) and containing QoS and charging, route forwarding and other policies is returned to GwU service instance for policy enforcement.

Step 611: GwU service instance executes the load level QoS policy such as descending gate control according to the current policy (local policy or policy provided by GwC), executes load binding, executes the meter statistics of the charging and usage of descending data, and updates the flow into the flow table.

Step 612: GwU after the service instance executes the policy and charging related to the load and the usage statistics, it sends a request message to GwU shared statistics table instance to request the APN-AMBR decision indication or the current APN-AMBR value. The request message carries APN-AMBR identification information (e.g., ID of APN-AMBR shared meter), measurement information of current data (e.g., meter statistic), TEID and quintuple information, etc. GwU, the execution of the statistic table item between the instances adopts a lock mutual exclusion mechanism to ensure that only one GwU instance has right to access or modify the statistic table at the same time, and the invention is not limited to the specific mechanism.

Step 613: GwU the shared statistical table instance receives a request message carrying measurement information and APN-AMBR identification information sent by GwU service instance. And comparing the current APN-AMBR subscription information of the UE with a local APN-AMBR shared measurement statistical table, and performing unified measurement statistics according to the measurement information carried in the request message. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is larger than the signed APN-AMBR after statistics, the data stream needs to be discarded. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is smaller than the signed APN-AMBR after statistics, the data stream can be sent. And updating the current APN-AMBR shared measurement statistical table, and deciding the discarding or forwarding of the current data flow. And returns a decision indication to the requesting GwU service instance.

Step 614: GwU the shared statistics table example returns the decision response of APN-AMBR to the GwU service example sending the request, carries APN-AMBR indication mark, and indicates the discarding or forwarding of the current data stream. Optionally, the message carries a value of the current APN-AMBR of the shared statistics table.

Step 615: GwU the service instance receives a response message from GwU instance, the response message carries APN-AMBR execution indication mark and possibly APN-AMBR value. And (4) reducing the meter statistics of the charging and the consumption of the current downlink data, and updating the flow table. And if the APN-AMBR value is larger than the signed allowable value or indicates that the APN-AMBR exceeds the threshold value, the data flow cannot be sent and gating discarding is performed. And if the APN-AMBR value is smaller than the signing allowable value or indicates that the APN-AMBR is in the allowable range, enhancing the information to be carried, such as binding bearing information and routing forwarding information, into a data packet header, and encapsulating the data packet.

Step 616: confirming that the data packet is within the range of the APN-AMBR allowed by the subscription, the GwU service instance issues the data packet according to the routing forwarding strategy of the data packet.

As shown in step 601-616, for the downstream data stream, the shared data statistics table is stored in an independent GwU shared data table instance, and the execution of the statistics table entry between GwU service instances adopts a lock/mutex mechanism to ensure that only one GwU instance has permission to access or modify the statistics table at the same time.

Example three

As shown in fig. 7, this example corresponds to a non-roaming scenario, where a UE accesses a 3GPP network, creates a default bearer after activation, establishes a user session table and a bearer forwarding table for the user at GwU, and acquires and stores policies such as QoS authorization information and PCC rules of the user at GwC. By establishing a shared APN-AMBR statistical table for each GwU instance (the shared statistical table is stored in a shared memory of each GwU instance), GwU performs APN-AMBR-based bandwidth control on non-GBR bearer data flows uplink to the UE, specifically including the following steps:

step 701: GwU the receiving instance receives the upstream packet. Recognizing the uplink message as user plane data GTPU message, looking up the forwarding table to find GwU service instance corresponding to the user service

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

Step 703: GwU service instance carries out matching of bearing forwarding table according to TEIDU, and carries out matching of internal five-tuple after decapsulating data. If the corresponding flow table and policy are matched, step 710 is performed.

Step 704: and if the current flow table and the strategy cannot be matched, establishing a new flow table, forwarding the data message to the GwU DPI example, and identifying the application information of the data flow.

Step 705: and after the GwU DPI instance is matched with the relevant service information according to the local feature library, returning information such as the message and the corresponding application identifier to the GwU service instance.

Step 706: GwU, the service instance matches the TFT such as quintuple according to the received application identifier, if the corresponding flow table and strategy are matched, then step 710 is executed; if the application id cannot be identified (cannot be matched to the corresponding flow table and policy), or is changed, the message is cached, and step 707 is executed.

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

Step 708: GwC, according to the service mark and quintuple carried by the request message, acquires the local policy, or requests the policy rule information to the outside (PCRF).

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

Step 710: GwU service instance executes the load level QoS policy such as up gate control according to the current policy (local policy or policy provided by GwC), executes load binding, executes the meter statistics of the charging and usage of up data, and updates the flow into the flow table. And accessing a shared APN-AMBR statistical table in a shared memory of each GwU example, carrying out meter measurement, and comparing the current APN-AMBR subscription information of the UE. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is larger than the signed APN-AMBR after counting, executing a gating strategy on the data, and discarding (optionally counting into discarded traffic). If the maximum bit rate of all non-GBRs of the UE under the APN is smaller than the maximum bit rate of the signed APN-AMBR after statistics, the UE needs to encapsulate the data again and send the data according to a routing strategy, and information to be carried, such as binding bearer information and routing forwarding information, is enhanced into a data packet header to encapsulate the data packet.

GwU, the execution of the statistic table item between the instances adopts a lock mutual exclusion mechanism to ensure that only one GwU instance has right to access or modify the statistic table at the same time, and the invention is not limited to the specific mechanism.

Step 711: confirming that the data packet is within the range of the 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 forwarding strategy of the data packet.

As shown in 701-711, for the upstream data stream, the shared data statistics table is stored in the independent GwU shared data table instance, and the execution of GwU service instances on the statistics table entry adopts a lock/mutex mechanism to ensure that only one GwU instance has permission to access or modify the statistics table at the same time.

Example four

As shown in fig. 8, this example corresponds to a non-roaming scenario, where a UE accesses a 3GPP network, creates a default bearer after activation, establishes a user session table and a bearer forwarding table for the user at GwU, and acquires and stores policies such as QoS authorization information and PCC rules of the user at GwC. By establishing a shared APN-AMBR statistical table for each GwU instance (the shared statistical table is stored in a shared memory of each GwU instance), GwU performs APN-AMBR-based bandwidth control on a downlink non-GBR bearer data stream, specifically including the following steps:

step 801: GwU the receiving instance receives the downstream packet.

Step 802: GwU the receiving instance recognizes the data packet as a downlink message, and finds out the GwU service instance corresponding to the user service according to the IP forwarding table.

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

Step 804: GwU the service instance matches the user session table according to the IP and the VRF and performs five-tuple matching. And if the downlink data packet is matched with the flow table, determining whether to send the downlink data packet to the GwU DPI instance for further analysis according to the mark in the flow table. If the GwU DPI instance needs to be sent for further analysis, executing step 805; if the corresponding flow table and policy are matched and there is no need to send the GwU DPI instance for further analysis, step 811 is performed. If the corresponding flow table is not matched, a flow table is established, the message is cached, and step 808 is executed.

Step 805: if the current flow table is matched, but the GwU DPI is required to be further analyzed according to the mark in the flow table, caching the message, and sending the key information of the data message to the GwU DPI instance to identify the information such as the application identifier of the data flow.

Step 806: and after the GwU DPI instance is matched with the relevant service information according to the local feature library, returning information such as the message and the corresponding application identifier to the GwU service instance.

Step 807: GwU, the service instance matches the TFT such as quintuple according to the received application identifier, if the corresponding flow table and strategy are matched, then step 811 is executed. If the application identifier cannot be identified or is changed, the packet is cached, and step 808 is performed, and if the application identifier can be matched with the flow table to obtain the detailed policy, step 811 is performed.

Step 808: GwU, the service instance sends request message for obtaining processing policy to GwC, where the request message carries TEIDU of the message, quintuple information, and application identifier.

Step 809: GwC, according to the service identification and quintuple carried by the request message, acquires the local policy, or requests the policy rule information to the outside (for example, PCRF).

Step 810: GwC, the information of the policy, which is provided locally or by an external policy decision entity such as PCRF, and includes QoS, charging, and routing forwarding, is returned to GwU service instance for policy enforcement.

Step 811: GwU service instance executes the load level QoS policy such as descending gate control according to the current policy (local policy or policy provided by GwC), executes load binding, executes the meter statistics of the charging and usage of descending data, and updates the flow into the flow table. And accessing a shared APN-AMBR statistical table in a shared memory of each GwU example, carrying out meter measurement, and comparing the current APN-AMBR subscription information of the UE. And if the maximum bit rate of all non-GBR bearers of the UE under the APN is larger than the signed APN-AMBR after counting, executing a gating strategy on the data, and discarding (optionally counting into discarded traffic). If the maximum bit rate of all non-GBRs of the UE under the APN is smaller than the maximum bit rate of the signed APN-AMBR after statistics, the UE needs to encapsulate the data again and send the data according to a routing strategy, and information to be carried, such as binding bearer information and routing forwarding information, is enhanced into a data packet header to encapsulate the data packet.

Step 812: confirming that the data packet is within the range of the APN-AMBR allowed by the subscription, the GwU service instance issues the data packet according to the routing forwarding strategy of the data packet.

As described above 801-.

In the above examples one to four, GwU may forward data directly or by defining a new interface, and the present invention is not limited thereto.

The present invention provides a method and an apparatus for implementing access point bandwidth limitation, where a shared access point aggregated maximum bit rate APN-AMBR statistical table is established for multiple gateway user plane GwU modules, a GwU module accesses a shared APN-AMBR statistical table of a user equipment corresponding to a data packet under a current access point when receiving the data packet, and performs 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 performs bandwidth control based on the APN-AMBR according to a statistical result.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits, and accordingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present invention is not limited to any specific form of combination of hardware and software.

It should be noted that the present invention can be embodied in other specific forms, and various changes and modifications can be made by those skilled in the art without departing from the spirit and scope of the invention.

Claims

1. A method of implementing access point bandwidth limiting, the method comprising:

the GwU module accesses the shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, and performs statistics on the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and performs bandwidth control based on the APN-AMBR according to the statistical result;

the GwU module accesses the shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, and according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, the APN-AMBR of the user equipment under the current access point is counted, and according to the statistical result, the bandwidth control based on the APN-AMBR is performed, which includes:

GwU, when receiving a data packet, a service instance sends a request for accessing a shared APN-AMBR statistical table to an independent GwU shared data table instance, after the GwU shared data table instance receives the request for accessing the shared APN-AMBR statistical table, the GwU shared data table instance counts the APN-AMBR of the user equipment 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 statistical table, and returns a response message to the GwU service instance, and the GwU service instance forwards or discards the data packet according to the response message; or,

GwU accessing the shared APN-AMBR statistical table stored in the shared memory by the service instance, counting the APN-AMBR of the user equipment 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 statistical table, and forwarding or discarding the data packet according to the counted APN-AMBR value;

2. The method of claim 1, wherein:

3. The method of claim 1, wherein:

GwU modules adopt a lock and mutual exclusion mechanism to access or modify the shared APN-AMBR statistical table, only one GwU module has the authority to access or modify the shared APN-AMBR statistical table at the same time.

4. The method of claim 1, wherein:

GwU, one or more GwU instances exist in the module, each GwU instance handles traffic data of multiple user equipments, multiple GwU instances share an APN-AMBR statistical table; one or more GwU modules exist below one gateway control plane GwC module.

5. The method of claim 2, wherein:

6. The method of claim 2, wherein:

7. An apparatus for implementing access point bandwidth limiting, comprising:

the bandwidth control module is used for the GwU module to access a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when receiving the data packet, to count the APN-AMBR of the user equipment under the current access point according to the measurement information of the current data packet and the APN-AMBR value obtained by accessing the shared APN-AMBR statistical table, and to perform bandwidth control based on the APN-AMBR according to the statistical result;

8. The apparatus of claim 7, wherein:

a setting module configured to establish a shared access point aggregated maximum bit rate APN-AMBR statistical table for a plurality of GwU modules, comprising:

9. The apparatus of claim 7, wherein:

10. The apparatus of claim 7, wherein:

11. The apparatus of claim 8, wherein:

a bandwidth control module, configured to access, by the GwU module, a shared APN-AMBR statistical table of the user equipment corresponding to the data packet under the current access point when the data packet is received, perform statistics on an 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 perform bandwidth control based on the APN-AMBR according to a statistical result, including:

12. The apparatus of claim 8, wherein: