Service control method and system, evolved nodeB, and packet data network gateway

• US 9,451,502 B2
• Filed: 05/08/2013
• Issued: 09/20/2016
• Est. Priority Date: 11/19/2010
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Guo, Junxiang, Lei, Lingyun
• Primary Examiner(s): Rutkowski, Jeffrey M
• Assistant Examiner(s): Rivas, Salvador E
• Application Number:
  US13/889,706
• Publication Number:
  US 20130242733A1
• Time in Patent Office: 1,231 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 72/12 Wireless traffic scheduling
• CPC Class Codes: H04W 88/08 Access point devices
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

Embodiments of the present invention disclose a service control method and system, an evolved NodeB, and a packet data network gateway, to perform resource scheduling on a packet. The method provided in an embodiment of the present invention includes: receiving, by an evolved NodeB, a packet; determining, by the evolved NodeB, a service control policy corresponding to the packet according to correspondence between a service application type and a service control policy and a service application type corresponding to the packet; and performing, by the evolved NodeB, resource scheduling on the packet according to the service control policy corresponding to the packet. Embodiments of the present invention further include a service control system, an evolved NodeB, and a packet data network gateway.

Claims

1. A service control method, comprising:

receiving, by an evolved NodeB, a packet;

determining, by the evolved NodeB, a service control policy corresponding to the packet according to correspondence between the service control policy and a service application type corresponding to the packet; and

performing, by the evolved NodeB, resource scheduling on the packet according to the service control policy corresponding to the packet by determining an identity of a flow to which the packet belongs and at least one of;

controlling the transmission and scheduling of resources of all or some flows of a user according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of all or some flows of a user includes;

determining whether a privacy policy for each of all or some flows allows inspection of the flows,

delivering service control policy information in a process of setting up the all or some flows of the user when the privacy policy allows inspection of the flows, and

differentiating flows of the user to which the packet belongs from other flows, and

controlling the transmission and scheduling of resources of a specific flow of all users or a group of users according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of the specific flow of all users or the group of users includes;

determining whether a privacy policy for the specific flow allows inspection of the specific flow

delivering the service control policy corresponding to the packet in a process of setting up the specific flow for a first time or in a process of updating the service control policy when the privacy policy allows inspection of the specific flow, and

differentiating the specific flow to which the packet belongs from other flows.

2. The method according to claim 1, wherein the correspondence between the service application type and the service control policy is stored by the evolved NodeB.

3. The method according to claim 1, wherein the correspondence between the service application type and the service control policy is carried in service control policy information sent from a first entity, wherein the first entity is configured to implement a policy and charging enforcement function.

4. The method according to claim 1, the method further comprising:

obtaining, by the evolved NodeB, the service application type corresponding to the packet.

5. The method according to claim 4, wherein

the service application type corresponding to the packet is sent from an inspecting entity to the evolved NodeB, wherein the inspecting entity is configured to inspect the service application type corresponding to the packet.

6. The method according to claim 5, wherein the inspecting entity is located in a packet data network gateway (PDN-GW).

7. The method according to claim 4, wherein the obtaining, by the evolved NodeB, the service application type corresponding to the packet comprises:

determining, by the evolved NodeB by using a filter, an identity of a flow to which the packet belongs;

searching, by the evolved NodeB, for the service application type corresponding to the identity of the flow to which the packet belongs, in mapping between the identity of the flow and the service application type.

8. The method according to claim 7, wherein the mapping between the identity of the flow and the service application type is obtained by the evolved NodeB from a packet data network gateway (PDN-GW).

9. The method according to claim 7, wherein the mapping between the identity of the flow and the service application type is stored by the evolved NodeB.

10. The method according to claim 7, wherein information of the filter is obtained by the evolved NodeB from the PDN-GW.

11. A device, comprising a transmitter, a processor and a memory, wherein:

the transmitter is configured to receive a packet;

the processor is configured to determine a service control policy corresponding to the packet according to correspondence between the service control policy and a service application type corresponding to the packet; and

to perform resource scheduling according to the service control policy corresponding to the packet

and to determine an identity of a flow to which the packet belongs and at least one of;

control the transmission and scheduling of resources of all or some flows of a user according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of all or some flows of a user includes;

determining whether a privacy policy for each of all or some flows allows inspection of the flows,

delivering service control policy information in a process of setting up the all or some flows of the user when the privacy policy allows inspection of the flows, and

differentiating flows of the user to which the packet belongs from other flows, and

control the transmission and scheduling of resources of a specific flow of all users or a group of users according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of the specific flow of all users or the group of users includes;

determining whether a privacy policy for the specific flow allows inspection of the specific flow,

delivering the service control policy corresponding to the packet in a process of setting up the specific flow for a first time or in a process of updating the service control policy when the privacy policy allows inspection of the specific flow, and

differentiating the specific flow to which the packet belongs from other flows.

12. The device according to claim 11, the memory is configured to store the correspondence between the service application type and the service control policy.

13. The device according to claim 11, wherein the transmitter is further configured to receive service control policy information carrying the correspondence between the service application type and the service control policy.

14. The device according to claim 11, wherein the transmitter is further configured to receive the service application type corresponding to the packet from an inspecting entity, wherein the inspecting entity is configured to inspect the service application type corresponding to the packet.

15. The device according to claim 11, wherein the processor is further configured to determine by using a filter an identity of a flow to which the packet belongs, and search, in mapping between the identity of the flow and the service application type, for the service application type corresponding to the identity of the flow to which the packet belongs.

16. The device according to claim 15, wherein the transmitter is further configured to receive the mapping between the identity of the flow and the service application type from a packet data network gateway (PDN-GW).

17. The device according to claim 15, wherein the memory is further configured to store the mapping between the identity of the flow and the service application type.

18. The device according to claim 15, wherein the transmitter is further configured to receive information of the filter from a PDN-GW.

19. The device according to claim 11, wherein the device is an evolved NodeB.

20. A system, comprising:

an evolved NodeB, configured to receive a packet, and perform resource scheduling according to a service control policy corresponding to the packet, wherein the service control policy corresponding to the packet is determined according to correspondence between the service control policy and a service application type corresponding to the packet,

wherein performing resourcing scheduling according to the service control policy corresponding to the packet comprises determining an identity of a flow to which the packet belongs and at least one of;

control the transmission and scheduling of resources of all or some flows of a user according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of all or some flows of a user includes;

determining whether a privacy policy for each of all or some flows allows inspection of the flows,

delivering service control policy information in a process of setting up the all or some flows of the user when the privacy policy allows inspection of the flows, and

differentiating flows of the user to which the packet belongs from other flows, and

control the transmission and scheduling of resources of a specific flow of all users or a group of users according to the service control policy corresponding to the packet, wherein controlling the transmission and scheduling of resources of the specific flow of all users or the group of users includes;

determining whether a privacy policy for the specific flow allows inspection of the specific flow,

delivering the service control policy corresponding to the packet in a process of setting up the specific flow for a first time or in a process of updating the service control policy when the privacy policy allows inspection of the specific flow, and

differentiating the specific flow to which the packet belongs from other flows.